Since I recently reported an ashquick problem I thought I would try to reproduce this one too.
I set ashquick to scan a 2GB zip file on a network drive. After it was running for some time I shut down the system which hosts the file.
At first the results were similar, the ashquick progress window stopped updating and ashquick.exe went to 99% CPU utilization. I just observed for some minutes to see if any kind of timeout might kick in but none appeared to. I went away leaving the system in that state.
When I returned, some time later, the ashquick statistics report was on the screen reporting a successful scan with the number of files that had been scanned in the zip file (up to the point when the host was shut down) and the ashquick process had terminated. No problem with being unable to complete the scan was reported.
On checking my system logs I find that I was away for about 15 minutes, and that 20 minutes had elapsed since I had shut down the host system of the file being scanned. During that interval it seems some timeout kicked in that caused ashquick to believe it had reached the end of the file.
