Weird file save/quit problem

[new_mac_user]

Version: 2008 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel I've got a weird one for you. I'm mounting a shared drive using smb. Mac OSX 10.5.8. If I open MS Word and create/update a document then save, no problems. I can do incremental saves as I change the file until the cows come home without a problem. If I save the file, CLOSE the file, then quit Word -- there are no problems.

HOWEVER -- if I try to quit and save (cmd-q [yes to save] or cmd-s then cmd-q), not only does MS Word hang but the share mount hangs and I lose all connectivity to the share. I originally thought the share or a file was corrupted in the share because I would lose the ability to "ls -l" in the directory. If I want a minute, all "ls" functionality to all directories in the share is lost as well so what ever Word is doing is really screwing up teh mount point.

With Word hung, trying to kill Word through the Activity Manager doesn't work. Trying to disconnect or re-connect the share doesn't work. Trying to shut the O/S down gracefully doesn't work, it hangs too. The only thing I can do is hard power off.

I've tried this with at least a dozen Word files in different locations throughout several shares, some new, others pre-existing -- same response. It does NOT happen with Powerpoint or other MS applications though. Save/quit works fine when using the internal drive on the MBP.

Any thoughts on why a "save/close/quit" works but a "save/quit" doesn't??

 

[John McGhie]

It's a bug

Word is posting a wait for completion to the server, meanwhile, OS X is
dropping the network connection, and nobody thought of this scenario

Use Help>Send Feedback to tell Microsoft about that one. Include a working
email address so they can get back to you.

Cheers

Version: 2008 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel I've
got a weird one for you. I'm mounting a shared drive using smb. Mac OSX
10.5.8. If I open MS Word and create/update a document then save, no problems.
I can do incremental saves as I change the file until the cows come home
without a problem. If I save the file, CLOSE the file, then quit Word -- there
are no problems.

HOWEVER -- if I try to quit and save (cmd-q [yes to save] or cmd-s then
cmd-q), not only does MS Word hang but the share mount hangs and I lose all
connectivity to the share. I originally thought the share or a file was
corrupted in the share because I would lose the ability to "ls -l" in the
directory. If I want a minute, all "ls" functionality to all directories in
the share is lost as well so what ever Word is doing is really screwing up teh
mount point.

With Word hung, trying to kill Word through the Activity Manager doesn't work.
Trying to disconnect or re-connect the share doesn't work. Trying to shut the
O/S down gracefully doesn't work, it hangs too. The only thing I can do is
hard power off.

I've tried this with at least a dozen Word files in different locations
throughout several shares, some new, others pre-existing -- same response. It
does NOT happen with Powerpoint or other MS applications though. Save/quit
works fine when using the internal drive on the MBP.

Any thoughts on why a "save/close/quit" works but a "save/quit" doesn't??

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!

--

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]