		 Central Point Anti-Virus for NetWare v2.0
 
This file contains information that is not in the manual or has changed
since the manual was printed. Please take a moment to read it.
 
This file is organized into four sections: 
   - Installation Notes
   - Configuration Notes
   - Compatibility Issues   
   - CentralSetup Notes
   - Changes to the Documentation


==============================================================================  
			    INSTALLATION NOTES


Installing Central Point Anti-Virus for NetWare v2.0 over v1.0
--------------------------------------------------------------  
  If you are currently running Central Point Anti-Virus for NetWare v1.0,
  you need to unload some of those files before you load v2.0:
	1. Unload the Central Point Anti-Virus for NetWare NLMs (CPAVNET
	   and CPMASTER) from the Central Point Anti-Virus for NetWare 
	   screen on the system console.
	2. At the server colon prompt, type UNLOAD CPLIB.
	3. You are now ready to install Central Point Anti-Virus for 
	   NetWare v2.0.


Upgrading from Central Point Anti-Virus for NetWare v1.0 or 1.1
---------------------------------------------------------------  
  The recipient lists for MHS and Pagers and subsequent information 
  must be reentered in v2.0. For instructions, see pages 18-29 of the 
  CentralAlert manual (Windows users) or pages 72-81 of the same manual 
  for DOS users.
  

Compressed Files on Local Disk after Installation
-------------------------------------------------  
  After installation is complete, you will find some compressed files in 
  the \CPAVNET directory on your local disk. These files are the SNMP 
  Agent upgrade files and are necessary to upgrade SNMP on any NetWare
  3.11 servers. The installation process leaves these files compressed,
  and they are expanded on the server when you upgrade SNMP.


Windows Program Groups
----------------------

  In certain cases, installation may not create a Windows program group for 
  Central Point Anti-Virus for NetWare. To create the program group in 
  that instance, add the following three executable files to that group:

	WNCALERT.EXE (CentralAlert)
	WNCPAVNT.EXE (Central Point Anti-Virus for NetWare)
	WNCSUP.EXE   (CentralSetup)


==============================================================================  
			     CONFIGURATION NOTES


"Down Server" Alerts
--------------------

  Central Point Anti-Virus for NetWare automatically keeps track of all
  the servers in its domain by pinging them every 60 seconds. If there
  is no reply from a particular server for approximately three minutes,
  the program issues a warning that the server is down.

  You can adjust the timeout period for the Down Server warning by editing 
  the file CPMASTER.CFG, located in SYS:SYSTEM\CPAVNET. You need to add a
  line to the bottom of the file that reads

	DOWN_SERVER_TIME xxx

  where xxx is the time in ticks (1/18th of a second). The default setting
  is 2340, or a little over three minutes. For purposes of calculating the
  timeout, note that there are 1,080 ticks per minute.

     NOTE: Please exercise caution when editing this file. Be sure to add 
     the new line to the bottom of the existing CPMASTER.CFG file, and not 
     to change any other settings.

  If you are having problems with Central Point Anti-Virus for NetWare 
  issuing Down Server warnings, you should try increasing the timeout 
  significantly. For example, setting the number of ticks to 11,000 would
  cause Central Point Anti-Virus for NetWare to wait approximately ten
  minutes before it issued the warning.

  When you save the file on the server running the CPMASTER NLM, it takes
  effect automatically.


==============================================================================  
			     COMPATIBILITY ISSUES


