Re: [Declude.Virus] 4.2.20 Error in Log

2006-07-13 Thread Darrell \([EMAIL PROTECTED])
Andy, Besides AVG I have 3 scanners: listed in order (F-Prot, Clam AV, McAfee). I do think its an AVG issue like you suggested. I am trying to find a way to disable the built in AVG virus scanner to see if this message goes away. Darrell Andy Schmidt writes: Do you have a

RE: [Declude.Virus] 4.2.20 Error in Log

2006-07-13 Thread Andy Schmidt
There is a parameter in the Virus.cfg to disable the internal scanner. I don't have it in front of me, but it was in the comments just below the external virus sample. Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Message- From:

RE: [Declude.Virus] 4.2.20 Error in Log

2006-07-13 Thread David Barker
BUILTINSCANNEROFF Located in Virus.cfg. Will disable the internal AVG scanner. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell ([EMAIL PROTECTED]) Sent: Thursday, July 13, 2006 8:34 AM To: declude.virus@declude.com

RE: [Declude.Virus] 4.2.20 Error in Log

2006-07-13 Thread Chris Asaro
To turn off the internal scanner BUILTINSCANNEROFF Located in Virus.cfg. Will disable the internal AVG scanner. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt Sent: Thursday, July 13, 2006 8:58 AM To: declude.virus@declude.com

RE: [Declude.Virus] 4.2.20 Error in Log

2006-07-13 Thread Chris Asaro
Your pretty quick for a pinata Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Asaro Sent: Thursday, July 13, 2006 9:10 AM To: declude.virus@declude.com Subject: RE: [Declude.Virus] 4.2.20 Error in Log To turn off the internal scanner

Re: [Declude.Virus] 4.2.20 Missing File Error in Log

2006-07-13 Thread Darrell \([EMAIL PROTECTED])
After testing with AVG off it appears that the error about the missing file only occurs when AVG is on. With AVG disabled I get no error messages. Here is the relevant log info. I have confirmed this is an AVG issue. With AVG on I get the error with AVG off I do not get the error.