NetWare 4.2 Release General Readme File v1.3
March 1999

================================================================


Table of Contents

1.0  PRINTING THIS README

2.0  NETWARE SERVERS

     2.1  Installation Prerequisites 

     2.2  Installation Procedure

     2.3  Installation Issues
          2.3.1   Ensuring that the DOS PATH Statement Includes
                  the DOS OS Directory
          2.3.2   Installing from a NetWare Volume
          2.3.3   Installing from CD-ROM 
          2.3.4   Installing Across the Network Using NetWare
                  Client 32 for DOS and Windows 3.1x
          2.3.5   If a Remote Install Hangs
          2.3.6   Selecting Additional ASPI NLM Files for Some
                  Disk Drivers
          2.3.7   Ensuring Autodetection Hardware Support 
          2.3.8   Updating the LSP Default Size

     2.4  Upgrade/Migration Issues
          2.4.1   Ensuring Adequate Disk Space
          2.4.2   Upgrading NetWare 4.1 SFT III Servers
          2.4.3   Upgrading Disk Drivers Using the Upgrade
                  Option in the Installation Program
          2.4.4   Replace ISADISK.DSK with IDEATA.HAM Device
                  Driver
          2.4.5   Purging Deleted Files Before Upgrading

     2.5  Other Server Issues
          2.5.1   NetWare Server
          2.5.2   SMP
          2.5.3   LAN Drivers
          2.5.4   Installing Disk Driver for BusLogic (Mylex)
                  Flashpoint Host Bus Adapter
          2.5.5   IPXRTR
          2.5.6   SFT III

3.0  NOVELL CLIENTS

     3.1  Novell Client Software

     3.2  SCMD Gateway on a 4.2 Server Using a IP CMD Windows NT
          Client

4.0  UTILITIES

     4.1  NetWare Administrator

     4.2  NDS Manager
          4.2.1   Refreshing the Screen Display after a Move
                  Partition Operation
          4.2.2   Running NDS Manager (NDSMGR32.EXE)
          4.2.3   Accessing the NetWare 4.2 NDS Manager from a
                  Client Workstation

     4.3  NCOPY Backwards Compatibility

     4.4  Using the Execute Only Option in FLAG

     4.5  Setting the Correct Operating Language for 32-bit
          Utililties in Windows 95/98

     4.6  Running RCONSOLE in a Windows Environment

5.0  NDS ISSUES

     5.1  NetWare 5 Compatibility

     5.2  Installing a Server Object into a Directory Tree with
          an Existing Server Object of the Same Name

     5.3  NDS Schema Modification Errors During NetWare 4.2
          Installation

     5.4  Resolving NDS Traffic with RIP and SAP Filtering

     5.5  Increasing the Default Setting for IPX Sockets

     5.6  Merging Directory Trees that Have Auditing Enabled at
          the [Root]

     5.7  Merging NetWare 4.x Trees with NetWare 5 Trees

6.0  DATA PROTECTION SERVICES

     6.1  SFT III
          6.1.1   Using SFT III for HardWare Fault Tolerance
          6.1.2   Fixing Problems Related to MSEngine Abend when
                  Receiving an "MSEngine Produced Different
                  Outputs" Message
          6.1.3   Ensuring Hardware Certification
          6.1.4   Balancing the LAN Channel Speed to the MSL
                  Channel Speed
          6.1.5   Identifying Scalability Issues with SFT III 
          6.1.6   Determining Which Products Are Supported on
                  SFT III Servers
          6.1.7   Copying SFT III Files to Diskette
          6.1.8   Using EDIT.NLM on an SFT III Server

     6.2  Backup

7.0  FILE SERVICES ISSUES - Volumes on removable Media

8.0  PRODUCT DOCUMENTATION CHANGES

     8.1  Utilities Reference
          8.1.1   NLIST Documentation 
          8.1.2   Using Register Memory

     8.2  Auditing the Network
          8.2.1   Chapter 4, "Using AUDITCON for Volume
                  Auditing"
          8.2.2   Chapter 5, "Using AUDITCON for Container
                  Auditing"
          8.2.3   Chapter 6, "Using AUDITCON to Audit External
                  Audit Trails"

     8.3  Supervising the Network
          8.3.1   Setting Up NetWare Administrator on a Windows
                  95/98 Workstation
          8.3.2   Trustee Assignments vs. Security Equivalence
          8.3.3   User Template
          8.3.4   Partition Operations

     8.4  Features Guide
          8.4.1   NetWare Administrator and NETADMIN
          8.4.2   Managing Multiple Trees
          8.4.3   Setting Properties for Multiple Users at the
                  Same Time

9.0  ISSUES WITH OTHER PRODUCTS 

     9.1  Global MHS Support in NetWare 4.2

     9.2  ManageWise 2.1 and 2.0

     9.3  Multiple Protocol Router (MPR) 3.0 incompatibility
          with NetWare 4.2

     9.4  Novell Licensing Services (NLS) in a NetWare 4.2 /
          NetWare 5 mixed environment

     9.5  NDPS 1.0 Issues

     9.6  Oracle8 for NetWare Installation Steps

     9.7  Installing Other Products After NetWare 4.2 is
          Installed

     9.8  Running NetWare 4.2 in a language other than English
          with NFS installed

10.0 REQUIRED PATCHES FOR RUNNING OTHER PRODUCTS WITH NETWARE
     4.2

11.0 NOVELL SUPPORT CONNECTION

12.0 TRADEMARKS

     12.1 Novell Trademarks

     12.2 Third-Party Trademarks

13.0 DISCLAIMER AND COPYRIGHT


================================================================





1.0  PRINTING THIS README

     To print this file and any other text files on the CD from
     a workstation to a local printer, do the following: 

     1.   (Conditional) If CD-ROM reader is connected locally:

          a.  Set up the CD-ROM reader (see instructions
              included with the CD-ROM device).

          b.  Change to the CD-ROM drive. 

          c.  Change the directory to the CD root or other
              directories containing readme files.

          (Conditional) If the CD-ROM reader is connected to a
          server:

          a.  Mount the CD-ROM reader as the NetWare volume
              "NW42:"

          b.  Log in to the network and map a drive to the NW42:
              volume and the directory containing the readme
              file that you want to print.

     2.   At the DOS prompt, type "COPY filename PRN" and press
          <Enter>.

          For example, type

                  COPY README.TXT PRN <Enter>





