|
This installation document applies to the TokenExpressTM PRO adapter software release v3.0, which is available in the archive TPRODISK.EXE.
Location of Driver: \NETWARE\TPRO.LAN
Novell NetWare* for SAA v1.3
Intel drivers provide support for Novell NetWare for SAA, v1.3. NetWare for SAA provides communication between LANs and IBM hosts.
Novell's NetWare for SAA v1.3 can be installed in two different server types:
- NetWare 3.12 Server - (runtime version-dedicated SAA server, or standard server, using 3.12 server driver: TPRO.LAN)
- NetWare 4.1x Server - (runtime version-dedicated SAA server, or standard server, using 4.1x server driver: TPRO.LAN)
The following are examples of STARTUP.NCF and AUTOEXEC.NCF files that load the TPRO.LAN driver with the Novell NetWare SAA Gateway v1.3 software on an existing NetWare server.
Sample STARTUP.NCF
LOAD ISADISK PORT=1F0 INT=E
SET MINIMUM PACKET RECEIVE BUFFERS=500
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 4202
SET MINIMUM PACKET RECEIVE BUFFERS
This command can help prevent 3270 workstations from receiving network disconnects (a 590 error) from NetWare on a network with heavy communication traffic. When you set this command, you determine the minimum number of packet receive buffers that the operating system can allocate. Rather than waiting for requests to come in, the operating system allocates the minimum number of buffers as soon as the server boots.
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE
This setting corresponds to the "Maximum Frame Size to Transmit Inbound" setting in CSCON. The Frame Size is the number of bytes to be included in frames being sent to the host. The default is 265, but you can raise this value to 521, 1033, 2048, or 4202 bytes if the host system supports larger frame sizes (performance improves with larger frame sizes). This matches the MAXDAT=value in the host definition.
Sample AUTOEXEC.NCF files
Note: Make sure the PORT and INT in the load lines match the adapter's settings in TokenSet.
One TokenExpress PRO adapter for both Host and LAN:
FILE SERVER NAME INTEL_TEST
IPX INTERNAL NET 311
LOAD TPRO PORT=300 NAME=TOKEN1 NODE=70930004 SAPS=2 LS=16
BIND IPX TO TOKEN1 NET=30
LOAD COMMEXEC
Two TokenExpress PRO adapters - one for the Host and one for the LAN:
FILE SERVER NAME INTEL_TEST
IPX INTERNAL NET 311
LOAD TPRO PORT=300 NODE=70930004 SAPS=2 LS=16
LOAD TPRO PORT=310 NAME=TOKEN1
BIND IPX TO TOKEN1 NET=30
LOAD COMMEXEC
Four TokenExpress PRO adapters - two for the Host and two for the LAN:
FILE SERVER NAME INTEL_TEST
IPX INTERNAL NET 311
LOAD CLIB
LOAD SPXS
LOAD BTRIEVE -U=1 -P=4096 -F=20 -H=60 -L=20 -C
LOAD LSLENH
LOAD SPXFIX2
LOAD TPRO PORT=300 NODE=70930004 SAPS=1 LS=8
LOAD TPRO PORT=310 NODE=70930005 SAPS=1 LS=8
LOAD TPRO PORT=320 NAME=TOKEN1
LOAD TPRO PORT=330 NAME=TOKEN2
BIND IPX TO TOKEN1 NET=30
BIND IPX TO TOKEN2 NET=40
LOAD COMMEXEC
Note: It may be necessary, depending on what version of NetWare you have, to specify a 12 digit node address instead of 8 digits when you are using Locally Administered Addresses.
Example:
LOAD TPRO PORT=300 NODE=400070930004 SAPS=1 LS=8
Hints and Tips
NetWare server load command options:
PORT
The Base I/O address of the adapter. This should match the I/O address in TokenSet.
INT
Optional, not required. The system IRQ that the adapter is to use. If set, this should match the Interrupt selected in TokenSet.
NODE
Locally administered address. Example: NODE=400012345678. It may be necessary with some versions of NetWare to specify an 8 digit address instead of 12 digits; some versions automatically insert the first 4 digits.
- Example NODE=12345678.
FRAME
The frame type that the driver is to support.
- Examples: TOKEN-RING and TOKEN-RING_SNAP.
MAX_PACKET_SIZE
The maximum frame size the driver is to use, up to 8298 bytes (4.01 driver only).
Error Message: "Loader cannot find public symbol: <symbol name>"
This error message occurs when the server is loading older versions of MSM.NLM, NBI.NLM, or TOKENTSM.NLM. Verify that you are loading newer versions of these NLMs. MSM.NLM, NBI.NLM, and TOKENTSM.NLM are included on TokenExpress PRO Adapter Configuration disk in the directory, \NETWARE\NLM41X.
If you can log in to the server, copy these updated NLMs into the SYS:SYSTEM subdirectory. If you do this, you won't need to specify a path on the load line. If you copy it to another directory, make sure the LOAD statement includes the correct path.
This applies to:
| 
