Orb cannot run on my system: I have NOD32 Antivirus software installed. |
||||
Like many other antivirus programs, NOD32 Antivirus software pre-version 3.0 installs and uses an LSP (layered service provider) DLL called IMON.DLL which monitors Internet traffic in and out of your PC to protect your system against viruses and other malware threats. Some adware, spyware, and firewall software also use LSPs to imbed themselves in your system.
Unfortunately, IMON.DLL is known to create a severe conflict with Orb on many systems and prevent it from properly running or even causing it to crash. IMON.DLL may also put your CPU usage to 99-100% while streaming, or cause glitches and freezes on the Orb PC. Also, in some instances, it has been known to crash Orb on your PC when moving the Seek bar while streaming a file in WMP (on the remote client).
What can you do about it? Here are four things you can try:
a) Upgrade your version of NOD32 to the recently released v3.0 which, reportedly no longer uses IMON.DLL.
b) Uninstall NOD32 and use another antivirus software which does not cause conflict with Orb. One such program is the free AVAST-Home antivirus.
c) Uninstall your current version of NOD32, reinstall the program and select the 'Expert" option so you can select features you want to install and make sure you disable Internet Monitor when prompted during the installation. Then try using Orb again to see if the problem is resolved. (Note that some users have reported that disabling Internet Monitor alone does not resolve it, and they had to entirely remove NOD32 altogether to prevent further crashes).
d) If you cannot uninstall and reinstall NOD32, then try to unregister IMON.DLL from a command prompt, as follows:
1. from your Windows desktop, click Start > Run... then type cmd
2. at the prompt, type: regsvr32 /u imon.dll
3. close the command prompt window
After doing any of the above, you should do a clean install of Orb again as follows:
1. download and run the Orb Cleanup utility to completely remove Orb from your system;
That should fix it.
|
||||
Powered by
KBPublisher (Knowledge base software)

