Copyright: ó 1995 avanti tecnhnology, inc.


Contents
NodeInfo v2

Installation Overview

There are two different methods for installing NodeInfo:  Manually. for those who are interested in only installing the DOS client; and through Windows, which will install both the DOS and Windows clients.

It should be noted that using the Windows method does not preclude or limit the use of the DOS client.  However, using the windows method does require that Windows be installed and properly configured for use of third-party network applications on the workstation from which the installation will be performed.

Prior to installing NodeInfo using either method, a valid network connection with SUPERVISOR rights must be established.  Additionally, a drive must be mapped to the desired File Server onto which the Server components (.NLM and .HLP file) are to be installed.

Windows Installation

DOS Installation


Windows Installation

Windows Installation - NLM & Windows Clients

Before proceeding with the Windows Installation, the following checklist of requirements should be confirmed:

Windows Installation Checklist

•	Novell NetWare v3.11, v3.12, v4.0x or v4.10

For NetWare v3: 	CLIB v3.11 revision D or later

For NetWare v4.0x: 	CLIB v4.0x revision A or later

•	Windows v3.1 or Windows for Workgroups v3.11

•	Windows Setup Network option properly configured

•	Latest Novell NetWare Windows client drivers loaded

•	Logged in to Server as SUPERVISOR or equivalent

•	One or more drives mapped to destination Server

•	Server files destination (server/volume/path) decided

•	Client files destination (drive/path) decided

The Windows installation process requires that Microsoft Windows v3.1 (or later) or Microsoft Windows for Workgroups v3.11 (or later) be running on the workstation where the software is to be installed.  In addition, Windows should have already been properly configured for support of Novell NetWare (shell versions 3.26 and above).  This can be confirmed by running the Windows Setup program in the Main program group and reviewing the Network option.

If the Network option is not set, select Change System Settings under the Options, then follow the prompts and instructions provided by Windows for configuring the Network option.

If the Network option was set using the drivers supplied by Microsoft or if an older set of Novell's drivers is in use, it will be necessary to upgrade to the latest files available from Novell.  The easiest way to confirm whether or not older drivers are in use is to perform a directory of the NW*.* files in the Windows SYSTEM directory.  If these files are not stamped with a late 1994 date, it is recommended that the latest Novell NetWare client kit for Windows be installed.  Older versions have been known to cause General Protection Faults (GPFs) under Windows when certain NetWare API requests are issued.

Important Note: Should you experience any problems in the installation or initial execution of NodeInfo, the most likely cause is the use of older drivers or mismatched drivers.  Please confirm that the latest releases of the drivers and that the proper set of files for NETX or VLM were installed prior to seeking support.

The user must be logged in to the Server to which the software is to be installed as SUPERVISOR (or equivalent).  This insures that the files can be copied to the destination locations.

The workstation must have a drive mapped to the Server.  The installation utility uses DOS Copy logic which requires that a physical or logical drive be mapped to the file copy destination.

The destination location for the client and server files should be determined.  By default, the installation utility will make the following suggestions:

Client	C:\NODEINFO

Server	\\<server>\SYS\SYSTEM\NODEINFO

To start the installation process, load Windows and then select Run under the File options on the Windows main screen.  Type the drive (and path, if appropriate) where the distribution files are located followed by SETUP and press the Enter key.

Example	A:\SETUP <Enter>

After screen initialization, the Welcome to the NodeInfo Setup program dialog box will appear.  Selecting Continue will result in the installation utility displaying a list box of the Servers to which the workstation has mapped drives.   Selecting a Server from this list defines the destination for the Server files and the default Server.

If the desired Server is not included in this list, it is because there is not a mapped drive associated with the Server.  As previously mentioned, a workstation drive must be mapped to the destination Server for the installation process to succeed.  The installation utility uses DOS Copy logic which requires a physical or logical drive as the file destination.

To map a workstation drive to the desired Server, Exit the installation process then exit Windows and map a workstation drive to the desired Server.  The desired Server should then appear in the list box once the installation process is restarted.

Important Note: Launching a DOS task and mapping a drive to the desired Server will not cause it to appear in the list box upon return.  The mapped drive must have been established prior to loading Windows.

The next prompt will be for an installation check box.  The following options are displayed:

Install Client files

Install Server files

The initial installation should include all of the files.  However, it is possible to only install a portion of the distribution files by selecting the appropriate check boxes.  This option simplifies the installation of the NodeInfo client files on additional workstations without forcing the installation of the server files.

