I ran the old version (can't tell you which one now) it asked me to upgrade, I did. When the installer ran it detected the old one running and asked me if I wanted it stopped, I did. seconds later a BSOD flashed then the system rebooted. Now that's all that happens. The system boots starts, loads my desktop, then BSOD and reboot. The BSOD flashes too fast to read. THE C DRIVE ALWAYS HAS A BAD FILE CALLED WIASvd.log or something close.

Any suggestions?

Scott

it doesn't sound right, are you sure it was clamwin that asked you if you want to stop the infected program? I am sking because clamwin does not prompt before stopping the program
In any case you could try to restore XP install using the installation cd.

There was a problem reported around March 20th. A similar problem happened during scanning. It happened to a few people--including moi. The result was a permanent BSOD. I didn't have access to the Web for info, so I had to restore my entire Win XP system--right in the middle of income tax season!

Check out the posts about this. The first post was from wtfia, and it was headed "Trojan.Agent-2322 in winlogon.exe - false positive." It appears that the database contained something that treated winlogon.exe as a virus. See if you can restore that file. On my machine, it is located both in Windows/system32 and in the i386 directories.

Regards,

I wasn't scanning anything. There was no virus detected. I got a notice from clamwin that I needed to update my virus database (I hadn't booted into windows in a while) but when I brought up the control panel it said that a new version of clamwin was available would I like to download it. I downloaded it. I closed the control panel and I double clicked on the installer. The installer said "I see you are already running blah blah version of clamwin, should I close it?. I said yes. A BSOD then occurred and has occurred ever since.

Now any ideas?

If you were unable to use the suggestions posted in the March 20th post, the only thing I can suggest is to boot in Safe Mode and see if you can repair Windows. Failing that, try to re-install Windows from your original media.

I was unable to repair my OS, but Dell had a Norton Ghost snapshot of the original installation accessable from Safe Mode (via F11, I believe it was). I was thus able to start all over again and had everything back by the end of the day, thanks to backed up data files and new program CD files. I've now got a snapshot program accessable via F7 before Windows boots--if it ever happens again.

Good luck.

Regards,

This does not bode well for the usability of this program. I can not find the post to which you refer. I've never had a virus do as much damage to my system as this program has, can you feel the irony here? And I was simply trying to upgrade it. Apple does not provide such a backup(running boot camp not an emulator), however I do have a backup that I can restore and merely be put back several months. I thank god that I ran this on a secondary laptop rather than my production system (well it isn't quite version 1.0 after all). Seems that both the support and the code have a ways to go yet. I'd fix the support, and then the code. I'm not angry, but I would be if I'd paid for this software.

Thanks very much for all your work so far, I'll look in again later.
Scott

The referenced posts are at: https://forums.clamwin.com/viewtopic.php?t=993. Maybe that will help.

It appears that the problem was the signature database, which for some reason recognized an important Windows file as having a virus. Naturally, most users either have preferences set to delete the virus/file or quarantine it.

Both the database and the engine for ClamAV are handled by ClamAntivirus, which is primarily run on Linux email servers. ClamWin puts a GUI on the ClamAV engine. Clam/ClamWin is usually pretty stable, but they are still in beta programs.

Stuff like this happens. Seems like Norton recognized Google as bad last year. I'm just another average user, and I have about one system crash per year and have to restore things.

Regards,

You could boot your system up using a windows-PE bootdisk or a linux bootdisk or "Recovery Console" on the XP installation disk.
Then you would need to make a backup of all the files in "c:\windows\system32\config", and then overwrite the files using system-restore files which will be found in "c:\System Volume Information\_restore*****...\RP**\snapshot\" or failing that, use the 'repair' registry found in "c:\windows\repair"
Alternatively, ClamWin may (I've never used it ) install drivers into "c:\windows\system32\drivers" and deleting them may stop your BSOD (make backups)

You could also try a windows repair.

OffTopic: Does ClamWin use any device-drivers to accomplish it's tasks, or is it all ring-3?