              NETWARE CLIENT KIT README (10/12/94)


To print this file to a local printer,

  1. Insert the workstation diskette containing this file into
     drive A: (or B:).
  2. At the DOS prompt, type "A:" (or "B:") and press <Enter>.
  3. At the DOS prompt, type "COPY README.TXT PRN" and press 
     <Enter>.

     NOTE: If you have a postscript printer, import this file into
     a word processing application and print from the application.
------------------------------------------------------------------
Contents

This document contains the following topics about the NetWare
Client for DOS and MS Windows:


1.0 General Information

     1.01 Avoiding Loss of Fake Root Mapping

          Do not use the DR DOS MOVE command. The MOVE.EXE file in
          DOS causes the loss of the fake root mapping, because
          MOVE obtains the current path and attempts to perform a
          CD command on that path.


     1.02 Resolving the NDIR Error in Compaq DOS 5.0 and DR DOS 6.0

          In Compaq DOS 5.0 and DR DOS 6.0, the following commands
          produce an error:

               NDIR servername/volume:
               DIR servername/volume:
               CD servername/volume:

          This is because DOS treats / as an option specifier when
          it does its preprocessing. You can map a drive and use
          drive letters instead of the servername/volume syntax.


     1.03 Supporting Current NetWare Client File Versions

          To support the Packet Burst ODI functionality, the SFT
          III checksums, and the NetWare management responder, the
          IPXNCP.VLM file requires the IPXODI.COM file version 2.0
          or later to be loaded, with support for checksums and
          GNMA enabled (the version and the API support level are
          treated separately in IPXODI).     1.04 Logging In to a Personal NetWare Server

          The PNW.VLM file needs to be loaded before connecting to
          a Personal NetWare server.  Use the NETWARE
          PROTOCOL line in your NET.CFG file to load the PNW
          software.  For example:

               NetWare DOS Requester
                    NETWARE PROTOCOL = NDS BIND PNW

          Using MS Windows
          Use the NetWare User Tools for Windows to log in to a
          Personal NetWare server. Ensure that the Personal
          checkbox is marked in the "Resource Display Option" box
          under "NetWare Settings" in the NetWare User Tools. If
          the Personal checkbox is not marked, Personal NetWare
          resources are not accessible.

          Ensure that the PNW.DLL file is copied to the MS Windows
          SYSTEM directory.

          Using DOS
          Use the NET.EXE utility provided with Personal NetWare to
          log in and access Personal NetWare resources in DOS.
          Ensure the following:
          
               The NET.EXE, NETU.OVL, and NETA.OVL file is copied
               to your NetWare client directory (default is
               C:\NWCLIENT) and the NETC.MSG file is copied to the
               NLS\ENGLISH directory under the NetWare client
               directory.


     1.05 Using the Receive Monitor Utility (RXMONSTK.COM) with
          Management Applications



          
  2.0 Information Specific to Using the NetWare DOS Requester


     2.01 Mapping Roots within Paths over 64 Characters in Length

          DOS limits the number of characters that the NetWare DOS
          Requester software can support in a path name. To use
          longer paths, map a root within the path at a point where
          fewer than 64 characters remain in the path.

          DR DOS 6.0 and Novell DOS 7 allow paths longer than 64
          characters on local drives only. To use paths longer than
          64 characters on network drives, follow the root mapping
          instructions in the previous paragraph.



     2.02 Search Mode Now Uses the DOS ENVIRONMENT Variable
       
          The "SEARCH MODE" function uses the "PATH" DOS
          ENVIRONMENT variable rather than the public search mode
          table provided in the NETX.VLM file. You will experience
          no change unless users corrupt their workstation
          environment. If you exceed the PATH limitation, your
          search drive mappings will not be included in the PATH.


     2.03 Difference In Diagnostic Information Reported In the    
          NETX.VLM File Compared to the NETX.COM and Related Files

          Some of the current diagnostic information supported
          in the NETX.COM file will appear to be invalid in the
          NETX.VLM file. This is because the NetWare DOS Requester
          is responsible for much of the diagnostics information
          previously maintained in the NetWare Shell for DOS. Some
          of the information maintained in the diagnostics
          responder will not be updated.  Such information includes
          the following:

                    Bad reply header (InvalidReplyHeaderCount)
                    Bad slot (InvalidSlotCount)
                    Bad sequence number
(InvalidSequenceNumberCount)
                    No router found (NoRouterFoundCount)
                    Request in process (BeingProcessedCount)
                    Bad server slot (InvalidSlotFromServerCount)
                    Bad net address (NetworkGoneCount)
                    Bad local address (BadLocalAddressCount)
                    Allocate slot errors
(AllocateSlotCannotFindRoute,
                    AllocateNoSlotsAvailable, AllocateServerIsDown)

          The NetWare Management Responder (NMR.VLM) file will now 
          provide diagnostic information similar to that mentioned
          above.
