NetWare IPX Workstation Installation

This file contains instructions specific for the installation and operation of Intel's TokenExpress™ adapter driver. Refer to the appropriate Network Operation System documentation for any NOS-specific questions or other information.

These instructions apply to Release 5.0 of the software.

Installing and configuring the Intel TokenExpress™ adapter driver for Novell NetWare Workstations using WSGEN.

Introduction
WSGEN is the program that ships with NetWare* 286 v2.2 or NetWare 386 v3.x. The program that ships with NetWare v2.1x is "SHGEN". The instructions are similar, however, there are some differences. Refer to your NetWare installation manual for additional information on SHGEN.

WSGEN generates the workstation software using the TokenExpress LAN adapter driver. The NetWare workstation software performs two DOS functions:

• It sends requests from the workstation to the appropriate operating system (DOS in the workstation or NetWare in the file server). This referred to as the Shell. (Example: NET5.COM or NETX.COM)
  
  
• It sends messages to another workstation or other appropriate destination on the network using the NetWare Internetwork Packet Exchange (IPX.COM) protocol.

The Intel® TokenExpress™ driver diskette (volume label: LAN_DRV_453) contains the NetWare workstation shell module used by SHGEN or WSGEN.

The following files (located in the driver diskette root directory) are used:

• Descriptor file used by SHGEN, WSGEN
  
  
• Object module used when generating IPX.COM with SHGEN or WSGEN
  
  
• Batch file that copies the TokenExpress NetWare* drivers to a hard disk or a network drive.

Installing and configuring the Intel® TokenExpress™ driver
There are two methods to run the WSGEN program, the floppy disk method or the hard disk method. This document describes the hard disk method.

1. Create a directory where you will store the workstation software generation files, for example C:\NETWARE
   
   
2. Locate the WSGEN diskette supplied with NetWare. Create a subdirectory under the NETWARE directory called WSGEN(C:\NETWARE\WSGEN). Copy the contents of the WSGEN diskette to this directory.
   
   
3. Copy the WSGEN.EXE program from the WSGEN diskette to the C:\NETWARE directory.
   
   
4. At the C:\NETWARE prompt, type "WSGEN".
   
   
5. The introductory screen will appear. Press enter and a list of drivers will appear.
   
   
6. To add the driver for the TokenExpress adapter, press the insert key, and when prompted to enter the diskette labeled "LAN_DRV_xxx", insert the diskette supplied with the TokenExpress adapter with the volume label "LAN_DRV_453".
   
   
7. The driver for the TokenExpress adapter will appear on the driver list. Highlight this and press enter.
   
   
8. When the next screen appears, highlight the network board driver configuration and press enter. The configuration option for the default settings on the board is option "0". Unless you have changed settings on the board, choose this option. If you changed any settings on the board, or if you are using "Source Routing", you must choose an option that will match those settings. (Refer to the section "Hardware Configurations for NetWare Dedicated IPX" below).
   
   
9. The configuration option will now be displayed. At this point answer "Yes" to generate the workstation software. The IPX.COM file will be modified with the settings you specified.
   
   
10. The files you will need to connect to the network are in the C:\NETWARE\WSGEN directory. Copy IPX.COM and NETx.COM to the directory you will be executing them from, probably your root directory. The newest shell program is NETX.COM. This shell can be used with any version of DOS as it checks for the version as it loads.

    NOTE: A word on NETx.COM. The "x" in NETx.COM refers to the DOS version level. If you are using DOS v3.x then you will use NET3.COM etc... NET5.COM is available on Netwire. If you will use expanded (LIM 4.0 EMS compatible) memory, use EMSNETx.exe. If you will use extended memory (XMS 2.0 compatible), use XMSNETx.exe.

11. Include four statements in your AUTOEXEC.BATt file or a batch file to be executed at the DOS prompt. The sequence is as follows. IPX, NETX, F:, LOGIN

At this point you should be able to enter your user name. Refer to your NetWare installation manual for additional information about WSGEN.

NOTE: EARLY TOKEN RELEASE is always enabled in the Intel TokenExpress NetWare drivers.

