I'm using Avast 4.1 home edition, build 4.1.342 VPS file 0402-1 on Win9x dialup old Pentium
w/ 98Mb ram
1) I'm comparing Avast to Mcafee Virus scan. Scanning my c drive with Mcafee it scans 23,132 files (rate = 453.57/min) & comparing to Avast most thorough scan + archive scanned 19242 files (rate = 545.1/min).
my issue is with the difference in total files scanned (3890 files less with Avast ). What would account for
this difference? Can I adjust anything which will get me closer to total files scan by Mcafee?
I found the missing files, they were starring me in the face in the exception report (files not scanned)
Two corrupted java lib files which Mcafee "says it can scan", but which can't be scanned by Avast
accounted for the huge difference.
I actually like the result given by Avast 'cause it points you to an issue (possible corrupt file which may need to be addressed).
3) I'm still contemplating whether resident protection is better/worse than what Mcafee offers which is download scan - if virus/trojan is sniffed while on the net, it is caught on the fly before it gets to your hard drive.
Seems like with resident, if I understand correctly, nothing is scannned till it has reached your hard drive.
just like to know if the above is correct interpretation of how resident works. if not what please explain
My conclusion is it probably doesn't matter. I prefer the way Mcafee seemingly intercepts before it hits your hard drive, but also impressed with the way Avast handles.
demo: go to eicar.org and select the first eicar.com demo you will see Avast jump into action and pick this off seemingly before it hits your hard drive it's so fast, but actually it is picked off in cache and then you get to cancel the save download. No trace of the eicar.com file if you Avast delete (permenant), and cancel the save download.
http://www.eicar.org/anti_virus_test_file.htm5) thorough scan reports show about 6 files skipped for 1 reason or another (corrupted or password protected was the reason given. example:
\spybot - search & destroy 1.1 \spybot - search & destroy\recovery\alexarelated.zip\related.htm result: unable to scan archive is password protected
the above file related.htm was taken out by Spybot and backed up by Spybot
question why is this difficult for Avast to scan?
Mcafee does not have a problem scanning.
Not true that Mcafee does not have a problem scanning password protected archive. It may say it has scanned, but not sure how effective it is. As proof of this I copied the eicar string into a notepad text file and then saved it in an archive password protected zip file. I created a second zip archive using the same method but left this archive without a password.
Next I tested Mcafee:
Result Mcafee is able to id the eicar.com in the archive without the password, but could not when I scanned the password protected archive zip.
Bottom line is I like the honesty presented by Avast on this. Upfront id'd files it could not scan. Ideally user would further investigate the exception report and take appropriate action.
sorry for being so long winded, but thought I would bring these questions full circle based on my own experience in case someone has similar issues and searches forum archives.