2.0  NETWARE SERVERS

     The following server types are provided in this release of
     NetWare 4.2: Native, SMP, and SFT III. 

     You can install each of these server types directly from
     the CD-ROM.


     2.1  Installation Prerequisites 

          -   Set up a CD-ROM reader as a DOS device (see
              instructions included with CD-ROM device). Boot
              the machine up to the **DOS prompt. Change to the
              CD-ROM drive.

              or

          -   Load the driver for the CD-ROM reader. Load
              CDROM.NLM. Type "CD MOUNT device_number" or "CD
              MOUNT volume_name" and press <Enter>. (For a
              listing of device numbers or volume names, type
              "CD HELP".)


     2.2  Installation Procedure

          1.  Insert the CD into the CD-ROM reader.

          2.  Type "INSTALL" and press <Enter>.

              INSTALL.NLM copies all files to their appropriate
              directories.

          IMPORTANT:  Autodetection for some LAN and disk
                      drivers exists in this release. Because of
                      this, the process for selecting LAN and
                      disk drivers might change from previous
                      NetWare installations for your particular
                      configuration.


     2.3  Installation Issues


          2.3.1   Ensuring that the DOS PATH Statement Includes
                  the DOS OS Directory

                  The DOS operating system directory must be in
                  the current PATH before running the server
                  installation program. This is because the
                  server installation program needs access to
                  the MORE command line utility to display
                  readme file information. If the MORE command
                  is not available, the installation program
                  will issue the following message: 

                          "Bad Command or Filename."


          2.3.2   Installing from a NetWare Volume

                  The drive mapping to the NetWare volume you
                  are installing from must be mapped to the root
                  directory. Use the MAP ROOT command to set the
                  appropriate drive mapping.


          2.3.3   Installing from CD-ROM 

              2.3.3.1 Ensuring that the DOS Path Includes the
                      DOS OS Directory

                  The DOS operating system directory must be in
                  the current PATH statement before attempting
                  to install from the CD-ROM. If the DOS
                  operating system directory is not included,
                  you might receive the following message upon
                  running the installation program:

                          "Bad Command or Filename."

              2.3.3.2 Unloading the CDROM.NLM After Installation

                  After completing the installation from CD-ROM,
                  reboot the server or reload CDROM.NLM. If you
                  don't reboot, you will not have access to any
                  of the CDROM.NLM command line functions.


          2.3.4   Installing Across the Network Using NetWare
                  Client 32 for DOS and Windows 3.1x

                  If you are using NetWare Client 32 for DOS and
                  Windows 3.1x to install the server across the
                  network, you may experience server load
                  failure or volume mount failure due to low
                  memory.

                  If this condition occurs, edit the following
                  line in the NET.CFG file:

                          NETWARE DOS REQUESTER
                            MAX CACHE SIZE = 1024

                  This will reduce the amount of memory used by
                  Client 32 software for caching. Do not set the
                  value to zero (0). Zero specifies that
                  CLIENT32.NLM should dynamically configure the
                  amount of memory used for caching.


          2.3.5   If a Remote Install Hangs

                  When installing across the network (instead of
                  from a local CD), some machines will hang due
                  to problems with shared interrupts and might
                  display a "CPU Hog" message. The installation
                  on these machines will need to be completed
                  using the CD.


          2.3.6   Selecting Additional ASPI NLM Files for Some
                  Disk Drivers

                  If you are installing disk drivers (.DSK)
                  rather than a .HAM driver, the ASPI layer will
                  not be autoloaded. You should ensure that all
                  of the correct files have been selected
                  following the installation programs attempt to
                  autodetect the driver. Some of the ASPI NLM
                  programs are not autodetected by the
                  installation program.


          2.3.7   Ensuring Autodetection Hardware Support 

                  The following are NBI.NLM hardware support
                  requirements:

                  1.  PC Card (PCMCIA) Support Requirements: 

                      a.  DOS card and socket services

                      b.  DOS configurator (card services client
                          that does resource allocation for the
                          hardware, such as interrupt and I/O
                          port)

                  2.  PnP ISA (Plug and Play ISA) Support
                      Requirements:

                      a.  DOS PnP ISA Configuration Manager
                          (Intel's DOS/WIN 3.1 Configuration
                          Manager)

                      b.  PnP ISA BIOS (Non-PnP OS option)

                      NOTE: Most EISA machines do not support
                      either set of requirements.


          2.3.8   Updating the LSP Default Size

                  The default size for Link State Packets (LSPs)
                  on an IPX network has been changed from 512 to
                  1024 bytes. The server installation program
                  automatically updates all servers, except for
                  SFT III servers, with this new default
                  setting. To configure this parameter for SFT
                  III servers or other servers, change the LSP
                  size under the IPX heading in "Protocols"
                  using INETCFG.

                  See "How to Change the LSP Size" in Contents >
                  Network Services > Connectivity Services >
                  Routing Configuration > Configuring NLSP on
                  the Online Documentation CD for more
                  information.


     2.4  Upgrade/Migration Issues


          2.4.1   Ensuring Adequate Disk Space

                  The NetWare 4.2 server installation currently
                  requires a minimum of 40 MB of disk space in
                  the DOS partition. You should ensure that you
                  have the recommended minimum of 175 MB of disk
                  space for volume SYS: before upgrading to
                  NetWare 4.2.


          2.4.2   Upgrading NetWare 4.1 SFT III Servers

                  You should perform the following procedures if
                  either of the following two conditions exist:
                  You are upgrading a server from NetWare 4.1
                  SFT III to NetWare 4.2 SFT III and are using
                  name spaces other than DOS on your volume; or,
                  you are loading NLM programs that load
                  CLIB.NLM in the IOAUTO.NCF file.

                  1.  If you are using name spaces other than
                      DOS, copy all of the *.NAM files from the
                      NetWare 4.2 CD to the SYS:SYSTEM directory
                      on the NetWare 4.1 SFT III server before
                      performing the upgrade.

                      If you don't perform this procedure, the
                      following will occur:

                      a)  An error is issued stating that the
                          phantom public symbol cannot be found
                          during an upgrade.

                      b)  The volume that the name spaces are
                          loaded on will not mount.

                  2.  If you are using CLIB modules or if you
                      load any NLM programs that autoload the
                      CLIB modules the IOAUTO.NCF file (such as
                      INETCFG.NLM, TCPIP.NLM, or management
                      agents), first copy the following files to
                      the SYS:SYSTEM directory on the NetWare
                      4.1 SFT III server before performing the
                      upgrade: CLIB.NLM, THREADS.NLM, NIT.NLM,
                      NLMLIB.NLM REQUESTR.NLM, FPSM.NLM,
                      MATHLIBC.NLM, and MATHLIB.NLM.

                      If are using a product that loads in the
                      IOAUTO.NCF file and that uses a version of
                      DSAPI.NLM dated prior to February 1995,
                      you must also copy the following files to
                      SYS:SYSTEM: DSAPI.NLM, AUDNLM32.NLM,
                      CALNLM32.NLM, CLNNLM32.NLM, CLXNLM32.NLM,
                      LOCNLM32.NLM, NCPNLM32.NLM, and
                      NETNLM32.NLM.

                      NOTE:   You can also load and bind LAN
                              drivers in the IOAUTO.NCF file and
                              comment out other products in
                              IOAUTO.NCF file during the
                              upgrade.

                      If you don't perform this procedure before
                      upgrading, you will see error messages
                      stating that the NLM programs that use
                      CLIB modules did not load because the
                      symbols were not available. However, if
                      you bring down the upgraded server and
                      bring back the server pair, this problem
                      will not exist.

                  3.  During the upgrade from NetWare 4.1 SFT
                      III or NetWare 3.11 SFT III to NetWare 4.2
                      SFT III, you might not have enough disk
                      space on the SFT III diskettes. Before
                      copying NetWare 4.2 SFT III files to
                      diskettes for setting up the second
                      server, you should ensure that all
                      unnecessary .MSL driver files are deleted
                      from the first server's NetWare 4
                      directory (default is C:\NWSERVER). If
                      not, you might encounter a "disk full"
                      error when copying SFT III files to
                      diskette. 


          2.4.3   Upgrading Disk Drivers Using the Upgrade
                  Option in the Installation Program

                  If you are using the "Simple" or "Custom"
                  installation, this operation is not necessary,
                  because the old STARTUP.NCF file is
                  overwritten by the updated one and is
                  configured correctly.

                  The slot number, required by "HIN-aware"
                  drivers written specifically for NetWare 4.11,
                  is formulated differently from the driver
                  supplied in NetWare 4.10, so the slot number
                  defined in STARTUP.NCF will probably be
                  incorrect for the upgrade driver.

                  As you perform the upgrade installation
                  option, INSTALL attempts to load the new
                  driver, but with the old slot number specified
                  in STARTUP.NCF. INSTALL displays a warning,
                  indicating the driver failed to load.

                  Perform the following procedure to complete
                  the loading of a disk driver during an
                  upgrade:

                  1.  Press <Alt+Esc> to switch to the main
                      console screen.

                      The console displays the correct slot
                      number at the prompt.

                  2.  Write down this value and press <Enter>.

                      The driver will now load properly.

                  3.  Switch back to the installation screen and
                      choose "Continue Installation."

                  4.  Once installation is complete, you should
                      edit the STARTUP.NCF file before rebooting
                      the server.

                      To edit the STARTUP.NCF file, use the
                      following procedures:

                      4a. Load INSTALL.NLM.

                      4b. From the options menu, choose "NCF
                          Files Options."

                      4c. Choose "Edit STARTUP.NCF File."

                      4d. Specify the path for the server boot
                          directory.

                      4e. Edit the line that loads the disk
                          driver, and change the slot number to
                          the value you wrote down earlier.

                          You should do this for each host bus
                          adapter that applies.

                      4f. Save and exit the STARTUP.NCF file.

                      4g. Exit INSTALL, bring down the server,
                          and then restart the server.


          2.4.4   Replace ISADISK.DSK with IDEATA.HAM Device
                  Driver

                  When upgrading from NetWare 3.x to NetWare
                  4.2, it is recommended that machines using the
                  ISADISK.DSK device driver be upgraded to use
                  the IDEATA.HAM driver--the currently supported
                  replacement driver.

                  During the upgrade process, delete ISADISK.DSK
                  as the preferred device driver and insert the
                  IDEATA.HAM device driver. If this is not done,
                  the installation may not complete
                  successfully.


          2.4.5   Purging Deleted Files Before Upgrading

                  Before upgrading an existing server, you
                  should purge the deleted files from volume
                  SYS: by using PURGE from a workstation. If you
                  do not purge the deleted files, you will
                  receive an incorrect report of the free space
                  available in volume SYS:.


     2.5  Other Server Issues


          2.5.1   NetWare Server

              2.5.1.1 Configuring for Systems with More than 1
                      GB of Memory

                  If your server is equipped with more than 1 GB
                  of memory, you should ensure that the "CPU Hog
                  Detection" setting is set to two minutes
                  instead of one minute. You should ensure that
                  this setting is made in the STARTUP.NCF file.

              2.5.1.2 Booting a Server When Running HIMEM.SYS

                  A problem exists when booting a server that
                  has HIMEM.SYS loaded. When booting the server,
                  the following error might be displayed:

                          "Attempt to auto-register memory above
                          16 megabytes failed"

                  If the server contains more that 16 MB of
                  memory, the error messages is probably
                  invalid. You can check the amount of memory by
                  running MEMORY at the server console. If the
                  error message is invalid, you should comment
                  out the DEVICE=HIMEM.SYS" in the CONFIG.SYS
                  file to prevent it from loading.


          2.5.2   SMP

              2.5.2.1 Undocumented SMP Parameters

                      "SMP interrupt affinity" ON/OFF
                          Default: OFF

                          If set to ON, this parameter
                          associates LAN driver interrupts with
                          specific processors. For example, if
                          there are four network boards, the
                          first interrupt is assigned to the
                          first processor, the second to the
                          second processor, and so on. If set to
                          OFF, the interrupts float freely
                          across processors.

                      "SMP display spurious interrupts alerts"
                      ON/OFF
                          Default: OFF

                          This parameter controls alert messages
                          about spurious interrupts. Spurious
                          interrupts occur when a hardware
                          interrupt is generated in the server
                          and none of the device drivers that
                          have registered for that interrupt
                          accept responsibility for handling it.
                          Spurious interrupts can also occur
                          when the BIOS contains invalid
                          information about interrupt polarity.

                      SMP spurious interrupts generate the
                      following message:

                          "SMP WARNING: (#) Spurious hardware
                          interrupt(s)<number> detected on INT
                          (#)."

                          This message indicates a serious error
                          in the hardware. 
                          
                          If your server console displays this
                          message, remove all add-on boards and
                          run SERVER. If the message doesn't
                          appear after you've removed the
                          boards, add the boards one at a time
                          to determine which board caused the
                          spurious interrupt, then contact the
                          vendor. Set the parameter to OFF while
                          you are waiting for a resolution.

                      IMPORTANT:  If you receive a large number
                                  of spurious interrupts, it
                                  might indicate that the
                                  problem is not with a device
                                  driver but with the MP tables
                                  in the BIOS. Contact the BIOS
                                  manufacture for a BIOS
                                  upgrade.

                      NOTE:       You can set SMP parameters in
                                  the AUTOEXEC.NCF file. SMP set
                                  parameters cannot be set in
                                  the STARTUP.NCF file.

              2.5.2.2 Unloading the MPDRIVER

                  If you plan on unloading and then reloading
                  the MPDRIVER on an SMP server, first add the
                  "SET SMP Flush Processor Cache = ON" parameter
                  setting to the AUTOEXEC.NCF file.

              2.5.2.3 Loading LAN and Disk Drivers with the Same
                      Interrupt

                  You might experience problems loading .LAN
                  drivers with the same interrupt as a disk
                  driver with a .DSK extension. If you are
                  loading LAN drivers with DSK drivers on the
                  same machine, you should ensure that the same
                  interrupt is not being used. (The server will 
                  probably function properly if the same
                  interrupt is used; however, you should be
                  aware that problems might occur.)


          2.5.3   LAN Drivers

              2.5.3.1 Using 3.30 AHSM or Above or 1.11 CHSM or
                      Above Specification LAN Drivers

                  The LAN drivers available in this release have
                  been updated to the 3.30 AHSM or above or the
                  1.11 CHSM or above specification. 

                  If you are using a network board that is not
                  listed in the LAN driver listing in the server
                  installation program, contact the manufacturer
                  for information concerning availability of a
                  3.30 AHSM or above or 1.11 CHSM or above
                  specification driver for NetWare. Some 3.2
                  specification drivers can operate on NetWare
                  4.11 or above, but Novell cannot ensure the
                  reliability of those drivers.

              2.5.3.2 Installing PCI LAN Hardware Using the
                      "Upgrade" Option in INSTALL

                  The slot number required by some new LAN
                  drivers is formulated differently from that of
                  the driver supplied in NetWare 4.10. If you
                  have PCI-based LAN hardware in your server,
                  you may need to correct the slot number in the
                  AUTOEXEC.NCF when using the "Upgrade" option
                  in INSTALL. This is only necessary for some of
                  the LAN drivers that have been updated for
                  NetWare 4.2 and are "HIN-aware."

                  Also, a system that loads a WAN (wide area
                  network) driver may need to be modified in a
                  slightly different manner. Verify this by
                  viewing the AUTOEXEC.NCF file to see if the
                  INITSYS.NCF file is executed therein. If so,
                  and if a PCI LAN adapter is also installed,
                  you may need to load the INETCFG.NLM program
                  and edit the slot number from there for the
                  LAN driver.

                  NOTE:   If you are using the "Simple" or
                          "Custom" installation option, the
                          following procedure will not be
                          necessary.

                  As you perform the Upgrade installation
                  option, INSTALL attempts to load the new
                  driver, but with the old slot number specified
                  in the AUTOEXEC.NCF file. INSTALL displays a
                  warning, indicating the driver failed to load.
                  Complete the following steps to correct the
                  problem and load the new driver. If two or
                  more network boards are installed, you need to
                  complete each step for each driver that has a
                  loading error.

                  1.  Press <Alt+Esc> to switch to the main
                      console screen.

                      The console displays the correct slot
                      number at the prompt. If there is more
                      than one network board in the system,
                      there should be an equal number of
                      possible slot numbers displayed.

                  2.  Write down the value and press <Enter>.
                      The driver will now load properly.

                  3.  Switch back to the installation screen and
                      choose the "Continue Installation" option.

                  4.  Once installation is completed and before
                      rebooting the server, load INSTALL.NLM and
                      select the "NCF Files Options," then "Edit
                      AUTOEXEC.NCF file."

                  5.  Edit the line that loads the LAN driver
                      and change the slot number to the value
                      you wrote down earlier.

                  6.  Save and exit the STARTUP.NCF file.

                  7.  After editing and saving the AUTOEXEC.NCF
                      file and exiting INSTALL, bring down the
                      server and restart it to make the changes
                      effective and to load the new driver(s).


          2.5.4   Installing Disk Driver for BusLogic (Mylex)
                  Flashpoint Host Bus Adapter

                  The FLASHP4X.DSK driver used with the BusLogic
                  (Mylex) Flashpoint host bus adapter operates
                  reliably on all NetWare 4.2 server platforms
                  except NetWare SFT III. When the driver is
                  loaded on a NetWare SFT III server, it
                  frequently causes the primary IOEngine to
                  abend.

                  You should use the BLGCFP01.HAM driver when
                  using the BusLogic (Mylex) Flashpoint host bus
                  adapter. This driver is the default driver for
                  this host bus adapter and operates reliably on
                  all NetWare 4.2 platforms.


          2.5.5   IPXRTR

                  By default, NetWare 4.2 installs IPXRTR with
                  NLSP support. In some environments this causes
                  a server to not see all servers that it
                  expects to see. Enter the "Display Servers"
                  command from the server's System Console to
                  detect this problem. If the problem exists,
                  unload IPXRTR and use the internal router.


          2.5.6   SFT III

                  When installing SFT III, you may run out of IO
                  Engine memory resources. To avoid this
                  problem, follow these steps.

                  1.  Follow normal installation procedures
                      until you reach the screen that asks, "Do
                      you want to modify, add, or delete any
                      special startup set commands?"

                  2.  Highlight Yes and press Enter.

                  3.  Type the following commands. Numbers shown
                      are minimum values. Use higher values if
                      desired.

                      set new start address for unclaimed memory
                      block = 8912896

                      set new end address for unclaimed memory
                      block = 32997376

                  4.  Press F10 to save and continue.
                          





3.0  NOVELL CLIENTS


     3.1  Novell Client Software

          NetWare 4.2 includes the latest Novell Client
          software. All Client-specific release notes are
          contained on the Novell Client CD.


     3.2  SCMD Gateway on a 4.2 Server Using a IP CMD Windows NT
          Client

          Windows NT clients will be extremely slow (hours in
          magnitude) logging in through a SCMD gateway on a
          NetWare 4.2 server if the preferred tree in the Client
          settings is in some way inaccessible via IPX.

          This is because the Windows NT client tries to make a
          connection to the preferred tree even if an alternate
          tree is entered into the Gina.

          To overcome this problem, perform a "workstation only"
          login, blank out the "preferred tree" field under the
          client tab of the Novell Client for Windows NT
          service, then log in to the network.





4.0  UTILITIES


     4.1  NetWare Administrator

          We recommend that you upgrade all clients on your
          network to the Novell Clients included with NetWare
          4.2 and use SYS:PUBLIC\WIN32\NWADMN32.EXE to perform
          all network administration tasks.


     4.2  NDS Manager


          4.2.1   Refreshing the Screen Display after a Move
                  Partition Operation

                  NDS Manager does not automatically refresh the
                  screen after a move partition operation. Press
                  <F5> to refresh the screen.


          4.2.2   Running NDS Manager (NDSMGR32.EXE)

                  Run NDS Manager as a standalone executable
                  from SYS:PUBLIC\WIN32. 


          4.2.3   Accessing the NetWare 4.2 NDS Manager from a
                  Client Workstation

                  You should use the Novell Client software
                  included in NetWare 4.2 on all client
                  workstations from which you wish to access the
                  NetWare 4.2 NDS Manager for Windows 95/98 and
                  Windows NT (SYS:PUBLIC\WIN32\NDSMGR32.EXE). 


     4.3  NCOPY Backwards Compatibility

          NCOPY version 4.1 will not run in a NetWare 4.2
          environment. You must copy the NCOPY 4.11 version to
          all NetWare servers in your Directory tree. NCOPY 4.11
          will run on NetWare 2, NetWare 3, and NetWare 4
          servers.


     4.4  Using the Execute Only Option in FLAG

          You should ensure that the Execute Only FLAG option is
          used for program files that are run in a DOS
          environment only. You will receive a fatal error in
          Windows if you access a program file that is flagged
          as Execute Only.


     4.5  Setting the Correct Operating Language for 32-bit
          Utililties in Windows 95/98

          Use the following procedure to set the operating
          language for 32-bit utilities in Windows 95/98:

          1.  Click on the Start menu.

          2.  Select "Run..."

          3.  Type REGEDIT.EXE.

          4.  Expand the key "HKEY_LOCAL_MACHINE."

          5.  Expand the key "Network."

          6.  Expand the key "Novell."

          7.  Expand the key "System Config."

          8.  Expand the key "Language."

          9.  Click on the key "NWLANGUAGE."

          10. In the right-hand window, select the text
              "(default)" in the "Name" column.

          11. Enter one of the following values depending on the
              desired language:

                  Language    Value
                  ---------------------
                  English     English
                  French      Francais
                  German      Deutsch
                  Spanish     Espanol
                  Portugues   Portugue
                  Italian     Italiano
                  Korean      Korean
                  Chinese     Chineset
                      (Traditional)
                  Chinese     Chineses
                      (Simplified)
                  Japanese    Nihongo

          12.Click "OK"

          13.Close Registry Editor


     4.6  Running RCONSOLE in a Windows Environment

          You should avoid setting the "Background Always
          Suspend" option in the DOS Properties when running
          RCONSOLE in a Windows environment.





5.0  NDS ISSUES


     5.1  NetWare 5 Compatibility

          General guidelines for installing NetWare 5 in a
          NetWare 4.x tree are listed below. For further
          information, refer to the NetWare 5 documentation and
          Technical Information Document number 2943193 on the
          Novell Support Connection at support.novell.com.

          Before installing a NetWare 5 server into an existing
          NetWare 4.10, NetWare 4.11, or NetWare 4.2 tree, you
          must verify the following three things:

          -   All NetWare 4.10 servers are running NDS version
              5.15 or higher.

              To ensure this, obtain DS410N.EXE from the Minimum
              Patch List located at support.novell.com and
              follow the instructions included with the file.

          -   All NetWare 4.11 servers are running NDS version
              6.00 or higher.

              To ensure this, obtain DS411N.EXE from the Minimum
              Patch List located at support.novell.com and
              follow the instructions included with the file.

          -   All NetWare 4.10 and 4.11 servers must have
              DSRepair version 4.59 or higher, which is included
              with the above-mentioned files.

          Important:  If your NDS tree was originally installed
                      using NetWare version 4.0 or 4.01, you
                      must run DSRepair 4.59 or greater on a
                      NetWare 4.1x server holding the Master or
                      a R/W of the [Root] partition. Select
                      "Repair Local DS Database" under "Advanced
                      Options."

                      If your tree did not start out with a
                      NetWare 4.0 or NetWare 4.01 server, it is
                      not necessary to run this. However, unless
                      you are absolutely certain, we recommend
                      running DSRepair on the Master or a R/W of
                      [Root].


     5.2  Installing a Server Object into a Directory Tree with
          an Existing Server Object of the Same Name

          When you install a NetWare Server object in a
          Directory tree, make sure that no NetWare Server
          object of the same name exists in the same
          internetwork. This includes anywhere in the same tree
          (not just the same context) that the new server is
          being installed into, in addition to any other
          Directory trees or older NetWare 3.1x servers sharing
          the same internetwork (cable).

          Server names are usually transmitted through SAP to
          all other NetWare servers on the same network, thus
          the unique name requirement.

          NOTE:   The internal network address must also be
                  unique within an internetwork.

          If a duplicate name exists outside the tree you are
          installing into, no notification will be given, but
          SAP name collision problems will result. If a NetWare
          Server object of the same name exists in the same
          tree, the installation program prompts you to delete
          the existing NetWare Server object or choose a
          different context. 

          If you choose "Yes" to delete the existing NetWare
          Server object, the installation program deletes the
          object and continues. However, if a "corrupt" NetWare
          Server object exists with the same name, the
          installation program returns to the screen where you
          specify the context to install the server. If this
          condition occurs, you should locate the "corrupt"
          NetWare Server object with NDS Manager or PARTMGR and
          delete it from the Directory tree, and then install
          the server.


     5.3  NDS Schema Modification Errors During NetWare 4.2
          Installation

          When upgrading a server to NetWare 4.2, if the NDS
          schema has already been extended in the tree, errors
          may be returned as INSTALL attempts to modify the
          tree's schema again. (For example, error occurred
          modifying the NDS schema for file
          sys\system\schema\nwadmin.sch, etc.) Ignore these
          errors.


     5.4  Resolving NDS Traffic with RIP and SAP Filtering

          When you manage Novell Directory Services (NDS)
          traffic on your network, don't use RIP filtering and
          do not filter specific SAP types used by NDS. This is
          because NDS uses RIP and SAP protocols (during
          installation or if a server does not hold a replica)
          to communicate during synchronization.

          If you want better traffic management across your
          NetWare network, you should enable NetWare Link State
          Protocol (NLSP). See "Novell Guide to NLSP Migration"
          in the Novell Online documentation for more
          information. 

          WARNING:    You should not enable RIP filtering on
                      network servers running NDS, because NDS
                      uses RIP protocols to communicate during
                      synchronization.

          When filtering specific SAP types, you should be aware
          of the following issues:

          -   SAP type 278 is used by the installation program
              when selecting a Directory tree to install into.
              The SAP type 278 (hex) is also used by NetWare
              client software to discover Novell Directory
              Services on initial bootup (preferred tree). The
              client software reverts to SAP type 4 (for
              preferred server) if 278 is not discovered or if
              no preferred tree is given.

          -   If you want to do additional SAP filtering, you
              may want to use a configured time source. This
              will allow you to eliminate SAP type 26B (hex);
              however, TIMESYNC.NLM relies on SAP type 4, even
              if you have a configured time source.


     5.5  Increasing the Default Setting for IPX Sockets

          If you have a very large Directory tree (approximately
          100 servers or more), and you have one or more servers
          that need to communicate with the 100 or more servers
          at once (if, for example, one server holds replicas of
          every partition in the tree), then you should increase
          the maximum value of IPX sockets that is set during
          installation from the default of 1,200 to a greater
          value.

          Every time an outgoing connection is established,
          three IPX sockets are employed; one socket conducts
          primary NCP packet exchanges, one is used by a
          watchdog timer, and one is used to retrieve messages
          from the server.

          Novell Directory Services (NDS) correctly handles
          closing connections to some servers and making new
          connections to other servers, so operations run
          smoothly even though the value might be too small.
          However, if the value is too small, performance on
          servers that are communicating with 100 or more
          servers in the Directory tree are affected.

          To increase the maximum number of sockets supported on
          a server, use one of the following two methods:

          -   Run SPXCONFG and increase the maximum open IPX
              sockets from 1,200 to a higher value. You must
              reboot the server before the new maximum socket
              number value will take effect.

              You should also make the IPX configuration setting
              permanent by adding the following line in the
              AUTOEXEC.NCF file

                      LOAD SPXCONFG Q=1 I=<n> 

                      where n is the maximum open IPX sockets,
                          between 120 and 65,520

          Or

          -   Complete the following procedure

              1.  Run INETCFG and select "Protocols."

              2.  From the "Protocols Configuration" menu,
                  select "IPX."

              3.  Select "EXPERT Configuration Options."

              4.  Select the "IPX/SPX Parameters" option and
                  then configure the "Maximum IPX Socket Table
                  Size."

              Using this method, the INETCFG program initializes
              the system.

          NOTE:   You should begin by changing the value to
                  2,040 and monitoring for possible errors.


     5.6  Merging Directory Trees that Have Auditing Enabled at
          the [Root]

          The DSMERGE utility requires you to disable auditing
          at the Directory tree [Root] and remove any Auditing
          File objects that were created immediately subordinate
          to the [Root] before starting the merge process. Be
          sure to use the DSMERGE utility from NetWare 4.2, and
          not an older version from NetWare 4.10.


     5.7  Merging NetWare 4.x Trees with NetWare 5 Trees

          To merge a NetWare 4.x tree into a NetWare 5 tree, you
          must first upgrade the server in the tree that
          contains the master replica of the root partition to
          NetWare 5. Then run DSMERGE on that server.

          Note:   If the server holding the master cannot be
                  upgraded, you can select another server to be
                  the master, as long as it is running NetWare 5
                  at the time of the merge.





