3.0 Chapter 3. Configuring the LAN Support Program NDIS Manually
The Installation Aid enables you to do a complete configuration,
including changing all the driver parameters. However, if you prefer to
do a manual configuration, the following steps outline the process:
Note: For credit card adapters, an additional installation step may be
required. See the Installation and Testing Instructions for your adapter
for more information.
1. Prepare your computer for installing the LAN Support Program NDIS (LSP
2. Make a backup copy of the diskette that contains the LSP NDIS files.
3. Decide which LSP NDIS drivers you want to use.
4. Select the files to copy from the backup disk to the working copy. (1)
5. Copy the files from the backup disk to the working copy.
6. Edit CONFIG.SYS.
7. Edit AUTOEXEC.BAT.
8. Edit PROTOCOL.INI.
9. Load the working copy and restart the computer.
If you plan to use two adapters, first read the instructions for
configuring one adapter. Then, proceed to the special instructions that
apply when configuring for two adapters.
For a description of the LSP NDIS Version 1.0 drivers, see "LSP NDIS
Driver Summary" in topic 4.1.
(1) A working copy is a copy of the program that has been
configured for use in a particular computer. The working
copy can be installed on a diskette or on a hard disk.
3.1 Preparing the Computer
° If you are starting the computer from a hard disk, make sure that DOS
3.3 or higher has been installed on the hard disk. Use the DOS VER
command to check the DOS level. If you must reformat your hard disk,
be sure to back up your files. See the IBM Personal Computer Disk
Operating System user's guide for your version of DOS for
° If you will be starting the computer from a diskette, be sure that you
have a formatted diskette for use as the working copy. It must be
formatted as a DOS 3.3 or higher system diskette. If it is not
already formatted, use the DOS FORMAT command with the /S option to
3.2 Making a Backup Copy
Make a backup copy of the diskette that contains the LSP NDIS files using
the DOS DISKCOPY command, or copy the contents of the diskette to the hard
disk. If you copy the files to a hard disk, be sure to maintain the
directory structure and file names found on the LSP NDIS diskette.
After you make the backup copy, keep the original diskette in a safe
3.3 Selecting and Copying the Files
Create a directory on the working copy using the DOS MD command (for
example, the directory \LSP). After you select the LSP NDIS files, you
should copy them to this directory. Next, select and copy the following
DXMMSG.ccc (ccc represents the DOS country code; this file must be
renamed to DXM.MSG).
DXMA0MOD.SYS is the interrupt arbitrator for all the LSP NDIS driver
files. It has a language parameter (ccc) that defines the language in
which load-time messages are displayed. This parameter corresponds to one
of the values used by the DOS COUNTRY command defined in the IBM Personal
Computer Disk Operating System user's guide for your version of DOS.
If this parameter is equal to 001, all load-time messages are displayed in
U.S. English. See "Parameter for the Interrupt Arbitrator Device Driver
(DXMA0MOD.SYS)" in topic 4.2 for a syntax example and a list of the
country codes and corresponding languages supported by LSP NDIS. Choose
the desired country code from this list and specify it as the command line
parameter for DXMA0MOD.SYS in CONFIG.SYS.
DXMMSG.ccc is the message file. Its extension, represented by ccc, must
match the language parameter for DXMA0MOD.SYS. For example, if the
parameter is 034 (for Spanish), you must copy DXMMSG.034 to your working
copy. When you copy DXMMSG.034, you must copy it as DXM.MSG. For
example, you could use this DOS command if you were copying the LSP NDIS
files to the C: drive:
COPY A:\DXMMSG.034 C:\LSP\DXM.MSG
If the message file is missing, named incorrectly, or does not correspond
to the language parameter specified for DXMA0MOD.SYS, LSP NDIS cannot be
3.3.1 LSP NDIS Drivers
Select and copy the required LSP NDIS drivers:
The NDIS files associated with the adapter that was provided with LSP
The protocol driver, DXME0MOD.SYS or DXMJ0MOD.SYS, or both
DXME0MOD.SYS is the protocol driver for the IEEE 802.2 interface;
DXMJ0MOD.SYS is the protocol driver for the NetBIOS interface. At least
one of these protocol drivers must be included; DXMT0MOD.SYS may also be
required. See "Choosing the LSP NDIS Drivers to Provide IEEE 802.2 and
NetBIOS Support" in topic 2.1.2 for more information.
Both the NDIS MAC driver files and the LSP NDIS drivers are found on the
LSP NDIS diskette. See Appendix D, "Contents of the LAN Support Program
NDIS Version 1.0."
3.3.2 Editing CONFIG.SYS
Be sure to copy the existing CONFIG.SYS with a numeric file extension so
that you can retrieve it if necessary. Then, add the DEVICE= statements
to CONFIG.SYS to load the LSP NDIS drivers.
The DEVICE= statements must be entered in CONFIG.SYS in the correct
sequence, or the program will not start. In the following example using a
Streamer(*) Family Adapter., all the files are located in the directory
\LSP. The /I: parameter is used to enable PROTMAN.DOS to locate
PROTOCOL.INI. See "Using the /I: Parameter" in topic 3.3.4 for more
For one NDIS adapter with both IEEE 802.2 and NetBIOS support, the
sequence is as follows when the NetBIOS support is provided by
If you do not want NetBIOS, keep the same sequence but remove the
statement for DXMT0MOD.SYS.
Note: If you set any parameters for DXMT0MOD.SYS, you must include the
parameter O=N. See "Keyword Values for DXMT0MOD.SYS New Parameters" in
topic 4.4.2 for more information.
For one NDIS adapter with only NetBIOS support, the sequence is as follows
when DXMJ0MOD.SYS provides the NetBIOS support:
Using DXMJ0MOD.SYS may result in improved performance.
3.3.3 Rules for Editing CONFIG.SYS
1. Each DEVICE= line must not exceed one line in the CONFIG.SYS file.
2. Be sure to change only the lines needed for the LSP NDIS drivers.
3. You must list the interrupt arbitrator device driver (DXMA0MOD.SYS)
before DXME0MOD.SYS, DXMT0MOD.SYS, or DXMJ0MOD.SYS. PROTMAN.DOS must
precede the NDIS MAC driver, DXMA0MOD.SYS, and the LSP NDIS drivers.
4. If the NetBIOS interface device driver is required, list it last.
5. The DEVICE= line needs to include the path DEVICE=\LSP\DXM... where
\LSP represents the directory. You can substitute another directory
name in place of \LSP.
For more help determining the order in which the drivers in CONFIG.SYS are
listed, see Appendix B, "Sample Configurations" in topic B.0.
3.3.4 Using the /I: Parameter
If all the files are copied to one directory other than \LANMAN,
CONFIG.SYS must be edited because the protocol manager, PROTMAN.DOS, by
default, looks for PROTOCOL.INI in a directory called \LANMAN. To
override that default, the /I: parameter must be added to the
DEVICE=\LSP\PROTMAN.DOS statement in CONFIG.SYS. Add it as follows:
2. One space must precede the /I: parameter. Write the parameter after
3. Behind the parameter, list the drive and directory in which
PROTOCOL.INI is found. No space is allowed between the colon in the
/I: parameter and the next character entered (in this example, this
character is C). In this example, PROTMAN.DOS and PROTOCOL.INI are in
the \LSP directory on the C: drive:
The /I: parameter can also be used to specify a drive and directory
different from the one where PROTMAN.DOS is found. If PROTMAN.DOS is in
the directory \LSP on disk A: and PROTOCOL.INI is in the directory \NDIS
on disk C:, type this:
3.4 Editing the AUTOEXEC.BAT File
Save a copy of the current AUTOEXEC.BAT with a new file extension. Then,
edit AUTOEXEC.BAT by adding the following line:
Put this line in AUTOEXEC.BAT after any statements for terminate and stay
resident (TSR) NDIS protocol drivers and before any statements for
application programs supported by LSP NDIS. NETBIND is the NDIS protocol
binding utility file; it must be executed before any network activity is
3.5 Editing the PROTOCOL.INI File
PROTOCOL.INI is a file that contains sample parameters associated with
each LSP NDIS protocol driver and the Streamer Family adapter NDIS MAC
driver. It is recommended that you use the sample of PROTOCOL.INI shipped
on the LSP NDIS Version 1.0 diskette. (2) PROTOCOL.INI contains a named
section for the NDIS MAC driver and for each LSP NDIS protocol driver.
Each named section is identified by a module name, which is [DXME0_MOD]
for DXME0MOD.SYS or [DXMJ0MOD_MOD] for DXMJ0MOD.SYS. The named section
consists of the module name followed by the parameters for the NDIS MAC
driver or protocol driver. (3) The parameters for the protocol drivers
include a keyword DriverName and a keyword Bindings. The parameter for
Bindings is left blank. You must enter the module name for your adapter
as the parameter for Bindings = to enable the protocol driver to be bound
with the NDIS MAC driver. See Appendix B, "Sample Configurations" for
examples of the Bindings = statement.
For example, if you are using a Streamer Family adapter, enter IBMMPC_MOD
after the Bindings = statement in [DXME0_MOD]. This will configure the
Streamer Family adapter as a primary NDIS adapter supported by the
protocol driver DXME0MOD.SYS. After you edit PROTOCOL.INI, the named
section will look like this:
DriverName = DXME0$
Bindings = IBMMPC_MOD
Information about editing PROTOCOL.INI for two adapters is found in
"Configuring for Two Adapters" in topic 3.6. If you want to set up a
single adapter as an alternate adapter, see "Editing PROTOCOL.INI for
Primary or Alternate Adapters" in topic 3.5.1.
(2) If you have previously configured LSP NDIS using the
Installation Aid, the working copy will not contain the
complete sample PROTOCOL.INI file. For a complete copy of
PROTOCOL.INI, use the version of PROTOCOL.INI found on your
backup copy of the LSP NDIS diskette.
(3) In addition to named sections for LSP NDIS drivers, you may
see [DXMAIDXCFG]. This named section contains parameters
used only by the Installation Aid. You should ignore it.
3.5.1 Editing PROTOCOL.INI for Primary or Alternate Adapters
Adapters may be configured as primary or alternate, depending on how the
application addresses them. If you have just one Streamer Family adapter
and you wish to make it primary, enter the module name of the adapter.
For example, as previously mentioned, type:
Bindings = IBMMPC_MOD
To configure one adapter as an alternate adapter, you should edit the
Bindings = statement differently depending whether you are using
DXME0MOD.SYS or DXMJ0MOD.SYS. If you are using DXME0MOD.SYS, DriverName
is set equal to DXME0$. To configure the adapter as an alternate adapter,
Bindings = "",IBMMPC_MOD
The double quotes with no space between them signify a null parameter that
takes the place of a name for the primary adapter.
If you are using DXMJ0MOD.SYS, DriverName is set equal to NETBEUI$. To
configure the adapter as an alternate adapter, type:
Bindings = IBMMPC_MOD
Then, set the LANABASE parameter in the [DXMJ0MOD_MOD] section of
PROTOCOL.INI to a value equal to 1.
See Appendix B, "Sample Configurations" in topic B.0 for some examples of
lines from PROTOCOL.INI.
3.5.2 Editing Rules for PROTOCOL.INI
1. Blank spaces around the "=" sign are not significant, nor are trailing
blanks on the line. Except for these leading and trailing blanks, all
other characters of the value string are taken as they are
2. A line starting with a semicolon in column 1 is a comment and is
ignored. Entirely blank lines are also ignored.
3. Lines may be as long as required. Continuation lines are not
supported. Lines end with the Carriage Return (CR) and Line Feed (LF)
3.6 Configuring for Two Adapters
Before you read this section, you need to read the configuration
instructions for a single adapter. A Streamer Family adapter is used as
an example on the following pages. Please see the Installation and
Testing Instructions for more specific information about your adapter.
To configure for two Streamer Family adapters, you must edit CONFIG.SYS
and PROTOCOL.INI, and copy the required files to one directory. You
should already have entered NETBIND in AUTOEXEC.BAT.
3.6.1 Editing the CONFIG.SYS File for Two Adapters
Since both Streamer Family adapters use the same NDIS MAC driver, only one
DEVICE= is required to load IBMMPC.DOS Likewise, the LSP NDIS drivers
require only one statement each. Therefore, CONFIG.SYS is edited the same
way for one or two Streamer Family adapters. See "Editing CONFIG.SYS" in
topic 3.3.2 for examples.
3.6.2 Editing the PROTOCOL.INI File
You must write the module names for your NDIS adapters after the Bindings
= statement in the named sections of PROTOCOL.INI for each LSP NDIS
protocol driver you are using.
When two identical adapters (such as two Streamer Family adapters) are
installed in one computer, both are ordinarily supported by the same NDIS
MAC driver, but a separate named section for the NDIS MAC driver is
required for each adapter. The first module name IBMMPC_MOD identifies
the primary adapter and the second module name IBMMPC2_MOD identifies the
alternate adapter. For example, for two adapters using DXME0MOD.SYS, edit
PROTOCOL.INI as follows:
DriverName = PROTMAN$
DriverName = DXME0$
Bindings = IBMMPC_MOD, IBMMPC2_MOD
DriverName = IBMMPC$
DriverName = IBMMPC$
Appendix B, "Sample Configurations" shows an example of some of the
IBMMPC.DOS parameters used in PROTOCOL.INI.
3.6.3 What's Next?
If you plan to configure device driver parameters, see Chapter 4,
'Customizing Driver Parameters for the LAN Support Program NDIS'
If you load LSP NDIS from a diskette, insert the working copy into the
diskette drive. If you load LSP NDIS from a hard disk, make sure the
diskette drives are empty. To activate the program, press and hold Ctrl
and Alt; then, press Del. Release all keys. A copyright statement will
be displayed. Look for messages. If there are no messages or if there
are only information messages, LSP NDIS is correctly loaded. If any error
messages are displayed, LSP NDIS may not be correctly installed; see
Appendix A, "Messages." For additional help, see Chapter 6,
"Recommendations and Problem Solving." If no LSP NDIS copyright statement
is displayed, LSP NDIS is not installed or has been removed. In this
case, make a new backup copy of LSP NDIS and reinstall it.
See "Removing the LAN Support Program Configuration" in topic 2.2.5 to
remove the program.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.