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

WELCOME TO THE NORTON ANTIVIRUS FOR NETWARE (NAVNLM)!

This file contains information about NAVNLM that is not included in
the NAVNLM User's Guide.  Please read this file thoroughly before you install
or use NAVNLM. To print the file from the DOS prompt, type:

      COPY READ.ME PRN:

This document includes the following sections:

    1) Installation Information
    2) General Program Information
    3) Pager Information
    4) Compatibility Information
    5) Novell NetWare Directory Services Issues
    6) Windows 95 Issues
    7) Workstation Configuration for Windows

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

BEFORE INSTALLATION

You can now launch INSTALL.EXE from DOS or Windows. If installing from DOS, you
must first log in with supervisor equivalent rights and map a drive to the SYS:\
directory of the server to which you want to install. (If installing from Windows,
you can map during the installation process). 

To map from DOS:

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

2. Press Enter.


LAUNCHING THE INSTALLATION

The NAVNLM User's Guide includes an error in the installation section that recommends
upgrading servers running earlier versions of NAVNLM to version 1.5. This should instead
read as "While you can freely intermix NLMs from all versions of NAVNLM, we recommend
upgrading your servers to the latest version of NAVNLM."

- To launch INSTALL.EXE 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 INSTALL.EXE from Windows, access the appropriate drive window and
  double-click INSTALL.EXE.

  Refer to the NAVNLM and Novell help available in the installation program for more
  detailed information about installing and mapping in Windows.


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

Symantec does not support running NAVNLM under Windows in standard mode. If you
choose to run in standard mode, load TBMI2.COM before you start Windows.

Windows must have its network support enabled (this is done via the network section
of the Windows Setup program). 

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 *
*********************

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 successfully
transmit.  For numeric dialing sequences and messages longer than 32 characters, the
modem must have a dialing buffer that is longer than 32 characters.

Pagers:  If a user tries to transmit a page on a server with no modem installed, the page
will not be transmitted.  Error messages are written to the server console screen and the
activity log.


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

Norton AntiVirus for NetWare 2.0 is compatible with and Novell certified
for use with NetWare 3.11 and 3.12, 4.01, 4.02, 4.1, SFT-III 3.11, SFT-III
4.1 systems, and NetWare for OS/2.

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

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

NetWare 3.1x File Hooks: NAVNLM 2.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 NAVNLM after these other NLM's. If another NLM is
not sharing the file hooks, NAVNLM displays a message, to which you can respond by reversing
the load order of NAVNLM and the other NLM.

Unloading: If NAVNLM 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.


********************************************
* NOVELL NETWARE DIRECTORY SERVICES ISSUES *
********************************************

If you have NAVNLM installed in Directory services, and configured it to use either Directory
servers or bindery emulation, and you want to change the operational mode, you must delete the
NAV for NetWare object in the Directory services tree. This object will be in the same container
as the server. The next time NAVNLM is loaded, it will prompt you to log in to Directory services
and will allow you to set the mode in which it runs.

If you are using Norton Desktop for Windows and operating under a NetWare 4.x Directory Services
environment, you may need to modify your path to include the NetWare NLS directory. The NLS directory
normally appears as a branch of the Windows directory. For example:

PATH C:\WINDOWS\NLS;C:\WINDOWS;[rest of the path]


*****************************************
* WINDOWS 95 ISSUES                     *
*****************************************

There are help engine problems in the M6 build (224) of Windows 95. The engine occasionally
crashes NAVNLMW when selecting help items. This problem has been fixed in later Windows 95 builds.

When running some combinations of network drivers and shells, install may not display the
Network button in the dialogs that select the install directories. In this case you can map
a drive using the Windows 95 Explorer.


*****************************************
* WORKSTATION CONFIGURATION FOR WINDOWS *
*****************************************

There are different versions of NETWARE.DRV to use for NETX versus VLM drivers when running
under Windows 3.x and above. If the VLM version of NETWARE.DRV is used with NETX drivers,
NetWare will not be fully functional under Windows and NAVNLMW.EXE will not have the needed
NetWare support it requires. NAVNLMW.EXE will issue the message, "cannot find a server running 
NAVNLM."

The user may get a message from NetWare during Windows startup that warns that the NetWare
drivers have not been loaded. When NetWare is fully functional under Windows, File Manager 
has a "NetWare Connections..." selection in the Disk Menu. It that selection does not appear,
NAVNLMW will not operate.

NETX operation under Windows requires NETWARE.DRV version 2.xx.
VLM operation requires NETWARE.DRV version 3.xx, which is located in the Windows\SYSTEM directory.

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