Note to Users of Cheyenne ARCserve
----------------------------------  
  Consider the following important guidelines when running any anti-virus 
  software on a NetWare server that also uses Cheyenne's ARCserve backup 
  (other backup programs might also apply). Note also that several companies
  offer ARCserve under other names; check with your supplier.
  
  If you are using ARCserve 4.0, your server might ABEND if you are running 
  anti-virus software at the same time ARCserve tries to back up an infected 
  file. This happens when running a backup with earlier versions of ARCserve. 
  Check with Cheyenne to make sure you have TAPEDRV.NLM (CHEYENNE.NLM) dated 
  4-15-93 or later and ARCSERVE.NLM dated 6-17-93 or later. In addition, 
  load the latest STREAMS and CLIB NLMs in the order listed below. Then 
  load ARCserve and Central Point Anti-Virus for NetWare, respectively.
  
     LOAD PATCHMAN (Patch manager for NetWare 3.11, 3-12-92 or later)
     LOAD STREAMS  (NetWare Streams ver. 3.11g, 8-24-92 or later) 
     LOAD CLIB     (NetWare C runtime library ver. 3.11d, 12-16-92 or later)
     LOAD TAPEDRV (or TAPEDU) LOCK (Need 4-15-93 or later)
     LOAD ARCSERVE (Need 6-17-93 or later!)
     LOAD CPMASTER
     LOAD CPAVNET
  
  If you are using ARCserve 5.0, Cheyenne suggests that you should load the 
  latest CLIB 3.11d and STREAMS 3.11g or later (check dates listed above).
  Central Point testing has been done successfully with ARCserve v4.0, v4.02, 
  and v5.0.
  
  Novell provides frequent patches, which are available on CompuServe. Check 
  with your NetWare representative or consultant to ensure that you have 
  all the necessary patches for your particular environment. Remember that 
  not all patches are necessary and that some, if loaded but not needed, 
  might actually cause problems. If you are unsure, please check with a 
  certified NetWare professional.

  Novell suggests that you maintain cache buffers at or above 40% of your
  total server memory. If the installation of Central Point Anti-Virus for
  NetWare, or any other product, causes your server memory to drop below
  40%, you need to add more RAM.
  

SFTIII Compatibility
--------------------  
  Central Point Anti-Virus for NetWare should be loaded only in the MSEngine, 
  not in either IOENGINE.  

  Due to problems with some Novell files, CentralAlert will not load under 
  SFTIII until Novell provides a CLIB fix, due in early 1994. At that time, 
  Central Point will provide you with the necessary files to run CentralAlert 
  under SFTIII.

  Keep in mind that SFTIII does not support SNMP or AIO; it is not expected
  to support these until SFT for NetWare 4.0, due in 1994. What this means
  to you as a Central Point Anti-Virus for NetWare user is that paging and
  NMS alarm functions are not available under SFTIII. However, CentralAlert
  can manage any domain containing SFTIII servers, simply by running on a
  non-SFTIII server. The two Central Point Anti-Virus for NetWare NLMs,
  CPAVNET.NLM and CPMASTER.NLM, will run without problems.


HP Printer Compatibility
------------------------  
  The HP Printer driver for the HP LaserJet III shipped with Windows 3.1 
  might cause problems printing reports in landscape mode. You need to 
  obtain an updated printer driver. This updated driver is being shipped 
  with the latest version of Microsoft products, or you can obtain it 
  directly from CompuServe, Microsoft, or Hewlett-Packard.


Central Point Anti-Virus for NetWare Version Compatibility
----------------------------------------------------------  
  Do not mix different NLM-based Anti-Virus software programs on the same 
  server. This will yield unpredictable results. 

  Also, do not put servers running Central Point Anti-Virus for NetWare v1.1 
  and Central Point Anti-Virus for NetWare v2.0 in the same domain.

  You cannot use Central Point Anti-Virus for NetWare v2.0 control programs 
  to configure Central Point Anti-Virus for NetWare v1.1 servers; nor can
  you use earlier versions of Central Point Anti-Virus for NetWare to 
  configure v2.0 servers. To have the optimal level of protection, you 
  should always upgrade all of your servers to the latest version of
  Central Point Anti-Virus for NetWare.


NetWare 4.0 Users
-----------------  
  You must use Bindery Emulation when using NetWare v4.0 with Central
  Point Anti-Virus for NetWare, CentralSetup, or CentralAlert.
		 

NetWare 4.0 Memory Protection (DOMAIN.NLM) WARNING!
---------------------------------------------------  
  If you are using NetWare v4.x and want to use CentralAlert, note the
  following:

  1.  If your NetWare 4.0 server is running DOMAIN.NLM (the memory
      protection NetWare Loadable Module or NLM), load the versions of 
      SNMP.NLM and AIO.NLM (shipped with CentralAlert) in Ring 0 
      (the OS domain) and NOT in Ring 3 (the OS_PROTECTED domain).
  
  2.  CentralAlert must also be in Ring 0 if you wish to send SNMP 
      traps. This is due to the fact that SNMP.NLM does not support
      Ring 3.

  3.  Since AFP.NLM v4.00a cannot be run in the NetWare 4.x Protected
      Domain, Central Point Anti-Virus for NetWare cannot scan volumes
      with the Macintosh Name Space when running in the OS_PROTECTED
      Domain.


