NOD32 Beta and Winsock LSP files...

Hello all,

I get the following errors on a "StartUpList" report.....

Enumerating Winsock LSP files:

Protocol #1: imon.dll (file MISSING)
Protocol #2: imon.dll (file MISSING)
Protocol #3: imon.dll (file MISSING)
Protocol #4: imon.dll (file MISSING)
Protocol #5: imon.dll (file MISSING)
Protocol #6: imon.dll (file MISSING)
Protocol #7: imon.dll (file MISSING)
Protocol #8: imon.dll (file MISSING)
Protocol #9: imon.dll (file MISSING)
Protocol #10: imon.dll (file MISSING)
Protocol #11: imon.dll (file MISSING)
Protocol #12: imon.dll (file MISSING)
Protocol #13: imon.dll (file MISSING)
Protocol #14: imon.dll (file MISSING)
Protocol #15: C:\WINDOWS\System32\dcsws2.dll
Protocol #16: C:\WINDOWS\System32\dcsws2.dll
Protocol #17: C:\WINDOWS\System32\dcsws2.dll
Protocol #29: imon.dll (file MISSING)

On my system NOD seems to be working with no problems, but since it is a beta, I thought I should post this. I am not sure if this is a serious problem or not.

Any words of wisdom will be greatly appreciated ....

Regards,
Kent

 

I can't help with the problem, but you might submit it to the email support for version 2. It is serious.
Mostly I wanted to post to tell you I'm drooling over your Dell.
Awesome, and don't tell me you don't love it.

 

Thanks Root and YES...I do love it....
Upgraded to this from a Gateway Essential Celeron 400 mhz with 8 gig HD, CD-ROM and SoundBlaster built on the MB....
Figured this time buy a good system and not have to worry about upgradind for a loooong time.....

I will send off an email to ESET about this error. It would be interesting if others would run StartUpList and see if anyone else gets this problem..... I used version 1.5 which I think is the latest.....

Regards,
Kent

 

Out of curiosity, I just went and download startuplist and lo and behold:

Enumerating Winsock LSP files:

Protocol #1: imon.dll (file MISSING)
Protocol #2: imon.dll (file MISSING)
Protocol #3: imon.dll (file MISSING)
Protocol #4: imon.dll (file MISSING)
Protocol #5: imon.dll (file MISSING)
Protocol #11: imon.dll (file MISSING)

So,I have the same problem. (I have to study the report... a lot to digest. I note that it says my registry check failed because the reg open command is "not normal". Whatever that means! Something to do with Script Sentry).

W98SE
Pentium III
450MHz.

 

Hello all,

I am posting again on this topic as I have not heard anything as to whether this is a serious issue or not. I sent an email to beta support as requested, but to date have not heard anything. I am 'still' using the beta and all still 'seems' to be fine, but a response would set my mind at ease .

Sorry, I know all you guys at ESET have your hands full at the moment, so please do not think I am complaining .

Regards,
Kent

 

> I am posting again on this topic as I have not heard anything as to whether this is a serious issue or not.

If you still have the missing .dll then it sounds like it might be serious.

Sorry ... I have no solution to suggest apart from a complete uninstall (including deleting the Eset directory) and a re-install.

I read in another thread that Jan had sent another user a modified Imon ... this may or may not help your problem ... I don't know.

 

Rodzilla,

I have tried the complete uninstall, deletion of ESET directory, cleaning the registry of any leftover NOD keys/values, and then reinstall. Still the same error when I run StartUpList. The imon.dll is in the system32 folder but for some reason StartUpList picks up an error...... It may be a problem with StartUpList, but I do not know. I do not seem to have any internet problems that I know of related to this. All seems OK and NOD beta seems to work fine....

Thanks for the response. I will try to get with jan and get an updated imon.dll and see if this helps.

Regards,
Kent

 

Hey puff-m-d,

sorry for the "Beta processing caused" delay.

>The imon.dll is in the system32 folder

This is important.

>It may be a problem with StartUpList

Yes - it looks like this. It doesn't seem to be any serious problem.

rgds,

jan

 

jan,

Thanks for the prompt reply....

Thanks for confirming what I was already leaning towards, that this particular problem was with StartUpList, not the imon.dll.....

Regards,
Kent

 

> Thanks for confirming what I was already leaning towards, that this particular problem was with StartUpList, not the imon.dll.....

That's the "other" possibility.