Windows XP SP2 - Any Compatibility Issues with Nod32?

[lingochard]

The gigantic update is comming out soon...anyone have the beta of SP2 and been running Nod32 along with it? Any problems? Thoughts!

[NAMOR]

I have been running XP's SP2 RC2 for awhile now.... From my experience, I have not had any troubles with NOD and SP2 RC2. ;D

[tazdevl]

No troubles. Next time it might be a good idea to run a search before posting, this topic has been covered more than a few times.

[rdsu]

The beta version works very well on my system ;)

[coolasmoo]

Hi guys,

There is a very big problem with Nod32 and the RTM version of sp2

I double checked with a clean install of XP and as soon as you install Nod32 the network icon shows LIMITED OR NO CONNECTION.

The only things i have got on the OS at the moment are XP RTM , Via Hyperion Drivers, Realtek 1000 drivers and Nod32.

[Coolasmoo]

Im just currently downloading the Beta Version, and i will see if that will cure the problem for now.

Will report back

[Coolasmoo]

Well the Beta is incompatible aswell :(

If anyone can help heres my system specs


A64 3400
MSI K8Tneo
XP SP2 RTM

Using onboard Realtek Gigabit Ethernet

[ronjor]

What's in your error log for xp?

[Coolasmoo]

{QUOTE-> What's in your error log for xp? <-QUOTE}



Your computer was unable to automatically configure the IP parameters for the network card with the network address xxxxx. The following error accurred during configuration. The requested service provider could not be loaded or initialized


And

The IPSEC Services terminated with the following error.

[tazdevl]

{QUOTE-> Well the Beta is incompatible aswell :(

If anyone can help heres my system specs


A64 3400
MSI K8Tneo
XP SP2 RTM

Using onboard Realtek Gigabit Ethernet <-QUOTE}

You sure it's RTM? 2180? No issues here.

Sounds like you might have an app compatibility issue or something is borked with your install. Could be the medium itself.

Sounds like a problem with your network driver.

Are you running a VPN? Proxy server?

[Coolasmoo]

Yes its Final Build


I installed SP2 on my 3 month old install, and as soon as it rebooted the network became unusable.

So i thought Going to a fresh install would solve the problem, but it didnt.

Like i said i havent even loaded the X800 or sound drivers yet. Just the bare minimum to find the problem, and for me the problem is definatly Nod32.

As soom as i revert back to a restore point before i installed Nod32 the network works fone.

[Coolasmoo]

{QUOTE-> You sure it's RTM? 2180? No issues here.

Sounds like you might have an app compatibility issue or something is borked with your install. Could be the medium itself.

Sounds like a problem with your network driver.

Are you running a VPN? Proxy server? <-QUOTE}


Im running a Speedtouch 510V4 router with the Realtek NIC.

[Coolasmoo]

Just another quick update and i will leave it tonight.

It seems the problem is DHCP, as it wont assign an IP address.

I cant imagine why Nod32 is causing this but i hope this helps

[Coolasmoo]

I searched the forum and found a utility called ISPFIX

This told me that IMON.DLL was at fault and it removed the file

On reboot my network was back online, so i have temporarily disabled IMON after it re-registered itself .

I think im getting somewhere now.

[Blackspear]

{QUOTE-> I searched the forum and found a utility called ISPFIX

This told me that IMON.DLL was at fault and it removed the file

On reboot my network was back online, so i have temporarily disabled IMON after it re-registered itself .

I think im getting somewhere now. <-QUOTE}

IMON has a repair function as well...

IMON
Setup
Advanced Tab
Repair Now

Hope this helps...

Cheers ;D

[Coolasmoo]

{QUOTE-> IMON has a repair function as well...

IMON
Setup
Advanced Tab
Repair Now

Hope this helps...

Cheers ;D <-QUOTE}


Thanks for the help, but all that does for me is re-register imon and im back to square 1.

Now i know what the problem is, im not too bothered not running IMON as im sure AMON will take care of anything.

The thing that bugs me is my other PC is running the same SP2 RTM and connects through the same router and is running AVAST of all things with no problems :/

[Marcos]

Hi Coolasmoo,
please download and run the following utility: http:\\eset.zftp.com/npe.exe and send the log created along with a description of the problem to support@nod32.com

[coolasmoo]

{QUOTE-> Hi Coolasmoo,
please download and run the following utility: http:\\eset.zftp.com/npe.exe and send the log created along with a description of the problem to support@nod32.com <-QUOTE}



Ive sent you the results with Imon Enabled and Disabled.

Thank you for your help.

[Coolasmoo]

Hi again,

Thanks for the reply back from tech support but it didnt help as i dont have Nortan previously installed.

Ive found another user with the same problem, and ive asked him to post here.

[Cr4iG]

Im also having a problem with XP SP2, i cant get a IP address from my wireless network when it trys to assign it via DHCP. Just bought NOD32 a few days ago too :(

[kbrooks78]

Same issue here with a wireless connection, going to try setting a manual IP instead of automatic, let you know how that goes later.

[kbrooks78]

Setting a manual IP instead of automatic fixed the issue for me temporarily until NOD32 addresses the issue

[Cr4iG]

I am already using the static IP solution, but i use my laptop in wireless hotspots and in hotels alot, and alot of the time i dont know their IP ranges, so it isnt the best of solutions :(

[SimonJN]

Same issue here with my wireless connection - dhcp is unable to allocate an ip address, although I can manually configure one. It get's even stranger though - if I manually configure an ip address then my ISP won't let me access the web without bouncing me to a page that says I have the netsky virus ... neither nod nor mcafee stinger could find anything though!

Uninstalling sp2 fixed the problem. It didn't occur to me that Nod might be at fault ... I'll try removing that this evening and see if I have any more luck.

[Coolasmoo]

Well atleast we know that we could have a problem with NOD32 (IMON)

Is it a case of there may be a Fix, or is it better to try another (/shrugs) AV temporarily.

Im sure this problem will become more widespread as soon as SP2 goes on live update.

[SimonJN]

Uninstalled Nod, and reinstalled SP2 again. No problems with getting an ip address this time, nor does my isp think I have a virus anymore (although ironically I'm now vulnerable!). There would certainly seem to be clash between nod and sp2 ...

(edit) Oh, I almost forgot - these problems were using the current beta.

[SimonJN]

Another update - Installed Nod on my now working SP2 system, but this time not the beta. Did an expert installation and told it not to enable imon. Restarted system and internet worked ok. Enabled IMON. Internet still ok. Allowed Nod to update - everything still ok. Rebooted ... and internet no longer worked. Disabled IMON and tried to get an ip address but couldn't. Rebooted with IMON disabled and internet still didn't work. Uninstalled nod, and everything fine again...

[Marcos]

SimonJN,
couldn't it be the case described at http://www.wilderssecurity.com/showthread.php?t=28121 ?

[SimonJN]

{QUOTE-> SimonJN,
couldn't it be the case described at http://www.wilderssecurity.com/showthread.php?t=28121 ? <-QUOTE}

Hi Marcus - That was the case where you uninstalled Norton and it broke DHCP? No - this was a brand new pc with a fresh xp installation. I got caught by that "feature" of Norton before and haven't used it since.

I did check the dhcp service though (in case it was something similar), and it was running ok. It had written an error to the event log saying it couldn't allocate an ip address. I first assumed it was a compatibility issue with my wireless netword card drivers, but updating them had no effect. Only nod seems to have any effect. When I have time I'll do some more tests to try and tie down when it occurs more precisely.

[Stan999]

{QUOTE-> Another update - Installed Nod on my now working SP2 system, but this time not the beta. Did an expert installation and told it not to enable imon. Restarted system and internet worked ok. Enabled IMON. Internet still ok. Allowed Nod to update - everything still ok. Rebooted ... and internet no longer worked. Disabled IMON and tried to get an ip address but couldn't. Rebooted with IMON disabled and internet still didn't work. Uninstalled nod, and everything fine again... <-QUOTE}

Could it be a firewall problem?

[SimonJN]

Marcus, I did another quick test. I Installed the beta this time using expert mode, and I told it not to register Imon. My internet connection works fine. I allowed it to download the lastest definitions and rebooted again. Still fine. I suspect given my previous results that if I enable Imon that my internet connection will stop working again, and will remain broken until I uninstall Nod.

[SimonJN]

{QUOTE-> Could it be a firewall problem? <-QUOTE}

I suppose so. I'll disable the windows firewall entirely, and then enable IMon and see what happens.

[SimonJN]

{QUOTE-> I suppose so. I'll disable the windows firewall entirely, and then enable IMon and see what happens. <-QUOTE}

Right - one last test before bed! I disabled the windows firewall, and enabled IMon. Everything was ok. I restarted the system, and I was unable to get an ip address. Disabling IMon made no difference after that - I tried disabling & re-enabling my wireless connection but it kept failing. I tried using ipconfig to renew my ip address (ipconfig /renew) and got the following error :-

"An error occurred while renewing interface Wireless Network Connection : The requested service provider could not be loaded or initialized."

Once Nod had been uninstalled my connection started working again. I then reinstalled *without* Imon and it was still ok. It seems that if I enable IMon just once, then my connection breaks and stays broken.

[Blackspear]

{QUOTE-> ...It seems that if I enable IMon just once, then my connection breaks and stays broken. <-QUOTE}

Have you tried the "Repair" function after installing IMON?

Control Centre
IMON
Setup
Advanced (Tab)
Repair Now

Hope this helps...

Cheers ;D

[SimonJN]

{QUOTE-> Have you tried the "Repair" function after installing IMON? <-QUOTE}

I haven't yet - I won't be able to test that until Thursday. Will post back here when I have some more results.

[kbrooks78]

{QUOTE-> Have you tried the "Repair" function after installing IMON?

Control Centre
IMON
Setup
Advanced (Tab)
Repair Now

Hope this helps...

Cheers ;D <-QUOTE}

I tried this, but it didn't help me. :(

[BG]

ok ... I'll be a guinea pig. I plan on installing sp2 on my new notebook today. It has a Netgear wireless setup and ask that you use Netgears wireless drivers and disable XP's wireless service. This might be something to consider. I don't have the NOD beta installed just the current public version. Will write back when finished.

[BG]

OK just installed SP2 on my notebook with NOD, OUTPOST, BoClean, and Wireless connected to net running in the background. Only problem was when I created a rule in Outpost for alg.exe. Lost access to net. Deleted the rule and net access ok now. Updated the def in NOD no problems. Writing this from the notebook now.

[SimonJN]

{QUOTE-> OK just installed SP2 on my notebook with NOD, OUTPOST, BoClean, and Wireless connected to net running in the background. Only problem was when I created a rule in Outpost for alg.exe. Lost access to net. Deleted the rule and net access ok now. Updated the def in NOD no problems. Writing this from the notebook now. <-QUOTE}

So, the implication is that it's the combination of SP2, my wireless drivers and Nod that are causing the problem. Well, I've got another wireless card lying around so I'll add that to my list of things to try! I think it might simpler to just roll back to SP1 again :)

[hardhit]

I today also installed SP2 and I have the same problem of no longer being able to connect to the internet. I'm not using a wireless card so the problem also exists with wired cards.

Perhaps a good question what cpu are you guy's running on.

The ones without problems and the one with problems.

I myself am using an AMD A64 3200+ CPU.

Could this be cpu related ?

The only solution that I have found till now is to use a program called WinsockXPfix. This somehow disables the IMON monitoring. After a restart then I get my connection back. I can then restart the IMON service but the problem is there again after a restart. I can however now disable the IMAN service within the NOD32 program and I get my connection back. After I got my connection back I can then again restart the IMON service.

I know this is not an easy way to use the program but it's a way.

Regards,

Peter

[Coolsasmoo]

My system for comparison

A64 3400+
MSI K8T NEO fsr2
Using onboard Realtek Gigabit Network Card
Via 4.51 drivers
ATI X800XT
SB audigy 2

The audigy and the X800XT arnt the problems because i did a fresh install and IMON was causing problems before these were installed.

So its either the A64, Realtek Network Card or the VIA 4.51 Drivers and IMON

[BG]

P4 2.6g
512mg ddr
Netgear MA521 Wireless pcmcia

[Alec]

Guys, everything everyone is saying sounds consistent with a conflict among what's called "Layered Service Providers" or LSP's. LSP's are kernel mode snippets of code that get "sandwiched" or "layered" in the Winsock TCP/IP stack. That is how IMON apparently works it magic, it has code that gets inserted into the protocol stack as an LSP. LSP's sort of form a chain and if there is a conflict or an erroneous entry in the chain then it can basically kill or stop all communications through that chain of LSP's.

Apparently, enabling and/or disabling IMON is adding or removing these LSP entries. Disabled, no problems... enabled, the chain gets broken and communication stops. Some of you say that installing NOD32 without IMON and then enabling IMON later on works once (prior to a reboot); but I'm curious if that is actually enabling IMON to inspect actual POP3/SMTP/HTTP traffic during that current session. My guess is that enabling IMON only adds the LSP entries in the registry somewhere and that it doesn't really work until a reboot... which in turn causes the conflict and the resulting failure.

Anyway, with all these reports of issues, hopefully Marcos can gather enough evidence to isolate the bug. As someone early on pointed out, LSPFix (http://www.cexx.org/lspfix.htm) should help you fix your problems. Also, users of Ad-Aware can install a plug-in called LSP Explorer (http://www.lavasoftusa.com/software/plugins/lspexplorer.shtml) that will show you what Layered Service Providers are installed. Other than that, if you have problems just keep IMON off. :(

[Cr4iG]

So will ESET be releasing a fix for this? Or am i going to have to put up with this "feature" if not, then i think its time to move to another AntiVirus, quite dissapointing because ive had NOD32 just over a week.

[Alec]

{QUOTE-> So will ESET be releasing a fix for this? Or am i going to have to put up with this "feature" if not, then i think its time to move to another AntiVirus, quite dissapointing because ive had NOD32 just over a week. <-QUOTE}Well, first off, just keep in mind that I'm simply speculating based on what I have heard. Secondly, I'm not in any way, shape, or form an official spokesperson. Third, there may not be any "bug" at all. It may somehow be a simple (or not so simple, depending upon your perspective) misconfiguration, or something otherwise wholely unrelated to the NOD32 code itself. However, it sounds like several people had the same/similar problem, so that is probably doubtful.

Keep in mind that we are all dealing with several complicated variables... the release of SP2, the release of new functionality in NOD32 v2, etc. With SP2 there are bound to be a few rough patches, and not just with NOD32. If it is an Eset problem, I think they will resolve it in a fairly timely fashion. They seem to be fairly responsive based upon my experience. They also seem to have a nice componentized structure that lends itself to modular updates, so hopefully any issues can be fixed just that much quicker.

[SimonJN]

Finally got a chance to try a few more things ...

1. Using Repair in IMON - no effect.
2. Enabling IMON and then using LSPFix - yes, that fixes it but only by disabling IMon.

I noticed that the IPSEC service always failed to load as well. This may be related or not.

Regarding my hardware - I have an Athlon 64 3000 (so that makes three of us), it's on a NForce 3 motherboard and my network card uses a Prism chipset .

Since the Athlon 64 has the NX bit which stops programs running code from data segments, I wondered if that might be related. By default SP2 enables it only for "essential windows programs and services" which you would assume includes Nod ... anyway, I turned it on for everything. Nod wouldn't load at all after that - no32krn.exe kept repeatedly crashing and restarting and filling up my event log with error messages (like) :-

"The NOD32 Kernel Service service hung on starting." -and-

"The NOD32 Kernel Service service terminated unexpectedly. It has done this 20 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service."

If any of you other A64 owners want to try it (just in case it's my xp installation that's shafted), you'll find the option in control panel / system / advanced / Performance Settings / Data Execution Prevention.

Thanks for the various suggestions - I'll be leaving IMon disabled for the moment.

[kbrooks78]

I have a Athlon64 3400+ on an Asus K8N (Nforce3), same problems on wireless usb nic and onboard ethernet. I think I remember a option to disable the data protection thing, gona see if I can do that for NOD32 when I get home (at work now).

[Blackspear]

One last suggestion, have you tried removing Winsock and Winsock2 by doing the following:

How to Recover from Winsock2 corruption

To resolve this issue, delete the corrupted registry keys, and then reinstall of the TCP/IP protocol.

Step 1: Delete the corrupted registry keys

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

4. When you are prompted to confirm the deletion, click Yes.

Note Restart the computer after you delete the Winsock keys.

Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.

Step 2: Install TCP/IP

1. Right-click the network connection, and then click Properties.
2. Click Install.
3. Click Protocol, and then click Add.
4. Click Have Disk.
5. Type C:\Windows\inf, and then click OK.
6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
7. Restart the computer.

Cheers ;D

[Cr4iG]

Athlon 64 3400+ In my laptop too, wireless card is made by Ralink

[SimonJN]

So, BG and Blackspear have P4's and have no problems with SP2/NOD, and those of us that have Athlon 64's (5 in this thread? all have the same problem ...

I haven't tried Blackspear's suggestion about removing winsock (I'll try that this evening), but I am really starting to believe it's a three way clash between the cpu, sp2 and nod ... I wonder is anyone at Eset has an Athlon 64? If not, I'm happy to do more tests for them.

On a related note - I tried to totally disable DEP last night, but it didn't seem to work. However I did get a slightly different error on boot up. Instead of the nod kernel crashing, I got a message saying that it had been stopped by DEP.

[Coolasmoo]

I concur that it must be A64 related

And i can carry out tests if needed by ESET.

[SaphireX]

Hey Coolasmoo

I would try uninstalling the Realtek Gigabyte LOM drivers and after rebooting re-install them. To SEE if your onboard Nic works. I installed the IT version of SP2 (the full boat) yesterday and have no problems connecting using my on-board 3-Com Gigabyte LOM. I am running the NOD32 Beta and except for the error code 0x800A01AD = Web Page Run-Time Errors at the new XP Update Site caused by IMON running everything else seems to be running normally.

SP2 added a tray icon for Local Area Coonection and it is in a limited state. SP2 added the firewall to both my DSL connection as well as the 1394 connection (since the on-board chipset establishes that).

I found that disabling IMON allows the windows update site to function correctly and hope that Eset modifies NOD32 so that temporarily turning off IMON is not a long standing workaround....

Hope this Helps

Saphire

[Coolasmoo]

Hey SaphireX,

Thanks for the suggestion, but un-installing and re-installing the NIC didnt help.

I see your also using the A64,


Ive just found a new feature to SP2 and wondered if installing this would help.

http://www.tweaktown.com/document.php?dType=guide&dId=682&dPage=4

IPv6 Support

quote: SP2 comes with support for version 6 of the Internet Protocol (IPv6). Those of you running (or wishing to run) IPv6-compatible networks can now install the protocol by clicking “Install…” in the properties dialog for the specified connection.

[SimonJN]

Hi Folks,

I emailed Eset with my problem re: A64 / SP2 / Nod and been unable to get an ip address - and they sent me a link to the latest beta. You'll be happy to hear that it fixes my problem. Thanks to those who gave suggestions / help ... hope this release fixes your problems too.

Oh, and thanks to Eset who responded within minutes to my email ...

[Blackspear]

For those having this problem, try emailing beta2011@eset.sk and place a link to this thread, they will probably give you a newer version of the Nod32 Beta as SimonJN has found, it solved the problem...

Cheers ;D

[Coolasmoo]

E-mail sent,

Thanks for the heads up SimonJN / Blackspear

As soon as i get a link and install, i will post back with results

[Cr4iG]

I have emaild them too, thanks for the address, will let you know how i get on :)

[Anonymous]

I have an AMD 2500+ and have the same problem as everyone else here. Turning off IMON completely is the only solution I have found. I am using the latest beta from ESET, and it still has the same issue.

[Blackspear]

{QUOTE-> I have an AMD 2500+ and have the same problem as everyone else here. Turning off IMON completely is the only solution I have found. I am using the latest beta from ESET, and it still has the same issue. <-QUOTE}
Is the Beta you have version 2.12? See the following:

NOD32 Antivirus System information
Virus signature database version: 1.842 (20040813)
Dated: Friday, 13 August 2004
Virus signature database build: 4754

Information on other scanner support parts
Advanced heuristics module version: 1.008 (20040804)
Advanced heuristics module build: 1057
Internet filter version: 1.002 ( 20040708 )
Internet filter build: 1013
Archive support module version: 1.018 (20040727)
Archive support module build version: 1093

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.0
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.0
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.0

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 496 MB
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz (2813 MHz)

If it is, please re-email Eset using the address posted above...

Cheers ;D

[RottGutt]

I guess that I do NOT have the latest build. Here is what I have:

NOD32 Antivirus System information
Virus signature database version: 1.842 (20040813)
Dated: Friday, August 13, 2004
Virus signature database build: 4754

Information on other scanner support parts
Advanced heuristics module version: 1.008 (20040804)
Advanced heuristics module build: 1057
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.018 (20040727)
Archive support module build version: 1093

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.000.11b
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.000.11b
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.000.11b

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 512 MB
Processor: AMD Athlon(tm) XP 2500+ (1837 MHz)

I am now searching for this latest buil to try out.

[Mele20]

NOD32 is on the Microsoft list of applications that will likely have problems after SP2 is installed. After reading that list and seeing a large number of my applications on it, I am even more convinced that I won't be installing SP2 until Microsoft no longer supports SP1 which is at least a year into the future. Even Word and Works Suite are affected! Several other av programs besides NOD32 are listed also.

[RottGutt]

Anyone have the link to the v2.12 beta? I am not getting any responses to the 2 tech support e-mail I sent ESET.

[izi]

{QUOTE-> NOD32 is on the Microsoft list of applications that will likely have problems after SP2 is installed. After reading that list and seeing a large number of my applications on it, I am even more convinced that I won't be installing SP2 until Microsoft no longer supports SP1 which is at least a year into the future. Even Word and Works Suite are affected! Several other av programs besides NOD32 are listed also. <-QUOTE}Where did you find list of applications that will likely have problems after SP2 is installed? Could you post link here?

[ronjor]

http://support.microsoft.com/default.aspx?kbid=884130&product=windowsxpsp2

[Blackspear]

{QUOTE-> ...I am not getting any responses to the 2 tech support e-mail I sent ESET. <-QUOTE}
Did you email beta2011@eset.sk and place a link to this thread?

Cheers ;D

[Thorz]

I have seen that some of you people are using wireless. I have a recommendation to you that has worked for me, but it has nothing to do with SP2. I have a laptop with an Asus WL100g card and NOD32. When I installed the card it has also installed the Asus WLAN utility that takes over the Windows Zero Wireless Configuration service. This utyl was working ok but after I installed NOD32 I could not access my WLAN. The solution was removing this utyl and leting Windows control the WLAN connection, configuring everything through the Windows network setup boxes. I have read that this is advised in many situation of incompatibilities, not only with NOD32. Be sure also if you are not on SP2 yet to install the WPA patch from Windows update.
I hope that your problems are solved, I have been facing other kind of bugs.
By the way: I a on an Intel (P4 3Ghz) machine with NOD32 official installed and have instaleled SP2 without any problem, but as you all have already said the problem is related with the A64 processors. I think that M$ shares the feil here. That list of apps is unbelieveble long!

[SaphireX]

I sent 2 emails to the beta address asking for a newer version to test and thus far have not received any reply..I am guessing that since this is a weekend that nothing will come of it till the regular work-week

Thus far in comparison to the SP2 beta that I toyed with when it first came out the final version of SP2 has not posed any of the crashes and application incompatabilities with the NX Flag turned on since my CPU has native support for that "flag"

I did noticed that the NO Data Execution setup has dramatically changed in the final SP2 than the way it was in the beta SP2 where it basically applied the flag to all applications regardless if you tried to turn it off....

The only unresolved issues so far that I have discovered is that IMON is blocking the runtime code on the Windows Update 5 Site and is why? I am asking Eset to send me the "beta version" that Blackspear talks about..Hopeing that will solve the IMON compatability with Windows Update Site 5. I still have the problem of moving files in explorer due to AMON under SP2 and hoping that a newer version of that sub-application will solve that as well

Cheers

Saphire

[Cr4iG]

The latest beta from the NOD32 website did not fix my problem sadly :(

[Coolasmoo]

If its any help to Eset,

I changed Motherboards today.

Went from a Via based K8T Neo with onboard Lan

To an Nvidia Nforce 250 K8N Neo with onboard Lan

And the problem is still there, So its not Network / Lan Drivers its A64 causing the problem.

[Tempest]

{QUOTE-> If its any help to Eset,

I changed Motherboards today.

Went from a Via based K8T Neo with onboard Lan

To an Nvidia Nforce 250 K8N Neo with onboard Lan

And the problem is still there, So its not Network / Lan Drivers its A64 causing the problem. <-QUOTE}

If you look in another thread is seems like this has/is being fixed as we speak and a new fixed version is on the horizon......

I guess AMD64 and SP2 was too much of a combination, though............

What does ANNOY ME is that why don't they put this info up on their website and stop users having to scrabble around forums trying to find out what's going on..

Communication please guys :)

[Cr4iG]

Just got an email off Eset support, latest internal beta fixes this issue :)

[Coolasmoo]

Yep. just got the link to the Beta, and its solved me problems.

Thanks all,

[Blackspear]

{QUOTE-> Just got an email off Eset support, latest internal beta fixes this issue :) <-QUOTE}

{QUOTE-> Yep. just got the link to the Beta, and its solved me problems... <-QUOTE}
Good to see, thanks for keeping us in the loop...

Cheers ;D

[SaphireX]

Hi All

Mark at ESET Tech Support was kind enough to send me the latest "test beta" and here is the text of my reply based on my observations with this new build..........

"Hi Mark at ESET Tech Support

I just uninstalled the "old" version of NOD32 "beta" and installed the newer "beta" version you just sent me and SURPRISE :) both the Windows Update Site as well as the Office 2003 Update Site worked just fine-without a hitch!

So it looks like this build is fully compatible with the SP2 Windows Update Site, The Office 2003 Update Site. My onboard 3-Com Gigabyte LOM NIC chip connected to the web without any issues......

I did check to SEE if I can move files around using Explorer and it looks like I can move files around OK with the exception of DivX AVI files where They cannot be moved around without producing the error message that "it is being used by another person or program-close any programs that might be using the file"

I am thinking that this might be a "DivX" thing and that the latest version of DivX is not fully compatable with SP2

All in all I am very pleased with this new build and I Thank You very much for sending it to me

Thanks Again

Jim

NOD32 Antivirus System information
Virus signature database version: 1.845 (20040816)
Dated: Monday, August 16, 2004
Virus signature database build: 4764

Information on other scanner support parts
Advanced heuristics module version: 1.008 (20040804)
Advanced heuristics module build: 1057
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.018 (20040727)
Archive support module build version: 1093

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.0
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.0
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.0

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 1023 MB
Processor: AMD Athlon(tm) 64 Processor 3200+ (2002 MHz)

[Blackspear]

{QUOTE-> ...All in all I am very pleased with this new build... <-QUOTE}
Great to see Jim

I know they are working on fixing problems, it would just be nice to hear a little more from the Beta team as to progress...

Cheers ;D

[kbrooks78]

Got the beta email also and it fixed my issues also, yay! ;D


--edit--
yay first post on page 4!!!!

[Nirvy]

I too have both these issues, the most frustrating is the DEP shutting NOD32 down all thr time.
Where do i get this beta? I have sent several Tech support emails off from their site, about 5 days ago, but have no reply yet. I only bought nod32 a week ago, and am regretting it now :(

I too have an A64 3200 and SP2

[Blackspear]

{QUOTE-> I too have both these issues, the most frustrating is the DEP shutting NOD32 down all thr time.
Where do i get this beta? I have sent several Tech support emails off from their site, about 5 days ago, but have no reply yet. I only bought nod32 a week ago, and am regretting it now :(

I too have an A64 3200 and SP2 <-QUOTE}
Send an email to beta2011@eset.sk and place a link to this thread...

Hope this helps...

Cheers ;D

[SaphireX]

Hey Nirvy

Perhaps the latest NOD32 "beta" might help solve the nx=no data execution issue and the crashes you are experiencing ....However since we both have the AMD64 CPU that supports the NX Flag=DEP ... I strongly recommend that you change it to be setup as, .... per the attached snapshot.

I found this NX Flag or DEP if it was set to cover all programs in the beta version of SP2 to be completely unworkable and crashed several applications or worse BSOD's !

So I decided that in the final released version of SP2 to keep DEP on only for essential windows programs and services.......

Hope this helps

Saphire
http://img.photobucket.com/albums/v242/Saphirex/nx1.jpg

[fredra]

{QUOTE-> Send an email to beta2011@eset.sk and place a link to this thread...

Hope this helps...

Cheers ;D <-QUOTE}
Hi Blackspear
I followed your advice and sent the email, outlining my anomalies, (unable to get Windows updates and tranferring large files) with a link to this thread. Unfortunately, I have not received any response as yet. ???
I had to remove NOD32 (didn't want to) for the time being, until ESET comes out with a new "beta" version. When the version arrives, I will install that and try again.
Thanks for all your assistance.
Cheers :)

[Blackspear]

{QUOTE-> ...I had to remove NOD32 (didn't want to) for the time being, until ESET comes out with a new "beta" version. When the version arrives, I will install that and try again. Thanks for all your assistance... <-QUOTE}
My pleasure Fredra, new Beta arriving shortly...

Cheers ;D

[Coolasmoo]

Hey again Blackspear.

Just one question,

Now that the latest beta solves our problems, is it a case of checking back here for a Final version or will we be notified by e-mail.

[Blackspear]

{QUOTE-> Hey again Blackspear.

Just one question,

Now that the latest beta solves our problems, is it a case of checking back here for a Final version or will we be notified by e-mail. <-QUOTE}
How Eset did the last one was a notification through your installed version of Nod32, that there is a "Program Component Upgrade" available...

Hope this helps...

Cheers ;D

PS. are you going to join us as a member one day?

[Nirvy]

Thanks all, installing this latest beta fixed it.

Thanks for the hint Saphire, but in the ned i turned DEP of completely by modifying my Boot.ini. I'll give it 3 or 4 months for patches to come out for 3rd party apps then try it again

[Blackspear]

{QUOTE-> Thanks all, installing this latest beta fixed it... <-QUOTE}
Good to see Nirvy.

Cheers ;D

[Coolasmoo]

{QUOTE->

PS. are you going to join us as a member one day? <-QUOTE}



NEVER


:P

[ronjor]

Welcome coolasmoo! :D Nice to have your input.

[Blackspear]

{QUOTE-> NEVER


:P <-QUOTE}
ROFLMAO well it looks like it is too late, you are in quicksand now my friend ;D once here, hard to get away ;D

;D 8) ;D 8) ;D

[Coolasmoo]

Thanks Guys :D


TBH, Im happy that with a bit of input from the community we got a fix and it didnt take too long.


Ive used quite a few AV's in me time and nothing comes close to Nod32.

If i can offer any future testing just throw an e-mail my way.

[myluvnttl]

I have a problem with NOD 32 and SP2. When the computer does a hot reboot, there would be a long delay loading up and it would say error loading the NOD Kernel Service. But if I log off and back in, NOD would load up. I will stick to SP1 untill they fix the bug in SP2.

[Blackspear]

{QUOTE-> I have a problem with NOD 32 and SP2. When the computer does a hot reboot, there would be a long delay loading up and it would say error loading the NOD Kernel Service. But if I log off and back in, NOD would load up. I will stick to SP1 untill they fix the bug in SP2. <-QUOTE}
What firewall are you using? If it is ZA 5.1.011 can you try uninstalling that and reinstall ZA 4.5.594

Can you also try the Nod32 Beta with SP2, I have not had a problem with that combination, other than beng one of a VERY small minority that still has a Lsass.exe error...

Let us know how you go...

Cheers ;D