Secure Path Agent for NetWare Installation Notes
================================================
HPQSPAGT.NLM Version X2.0 Build 014
QL2300.HAM Version 6.50s
SPM.EXE Version 3.1 Build 026

March 30, 2001

1.  Install and configure a NetWare 5.1 or 6 server,
including TCP/IP networking services.  Be sure to
configure SYS:ETC/HOSTS or a name service in order to
map server host names to all server IP-Addresses on all
interfaces.  It is assumed that the reader is familiar
with the required procedures.

2.  Decide which network hosts will be authorized to
support Secure Path Clients.  Be sure to configure
SYS:ETC/HOSTS or a name service in order to map Client
host names to all Client IP-Addresses.  It is assumed
that the reader is familiar with the required procedures.

3.  The remainder of these notes assume that the installation
media is on floppy drive "a:\", however the installation can
be performed from any directory residing on any DOS drive or
any NetWare volume.  (Note:  Installing from real mode DOS
drives may cause a node cast-out on clustered servers.)

4.  The default installation configuration is recommended
for most Secure Path installations.  Invoke the NetWare
configuration utility from the NetWare server console:

NETWARE: load nwconfig

The default installation will install and start both the
Driver (QL2300.HAM) and the SecurePath Agent (HPQSPAGT.NLM).
From the "Configuration Options" menu, first select
"Product Options", and then "Install a product not listed".
Verify that the Secure Path installation disk is inserted in
floppy drive "a:\", and perform the installation.

5.  If the default installation configuration fails, the user
may wish to perform an interactive installation in order to
verify and possibly override certain installation parameters.
In order to perform an interactive installation, verify that
the Secure Path installation disk is inserted in floppy drive
"a:\", and invoke the installation program directly from
the NetWare server console:

NETWARE: load a:\pinstall /i

Either accept or modify the default answer to each prompt.
For the purposes of the Secure Path installation, "clobber"
indicates that all files will be overwritten, "noclobber"
indicates that existing files will be preserved, "upgrade"
indicates that existing files will be upgraded, "disable"
indicates that the operation will not be performed.  Please
refer to the Secure Path User's Guide for more information
regarding specific installation parameters and options.
Enter "yes" when prompted for the final confirmation, or
enter "no" to abort the installation.  One may also abort
the installation by entering the interrupt key at any prompt.
(interrupt is usually CTRL-C or CTRL-Z, followed by ENTER).

6.  Once the installation is successfully completed, use the
Secure Path Agent User Interface (cycle through server screens
by pressing ALT-ESC) in order to specify the Client password
(SECUREPATH by default) and in order to specify which Client
hosts are authorized to connect to the Agent.  Be sure to
specify the same Client host names as configured in step 2.

7.  In some rare cases, it may be necessary to restart the
Driver and/or Agent manually.  This is necessary when installing
an older or identical version of the Driver, when either the new
or existing versions of the Driver are not hot-swap capable,
or when other programs (or the user) attempt to use the server
console during stage 2 of the installation.  Both the Agent and
the Driver may be restarted using the UNLOAD/LOAD commands:
(Note:  Restarting the driver may cause a node cast-out on
clustered servers.)

NETWARE: unload QL2300.ham
NETWARE: load QL2300.ham
NETWARE: unload hpqspahw.nlm
NETWARE: load hpqspahw.nlm
NETWARE: unload hpqspagt.nlm
NETWARE: load hpqspagt.nlm

8.  The installation may add lines to the system STARTUP.NCF
and/or AUTOEXEC.NCF in order to load the Driver and/or Agent at
boot time.  Do not change the .HAM or .NLM extensions for the
Driver (QL2300.HAM) or Agent (HPQSPAGT.NLM) if these lines are
manually modified (e.g. to specify slot=X Driver arguments).
Subsequent instances of the installation program will not be
able to recognize commands affecting the Driver or Agent if
the .HAM or .NLM extensions are not intact.
