On 9/8/05 14:44, "Meg Faddick" <email@hidden> wrote:
> I also tried changing the autosave and document location settings in Word (as
> a couple other people mentioned doing) and that didn't work either. The old
> delete Registration Cache fix for previous versions didn't work.
>
> Right now, I have a world-write folder available on the image and users have
> to save to that, then drag their files back to their home documents when done.
> Painful and ugly.
>
> I'd love to know exactly what was changed...
What happened is that Apple changed some small, but significant things in
how home directories mount, and it freaked Word out. This is due to the way
Word saves, which needs to be fixed, but isn't something that is easily
fixed, nor even attempted until they have to, which is now happening.
Some things...
1) in Word's preferences, change the location of the autorecover files to a
spot on the local drive.
2) If you're using network homes, try changing the location of your Normal
template from ~/documents/Microsoft User Data to a different (non-Network)
location using Word>Preferences
(i.e. Go to Word>Preferences>File Locations>User Templates and change it to
somewhere else. Of course, this means that every user on that physical
machine has to have a somewhere else, so they aren't overwriting normal.dot
files all the time. Obviously, this is only a good solution for machines
with a small, predictable number of users.)
Then Quit Word, move the "real" Normal Template from the home directory to
the new folder and re-launch.
>From one of the Word MVPs, (he's one with Word, so I tend to take anything
he says seriously, even if I don't like it. He's also a really pissed - off
aussie who would really like to move to 10.4, but can't because of this.
He's not being really nice in his complaints about this. I know, I see them)
" Check that your user home folder is not on the same server as a mounted
server.
If it is, when Word plays up, unmount your home folder. Word will then
complete the save.
It appears that in OS 10.4.2, the server locks a file in the user's home
folder TWICE, once along the home folder path, and again along the mounted
path. When Word tries to Save, the server rejects the write operation
because it reports that the file is locked for edit along the other path.
This will not apply to all users, and is more prevalent if the server is
mounted by SMB or AFP"
This is partially due to, in Mac OS X 10.4, esp. 10.4.2 Apple making some
changes to Carbon that borked file locking via API methods, and now expects
everyone to use .lck files. Word gets hit with this worse, because of it's
infamous "MAKE A LOT OF TEMP FILES" behavior.
Apple and MS are working on fixes while they busily blame each other. Both
have huge code bases, so fixes don't come easily.
However, for what it's worth, this bug has whatever the MacBU's highest
priority happens to be. They really do know about it, (yes, I do personally
know they know about it, I've told them enough about it.) The only thing I
personally can think of is to try using portable home directories (aka
synch'd mobile homes) and seeing if that helps, since at that point, you're
saving locally, then synchronizing later on.
john
--
John C. Welch Writer/Analyst
Bynkii.com Mac and other opinions
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Client-management mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/client-management/email@hidden
This email sent to email@hidden
