Not only does it not happen on normal folders inside the VM, it doesn't happen when I start a new Word file and save it in the shared folders. It only seems to affect files which I already have open, perhaps because they have gone through a few cycles of going to sleep and waking up (the laptop in OS X, *not* the VM).

1) I create a new word file, save it in nonshared space - no problem
2) I take a new word file, save it in shared folder - no problm
3) I take already open file, try to save it, or save as, etc - doesn't work (gives error, and it even tells me it's postponing the autosaving periodically, for the same reason - out of space or whatever)
4) I take a new word file, suspend the laptop, wake it up, and I can still save the new word file. So I guess I can't conclude that it's going to sleep that breaks some link, but it looks to me that the error means that the VM's path is changed on the wakeup so it tries to save somewhere that's an invalid path. Actually, I've seen in a couple of the errors that it complains about saving to H:: (drive letter has an extra colon)
5) Final interesting test -- I close the problematic word file that I've had open for days, reopen it, and now it has no error saving or saving as.

The problem didn't occur with only one file -- it occurred with at least 3 today, all of which have been open for a few days straight (through a few hibernates, etc).

By the way -- I have my entire data repository on the Mac partition, and try to do work with both OS's on the same data. Therefore Windows almost exclusively works on files in a shared folder. It's only the Windows apps, etc that are installed on the VM "hard drive". Is this a problem, generally?

Thanks a lot,

Milos