IMON disabled with X-Cleaner

IMON is an additional level of protection to AMON working on Winsock level as an LSP. That means any application that does not work correctly with other LSPs may render network connectivity broken. I don't see any sense in bashing NOD32 for something that fully depends on the abilities of the oper. system itself. I'd suggest you address your inquiry directly to Microsoft as they are the developer of Winsock and they are responsible for how this technology works and doesn't provide any protection mechanisms that yould prevent the LSP stack from being modified by others LSPs.

 

Thank you Marcos for providing further understanding of Winsock and LSP's. I really don't think anyone was bashing Nod32, they were just curious as to how LSP's could be protected.

Cheers

 

OK then. Since IMON will be discontinued from NOD32 3.0, I assume any further comments on this are unnecessary and everything has been explained.

 

Marcos, thank you very much for the explanation. Timing is good because somebody just suggest me that my winsock might be corrupt. I'll try to repair that with the proper application.

Best regards.

 

Further information on repairing Winsock can be found HERE.

Cheers

 

Yeah no bashing from my part, I love my lil' NOD
I was wrong however about the IMON/AMON issue since IMON is using LSP.
I already knew that, but of course I forgot it - So it made me wonder a bit.

Anyways, looking forward to NOD 3 - Think I'll even have a go at the beta when it's released.

 

i assume nod32 will still have an http scanner, so how will it be different in v3.0 of nod32?