FAQ/NOD32

From VFXPedia

NOD32 internet security and anti-virus software blocks all TCP/IP communication in fusion which can manifest itself as failures to render, run bins, disabling scripting, and failure to save or "save as" comps.

The problem is due to IMON, which can safely be disabled. You should also add Fusion.exe, eyeonScript.exe, eyeonServer.exe, files to the exclusion list within AMON.

In 1992, when NOD32 was introduced, very few programs operated at the Winsock level. Today, developers are regularly creating software in this manner. That would be fine, except for the fact that any application that operates here needs the top spot in the stack, and only one program can have it.

IMON was the first layer of defence; a supplement. The strength of NOD32 is AMON, which scans every file that performs an action, as it performs that action and the advanced heuristics which is stopping 90%+ of all new threats, before a definition is even written.

The current workaround is to add exceptions to AMON and turn IMON protection off, which will allow Fusion to communicate with other machines normally. By quitting IMON now, you'll not only allow both programs to operate together, but you'll also lose no coverage.

To add exclusions, open up the NOD32 Control Center> AMON> Setup> Exclusions Tab> Add>You can then click either Folder or File and then browse to whichever it is you wish to exclude.

Click "Ok" until you are back to the Control Center.

To disable IMON, please go to NOD32 Control Center (down by the clock) > IMON > Quit. Now a reboot is necessary.

After rebooting, the icon should be gray.

The next version of NOD32 will be sans IMON. It's being totally eliminated from the program for this very reason.