G
Hey folks, this is my first post and a last desperate attempt to get
Office 2004 to work properly on my machine. I searched a bit to see if
this issue has been addressed but couldn't find anything.
First a little background: I have a 1.8ghz [dual processor] G5 running
10.4.3 and I have been running Office X without any issues. I bought
Office 2004 Standard edition [upgrade] to keep everything current on my
machine. I'm a freelance art director/graphic designer so keeping
current usually makes my life easier.
Currently I use Font Book as my font manager. This is my work machine,
I don't have any games or other freak programs installed.
Installation seemed to go fine. I entered my key, it searched and found
the previous version's info and the installation went without a
hitch. When I went to open word for the first time I got these
continual messages saying that my fonts were corrupt. I called MS
support twice they had me throw out preferences, rename my font folder,
verify and repair my permissions and nothing seemed to work. Like I
mentioned before, I'm a graphics guy so I have quite a few fonts.
They are all stored in a separate folder in my documents folder. I
ended up stripping out all but the system fonts and a few fonts
installed by MS and Quark. Still had the same problem. I've
un-installed the program and reinstalled it with no effect. With the
limited number of open fonts, I can click through the corrupt font
warnings and the program finally opens fine. I can close it, restart
the machine and it opens fine until I install another font and the
whole issue starts up again.
Oh, and I also installed the MS update offered off Mactopia.
This is getting on my nerves. I don't believe that every font is
corrupt; they work fine on every other program including Office X and
as read on, there is more evidence that the font's seem to be good.
One other thing that is happening, I'm not sure it's related [other
than it's driving me nuts], but Entourage opens, gathers all the info
from the previous version except for the last three weeks of incoming
mail [go figure].
Now here is where things get interesting. I have only one user on my
machine, that's me. So I try an experiment and create a new user
account. I log off my account, create and log into the new account. I
open word and everything is as it should be. So I need to mess with the
fonts. Considering all my personal fonts are in my documents file under
my old account, I grab a CD with fonts and install them into a folder
under the documents folder in the new user account. I go to font book,
install a token font, and open word up again. Everything is good, no
corrupt message. Now I'm baffled. I guess there is something in my
other profile that is causing this [these] issue. I guess I could go
through all the work to transfer all my files to the new user account
but this still doesn't explain the problem.
Anyone have any ideas? MS support couldn't offer any other solutions
other than a phone number to get my money back. Although I've read
about a few other folks with similar issues in the apple forums, I
haven't found anything that completely resolves this issue. Anyone
got a miracle?
-jeffrey
Office 2004 to work properly on my machine. I searched a bit to see if
this issue has been addressed but couldn't find anything.
First a little background: I have a 1.8ghz [dual processor] G5 running
10.4.3 and I have been running Office X without any issues. I bought
Office 2004 Standard edition [upgrade] to keep everything current on my
machine. I'm a freelance art director/graphic designer so keeping
current usually makes my life easier.
Currently I use Font Book as my font manager. This is my work machine,
I don't have any games or other freak programs installed.
Installation seemed to go fine. I entered my key, it searched and found
the previous version's info and the installation went without a
hitch. When I went to open word for the first time I got these
continual messages saying that my fonts were corrupt. I called MS
support twice they had me throw out preferences, rename my font folder,
verify and repair my permissions and nothing seemed to work. Like I
mentioned before, I'm a graphics guy so I have quite a few fonts.
They are all stored in a separate folder in my documents folder. I
ended up stripping out all but the system fonts and a few fonts
installed by MS and Quark. Still had the same problem. I've
un-installed the program and reinstalled it with no effect. With the
limited number of open fonts, I can click through the corrupt font
warnings and the program finally opens fine. I can close it, restart
the machine and it opens fine until I install another font and the
whole issue starts up again.
Oh, and I also installed the MS update offered off Mactopia.
This is getting on my nerves. I don't believe that every font is
corrupt; they work fine on every other program including Office X and
as read on, there is more evidence that the font's seem to be good.
One other thing that is happening, I'm not sure it's related [other
than it's driving me nuts], but Entourage opens, gathers all the info
from the previous version except for the last three weeks of incoming
mail [go figure].
Now here is where things get interesting. I have only one user on my
machine, that's me. So I try an experiment and create a new user
account. I log off my account, create and log into the new account. I
open word and everything is as it should be. So I need to mess with the
fonts. Considering all my personal fonts are in my documents file under
my old account, I grab a CD with fonts and install them into a folder
under the documents folder in the new user account. I go to font book,
install a token font, and open word up again. Everything is good, no
corrupt message. Now I'm baffled. I guess there is something in my
other profile that is causing this [these] issue
through all the work to transfer all my files to the new user account
but this still doesn't explain the problem.
Anyone have any ideas? MS support couldn't offer any other solutions
other than a phone number to get my money back. Although I've read
about a few other folks with similar issues in the apple forums, I
haven't found anything that completely resolves this issue. Anyone
got a miracle?
-jeffrey