Numerous First Resort clients who have implemented Symantec's Norton AntiVirus software have reported the following symptoms when Norton AntiVirus' auto-protect feature is enabled:

1. Error messages such as 'File XXXXXX.FIL does not exist' and 'Error 12 opening XXXXXX.FIL' on Novell networks.
2. Error messages such as 'Waiting for Lock' on Windows NT networks.
3. Inability to print from First Resort, with a resultant error message of 'abort, retry, fail.' See the related article from Symantec's knowledge base: http://service1.symantec.com/SUPPORT/nav.nsf/pfdocs/2001011513333706.
4. A significant slowdown in the speed at which First Resort runs.

In each of these instances, turning off Norton AntiVirus' Auto-Protect feature resolved the symptoms (although with printing problems, it may be possible to disable Script Blocking instead. See article linked above). Current versions of Norton AntiVirus allow for the exclusion of specific file extensions from Realtime protection while keeping it enabled. Some First Resort clients have had success excluding .fil and .idx file extensions from the Realtime protection (we have client reports that this exclusion capability does not exist in some Corporate editions of Norton AntiVirus). While this does not provide protection for First Resort data files, they are not typically at high risk for virus infection; virus programs typically infect boot sectors, executable program files, or dll library files.

Additionally, while we do not endorse one program over another, we have not heard of clients experiencing these types of problems with other leading AntiVirus programs such as McAfee or eTrust.com (Computer Associates).