ClamWin seems to be leaving a number of temp files behind when it does it's up date. The files are located in Documents and settings\Administrator\Local Settings\temp. All the files end in clamtmp. The problem is that Immunet picks up these files as a Trojan. Is there a way to change the location of the temp files? Why doesn't clamwin clean up these files? I'm currently using version 0.96.2.1 on Windows XP Pro.

You may be able to change the location of the temp directory via ClamWin's advanced tab-command line paramaters, but I think the easiest thing to do would be to exclude that temp directory from Immunet scans. You might also upgrade to the latest version of ClamWin, version .97.

My question is why are you running ClamWin with Immunet? They are both based on Clam AV, so you have some duplication there. Immunet is a real-time scanner, unlike ClamWin, and it has more protection.

Regards,

thanks for your reply. It was my understanding that Immunet acts as a companion virus scanner to any current viruscan you may have installed. Immnunet free version did not strike me as a stand alone virus scanner. I thought about excluding the temp directory but I didn't want to exclude the whole directory because viruses do still populate the temp directory and I wanted to make sure that it was still being monitored. Just to be clear the clamtmp files are temp files from Clamwin?

Yes, Immunet bills their AV as a "companion antivirus." I'm sure it works well with most AVs, so you are okay in using it with ClamWin. It's just that there will be some duplication of code/signatures, but since ClamWin is not a real-time scannner, that's all right.

The clamtmp files are most likely ClamWin temp files created during scanning. If they were Immunet files, it would not pick them up. I would not change their directory in ClamWin. Other AVs sometimes occasionally pick up clamtmp files as infected. See if you can exclude *.clamtmp from Immunet's scans. If it doesn't "mop up" these files during a scan, ClamWin is supposed to delete them at the next restart of the computer. This didn't work too well in some older versions, so I deleted them manually for awhile, but I haven't heard of any problems lately.

Regards,