jeffw_00
September 29th, 2007, 12:56 PM
I really like NOD32, except for one thing.
Once in a while, for work-purposes, I drop a really big data file (100 - 300MB) on my machine. As soon as NOD32 sees the file it grabs it, and really locks up my 3GHZ p-IV (dual-thread) machine until it's done checking it. There doesn't seem to be any to stop it, even by killing the NOD process (it's the "SYSTEM" process that soaks up all the CPU cycles). I hate to exclude extensions because that's a vulnerability. But I wish there was a "that file is ok" button I could press (or NOD could work more in the background).
It's the type of thing where I think the developers tested on much smaller files and never realized the consequences of a really big file
/j
Once in a while, for work-purposes, I drop a really big data file (100 - 300MB) on my machine. As soon as NOD32 sees the file it grabs it, and really locks up my 3GHZ p-IV (dual-thread) machine until it's done checking it. There doesn't seem to be any to stop it, even by killing the NOD process (it's the "SYSTEM" process that soaks up all the CPU cycles). I hate to exclude extensions because that's a vulnerability. But I wish there was a "that file is ok" button I could press (or NOD could work more in the background).
It's the type of thing where I think the developers tested on much smaller files and never realized the consequences of a really big file
/j