NOD32 WINS VB100 #20 !!!

01 November 2002

NOD32 has won its 20th Virus Bulletin VB100% Award with yet another "clean sweep" of every virus in every category ... maintaining its unbeatable record as the only antivirus program in the world which has not missed a single "in the wild" virus since its first test by Virus Bulletin in May 1998 and further reinforcing its envied position as the world's #1 virus detector!

 

BUT OF COURSE IT DOES!!!! .... AFTER ALL IT IS NOD



Cheers

 

Congrats to the team, a truly great product.

 

The creators of BOClean don't seem to think so. See the "Help with BOClean" thread in the grc.security.software newsgroup. It seems that NOD32 causes alot of problems with BOClean. They recommend using one of the "better AV's out there."

 

Running BOClean 4.10 build 004 with Nod32 here.
Not a single prob.

Cheers,

 

Same here!

 

20 VB Awards wiith only 3 failures, and the failures had to do with false positives, I presume! NEVER missed a single virus in the wild!!! That really is a feat! Another smart, proud NOD32 user here!!!!!

 

I had problems running both. It seems to show up more on WIN98SE systems. Kevin had to personally "tweak" my copy of BOClean in order to get it to work with NOD32. Apparently (according to Kevin) the creators of NOD aren't too interested in working with him to fix the problem. I've also heard horror stories (from many people) about the poor support at ESET...it sounds almost as bad as the non-existent support at Zonelabs. One thing is for certain, BOClean support is incredible. Nobody comes close to the personal support they give to each and every customer. Other companies can learn alot from them.

 

I'm running them on Win 98 SE as well, and, as I said, not a single prob.

With 4.08 and 4.09 I had a problem with Pstores.exe page faults, and Kevin diagnosed those to be due to a conflict with a combination of NAV and TClockEx.

After applying a patch, the problems disappeared.

v 4.09 never conflicted with Nod32, though.

And V 4.10 doesn't require any patch at all in order to get along with anything I have running.

And as for Nod32, I'm extremely happy with it, after having run McAfee and NAV 2000, 2001, and 2002.
And by the looks of it, it will even get better before long.

I'm sorry to hear that your experiences differ, but that's life:

You find me 10 people who think NAV's the greatest thing since sliced bread, and I'll find you another 10 who'll assure you it sucks, and crashes their systems 8 times a day (or vice versa).

The same goes for McAfee, Zonealarm, or anything else.

And apparently some people even think it goes for Nod32 as well...

Cheers,

 

Tony

Whay haven't you tried NAV 2003 yet?

Does anybody have a NOD-4 beta screen shots to share?
I would love to see some

 

I've just read the thread 'Help with BOClean' on grc.security.software and I think people there are getting the wrong impression of NOD32.

To quote - '...My opinion is based on the recently lackluster detection rates as seen in several AV tests..'

Both products are good, I use both without any problems, although no doubt some hardware/software combinations may have issues.

Can I suggest that ESET and BOClean developers talk to one another, so that known workarounds can be shared and passed onto users.

The impression being given on grc seems a little one sided as the moment perhaps someone from ESET can put their side of the argument.

Jan V

 

BOclean developers are suggesting you try "a better AV "? Hmm lets see,THERE IS NOE BETTER AV!. I have a suggestion if you have conflicts with the two programs maybe you can try "a better Trojan detector". Congrats to NOD32 on its 20th win. Dumped Norton AV, best decision I ever made.

 

Yes, but that doesn't necessarily mean BOClean was the problem.

Well, I was the one that actually tweaked it....according to Kevin's instructions, not sure if this is the same tweaked version others are using. It added a time delay of some type. The point is, Kevin tried working with ESET but they weren't that co-operative, so Kevin had to come up with a work-around. Of course, I don't know ESET's side of the story, I'm just going by what Kevin told me.

I agree....but I've also learned that where there is smoke, there is usually fire. I'll give ESET the benefit of the doubt on this one....until I have actual experience with their support.