How to stop Nod32 from scanning..?

Hi.
Sometimes I download very big compressed files (hundreds of MB, even GB) with a lot of small files inside them.
Problem is that, when is about to finish, Nod32 starts to scan the file (very slow). One time I waited over an hour (2.5 GB file)...
And if it happens that 2 or more downloads "meet" at "finish" line it's worst. My HDD is "suffocated". One time it was so worst that I pressed Reset button
One solution is to deactivate scan before downloading the file(s). But it's not wise and sometimes I forget (even to reactivate it )...
Other solution is to deactivate the scan of compressed files completely. Also not wise...

So, is there a way to stop the scan - once started...?
Thank you.

Best regards, Cosmin3

 

see what Marek recommended here, whole topic is here

 

It's not the perfect solution, but it's better than nothing.
Thank you.

A funny thing: yesterday I deactivated "antivirus and spyware protection" and I forgot to reactivate it.
Meanwhile I used Driverpack Base to integrate MassStorage drivers into my Windows XP installation files.
Last time I did that it took over 15 minutes.
This time it took almost a minute
I thought it was an error, I wrote on their forum...
But later I realized that it was from Eset Nod32

More than 1500% time difference

 

If there's a problem with slow scanning certain files, please provide me a link to them so that I can check if it can be speeded up somehow.

 

Ok...
The files are packed into "DriverPack Mass Storage 10.09 for Windows 2000/XP/2003 (x86)" from http://dpsdownloads.drupalcdn.netdna-cdn.com/xp/x86/DP_MassStorage_wnt5_x86-32_1009.7z

The program DriverPacks BASE from http://dpsdownloads.drupalcdn.netdna-cdn.com/applications/driverpacks-base/DPs_BASE_1006.exe inserts them into the Windows XP installation files (I think it copies them into i386 folder and adds them to txtsetup.sif and/or dosnet.inf).

If you need more info I'll try asking the guys who made it...

 

So, any news...?

 

Below are scan times (in sec.) of files in the archives mentioned above. The other files were scanned in less than 100 ms. There are no excessive times as you can see:

DP_MassStorage_wnt5_x86-32_1009.7z
D\M\Q3\ql2300.sys 0.156
D\M\I4\IaStor.sys 0.141
D\M\PC\FTTXR5_O.INF 0.125
D\M\I4\IaStor4.sys 0.11
D\M\L6\megasr2k.sys 0.11
D\M\S9\SI3124R.cat 0.11

DPs_BASE_1006.exe
bin\DPsFnshr.7z 1.829
DPs_BASE.exe 1.016
bin\md5deep.exe 0.734
bin\wnt5_x86-32\ROE.exe 0.437
bin\un7zip.exe 0.329
bin\7z.exe 0.297
bin\7-zip32.dll 0.281
bin\wnt5_x86-32\DP_Install_Tool.7z 0.187
bin\makecab.exe 0.14
bin\uni2ansi.exe 0.14
bin\wnt5_x86-32\KB888111.7z 0.125

 

Ok, but why that program is slowing down so much..?
Is it an incompatibility between the program and Nod32 or is it program's fault..?

 

If you have a large archive scanned, each of the files in the archive is extracted and scanned. As a result, scanning of such an archive may take minutes or even hours, depending on the number of files inside as well as the type and characteristics of the files.

 

I scanned DP_MassStorage_wnt5_x86-32_1009.7z and it took a few seconds.
Anyway when the program stats slipstreaming the drivers the entire archive is decompressed in a working folder and from there the files are processed.

 

I tested with other antiviruses: the time interval is different on each one but on everyone is less than 2 minutes.
So apparently is Nod32's fault.

 

Remember that the scan is not made in some files due to optimization processes.
This happens if those files were scanned before, under certain conditions.

 

Look, I'm not an expert in how antiviruses work, I'm just an average user.
I only saw that with other antiviruses works fine, with Eset Nod32 it doesn't.

 

I have noticed the same slowness in scanning with game files downloaded from GOG.com. The files are in an .exe format, so who know how they are packed in there. A normal scan will take around 23 minutes for my entire system, if one of these files is included, it will add approximately 2 hours. It is interesting because on download, the real time scanner takes no time at all, it is only on manual (in-depth) scans that the additional time is added. My solution was to isolate these files in a directory, scan them once for the security, then uncheck that directory from my manual scan.