Hardware Configurations for NetWare Dedicated IPX

0: I/O = A20,A30 self configuring IRQ and DMA. No Src Routing
1: I/O = A24,A40 self configuring IRQ and DMA. No Src Routing
2: I/O = A50,A60 self configuring IRQ and DMA. No Src Routing
3: I/O = A54,A70 self configuring IRQ and DMA. No Src Routing
4: I/O = A20,A30 self configuring IRQ and DMA. Src Routing
5: I/O = A24,A40 self configuring IRQ and DMA. Src Routing
6: I/O = A50,A60 self configuring IRQ and DMA. Src Routing
7: I/O = A54,A70 self configuring IRQ and DMA. Src Routing

For the EISA/32 adapter, the above I/O addresses fall within the ranges selected in the EISA configuration program:

A20, A30 corresponds to the selection 0A18-0A23 & 0A30-0A3F
A24, A40 corresponds to the selection 0A24-0A2F & 0A40-0A4F
A50, A60 corresponds to the selection 0A50-0A53 & 0A58-0A6F
A54, A70 corresponds to the selection 0A54-0A57 & 0A70-0A87

The remaining I/O addresses (1Axx range of addresses) are not currently supported.

Mixing NetWare* with IBM* operating environments

The IPX.COM driver generated from STOKEXPR.OBJ is standalone. No drivers in CONFIG.SYS nor any download programs invoked in AUTOEXEC.BAT are needed with this dedicated IPX.COM

If you need concurrent communication using protocols other than IPX that communicate through the DLC (802.2) interface (typically 3270 or AS400 host communication), load the DLC driver OC02DLC.SYS. This replacement for the DXMC0MOD.SYS used with IBM Token-Ring boards requires an IPX that interfaces to this DLC driver. Use the IBM Lan Support Program when generating the IPX in WSGEN or SHGEN. Use version 3.10 of IPX/SPX; previous versions do not work. The resulting combination is slower and consumes more memory than a driver that directly accesses the hardware.

Look at the following documents for more information about setting up configuration files for a mixed operating environment:

NetWare & IBM DOS Workstation
NetWare DOS/IPX Workstation Configurations
NetWare DOS ODI (DOS) Workstation
IBM - 3270 Connectivity
IBM - AS400 Connectivity

Notes for use with Qualitas' 386MAX Memory Manager

The 386MAX Memory Manager program allows physical memory above 1 Meg to be mapped into the address space between the video RAM and the BIOS ROM. You can free up conventional DOS memory by loading IPX.COM and/or NETx.COM into this area.

Additional considerations:

• The driver may not work if 386MAX is used to backfill the lower 640 Kbytes (used if your 80386 machine does not have 640K low DOS memory without the 386MAX)
  
  
• Automatic recovery of unused shadow RAM by 386MAX should be disabled when using the TokenExpress MCA adapter because the shadow RAM may not be accessible. This is done by adding the "noxram" parameter to your existing 'device = 386max.sys' statement as follows:
  
  
  device = 386max.sys noxram
  
  
• Do NOT use the option 'EMS=0' when installing 386MAX.SYS. If using 386MAX version 4.08 or higher, you may use the NOFRAME option instead.

Notes for Use With AST RamPage (or similar) Expanded Memory Boards in IBM AT Compatibles

If applications transfer data directly from expanded memory in an AT to the network, data may be corrupted if the TokenExpress ISA 16/4 adapter is configured to use DMA.

To eliminate this problem, configure the adapter to use programmed I/O mode. Refer to the your Intel TokenExpress ISA installation guide for a description of the switch settings.

Note for WINDOWS* 3.0 In Standard Mode

The NetWare dedicated IPX driver (IPX.COM) cannot be loaded into high memory using a memory manager such as EMM386, QEMM, etc.

Note for TCP/IP Support

TokenExpress ISA adapters configured in *programmed I/O* mode cannot use TCP/IP.

This applies to:

TokenExpress™ 16/p Adapter TokenExpress™ EISA 16/4 Adapter TokenExpress™ EISA 32 Adapter TokenExpress™ MCA Adapter