Wilders Security Forums  

Go Back   Wilders Security Forums > Archived Forums > Closed Sub-Forums > Archived ESET Support Forums > NOD32 Early v2 Beta
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
 
Thread Tools Search this Thread
  #151  
Old February 7th, 2003, 07:42 PM
M. Kabat
 
Posts: n/a
Default Re:(possible) bug reports v2.0 Beta1

Hi,

I've been testing NOD32 beta for a several weeks on WinXP Pro now without any problems. But yesterday I installed a new nVidia Detonator driver (v41.09) and NOD totally screwed up the TCP/IP protocol. A few necessary services refused to load, followed by socket errors. Uninstall of NOD resolved the problem (I've trided uninstalling the graphics driver first, but that didn't help; even a system restore to a week earlier did not work). Maybe it's just a coincidence, but the problems started after the required reboot from the graphics driver, and everything is fuctioning ok now with the new graphics driver and the first version of NOD. Maybe some can look into this...

Greetings,
Marek

  #152  
Old February 7th, 2003, 09:46 PM
Smokey's Avatar
Smokey Smokey is offline
Very Frequent Poster
 
Join Date: Apr 2002
Location: Annie's Pub
Posts: 1,513
Default Re:(possible) bug reports v2.0 Beta1

Quote:
quoting: M. Kabat link=board=36;threadid=5699;start=150#47277 date=1044664975]
Hi,

I've been testing NOD32 beta for a several weeks on WinXP Pro now without any problems. But yesterday I installed a new nVidia Detonator driver (v41.09) and NOD totally screwed up the TCP/IP protocol.

You realize v41.09 is a beta-version and not very reliable?
  #153  
Old February 8th, 2003, 12:30 PM
Marek
 
Posts: n/a
Default Re:(possible) bug reports v2.0 Beta1

Yes I do, but that counts for NOD also. And sice the driver works without problems with NOD 1, I think maybe the effect is the result between a conflict beteen the two beta programs. But eventually it was NOD which screwed up the system, not the driver, but I really can't figure out how this could have happened. I mean why would NOD screw up TCP/IP when anew graphics driver is installed, which has nothing to do with it? But just like I said, maybe it was a coincidence and NOD would have screwed up the protocols anyway.... I'll test it again when a new WHQL graphics driver is released to see if the error occurs again.

Greetings,
Marek
  #154  
Old February 8th, 2003, 02:01 PM
Fedorov999 Fedorov999 is offline
Regular Poster
 
Join Date: Sep 2002
Posts: 182
Default Re:(possible) bug reports v2.0 Beta1

FYI, I've been running 41.09 for a couple of months now and they are 100% stable, only thing I can suggest is you DISABLE Amon prior to installing drivers, many companies/products recommend you do this with resident AV scanners to avoid conflicts.

Also, invest in either PowerQuest DriveImage OR Acronis TrueImage and *always* take an image of your WinXP partition prior to removing/installing any new drivers.

It takes me 1min 30secs to restore my WinXP C: partition should I ever break it

Fedorov.
  #155  
Old February 8th, 2003, 03:47 PM
Marek
 
Posts: n/a
Default Re:(possible) bug reports v2.0 Beta1

AMON was disabled during Detonator installation.

Marek.
 

Wilders Security Forums > Archived Forums > Closed Sub-Forums > Archived ESET Support Forums > NOD32 Early v2 Beta « Previous Thread | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 08:04 AM.


Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums