

                            InocuLAN Version 3.00
                Copyright 1992-1994 by Cheyenne Software, Inc

  Cheyenne Software, Inc.               TEL (516) 484-5110
  3 Expressway Plaza                    FAX (516) 484-3446
  Roslyn Heights, NY 11577              BBS (516) 484-3445
  USA                                   CompuServe:  GO CHEYENNE

  =======================================================================

  The following information is not included in InocuLAN's printed
  documentation.


NLM Installation
================
When installing InocuLAN, it is recommended that the workstation be
booted from a clean DOS System diskette.  Be sure to set FILES = 20 or
higher in the CONFIG.SYS file.  Next, run the InocuLAN installation 
program (INSTALL.EXE).


3.11 Servers
============
It is recommended that the Novell patch file REMFILFX.NLM be loaded when
running InocuLAN.

Installing Inoculan for Macintosh
=================================
An installation program is available to install Inoculan for Macintosh to your
Macintosh. To access this program, insert the InocuLAN for Macintosh diskette
into your floppy drive and click on the install icon. The program will
create folders and copy files as required to install InocuLAN for Macintosh.

To install InocuLAN for Macintosh from your network, copy the InocuLAN for
Macintosh disk to a folder on your server, then click on the install icon from 
the server folder.

Note: If you do not want to install the Virus Test Program on the workstations,
remove the program from the InocuLAN folder in the server. Disregard the
failure at the end of the installation that reads, "Couldn't open the source
file: 'Cheyenne:InocuLAN:VIRUS TEST PROGRAM' for reading".

If you choose to copy this file to the workstations, you must either disable
the InocuLAN NLM Real-time Monitor or set the File Selection/Mac File setting to
'No Scan'. Return this setting to its original state when InocuLAN for Macintosh
installations are complete.

This process can expedite installation in Macintosh workstations.


Upgrading from v1.1 v2.0 to v3.00
=================================
  The installation program will preserve the scheduled scan information,
  the users to be excluded from enforcement, and the notification
  configuration.


AVUPDATE: (This is available only to InocuLAN network users)
=========
  AVUPDATE may be executed in a quiet mode by adding the parameter /Q to
  the AVUPDATE command in the System Login Script.  When loaded in the quiet
  mode, AVUPDATE will not prompt the user with the message:  "Check Local
  InocuLAN Files Against Server Files <Y/N>?", but will still automatically
  check (and update if necessary) the InocuLAN files. 
  
  In order to update the Manager installed on the workstations, copy all 
  Manager files (except INSTALL.EXE and INSTALL.DAT) to the subdirectory 
  where the InocuLAN NLM was installed.  AVUPDATE will update the files to
  the subdirectory pointed to by the workstation's environment variable,
  INOCULAN.  AVUPDATE.DAT contains the list of files to be updated on the
  workstation.

  For example: if InocuLAN V3.00 NLM was installed in subdirectory
  SYS:\INOCULAN and InocuLAN Manager (previous version) was installed in
  subdirectory C:\INOCULAN:
        1. Copy the Manager files to SYS:\INOCULAN
        2. Check that the System Login Script has the line:
                #SYS:INOCULAN\AVUPDATE
           (Add parameter /Q if you want quiet mode.)
        3. Verify that the workstation's environment variable INOCULAN points to
           C:\INOCULAN.  You can do this by typing the AUTOEXEC.BAT to see that
           it contains the statement:
                SET INOCULAN=C:\INOCULAN
           (This should have been done by the previous version of Inoculan's
           Installation program).

  Note: When EXAMINE is run with the updated version, it will report that the
  signatures on the disk are invalid.  Answer YES to the question "Do you wish
  to create new signature files?". (Another alternative is to run the InocuLAN
  Manager and back up the Critical Disk Area).


SUPDATE
=======
1.  When supdate is executed and completes scanning the network for InocuLAN
    server information, the signature file version field may read 'XXXXXXX'
    for some servers. If this is the case, it is recommended that InocuLAN
    be reinstalled on the server, unloaded and reloaded.


