conflicts with mcafee virus software

[e]

I am running Win 2000 Pro with Office XP Pro and McAfee
VirusScan v4.5.1. Does anyone know of any conflicts
between Word and McAfee? For the past several months Word
has been freezing up while using it for no apparent
reason. We started removing other applications to try and
determine if there may be a conflict. Ever since we
disabled mcshield.exe, we haven't had anymore problems.
Any thoughts on this?

 

[Rob Newson]

I'm new to this so I don't know if this helps but,
I'm having a problem at work that started happening when our Systems people
installed McAfee on our machines.
Suddenly, and intermittently, the machines could not find a template located
in a subdirectory of the WorkGroup Templates directory. A "5121 Error -
Cannot open Doc.." error occurred (the template was being opened from a VBA
macro).
The macro has been working for years (Word97 on an NT network). I seemed to
have solved it by killing the AV process.
However, this was done yesterday, so who knows ie maybe it'll pop up on
Monday, as I said, I'm no expert!.

At the end of the day I'd say there may be a conflict.

Regards;
Rob

 

[TF]

Rob

Yep. Norton is a heap of garbage. But now that is off my chest... which
version of Norton have they installed. If it is just NAV (i.e. not Corporate
version), then just open NAV and disable the Office Plug-in.

Best advice is to tell your Systems People that if it isn't too late, return
Norton and get something that works properly such as Network Associates
Active Virus Defence.

--
Terry Farrell - Word MVP
http://www.mvps.org/word/

I'm new to this so I don't know if this helps but,
I'm having a problem at work that started happening when our Systems people
installed McAfee on our machines.
Suddenly, and intermittently, the machines could not find a template located
in a subdirectory of the WorkGroup Templates directory. A "5121 Error -
Cannot open Doc.." error occurred (the template was being opened from a VBA
macro).
The macro has been working for years (Word97 on an NT network). I seemed to
have solved it by killing the AV process.
However, this was done yesterday, so who knows ie maybe it'll pop up on
Monday, as I said, I'm no expert!.

At the end of the day I'd say there may be a conflict.

Regards;
Rob