Hello...

I'm running 0.88.2.3 on Microsoft Windows Server 2003 Enterprise Edition,

and since the update to 0.88.2.3, I've had to disable scheduled scans because clamscan.exe uses up all of my cpu.

Process Explorer v9.25 shows that clamscan.exe goes up to 99%.

This is not a problem in and of itself as long as clamscan.exe lets me do other things when needed,

and indeed it does not affect running tasks very much. However starting new tasks, like starting any kind of program, explorer window etc,

takes a considerable time when clamscan.exe is running scheduled.

Strangely this is not happening when I run it manually: the cpu still goes through the roof but it lets me start new tasks and windows without the delay that appears when running sheduled ...

The log shows nothing strange at all, it just states

--------------------------------------
Scan started: Fri Jun 02 02:00:00 2006


Any suggestions appreciated.

Thanks,

check that advaced setting shows LOW priority

Yes it does show "low", sorry I forgot to mention that, it's obviously relevant to this...

I've also confirmed in Process Explorer v9.25 that the process Priority is 4 = Idle.

Thanks,

well a process with low priority will use 99% cpu when no other process need it.
I noticed that the windows xp scheduler is not so fast to reschedule a process,
I was using folding @home client in idle priority but it was slowing a lot the system.
This may be less significative when the cpu is enough fast, my pc is a tb @ 1.2ghz