NetWare 3.11 Users
------------------  
  If you are running NetWare v3.11 and want to send SNMP traps from 
  CentralAlert to NetWare Management System, you must upgrade from
  SNMP.NLM v1.0 to SNMP.NLM v2.0, which is shipped with CentralAlert.
  See "Upgrading to SNMP v2.0" on page 34 of the CentralAlert manual
  for more information.

  The following is extracted from INSTRUCT.TXT, a Novell file. It contains 
  instructions and an installation program to upgrade the SNMP.NLM agent 
  that was shipped with NetWare v3.11. Do not use this with SFT III or 
  NetWare v3.12 or v4.01; it is intended for use with NetWare v3.11 only.
  
  The v2.x version of SNMP.NLM is required to support sending SNMP Alerts.
  Without it, CALERT.NLM will be unable to send SNMP Traps.
  
  CentralAlert's Windows user interface copies Novell's SNMP agent upgrade
  to a designated server. You must then run PINSTALL.NLM from the server 
  console.
  
  Following is a portion of the text from the file INSTRUCT.TXT, which is 
  copied to the SYS:SNMP_1 directory by CentralAlert:
      
      =====================================================================
      NetWare v3.11 SNMP Agent Upgrade Version 2.1
  
      Installation Instructions
      =====================================================================
      The SNMP Agent for NetWare (NetWare SNMP) NetWare Loadable Module (NLM)
      file, SNMP.NLM, performs NetWare SNMP services. The NetWare SNMP 
      Upgrade Diskette allows you to upgrade NetWare SNMP on NetWare v3.11 
      servers.
  
      For NetWare v3.11, NetWare SNMP also depends on another NLM, the 
      AFTER311 NLM. Furthermore, you must load the TCP/IP NLM if the SNMP 
      management stations you run use IP as their transport mechanism. 
      This file explains how to install these NLM files on a NetWare v3.11 
      server.
  
      !!WARNING!! When you install NetWare SNMP, always use the NetWare SNMP 
      installation program from the NetWare SNMP Upgrade directory 
      (SYS:SNMP_1).
  
      The installation program contains version checking to prevent 
      existing versions of NetWare SNMP from being incorrectly 
      overwritten. This version checking is extremely important. 
      For example, NetWare MultiProtocol Router software v2.0 or 
      later, WAN Links software v2.0 or later, and NetWare v4.0 
      already contain coordinated versions of the NetWare SNMP 
      NLM and related NLM files. Installing the NetWare SNMP Upgrade 
      without using the version checking can overwrite existing 
      NLM files and disable services, such as routing, that depend 
      on these files.
    
      Since the NetWare SNMP NLM depends on other NLM files, you
      *must* use the installation program. Do NOT simply copy the
      NetWare SNMP NLM to the server.

      When the workstation is finished upgrading SNMP on the server, the 
      Workstation will prompt the user to run PINSTALL on the server.  Centra-
      Alert must be loaded on the Server before PINSTALL can be run.  PINSTALL
      will complete the SNMP upgrade on the server.
==============================================================================  
			  CENTRALSETUP NOTES


CentralSetup Installation
-------------------------    
    When you Install Central Point Anti-Virus for NetWare, CentralSetup is 
    not automatically installed on the network. CentralSetup is installed in 
    the administrator's Central Point Anti-Virus for NetWare directory.
    The first time you save the configuration settings after running
    CentralSetup, a dialog box notifies you that the files have not yet been
    saved to the proper server, and gives you the opportunity to do so at 
    that time.


Updating Local Files
--------------------    
    CentralSetup checks the directory where Central Point Anti-Virus for
    NetWare was installed (the default is C:\CPAVNET) on the administrator's 
    workstation for the latest versions of VSafe, VWatch, BootSafe, 
    CINSTALL.EXE, and CPDOS.CPS. It copies the updated files to the 
    network. Then, CentralSetup copies these updated files to the user's 
    local drive.

    If you have a newer version of any of these files, you can manually copy 
    the file to the Central Point Anti-Virus for NetWare directory on the
    administrator's workstation.


Sharing Windows Files on a Network
----------------------------------  
  If a workstation is running Windows over the network, the administrator 
  needs to add WNTSRMAN.EXE in the WIN.INI load= line for VSafe and VWatch.
  You should also add CPAVCGRP.EXE to the WIN.INI run= line to create the
  necessary Windows groups.

  Remember to add the appropriate pathnames before WNTSRMAN.EXE and 
  CPAVCGRP.EXE.


Free Disk Space Required upon Booting Your Computer
---------------------------------------------------  
  Users need at least 310 KB of free disk space on the boot disk of their
  workstations for CentralSetup to function properly.


    
==============================================================================  
			CHANGES TO THE DOCUMENTATION

  
