                            LANauditor
                           Version 3.00
                                 
                     Horizons Technology, Inc.
                         3990 Ruffin Road
                       San Diego, CA  92123
                 Technical Support: (619) 292-8320
                                 
                        September 29, 1993


This README file is organized into the following sections:

   I.   Installation
   II.  Auditor Module
   III. Console Database Module
   IV.  Database Convert Utility
   V.   Changes to the User's Guide
   VI.  Miscellaneous Release Notes

____________________________________

I. Installation
____________________________________

A. The following LANauditor files are provided in this release:

   LAD.EXE      -- The DOS model console database program.
   LAW.EXE      -- The Windows model console database program.
   SAMPLE.DAT   -- A sample database to demo.  To bring this
                   sample database into the console, rename
                   this file "AUDITOR.DAT", and perform an
                   inventory update on it.
   LACVT30.EXE  -- Database convert utility used to convert from 
                   LANauditor version 2.1x to version 3.0.
   WAUDITOR.EXE -- File name of the DOS auditor program in use.
   WAUDDISP.EXE -- Auditor module display routine.
   SAUDITOR.BV  -- Banyan VINES file server audit program.
   WAUDITOR.BV  -- Banyan VINES specific workstation auditor
                   program.
   SAUDITOR.LM  -- LAN Manager/NetBIOS file server audit program.
   WAUDITOR.LM  -- LAN Manager specific workstation audit program.
   AUDSPROC.EXE -- LAN Manager/NetBIOS server process.
   AUDITWFW.EXE -- Microsoft Windows for Workgroups workstation
                   audit program.
   AUDSPROC.NLM -- NetWare server process.
   SAUDITOR.NW  -- NetWare file server audit program.
   WAUDITOR.NW  -- NetWare specific workstation audit program.
   AUDITOS2.EXE -- OS/2 workstation audit program.
   AUDITOS2.SYS -- OS/2 workstation device driver.
 
B. Steps to be taken before installation.

            IMPORTANT!!!
 
   1. 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.
 
   2. 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).
      Also, if you have any copies of the LANauditor v3.0
      field test (Beta) versions on your system, you should
      delete any field test files and/or directories that may
      exist on your system before continuing.
 
   3. For LANauditor version 2.11 and 2.12x users, you can 
      install this new version in the same location and retain all
      of your existing data.  For version 1.x and 2.0x, users you
      must install this version in a new location.
 
C. Installation steps.
 
            IMPORTANT!!!

   1. 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.

   2. 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.
         (FOR EXAMPLE Z:\PUBLIC\WAUDITOR.EXE)

   3. Insert the disk labeled "Disk #1" into a floppy drive and
      change to that drive.

   4. Type "INSTALL" and press <Enter>.

   5. Follow the instructions on the screen.

   6. 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.

D. To run the Console Module programs LAD.EXE or LAW.EXE.

   1. You have to execute the DOS SHARE command
      to use the program in multi- or single-user mode.

E. Post-installation notes.

   1. All Networks

      a. Identification of networked workstations is based on the
         combination of network card identifier and the Machine ID
         field in the database.  The NIC ID field is automatically
         determined, while the Machine ID field is user defined.  
         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.

   2. Novell NetWare

      a. The WAUDITOR.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)

               #WAUDITOR /OY:\SHARED\LADATA

         where all users MUST have read and write privileges to
         the directory Y:\SHARED\LADATA.  The users need only 
         read-only rights to the Auditor module files in 
         Z:\PUBLIC.

   3. Banyan VINES

      a. WAUDITOR.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.
         If you need to execute more than one program during 
         login, then you need to create a batch file.  POSTLOGIN
         would then call this batch file to run WAUDITOR and 
         other programs.
 
      b. The call for WAUDITOR must come after the set drive 
         command to gain access to WAUDITOR.EXE.  The users must 
         have Read and Execute privilege for the WAUDITOR.EXE 
         directory.  They need MODIFY privileges (Read, Write, and
         Execute) for the WAUDITOR output directory.

   4. Microsoft LAN Manager and other NetBIOS networks

      a. WAUDITOR.EXE must be referenced in the login profile or a 
         common batch file.  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 
         redirectors workstations, you will have to insert a 
         reference to the Auditor module in the AUTOEXEC.BAT 
         file).  As an example, the login script might appear as:

               AUDITOR /OY:\SHARED\LADATA

         where all users MUST have read and write privileges to
         the directory Y:\SHARED\LADATA.

      b. LANauditor can be installed on LAN Manager v1.3 and 
         higher (or equivalent) networks.  However, all changes
         to the network login scripts must be made as described 
         above.  In addition, path rights for installation
         directories will not be shown for these networks during 
         installation.

