NetWare Client for Windows NT: Pre-release Document


Thank you for your interest in the NetWare Client for Windows NT.
We hope this pre-release helps in your product development and
planning. 

This information explains how to set up the NetWare Client for
Windows NT.  It contains the following sections:

  ** What You're Getting
  ** Before You Install
  ** Installing the NetWare Client for Windows NT
  ** Accessing NetWare Services
  ** Reporting Problems


** What You're Getting

Installing the NetWare Client for Windows NT provides you with
basic NetWare services.  In this release you'll be able to:
     Connect to NetWare servers
     Map drives to NetWare servers
     Communicate with NetWare servers 

We currently support the NE2000 and IBM Token-Ring network boards. 
We will update the list of supported network boards in the future.

Important:  This pre-release software allows users of Microsoft's
Win32 Applications Sampler CD to have a first look at how the
NetWare Client works transparently with Windows NT.  However, as
Novell and Microsoft complete product development for the NetWare
Client and the Windows NT OS respectively, interfaces and
functionality will be added or may be changed.

For example, certain functionality, such as print services and
local redirector caching will be added as development continues.  


** Before You Install

You should have installed Windows NT on your system.

You must install LanMan services in order for the NetWare
Redirector to work. (The NetWare Redirector relies on the Windows
NT MUP service.  If no LanMan services are installed, MUP is not
installed.)

We suggest you make your login name for NetWare servers the same as
your username for NT. You can either add a new user on your Windows
NT system or use the SYSCON utility to change your NetWare login
name.

If you are running Windows NT with LAN Manager and are using an
NE2000 or Token-Ring network board, running NWSETUP disables LAN
Manager.   Since NWSETUP uses ODI-compliant drivers instead of the
NDIS drivers that are supplied by Microsoft, the NDIS drivers are
disabled and our ODI-compliant drivers are added to the registry.

For the NE2000 board, the NetWare ODI-compliant driver requires
use of the ETHERNET_802.3 frame type and the default settings
of IRQ 3 and I/O Port 300.  The Token-Ring board requires the use
of the TOKEN-RING frame type and  the port address must be
set to port A20; all other settings are read from the network board.

If you use LAN Manager, we suggest that for this release of the
NetWare Client for Windows NT you use LAN Manager with a second
network board such as the NE3200 or 3C503. Running LAN Manager with
any network board other than the NE2000 or Token-Ring provides you
with dual functioning redirectors, and you can use both NetWare and
LAN Manager.  We are developing a single card solution for a future
release.


** Installing the NetWare Client for Windows NT


1. Log on to your NT system as Administrator.

2. Make your username a member of the Administrators group.

     To do this, use the User Manager utility in the 
     Administrative Tools group.

3. Open an MS-DOS session.

4. Insert the Netware Client for Windows NT "Install" diskette into
   drive A:.

5. Change to drive A: and type NWSETUP [ Driver Name ].

      Driver Name can either be NE2000 or TOKEN.
  
      NWSETUP.CMD updates the registry, creates a new WINFILE.INI, 
      and copies NetWare files to the directories as shown below:

          DRIVER.ODI    SYSTEM\NETWARE
          LSL.SYS       SYSTEM\NETWARE
          ODILOAD.SYS   SYSTEM\NETWARE
          IPX.SYS       SYSTEM\NETWARE
          NWFS.SYS      SYSTEM\NETWARE
          RESMGR.SYS    SYSTEM\NETWARE
          NETWARE.DLL   SYSTEM
          NETWARE.CPL   SYSTEM
          
        
6. Once NWSETUP has completed, exit the MS-DOS session, remove the
"Install" diskette, shutdown, and reboot your machine.

     Note: During shutdown, you may receive a message stating that
the NetWare redirector is unable to load.  This message is not an
error; it is due to the fact that the NetWare redirector has not
loaded yet.  After you reboot, this message will not appear again
unless there is a problem and the NetWare redirector is unable to
load.

7. Start NT and log on with your NT username.



** Accessing NetWare Services

You can access NetWare services through File Manager and Control
Panel.  Remember, to specify network resources, you must use UNC
formatting conventions (\\SERVER\VOLUME\DIRECTORY\DIRECTORY).
Note that under "Connect Network Drive", long path names may be
truncated when they are displayed in the lower box.  This is a 
known problem.

File Manager:  NetWare provides a menu in the File Manager menu
bar. The NetWare menu offers connection and drive management.

Control Panel:  The NetWare icon in the Control Panel lists your
connections, username, and connection ID.  It offers connection
management and drive management. 



** Reporting Problems

We welcome any suggestions and comments you have concerning this
product.

Novell has set up areas on CompuServe for you to communicate
pre-release problems or suggestions. These areas are located in the
NDSG forum, section 14, and NOVDEV, section 17.  

While this pre-release version is unsupported, Novell will monitor
these forums so that responses and fixes can be made available.
These will be the only forums available to you to discuss problems
or suggestions concerning the NetWare Client for Windows NT.
Novell will not monitor other forums such as MSWIN32 or WINNT for
Windows NT/NetWare issues.

If you prefer, you can communicate your problems or suggestions via
FAX.  Complete the TEMPLATE.FAX file and return it to:

           FAX: 801-429-3098 
     Attention: NetWare Client for Windows NT, Development