Central Point Anti-Virus for NetWare Configuration 
--------------------------------------------------
The configuration file, CPAVNET.CFG, is in the SYS:SYSTEM\CPAVNET
directory, not in the SYS:SYSTEM directory as mentioned in the documentation.

To improve security, the ability to configure Central Point Anti-Virus 
for NetWare has been changed to require Supervisor Equivalent security when
you are using v2 of Central Point Anti-Virus for NetWare in Windows. 
The v1.1 programs did not have this security feature.


CPSCAN Options  
--------------
  In the Central Point Anti-Virus for NetWare manual on page 71, the 
  CentralSetup options are incorrect. The documentation states that there 
  are two options: "Rules-Based Scan" and "Use Virus Analyzer." Virus 
  Analyzer is the only optional scanning method. 
  
  The local scanning software that runs on users' workstations employs a 
  signature-based scanning method to detect infected files. In addition 
  to this signature-based method, you can specify an additional scan using 
  the virus analyzer. The virus analyzer uses an expert system that looks 
  at files to see if they match an infected file profile. This technique is
  particularly useful for finding new and unknown viruses; however, it does 
  require additional scanning time.

VSafe Setup
-----------
  In the VSafe setup section of the Central Point Anti-Virus for NetWare
  manual on page 68, the option "General Write Protection" is 
  described incorrectly. When selected, this option displays a dialog box 
  that notifies the user any time the system attempts to write
  to the hard disk. The user then has the option of cancelling the write or
  allowing it to continue.

Priority Status for CentralAlert and Central Point Anti-Virus for NetWare
--------------------------------------------------------------------------  
  Both CentralAlert and Central Point Anti-Virus for NetWare show the 
  priority status as a series of numbers. This table shows the 
  correspondence between priorities and the numbers you see on the screen:

	1       Critical
	2       Major
	3       Minor
	4       Informational
	5       Priority unknown
  
  See page 73 of the Central Point Anti-Virus for NetWare manual for 
  information on assigning priorities to alert conditions.