3.0  Information Specific to Using MS Windows


     3.01 Using the NETWARE.DRV Version 3.03 with MS Windows

          The current version of NETWARE.DRV (version 3.03)
          requires the NWGDI.DLL file to be loaded when running MS
          Windows 3.1 or later version.  If you receive the
          following message when loading MS Windows with the
          NetWare for MS Windows client software, you should ensure
          that you a copy of the NWGDI.DLL file exists in your MS
          Windows SYSTEM directory:

          Application Error: Call to Undefined Dynalink


     3.02 Using the Correct Version of the Dynamic Link Libraries
          (*.dll) Files with NetWare Administrator Utility in
          NetWare 4      
          
          The dynamic link library (*.DLL) files provided with   
          the current version of the NetWare Client software do not
          support the NWADMIN.EXE file version 4.05 or earlier   
          (NetWare 4.0 4.01).

          To support the NWADMIN.EXE file version 4.05 or earlier,
          download the WINDR1.EXE from NetWare or FTP.NOVELL.COM.


     3.03 Fixing Situation In Which MS Windows Hangs and Displays
          a Blinking Cursor in the Upper-Left-Hand Corner of the
          Screen 

          If you are experiencing the situation in which MS Windows
          hangs and then displays a blinking underline cursor 
          in the upper-left-hand corner of the screen, you should
          perform one or all of the following procedures.

          1.>  If you are using a third-party memory manager, do
               not load any IPX interface software into high
               memory, such as LSL.COM or IPXODI.COM.

          2.>  Virtualize the network board's IRQ in the [VIPX]
               section of the SYSTEM.INI if using IBM LAN SUPPORT.
               (See "Specialized Configuration Parameters" below
               for instructions)

          3.>  Add the TimerCriticalSection=10000 command line in
               the [386Enh] section of the SYSTEM.INI file.

          4.>  Download and implement the VTDA.386 driver from
               Microsoft as documented in the README file.

               You can obtain a copy by downloading the appropriate
               file from Microsoft Download Services or
               FTP.MICROSOFT.COM SOFTLIB Area.

Specialized Configuration Parameters
------------------------------------

          Under most circumstances, VIPX will work fine under the
          default configuration.  However, there may be some
          applications that require custom configuration of the
          driver.  This following is a list of SYSTEM.INI
          parameters that can be used to configure VIPX:

          [VIPX]
          VipxMappingPages=[number of 4K pages] (default=16)
          VipxFailOverSizedPackets=[ON|OFF|TRUE|FALSE](default=OFF)
          VirtualizeIrq[0-F]=[ON|OFF|TRUE|FALSE] (default=OFF) 

     VIPX Parameters
     ---------------
 
          VipxMappingPages
               
          This is the number of pages that VIPX can use to
          globalize request to the global IPXODI.COM driver.  VIPX
          is not absolutely guaranteed to have all of these pages
          available at any one point, because this is the requested
          number of pages for shared global mapping that VIPX makes
          to the Windows VMM at initialization time.


          VipxFailOverSizedPackets

          This parameter tells VIPX to fail any requests that
          require more than the maximum allowed globalization size. 
          The actual maximum will vary according to the media the
          user is using.  The absolute maximum is 8000 (decimal)
          bytes. With media that have smaller packets than 8000
          bytes, the maximum allowed size is the maximum packet
          size that can be put onto the media.


          VirtualizeIrq[0-F]

          VIPX v1.15 or greater avoids a deadlock between the
          machine and network board by virtualizing the network
          board's IRQ.  With ODI and dedicated IPX (IPX.OBJ)
          drivers, VIPX will automatically read the configuration
          of the network board from the driver and virtualize the
          selected IRQs.  However, when using the IBM LAN Support
          Program with SLANSUP.OBJ or LANSUP.COM, the LAN IRQ is
          not readable from the driver.  The only way to get this
          information is to read the network board hardware itself. 
          The problem with doing this is that the hardware can be
          Token Ring, PCN2 or Ethernet. 

          VIPX must now be aware of many different hardware
          configurations. 

          Instead of this, VIPX requires the IBM LAN Support user
          to specify the network board's IRQ in the [VIPX] section
          of the SYSTEM.INI. 

          IRQs range from 0 to F (hex).  An example is listed
          below:         

          [VIPX]
          VirtualizeIrq2=TRUE
          VirtualizeIrq3=TRUE

          In this example, VIPX will virtualize both IRQ 2 and 
          IRQ 3. VIPX can virtualize up to four different LAN IRQs. 
          The reason for virtualizing multiple IRQs is to allow
          other LAN boards and protocols to be installed on the
          same client workstation and prevent them from
          deadlocking the machine.  For example, you may have IPX
          running through an NE2000 board on IRQ 3 and TCP/IP
          running through to an IBM Token-Ring board on IRQ 2.


     TimerCriticalSection
     --------------------

     As of version 1.15 of VIPX, TimerCriticalSection is required
     to be set on.  The recommended setting is as follows:

     [386Enh]
     TimerCriticalSection=10000

     The reason for this parameter is to avoid a deadlock with the
     LAN IRQ Virtualization code.  See "VirtualizeIrq[0-F]"
     section.

     
4.0 Information Specific to Using MS Windows for Workgroup


     4.01 Using LSL.COM, 3C5X9.COM, IPXODI.COM, and the NetWare DOS
          Requester with Windows for Workgroup NWLINK.386 and
          MSODISUP.386 files

          When copying files from a local to a network drive from
          MS Windows for Workgroups 3.11, the file would sometimes
          become corrupted, or the client workstation would hang or
          lose network connection.

          You should update your version of Microsoft's
          MSODISUP.386 file. You can obtain a copy by downloading
          the WG1004.EXE from Microsoft Download Services or
          FTP.MICROSOFT.COM SOFTLIB Area.


     4.02 Supporting DOS Named Pipes 

          Novell's DOSNP.EXE file is not compatible with MS Windows
          for Workgroup (WFWG) version 3.11. WFWG does not allow
          the use of INT 21 named pipes requests used by the
          DOSNP.EXE file. 

          Currently, there is no fix available.

-----------------------------------------------------------------
                         DISCLAIMER

Novell, Inc., makes no representations or warranties with respect
to any NetWare software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose.

Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc. Further, Novell reserves
the right to discontinue distribution of any NetWare software.

Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of recreating lost data, the
cost of any substitute equipment or program, or claims by any party
other than you.

Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at
the discretion of Novell.
