Hello, I recently purchased NOD32 for my corporate network and used a script to deploy it at logoff on user's workstations. We audited the script on several workstations with much success. After rolling it out to the general population, we had 4 complaints of the computer not allowing the user to login after it had restarted. The specific error they were getting was that their profile could not be loaded and the default windows profile would be used instead. The computer would then just sit at a blank desktop image for several minutes and then the Logon Screen would appear again. Repeating the process would result in a loop. Could not boot into Safe Mode or login as the local administrator of the workstation. Here are the specs of the machines affected: Dell Optiplex GX620n Desktop 3.4Ghz Pentium D 4.0GB RAM ( 4 X 1GB) 80GB SATA HDD DVD ROM ATI 128 MB X300 PCI express video card Microsoft Windows XP Professional w/SP2 and latest patches Now, since we use AutoCAD and AutoDesk products, we are required to have large amounts of ram to process our jobs effeciently. So, with the 4.0GB of RAM it is recommended by Microsoft and other vendors to use the /3GB switch in the boot.ini file to offset the kernel memory. By doing this, it actually caused a problem with the NOD32 modules (I was unable to isolate which one) but by booting to an NTFS dos editor program from CD Drive I removed the /3GB switch and it began working again instantly. So, my real question becomes, that on the exchange server in our organization, running windows Server 2003 SP2 and the /3GB switch, will I have the same problem and is there a way to overcome this problem. I am going to try and test further before deploying to my exchange server but any help would be appreciated. Steve Gear Information Systems Mgr Larson Binkley, Inc.