F. OS/2 installation.

   1. To audit OS/2 PC's you need to copy the file WAUDITOR.SYS 
      from the AUDITOR module directory to the local hard drive 
      of the OS/2 workstation.

   2. Modify the CONFIG.SYS to add two lines after the SET PATH 
      and SET LIBPATH.  Add the two lines as follows.  

            IOPL=YES
            DEVICE=C:\OS2\WAUDITOR.SYS

      You have to reboot for the changes to take place.

G. MAC installation.    

   1. Take the Mac Auditor diskette and copy the contents into
      the CONTROL PANEL folder.  

   2. Reboot the computer and you should be able to see the 
      LANauditor ICON appear during boot up process.  The
      Mac Auditor loads as an extension.

   3. The Mac Auditor is invoked by the combination of the APPLE
      key and an alphabet key.  This will run the audit and save
      the information to the specified location that is defined
      in the Mac Auditor console.

____________________________________

II. Auditor Module
____________________________________

A. Release notes.

   1. The Auditor module is compatible with the following
      network operating systems:

      *  Artisoft LANtastic 2.3
      *  AT&T StarLAN 3.2 & 4.x
      *  Banyan VINES 4.x & 5.x
      *  DEC Pathworks 4.x
      *  HP LAN Manager 2.x
      *  IBM LAN Server 1.3 +
      *  Microsoft LAN Manager 2.x
      *  Novell NetWare 2.1x, 3.x & 4.0
      *  Microsoft Windows for Workgroups 3.1
      *  3Com 3+Open 1.1

   2. 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.

   3. Some non-standard disk partitions (created by third-party
      disk format products) are reported as "Unknown" followed
      by a value.

   4. The Auditor module will not perform an audit when
      running in the DOS Compatibility box of OS/2 or from the 
      DOS box of Windows 3.x.  It will simply issue a warning 
      message and exit.

   5. If any of one of the command line switches /H, /P,
      /R, /S, or /V are present, no AUDITOR.DAT file will be
      written and no audit will be performed.

   6. If the HIMEM.SYS driver is used for extended memory,
      the available amount of extended memory is reported as 0.

   7. To perform software audits during the logon process
      under Microsoft LAN Manager for Enhanced workstations, a
      minimum of 420 KB of available RAM is needed prior to
      executing NET LOGON.

   8. The file SAUDITOR.EXE is used to perform a server
      audit.  In the Auditor module directory you must first
      rename the appropriate files as an "EXE" file.  (".BV" is
      for Banyan VINES, ".NW" is for NetWare, and ".LM" is for 
      LAN Manager and other NetBIOS Networks).  For NetWare 3.x
      and NetBIOS networks you must install a server process to
      collect information.  In order to obtain a full software
      audit of the server, you MUST have all rights to all 
      file server shared services and all of their directories.

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

      a. For NetWare 3.x servers:  First copy the AUDSPROC.NLM
         into the SYS:SYSTEM directory and load the NLM before
         running the SAUDITOR command.
         Note: There is no warning message if the NLM is
               not loaded on the server.  When you run
               the SAUDITOR without the NLM, it will not 
               run the audit or create an AUDITOR.DAT.

      b. For LAN Manager and NetBIOS servers:  First copy the
         AUDSPROC.EXE into the SERVICES directory of the server
         and edit the LANMAN.INI to add reference to the
         AUDSPROC.EXE file.
               SRVSERVICES = <existing services>, LANAUDITOR
         and
              [Services]
              ..
              ..
              LANAUDITOR = SERVICES\AUDSPROC.EXE

         You must then reboot the server to start the 
         LANAUDITOR service.  The SAUDITOR must be 
         performed from an enhanced workstation.  
         LAN Manager/X and DEC Pathworks will not support 
         any server audit.

   9. The Auditor module will collect information on hidden files
      and directories when performing a software audit of a local
      workstation's hard disk.

   10. 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

