SimonW
March 2nd, 2004, 06:03 AM
I've been running a full copy of NOD32 for around 4 months now without problems in any application.
Recently updated my firewall to LnS, and after some great help from Phant0m configured it to work with Shareaza. Unfortunately, after an short time ( >30mins) it (shareaza) crashes giving IMON.DLL as the cause of the error.
IMON is the dynamic internet monitor within NOD32 and I wonder if the combination of high P2P traffic / LnS / IMON checking could be the cause of the problem. I don't want to disable IMON completely, however it can be configured to ignore certain apps, which I've tried to no avail. I've also tried enabling/disabling the DLL scanning of IMON within LnS, as IMON will (due to its nature) appear constantly in the LnS log.
Again, I don't believe my problem is NOD32 directly, as I've been running it sccessfully with Shareaza for 4 months and differing firewalls. I really like LnS so don't want to move away from it back to a different firewall again either.
Any ideas would be appreciated...
Recently updated my firewall to LnS, and after some great help from Phant0m configured it to work with Shareaza. Unfortunately, after an short time ( >30mins) it (shareaza) crashes giving IMON.DLL as the cause of the error.
IMON is the dynamic internet monitor within NOD32 and I wonder if the combination of high P2P traffic / LnS / IMON checking could be the cause of the problem. I don't want to disable IMON completely, however it can be configured to ignore certain apps, which I've tried to no avail. I've also tried enabling/disabling the DLL scanning of IMON within LnS, as IMON will (due to its nature) appear constantly in the LnS log.
Again, I don't believe my problem is NOD32 directly, as I've been running it sccessfully with Shareaza for 4 months and differing firewalls. I really like LnS so don't want to move away from it back to a different firewall again either.
Any ideas would be appreciated...