View Full Version : troubles with NOD v2 and ZAF
June 15th, 2003, 10:59 AM
When using v2 of NOD I encounter severe incompatabilities between it and ZAF latest v 3.7.159. Every program trying to access the internet crashes or makes ZAF crash, leaving the system with no internet access. Uninstalling NOD solved the problem, so it definitely is NOD v2 related.
This is on a Win98 (non SE) system. I have no other systems available at the moment, so I cannot check with other OS versions.
Has anybody set up NOD and ZAF in peaceful coexistence?
June 15th, 2003, 11:31 AM
This wont help you much, but im running Nod v. 2 & Zapro 4.0 with zero probs, so it should also be running with Zaf, i would think.
June 15th, 2003, 12:43 PM
Iam running Kerio 2.15, also freeware, completely stealth, like ZAF, besides that i have the latest ZAPro at my disposal, and after installation of NODv2 had no probs.
An option maybe is switching to Kerio 2.15, a good choise i believe replacing ZAF.
Keep me posted,
June 15th, 2003, 12:53 PM
I am also running NOD32 V2 along with ZAP V4 and they both run great together. Did you try to uninstall ZAF to isolate the problem.
June 15th, 2003, 12:59 PM
True Rav, you first have eliminate all other possibilities before giving the blaim to a new program, good observation :)
June 15th, 2003, 01:26 PM
This may not have anything to do with it, but did you unload ZA completely and properly when you installed NOD?
The behavior you mention (losing internet connectivity) is typical of ZA when it hasn't been shut down properly. Just tossing it out there, just in case. It could be something else, of course, since you mention other programs crashing.
June 15th, 2003, 01:36 PM
That's often the problem with ZAF.
Proper deinstallation is:
Open ZAF, make sure it doesn't startup next time you reboot.
Close ZAF from the taskbar.
After this install any other internet related program of your liking.
This is the only way uninstalling ZAF or ZAP for that matter.
It is advisable after all this clean out your registry for some leftovers from ZAF before installing any new software.
June 15th, 2003, 02:24 PM
Ah, I meant unloading ZA as in shutting down, not uninstalling. For example, if one just exits the program as I recall vsmon may still be running although the GUI is off. Or someone might not load ZA at start up by using msconfig and unchecking the components rather than setting ZA not to load at start up from within the program itself and then rebooting.
Again, this may have nothing to do with the problem, just tossing it out there just in case it might be relevant. (Only because in the past I've seen people reporting internet connectivity problems with ZA when they used msconfig to have ZA not load at boot up.)
June 15th, 2003, 02:35 PM
You must agree that ZA has a long history with this issue when not correctly uinstalled and it always leaves a bunch of registry entries of which they say isn't, so it's better to clean out the registy too before installing other software (internet related)
June 15th, 2003, 02:51 PM
Yes, but I in reference to the topic of the thread I was talking about the recommended procedure of shutting down all other programs that are running before installing another program.
He's still running ZAF so presumably he didn't uninstall it. And the connectivity issue only arose when he installed NOD and went away when he uninstalled NOD. So I was just wondering on the offchance that perhaps if ZAF was running or improperly shut down when NOD was installed that may have had something to do with the issues he was experiencing.
June 15th, 2003, 02:58 PM
Stating the fact that he might uninstall ZA it's in order to know the right way of uninstalling ZA, surely not knowing
this, it is certain that he should meet trouble thinking the uninstalllation is succesfull but isn't.
June 16th, 2003, 03:51 PM
Thank you for the replies.
Well, it all comes down to an incompatability between NOD and ZAF, at least on my system.
Uninstalling ZAF resolves the situation, but again, I still want to use it. And it definitely is not an issue of a wrong ZA install. I have installed ZA in all variants on dozens of systems, cleaned out the registry countless times, fixed errors with etc., so I know about its weaknesses ;).
The very special thing about my problem is, that NOD and ZAF in combination block any internet access, so I have to remove one of them. Tried this on a clean win98 install and can reproduce it.
Each program alone does not cause any problems.
It still can be a lot of other reasons, dlls, drivers etc, so I am interested in reports from other users of ZAF v 3.7.159 on Win9x with the latest NOD...anybody out there?
June 18th, 2003, 01:35 PM
Hello, really nobody with ZAF and NOD?
A bit more of info on this issue: The conflicting component is (well, not a surprise ;)) Imon. If I disable that, everything works ok...will dig a bit deeper into the winsock setup...maybe some corruption there...
In the meantime please report if you have a running ZAF + NOD + Win9x.
Thank you .
June 18th, 2003, 02:48 PM
A little closer to the solution. Imon seems to be unable to install itself as a winsock provider. To visualize this behaviour I used the LSPfix utility mentioned here: http://www.wilderssecurity.com/showthread.php?t=10101.
After checking the appopriate registry entries I find that Imon adds a lot of double entries and some entries where it overwrites the beginnings of the PackedCatalogItem binary registry entry. I am not a Winsock expert ;), but looks like a setup failure...anybody from the NOD tech team around?
June 18th, 2003, 03:02 PM
Ok, I know I am getting on everybody's nerves with this...;) but seems like IMON is really failing to install sometimes.
Found an old programming project of mine which installs a LSP and checked the way this project created registry entries :). In fact it stores the whole path to the dll in the provider string. Like c:\windows\system\provider.dll. Instead IMON adds only imon.dll and leaves over the rest of whatever provider name it has replaced.
Even worse: IMON adds a (random?) number of entries containing imon.dll.S\SYSTEM\rsvpsp.dll which once was c:\windows\system\rsvpsp.dll.
Result: When processing provider transaction the OS cannot find the given provider and inet access is impossible.
Well, I guess I have found what causes the problem...if anybody of the NOD tech team has time...let me know if I can be of further help in fixing it :). I guess a topic rename would be nice as this seems to have nothing to do with ZAF...is that possible??
June 18th, 2003, 05:49 PM
I noticed ZAF not responding upon shutting down several times upon the upgrade from Beta 5 to the final version 2.0 However my system (XP Pro) seems to have settled down.
I have done a IMON\Setup\Network Configuration Changes\Repair
June 19th, 2003, 05:09 AM
I'll get in touch with the IMON developer.
June 19th, 2003, 05:56 AM
Blackspear: The repair function does not solve the problem.
Seems this problem occurs only on Win9x systems. I tested it again on a completely clean install of Win98 and I can reproduce this faulty behaviour, so I guess it is just a bug in the setup routine, maybe wrong retrival of the path to the imon.dll...just a guess ;).
June 20th, 2003, 04:18 PM
Any news about the IMON install? More info needed? Or all too busy ;)?
June 23rd, 2003, 04:40 AM
>Or all too busy ?
I can't say no here. :)
Anyway, pls. PM me with your e-mail address - need more info from you.
June 23rd, 2003, 04:54 AM
I posted a fix in the forum right now. Send you my email in pm.
vBulletin® Copyright ©2000-2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums