Hi Terry:
Known bug that was supposed to have been fixed in 10 but there seems to be a
reversion in 10.1.
The Microsoft coder looking after Word says " Yeah, this is a known issue
that Symantec are aware of. This was purportedly fixed in NAV 10.0, but has
reportedly begun to occur again with updates.
I have yet to be successful reproing this in house, but one thing that I do
know is that they may not need to turn off NAV completely, just the
auto-protect feature."
One of the other Beta List participants says:
" It's a bug on Symantec's part. Basically, you can't autoprotect any
directory that any Carbon application writes to. According to Symantec, it's
because Carbon applications aren't "native", but just old, munged OS 9 code.
The real reason is that they assume that all applications delete ala Cocoa,
which is really just an unlink, instead of the way Carbon applications do
it, which is a true delete."
Hope this helps
> Hi all,
>
[quoted text clipped - 17 lines]
>
> Regards, Terry

Signature
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <john@mcghie.name>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410