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
/
ibmmpc.txt
< prev
next >
Wrap
Text File
|
1995-05-22
|
18KB
|
342 lines
Information file for IBM Streamer(**) Family NDIS 2.0 MAC Device Driver
------------------------ Information About This Release ------------------------
Version 4.44.00
This device driver supports the following IBM Streamer Family adapters:
- IBM LANStreamer(**) MC32 Adapter (see Special Notice below)
- IBM LANStreamer MC16 Adapter (see Special Notice below)
- IBM Auto LANStreamer(**) MC32 Adapter
- IBM Dual LANStreamer MC32 Adapter
- IBM Auto LANStreamer PCI Adapter
- IBM EtherStreamer(**) MC32 Adapter
- IBM Dual EtherStreamer MC32 Adapter
Note that previous versions of this device driver may not support all of the
adapters listed here, so you should reinstall with the latest version.
************************************************************************
* Special Notice to IBM LANStreamer MC32 and MC16 Users *
************************************************************************
* This version of the IBMMPC.OS2 and IBMMPC.DOS NDIS MAC driver *
* for the IBM Streamer Family adapters now supports the existing *
* IBM LANStreamer MC32 and MC16 adapters. Note that the IBM *
* LANStreamer MC32 and MC16 adapters are shipped with the *
* IBMTRDB.OS2 and IBMTRDB.DOS NDIS MAC drivers. *
* *
* If you wish to use the IBMMPC driver instead (for example, you *
* have a system with a mixture of IBM Streamer Family adapter *
* types), you must first remove the existing LANStreamer NDIS con- *
* figuration, then reinstall the NDIS support using the IBMMPC *
* driver and its associated files. This is the recommended method. *
* *
* Should you choose to keep the IBMTRDB driver support for the *
* LANStreamer MC32 and MC16 adapters, yet add one or more of the *
* IBM Streamer Family adapters that use the IBMMPC driver, the *
* DEVICE= statement for the LANStreamer IBMTRDB driver *MUST* *
* appear BEFORE the DEVICE= statement for the IBMMPC driver in the *
* CONFIG.SYS file. Otherwise, the results will be unpredictable. *
************************************************************************
------------------------------ General Information -----------------------------
The message files for the IBM Streamer Family NDIS MAC Driver are LTC.MSG and
LTCH.MSG. The messages and their associated help text refer in general to the
adapter name as IBM Streamer Family adapter.
The IBM Streamer Family NDIS MAC Driver supports Promiscuous Copy.
-------------------------- Changes to the Publication --------------------------
When configuring multiple IBM Streamer Family adapters using the system
Reference Diskette, you are no longer required to set all of these adapters
to the same System Interrupt Level in order to operate with this version of
the NDIS MAC Device Driver (although they will continue to work properly if
set to the same level).
Support for OS/2 Computers with more than 16 Megabytes of Memory:
The IBM Streamer Family adapters use bus mastering to transfer data
between the computer and the adapter. For 16-bit adapters, or if an
adapter is placed in a 16-bit system slot, the adapter can only address
system memory up to 16 megabytes (MB). For this reason, the IBMMPC.OS2
device driver will automatically configure and use local buffers
allocated below this 16 MB addressing limit. Frame data located above
16 MB will be copied into local buffers for frame transmission so
that it can be accessed by the adapter.
Some device driver messages have had wording changes, while others were
added after the adapter publication had been printed. The affected messages
are shown in their current form towards the end of this file, in the section
entitled "New/Changed Device Driver Messages".
---------------------------- Additional Information ----------------------------
The Network Information File (NIF) to be used with the IBM Streamer Family
NDIS MAC Driver is IBMMPC.NIF, which contains configuration and tuning
parameters that can be adjusted by the user. Look at the NIF file for Help
text available on each parameter. Additional information on some parameters
is provided here.
LoopBack -- will default to NO for an adapter that is either a
16 bit card or in a 16 bit system bus slot, AND is used for
Ethernet or 16 Mbps Token Ring operation. For all other cases,
with the exception of token ring full duplex, LoopBack defaults
to YES. If the EnableTRFDX parameter (see below) is set to YES,
this LoopBack parameter must be set to match the loopback capability
of the attached token ring full duplex switch, and will default to
NO if not specified.
Enet20UTP -- enables 20 Mbps Ethernet operation in an IBM Streamer
Family adapter that supports Ethernet. The adapter must be
attached with a UTP cable to a switched Ethernet concentrator
that supports full duplex operation for this function to be
activated. When this function is activated, the adapter loopback
mode will always be forced off, regardless of the setting of the
LoopBack parameter. The Enet20UTP parameter is ignored for token
ring operation.
UseVDS -- allows the device driver to build the necessary data structures
for use with Virtual DMA Services (VDS). Setting this parameter to
"YES" is a requirement when using the IBM Streamer Family NDIS MAC
driver with either Microsoft Windows(**) or Microsoft Windows For
Workgroups(**) in enhanced mode. It may also need to be set to
"YES" when using some memory managers that support VDS.
LLCOnly -- indicates whether only LLC frames should be copied by the
adapter when it is running in promiscuous copy mode. If this
parameter is set to "YES", then no MAC frames will be copied while
in promiscuous copy mode.
DataRate -- used for configuring the ring speed of the IBM Auto LANStreamer
PCI adapter. It can be set to "AUTO", "16" or "4", with "AUTO" being
the default value if none is specified. Note that this parameter is
not used by any of the other IBM Streamer Family adapters.
EnableTRFDX -- configures the device driver to attempt to use the adapter
in token ring full duplex mode. The adapter must have full-duplex-
capable microcode installed, and must be connected to a full duplex
switch before this mode of operation is attempted. Also note that
for proper token ring full duplex operation, you must set the value
of the LoopBack parameter to match the frame loop back capabilities
of your full duplex switch. The EnableTRFDX parameter is ignored for
Ethernet mode (see the Enet20UTP parameter description above).
Maximum Frame Size Supported: the maximum frame size supported by the NDIS
MAC driver is determined by the SMALLEST of the following values:
- MaxTxFrameSize setting in PROTOCOL.INI
- (MinRcvBuffs x SizWorkBuf) PROTOCOL.INI parameters, less 4 bytes
- (10 x SizWorkBuf) PROTOCOL.INI parameter
- Largest frame permitted by the physical LAN medium (approximately 4500
bytes for 4 Mbps and 18000 bytes for 16 Mbps token rings, and 1514
bytes for Ethernet)
Microsoft Windows For Workgroups(**) Users: when entering or changing the
value of the Network Adapter Address parameter for the IBM Streamer Family
adapter, you must enclose the address string in double quotes.
Example: "xxxxxxxxxxxx"
---------------------- New/Changed Device Driver Messages ----------------------
The following messages were added to the device driver:
LTC0013 -- Slot nn: Invalid IBM Streamer Family adapter configuration
detected; interrupt 0 not allowed.
Explanation: The device driver has detected that interrupt level 0 was
assigned by the system to the IBM Streamer Family adapter
located in Slot n. This interrupt level is invalid, and was
probably assigned by the system automatically, especially for
PCI adapters.
User Action: Reconfigure the system slot use a valid interrupt level
for this adapter.
LTC0023 -- Slot nn: The adapter is configured for full duplex, but could
only be opened in half duplex mode.
Explanation: The EnableTRFDX keyword in PROTOCOL.INI was set to "YES",
indicating that full duplex token ring operation is desired, but
the adapter was no able to open in full duplex mode. Instead,
it opened successfully in half duplex.
User Action: This is an informational message only. If full duplex
operation is desired, you should verify that the adapter is
properly connected to a token ring full duplex switch and that
the switch is operating in full duplex mode. If you are not
interested in token ring full duplex mode, change the setting
of the EnableTRFDX keyword to "NO" in PROTOCOL.INI.
LTC0040 -- Slot nn: Using local transmit buffers to access data above
16 megabytes.
Explanation: The device driver has detected more than 16 megabytes
of RAM in the computer, and the adapter is either a 16-bit
adapter or is located in a 16-bit system slot. The device
driver will copy any frame data located above the 16 MB
address limit to local transmit buffers.
NOTE TO OS/2 2.0 USERS: Early versions of OS/2 2.0 will
only indicate that at least 16 MB of RAM exist in the
computer. If your computer has exactly 16 MB of RAM,
you will see this message. However, there will never be
any data above the 16 MB addressing limit to copy into
local buffers.
User Action: This is an informational message only. No action is
necessary.
LTC0041 -- Slot nn: Overriding MAXTRANSMITS in PROTOCOL.INI with a
value of xx.
Explanation: The amount of local memory needed to hold all possible
queued transmit frames, MAXTRANSMITS * MAXTXFRAMESIZE, is
greater than 128 kilobytes. The device driver has reduced
the MAXTRANSMITS value to allow the maximum number of
transmit frames to fit within the default 128 kilobytes of
local buffer space.
User Action: Ensure that the values specified for MAXTRANSMITS and
MAXTXFRAMESIZE are accurately specified in PROTOCOL.INI. If
not specified, they should both be added with appropriate
values.
The default values for these parameters in OS/2 are
MAXTRANSMITS = 31 and MAXTXFRAMESIZE = 18000, which exceeds
the 128 kilobytes allocated by the device driver for the
local transmit buffer space. These local transmit buffers
are needed when more than 16 megabytes of system memory is
detected, and this IBM Streamer Family adapter is unable to
access above 16 megabytes.
A new PROTOCOL.INI parameter, LOCALBUFFSEGCNT, can be used
to change the amount of storage used for the local transmit
buffers. It can be set from 1 to 16, and defaults to 2 if
not specified. Note that 64 kilobytes of system memory are
used for each local buffer segment configured with this
parameter.
Example: LOCALBUFFSEGCNT = 2
LTC0042 -- OEMHLP could not be accessed.
Explanation: The IBM Streamer Family adapter device driver was
unable to determine the amount of system RAM in the computer.
User Action: Contact your customer service center.
LTC0057 -- Slot nn: IBM Streamer Family adapter opened for: Token Ring,
xx Mbps Full Duplex.
Explanation: Denotes that the adapter was opened in token ring full
duplex mode.
User Action: This is an informational message only. No action is
necessary.
LTC0058 -- Slot nn: IBM Streamer Family adapter has entered promiscuous
copy mode.
LTC0059 -- Slot nn: IBM Streamer Family adapter has exited promiscuous
copy mode.
LTC0060 -- Slot nn: IBM Streamer Family adapter has received a remove LLC
frame.
Explanation: These three messages provide information for an adapter
that enters and exits promiscuous copy mode.
User Action: These are informational messages only. No action is
necessary.
LTC0063 -- Slot nn: A protocol error occurred while attempting to open
the adapter in full-duplex mode.
Explanation: The adapter is configured for token ring full duplex
operation, but encountered a problem when attempting to connect
to the full duplex switch.
User Action: Verify that your full duplex switch is functioning
properly and that your adapter is properly connected to it.
If this problem persists, contact your customer service center.
The following device driver messages have been reworded as follows:
LTC0034 -- Slot n: Network failure or beaconing was encountered
while inserting into the network.
Explanation: The token ring network is not functioning,
or is currently in a beaconing state. Another possibility is
that the token ring cable is not connected to the adapter
card, or the adapter is configured for the wrong speed.
User Action: Make sure the token ring cable is attached to
the appropriate connector on the adapter. Verify that the
adapter is properly configured for the ring speed (data rate)
and media type. Reboot your computer. If this problem still
exists, contact your network administrator.
LTC0037 -- Slot n: Data rate of the Token Ring does not match the
data rate configured for the adapter.
Explanation: The data rate of the network is different from
the data rate configured for the IBM Streamer Family adapter.
That difference was detected when the adapter attempted to
insert into the network.
User Action: For MCA adapters, use the reference diskette
that came with your computer to ensure that the adapter is
configured at the same speed as the Token Ring, or is
configured for autosense mode. For ISA adapters, use the
appropriate configuration program. For PCI adapters, add or
modify the DataRate paramenter in PROTOCOL.INI to the data
rate of the network to which the adapter is connected.
LTC0038 -- A new adapter cannot be opened in AutoSpeed mode if it
is the only station on the network.
Explanation: While attempting to open a new adapter in Token
Ring mode using the AutoSpeed configuration option, it was
determined that the adapter was the only station on the ring.
The adapter will not be allowed to open in order to prevent
possible network disruptions. (NOTE: some adapters use the
term 'autosense' instead of 'autospeed' to mean the same thing).
User Action: Reboot the computer at a later time, when at
least one other station is on the ring. As an alternative,
reconfigure the adapter for manual mode, specifying the
correct speed of the Token Ring to which the adapter is
connected, then restart the computer.
LTC0047 -- Could not determine the system I/O bus type
Explanation: The IBM Streamer Family NDIS MAC Driver was
unable to determine the type of I/O bus designed into the
computer system. It is looking for a Micro Channel, ISA,
EISA, or PCI bus.
User Action: Make sure your system is based on a Micro
Channel, ISA, EISA, or PCI bus and contains an industry
standard BIOS. Contact your customer service center.
(**) Trademarks
---------------
IBM is a trademark of International Business Machines, Inc.
Streamer is a trademark of International Business Machines, Inc.
LANStreamer is a trademark of International Business Machines, Inc.
EtherStreamer is a trademark of International Business Machines, Inc.
Microsoft Windows is a trademark of Microsoft, Inc.
Microsoft Windows For Workgroups is a trademark of Microsoft, Inc.