[pendragon]

Recently, when saving a Word document in Office 2004 (Service Pack 1), the following dialog will appear on my DP 800, 10.3.7, 1.25 GB RAM:

“Word cannot save or create this file. The disk may be full or write protected. Try one or more of the following:
• Free more memory
• Make sure that the disk you want to save the file on is not full, write-protected, or damaged.
(AutoRecovery save of Document [name])

I have Repaired Permissions, FSCK’d, Safe Booted, run TTP and DiskWarrior (both without issue). Also, I have run all routines in Cocktail.
I am not allowing Fast Saves.

Thinking the issue may be OS related, I reinstalled via the Combo updater. No joy.

If I quit Word and relaunch it, the problem disappears. But then the next day, the problem returns, as if the problem were related to the clock.

I am using 8 GB of an 80 GB drive. I am Saving to Desktop.

This “issue’ is most vexing and I remain confused. And frustrated too!

And finally, I know many of you are most busy in the next few days, so your time is especially appreciated; and indeed, this too shall pass (I hope). Still, comments, suggestions, musings, ramblings, and guesses will be warmly received.

Season cheers to all!

[f1000]

Have you tried trashing the MS User Data folder in your Documents folder? Don't 'trash' it per se, but drag it out of your Documents folder to a safe location and let Word make a new one upon restart.

[pendragon]

I'm now about 98% certain I have found the problem.

Word works as advertised until Cocktail 3.5 is run. Then, the problem as originally described occurs. What specific function from within Cocktail that is causing this (I run most everything) is still TBD, at least to me.

I am able to reproduce this condition/cause & effect, thus my conclusion.

UPDATE: As of now, I have determined that Cocktail 3.5 will work as long as I am running it without the cache cleaning option.

I am now working with Kristofer Szymanski to see if I can isolate the specific function within Cocktail 3.5 that is conflicting with Word.

Perhaps in a few days, I’ll have more to post.

[pendragon]

Problem Solved! Well sorta.

After a bit of experimenting, I have finally determined that Cocktail 3.5 works fine as long as I am running it without enabling the “Other Temporary Files” in the System Cache Cleaning option.

When the System Cache cleaning/Other Temporary Files is enabled, the problem originally described, always occurs.

My work with Kristofer Szymanski continues, but I have no knowledge of what or when the fix will be implemented.

[pendragon]

Just to closeout this issue-

Comments from Cocktail, 3 Jan 05:
"Thank you very much for your help. I was now able to replicate this "bug". The problem is that Microsoft Word is saving a lot of temporary files in /tmp directory when a document is open and edited. If you run Cocktail and clean these files, Word tells you that it is not able to save the document (but it is). There is not much I can do about this problem because Words temporary files have no extension or standard name. However the "Other temporary files" option will be no longer be enabled by default in Cocktail 3.5.1."

How nice it is to work with a developer who is both responsive and technically competent. Cocktail remains a great product.

Bravo to Kristofer Szymanski!