NConsole v1.03
--------------
The following notes are specific to the NConsole product (NCONSOLE.NLM,
formerly the N-Spector NLM, NSPECTOR.NLM, and the NCONSOLE.EXE client
utility) developed by Avanti Technology, Inc.


STATEMENT OF TITLE AND WARRANTY
-------------------------------
NConsole (the Software) was developed by and is the property of Avanti
Technology, Inc., of 13492 Research Boulevard, Suite 120-271, Austin,
Texas 78750 USA (Avanti).  All rights are reserved worldwide under both
Federal and International Copyright Laws.  No distribution or use of the
Software in any form relinquishes Avanti's claim to ownership and title
of the Software and concept.

Avanti warrants that the Software, when used as intended, is free from
known defects at the time it was distributed.  Should a defect become
evident, a detailed report of the conflict or anomaly should be provided
to Avanti.  Upon confirmation of the report, Avanti will endeavor to
correct the problem and make the correction available to registered users.
If a registered user encounters a defect within the initial ninety (90)
days following original receipt of the software which Avanti is unable to
rectify, the software may, at Avanti's sole discretion, be replaced or
arrangements made for a refund of the license fee.

Avanti shall not be required to insure the compatibility of the Software
with future revisions to the workstation or network operating system, nor
the hardware on which it may be installed.  Nevertheless, Avanti reserves
the right to enhance, update, or change the Software in ways which may
alter its specification, operation, performance, and/or support levels.
However, such a modification does not obligate Avanti to continue doing
so.  Registered users of the Software may be eligible for such revisions
provided they adhere to the terms of the Software License Agreement
accompanying the Software.


NOTICE OF DISCLAIMER
--------------------
AVANTI TECHNOLOGY, INC. SPECIFICALLY DISCLAIMS ALL OTHER WARRANTIES
IMPLIED OR EXPRESSED, INCLUDING BUT NOT LIMITED TO, IMPLIED WARRANTIES
OF MERCHANTABILITY AND ANY IMPLIED OR EXPRESSED WARRANTY FOR PARTICULAR
USE.  IN NO EVENT SHALL AVANTI TECHNOLOGY, INC. BE LIABLE FOR ANY LOSS
WHICH IS GREATER THAN THE LICENSE FEE PAID BY THE REGISTERED USER.
AVANTI TECHNOLOGY, INC. SHALL NOT BE LIABLE UNDER ANY CIRCUMSTANCES FOR
DIRECT, INDIRECT, OR SPECIAL DAMAGES RESULTING FROM THE USE OF THE
SOFTWARE (some of these exclusions may not apply in some states).


Overview:
---------
    The NLM collects, averages, accumulates, and tracks key server
    performance statistics.  Though providing much of the same
    information as found in Novell's MONITOR.NLM, the NLM presents
    the statistics in a far more informative fashion.  Moreover, it
    combines information from several different MONITOR screens into
    a single, easier to correlate screen and logs the statistics
    whenever peak levels have been reached/exceeded.  It also provides
    a scrolling, bargraph review of the CPU Utilization over the most
    recent 74 seconds and an option to lock the Console keyboard.

    The screen saver designed into the NLM provides more indepth
    information than that offered by Novell's MONITOR.NLM.  The screen
    saver is the CPU Utilization bargraph as presented on the main
    screen, updated every second and scrolled up/down the screen.
    The screen saver is automatically activated after a defined period
    of Server Console keyboard inactivity (five minutes by default and
    user defined through a command line option).  The screen saver can
    also be manually activated through the F10 key and deactivated by
    pressing most any key on the Server Console keyboard.

    After a period of load tracking, the NLM will automatically log
    the most recent statistics whenever the previous Peak is exceeded
    or, in certain cases, reached.  The NLM waits a minimum period of
    time (default = 48 minutes, definable through the LOAD=## command
    line option) then performs a load tracking algorithm to determine
    when the Server has become stable.  This algorithm requires that
    a period of activity occur without a new Peak being detected before
    the Server is considered stable.  The total amount of time required
    by default is approximately one hour.  Once the Server is considered
    stable, the automatic logging of statistics occurs whenever previous
    Peaks have been exceeded/reached.

    The most recent statistics are automatically written to the log
    file (SYS:SYSTEM\NCONSOLE.LOG) whenever the previous Peak level
    is exceeded for any statistic or if the tracked Peak is reached
    for any of the following critical statistics: Utilization,
    Dirty Blocks, I/Os Pending, No ECBs, or Unclaimed Packets.  The
    statistics can also be manually logged by pressing the F4 key
    (client or server).  Pressing the F5 key (client or server) will
    result in the log file being cleared, the most recent statistics
    being written to the new log file, and then all of the statistics
    (Current, Average, Peak, and Cummulative) being reset.  The F6 key
    can be used to clear the log file of all entries.

    The client (.EXE) program polls the NLM and displays the monitored
    statistics, without the overhead and hassle of using Novell's
    RCONSOLE or physically going to the Server to review the less
    informative statistics of the MONITOR NLM.


