 
                      ===================================
                      |                                 |
                      |         LAN Auditor (tm)        |
                      |                                 |
                      |           README FILE           |
                      |                                 |
                      |          Version 2.11           |
                      |                                 |
                      ===================================
 
 
                           Horizons Technology, Inc.
                          Software Products Division
                               3990 Ruffin Road
                           San Diego, CA 92123-1826
                                (619) 292-8320
 
 
    Copyright 1990-1992 (c) Horizons Technology, Inc.  All rights reserved.
 
 
     Installation
     ==================================================================
 
     1.  Summary.
 
         Two LAN Auditor modules can be installed:
 
         a)  The Database module.  This provides a user-friendly
             interface to your PC resource data.  This module can
             be installed to any valid network or local drive.
             The drive must have at least five megabytes of available
             space depending on the installation options selected.
             You will probably need more as the PC resource
             database grows.
 
         b)  The Auditor (tm) module.  This consists of the files
             AUDITOR.EXE, AUDADMIN.EXE, and AUDDISP.EXE which
             perform the workstation audit.
 
     2.  Steps to be taken before installation.
 
                                  IMPORTANT!!!
 
         a)  YOU MUST BE LOGGED INTO THE NETWORK AS A SUPERVISOR OR A
             USER WITH FULL SUPERVISORY RIGHTS TO THE SERVER WHERE THE
             PROGRAM WILL BE INSTALLED!  ATTENTION:  YOU MUST BE LOGGED
             INTO (NOT ATTACHED TO) THE SERVER WHERE THIS PROGRAM WILL
             BE INSTALLED.
 
         b)  The Auditor module can only recognize valid DOS drive
             designators and paths.  It does not recognize file
             volume identifiers (such as NetWare volume names like
             SYS).
 
         c)  For LAN Auditor version 2.0 or 2.01 users you can
             install this new version in same location as the
             2.0 version and retain all of your existing data.
             For version 1.x users you must install this version
             in a new location.
 
     3.  Installation steps.
 
                                  IMPORTANT!!!
 
         a)  DO NOT COPY FILES FROM THE DISTRIBUTION DISKS TO THE
             INSTALLED LOCATION.  THE FILES ARE COMPRESSED AND CAN
             ONLY BE DECOMPRESSED AND PROPERLY INSTALLED USING THE
             INSTALL PROGRAM.
 
         b)  WHEN INSERTING A REFERENCE TO THE AUDITOR MODULE IN
             A LOGIN SCRIPT OR PROFILE (FOR ANY OF THE SUPPORTED
             NETWORKS), YOU MUST MAKE CERTAIN THAT THE AUDITOR
             MODULE IS:
 
                * IN THE DOS PATH OR HAS A SEARCH MAPPING TO
                  ITS INSTALLED LOCATION (AND THIS MUST OCCUR
                  IN THE LOGIN SCRIPT OR PROFILE PRIOR TO
                  THE INVOCATION OF THE AUDITOR MODULE), OR
 
                * MODIFY THE LOGIN SCRIPT OR PROFILE SO THAT
                  ITS INVOCATION INCLUDES AN EXPLICIT DOS PATH.
 
         c)  Insert the disk labeled "Disk #1" into a floppy drive and
             change to that drive.
 
         d)  Type "INSTALL" and press <Enter>.
 
         e)  Follow the instructions on the screen.
 
         f)  You may view this file at any time from within the INSTALL
             program by pressing the function key "F1".  Once it appears
             on the screen, you may also print it by pressing "P".  The
             INSTALL program will print it to the LPT1: port.
 
     4.  Multi-user notes.
 
         a)  You DO NOT have to the execute the DOS SHARE command
             to use program in multi-user mode.  Each workstation
             that accesses the Database module does have to run
             the NetBIOS protocol (its invocation varies with
             each network operating system).
 
     5.  Post-installation notes.
 
         * All Networks
 
         a)  Identification of networked workstations is based on the
             network card identifier.  This identifier is automatically
             determined.  For non-networked workstations, a DOS
             environment variable, AMACH, must be present and set to
             a unique value (such as a property tag number or a name).
             For example, type
 
                          SET AMACH=12345
 
                                or
 
                          SET AMACH=Pat's computer
 
             from the DOS prompt before auditing the workstation.
             It is recommended that this DOS command be inserted into
             the AUTOEXEC.BAT of the workstation.  Refer to the User's
             Guide for details on this and other alternative methods
             of tagging non-network workstations.
 
         * Novell NetWare
 
         a)  During LAN Auditor installation, the files AUDITOR.EXE,
             AUDADMIN.EXE, & AUDDISP.EXE are installed.  The AUDITOR.EXE
             file should be referenced in the system login script, in
             order to gather data from every workstation as a login
             occurs, or in the personal login scripts of users whose
             workstations you wish to audit.
 
         b)  You may want to install the Auditor module in Z:\PUBLIC
             and have the Auditor data stored to another directory.  If
             so, the following reference should be made in the login
             script (presuming the Z:\PUBLIC has been made a search
             mapping prior to this line)
 
                          #AUDITOR /OY:\SHARED\LADATA
 
             where all users MUST have all rights to the the directory
             Y:\SHARED\LADATA.  The users need only read-only rights to
             the Auditor module files in Z:\PUBLIC.

             Note: Type the #AUDITOR /O[path] and do not use LOGIN.INC
				       as noted in the manual.

         * Banyan VINES
 
         a)  During LAN Auditor installation, the files AUDITOR.EXE,
             AUDADMIN.EXE, & AUDDISP.EXE are installed.  The
             AUDITOR.EXE is referenced in the login profile using a
             POSTLOGIN command. It should be referenced in the most
             common login profile, in order to gather data from every
             workstation as a login occurs, or in the personal login
             profile of users whose workstations you wish to audit.
 
         b)  For multi-user access to the Database module, NetBIOS
             must also be loaded on the lock manager workstation and
             each workstation running the Database module (it is NOT
             required for workstations running the Auditor module).
             There are two methods to set up NetBIOS.  You can use
             the PCCONFIG program to specify that the NetBIOS software
             is loaded at login time, or you can execute the PCNETB
             command from the DOS prompt.  Refer to you VINES
             documentation for details.
 
             The next step is to add a VINES NetBIOS service using
             the MSERVICE utility.  Again, refer to your VINES
             documentation.
 
             Once NetBIOS is loaded, a NetBIOS server-based service
             must be established.  To set up the service enter
 
                        SETNETB netb@group@organization
 
         * Microsoft LAN Manager
 
         a)  During LAN Auditor installation, the files AUDITOR.EXE,
             AUDADMIN.EXE, & AUDDISP.EXE are installed.  In order to
             gather data from every workstation as a login occurs
             a reference to the AUDITOR.EXE must be made.  For Enhanced
             workstations, this reference should be in a common login
             script to collect audit data on all of the workstations, or
             in a user login script for an individual user (for Basic
             workstations, you will have to insert a reference to the
             Auditor module in the AUTOEXEC.BAT file).
 
             As an example, the login script might appears as:
 
                          AUDITOR /OY:\SHARED\LADATA
 
             where all users MUST have all rights to the the directory
             Y:\SHARED\LADATA.
 
         b)  LAN Auditor can be installed on LAN Manager v. 1.3 (or
             equivalent) networks.  However, all changes to the
             network login scripts must be made as described in
             Appendix A of the LAN Auditor User's Guide.  In addition,
             path rights for installation directories will not be
             shown for these networks during installation.
 
 
     User's Guide
     ==================================================================
 
     1.  Release notes.
 
         a)  The DOS SHARE program DOES NOT have to be invoked
             to run the Database module for either single-user
             or multi-user access modes in most cases.  It is only
             necessary when running multiple instances of the
             DOS version of the Database module off a local
             hard disk.
 
     2.  Software Dictionary.

      	 The LAN Auditor software dictionary may be updated via either the 
         following procedures.

             a)  To identify an unknown file:

                 1. Select the machine record with the software
                    information to be modified.
                 2. To modify it, highlight the record and choose
                    MODIFY RECORD under EDIT on the main menu.
                 3. Hit the PAGE button and go to the SOFTWARE LIST screen.
                 4. Choose UNKNOWN for file types.
                 5. Go to the directory where the unidentified software
                    package is stored.  To select the package, double 
                    click or press shift+spacebar on the unknown file.
                 6. At the IDENTIFY SOFTWARE screen, enter the correct
                    manufacturer, package name, and version.  The box 
                    marked IDENTIFYING FILE needs to be marked when you are
                    identifying the primary file that runs the program.  
                    For example, COMMAND.COM is an identifying file for DOS, 
                    while FORMAT.COM and BACKUP.COM are only accompanying 
                    files.  The accompanying files are not needed to run DOS  
                    as an operating system.

               This will identify the package and allow you to update the 
               software dictionary.  

           b)  When LAN Auditor incorrectly identifies a software package:

               If an exact match for a software package was not found in
               the software database, LAN Auditor may identify a file as an
               approximate match.  

               To determine whether a file has been identified as an 
               approximate match, go to the software list screen.  Double 
               click or press shift+spacebar on the software package in 
               question to bring you to the file list screen.  If it has 
               been identified by an approximate match, there will be an 'a' 
               between the file name and file location; e.g., 
                  "COMMAND.COM  a  C:\DOS"  

               To identify the appoximate file, double click or press 
               shift+spacebar on the filename to display the identifying 
               package screen; see procedure a. above.



     Auditor Module
     ==================================================================

     1.  Release notes.
 
         a)  The Auditor module is compatible with the following
             network operating systems:
 
                       * Artisoft LANtastic 2.3
                       * AT&T StarLAN 3.4 & 4.x
                       * Banyan VINES 4.x & 5.x
                       * DEC Pathworks 4.x
                       * HP LAN Manager 2.x
                       * Microsoft LAN Manager 2.x
                       * Novell NetWare 2.1x & 3.x
                       * 3Com 3+Open 1.1
 
         b)  The root of the drive pointed to by the DOS environment
             variable COMSPEC is considered the boot drive for purposes
             of collecting the AUTOEXEC.BAT and CONFIG.SYS files for
             DOS 3.x.  For DOS 4.x & 5.x this information is provided
             to the Auditor module by DOS.  If for any reason this
             information is incorrect, the DOS environment variable
             ABOOT can be set to inform the Auditor module of the
             correct location.  The syntax is
 
                                 SET ABOOT=C:\
 
             where C:\ (or whatever is appropriate) represents
             the boot drive & directory.
 
         c)  Some non-standard disk partitions (created by third-party
             disk format products) are reported as "Unknown" followed
             by a value.
 
         d)  The Auditor module will not perform an audit when
             running in the DOS Compatbility box of OS/2 or from
             Windows 3.x.  It will simply issue a warning message
             and exit.
 
         e)  To view the AUDITOR.PRF preference file, type
 
                           AUDITOR /S /O <directory>
 
             where <directory> represents the location of the
             AUDITOR.PRF file.  Press the End key to see the last
             screen; this will show the selected preferences.
 
         f)  If any of one of the command line switches /H, /P,
             /R, /S, or /V is present, no AUDITOR.DAT file will be
             written and no audit will be performed.
 
         g)  If the HIMEM.SYS driver is used for extended memory,
             the available amount of extended memory is reported
             as 0.
 
         h)  To perform software audits during the logon process
             under Microsoft LAN Manager for Enhanced workstations,
             minimum of 420 KB of available RAM is needed prior to
             executing NET LOGON.
 
         i)  The command line switch /Z is used to perform a server
             audit.  In order to obtain a full software audit of
             the server, you MUST have all rights to all file server
             volumes and all rights to all directories on those
             volumes.

             You may want to do server audits when the network is not
             busy, as there will be conflicts when AUDITOR is doing a 
             server audit with files that are still open by other 
             software packages.

         j)  The Auditor module will collect information on
             hidden files & directories when performing a software
             audit of a local workstation's hard disk.
 
         k)  For diskless computers that boot off a file server,
             we recommend that the DOS environment variable ABOOT
             be set to indicate a valid boot location and that
             the APATH variable be set to "NO".  For example,
             you might set these variables in the AUTOEXEC.BAT
             file as follows.
 
                                 SET ABOOT=Y:\
                                 SET APATH=NO

     2.  Known limitations/problems.
 
         a)  Some older model Compaq Deskpro computers (with BIOS
             dated between late 1986 and early 1987) running
             under NetWare may not correctly perform the network
             audit.  We recommend that these machines be audited
             manually using /A /XNET command line switches (/A to
             collect the Machine id and /XNET to exclude the
             network information).  An alternative to using the
             /A switch is to include the DOS environment variable
             AMACH in the AUTOEXEC.BAT file.  AMACH is equivalent
             to the Machine id field & its purpose is to uniquely
             identify the machine in the LAN Auditor inventory
             database.

         b)  For Novell NetWare 2.x, the /O command line switch
             is required in order for the audit data to be written
             to disk when invoking the Auditor module from a
             login script.
 
         c)  The video adapter memory reported for values greater
             than 256 KB is reported as 256 KB.
 
 
     Database Module
     ==================================================================
 
     1.  Release notes.
 
                                  IMPORTANT!!!
 
         a)  IT IS RECOMMENDED (THOUGH NOT REQUIRED) THAT THE FILES
             & BUFFERS PARAMETERS IN THE CONFIG.SYS FILE BE SET TO
             AT LEAST 40.  ALSO, FOR BEST PERFORMANCE IT IS HIGHLY
             RECOMMENDED THAT THE DOS OR WINDOWS SMARTDRV DISK
             CACHING UTILITY BE LOADED & THE CACHE SIZE SET TO 2 MB.

         b)  Windows 3.0 version must run in standard or enhanced mode,
             not real mode.  This module will run in 2 MB of memory,
             though better performance can be obtained with 3 MB or
             more of memory.
 
         c)  Some non-standard disk partitions (created by third-party
             disk format products) are reported as "Unknown" followed
             by a value.
 
         d)  Digital Research's DR DOS 5.00 & 6.00 are fully supported
             for the Database module (both Windows and DOS versions).
 
         e)  The DOS SHARE program IS NOT REQUIRED to be loaded to
             run the Database module.
 
         f)  In the DOS version when using a mouse, the mouse cursor
             will at times change to the Greek letter sigma (d).
             This is a signal that the program is busy with an
             assigned task, and that no further work can be done
             until the mouse cursor returns to its normal form ([).
 
         g)  The "Refresh package" option under the Utilities menu
             is used to update ALL references in ALL machines to
             user-defined packages.  This options requires accessing
             every machine in the database and can take several minutes
             or longer to process (depending on the number of machines
             in the database).  It is recommended that this option
             only be invoked after all user-defined packages have
             been defined.
 
         h)  If for any reason the SUPERVISOR password is changed
             & forgotten, use the program SUPER.EXE to clear the
             password.  To run the program, type SUPER and press
             Enter.  The program will prompt for the location of
             the LAN Auditor database (for example, enter
             C:\LA\DATA).  

             SUPER.EXE is not normally installed and can be found on
             the INSTALL Disk (Disk #1).
 
     2.  Known limitations/problems.

         a)  In the Windows version when running a concurrent
             application which forces itself to the front (such
             as the Clock program), this at times can interfere
             with the appearance of the main screen.  Keeping
             such applications outside the borders of the main
             LAN Auditor window will prevent any screen refreshing
             problems.




     Release Notes 2.11
     ==================================================================

     1.  LAN Auditor for DOS.

         a)  In version 2.11 the DOS module will utilize the extended
             or expanded memory.  You need at least 2MB to run the DOS 
             Module, but we recommend 3MB or more. 

         b)  If an expanded memory (EMS) handler is installed, it must 
             follow the EMS 4.0 and VCPI specifications.  If yours is 
             not VCPI compatible, contact the manufacturer to upgrade to
             a newer version.

         c)  Microsoft's EMM386, included with DOS 5.0 and Windows 3.0,
             is VCPI-compatible, and can therefore be used with the DOS
             module of LAN Auditor.  However, the EMM386 NOEMS switch 
             effectively disables VCPI support, and therefore cannot be
             used.

         d)  When using HIMEM.SYS, we recommend setting a fairly large
             handle count, for example 127.  Insert the NUMHANDLES 
             parameter for HIMEM.SYS in your config.sys file.  
                (e.g., DEVICE = C:\DOS\HIMEM.SYS /NUMHANDLES=127)

     2.  International Date Format.

         a)  LAN Auditor now supports three types of date format.
             The first is Month/Date/Year, second is Date/Month/Year, and
             third is Year/Month/Date.  To choose between the different 
             formats, go to OPTIONS under the main menu and under Set
             Date Format.  A dialog box will allow you to 
             choose the preferred format.

             NOTE.  The BIOS date is unaffected.  Auditor will report what
                    is in memory, and therefore it will not differentiate 
                    between the formats.




     Release Notes 2.12
     ==================================================================

     1.  To run in multi-user mode, you no longer have to load 
	      NETBIOS and LM_TSR.EXE. LAN Auditor uses a general lock 
         manager, which replaces the TSR version of the lock manager.  
         In order for LAN Auditor to run in multi-user, install LAN  
         Auditor in Multi-User mode at installation.

     2.  The AUDITOR module will write the administrative information
         to the AUDITOR.INI file.
	 
     3.  The AUDITOR module for Banyan Vines network now include an 
         extra file called GETNIC.EXE.  Make sure this file is 
         copied if you decided to copy the AUDITOR module.

                             [ End of README File ]