B. Known limitations/problems.

   1. Server process (i.e., AUDSPROC.NLM) data collection
      problems have been reported with some NetWare 4.0
      configurations.  The next maintenance release of 
      LANauditor will address these problems.

   2. The Auditor Module will not pick up all Video Card Memory.
      On some cards it will only track 256K of memory.

   3. The Auditor Module is 90% correct in determining which
      CPUs are "SX" or "DX" chips.  On some Hardware, the Auditor
      Module will incorrectly identify the SX or DX designation.

   4. The following modifications to DEC Pathworks will be
      provided in the next maintenance release of LANauditor:
      a. Save DECNet node name to machine name (in addition to
         primary login).
      b. Save DECNet address to NIC configuration field.
      c. Display Network type as DEC Pathworks rather than 
         LAN Man.
      d. Display correct Pathworks version.
      e. Display Machine Class for DEC machines rather than
         "IBM Clone".

   5. 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 LANauditor inventory
      database.

   6. 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.

   7. Mac Auditor compatibility problems have been reported
      with some Macintosh SE computers.  These problem will
      be addressed in the next maintenance release.

   8. There is a NetWare incompatibility with OS/2 version
      1.3.  If you are using OS/2 version 1.3 with NetWare,
      you need to upgrade your OS/2 to be able to schedule
      an OS/2 workstation audit.

   9. If you are having trouble auditing IPXODI driver
      workstations and you have NET.CFG and/or SHELL.CFG in
      the root of the boot drive, you need to relocate the
      NET.CFG and/or SHELL.CFG file to the \NETWARE
      directory.  This inconvenience will be corrected in
      the next maintenance release.

____________________________________

III. Console Database Module
____________________________________