6.0  DATA PROTECTION SERVICES


     6.1  SFT III


          6.1.1   Using SFT III for HardWare Fault Tolerance

                  NetWare 4.2 SFT III is included in the NetWare
                  4.2 package as an add-on service to the
                  NetWare 4 operating system. It provides a
                  fault-tolerant mirrored-server solution for
                  your network.

                  The main purpose for using SFT III in your
                  network is to ensure continuous access to
                  network servers and server data in case of a
                  single hardware-based server failure.

              6.1.1.1 You should use SFT III for the following
                      reasons:

                  a.  Consolidation

                      Allows you to consolidate servers
                      throughout your network and eliminate
                      single points of failure. By properly
                      implementing SFT III, you can effectively
                      right-size your network.

                  b.  Reduced down time

                      Allows you to reduce server down time when
                      problems occur due to a hardware failure.

                  c.  Online maintenance

                      Allows for limited maintenance and
                      hardware upgrades without interrupting
                      user operations.

                  d.  Disaster prevention

                      Supports disaster prevention techniques of
                      geographically separating fault-tolerant
                      servers at different locations.

              6.1.1.2 SFT III is not useful in the following
                      circumstances:

                  a.  Software fault tolerance

                      Is not a software fault tolerance solution
                      where SFT III masks the presence of faults
                      within the network or application
                      software.

                  b.  Backup

                      Is not a backup and restore solution for
                      disaster conditions.

                  c.  Nonidentical servers

                      Does not support different servers in the
                      primary-secondary configuration. The
                      server hardware/software must be identical
                      for both machines.

                  d.  Symmetrical processing

                      Does not support symmetrical processing
                      environments such as NetWare SMP.


          6.1.2   Fixing Problems Related to MSEngine Abend when
                  Receiving an "MSEngine Produced Different
                  Outputs" Message

                  The MSEngine (secondary server) reboots when
                  receiving an "MSEngine Produced Different
                  Outputs" error message. This has been resolved
                  in a patch that can be obtained through the
                  Novell Support Connection. See "Novell Support
                  Connection" for more information.


          6.1.3   Ensuring Hardware Certification

                  All hardware systems that you use must have
                  been certified with Novell Labs. This includes
                  motherboards, network boards, MSL boards, and
                  drivers. Novell Labs provides certification
                  bulletins that list certified systems
                  available for supporting SFT III.


          6.1.4   Balancing the LAN Channel Speed to the MSL
                  Channel Speed

                  SFT III architecture requires that all
                  information passed to the Primary IOEngine
                  passes through the MSL channel (MSL board).
                  This means that all memory and disk-mirroring
                  information is constantly passed through the
                  MSL board. Because of this, you should ensure
                  that the accumulative amount of traffic passed
                  through the LAN channel (network boards) does
                  not exceed the amount passed through the MSL
                  board.

                  For example, if your server has one 10MB
                  Ethernet board and three 16MB token ring
                  boards totaling an accumulative bandwidth of
                  58 MB, you should install an MSL board that
                  supports a bandwidth greater than 58 MB, such
                  as a 100MB MSL board.

                  It is possible for the server to receive more
                  traffic through multiple network boards than
                  the MSL board can support. This may cause
                  bottlenecks through the MSL channel that
                  result in high server utilization,
                  unresponsive server performance, and IOEngine
                  queue overruns.


          6.1.5   Identifying Scalability Issues with SFT III 

                  The functionality provided by SFT III on
                  NetWare servers assumes a greater level of
                  hardware and environment overhead than non-SFT
                  III NetWare servers (native servers). Because
                  of this, you should consider the difference in
                  scalability of SFT III servers compared to
                  other NetWare servers when considering
                  hardware requirements, client support, and
                  available services from the SFT III servers.

                  SFT III supports dual processor machines based
                  on an asymmetric multiprocessing (ASMP)
                  architecture. Because of the various
                  implementations of ASMP across servers, SFT
                  III servers might not scale as efficiently as
                  non-SFT III servers.

                  Dual processor support on SFT III servers
                  operates on the assumption that one processor
                  in each server is dedicated to the IOEngine
                  and the other processor in each server is
                  dedicated to the MSEngine. SFT III servers
                  split the processing load across the two
                  processors, which greatly improves performance
                  and scalability.


          6.1.6   Determining Which Products Are Supported on
                  SFT III Servers

                  For a list products currently supported on SFT
                  III, contact your Novell reseller or Novell
                  Support Connection. See "Novell Support
                  Connection" for more information.


          6.1.7   Copying SFT III Files to Diskette

                  Before copying NetWare 4.1 SFT III files to
                  diskette for setting up the second server, you
                  should ensure that all unnecessary .MSL driver
                  files are deleted from the first server's
                  NetWare 4 directory (default is C:\NWSERVER).
                  If not, you might encounter a "disk full"
                  error when copying SFT III files to diskette. 


          6.1.8   Using EDIT.NLM on an SFT III Server

                  EDIT.NLM has a new feature that allows you to
                  browse the file system for a file you want to
                  edit. This feature is not supported on the
                  IOEngine of SFT III. You should avoid using
                  the browse feature in EDIT while running on
                  the IOEngine.

                  The new browse feature is fully supported on
                  the MSEngine of SFT III.

                  A page fault can occur when EDIT.NLM is loaded
                  with a volume path at the command line on the
                  IOEngine.

                  For example,

                      LOAD EDIT SYS:\ 

                  This is not a problem if you reference a DOS
                  path such as LOAD EDIT C:\ or if you load
                  EDIT.NLM on the MSEngine.


     6.2  Backup

          When you are backing up a NetWare Client 32 for DOS
          and Windows 3.1x Workstations, TSATIMER.NLM must be
          loaded before TSASMS.COM. If not, the workstation
          might hang and require rebooting. Edit the
          STARTNET.BAT file to ensure that the proper load order
          is used.





