spm
April 14th, 2005, 10:30 AM
In NOD32 v2.1 (and the 2.5 beta), the IMON LSP library causes problems with other programs also installing an LSP. In particular, if the IMON LSP is present, it not only stops many web filtering programs (such as CyberSitter, CyberPatrol, ContentProtect, etc.) from functioning correctly, it also in some cases adds serious Windows startup delays (in the order of minutes) and can even stop logons succeeding at all when any of these programs are installed.
If IMON is stopped (i.e., its LSP is not installed), all of these issues go away.
Also, the IMON LSP DLL causes recognition issues with some anti-spyware programs like CounterSpy and MSAS (both being derived from the old Giant AntiSpyware, of course).
Interestingly, LSPFix also suggests removing IMON.
Is Eset planning on fixing this for NOD32 2.5 (it doesn't look like it, yet)?
If IMON is stopped (i.e., its LSP is not installed), all of these issues go away.
Also, the IMON LSP DLL causes recognition issues with some anti-spyware programs like CounterSpy and MSAS (both being derived from the old Giant AntiSpyware, of course).
Interestingly, LSPFix also suggests removing IMON.
Is Eset planning on fixing this for NOD32 2.5 (it doesn't look like it, yet)?