Firstly, thanks for a great piece of software, the world would be better if all software worked as well as avast.
I’m using emule client to download large .rar files that have thousands of small files packed in them (say 2 GB file with 20000 small .rars inside). When the file completes, stardard shield scans the newly created file. Normally there’s no problem, but when such big .rar file is completed, avast hogs all CPU resources, hangs the Windows Desktop to complete the new .rar file scan with thousands of small files inside. Emule client reports “completing” for file status as avast is scanning away, sometimes rendering computer unusable for 2 hours. It seems that the Windows Desktop hangs due to the ashserv.exe being set to High Priority.
I’m using avast! 4.6 Home Edition, Windows 2000 SP4 and the emuleplus latest client.
The resolve would be to lower priority of ashserv.exe or change routine for big archive file scan. If something can be done immediately to resolve this, please inform me. The only workaround I’ve found is to temporarily switch off standard shield for file completion to finish without avast scanning it, but that’s obviously not a good solution.
Normally there is not to scan large file size like 1 gb…it ofcourse slows down…that normal with avast…Did it scan automacially,I mean is did u enable P2P shield in avast…?If so just pause it and unzip .rar files manually…and scan the 20000 .rar within the folder…it takes time…so better leave the comp along when u have ur dinner or lunch…or when u sleep?I guess there is no other choice to scan manully…better to scan manuallly…and pause the standard sheild…for time been and scan it manually…wait for more post…it that time. ???
Thanks for your advice. This is actually what I’ve been doing to these .rar big files all along - scanning them manually. With manual scan there are no problems, the desktop doesn’t hang. Problems come only when standard shield is running and such a big file completes in emule. Since I don’t want to leave my computer unprotected all the time, I’d rather have the Standard shield running. But sometimes I forget that a huge .rar is coming, and when it comes, then when the problems start, and the comp hangs.
Ther’es an option to exclude files from being scanned in avast, I thought to use that for emule. Question: if my files come to emule to directory g:\emule, should I write in avast g:\emule, or g:\emule*., or g:\emule, or g:\emule*.\ ?
If you read new virus technologies you’ll see that this is not enough anymore. The virus code could be run even before the file is saved and, after, scanned. Against these malwares there is the WebShield technology: Web Shield is a new provider. It is a proxy that filters the communication of a web browser, looking for viruses. It also makes it possible to block certain files by URL or MIME type. HTTP Scanner should deal with all network traffic such as spywares, adwares, toolbars, BHOs, hijackers and other malicious scripts. It will work as a real time network-based antivirus firewall, it will filter HTTP (web) traffic before it reaches the browser.
I think you took my words out of context. Surely, it is possible to run malicious code for the web browser, but my main concern were big .rar archives arriving in emule. I’m pretty certain that there’s no way for a virus to attach itself to the header of a .rar archive so that it is executed by the system before the .rar is saved onto disk. And so the only place the virus could exist in a .rar file is inside the archive, attached to one of the archived files. And that could certainly be checked for after file’s arrival, couldn’t it?
But thanks anyway!