-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry
Sent: Wednesday, 22 January 2003 6:10 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.Virus] log expansion
>Yep. I changed the name of the old one and dropped the new one right in its
>place. I'm going t
Yep. I changed the name of the old one and dropped the new one right in its
place. I'm going to get a fresh copy of 3.12D and repeat the install, and do
some more Eicar testing and get this right.
If you want, you can use the debug mode ("LOGLEVEL DEBUG") until at least
one E-mail is scanned,
EMAIL PROTECTED]]On Behalf Of R. Scott Perry
Sent: Wednesday, 22 January 2003 5:11 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.Virus] log expansion
>I loaded 1.66 and the copy of fpcmd.exe from out of fp-win_312d_m.exe on
>Monday morning. Since then my log files have grown dramatically, mostl
I loaded 1.66 and the copy of fpcmd.exe from out of fp-win_312d_m.exe on
Monday morning. Since then my log files have grown dramatically, mostly from
the inclusion of countless lines like these:
01/20/2003 12:55:00 Q37e6146 Could not find parse string Infection in
report.txt
01/20/2003 12:55:01
I loaded 1.66 and the copy of fpcmd.exe from out of fp-win_312d_m.exe on
Monday morning. Since then my log files have grown dramatically, mostly from
the inclusion of countless lines like these:
01/20/2003 12:55:00 Q37e6146 Could not find parse string Infection in
report.txt
01/20/2003 12:55:01 Q3
