xp MS antispyware error log 1.2g

[dave]

I had a serious increase in disk use. Removed everything
I could including antispyware. Finally found the errors
log and it was 1.2 gig. I checked my other computer and it
was 24meg. I erased both and everything is fine at this
time. On my Win2000 I checked and the error file was only
4k.
Even with this strange bug on the XP's this is still the
best program around.

 

[dave]

Just checked two more Win 2000 computers with Antispyware.
One had a 1kb errors log file and the other had a 4kb
file. It appears the large error file is only on xp.
Errors are strange. Most errors are similar to this one
"7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::2/1/2005 9:50:15
AM:1.0.501"

 

[Guest]

-----Original Message-----
I had a serious increase in disk use. Removed everything
I could including antispyware. Finally found the errors
log and it was 1.2 gig. I checked my other computer and it
was 24meg. I erased both and everything is fine at this
time. On my Win2000 I checked and the error file was only
4k.
Even with this strange bug on the XP's this is still the
best program around.

.

 

[Bill Sanderson]

In contrast, I've only seen this on a Windows 2000 server--so experiences
vary.

If you don't feel like watching the file carefully, I'd uninstall for now.
I have seen this file go normally for weeks, and then suddenly take off
again--if there's a risk, I'd avoid it.

 

[jerrymarks]

I have found significant size errors.log file on my
Windows 2000 system. Each time I delete the file and then
it reappears again. I found it the first time when I
looked at my defrag log and found the largest fragmented
file that could not be fixed was this one. I just ran
defrag again and again, this file, and again I deleted
it. Microsoft needs to explain this and do something
about this. This is my only complaint about this program
thus far.

 

[Bill Sanderson]

The simple explanation is that it is a bug, it is not fixed in the builds
distributed thus far.

I would recommend not running this beta product on a server that has seen
this symptom at some time. It is likely to recur, in my own experience.