I have the latest version (0.87.1). I have setup a schedule to scan my entire C: drive at 5:30PM every weekday. However, the scan never completes. All I see in the "Virus Scan Report" are entries like this:

--------------------------------------
Scan started: Wed Dec 14 18:30:00 2005

--------------------------------------
Scan started: Thu Dec 15 18:30:00 2005

--------------------------------------
Scan started: Fri Dec 16 18:30:00 2005

--------------------------------------
Scan started: Mon Dec 19 18:30:01 2005

Is this normal? I'm expecting to see a "--summary--" section at the end as when I manually run clamscan.exe from the command line.

I have already tried the cygwin1.dll suggestion. I found one copy and overwrote it with the one from ClamWin\bin. However, I doubt that ever was a related issue as I had this problem before that other copy of cygwin1.dll got installed onto my machine.

Lastly, I'm writing a program that shells out to clamscan.exe to scan a specified folder. It's working great, unless there are a lot of files (over 100). In this case, clamscan.exe just keeps running and never returns (by "never" I mean I give up after about 10 minutes and do an End Task). I'm wondering if this issue is related to the above problem with scheduled scans.

Anyone encounter anything similar? Any suggestions?

Thanks.

David Prothero
TherapeuticResearch.net

can you try and leave the scheduled scan running longer then 10 minutes, say overnight? 10 minutes may not be enough for 100 or over files, depending on the filesize and whether or not files need unpacking.

I do leave it running longer than 10 minutes. I'm not even at my computer when the scheduled scan is running.

The waiting 10 minutes before doing an End Task was in regards to the custom program I'm writing that shells out to clamscan.exe and the issue I'm having with that (which may or may not be related to the scheduled scan completing).

Thanks.

David

More info. I noticed a clamscan.exe.stackdump file in the bin directory. Here are the contents... it was timestamped at 6:40PM, so the scan had been running for about an hour and 10 minutes before it crashed:

Exception: STATUS_ACCESS_VIOLATION at eip=610C4914
eax=61258F68 ebx=000000AE ecx=00000005 edx=00000000 esi=61159D48 edi=61259000
ebp=0022C638 esp=0022C62C program=C:\Program Files\ClamWin\bin\clamscan.exe, pid 1480, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022C638 610C4914 (61258F68, 61159CB0, 000000AE, 611582F8)
0022C668 6105C03F (611582F8, 611574B8, 000001A0, 00000000)
0022C688 610E10E7 (611582F8, 611574B8, 0022C6C8, 00000000)
0022C6B8 61011CFB (61154A78, 611574B8, 00000000, 00000000)
0022C6F8 61011E38 (61154A78, 0000000F, 00000010, 7C9106AB)
0022C738 6108E3FD (0000000F, 00000000, 00000000, 00000000)
0022D818 610844FF (10840E80, 00000000, 00000000, 00310044)
0022DC68 0040EF9D (0044AE5C, 10032C68, 100AFED8, 00000069)
0022DE88 0040CC72 (0000000F, 0022DEE8, 0044AE5C, 10032C68)
0022DEB8 0040F360 (0000000F, 0022DEE8, 0044AE5C, 10032C68)
0022DEF8 0040431F (10840DC8, 10032C68, 100AFED8, 00000069)
0022DF38 00405DC8 (10840DC8, 10032C68, 00000000, 100301B8)
0022DFE8 00406E7F (10840B68, 10032C68, 00000000, 100301B8)
0022E098 00406E42 (10840918, 10032C68, 00000000, 100301B8)
0022E148 00406E42 (108406D8, 10032C68, 00000000, 100301B8)
0022E1F8 00406E42 (1083E210, 10032C68, 00000000, 100301B8)
End of stack trace (more stack frames may be present)