Network Supervisor's Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ Network Supervisor's Toolkit / Network Supervisor's Toolkit.iso / patches / _410ptch / libup4 / install.doc < prev next >

Wrap

Text File | 1996-07-10 | 18.3 KB | 416 lines

NOVELL Server Library Update The Server Library Update package provides a convenient and effective method for NetWare system administrators to install updated server libraries. It is Novell's desire to provide its customers with server library updates in the most convenient and efficient manner possible. With this in mind, INSTALL.EXE was designed emphasizing ease-of-use and operating system integrity. As a result, INSTALL.EXE supports several important features and is capable of * Installing upgraded NetWare NLMs automatically * Creating a log file to capture system messages * Uninstalling the upgrades and returning the system to its original condition * Testing the system upgrade procedure before attempting the actual installation * Using command line parameters to help customize the utility to meet individual needs This document contains five main sections: * Directory structure This is a brief description of the directory structure created on the workstation during the extraction process. * Installation utility This section describes the function of INSTALL.EXE. * Command line parameters This section contains an explanation of the command line parameters supported by INSTALL.EXE. * Syntax This is an explanation of the INSTALL command syntax. * Error messages This section contains an alphabetical list of the error messages generated by INSTALL.EXE. Directory Structure ------------------- A directory structure similar to the one below should have been created in your workstation's current directory as a result of extracting the update package. At least one of the directories (3.x, 4.x or COMMON) will exist and will contain files that need to be installed. /<Current Directory> <Current Directory> / 3.x <Current Directory> / 4.x <Current Directory> / COMMON The current directory contains the installation utility (INSTALL.EXE) and the corresponding documentation (INSTALL.TXT). The 3.x directory contains all the files specific to NetWare versions 3.11 and 3.12. The 4.x directory contains those files specific to NetWare versions 4.0 and later. Files which will be installed on all versions of NetWare are contained in the COMMON directory. Installation Utility -------------------- The installation program supplied with this update (INSTALL.EXE) is a DOS command line utility which installs the updated NLMs on to one or more Novell NetWare servers. INSTALL.EXE performs three major tasks: 1. Analyzes all of the modules residing in subdirectories 3.x, 4.x and COMMON. 2. Gathers information such as NetWare version and available disk space for all the NetWare servers into which the workstation is currently logged. 3. Performs a systematic update of each qualifying NetWare server with the option of user prompts. Command Line Parameters ----------------------- The installation utility INSTALL.EXE supports the following command line parameters: /a Append output to INSTALL.LOG The installation utility creates a log file (INSTALL.LOG) which contains messages relating to the installation procedure. By default, INSTALL.LOG is overwritten if it exists. This switch will cause the messages to be appended to the existing INSTALL.LOG. /l# Set log file level /l0 Turn OFF the log file. /l1 Turn ON the log file (default). /l2 Turn ON the log file and disable the console. Installation messages will go to the log file instead of the console. /n Set "no action" mode Run the update procedure without actually performing the update. All prompt and log level switches are honored. This is useful for verifying the installation actions before installing. /p# Set prompt level /p0 Do not prompt before updating. /p1 Prompt before updating any server (default). /p2 Prompt before updating any server or file. /u Uninstall the candidates from an NCP Server This switch can be used with all of the other switches, including /n. It provides a quick way to back out the updated NLMs and restore the original files should the need arise. /v# Set verbose mode. /v0 Sets verbose mode to low, disabling most of the messages. /v1 Sets verbose mode to high, enabling all messages (default). NOTE: These command line parameters make it possible to test the installation utility on a specific system before performing the installation. For example, the command F:\UPDATE>INSTALL /n /p0 /l2 will create a log file containing all of the update information which would have been performed without pausing for user prompts. Syntax ------ The command line switches may be specified in any order and may be concatenated together without switch character delimiters. The switches are not case sensitive. The following four commands are equivalent. F:\UPDATE> install /p0 /l2 /v0 /n F:\UPDATE> install /p0l2v0n F:\UPDATE> install /P0 /L2 /V0 /N F:\UPDATE> install /V0N /P0L2 The switch character "/" may be changed by setting the SWITCHAR environment variable. For example, the command F:\UPDATE> set SWITCHAR=- sets the switch character to the hyphen "-" symbol. Error Messages -------------- This section describes the various error messages displayed by the INSTALL utility. Candidate <FILENAME> is not installed in SYS:SYSTEM INSTALL cannot find the candidate <FILENAME> on the server. Cannot backout <FILENAME> because <FILENAME.BAK> does not exist INSTALL cannot back out <FILENAME> because the original file was not found. During the update process, INSTALL renames the original file with a .BAK extension. Without this .BAK file, INSTALL is unable to restore the original file. Copy failed because of Ctrl-C key sequence Ctrl-C was pressed during the file copy. Copy failed because of destination close failure INSTALL could not close the destination file. Copy failed because of destination open failure INSTALL could not open the destination file. Copy failed because of read failure An error was encountered while reading the source file. Copy failed because of source close failure INSTALL could not close the source file. Copy failed because of source open failure INSTALL could not open the source file. Copy failed because of unknown error code An unanticipated internal error occurred. Copy failed because of write failure. An error was encountered while writing the destination file. Failed loading information about candidates Either an out-of-memory condition while processing the candidate files, or invalid NLM header information was encountered in one or more of the candidates. Try freeing additional memory by unloading unnecessary TSRs. Failed removing file <FILENAME> An error was encountered while attempting to erase <FILENAME>. This may be caused by insufficient rights to the SYS:SYSTEM directory. Failed renaming <FILENAME> to *.BAK An error was encountered while attempting to rename <FILENAME> to <FILENAME.BAK>. This may be caused by insufficient rights to the SYS:SYSTEM directory. Failed renaming <FILENAME> to *.QRM INSTALL was unable to rename the updated NLM with a .QRM extension. This may be caused by insufficient rights to the SYS:SYSTEM directory. Failed renaming <FILENAME1> to <FILENAME2> An error was encountered while attempting to rename <FILENAME1> to <FILENAME2>. This may be caused by insufficient rights to the SYS:SYSTEM directory. Failed resetting attributes of <FILENAME> The attempt to clear the attributes of <FILENAME> failed. This may be due to insufficient rights in the SYS:SYSTEM directory. <FILENAME> is currently installed in SYS:SYSTEM INSTALL discovered that <FILENAME> is currently installed on the server and is attempting to restore the original NLM. <FILENAME> not currently installed in SYS:SYSTEM No matching NLM was found in the NetWare server's SYS:SYSTEM directory. This message will be displayed when a specific NLM is loaded for the first time or if a specific NLM is not loaded in the SYS:SYSTEM directory. NOTE: If any of the NLMs being updated are loaded from the server's DOS partition, they must be copied back to the DOS partition manually after the update. INSTALL does not support copying NLMs to a server's DOS partition. RCONSOLE may be used for this purpose. <FILENAME> uninstall completed successfully The NLM <FILENAME> was successfully backed out and the original NLM was restored. <FILENAME> update completed The candidate file <FILENAME> has been fully processed. Installation is terminating INSTALL has terminated abnormally. Marking <FILENAME.BAK> as Read-Only... INSTALL has set the Read-Only attribute of a candidate file after that file has been successfully installed. NCP Server <SERVERNAME> can't be updated because the file has an invalid NLM header The specified NLM update candidate has in invalid header. NCP Server <SERVERNAME> can't be updated because the ID for volume SYS: is unavailable INSTALL is unable to obtain the volume ID for SYS:. NCP Server <SERVERNAME> can't be updated because the NLM version information is unavailable INSTALL is unable to obtain the NLM version information on an update candidate. NCP Server <SERVERNAME> can't be updated because the server information is unavailable INSTALL is unable to obtain server-specific information. NCP Server <SERVERNAME> can't be updated because the volume information is unavailable. INSTALL is unable to obtain the volume information for SYS:. NCP Server <SERVERNAME> can't be updated because you have insufficient rights You have inadequate rights to run INSTALL on volume SYS:SYSTEM. You need read, write, create, erase and access control to SYS:SYSTEM in order to run INSTALL. NCP Server <SERVERNAME> can't be updated because you need NetWare 3.11 or later The updated modules are intended only for NetWare versions 3.11 and up. NCP Server <SERVERNAME> can't be updated because of unknown error code An internal error occurred in the INSTALL program. NCP Server <SERVERNAME> should be upgraded to 4.01 <SERVERNAME> is running NetWare version 4.0 and should be upgraded to version 4.01. NCP Server <SERVERNAME> uninstall is complete. The uninstall process of server <SERVERNAME> is complete. NetWare Requester or Shell is not loaded INSTALL requires the use of either the NetWare DOS Requester (VLM.EXE) or the NetWare Shell (NETX.EXE). One of these two files must be loaded before INSTALL can function. No files were found to update No files were found in the 3.x, 4.x or COMMON subdirectories. Make sure these directories were created during the extraction of the update package. Not enough disk space to install <FILENAME> Volume SYS: does not have enough space available to install <FILENAME>. Create more available space on volume SYS: and rerun the INSTALL utility. Note: Unable to build complete list of connections due to out of memory condition. Proceeding with partial update of NCP Servers. An out-of-memory condition was encountered while building the connection information list. NOTE: INSTALL will continue the update procedure, but will not process all of the connections. After completing the initial run, log out of the updated servers and rerun INSTALL to complete the update. It may be advisable to free additional memory by unloading unnecessary TSRs. Out of memory building connection tables INSTALL has encountered an out-of-memory condition. Free additional memory by unloading unnecessary TSRs. Program name must be [?:\path\] INSTALL.EXE The INSTALL utility as distributed by NOVELL is named INSTALL.EXE. If this message is displayed, the update you received may not be authentic. Removing SYS:SYSTEM/<FILENAME>.BAK... INSTALL is removing an NLM file with the extension .BAK from SYS:SYSTEM. When an update candidate is installed, the original file is renamed with a .BAK file extension. If a file with that name already exists, INSTALL will remove it before updating the NLM. Renaming <FILENAME.QRM> to <FILENAME.NLM> INSTALL is renaming the candidate NLM to its original distribution name. In order to minimize the chance of a partial update, INSTALL transfers candidate files with a .QRM extension. When the transfer is complete, INSTALL renames the existing file to have a .BAK extension and renames the candidate file to have a .NLM extension. Renaming SYS:SYSTEM/<FILENAME> to SYS:SYSTEM/<FILENAME>.BAK... INSTALL is renaming the current NLM with a .BAK extension. This is done so that a specific candidate may be easily backed out should the need arise. Resetting attributes of SYS:SYSTEM/<FILENAME> INSTALL is resetting file attributes, making it possible to rename or remove the file <FILENAME>. Transferring <FILENAME.NLM> to <FILENAME.QRM> INSTALL is transferring the candidate file <FILENAME.NLM> as <FILENAME.QRM>. When the transfer is complete, INSTALL renames the existing file to have a .BAK extension and renames the candidate file to have a .NLM extension. This method reduces the chance of having a partial upgrade. Unable to uninstall file <FILENAME> INSTALL was unable to uninstall <FILENAME>. The previous message in the log file INSTALL.LOG will indicate the reason for the failure. Unknown error processing SYS:SYSTEM/<FILENAME> INSTALL encountered an unknown error trying to access NLM version information from <FILENAME>. This error may be due to an invalid or corrupt header. Warning: Failed setting attributes of <FILENAME> INSTALL encountered an error while trying to set the attributes of <FILENAME> to read-only. This may be caused by insufficient rights to the SYS:SYSTEM directory.