A. Release notes.

            IMPORTANT!!!

   1. 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.

   2. 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.

   3. Some non-standard disk partitions (created by third-party
      disk format products) are reported as "Unknown" followed
      by a value.

   4. The DOS SHARE program IS REQUIRED to be loaded to run
      the Console Database module.

   5. In the DOS version when using a mouse, the mouse cursor
      will at times change to the Greek letter sigma 
      representing an hourglass.  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.

   6. If for any reason the SUPERVISOR password is changed
      and 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 LANauditor database (for example, enter
      C:\LA\DATA).  

      SUPER.EXE is not normally installed and can be found on
      the INSTALL Disk (Disk #1).

B. Known limitations/problems.

   1. 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
      LANauditor window will prevent any screen refreshing
      problems.

____________________________________

IV. Database Convert Utility (LACVT30.EXE Program)
____________________________________

If the convert program stops because of an error, there are 
some steps you can take to convert your database.  The format 
of the LACVT30 program is as follows:

   LACVT30 [opts] src dest 

where the three fields are,

   src    - The full path to where the LANauditor 2.1
            executables are located.

   dest   - The full path to where the LANauditor 3.0
            executables are located.

   opts are as follows:

   -H     - Shows the format, "LACVT30 [opts] src dest" 

   -G     - Ignore errors

   -Rs    - Remove source directory when done

   -Cx    - Put 'x' char in rec

   -I str - Include only subsystems in 'str'.  This will convert 
            only the subsystems in the 'str' string.  The
            allowable subsystems are given below.
               M - Machines      E - Exceptions
               L - Logins        S - Software
               Q - Queries       D - Software dictionary
               A - Admin         C - Collection paths
               P - Preferences   B - Hw+Sw Labels 
            Examples:
               -I d   - Will only convert the software dictionary.
               -I ms  - Will only convert machine records and
                        their software.

   -X str - Exclude subsystems in 'str', this will skip any 
            subsystems in the 'str' string.  Examples:
               -X s   - Will not convert the software part 
                        of a machine record.
               -X qa  - Will not convert queries or admin records.

   -Q     - Quiet mode, will not write any output to the screen.

   -G     - Go mode, this will by-pass any errors and convert as 
            much of the 2.1 database as possible.

   -Rs    - This will remove all the files in the source directory
            if there were NO errors during the convert. Any
            skipped errors like the -G option will cause this
            option not to run.

   -Cx    - Character 'x' is inserted as the first character in
            the machine id for every converted machine record.  

____________________________________

V. Changes to the User's Guide
____________________________________

Please, make the following corrections to your LANauditor v3.0
User's Guide.

Page 35, Replace the Note under Installing the NetWare Server
   Process.  Replace:
      'Note: You can audit file server hardware without installing
       the server process ...'
   With:
      'Note: You cannot audit a NetWare 3.x file server without
       first loading the AUDSPROC.NLM from the server console.'

Page 43, Change Special Installation Topics, OS/2 Installation.
   From:
      'DEVICE=C:\OS2\WAUDITOR.SYS'
   To:
      'DEVICE=C:\OS2\AUDITOS2.SYS'

Page 161, Appendix B, Memory for DOS and OS/2 Machines Figure.
   Change:
      'Memory Map Codes  "." = Free Memory'
   To:
      'Memory Map Codes  "." = Possibly Available'

For NetWare Management System (NMS) users:
   There is currently a limitation in the NMS OLF Editor and
   Introducer that requires LANauditor to be loaded in the
   \NMS\BIN directory.
   Therefore, on page 45 of the User's Guide it should say
   that all *.EXE, *.DLL, and the entire \DATA subdirectory
   need to be reside in the \NMS\BIN directory.

____________________________________

VI. Miscellaneous Release Notes
____________________________________

A. The Auditor default software auditing screen cannot be replaced
   with the AUDITOR.SCR file as described in the manual.

B. The users, who are being audited, no longer need CREATE rights.
   There will be an initial AUDITOR.DAT of size 122 bytes made in 
   the Auditor module directory. 
   
C. When operating in multi-user mode, if the database is be
   accessed by another console, you may be told that a 'Record is
   Unavailable".  This is the characteristic multi-user buzy
   message.

D. If problems are encountered during inventory update (e.g.,
   power failure, or aborted process), the following file naming
   conventions are used to retain information for recovery.

   During inventory update the AUDITOR.DAT is renamed to 
   HTILA-XX.XXX, where XX.XXX will be AA.AAA, AA.AAB, AA.AAC ...  
   depending if there are other HTILA-XX.XXX files in that 
   directory.  If the update is successful, the HTILA-XX.XXX file 
   is deleted, otherwise the HTILA-XX.XXX file is left for 
   trouble shooting.  If the user went over the license limits 
   he can expand LAW/LAD then recollect this file to get the 
   missed records.  

   NOTE 1 - If a user cancels the update, the AUDITOR.DAT file 
   will be left as HTILA-XX.XXX.  The user can then copy it back 
   to AUDITOR.DAT to run inventory update on it.
   
   NOTE 2 - Since we use the rename function now initial start up 
   is much faster, but the user MUST have rename and create rights
   in the AUDITOR.DAT directory.

E. Query temp files.

   The query portion of LANauditor uses five temporary files when 
   it runs.  The location of these file can be set by the user.  
   The way LAW\LAD decides is:

   1. Check the env. variable LAQRYPATH; if not set,
   2. Check la.ini file for 'Qry Path='; if not set,
   3. Use the current directory.

   If the product was installed on a network drive, setting the 
   query path to a local drive should speed up the query and cut 
   down on the network traffic.



--- End of README.TXT File ---
