I've noticed that when I scan certain files, it can take quite
a long time for the scan to finish -- I've seen large exe files take from 4 to 20 minutes.
When the same file is scanned a second time, however, it can take only ONE second to scan the same file.
At first I figured this was due to caching, but even with caching, this just seems like TOO much difference in time.
It appears that ZASS is either 1)
actually "scanning" the file on subsequent scans, or 2) that something was "wrong" the first time it scanned the file, and it should have scanned much, MUCH faster
It "feels" like
it's just reiterating the result from the previous scan.
I can even reboot the system and copy/rename the file, and re-scanning these files STILL only takes a second or two.
Once the file is scanned, NOTHING
make ZASS go back to taking several minutes to scan this file.
What is ZASS doing such that it can scan a file in one second that took several minutes the first time, and how can it do this after a reboot or copying/renaming the file?
Something really doesn't seem right here.
I've noticed this behavior on more than one system (a P4 2.5 and a dual P3 1Gig), so it's not related to the system.