Downloading and Installing the IntranetWare Support Packv3.0
Articles and Tips: tip
01 Aug 1997
The IntranetWare Support Pack v3.0 contains a comprehensive set of updates for all of the services contained in the IntranetWare box (NetWare 4.11, NIAS 4.0, NetWare MPR 3.0 &3.1, NetWare/IP, LAN drivers, and so on). The patches contained in this file have undergone rigorous testing, including component testing, core OS testing, and integration testing with other Novell products.
The IntranetWare Support Pack v3.0 features an improved "silent" installation program. Instead of prompting you to specify which Novell services are installed, the install script auto-detects them by first checking the PRODUCTS.DAT database (see the "Installed Products" option in INSTALL.NLM). The Support Pack adds an option to back up the files that normally would be overwritten when installing the IntranetWare Support Pack. The Pack lists only one entry in the installed products window for IntranetWare Support Pack v3.0, but you can see more information by highlighting the entry and pressing the <Enter> key.
The Support Pack includes a single NDS Manager program for both Windows 95 and Windows NT. This program is used to manage Novell Directory Services. After installing the IntranetWare Support Pack v3.0, this program is located in the SYS:PUBLIC/WIN95 directory.
The Support Pack also updates the CLIB modules and shared code libraries, as well as the Novell Directory Services TCPIP and IPX protocols and the CDROM.NLM program. The updates to the Web Server v2.51 product have been removed since the new 3.1 version is available from http://www.novell.com.
Downloading the Support Pack
To download the IntranetWare Support Pack v3.0, start your web browser and go to support.novell.com/search/patlst.htm. Next go to the IntranetWare Support Pack and NetWare 4.11 section. Click on the IWSP3.EXE file to bring up an extended rendition of the TID information that you are reading here (Technical Information Document #2926691). Under the Associated File heading on the TID, click on iwsp3.exe, then select a save directory from which to download the file. You can then read the whole TID or print it out if you want to.
Installing the Support Pack
To install the IntranetWare Support Pack, complete the following steps:
1. To extract the file, type IWSP3 <Enter>. You can extract it to the server's volume SYS, on another server volume, or on a local client if you are using RCONSOLE to run the installation.
Note: This file contains directory paths that could exceed DOS's limits if extracted locally. To prevent this problem, extract the file in a root level directory on your local drive, or choose a NetWare volume which accepts longer paths.
2. At the server console prompt, type LOAD INSTALL <Enter>.
3. Select "Product Options."
4. Select "Install a Product Not Listed."
5. Depending on where the Support Pack files are located, complete one of the following steps:
a. From the SYS volume:, press <F3> and specify the path, including the volume name (such as SYS:\directory name). Press <Enter>.
b. From a different server on the network, press <F3> and specify the full path including the server name (such as Server_Name\VOL1:\directory name). Then press <Enter>. This step may prompt you for a login name and password for the other server.
c. From a local drive on a client that is using RCONSOLE, press <F4> and press <Enter>.
6. Press <F10> to accept the marked options and continue.
7. After the files finish copying into their respective directories, the Support Pack installation is complete. Review the .NCF files for accuracy, then press <Enter> to complete the installation of the IntranetWare Support Pack before bringing down the server and restarting it.
Notes on Installing the IntranetWare Support Pack
NDS Manager Program for Both Windows 95 and Windows NT. After installing the IntranetWare Support Pack v3.0, you can locate the NDS Manager program in the SYS:PUBLIC/WIN95 directory. To use this with Windows NT, launch the NDSMGR32.EXE program from the SYS:PUBLIC/WIN95 directory. Another option is to copy the NDSMGR32.EXE to the SYS:PUBLIC/WINNT directory.
NetWare SFT III. SFTDPPSM.NLM is copied to the /MISC directory. If you have NetWare SFT III servers with two processors in each machine, you need to manually copy SFTDPPSM.NLM to the server boot directory, usually called C:\NWSERVER. This only works with the MPS14.PSM module, which is written to the Intel MPS 1.4 specification.
W95TSA.EXE. This file is an update to the Windows 95 Target Service Agent (TSA) used to backup local drives to the server. This is for use with SMS-compliant backup products, such as SBACKUP.NLM. The W95TSA.EXE program is located in the /MISC directory.
NE3200.COM. The NE3200.COM file is copied to the /MISC directory. If you are installing a NetWare 4.11 server containing a Novell NE3200 network adapter across the network, you need this updated LAN driver to prevent the server installation from hanging.
LSPUPD.NLM. This NLM program is run only once, during the installation of IntranetWare Support Pack v3.0. This resolves a problem with services being lost on large NLSP and RIP/SAP networks that contain a high number of SAPs and RIPs. This NLM program increases the LSP size to1024. If the size is 1024 or larger, no change will be made. This NLM program edits the SYS:\ETC\NLSP.CFG file, which can be viewed using INETCFG.NLM. This issue only occurs on servers configured for NLSP.
Issues When Installing the Support Pack
Issue 1. When you install the Support Pack, the installation process will update SERVER.EXE with the current version of LOADER.EXE. Some customers have indicated that the modified version of SERVER.EXE becomes corrupted and displays the following message: "LOADER-4.10-19: Error reading load file C:\NWSERVER\SERVER.EXE". This corruption has been linked to the DIE_HARD virus. If you see this error, first scan for viruses on the DOS boot drive of the file server, as well as any locations that the patch kit may have been copied to. Novell has ensured that the virus has not been encapsulated in the compressed Support Pack file.
Next, rename SERVER.OLD (or MSERVER.OLD if running NetWare SFT III) to SERVER.EXE (or MSERVER.EXE). Finally, run LSWAP.EXE to again update the LOADER file. The proper usage for running LSWAP is:
LSWAP [LoaderFilePath [ServerFilePath]]
Default LoaderFilePath = C:\NWSERVER\LOADER.EXE
Default ServerFilePath = C:\NWSERVER\SERVER.EXE (orMSERVER.EXE)
You can now run the newly modified SERVER.EXE (or MSERVER.EXE).
Issue 2. When you install the Support Pack in NetWare for OS/2, it is possible to see the error: "File C:\NWSERVER\LOADER.EXE (or LSWAP.EXE) cannot be opened". Error: Error Code 87 (57hex) Install 4.11-235 Press <Enter> to continue.
If you see this error, manually copy the LOADER.EXE and LSWAP.EXE files to the boot directory, usually C:\NWSERVER (the LOADER.EXE and LSWAP.EXE files are located in the PK411 directory). In the OS/2 window, run the LSWAP.EXE file by typing LSWAP LOADER.EXE SERVER.EXE <Enter>. (This only needs to be run once.)
Issue 3. If, for some reason, the server fails to boot after installation, you will need to manually rename the SERVER.OLD file to SERVER.EXE in order to bring the server back up.
Issue 4. If you always remove DOS once you load SERVER.EXE, you must restart the server with DOS active in order to install the IntranetWare Support Pack. This is because some files cannot be copied to the DOS partition unless DOS is active.
Issue 5. In order to install updates to services that are English-only, the server language must be set to English. The English-only products in the Support Pack are NetWare MPR 3.1 and the files under the ENGLISH directory.
Issue 6. The UXP200.EXE and NIP200.EXE files are included in this IntranetWare Support Pack.
Issue 7. Protocol updates are determined by the installed version of Mulitprotocol Router. To ensure that you receive the latest protocol updates you must install Multiprotocol Router version 3.1 (It was included with IntranetWare).
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.