D
D. Kirkpatrick
Windows XP, current service packs installed - on auto updates.
We have a licensed version of Microsoft Works installed (2004?) with
MS Word 2002 as a part of the package.
All was working fine until sometime within the last week.
Now when we attempt to open MS Word 2002 to a blank document or open
an existing document it reports an error that we do not have enough
storage or memory (presumably RAM).
We have 256 MB Ram and the HD is showing 15 GB storage which is about
1/2 full on this drive.
We also have a copy of Office 97 installed that has never been a
problem. When we open Office 97 (Word) it opens and runs fine, and
when we open any Word document with it, it also opens and runs fine.
It appears that Works, and/or MS Word 2002 may be damaged.
I can reinstall Works fromt he installer CD but I am also reading some
threads suggesting that an update received in August from Microsoft
may have done something to Word 2002 or similar versions.
Anyone else having a similar problem?
Will reinstalling Works clear this bug or is it Windows update related?
Thanks.
DMK
We have a licensed version of Microsoft Works installed (2004?) with
MS Word 2002 as a part of the package.
All was working fine until sometime within the last week.
Now when we attempt to open MS Word 2002 to a blank document or open
an existing document it reports an error that we do not have enough
storage or memory (presumably RAM).
We have 256 MB Ram and the HD is showing 15 GB storage which is about
1/2 full on this drive.
We also have a copy of Office 97 installed that has never been a
problem. When we open Office 97 (Word) it opens and runs fine, and
when we open any Word document with it, it also opens and runs fine.
It appears that Works, and/or MS Word 2002 may be damaged.
I can reinstall Works fromt he installer CD but I am also reading some
threads suggesting that an update received in August from Microsoft
may have done something to Word 2002 or similar versions.
Anyone else having a similar problem?
Will reinstalling Works clear this bug or is it Windows update related?
Thanks.
DMK