home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
us8210b4.dsk
/
IBMCOM
/
MACS
/
MACS.ZIP
/
ibmcom
/
macs
/
rtr16nds.txt
< prev
next >
Wrap
Text File
|
1995-09-13
|
7KB
|
165 lines
Automatic Installation
This driver supports the automatic installation procedure defined
by the IBM LAN Adapter and Protocol Support (LAPS) module. LAPS is
provided by IBM with the following services:
IBM OS/2 Extended Services 1.0
IBM OS/2 LAN Server 2.0
IBM OS/2 LAN Requester 2.0
Manual Installation
1. Copy the driver RTR16NDS.OS2, and the message file RTR16NDS.MSG
from the installation diskette to the desired fixed disk
drive and directory.
NOTE: If you are using an FPA based adapter, copy the file RTR16FPA.COD
from the installation diskette's DIAGS directory to the ROOT
directory on your LAN Server system drive. When the driver
loads, the message "Utilizing FPA microcode" will be displayed if
the RTR16FPA.COD file was found and an FPA based adapter is being
used. If the RTR16FPA.COD file was not found or the adapter is
non-FPA based, the message "Utilizing MAC microcode" will be
displayed.
2. Add the following line to the CONFIG.SYS.
DEVICE=[drive:directory]RTR16NDS.OS2
This line should be entered immediately following the line
which installs the PROTMAN.OS2 device driver.
NOTE: You must specify a DPATH in CONFIG.SYS to the subdirectory
containing the RTR16NDS.MSG file to enable driver error
messages and alleviate the "Cannot find message file" error
at boot time.
3. Add the following section to PROTOCOL.INI
[RTR16NDS_NIF]
DriverName = RTRNDS$
4. Add RTR16NDS_NIF to the bindings list of the protocol in the
PROTOCOL.INI. An example protocol section follows.
[NETBEUI_XIF]
DriverName = NETBEUI$
Bindings = RTR16NDS_NIF
RTR16NDS Parameters
The PROTOCOL.INI file defines the configuration of protocol
and NDIS drivers. The following table summarizes RTR16NDS
parameters.
┌────────────────────┬──────────────────────────────┬──────────┐
│ Parameter │ Range │ Default │
│ │ │ OS/2 │
├────────────────────┼──────────────────────────────┼──────────┤
│ DRIVERNAME │ RTRNDS$ or RTRNDSn$ │ Required │
│ IOADDRESS │ 0xA00, 0xA20, 0xA40, 0xA60 │ - │
│ MAXTRANSMITS │ 3 - 50 │ 6 │
│ NUMRXBUFFERS │ 3 - 100 │ 6 │
│ LOOKAHEAD │ See description │ │
│ RXBUFFERSIZE │ 256 - 17960 │ 2048 │
│ PSEUDODMA │ │ - │
│ NOEARLYRELEASE │ │ - │
│ NETADDRESS │ "000000000000"-"7FFFFFFFFFFF"│ BIA │
│ PIU │ 265 - 2048 │ │
│ RPL │ │ - │
│ PROMISCUOUS │ │ - │
└────────────────────┴──────────────────────────────┴──────────┘
DRIVERNAME
Identifies the network device driver. The DRIVERNAME is RTRNDS$
for the first driver and RTRNDS2$ for the second, and so on.
This parameter is required.
IOADDRESS
If no IOADDRESS is specified, the driver will search for an
adapter at all I/O addresses until one is found. Otherwise,
only the specified I/O address is checked. This parameter is
required when multi adapter support is desired.
MAXTRANSMITS
Sets the number of transmits that can be queued simultaneously
by the driver.
NUMRXBUFFERS
Sets the number of receive buffers to allocate.
LOOKAHEAD
Directs the driver to use the Receive Lookahead method in lieu of
the default Receive Chain method. NDIS requires the upper protocol
to support either method. Some protocols have been found to only
support Receive Lookahead. Receive Chain will typically give better
performance on DMA and Pseudo-DMA based adapters.
RXBUFFERSIZE
Sets the size of buffers used to queue received frames in the
driver. Several buffers may be required to queue a large
frame. Performance is improved if a received frame fits in one
buffer. Use the following formula to determine maximum frame
size. MediaMaxSize equals 17960 @ 16 Mbps, or 4490 @ 4 Mbps.
MaxFrameSize =
min(min(8, NumReceiveBuffers) x ReceiveBufferSize, MediaMaxSize)
NOTE: For maximum performance when using an FPA based adapter,
set RXBUFFERSIZE = 4128.
PSEUDODMA
This entry informs the driver to use pseudo DMA on 16 bit ISA
adapters. Normally, 16 bit adapters use DMA bus master mode.
Note that the pseudo DMA option is not supported on Micro-Channel
adapters. Also note that the 8 bit ISA adapter does not support bus
master DMA, and always defaults to the pseudo DMA mode. This entry
is not followed by an equal sign.
NOEARLYRELEASE
This entry informs the driver to disable early token release.
Early token release reduces the average time another network
adapter must wait to transmit a frame. This entry is not
followed by an equal sign.
NETADDRESS
This entry allow the driver to override the burned in address
(BIA). The entry must be a 12 character string of hexadecimal
digits, and must be enclosed in quotes.
PIU
Instructs the driver to implement Lying Sends on all transmits smaller
than the given PIU (Program Interchange Unit) size. The driver by default
will verify each transmit on the physical ring before confirming the
transmit to the upper protocol. Personal Communications 3270 ver 3.0x
requires all PIU transfers to confirm the transmit before it is physically
transmitted on the ring. The PIU option enables this 'Lying' send.
RPL
This entry provides compatibility when RPLing under OS/2 and
certain versions of IBM LAN Server. This parameter should be
specified for each station performing RPL, as required. This
entry should NOT be specified on server or non-RPLing PC's.
PROMISCUOUS
This entry enables the promiscuous mode in the driver. When
enabled, the Token Ring adapter will receive and forward to
the driver all MAC frames, even if they are not addressed to
the adapters unique node address. This mode will affect driver
performance and is not recommended for normal use. Either the
RTR16FPA.COD or RTR16CAF.COD file must have been successfully
read and downloaded to the adapter for this mode to function.
For example, the following is a sample PROTOCOL.INI file:
[RTR16NDS_NIF]
DRIVERNAME = RTRNDS$
IOADDRESS = 0xA20
MAXTRANSMITS = 10
NUMRXBUFFERS = 12
RXBUFFERSIZE = 4128
NETADDRESS = "400000000312"
PSEUDODMA