7.0  FILE SERVICES ISSUES - Volumes on removable Media

     Use MONITOR to dismount drives before ejecting removable
     media if a NetWare volume is mounted on it. This will
     ensures that the media itself is dismounted on the drive. 

     You should not simply eject the old media and insert new
     media. If you do so, you will receive the following message
     once new media is inserted in the device and a MOUNT VOLUME
     command is issued: 

          "SERVER-4.11-1652: Cannot read volume definition table
          from NetWare partition to invalid drive ID.

          SERVER-4.11-1649: Could not be mounted volume <name>.
          Cannot find some or all volume segment."

     If these error messages result from a MOUNT VOLUME command
     on a removable device, retry the MOUNT VOLUME command
     again. If the mount succeeds, disregard the previous error
     messages. If the problem persists, refer to the
     manufacturer's documentation for more information.





8.0  PRODUCT DOCUMENTATION CHANGES


     8.1  Utilities Reference


          8.1.1   NLIST Documentation 

                  The following command line example:

                      NLIST USER WHERE "ACCOUNT EXPIRATION" LE
                          06-30-96

                  Should appear as: 

                      NLIST USER WHERE "ACCOUNT HAS EXPIRATION
                          DATE" LE 06-30-96.

                  A space must be on both sides of the equal
                  sign in all NLIST commands.


          8.1.2   Using Register Memory

                  For the REGISTER MEMORY utility, the second
                  bullet item under "Using Register Memory" in
                  "Utilities Reference" is incorrect. It says
                  that if you want to run REGISTER MEMORY when
                  you boot the server, you should put the
                  command in the STARTUP.NCF file. The entry
                  then inaccurately describes the STARTUP.NCF
                  file as if it were the AUTOEXEC.NCF file.

                  The text should read as follows:

                  Before using "REGISTER MEMORY," you should use
                  the "Auto Register Memory Above 16
                  Megabytes=ON" SET parameter. This parameter
                  can be placed only in the STARTUP.NCF file. If
                  this parameter does not allow for additional
                  memory to be recognized, then you should use
                  the REGISTER MEMORY command at the server or
                  place it in an .NCF file.

                  If the memory is needed to mount volume SYS:,
                  the command should be added to the STARTUP.NCF
                  file. If the extra memory is not needed to
                  mount volume SYS:, the command line can be
                  added to the AUTOEXEC.NCF file. If the line is
                  added to the AUTOEXEC.NCF file, it should be
                  added before the MOUNT ALL command.


     8.2  Auditing the Network


          8.2.1   Chapter 4, "Using AUDITCON for Volume
                  Auditing"

                  AUDITCON requires Read right on the Audit File
                  Link attribute of the audited volume. This is
                  required where AUDITCON needs to follow the
                  link from the Volume object to the Audit File
                  object and is associated with the following
                  submenus under the Auditing Configuration
                  menu:

                      Audit by Event (Menu 401)

                      Audit Option Configuration (Menu 430)

                      User Restriction (Menu 480)

                  The following notation is a prerequisite to
                  the "Audit by Event," "Audit Options
                  Configuration," and "User Restriction"
                  sections:

                      "You must have the Read right for the
                      Volume object's Audit File Link property
                      for AUDITCON to locate the Audit File
                      object."


          8.2.2   Chapter 5, "Using AUDITCON for Container
                  Auditing"

                  AUDITCON requires the Read right on the
                  Container object Audit File Link attribute of
                  the audited container. This is required where
                  AUDITCON needs to follow the link from the
                  Container object to the Audit File object and
                  is associated with the following submenus
                  under the Auditing Configuration menu:

                      Audit by DS Events (Menu 1401)

                      Audit Options Configuration (Menu 1430)

                      User Restriction (Menu 1480)

                  The following notation is a prerequisite to
                  the "Audit by DS Events," "Audit Options
                  Configuration," and "User Restriction"
                  sections:

                      "You must have the Read right for the
                      Container object's Audit File Link
                      property for AUDITCON to locate the Audit
                      File object."


          8.2.3   Chapter 6, "Using AUDITCON to Audit External
                  Audit Trails"

                  In order to create an external audit trail,
                  the auditor must have additional rights to the
                  Volume object where the external audit data
                  will be stored.

                  The following notation is the fourth
                  prerequisite for "Create External Audit
                  Trail":

                      "You must have the Write right for the ACL
                      property of the Volume object (or the
                      Supervisor right to the Volume object
                      itself) where you will store the audit
                      data. (This can be a temporary assignment
                      that is revoked after the Audit File
                      object is created.)"


     8.3  Supervising the Network


          8.3.1   Setting Up NetWare Administrator on a Windows
                  95/98 Workstation

                  Chapter 1 of Supervising the Network, under
                  "Setting Up Administration Utilities,"
                  recommends using NWADMN95.EXE located in
                  SYS:PUBLIC. 

                  You should use NWADMN32.EXE located in
                  SYS:PUBLIC\WIN32 to perform all network
                  administration tasks.


          8.3.2   Trustee Assignments vs. Security Equivalence

                  In Chapter 1 of Supervising the Network, under
                  "Managing Trustee Assignments to Objects", the
                  example about user KSMITH states that her
                  assignment as a trustee of the MARKETING
                  Organizational Unit overrides any rights she
                  may have received by inheritance or security
                  equivalence. It is true that inherited rights
                  are overridden, but rights received by
                  security equivalence are equal in weight to
                  trustee assignments. In other words, KSMITH
                  will effectively have the rights that were
                  granted by either security equivalence or
                  trustee assignment, and she will be denied
                  only the rights that were denied by both
                  security equivalence and trustee assignment.


          8.3.3   User Template

                  NetWare 4.2 introduces a new class of NDS
                  object called Template to replace the former
                  USER_TEMPLATE object (which is a special
                  instance of the User object class). The
                  NetWare Administrator utility has been updated
                  to reflect this change, but the NETADMIN
                  utility and the manuals have not.

                  For information on the new Template object
                  class, see the NetWare Administrator online
                  help, under "Managing User Accounts." 

                  The following references to user templates in
                  Chapter 1 of Supervising the Network are
                  either incorrect or only partially correct: 

                  -   Tables 1-4 and 1-6 state that Organization
                      and Organizational Unit objects allow you
                      to define user templates. This is true in
                      NETADMIN, but not in NetWare
                      Administrator.


                  -   In NetWare Administrator, Template objects
                      are not associated with a container. Also,
                      Table 1-6 lists the USER_TEMPLATE, but
                      fails to mention the Template object
                      class.

                  -   Under "Creating Container Objects Using
                      NetWare Administrator," an option to
                      define user defaults is mentioned. This
                      option is no longer available as part of
                      the container creation process. You create
                      user templates as separate Template
                      objects.

                  -   Figure 1-3 and Table 1-5 don't include
                      Template in the list of available leaf
                      object classes.


          8.3.4   Partition Operations

                  You should perform all partition operations
                  using the NDS Manager utility (NDSMGR32.EXE)
                  located in SYS:PUBLIC\WIN32.

                  The following references in Supervising the
                  Network are incorrect:

                  -   In Chapter 1 under "Moving Container
                      Objects Using NetWare Administrator,"
                      Steps 3 and 4 should say to select the
                      container in the browser and use the
                      "Move" option on the "Object" menu. You
                      can move only containers that are
                      partitions which do not contain
                      subordinate partitions. 

                  -   In Chapter 1 under "Cautions When Deleting
                      NetWare Server Objects," the second
                      bulleted item should say to use either NDS
                      Manager or Partition Manager to delete NDS
                      servers.


     8.4  Features Guide


          8.4.1   NetWare Administrator and NETADMIN

                  In Chapter 3 of Features Guide, under "NetWare
                  Administrator and NETADMIN," the last two
                  bulleted items mention the "Rename Subtree"
                  and "Move Subtree" options. In NetWare
                  Administrator, the options are called "Rename"
                  and "Move," respectively; they are both on the
                  "Object" menu.

                  Note:   You cannot move container objects
                          using NetWare Administrator.


          8.4.2   Managing Multiple Trees

                  In Chapter 3 of Features Guide, under "NetWare
                  Administrator and NETADMIN," the fourth
                  bulleted item says you can drag and drop
                  Directory objects between trees. This is
                  incorrect. You can drag and drop only files
                  and directories between trees.


          8.4.3   Setting Properties for Multiple Users at the
                  Same Time

                  In Chapter 3 of Features Guide, under "NetWare
                  Administrator and NETADMIN," the fifth
                  bulleted item says you can change property
                  values for multiple users, containers,
                  templates, and groups at the same time.
                  Actually, you can only change property values
                  of multiple users at the same time. You can,
                  however, use containers, templates, and groups
                  as a means of selecting multiple users whose
                  properties you want to change.





