SYMANTEC CORPORATION - PETER NORTON GROUP
READ.ME file for THE NORTON ANTIVIRUS FOR NETWARE Version 1.05

WELCOME TO THE NORTON ANTIVIRUS FOR NETWARE!

This file contains information about The Norton AntiVirus for NetWare
that is not included in the user's manual.  Please read this file 
thoroughly before you install or use The Norton AntiVirus for NetWare.  
To print this file from the DOS prompt, type:

      COPY READ.ME PRN:

This document has four sections:

    1) Installation Information
    2) General Program Information
    3) Pager Information
    4) Compatibility Information

****************************
* INSTALLATION INFORMATION *
****************************

BEFORE INSTALLATION
From DOS, you need to map a drive to the SYS:\ directory 
of the server to which you want to install. This drive mapping must
be made while you have supervisor equivalent rights. 

1. At the DOS prompt, type the following, replacing SERVERNAME with 
   the actual name of the server:
 
       MAP NEXT SERVERNAME/SYS:

2. Press Enter.


INSTALLING
You can now launch INSTALL.EXE from DOS or Windows.

- To launch from DOS,  at the DOS prompt, type A:\INSTALL and press Enter.
  Substitute B as the drive letter if the diskette is in drive B.

- To launch from Windows, access the appropriate drive window and
  double-click INSTALL.EXE.


AFTER INSTALLATION

If you are installing to a NetWare 3.1X server and will be using a
modem on this server for paging, you will need to copy the AIO.NLM
and AIOCOMX.NLM files from Disk #1 to your SYS:\SYSTEM 
directory.  Do not copy these files if installing to a NetWare 4.x 
server.

Please note that if you have the SECURE CONSOLE command enabled on your 
server, you must install the product into the SYS:\SYSTEM directory, as
this will be the only location from which you can run any NLM.

The installation program will try to modify your AUTOEXEC.NCF file to
automatically load NAV.NLM.  On SFT-III systems, the installation program
will try to modify the MSAUTO.NCF file instead.

*******************************
* GENERAL PROGRAM INFORMATION *
*******************************

Configuration Program:  The configuration program requires the use of
IPX 3.10 and NETX 3.26 (or newer).  If the workstation is running Windows
in standard mode, TBMI2.COM must be loaded before starting Windows.
Windows must have its network support enabled (this is done via the 
network section of the Windows' Setup program). 

Configuration Program:  When logging in to the configuration program,
the username must have supervisory equivalency and an associated
password.  If the user attempts to use the configuration program without
an associated password, no servers will appear in the Servers list box.

NLM Console:  When enabling the NLM, disabling the NLM, starting a 
background scan, terminating a background scan, or unloading the NLM the
username must have supervisory equivalency and an associated password.

Server:  VREPAIR.NLM version 2.17 (distributed with NetWare 3.11) will
report that the score card entries in the Extended Attributes (EA) are
invalid for some files.  We recommend that you use VREPAIR version 2.18
(dated Sep 10, 1992) or later.

The VIRSPEC.TXT file contains information about viruses that cause
unique problems and require special handling.

*********************
* PAGER INFORMATION *
*********************

Support NLMs: AIO.NLM and AIOCOMX.NLM are required to be loaded if 
using a modem on a 3.1X server for paging.

Numeric Pagers:  When configuring for numeric pagers, the test message
and the actual message should not start with zero(0).  Services with 
voicemail may use zero to allow users to leave a private voicemail
message. If the user attempts to send a numeric message beginning
with a zero to a private voice mailbox, the page will not be
successfully transmitted.  For numeric dialing sequences and messages
longer than 32 characters, the modem must have a dialing buffer that 
is longer than 32 characters.

Pagers:  A server must have a modem installed on it before it can be 
used as a modem server.  If a user tries to transmit a page on a server
for which no modem is installed, the page will not be transmitted.  This 
will not be readily apparent to the user, although error messages are 
written to the server console screen and the activity log.

Modems:  When configuring for pagers, you must enable the modem 
associated with a server before you use that server.  By default, modems 
are not enabled. Also note that Norton AntiVirus for NetWare does not support
paging on SFT-III servers.

Pager Services:  When configuring pagers, the default for communications
is 300 baud - 7E1.  Some pagers require different settings, such as
300 baud - 8N1.  Verify your pager's requirements with your pager 
service.  Remember that the system should work correctly with all 
numeric pagers.  Alphanumeric pagers should comply to the 
Telecommunication Alphanumeric Protocol (TAP) standard.

*****************************
* COMPATIBILITY INFORMATION *
*****************************

Norton AntiVirus for NetWare 1.0 is compatible with NetWare 3.11, 3.12,
future 3.1X releases, 4.01, future 4.X releases, and SFT-III systems.

NLM Console: Norton AntiVirus for NetWare 1.0 automatically determines 
the type of monitor used by the server. If the server is using a color 
monitor, you can change the color display to monochrome by using the 
/MONOCHROME switch at the time you launch Norton AntiVirus for NetWare.
For example:

        load sys:\system\navnlm\nav.nlm /MONOCHROME

Novell File Hooks: Norton AntiVirus for NetWare 1.0 will use the 
standard file system hooks provided by Novell in CLIB 3.12f or later.
If you are running with an earlier version of CLIB, Norton AntiVirus
for NetWare will use a proprietary method of hooking the file system.
If compatibility problems arise under 3.12f with other NLM's that hook
the file system, you can use the /NOCLIBFILEHOOKS switch to force
Norton AntiVirus for NetWare to revert to its proprietary method of
hooking the file system. For example:

        load sys:\system\navnlm\nav.nlm /NOCLIBFILEHOOKS

NetWare 3.1x File Hooks: Norton AntiVirus for NetWare 1.0 can coexist
with most other NetWare 3.1x NLM's. This includes licensing, metering, 
and monitoring applications that also install file system hooks. For 
best results, load Norton AntiVirus for NetWare after these other 
NLM's. If another NLM is not sharing the file hooks, Norton AntiVirus 
for NetWare will display a message. If this happens, try reversing 
the load order of Norton AntiVirus for NetWare and the other NLM.

Unloading: If Norton AntiVirus for NetWare was not the last NLM to 
hook your NetWare 3.1x file system, you may not be able to unload
until the other NLM's are unloaded.

Users of NetWare 3.11 with the original shipping version of CLIB.NLM
dated February 14, 1991, may experience the following error message
when attempting to load NAV.NLM:

        Loader cannot find public symbol:  RenameThread

Users experiencing this problem can either upgrade to the latest version of
CLIB.NLM or load a patch NLM which is supplied on Disk #1. The PATCH311.EXE 
file is a Novell self extracting archive which contains PATCH311.NLM and a 
corresponding readme file. The PATCH311.NLM file should be copied to your 
SYS:\SYSTEM directory and loaded after loading CLIB.NLM. 
NOTE: This patch is only required when running NetWare 3.11 with the   
      original shipping CLIB.NLM

File Name Spaces: Norton AntiVirus for NetWare detects viruses on 
files accessed from DOS and Macintosh name spaces. OS/2 and other
name spaces are not monitored.

***** END OF FILE *****

