C.0 Appendix C. Files Required for NDIS Adapters
In the case of NDIS adapters, the IEEE 802.2 protocol driver for NDIS MAC
drivers (DXME0MOD.SYS) is part of an NDIS protocol stack that provides an
IEEE 802.2 interface for IEEE 802.5 frame formats. If you also need
NetBIOS support when using DXME0MOD.SYS, install DXMT0MOD.SYS or
DXMJ0MOD.SYS. See "Choosing the LSP NDIS Drivers to Provide IEEE 802.2
and NetBIOS Support" in topic 2.1.2.
NDIS is the LAN Manager Network Driver Interface Specification, which was
jointly developed by Microsoft and 3Com. It is the LAN Manager driver
architecture that lets a DOS or an Operating System/2(*) (OS/2(*)) system
support one or more network adapters and protocol stacks. It provides a
standardized way for writing drivers for network adapters and
communications protocols. It also defines the rules for configuring and
binding multiple drivers into the desired set of layered protocol stacks.
Following is a description of NDIS drivers and files that are part of the
NDIS protocol stack. Refer to Chapter 3, "Configuring the LAN Support
Program NDIS Manually," and Chapter 6, "Recommendations and Problem
Solving," for more information.
NDIS protocol manager (PROTMAN.DOS)
The protocol manager (PROTMAN.DOS) is a DOS device driver that
provides a standardized way for multiple MAC and protocol drivers to
get configuration information and bind together into the desired
protocol hierarchy. PROTMAN.DOS must be included in the CONFIG.SYS
file before DXME0MOD.SYS, DXMJ0MOD.SYS, or the NDIS MAC driver.
The protocol manager reads the NDIS configuration information out of
the PROTOCOL.INI file and makes it available to the protocol driver
and to the NDIS MAC drivers. The protocol manager looks for
PROTOCOL.INI in the default directory \LANMAN on the same disk from
which DOS was loaded. You can use the /I: parameter on the DEVICE=
line in CONFIG.SYS to specify the directory where PROTOCOL.INI is
found if PROTOCOL.INI is not in the default directory. For example,
specifies that PROTMAN.DOS is located in the \LSP directory on the C:
drive and that it can find PROTOCOL.INI in the NDIS directory on the
Note: When entering this /I: parameter, be sure to leave a blank
space in front of the parameter, as shown in the preceding example.
As outlined in the installation instructions in Chapter 3,
"Configuring the LAN Support Program NDIS Manually," if you are
configuring the LAN Support Program NDIS (LSP NDIS) manually, you must
copy PROTMAN.DOS and PROTOCOL.INI to the working copy.
NDIS configuration file (PROTOCOL.INI)
PROTOCOL.INI contains configuration information that is used by the
protocol manager and NETBIND to establish communication between the
protocol driver and the NDIS MAC drivers. A sample of this file is
included with LSP NDIS. PROTOCOL.INI must be in the \LANMAN directory
on the drive from which DOS is loaded, or in the directory specified
by the /I: parameter for the PROTMAN.DOS command line in CONFIG.SYS.
PROTOCOL.INI is divided into named sections for each module in the
NDIS system. Each named section is followed by configuration
parameters for that module. In addition to the parameters stated in
PROTOCOL.INI, other parameters for the protocol driver DXME0MOD.SYS
are specified on the CONFIG.SYS DEVICE= command line. For information
about these parameters, see "Parameters for DXME0MOD.SYS" in
topic 4.3; see "Parameters for DXMJ0MOD.SYS" in topic 4.7 for more
information about the parameters for DXMJ0MOD.SYS. Refer to the
Installation and Testing Instructions for your adapter for more
information about the parameters for the NDIS MAC driver.
In the version of PROTOCOL.INI shipped with LSP NDIS, [DXME0_MOD] is
the module name for DXME0MOD.SYS., and the driver name for
DXME0MOD.SYS is DXME0$. [DXMJ0MOD_MOD] is the module name for
DXMJ0MOD.SYS, and its driver name is NETBEUI$. In the process of
configuring LSP NDIS, the module names of the adapters that will be
bound to DXME0MOD.SYS must be entered after the Bindings = statement
under [DXME0_MOD]. The process of binding is the same for
DXMJ0MOD.SYS, except that the Bindings = statement is found in the
named section [DXMJ0MOD_MOD].
The NDIS MAC driver must be listed in CONFIG.SYS. This configuration
can be done manually or by using the Installation Aid. The order in
which two adapters are defined in the Bindings = statement determines
whether the adapter is primary or alternate. See Chapter 3,
"Configuring the LAN Support Program NDIS Manually" for more
information about using manual configuration.
NDIS MAC driver
An NDIS MAC driver such as IBMMPC.DOS is a DOS device driver that
provides low-level access to the adapter. The main function of the
MAC driver is to support transmitting and receiving packets. It
communicates with DXME0MOD.SYS and DXMJ0MOD.SYS using NDIS Version
2.01 or earlier. The NDIS MAC driver must be loaded in CONFIG.SYS
after PROTMAN.DOS and before DXMA0MOD.SYS.
NDIS protocol drivers (DXME0MOD.SYS and DXMJ0MOD.SYS)
NDIS protocol drivers provide higher level communication services from
data link to session. DXME0MOD.SYS is a protocol driver that provides
an IEEE 802.2 interface at the top and interfaces with the NDIS MAC
driver at the bottom. DXMJ0MOD.SYS is a protocol driver that provides
a NetBIOS interface at the top and interfaces with an NDIS MAC driver
at the bottom.
NETBIND is a program that initiates the bind process between the NDIS
protocol driver and the NDIS MAC driver. Adapter activity cannot
begin until the bind process is completed. NETBIND should be coded at
the beginning of AUTOEXEC.BAT.
Other LSP NDIS drivers are also used with NDIS adapters; see "LSP NDIS
Driver Summary" in topic 4.1 for more information.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.