9.0  ISSUES WITH OTHER PRODUCTS 


     9.1  Global MHS Support in NetWare 4.2

          Novell supports Novell GroupWise as its messaging
          solution. However, if you need access to the latest
          copy of MHS Services, you can access it on the Novell
          Support Connection. See "Novell Support Connection" in
          this readme for more information. 

          The following MHS products are not supported on
          NetWare 4.2 or any future version of NetWare:

          -   NetWare Global MHS

          -   NetWare MHS v1.5 (NetWare, Multi-Network, and
              Personal Edition)

          -   NetWare Remote MHS

          -   SNADS for NetWare Global MHS

          -   SMTP Protocol Module for NetWare Global MHS

          -   X.400 for NetWare Global MHS

          -   NetWare Global MHS to PROFS Module

          -   Global MHS Access Module


     9.2  ManageWise 2.1 and 2.0

          When running LANalyzer Agents on an SFT III Server,
          you should only run the LANalyzer Agents on one SFT
          III server (IOEngine) at a time. If LANalyzer Agents
          are run on both IOEngines simultaneously, Novell
          Directory Services -625 communication errors will
          appear on the Directory Services Console screen (DS
          Trace screen). 

          After ManageWise is installed, move the LANZ.NCF
          command from the MSAUTO.NCF to the IOAUTO.NCF. If the
          LANZ.NCF command remains in the MSAUTO.NCF file, it
          will incorrectly run LANalyzer Agents in the MSEngine,
          causing the server to abend. The LANalyzer Agents
          should run in the IOEngine.


     9.3  Multiple Protocol Router (MPR) 3.0 incompatibility
          with NetWare 4.2

          Do not install MPR 3.0 on NetWare 4.2. Instead,
          install Novell Internet Access Server 4.1, which
          contains MPR 3.2.


     9.4  Novell Licensing Services (NLS) in a NetWare 4.2 /
          NetWare 5 mixed environment

          Instructions for installing NLS in a mixed environment
          are included in the NetWare 5 product documentation.
          Refer to

              www.novell.com/documentation/

          Click NetWare 5 > Contents > Novell Licensing Services
          > Setting Up > "Installing NetWare 5 into a Mixed
          Environment."


     9.5  NDPS 1.0 Issues

          Refer to the readme included with NDPS for a complete
          list of issues. The following issues are most
          significant for NetWare 4.2.

          -   When installing NDPS 1.0 onto a NetWare 4.2
              server, the following warning message displays:

                      "File [filename] will be downgraded to an
                          older version..."

              At this point, you should select "Never overwrite
              newer files."

          -   Installing NDPS printers to the desktop through
              Add Printer Wizard is not supported in NDPS
              version 1.00. This task is accomplished through
              the Novell Printer Manager utility.

          -   For Client 32 versions 3.5 or higher always use
              SYS:PUBLIC\WIN32\NWADMN32.EXE to administer NDPS
              1.0.

          -   To set up an NDPS printer to service a queue, you
              must run SYS:PUBLIC\WIN95\NWADMN95.EXE using a
              Client 32 version 2.2. Client 32 version 3.5 or
              higher does not support this functionality on NDPS
              version 1.00.

          -   The NWADMN32 user interface shows that the HP
              Gateway can be configured for IP protocol. In NDPS
              version 1.00, the HP Gateway does not support IP
              connectivity.

          -   Windows 3.x desktops using Client versions 3.5 and
              higher can print using NDPS 1.0 but cannot perform
              administrative tasks.


     9.6  Oracle8 for NetWare Installation Steps

          Refer to the readme on the Oracle8 for NetWare CD for
          full installation and configuration information for
          the Oracle8 for NetWare product. The following
          additional information will be useful.

          Before installing Oracle8 for NetWare from a CD volume
          or a normal volume, you must load the long name space
          on the source and destination volumes before running
          install, or the JDBC/ODBC will not install.

          The following steps present a typical CD mount and
          install from the server console and assume an IDE
          controller for the CD:

          1.  Load IDEATA (accept default parameters).

          2.  Load CDROM.

          3.  Enter CD MOUNT ALL (or just o8nw8030).

          4.  Enter ADD NAME SPACE LONG o8nw8030.

          5.  Load INSTALL.

          6.  Choose Product Options.

          7.  Choose Install a Product Not Listed.

          8.  Press <F3> and enter the following path:
              o8nw803:netware\install.

          9.  Follow the install instructions.

          The database startup sequence is:

          1.  Enter ORALOAD (an ncf file)

          2.  Load SVRMGR30

          3.  Enter CONNECT INTERNAL/<password>

          4.  Enter the following command

              STARTUP PFILE=<oracle home>\DATABASE\INITORCL.ORA


     9.7  Installing Other Products After NetWare 4.2 is
          Installed

          Some product installs might overwrite NetWare 4.2
          files with older versions.  After installing other
          products on a NetWare 4.2 server, install the latest
          NetWare 4 Support Pack to ensure your server is
          running the latest files.  


     9.8  Running NetWare 4.2 in a language other than English
          with NFS installed

          If you are running NetWare 4.2 in a language other
          than English, and you have reinstalled Support Pack 6,
          the mapping between the group "world" and the server
          context will be lost.

          To restore the mapping, complete the following steps.

          1.  Enter LANGUAGE

          2.  Note your server's language number.

          3.  Enter LANGUAGE 4

              This switches the server language to English.

          4.  Load UNICON /L NFS

          5.  Follow the UNICON screen instructions to restore
              the mapping.

          6.  Enter LANGUAGE X, replacing X with your server's
              language number obtained in Step 1.