AIO_READ.ME file
----------------  
  In the CentralAlert manual on pages 22-23, there are references made to 
  the AIO drivers README file as both AIO_READ.ME README.AIO. The proper 
  name of the file is AIO_READ.ME. The text of the file is included below
  for your convenience.
			   
			   AIO Drivers README file

	Asynchronous input/output (AIO) drivers enable third-party 
	asynchronous adapters to be used with NLM products. 
	These adapters provide a wide range of performance and 
	packaging variations depending upon your needs.

	These drivers have been tested and certified under Novell Labs
	Independent Manufacturer's Support Program certification.  
	However, Novell Inc. does not guarantee or support these 
	drivers.  Please contact the appropriate vendor if you have
	problems.

	Installing AIO Drivers
	----------------------
	The product manual describes AIO driver installation 
	according to the needs of Central Point Anti-Virus for NetWare.
	In general, the driver files need to be placed in the SYSTEM 
	directory on the server and then loaded by typing 
	commands at the server console or by using automatic commands
	from within the AUTOEXEC.NCF file.
	
	The driver (AIOCOMX.NLM) is loaded after AIO.NLM (provided 
	with Central Point Anti-Virus for NetWare) using the command 
	line parameters (such as I/O ports and interrupts) as described 
	in the product documentation.

	The driver prompts you for needed information (or uses the
	defaults) if the appropriate information is not entered at the 
	command line. The driver gives a message indicating correct 
	or incorrect loading. When you have successfully loaded the 
	driver, you can then load the Master NLM for Central Point 
	Anti-Virus for NetWare.

	It is recommended that the driver be loaded manually at first
	to verify the parameters needed. Once the correct operation is
	achieved, the commands can be incorporated in the AUTOEXEC.NCF
	file to allow automatic loading whenever the server is started.


	Example:
	To load the AIOCOMX driver to provide COM1 use the following
	commands:

		load aio
		load aiocomx
	
	In this case AIOCOMX uses the defaults for COM1 (I/O port 3f8,
	Interrupt 4).  If you wish to use other settings, enter the new settings
	at the comand line as in the following example:

		load aiocomx port=2f8 int=3

	This example uses the hardware at the specified address with the new
	interrupt.

	Once you have verified that the driver works by using it with
	the NLM product, you should place the load statement into
	the AUTOEXEC.NCF. When the server is started the driver 
	should be automatically loaded. Be sure that you place the load 
	command after AIO.NLM is loaded.

	Each board using a particular driver must have a unique board
	number.  AIO requires that boards be numbered starting from
	zero, and that all boards using an individual driver have
	contiguous numbers.  

	Example:

		load aiocomx port=2f8 int=4 

	This will set the board number for this invocation of the driver
	to zero.  Normally COM2 would be assigned the board 
	number 1 (leaving 0 for COM1).  
       
		    AIOCOMX.NLM Version 1.02
			     January 9 1992

	This driver enables AIO applications to use the built-in
	serial ports on the server or those of an add-on adapter that
	emulates standard serial ports.  Up to four ports can be
	supported.  Each port requires its own interrupt. 

	Load directives:

	1) Type 'load aiocomx' to load COM1 at port=3f8, int=4 (if the
	    hardware is available) and loads COM2 at port=2f8, int=3 (if 
	    the hardware is available).

			       OR

	2) Type 'load aiocomx {optional parameters}' to customize 
	    the driver according to the options described in the help screen.

	    The optional load parameters and their descriptions are listed
	     below:

	     PORT=W,  where W is the hexadecimal port address at
			      which the device resides.

	      INT=X,    where X is the interrupt number assigned to the
			       particular device port.
			   AIO Drivers README file

	Asynchronous input/output (AIO) drivers enable third-party 
	asynchronous adapters to be used with NLM products. 
	These adapters provide a wide range of performance and 
	packaging variations depending upon your needs.

	These drivers have been tested and certified under Novell Labs
	Independent Manufacturer's Support Program certification.  
	However, Novell Inc. does not guarantee or support these 
	drivers.  Please contact the appropriate vendor if you have
	problems.

	Installing AIO Drivers
	----------------------
	The product manual describes AIO driver installation 
	according to the needs of Central Point Anti-Virus for NetWare.
	In general, the driver files need to be placed in the SYSTEM 
	directory on the server and then loaded by typing 
	commands at the server console or by using automatic commands
	from within the AUTOEXEC.NCF file.
	
	The driver (AIOCOMX.NLM) is loaded after AIO.NLM (provided 
	with Central Point Anti-Virus for NetWare) using the command 
	line parameters (such as I/O ports and interrupts) as described 
	in the product documentation.

	The driver prompts you for needed information (or uses the
	defaults) if the appropriate information is not entered at the 
	command line. The driver gives a message indicating correct 
	or incorrect loading. When you have successfully loaded the 
	driver, you can then load the Master NLM for Central Point 
	Anti-Virus for NetWare.

	It is recommended that the driver be loaded manually at first
	to verify the parameters needed. Once the correct operation is
	achieved, the commands can be incorporated in the AUTOEXEC.NCF
	file to allow automatic loading whenever the server is started.


	Example:
	To load the AIOCOMX driver to provide COM1 use the following
	commands:

		load aio
		load aiocomx
	
	In this case AIOCOMX uses the defaults for COM1 (I/O port 3f8,
	Interrupt 4).  If you wish to use other settings, enter the new settings
	at the comand line as in the following example:

		load aiocomx port=2f8 int=3

	This example uses the hardware at the specified address with the new
	interrupt.

	Once you have verified that the driver works by using it with
	the NLM product, you should place the load statement into
	the AUTOEXEC.NCF. When the server is started the driver 
	should be automatically loaded. Be sure that you place the load 
	command after AIO.NLM is loaded.

	Each board using a particular driver must have a unique board
	number.  AIO requires that boards be numbered starting from
	zero, and that all boards using an individual driver have
	contiguous numbers.  

	Example:

		load aiocomx port=2f8 int=4 

	This will set the board number for this invocation of the driver
	to zero.  Normally COM2 would be assigned the board 
	number 1 (leaving 0 for COM1).  
       
		    AIOCOMX.NLM Version 1.02
			     January 9 1992

	This driver enables AIO applications to use the built-in
	serial ports on the server or those of an add-on adapter that
	emulates standard serial ports.  Up to four ports can be
	supported.  Each port requires its own interrupt. 

	Load directives:

	1) Type 'load aiocomx' to load COM1 at port=3f8, int=4 (if the
	    hardware is available) and loads COM2 at port=2f8, int=3 (if 
	    the hardware is available).

			       OR

	2) Type 'load aiocomx {optional parameters}' to customize 
	    the driver according to the options described in the help screen.

	    The optional load parameters and their descriptions are listed
	     below:

	     PORT=W,  where W is the hexadecimal port address at
			      which the device resides.

	      INT=X,    where X is the interrupt number assigned to the
			       particular device port.

