T1108 OS/2 NetWare Requester driver installation

NetWare Requester for OS/2

TR2KNW.OS2 is designed to be used with Novell's Netware
Requester for OS/2. To install TR2KNW.OS2, complete the steps
outlined by Novell in the Netware Requester manual section
"Install the NetWare Requester". Add the following line to the
CONFIG.SYS file:

   DEVICE=C:\directory\TR2KNW.OS2

Copy TR2KNW.OS2 and MSM.MSG files from the distribution diskette into
the desired directory. This is usually \NETWARE. Make sure that the
adapter and cabling are installed correctly and reboot the computer.

Keyword support:

The following keywords are documented in the OS2 requester manual.

INT
   Usage: Specify the interrupt the adapter will use.
   Format: INT x
      Where x is the interrupt number
   Default: 2/9

NODE ADDRESS
   Usage: Specify a node address rather than using the burn-in
      address of the adapter.
   Format: NODE ADDRESS xxxxxxxxxxxx
      Where the x's are the node address you wish to use.
   Default: None

PORT
   Usage: Specify the I/O port of the adapter.
   Format: PORT x
      Where x is the the I/O port of the adapter.
   Default: A20

BIT16
   Usage: Specify sixteen-bit pseudodma.
   Format: BIT16
   Default: 8 bit pseudodma.

WS0
   Usage: Specify eight-bit pseudodma
   Format: WS0
   Default: None

SPEED
   Usage: Specify the speed of the lan
   Format: SPEED x
      Where x is the speed of the lan the adpater is attached.
   Default: 16 Megabits/second





The following is a sample net.cfg showing the use of the keywords.  It
configures the adapter for interrupt 2 at I/O port A40.  The adapter will
use sixteen bit pseudo DMA on a 16 megabit lan and the node address will
be 40001A123456.

netware requester
   preferred server-name
link driver tr2knw
  frame token-ring
  frame token-ring_snap
  int 2
  bit16
  port A40
  node address 40001A123456
  speed 16
protocol odinsup
  bind tr2knw



Some Requesters have a feature called Packet Burst which can
significantly increase the throughput on large file transfers
. However there appears to be a timing problem with some
Requesters which actually cause a SEVERE SLOWDOWN under some
specific conditions. Use of PSEUDO DMA seems to be a major
factor in this slowdown. Another major factor is if the server
is running on a much faster processor than the client.

It is recommended that until a new Requester ( which fixes
this problem ) becomes available, that the Packet Burst feature
NOT be enabled. If use of the Packet Burst feature is desired,
each workstations performance should be analyzed separately and
if a slowdown is detected, that workstation can be individually
disabled via NET.CFG (see your NET.CFG documentation).

NOTE: If Packet Burst IS enabled, some security functions may not
work properly, and a "SIGNATURE LEVEL 0" parameter may need to be
included in NET.CFG.