10.0 REQUIRED PATCHES FOR RUNNING OTHER PRODUCTS WITH NETWARE
     4.2

     The latest patches required for running other products on
     NetWare 4.2 are available on the Novell Support Connection
     Web sites and described in a file called Patlst.txt. 

     See the next section, "Novell Support Connection," for more
     information.





11.0 NOVELL SUPPORT CONNECTION

     The Novell Support Connection provides access to Novell's
     networking expertise through the Novell Support Connection
     Web site, the Novell Support Connection CD, and support
     programs for customers and partners.

     By using the Novell Support Connection Web site or CD, you
     can connect to the same networking knowledge used by Novell
     technical support engineers. In addition, the Web site
     provides an open Internet-based forum for customers and
     partners to share technical support information and
     solutions. The forums are staffed by volunteer System
     Operators (SysOps) who are invited and sponsored by Novell
     to answer questions posted in the forums. The Web site also
     offers information on Advanced Technical Training videos,
     CBTs, and conferences.

     For additional support, Novell encourages customers to
     contact a Novell partner. Customers can locate qualified
     partners using the Novell Support Connection Web site.
     Searches are based on geographic location, product
     expertise, or both.

     Visit the Novell Support Connection at:

          support.novell.com (Americas)

          support.novell.de (Europe, Middle East, Africa)

          support.novell.au (Asia Pacific)

     or call:

          Americas (English)      1-800-858-4000/801-861-4000

          Europe, Middle East, 

              Africa (English)    (49) 211 5632 744

          French                  (49) 211 5632 733

          German                  (49) 211 5632 777

          Asia Pacific (English)  (61) 2 9925 3133

     See the Novell Support Connection Web site for a complete
     list of languages and support telephone numbers.

     To order the Novell Support Connection CD, call 1-800-377-
     4136 or 1-303-297-2725 or visit the Novell Support
     Connection Web site.