ARCserve v4.0 Switch
====================
1. ARCserve v4.05 and v5.01G have been enabled with a command line switch to 
   allow InocuLAN to scan data on the host server before it is written to 
   tape or copied (Archiving operation).

   To obtain maximum speed and security for your backups, it is recommended
   that one of the InocuLAN switches be set when loading ARCserve.  To load
   ARCserve with the InocuLAN switch, type either of the following at the
   Server Console Screen:

        LOAD ARCSERVE INOCULAN_DELETE  - This will cause any viruses found
                                         to be deleted prior to backup.
        or

        LOAD ARCSERVE INOCULAN_RENAME  - This will cause any viruses found
                                         to be renamed with the .AVB extension
                                         prior to backup.


Alert Notification
==================
   To test that MHS, Pager, FAX and SNMP notification systems are set up 
   properly, a file called virtest.com has been included on the Server
   Diskette.
  
   InocuLAN will view this file as an infected file, but there are actually 
   no viruses present within the file. Load the IMMUNE TSR with the /ALL
   option.  Log into the InocuLAN server and then execute VIRTEST from the
   diskette by typing A:VIRTEST or B:VIRTEST. IMMUNE will detect the "Not a
   virus! Zerobug test" virus and report it to the server.  The NLM will then
   broadcast a message to the Supervisor and any users listed in the
   Broadcast Notification List. Next, it will send Alerts to personnel
   specified in the Alert System (either Default Configuration or Custom
   Configuration). The Alert Activity Log will hold the results.  


InocuLAN.NLM
============
1. Running with Memory Protection NLMs
   When running InocuLAN with memory protection utilities such as Novell's
   PROTECT or Nu-Mega's NET-check, InocuLAN must be loaded prior to loading
   the memory checking utilities.  In addition, InocuLAN should be unloaded
   only after unloading the memory checking utilities.

2. File Server Console Message 'Loader cannot find public symbol: MakeAlert1'
   If this message is displayed on the server console after InocuLAN.NLM is 
   loaded, unload ALERT.NLM at the server console and then unload ALBUILD.NLM.
   Verify that Alert version 2.x has been installed, then reload both Alert
   and InocuLAN.

3. InocuLAN server scanning records are automatically purged at an interval 
   defined in the PURGE.DAT file. This file specifies an interval (in days).
   Scanning records older than the the interval set by the PURGE.DAT file
   are purged. 

   The default interval is 90 days.

   The interval can be changed by editing the PURGE.DAT file 
   (using an unformatted text editor such a DOS's EDIT command)
   to specify the interval desired.

4. Real-time scanning of Macintosh files is effective only on outgoing files
   on NetWare 4.01 servers.

5. NetWare SFTIII Servers
   InocuLAN can only be loaded from the 'MSEngine'. If you experience
   difficulty loading InocuLAN or any of its related NLM's using the
   'LOAD INOCUCMD' command, load the following NLM's manually in the
   following order:

                WRAPxxxx.NLM
                ENGINE.NLM
                RTSCAN.NLM
                INOCUCMD.NLM


   Use the following table to determine the xxxx on WRAPxxxx.NLM:

   =============================================
   |  CLIB version  |  corresponding WRAP file |
   ---------------------------------------------
   |     3.11d      |       WRAPSFT3.NLM       |
   |     3.12       |       WRAP312.NLM        |
   |     3.12d      |       WRAP312.NLM        |
   |     3.12f      |       WRAP312F.NLM       |
   |     3.12g      |       WRAP312F.NLM       |
   =============================================

   These 'WRAP' files are in InocuLAN's home directory on the server.
   You can copy them to the SYSTEM directory on the server if you want to
   load them without having to especify the password.

6. Immediate Server Scanning and Alerts
   Alerts are not generated for immediate server scans entered at the
   server console. Consult the Activity Log or status screen for
   scan results.
              

GetBBS.NLM
==========
1. GetBBS.NLM is limited to the maximum speed rate that AIOCOMX shows when
   loading on the server.  That is, even if you connect a 9600 bps modem to
   the COM port on the server, if AIOCOMX rates the driver at 2400 bps, you
   cannot operate the modem at speeds higher than 2400 bps.
   This limitation comes from the UART chip used in implementing the COM port.
   If AIOCOMX reports the driver rated at 2400 bps, you have a 8250 or 16450 chip.
   If you want a higher speed, you will need to replace the 8250 or 16450
   UART with a 16550 UART. You can accomplish this by either changing the
   serial port board with one that has a 16550 UART (if you have serial port
   board) or changing the chip on the board (if the UART chip has a socket on the
   board).


2. GetBBS.NLM currently does not work on SFTIII servers.

