Slow deletes and NOD32

Deleting files in Dopus takes a while on my computer. Task Manager indicates that NOD32, my anti-virus program, is chewing up lots of CPU cycles; I guess that's the slow down. I have Dopus set to use Windows delete to Recycle bin, and do not see this behaviour in Windows Explorer. Anyone with NOD32 observe this too, and know if/what options I can tweak to have the delete mimic Windows behaviour which does not trigger the anti-virus scans of the files being deleted? (I am guessing that that is what is happening...)

i have NOD32 set to not scan all files. Go into the setup under AMOD and remove the check mark next to scan all files. See if that fixes things.

I have already done this earlier and it doesn't seem to have made a difference...

On 20/04/2007 10:31 AM, * mackal wrote:

[quote]FatherTime wrote:

[quote]i have NOD32 set to not scan all files. Go into the setup under AMOD and remove the check mark next to scan all files. See if that fixes things.
[/quote]

I have already done this earlier and it doesn't seem to have made a difference...

[/quote]
I use: AMON, Setup, Detection, Files, Scan on:

Uncheck: Open
Uncheck: Execute

Check: Create

If you do occassional manual scans, only created files can become a
problem. No need to scan each file on OPEN and EXECUTE. Try this and
see if it works for you...

--
W.K.(Bill) Oxtoby
boxtoby at sasktel dot net

I was pondering unchecking Open before, but I dare not turn off Execute... way too precious a safeguard. The disadvantage of a slower Dopus operation pales in comparison to the potential risk of running without the Execute-time checking for viruses...

Still, the thing that bothers me most is that deleting under Windows Explorer does not trigger this behaviour... I wonder what Dopus does differently...

I've got NOD32 set to scan all files on open, execute and create. Deleting to the recycle bin in Opus doesn't seem slow.

I don't know why there would be a difference between Opus and Explorer for recycle bin deletes. Opus calls the same API that Explorer does.

Is the slowness during the actual delete, or during file counting before the delete happens? Did you try restoring and then re-deleting exactly the same files in Explorer, and then doing it one more time in Opus (to account for caching of the disk data, or anti-virus scans)?

I haven't done the test, but excellent idea, that indeed is the sanest thing to do at this point.

[doing test...]

:blush:

Explorer takes just as long. It turns out this was a coincidence, in a way. The day I try out Dopus I decide to clean out my downloads directory; it contains much shareware that I was evaluating, most of which consists of packed executables, which NOD32 takes a while to scan (it unpacks them first before doing an actual scan for virus signatures). That explains the particularly slow deletes...

It's still Dopus' fault... it's so damned nice that I couldn't help myself when I got the HDD house-cleaning urge... :wink:

Now that I think about it, there were previous occasions where Explorer was this slow too (more packed executables being deleted), but I am so... dissatisfied with Explorer, and Windows in general, that these warts fly right under my radar, and are automatically chalked up to "there goes Windows again...". A great piece of software like Dopus I obviously hold up to a much greater standard... :smiley:

So all in all, there isn't much for me to do or tweak. The problem, if it can be claimed that there is one, is that ideally NOD32 should not scan files which are being placed into the Recycling bin, as there is little point (no extra security added as far as I can see).

On 20/04/2007 4:23 PM, * mackal wrote:

[quote]I haven't done the test, but excellent idea, that indeed is the
sanest thing to do at this point.

[doing test...]

[Embarassed]

Explorer takes just as long. It turns out this was a coincidence, in
[/quote]
--- snip --- snip ---

[quote]So all in all, there isn't much for me to do or tweak. The problem,
if it can be claimed that there is one, is that ideally NOD32 should
not scan files which are being placed into the Recycling bin, as
there is little point (no extra security added as far as I can see).
[/quote]
--- snip --- snip ---

I thought about this some more and you are correct that "NOD32 should
not scan files which are being placed into the Recycling bin..."
Although NOD32 scans as fast or faster than completing products, there
is no need to scan a file that has already been scanned, unless the file
has changed or the virus signature database has been updated. NOD32
would not normally rescan the files being deleted, if you have the
following setting:

AMON, Setup, Options:

Last Item: Check Optimize scanning

Also pressing the Help button there explains this setting. You may
already have this checked, but it wouldn't hurt to be double sure of
this. It could cause the described behavior. Hope this helps...

--
W.K.(Bill) Oxtoby
boxtoby at sasktel dot net