12.0 TRADEMARKS


     12.1 Novell Trademarks

          Client 32 is a trademark of Novell, Inc.

          Global MHS is a trademark of Novell, Inc.

          GroupWise is a registered trademark of Novell, Inc. in
              the United States and other countries.

          IPX is a trademark of Novell, Inc.

          LAN WorkPlace is a registered trademark of Novell,
              Inc. in the United States and other countries.

          LANalyzer is a registered trademark of Novell, Inc. in
              the United States and other countries.

          ManageWise is a registered trademark of Novell, Inc.

          NDS is a trademark of Novell, Inc.

          NetExplorer is a trademark of Novell, Inc.

          NetWare is a registered trademark of Novell, Inc. in
              the United States and other countries.

          NetWare 3 is a trademark of Novell, Inc.

          NetWare 4 is a trademark of Novell, Inc.

          NetWare Application Launcher is a trademark of Novell,
              Inc.

          NetWare Application Manager is a trademark of Novell,
              Inc.

          NetWare Client is a trademark of Novell, Inc.

          NetWare Connect is a trademark of Novell, Inc.

          NetWare Core Protocol and NCP are trademarks of
              Novell, Inc.

          NetWare DOS Requester is a trademark of Novell, Inc.

          NetWare MHS is a trademark of Novell, Inc

          NetWare/IP is a trademark of Novell, Inc.

          NetWare LANalyzer Agent is a trademark of Novell, Inc.

          NetWare Mobile is a trademark of Novell, Inc.

          NetWare MultiProtocol Router is a trademark of Novell,
              Inc.

          NetWare Telephony Services is a trademark of Novell,
              Inc.

          NetWare Web Server is a trademark of Novell, Inc.

          NLM is a trademark of Novell, Inc.

          Novell is a registered trademark of Novell, Inc. in
              the United States and other countries.

          Novell Authorized Reseller is a service mark of
              Novell, Inc.

          Novell Authorized Service Center is a service mark of
              Novell, Inc.

          Novell Client is a trademark of Novell, Inc.

          Novell Directory Services is a registered trademark of
              Novell, Inc. in the United States and other
              countries.

          Novell Labs is a trademark of Novell, Inc.

          Novell Support Connection is a trademark of Novell,
              Inc.

          PartnerNet is a service mark/trademark of Novell, Inc.

          SFT III is a trademark of Novell, Inc.

          VLM is a trademark of Novell, Inc.



     12.2 Third-Party Trademarks


          Adaptec is a registered trademark of Adaptec, Inc.

          PostScript is a registered trademark of Adobe Systems
              Incorporated.

          AppleTalk and Macintosh are registered trademarks of
              Apple Computer, Inc.

          CompuServe is a registered trademark of CompuServe
              Incorporated.

          DEC is a trademark of Digital Equipment Corporation.

          Pentium is a registered trademark of Intel
              Corporation.

          Microsoft, Windows, and Windows NT are registered
              trademarks of Microsoft Corporation.

          NFS is a registered trademark of Sun Microsystems,
              Inc.

          SAA is a registered trademark of International
              Business Machines Corporation.

          Unicode is a registered trademark of Transoft Ltd.

          UNIX is a registered trademark in the United States
              and other countries, licensed exclusively through
              X/Open Company, Ltd.






