Hi--

Have been using ClamWin for a couple of months on my WinXP machine. For the last three weeks or so, it has been failing to run, terminating the login of the user under which I run it.

Here is my set up:

WinXP Pro Version 2002 Service Pack 3
Pentium 4; 3 GHz, 1 gig ram
I access this machine from my linux box, using Terminal Server Client on the linux end, and RealVNC on the Win side
ClamWin Ver 0.95.3, db version main 52 daily 10603

I had this set to run at 3:30 am, and had these problems, so I changed it to 6:45 pm and it ran a couple days with no problems, then I changed it to run at 12:02 am and it has run a couple days with no problem, then it did not run the next day, the following day it did, and the next night, last night, it did not. The Event Log shows these things (previous entry was 2:04 am the prior day):

12:03:57 Microsoft (R) Windows (R) 5.01. 2600 Service Pack 3 Multiprocessor Free.
12:03:57 The Event log service was started.
12:04:22 The Network Location Awareness (NLA) service was successfully sent a start control.
12:04:22 The Network Location Awareness (NLA) service entered the running state.
12:04:22 The Application Layer Gateway Service service was successfully sent a start control.
12:04:22 The Application Layer Gateway Service service entered the running state.
12:04:55 The Terminal Services service was successfully sent a start control.
12:04:55 The Terminal Services service entered the running state.
13:43:26 The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

I am guessing this 12:04:55 entries are the problem, but I do not know what to do to resolve this.

The user whose login is used for this is the admin user, and has full privileges. The scan being run is a simple Scan C:\.

Any ideas what to try?

Thanks!

:- Doug.

Hi--

Tonight I decided to try activating the scheduler directly on the host winxp machine. It started at the correct time. Then I logged out of WinXP, but left the machine running.

When I went back to my login, 2 minutes later, the scan had aborted!

So this suggests that it could be happening the other way around--that something terminates the login, and the loss of the login then ends the scan.

Any ideas what could be going on?

And is there some way to get clamwin to run in the background without the login being active? A command line scheduler, perhaps?

Thanks!

And while I was writing the above post, I was running another scheduled scan and got booted off again.

It appears this has been solved.

Turns out that the power supply on this computer was going bad, intermittently and it seems especially when there was a load on the machine, such as Clam may have put on it.

We seem to be running OK, now.

Some AVs are starting to limit/throttle CPU used during a scan. I believe Microsoft Security Essentials does this. Using ClamWin and a real-time scanner at the same time can be resource intensive.

Regards,

Thanks, Bob!