Usage:
------
    Copy the NCONSOLE.NLM file to the SYS:SYSTEM directory on the
    Server.  Type LOAD NCONSOLE at the Server Console prompt.  The
    NLM will load, initializing the screen and data, opening the
    log file (SYS:SYSTEM\NCONSOLE.LOG) or creating one if it does
    not exist, and then begin the statistical collection process.

    The NLM can either be unloaded manually by typing UNLOAD NCONSOLE
    at the Server Console prompt or by pressing the Escape key when
    the NLM's main screen is active.

    The client files (NCONSOLE.EXE & NCONSOLE.HLP) can be copied to
    any directory.  However, the client utility will only communicate
    with server(s) running the NLM.


                Documentation on Usage and Statistics
                -------------------------------------

                                Keys:
                                -----
    The following keys are supported on both the client and server:

        Escape - terminate operations/exit the program
        F1 | ? - activate on-line help system
                 (Note: '?' can also be used within the client on-line help
                        system to access additional levels of information.)
        F4     - log the current stats (Current, Average, Peak, & Cummulative)
        F5     - clear the log file, write the current stats to the new log
                 file, & reset all stats (Average, Peak, and Cummulative)
        F6     - clear/reset the log file (SYS:SYSTEM\NCONSOLE.LOG)

    The following keys are supported on the client (.EXE):

        Insert - change Servers (pressing Insert within the Attached Servers
                 list will bring up a list of the other Available Servers)

    The following keys are supported on the server (.NLM):

        F10    - activate screen saver mode
        Sh-F10 - activate screen saver mode and lock the Console keyboard


                        Command Line Options:
                        ---------------------
    The following command line options are supported on the client (.EXE):

        S=[server]    - [server] to poll and synchronize with
                        (def = LOGIN/Primary server if not on network drive)

    The following command line options are supported on the server (.NLM):

        LOAD=##       -	minimum time (## = minutes) to allow the NLM to load
                        balance prior to starting Peak logging (default = 48)

        LOCK          - lock the Server Console keyboard/screen once loaded
                        (the optional password, P=[pwd] below, or the
                        SUPERVISOR [NW3] / ADMIN [NW4] password is
                        required to release the lock)

        MONO          - use monochrome display attributes
                        (even if server has color adapter/monitor)

        NOPEAKS       - do not write peak alerts to the log file
                        (normal tracking and logging still occurs)

        P=[pwd]       - an optional password, in addition to the
                        SUPERVISOR [NW3] / ADMIN [NW4] password,
                        which can be used to unlock the keyboard

        RESET=##      - hour to automatically reset the avg, peak, and cumm
                        stats (0 - 23 hours [military], -1 disables reset)
                        (Note: 24 forces hourly reset.)

        TIMEOUT=##    -	minimum Server Console keyboard inactivity (minutes)
                        before the screen saver activates (default = 5 mins -
                        -1 disables the automatic screen saver.)


                                Statistics:
                                -----------
    Statistical information is collected every second, even if the
    screen saver is active or the NLM's main screen is not displayed.
    The Current levels represent activity over the last second.  The
    Average levels represent the median level since the last monitoring
    period began.  The Peak levels represent the highest activity
    reached at any point since the NLM was loaded or the statistics
    were last reset.  The Cummulative levels represent the
    accumulated activity since the last monitoring period began.

    (Note: By default, the NLM runs non-stop without the Average, Peak,
    and Cummulative values being reset.  The statistics can be reset
    manually or through the RESET=## command line option.)


                        CPU Utilization BarGraph:
                        -------------------------
    The bottom of the main screen and the scrolling part of the screen
    saver represent a CPU Utilization bargraph.  This graph is 5 lines
    deep and uses three types of indicators.  Each full height block
    represents 20% utilization increments.  Half height blocks indicate
    an additional 10 to 19% and an underscore reflects another 1% to 9%
    of utilization.  The bargraph scrolls from left to right and reflects
    the most recent 74 seconds of server activity.

                                SERVER STATS
                                ------------
        Utilization:
        ------------
        The NLM calculates Server CPU Utilization in a similar manner
        as that used by Novell's MONITOR and STAT NLMs.  The algorithm
        is based upon a calculation of idle process time (i.e., the
        number of times the server is polling processes for something
        to do versus actually performing tasks for active processes).

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        Connections:
        ------------
        The NLM tracks the number of active server Connections.  A
        server connection does not necessarily reflect an active user
        since NetWare does not immediately clear a connection upon
        logout.  Instead, it marks the connection as not in use (or
        'NOT-LOGGED-IN') while keeping it active in case the same or
        another user should login at the same workstation within a
        short period of time.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        Recv Buffers:
        -------------
        The NLM determines the number of Packet Receive Buffers which
        contain requests needing to be processed by NetWare.  Normally
        this value will remain at or near zero since the servicing of
        workstation requests are among the highest priority processes.
        However, excessive loads or disk bottlenecks can cause the
        number of requests which are queued to rise.

        If the number of queued requests reaches the Maximum Packet
        Receive Buffers (a setable parameter supporting a range of
        50 to 2000 with a default of 100), the server may Abend.
        While increasing the number of Recv Buffers may bring
        temporary relief to a problem, ideally the cause of the
        backlog of requests should be identified as the long term
        solution to this problem.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        Server Procs:
        -------------
        The NLM tracks the number of active Service Processes.  Service
        Processes are process threads which are available to service
        workstation requests.  As the Polling Process determines a
        workstation request has been received, it hands the packet off
        to a Service Process thread and a flag is set indicating that
        that Service Process is in use.  Once the Service Process finishes
        processing the packet, the in use flag will be reset and the
        Service Process is available to handle another workstation request.

        If a burst of workstation request packets are received or the
        type of requests delay the return of the Service Process, NetWare
        may allocate another Service Process (up to the Maximum Service
        Processes setable parameter which defaults to 20 and supports a
        range of 5 to 40).  If no Service Process is available for use
        and the maximum number have been allocated, packets will remain
        queued in the Packet Receive Buffers until they can be serviced.
        If an inbound packet arrives and there remain no more Packet
        Receive Buffers to accept the packet, the server may ABEND.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        Active Procs:
        -------------
        The NLM tracks the number of Active Processes (non-Service
        Processes) initiated by loaded NLMs, LAN and DSK drivers.  NetWare
        creates numerous processes or threads which it uses to manage
        activity, flush cache data, update directories, etc.  In addition,
        other NLMs, etc. will initiate processes or threads to perform
        their tasks.  Each active thread must be managed and requires
        some amount of processing time.

        This statistic represents those processes or threads which are
        active on the run queue.  Since threads can be put to sleep and
        awakened as needed, it is not unusual for this number to fluctuate
        randoming.  However, any large fluctuations should be suspect.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


                                FILE SYSTEM:
                                ------------
        Cache Buffer:
        -------------
        The NLM tracks the percentage of available Cache Buffers.  The
        Cache Buffer memory pool is what NetWare uses for file caching and
        loading NLMs.  An insufficient supply of Cache Buffers can cause
        file access degradation, NLM load failures, communications problems,
        and server lock-ups.  Novell recommends a Cache Buffer ratio of 50%
        or better be maintained for optimum integrity.  However, most
        consultants, trainers, and NetWire Sysops recommend 65% or more.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level (in this case, the minimum
        available Cache Buffers or peak Cache Buffer usage) since the NLM
        was loaded or the statistics were last reset.


        Open Files:
        -----------
        The NLM tracks the number of Open Files concurrently in use
        on the server.  While the maximum number of files which can be
        opened concurrently under NetWare is beyond a practical limit,
        each open file consumes memory and requires resource to manage.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        Dirty Blocks:
        -------------
        The NLM tracks the number of Dirty Blocks reported by NetWare.
        Dirty Blocks represent cache buffers which have been modified
        by a file write operation.  If the entire cache buffer has been
        modified or the specified delay has passed since the last change
        to the cache buffer (based upon the Dirty Disk Cache Delay Time
        setable parameter which defaults to 3.3 seconds and supports a
        range of 0.1 to 10.0 seconds), NetWare queues up the Dirty Block
        to the disk I/O subsystem for flushing to disk.

        NetWare will queue disk requests in an effort to organize the
        operations by their location on the disk.  This technique,
        called Elevator Seeking, allows multiple disk operations to be
        performed in a single sweep of the disk versus the forward/backward
        method of servicing disk requests in the order received.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        I/Os Pending:
        -------------
        The NLM tracks the number of Disk I/Os Pending reported by
        NetWare.  Disk I/Os Pending represent the number of physical
        disk requests which have been queued up.  NetWare will queue
        disk requests in an effort to organize the operations by
        their location on the disk.  This technique, called Elevator
        Seeking, allows multiple disk operations to be performed in a
        single sweep of the disk versus the forward/backward method of
        servicing disk requests in the order received.

        If this statistic climbs abruptly during file requests or
        accumulates a double digit average, it may indicate a disk I/O
        bottleneck.  In this case the Maximum Concurrent Disk Cache
        Writes setable parameter may need to be increased (a range of
        10 to 100 with a default of 50 is supported) in an attempt to
        further improve the efficiency of the Elevator Seeking logic.
        If such an adjustment fails to reduce the level, it may be
        wise to review the controller/drive combination in the server.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


        Dir Buffers:
        ------------
        The NLM tracks the number of Directory Cache Buffers reported
        by NetWare.  Directory Cache Buffers are allocated by NetWare
        to store directory information about frequently requested files.
        Directory Cache Buffers are not typically affected by normal
        application requests but can be skewed by large directory search
        requests (such as a multi-level subdirectory listing via NDIR
        or logging a NetWare volume through file management utilities).

        Once allocated, Directory Cache Buffers are not returned to the
        operating system.  Since their memory is taken from the Cache
        Buffer pool, allowing this value to grow unchecked can affect
        overall File Server efficiency.

        If level of Directory Cache Buffers jumps sporadically, it is
        most likely due to non-typical tasks such a backup and volume
        logging.  In these cases, it may be beneficial to impose a limit
        on the number of Directory Cache Buffers which can be allocated.
        This can be done through the Maximum Directory Cache Buffers
        setable parameter (supporting a range of 20 to 4000 with the
        default being 500).

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The last column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.


                                LAN I/O
                                -------
        Receive:
        --------
        The NLM tracks the number of packets received by the Server
        as reported by the Link Support Layer (LSL) drivers.  This
        count includes workstation requests, Routing Information
        Packets (RIP), Service Advertising Packets (SAP), and any
        other packets which were sent to the Server as requests,
        informationally, or to be forwarded.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


        Transmit:
        --------
        The NLM tracks the number of packets transmitted by the Server
        as reported by the Link Support Layer (LSL) drivers.  This
        count includes service replies, Routing Information Packets
        (RIP), Service Advertising Packets (SAP), and any other
        packets which the Server responded to or forwarded.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.

        Routed:
        -------
        The NLM tracks the number of packets routed by the Server
        as reported by the Link Support Layer (LSL) drivers.  This
        count includes requests intended for other servers, replies
        from other servers for workstations on this server network,
        and any other packets which the Server forwarded.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


        No ECBs:
        --------
        The NLM tracks the number of Event Control Block (ECB)
        Failures as reported by the Link Support Layer (LSL) drivers.
        ECBs are used to manage the transmission and receipt of
        network packets.  ECB failures indicate request (transmit
        or receive) which could not be serviced.  ECB Failures
        should not occur except in situations of extreme network
        load or physical layer problems.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.

        Unclaimed Packets:
        ------------------
        The NLM tracks the number of Unclaimed Packets as reported
        by the Link Support Layer (LSL).  Unclaimed Packets represent
        packets which were received by the server but never processed
        by a driver or NLM.  This can indicate receipt of packets
        which are not expected or contain unexpected contents.
        Unclaimed Packets should not occur except in situations of
        extreme network load or physical layer problems.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


                                FILE REQUESTS
                                -------------
        Open/Create:
        ------------
        The NLM tracks the number of workstation requests to Open or
        Create a file as reported by NetWare.  In most cases, Open
        requests can be satisfied by information already stored in
        the Directory Cache Buffers.  However, Creates represent
        physical disk I/O since the file does not exist or will be
        recreated if the file does exist.

        NetWare will queue disk I/O requests in an effort to organize
        the operations by their location on the disk.  This technique,
        called Elevator Seeking, allows multiple disk operations to be
        performed in a single sweep of the disk versus the forward/backward
        method of servicing disk requests in the order received.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


        Delete:
        -------
        The NLM tracks the number of workstation requests to Delete
        a file as reported by NetWare.  NetWare normally will not
        immediately delete the file but relocate it to a higher level
        subdirectory for a period of time.  Since this requires physical
        disk I/O, NetWare will queue these requests in an effort to organize
        the operations by their location on the disk.  This technique,
        called Elevator Seeking, allows multiple disk operations to be
        performed in a single sweep of the disk versus the forward/backward
        method of servicing disk requests in the order received.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


        Read:
        -----
        The NLM tracks the number of workstation requests to Read
        a file as reported by NetWare.  Most such requests can be
        satisfied by the data already in NetWare's file Cache Buffers.
        However, if NetWare cannot satisfy the request from cache, it
        it will queue these requests in an effort to organize the
        operations by their location on the disk.  This technique,
        called Elevator Seeking, allows multiple disk operations to be
        performed in a single sweep of the disk versus the forward/backward
        method of servicing disk requests in the order received.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


        Write:
        ------
        The NLM tracks the number of workstation requests to Write data
        to a file as reported by NetWare.  This information is first
        written to the file Cache Buffers, modifying previously read
        buffers if it is an update or allocating new buffers if required.
        If the entire cache buffer has been modified or the specified
        delay has passed since the last change to the file Cache Buffer
        (based upon the Dirty Disk Cache Delay Time setable parameter
        which defaults to 3.3 seconds and supports a range of 0.1 to
        10.0 seconds), NetWare queues up the Dirty Block to the disk
        I/O subsystem for flushing to disk.

        NetWare will queue disk requests in an effort to organize the
        operations by their location on the disk.  This technique,
        called Elevator Seeking, allows multiple disk operations to be
        performed in a single sweep of the disk versus the forward/backward
        method of servicing disk requests in the order received.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


        Dir Search:
        -----------
        The NLM tracks the number of workstation requests to search a
        directory as reported by NetWare.  Most such requests can be
        satisfied by the data already in NetWare's directory Cache
        Buffers.  However, if NetWare cannot satisfy the request from
        cache, it it will queue these requests in an effort to organize
        the operations by their location on the disk.  This technique,
        called Elevator Seeking, allows multiple disk operations to be
        performed in a single sweep of the disk versus the forward/backward
        method of servicing disk requests in the order received.

        The first column represents the Current level of activity.  The
        second column shows the Average level for this monitoring period.
        The third column tracks the Peak level since the NLM was loaded or
        the statistics were last reset.  The last column represents the
        Cummulative level of activity for this monitoring period.


Licensing:
----------
    Avanti Technology, Inc. offers NConsole as a licensed software
    product with continuous right to use so long as the registered
    user remains in adherence to the terms and conditions of the
    Software License Agreement.  NConsole is available under the
    following licensing method:

            File Server License at $75.00/File Server

            (Note:  Introductory pricing only in effect for the first
                    ninety (90) days after the initial product release.)

    Under this licensing method, the user is provided with free
    technical support for the product and free upgrades for the
    first year after registration.  Upgrades after the first
    year are available at the then current fee schedule which
    may vary based upon the licensing method.

    Prices quoted are pre-paid in US Dollars, excluding any
    applicable sales taxes or export duties.  The license
    fee includes software delivery via ground services within
    the continental United States (call for quotes on express
    or non-continental U.S. delivery).  Quantity discounts and
    corporate licensing may be offered, call for requirements.
    The availability of credit terms and invoicing is at the
    sole discretion of Avanti Technology, Inc.


System Requirements:
--------------------
    This release of the NLM requires NetWare v3.11, v3.12, or
    v4.0x.  CLIB v3.11 rev D or later is required for the NLM
    to run under NetWare v3.1x.  The CLIB v4.01 rev B or later
    is required for the NLM to run under NetWare v4.0x.

    Note:  The CLIB shipped with initial copies of NetWare v4.0
           (CLIB v4.0x - no revision specification) has a bug
           in an internal function which will cause the server
           to ABEND (ABnormally END), even if called by CLIB.
           This NLM is susceptible to the bug and, thus,
           should not be loaded on any NetWare v4.0x server
           running CLIB v4.0x (no revision specification).
           This CLIB bug does not exist in CLIB v4.01 rev B
           or later, including the CLIB in NetWare v4.01.


Technical Support:
------------------
    In order to provide the best and most expedient technical
    support possible, it is requested that the following information
    be known prior to initiating technical support contact:

    File Server:   NetWare version and CLIB revision

    In addition, the more indepth the problem can be described & isolated
    (including any error message), the greater the chances are for quick
    resolution.  The following means may be used for technical support:

    Mail:          Avanti Technology, Inc.
                   13492 Research Boulevard
                   Suite 120-271
                   Austin, Texas  78750  USA

    Telephone:     (+1)512/335-1168
                   08:00 to 16:00 (US Central time zone)

    Facsimile:     (+1)512/335-7838

    CompuServe:    76517,3117


Release Notes for v1.03:
------------------------
      - Added support for NOPEAKS command line option which disables
        the automatic logging of alerts whenever a peak has been
        reached/exceeded after the stabilization period
        (Note: All peaks continue to be tracked and logged normally.
               Only the special alert logging is disabled.)
      - Added logic to detect a console DOWN request in order to
        disable Peak tracking/logging while system is being downed
      - Modified the password entry routine servicing the console
        keyboard lock function to provide operational messages

Release Notes for v1.02:
------------------------
      - Coded around a Microsoft C library/ANSI.SYS conflict in the
        client (.EXE) which could cause portions of the screen to
        not support any screen colors/attributes

Release Notes for v1.01:
------------------------
      - First commercial release
      - Added automatic logging of stats whenever Peak levels of activity
        are encountered to the NLM (Note: Logging does not occur until
        after a defined period of load balancing occurs to avoid excessive
        logging which would occur during the initial period after the
        NLM is loaded and begins tracking the statistics.)
      - Added support for F4 key (client and server) to write the most
        recent stats to the log file
      - Added support for F5 key (client and server) to clear the log file,
        write the most recent stats to the log file, and reset the stats
      - Added support for F6 key (client and server) to clear the log file
      - Added support for TIMEOUT=## (## = minutes) command line option
        (server) for user specification of the screen saver timeout factor
      - Changed Beta support of Del key (client and server) to F5 key
      - Changed Beta support of DELAY=##### (##### = seconds) command line
        option (server) to TIMEOUT=## (## = minutes)
      - Cosmetic enhancements and optimization of the main screen display
      - Corrected a logic problem which only supported alphabetic characters
        in the SUPERVISOR/ADMIN password when unlocking the Console Keyboard