The next prompt will be for the client program files destination.  Type the desired drive and path then press Enter to continue.

The next prompt will be for the server files destination.  Type the desired server, volume, and path in Universal Naming Convention (UNC) format then press Enter to continue.

Important Note: UNC format requires that a double backslash precede the server, while a single backslash separates the volume and path specifications.  If a known drive is mapped to the desired server and volume, it is possible to use a drive and path specification:

Example:  Z:\SYSTEM\NODEINFO

The installation utility should begin copying the files to the specified destinations, displaying status boxes indicating the percent completed.

If any errors are encountered during this process, please re-try the installation process after confirming the validity of the specified destination locations.  Should installation errors persist, please note the dialog box message displayed and contact Avanti for further assistance.

Once all of the files have been copied to the destination locations, the installation utility will create an NodeInfo program group and add the appropriate icons.

At this point, the installation utility will display a dialog box offering to execute Novell's RCONSOLE utility in order to load the NodeInfo NLM on the Server.  Selecting to execute RCONSOLE will cause the installation utility to attempt to launch the RCONSOLE utility from the SYS:SYSTEM directory of the destination Server. If RCONSOLE.EXE does not exist in that location, the process will fail. Unless Novell's RSPX and REMOTE NLMs are also loaded on the Server, RCONSOLE will not be able to communicate with the Server.

Important Note: The NodeInfo NLM must be loaded on the Server for full functionality of either of the NodeInfo clients.  If executing RCONSOLE is not selected or fails, the NodeInfo NLM will need to be loaded by the user.

As a final step in the installation process, the installation utility will launch Window's NotePad showing the README file.  This file should be reviewed in its entirety: It will list any revisions or enhancements made to NodeInfo since the manual was printed.  It also provides additional support and usage information.

Once the README has been reviewed, exiting NotePad should reveal the NodeInfo program group with the necessary icons.  The NodeInfo icon is for the Windows graphical client, while the NIRemote icon is for the DOS client which is a character based, limited version of the Windows client that includes command line options for use in batch file processing.

If the NodeInfo NLM has been loaded on the Server, the NodeInfo clients are now ready for execution.


DOS Installation

DOS Installation - NLM & DOS Client

The DOS Installation process will neither decompress the Windows client files, nor properly install the required .DLLs.  If you plan to use the Windows client, you must use the steps outlined in the Windows Installation section.

Before proceeding with the DOS Installation, the following checklist of requirements should be confirmed:

DOS Installation Checklist

•	Novell NetWare v3.11, v3.12, v4.0x or v4.10

For NetWare v3: 	CLIB v3.11 revision D or later

For NetWare b4.0x: 	CLIB v 3.0x revision A or later

•	Microsoft MS-DOS v3 (or later) compatible OS

•	Latest Novell NetWare client drivers loaded

•	Logged in to Server as SUPERVISOR or equivalent

•	One or more drives mapped to destination Server

•	Server files destination (server/volume/path) decided

•	Client files destination (drive/path) decided

Important Note: Should you experience any problems in the installation or initial execution of NodeInfo, the most likely cause is the use of older drivers or mismatched drivers.  Please confirm that the latest releases of the drivers and that the proper set of files for NETX or VLM were installed prior to seeking support.

The workstation must be logged in as SUPERVISOR (or equivalent) to the Server to which the software is to be installed.  This insures that all the files can be copied to the desired destination locations.

The workstation must have a drive mapped to the Server.  This is necessary so that the suggested DOS Copy commands can perform the desired task.

The DOS Installation is a manual process executed from the DOS command line.  It involves copying selected files to the desired client and server destination locations.

Important Note: If the desired destination directory does not already exist, it will need to be created prior to attempting the outlined copy process.

The following files need to be copied to the client destination location:

README 	(Notes pertinent to this release)

NIREMOTE.EXE 	(DOS client program)

NIREMOTE.PIF 	(Windows DOS Box .PIF File)

REVISION.DOC 	(ASCII revision history)

Copy these files to the desired client destination directory:

Example:  COPY A:\README C:\NODEINFO

The following files need to be copied to the server destination location:

NODEINFO.NLM  	(NLM server program)

NIREMOTE.HLP  	(On-line Help file)

Copy these files to the desired server destination directory:

Example: COPY A:\NODEINFO.NLM Z:\SYSTEM\NODEINFO

Once these files are copied to the destination locations, the NLM must be loaded before the NIRemote DOS client can access the NLM.