Print and save problem

E

Eleanor

Hi,
I hope someone can help.
It happens to me at least 2-3 a day. When I try to print or save, Word pop
up a message saying, "Word Cannot Print", or "Word Cannot Save". I don't
what causes this problem?!

We're running OS X 10.2.8, with Office v.X 10.5, 384MB of RAM.

I tried calling Microsoft support. They said there's the not enough of RAM.
That happens when there are too many programs open and/or the MS
Word's been opened for a long time.

Can someone tell me is that the case? Or anyone has some suggestions to
fix this problem? Thanks.

EC
 
J

John McGhie [MVP - Word]

Eleanor:

I hope you didn't pay $35.00 for that answer, because it is wrong. Absolute
rubbish (I nearly used a very rude word there...). Doesn't even apply to
the product you are using. If you did pay, get back to them and demand a
refund. Tell them I said so (use my name, and tell them I will refer it to
Mike Sampson if they wish). Again: Use his name. If they give you any
more nonsense, take their name and email me.

The actual problem is a bug in Word X. Search this newsgroup for "Unable to
save" and you will find multiple instances of the work-arounds (there's no
"good" answer).

The basics of the fix are: Apply all the service releases, then use Apple's
Disk Utility to Repair Permissions. To fix yours, you will probably have
to:

1) Run the uninstall utility from the value pack of your Office CD

2) Apply the latest updates to your operating system

3) Reinstall Office

4) Repair Permissions

5) Apply all service releases in the order described on the Microsoft
website

6) Repair permissions again

7) Reboot OS X

That will make it "better". Not fixed, but happens less often.

Cheers



from said:
Hi,
I hope someone can help.
It happens to me at least 2-3 a day. When I try to print or save, Word pop
up a message saying, "Word Cannot Print", or "Word Cannot Save". I don't
what causes this problem?!

We're running OS X 10.2.8, with Office v.X 10.5, 384MB of RAM.

I tried calling Microsoft support. They said there's the not enough of RAM.
That happens when there are too many programs open and/or the MS
Word's been opened for a long time.

Can someone tell me is that the case? Or anyone has some suggestions to
fix this problem? Thanks.

EC

--

Please respond only to the newsgroup to preserve the thread.

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs
+61 4 1209 1410, mailto:[email protected]
 
D

Dayo Mitchell

Eleanor,
For extended directions on what John recommends, see:

See here to make sure you are fully updated:
http://www.mcgimpsey.com/macoffice/office/vxversions.html

Then check for general troubleshooting tips:
http://www.mcgimpsey.com/macoffice/word/troubleshooting.html

John, are you saying it's the same thing we've been seeing lately? because
she isn't in Panther. And I personally wouldn't try running OS X with 384MB
of RAM, although I hear it's doable.

On the other hand, I get the impression Word is just slow with low memory,
not actually unable to function. Eleanor, did you test whether you get the
problem with Word when you have just opened it, and with no other programs
open?

Dayo
 
E

Eleanor

Hi John,

Thanks for the suggestion. I will give it a try and let
you know.

Actually, I didn't pay for the call. The Office v.X comes
with 2 free call support. So, I just want to see what
Microsoft will say about this. I thought the solution was
too simple, that's why I posted my problem on the
newsgroup.

EC
 
J

John McGhie [MVP - Word]

Hi Dayo:

Yes, I am. I think it's a Unix bug, not a specific Panther bug, but for
some reason we see it more often in Panther.

The old iBooks were limited to 384 MB of memory: that's all they will hold.
OS X runs fine in that, as does Office X and later versions. Unix is
actually easier on memory than Windows, but PowerPC code is twice the size
of WinTel code, so you get about the same result: 256 MB or better will
produce a useable system.

What slows Word down is motherboard and disk rather than processor. My
machine at work has a 350 MHz CPU, but Word's quite useable because it used
to be a server and has a fast SCSI disk and motherboard.

Last night on housemate Josie's laptop we hit the wrong button and
up-sampled a bitmap to 17 GB. That took 45 minutes to re-draw the screen on
a 512 MB memory 2.8 GHz machine: again: slow disk and motherboard on the
laptop is the culprit :)

Cheers

This responds to article
from "Dayo said:
Eleanor,
For extended directions on what John recommends, see:

See here to make sure you are fully updated:
http://www.mcgimpsey.com/macoffice/office/vxversions.html

Then check for general troubleshooting tips:
http://www.mcgimpsey.com/macoffice/word/troubleshooting.html

John, are you saying it's the same thing we've been seeing lately? because
she isn't in Panther. And I personally wouldn't try running OS X with 384MB
of RAM, although I hear it's doable.

On the other hand, I get the impression Word is just slow with low memory,
not actually unable to function. Eleanor, did you test whether you get the
problem with Word when you have just opened it, and with no other programs
open?

Dayo

--

Please respond only to the newsgroup to preserve the thread.

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs
+61 4 1209 1410, mailto:[email protected]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top