I see from various threads that some like myself use both Nod and SSM. The problem is that if I enable SSM to load at boot I get as far as the Nod32 Splash screen and the whole system locks up. If I enable SSM after the WinXP SP2 desktop has loaded all is well. NOD is not incorrectly identifying SSM as mal/riskware. Perhaps the combination of the "at boot scanners" found in NOD, SSM and Outpost 4 is too much at a kernel level if all are trying to load at boot? Any thoughts would be greatly appreciated. Thank you.