T
Tony
Hi,
Word 2004 (and previously Word v.X) is the only application that
unexpectedly quits and corrupts its own preference and setting files in
our Mac OS X 10.2.8 and Mac OS X 10.3.4 systems (PowerMacs, PowerBooks,
iMacs and eMacs), which otherwise are rock solid. This is a positive
criticism: please, please, please, make Word 2004 a truly Mac OS X
application: stable as the OS itself! Thanks.
Again, it is amazing to me that only Word causes these annoying
problems in Mac OS X. And we use dozens if not hundreds of applications
which never --or almost never-- ever quit.
Word quits unexpectedly mostly when opening files, closing files and
--mostly-- when copy/pasting/cutting text in simple or 100-page
documents even without tables or pictures. But he problem is
unpredictable. You cannot know when it will hit.
Note: deleting all current and previous Office versions and
clean-reinstalling Office 2004 (or Office v.X latest version) does not
help. I used the Remove Office (version 11.0.0) that comes with Office
2004. I also experienced this problem on Mac OS X v.X up to the latest
10.1.5 version.
I guess it has something to do with the "peculiar" way in which Office
(v.X and also 2004) handles the memory. Or else why only with Word and
not the other applications?
Thanks.
Word 2004 (and previously Word v.X) is the only application that
unexpectedly quits and corrupts its own preference and setting files in
our Mac OS X 10.2.8 and Mac OS X 10.3.4 systems (PowerMacs, PowerBooks,
iMacs and eMacs), which otherwise are rock solid. This is a positive
criticism: please, please, please, make Word 2004 a truly Mac OS X
application: stable as the OS itself! Thanks.
Again, it is amazing to me that only Word causes these annoying
problems in Mac OS X. And we use dozens if not hundreds of applications
which never --or almost never-- ever quit.
Word quits unexpectedly mostly when opening files, closing files and
--mostly-- when copy/pasting/cutting text in simple or 100-page
documents even without tables or pictures. But he problem is
unpredictable. You cannot know when it will hit.
Note: deleting all current and previous Office versions and
clean-reinstalling Office 2004 (or Office v.X latest version) does not
help. I used the Remove Office (version 11.0.0) that comes with Office
2004. I also experienced this problem on Mac OS X v.X up to the latest
10.1.5 version.
I guess it has something to do with the "peculiar" way in which Office
(v.X and also 2004) handles the memory. Or else why only with Word and
not the other applications?
Thanks.