|
These files have undergone component testing, core OS testing, and integration testing with other Novell products.
If you experience problems downloading large files, refer to TID 2947202.
To order the Support Pack CD, go to http://support.novell.com/csp/orderinfo.html.
Table of Contents
1.0 Support Pack Installation
1.1 Installing the Support Pack
1.2 SETUPNLS.NLM Error on NetWare 4.11
1.3 ManageWise Error During Installation
1.4 3.30 ODI Drivers for NetWare Connect
1.5 Configuring NetWare for SAA v3.0 and v4.0 before Installing the Support Pack
1.6 Radius
1.7 Installing on Multiple Servers
1.8 LSP Object Not Created Error
2.0 Notes
2.1 Documentation
2.2 Novell Directory Services
2.3 NDS Manager Program for Windows 95 and Windows NT
2.4 Using LSPUPD.NLM
2.5 Using CPUCHECK
2.6 NetWare Administrator with NetWare for SAA 4.0
2.7 Novell Client Versions
2.8 Installing the Support Pack with Vinca StandbyServer
2.9 Setting the Code Page for Portuguese
2.10 SCMD.NLM Load Parameter
2.11 PPPTSM Load Failure Error
2.12 Remote Boot
3.0 Tips
3.1 Installing Protocol Updates
3.2 Resolving LOADER Error
3.3 NetWare for OS/2
3.4 Resolving a Server Boot Failure
3.5 Installing the Support Pack if DOS Is Removed
3.6 Remote Boot and RPL
3.7 LAN Driver Issues
3.8 NBI.NLM Issue
3.9 GroupWise 5.5 and NetWare Administrator 32
3.10 Additional Information about the Install Program
3.11 Server Configuration Changes
3.12 Support Pack Testing
3.13 IP Compatibility
3.14 Uninstalling the Support Pack
3.15 Y2K Fixes in the Support Pack
4.0 Files in the TOOLS Directory
4.1 NetWare SFT III
4.2 NE3200.COM
4.3 Modem Support
4.4 Using Novell Client on NEC PC9800 Series or Fujitsu FMR
4.5 NPRINTER
5.0 Changes Since Last Support Pack
1.0 Support Pack Installation
The Support Pack requires up to 70 MB of additional
disk space. If you select the Backup option, you will
need an additional 160 MB of disk space.
You must upgrade all servers with the SCMD.NLM file
included in this Support Pack. SCMD.NLM works with
NetWare 4.11, 4.2, 5.0, and 5.1. Failure to upgrade all
servers at once will stop communication between the
servers.
Prior to installing the Support Pack, you should make
sure that you have a reliable backup. The backup option
(described in section 3.14 "Uninstalling the Support
Pack") provided by the Support Pack install will not
work if the server cannot be rebooted or the volumes do
not mount.
Make sure that the NetWare 4 server holds a copy of the
server's own partition with the same packet signature
level.
1.1 Installing the Support Pack
If installing from CD, begin with Step 2.
1) To explode the file, enter the filename. Explode the file
on the server's volume SYS:, or on another server's volume.
Note: This file contains directory paths that
could exceed the DOS limits. The file must be
extracted in a root-level directory on your local
drive or on a NetWare volume that accepts longer
paths.
2) At the server console prompt, enter LOAD INSTALL.
3) Select Product Options > Install a Product Not Listed.
4) Depending on where the Support Pack files are located,
complete one of the following steps:
- From the local volume SYS:, press F3, then specify the
path, including the volume name (for example,
SYS:<directory_name>).
- From a different server on the network, press F3, then
specify the full path including the server name (for
example, <server_name>\VOL1:<directory_name>).
This step prompts for a login name and password
for the other server.
The F4 option in RCONSOLE does not apply to this
Support Pack.
5) Press Enter.
6) Press F10 to accept the marked options and continue.
NOTE: If the option to back up files is not
selected, you will not be able to uninstall the
Support Pack.
7) Press Enter to end.
8) After the files finish copying, review the .NCF files for
accuracy, then type RESTART SERVER to complete the
installation of the Support Pack.
9) In order to activate the purge fixes (PRGFREFX.NLM), the
PURGE /ALL DOS command must be run at the root of all the
server volumes. In addition, VREPAIR.NLM should be run until
there are no errors.
NOTE: Newer files already existing on the server
will not be overwritten. The files are first
version-checked. If they are the same, they are
also date-checked.
1.2 SETUPNLS.NLM Error on NetWare 4.11
During the installation, the module SETUPNLS.NLM may
fail to load because of Public Symbol errors. This
usually indicates that the server modules may need to
be updated before loading SETUPNLS.NLM. If this
occurs, finish the Support Pack installation without
loading SETUPNLS.NLM. Reboot the server. At the
server console, enter LOAD SETUPNLS.
If you experience a licensing error when installing
the Support Pack, run the DSREPAIR utility followed
by the SETUPNLS utility.
1.3 ManageWise Error During Installation
If the ManageWise module GTREND.NLM is running on the
server, you may get the following error during the
install: "Cannot Open GT_ERR.LOG." Do the following
to resolve this error:
1) Switch to the server console.
2) Unload LANZSU.NLM.
3) Unload GTREND.NLM.
4) Switch back to the install screen (INSTALL.NLM).
5) Press Enter, then select the Retry Copying File option.
The installation will proceed.
1.4 3.30 ODI Drivers for NetWare Connect
NetWare Connect does not support 3.31 ODI drivers. If
NetWare connect is installed, the Support Pack will
not install the included 3.31 ODI drivers, even if
the Install Driver Updates for DISK, LAN, WAN option
is selected.
1.5 Configuring NetWare for SAA v3.0 and v4.0 before
Installing the Support Pack
NetWare for SAA v2.0, NetWare for SAA AS/400 Edition
2.1, NetWare for SAA v2.2, NetWare for SAA AS/400
Edition 2 (2.3), NetWare for SAA v3.0, and NetWare
for SAA v4.0 users must take the following action
when installing the Support Pack.
1) Install the most current IBM levelset APAR for your
version of NetWare for SAA.
The appropriate levelset APAR contains maintenance
patches that will upgrade your version of NetWare
for SAA to either NetWare for SAA 2.0.40, or
AS/400 Edition 2.1.30, 2.2.10, 3.0.10, or 4.0,
depending upon which version of NetWare for SAA is
installed. There is no levelset APAR for NetWare
for SAA AS/400 Edition 2 (2.3). The levelset APAR
and all other NetWare for SAA IBM APARs can be
downloaded from
www.software.ibm.com/network/commserver/support.
2) NetWare for SAA 3.0.10 and 4.0 users who are using the
SLP feature should also install IBM APAR number JR12403.
3) Install one of the following IBM NetWare for SAA APARs,
depending upon your version of NetWare for SAA:
- NetWare for SAA 2.0.40 - APAR - JR12978
- AS/400 Edition 2.1.30 - APAR - JR12987
- NetWare for SAA 2.2.10 - APAR - JR12979
- NetWare for SAA AS/400 Edition 2 (2.3) - APAR - JR12988
- NetWare for SAA 3.0.10 and 4.0 - APAR - JR12795
4) Verify that the network boards installed on your server
will support ODI v3.31 drivers before you attempt to install
the Support Pack onto a server that also has NetWare for SAA
installed.
Using the LANCHK.EXE utility (found at
support.novell.com) might help to verify the
network board driver capability, or contact the
network board vendor. Uncheck the Install Driver
Updates for DISK, LAN, WAN option on the Install
menu if the boards do not support ODI v3.31
compliant drivers.
Unchecking this option results in the ODI v3.31
drivers in the Support Pack not being installed.
Some boards used with NetWare for SAA are not
compatible with ODI v3.31 drivers, and problems
will occur if the ODI v3.31 drivers are installed.
5) Replace the LLC8022.NLM file installed by the Support
Pack with the LLC8022.NLM file contained in the IBM NetWare
for SAA APAR used in Step 3.
6) If you are using NetWare for SAA across a WAN and have
the WAN drivers installed on a NetWare for SAA server,
complete the following after first installing the Support
Pack on that server.
- If the Install Driver Updates for DISK, LAN, WAN option
was checked, then copy SDLCTSM.NLM, contained in the IBM
APAR downloaded in Step 3) above, into the SYS:SYSTEM
directory only. Failure to copy SDLCTSM.NLM before the
server is restarted can cause the server to abend after the
Support Pack has been installed. SDLCTSM.NLM should be
installed only if the Support Pack is also installed.
- If the Install Driver Updates for DISK, LAN, WAN option
was not checked, then copy CSL.NLM, dated 12-14-1994, from
the IBM APAR downloaded in Step 3) above into the
SYS:\SYSTEM directory only.
- If you are using SDLC, X.25, or frame relay, and the
Install Driver Updates for DISK, LAN, WAN option was
checked, then you also need to update the WAN support
modules.
Download NIAS41.EXE from suport.novell.com to
obtain the updated WAN support modules that work
with the ODI v3.31 drivers installed by the
Support Pack. If you are installing NetWare for
SAA v3.0 for the first time, you should install
NIAS41.EXE only after first installing the
NetWare for SAA v3.0 software.
- If you are using frame relay and the Install Driver
Updates for DISK, LAN, WAN option was checked, then you also
need to update the frame relay support modules.
Download both NIAS41.EXE and NWSAAHPR.EXE from
support.novell.com to obtain the updated frame
relay support modules that work with the ODI
v3.31 drivers installed by the Support Pack. If
you are installing NetWare for SAA v3.0 or v4.0
for the first time, you should install
NIAS41.EXE only after first installing the
NetWare for SAA v3.0 or v4.0 software. The
NWSAAHPR.EXE file should be installed after
first installing NIAS41.EXE.
1.6 Radius
After the Support Pack is installed, the server is
rebooted. If the server abends running process
RADIUS.NLM, edit the AUTOEXEC.NCF file. Move the LOAD
RADIUS.NLM command to the bottom of the AUTOEXEC.NCF
file.
1.7 Installing on Multiple Servers
The application to install the Support Pack on
multiple servers from a workstation is not included
with this Support Pack. It is available from the
Internet at
http://www.netpro.com/configcentral/novlsupportpack/.
1.8 LSP Object Not Created Error
If you receive an error message during the
installation stating that an LSP Object could not be
created, make sure that the server has the same
packet signature level as the server's partition,
then run SETUPNLS.
2.0 Notes
2.1 Documentation
- For information on the latest Support Pack issues, see
TID 10055204.
- For information on SCMD.NLM and compatibility mode
drivers, see TID 10014779.
- For information about configuring SCMD to support Network
Address Translation (NAT), see the NetWare 5 documentation
at www.novell.com/documentation/lg/nw5/docui/index.html.
- For information about login with NetWare IP, see TID
10054255.
2.2 Novell Directory Services
Upgrade the root of the NDS tree first.
Mixed versions of NetWare 4.11 NDS (DS.NLM)
interoperate completely, but we strongly recommend
that all NetWare 4.11 servers be upgraded to the new
version to ensure consistency and easier future
maintenance.
When using DSREPAIR.NLM, you must use version 4.59 on
all NetWare 4.11 servers running DS.NLM version 6.00.
2.3 NDS Manager Program for Windows 95 and Windows NT
The Support Pack copies the NDS Manager program to
the SYS:PUBLIC\WIN32 directory. To use it with
Windows NT, launch NDSMGR32.EXE from
SYS:PUBLIC\WIN32.
2.4 Using LSPUPD.NLM
This NLM program is run only once, during the
installation of the Support Pack. 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 to
1024. 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.
2.5 Using CPUCHECK
At the server console, enter CPUCHECK to display the
server CPU information.
2.6 NetWare Administrator with NetWare for SAA 4.0
The following is for NetWare for SAA version 4.0
only, when it is installed on a NetWare 4.x server.
In order for NetWare Administrator for Windows 95 or
Windows NT to recognize SAA objects, the following
files need to be copied manually into the given
directories. Otherwise, the SAA objects will not be
recognized by NetWare Administrator, and the
administration tools will not work properly.
1) Copy SAANT.DLL to SYS:PUBLIC\WIN32\SNAPINS\NTONLY.
2) Copy SAA95.DLL to SYS:PUBLIC\WIN32\SNAPINS\95ONLY.
3) Copy SAANNTR.DLL and SAANNTR.HLP to
SYS:PUBLIC\WIN32\SNAPINS\NTONLY\NLS\ENGLISH.
4) Copy SAAN95R.DLL and SAA95R.HLP to
SYS:PUBLIC\WIN32\SNAPINS\95ONLY\NLS\ENGLISH.
2.7 Novell Client Versions
The Support Pack was tested with the following
versions of Novell Client.
- Novell Client for Windows 95/98 3.3
- Novell Client for Windows NT/2000 4.8
2.8 Installing the Support Pack with Vinca StandbyServer
To avoid issues while installing the Support Pack on
servers running Vinca StandbyServer, complete the
steps in the following Vinca Technote:
kb.vinca.com/libraries/technotes/technote72.htm
This document also applies to NetWare 4 Support Pack
9.
2.9 Setting the Code Page for Portuguese
If you do not have the code pages set up correctly on
your server, the Brazilian character set will not
display correctly.
To correct this problem, complete the following
steps:
1) Make sure that you have the following files in the DOS
directory on the DOS partition of the server:
COUNTRY.SYS
DISPLAY.SYS
KEYBOARD.SYS
EGA.CPI
NLSFUNC.EXE
2) Add the following lines to the CONFIG.SYS file:
Syntax
country=country
code,,[drive][path]country.sys
device=[drive][path]display.sys
con=(monitor,hardware character set, number
of character sets)
Example
country=055,,c:\dos\country.sys
device=c:\dos\display.sys con=(ega,,1)
install=c:\dos\nlsfunc.exe c:\dos\country.sys
3) Add the following lines to the AUTOEXEC.BAT file:
Syntax
nlsfunc
mode con cp prep=((character
set)[drive][path]character set information
file)
chcp character set
keyb keyboard code,,[drive][path]keyboard.sys
Example
mode con codepage prepare=((850)
c:\dos\ega.cpi)
chcp 850
keyb br,,c:\dos\keyboard.sys
4) Reboot the server.
2.10 SCMD.NLM Load Parameter
In order to load SCMD.NLM on NetWare 4, use the
gateway option:
LOAD SCMD.NLM /G
2.11 PPPTSM Load Failure Error
PPPTSM.NLM may fail to load because dependant modules
are not present. The following messages are displayed
at the console:
Modules PPPTSM cannot be loaded until SPOOFER is loaded
Modules PPPTSM cannot be loaded until NLZS is loaded
Modules PPPTSM cannot be loaded until PRED is loaded
Modules PPPTSM cannot be loaded until CMPSUPER is loaded.
To resolve this issue, restore the PPPTSM.NLM from
your backup directory or download the ODIWAN1.EXE
patch from support.novell.com and copy the PPPTSM.NLM
file, dated 17 Jun 1997, version 3.21d, to your
SYS:SYSTEM directory.
2.12 Remote Boot
The files RPL.NLM, RBOOT.RPL, and TOKEN.RPL are not
included in this Support Pack. These files are
available from the Novell Support Connection WEB site
and the Novell Support Connection CD. They are found
in RPLKT5.EXE.
3.0 Tips
3.1 Installing Protocol Updates
To ensure that the server protocols are updated on
your server, the MultiProtocol Router v3.1 must be
listed as an installed product.
3.2 Resolving LOADER Error
When the Support Pack is installed, SERVER.EXE will
be updated with the current version of LOADER.
Occasionally, 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.
To resolve the error:
1) Scan for viruses on the DOS boot drive of the 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.
2) Rename SERVER.OLD (or MSERVER.OLD if running NetWare SFT
III) to SERVER.EXE (or MSERVER.EXE).
3) RUN LSWAP.EXE.
Syntax
LSWAP <LoaderFilePath> <ServerFilePath>
where Default LoaderFilePath =
C:\NWSERVER\LOADER.EXE and Default
ServerFilePath = C:\NWSERVER\SERVER.EXE (or
MSERVER.EXE)
Example
LSWAP C:\NWSERVER\LOADER.EXE
C:\NWSERVER\SERVER.EXE
4) Run the newly modified SERVER.EXE (or MSERVER.EXE)
program.
3.3 NetWare for OS/2
In NetWare for OS/2, when the Support Pack is
installed, you might see the following 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."
To resolve the error:
1) Manually copy LOADER.EXE and LSWAP.EXE to the boot
directory, usually C:\NWSERVER. (LOADER.EXE and LSWAP.EXE
are located in the PK411 directory.)
2) At the OS/2 window, run LSWAP.EXE. (This only needs to be
run once.) Enter LSWAP LOADER.EXE SERVER.EXE.
3.4 Resolving a Server Boot Failure
If, for some reason, the server fails to boot after
the installation, then you will need to rename the
SERVER.OLD file manually to SERVER.EXE to bring the
server back up.
3.5 Installing the Support Pack if DOS Is Removed
If you have removed DOS at the server, you must
restart the server with DOS active in order to
install the Support Pack. This is because files
cannot be copied to the DOS partition unless DOS is
active. If the AUTOEXEC.NCF file contains the REMOVE
DOS command, comment out that line and restart the
server.
3.6 Remote Boot and RPL
Remote Boot and RPL do not work with the Task 0 fix
located in the PK411.NLM patch. For more information,
see TID 2930738 at http://support.novell.com.
3.7 LAN Driver Issues
If the Install Driver Update for DISK, LAN, WAN
option is selected during installation, it may cause
the LAN communication to fail. Not all LAN drivers
are v3.31 compliant. Before selecting this option,
verify the compatibility of your driver with the LAN
driver vendor.
3.8 NBI.NLM Issue
If the server abends while the disk drives are
loading, you will need to use an earlier version of
NBI.NLM.
3.9 GroupWise 5.5 and NetWare Administrator 32
Installing GroupWise 5.5 after the Support Pack
installation installs an older version of the NetWare
Administrator 32 files. To restore the current
version of NetWare Administrator 32, reinstall
NetWare 4 Support Pack 9.
3.10 Additional Information about the Install Program
- The Support Pack files are copied to the server.
- LSWAP updates SERVER.EXE automatically with a new
LOADER.EXE.
- A record is added to the Btrieve PRODUCTS.DAT file, in
the "Installed Products" section, and the following appears:
"v9.0 Support Pack for NetWare 4.2/4.11." Any other product
updates are also listed.
3.11 Server Configuration Changes
The Support Pack installation detects the current
server configuration and installs the appropriate
files. If the server configuration is changed -- for
example, from NetWare SFT III to NetWare 4 -- you
will need to reinstall the Support Pack for the new
configuration.
3.12 Support Pack Testing
Novell has tested the Support Pack with the following
Novell products or services: NetWare for SAA v4.0,
UNIX Print Services v2.3, ManageWise v2.6, NetWare IP
v2.2, NFS v2.3, GroupWise v5.5 & v5.2, NetWare
Connect v2.0, SBACKUP.NLM (tested for any SMS-
compliant backup), Novell Internet Access Server v4.1
(includes MPR 3.1E), BorderManager v3.0 and v3.5, and
ZENworks v2.0.
Novell has encouraged third parties to test their
products with the Support Pack by providing them with
a beta copy and advance notice of the release
schedule.
3.13 IP Compatibility
NetWare IP and pure IP compatibility updates are
installed by the Support Pack. IP configuration
information is located in the June 19 99 Appnotes
article "Migration Stratergies for Upgrading IPX and
NetWare/IP networks to Pure IP," which can be located
at:
http://developer.novell.com/research/appnotes
/1999/june/a3frame.htm
3.14 Uninstalling the Support Pack
If you select the backup option during the
installation, files that will be overwritten by
installing the Support Pack are backed up to
SYS:SYSTEM\BACKSP9.
The server can be restored to its original state by
completing the following steps.
WARNING: Do not do the following if any products or
patches have been installed after the installation of
the Support Pack.
During the Support Pack installation, the backup
option must have been selected.
1) At the server console prompt, enter LOAD INSTALL.
2) Select Product Options > Install a Product Not Listed.
3) Press F3, then specify the path to the backup files,
SYS:SYSTEM\BACKSP9.
4) To use the backed-up configuration files, rename
STARTUP.PT and AUTOEXEC.PT to STARTUP.NCF and AUTOEXEC.NCF.
If Policy Manager errors occur after uninstalling the
Support Pack, complete the following steps:
1) In NetWare Administrator, delete the LSP configuration
object: NLS_LSP_"Servername" (for example, NLS_LSP_Novell).
2) If a version 5 license was installed before running the
Uninstall program, then reinstall the version 4 license.
3) Run SETUPNLS.NLM at the system console.
3.15 Y2K Fixes in the Support Pack
The Y2K fixes listed below were also included with
IWSP6a and later. If your NetWare 4.11 server has
IWSP6a or later, then your NetWare 4.11 server is
already completely Y2K-compliant.
RCONSOLE.EXE
When selecting the directory scan option, the year as
indicated by the file creation date displays as 100
instead of 00, 134 instead of 34, etc.
UIMPORT.EXE
Failed to properly create expiration dates for both
passwords and accounts when the dates are greater
than 1999.
NWVQUE3X.DLL
Unable to defer printing in NWADMIN.EXE to any date
after the year 1999.
NWVQUE95.DLL
Unable to defer printing in NWADMIN.EXE to any date
after the year 1999.
MENU.OVL
In the NMENU program, the only incorrect date is
found by pressing F2 and viewing the "Logged On
Since" parameter. Logged In Since Date displays the
year as 100 for 2000, 134 for 2034, etc.
VNETWARE.SYS
After the date rollover from 12/31/1999 to
01/01/2000, the OS/2 system date is rolled back to
1980.
4.0 Files in the TOOLS Directory
The files located in the TOOLS directory are not
installed automatically; they must be installed
manually.
4.1 NetWare SFT III
SFTDPPSM.NLM is copied to the TOOLS directory.
NetWare SFT III users with two processors in each
machine need to copy SFTDPPSM.NLM manually to the
server boot directory, usually C:\NWSERVER. This only
works with the MPS14.PSM module, which is written to
the Intel MPS 1.4 specification.
4.2 NE3200.COM
The NE3200.COM file is copied to the TOOLS directory.
If you are installing a NetWare 4.11 server
containing a Novell NE3200 network board across the
network, you need this updated LAN driver to prevent
the server installation from hanging.
4.3 Modem Support
For updates for server modem support, copy the files
MODEMS.INF, AIOMDMS1.MDC, AIOMDS2.MDC, and
NLABSMDM.MDC to the server SYS:\SYSTEM directory.
4.4 Using Novell Client on NEC PC9800 Series or Fujitsu FMR
If your NEC PC9800 or Fujitsu FMR VLM clients hang
because a resident program was loaded before the
NWP.VLM, replace NWP.VLM with the appropriate version
of NWP.VLM. To update NWP.VLM, complete the
following:
1) Rename the NWP.VLM in the VLM client directory, NWCLIENT.
2) Copy the appropriate file to the NWCLIENT directory. For
NEC PC9800 use NWP.VLM located in the TOOLS\PC98 directory,
and for Fujitsu FMR use the file in TOOLS\FMR.
4.5 NPRINTER
Printouts may become corrupt if a printer is
connected to a workstation and shared via a NetWare
queue using NPRINTER.EXE. This can be resolved with
IPX.NLM and NPRINTER.EXE.
The IPX.NLM program is runs with the latest version
of Novell Client 32 for DOS/Windows (v2.71). Copy
IPX.NLM from \TOOLS\NPRINTER to
C:\NOVELL\CLIENT32\IPX.NLM on the workstation. The
NPRINTER.EXE is automatically copied to the server's
SYS:PUBLIC directory.
|