13.0 DISCLAIMER AND COPYRIGHT

     EXCEPT AS OTHERWISE RESTRICTED BY LAW, NOVELL DISCLAIMSAND
     EXCLUDES ANY AND ALL IMPLIED WARRANTIES INCLUDING ANY
     WARRANTIES OF MERCHANTABILITY, TITLE, NON-INFRINGEMENT, OR
     FITNESS FOR A PARTICULAR PURPOSE. NOVELL MAKES NO WARRANTY,
     REPRESENTATION OR PROMISE NOT EXPRESSLY SET FORTH IN THIS
     LIMITED WARRANTY. NOVELL DOES NOT WARRANT THAT THE SOFTWARE
     WILL SATISFY YOUR REQUIREMENTS, THAT THEY ARE WITHOUT
     DEFECT OR ERROR, OR THAT THE OPERATION OF THE SOFTWARE WILL
     BE UNINTERRUPTED. Some jurisdictions do not allow certain
     disclaimers and limitation of warranties, so certain of
     these may not apply to You. 

     Non-Novell Products. NOVELL DOES NOT WARRANT NON-NOVELL
     PRODUCTS. ANY SUCH PRODUCTS ARE PROVIDED ON AN "AS IS"
     BASIS. ANY WARRANTY SERVICE FOR NON-NOVELL PRODUCTS IS
     PROVIDED BY THE PRODUCT MANUFACTURER IN ACCORDANCE WITH ANY
     APPLICABLE MANUFACTURER'S WARRANTY.

     Limitation of Liability. EXCEPT AS OTHERWISE RESTRICTED BY
     LAW, NOVELL'S AGGREGATE LIABILITY ARISING FROM OR RELATING
     TO YOUR USE OF THE SOFTWARE OR ANY SERVICES PROVIDED BY
     NOVELL AND/OR ITS AGENTS IS LIMITED TO THE TOTAL OF ALL
     PAYMENTS MADE BY OR FOR YOU FOR THE SOFTWARE. NEITHER
     NOVELL NOR ANY OF ITS LICENSORS, EMPLOYEES, CONTRACTORS, OR
     AGENTS SHALL IN ANY CASE BE LIABLE FOR ANY SPECIAL,
     INCIDENTAL, CONSEQUENTIAL, INDIRECT OR PUNITIVE DAMAGES
     EVEN IF ADVISED OF THE POSSIBILITY OF THOSE DAMAGES.
     NEITHER NOVELL NOR ANY OF ITS LICENSORS, EMPLOYEES,
     CONTRACTORS, OR AGENTS IS RESPONSIBLE FOR LOST PROFITS OR
     REVENUE, LOSS OF USE OF SOFTWARE, LOSS OF DATA, COSTS OF
     RE-CREATING LOST DATA, OR THE COST OF ANY SUBSTITUTE
     EQUIPMENT OR PROGRAM. Some jurisdictions do not allow the
     exclusion or limitation of incidental or consequential
     damages, so portions of the above limitation or exclusion
     may not apply to You.

     Copyright (C) 1998 Novell, Inc. All rights reserved.