[hodj]

Hi!

Just installed NOD32 v4.
For me it seems like NOD32 has changed it's behaviour a bit.

When completing a download the download is first locked and checked for viruses before the download programm is allowed to do something with it.


This means for jdownloader:

"file.rar.part" is downloaded and NOD32 checks for a virus.

Meanwhile jdownloader tries to rename "file.rar.part" to "file.rar"... but NOD32 tells JD to wait... and wait... and wait... as NOD32 still hasn't finished it's virus check.

Then after 100seconds JD says: timeout!
...and the download is marked aborted.


One solution would be to rise JD's timeout time.
But max is 120.000ms.



Anyone a solution at hand?

[Jiaz]

no this timeout has nothing to do with the problem you describe!
pls setup nod correct (disabling the webscanner, cause its bad like hell):
you need to add java.exe and javaw.exe to the exclude list (not to scan list)

[hodj]

Put them in the exclusion filter (though I wasn't very fond of the idea letting every java program do what it wants) ... yet... still the same.

ETA:00:00 .... pause... pause... pause...
meanwhile: ekrn.exe @ ~95% CPU usage
and after 2 minutes: timeout with [aborted] ... or ... [abgebrochen] (in german)

[Jiaz]

what process is ekrn.exe @ ~95% CPU usage ?
did you try to deactivate the check function for password protected archives?
or maybe you can disable to check archives over xy MB (dont worry, when you extract the archive, the files in it it will get scanned normally)

[hodj]

ekrn.exe is Nod32's kernel service.
It starts eating cpu power as soon as it starts scanning for viruses.
Archives don't need to be password protected to make Nod32 take control over them until it has finished scanning.
I will follow your last advise then.... I dont come up to something else.

Just hoped someone knew a magical switch to make Nod32 scan AFTER JD or other Download Managers are completely finished with a file ... not when the download has finished. Nod32 2.7 behaved like this.

If JD would allow to set a higher timeout than 2min this would help also.
(maybe via config file?)

I don't know, but maybe if JD dev team could make JDownloader allocate disk space for files that is downloading. Right now JD make one *.part file and it keep raising its size until everything is downloaded. At the other hand, most downloaders (flashget for instance), allocate file size in the very begining of downloading, and I never had problems with that while (and still) using NOD32. But with JD I have the same issues that you described.