6.0 Chapter 6. Recommendations and Problem Solving
This chapter contains recommendations to help you prevent or handle
problems you may have while using the LAN Support Program NDIS (LSP NDIS).
It also outlines guidelines for adjusting the NetBIOS parameter values
when using DXMT0MOD.SYS. Adjusting these parameters can improve the
performance of the token-ring network and its attached computers.
If you do not find the information you need in this chapter, you may want
to consult other sections of the publication, as follows:
° For tips on using DOS 5.0 with LSP NDIS, see Chapter 5, "Using DOS
5.0, Windows, and QEMM-386."
° See Chapter 4, "Customizing Driver Parameters for the LAN Support
Program NDIS" if you are having trouble loading the LSP NDIS and do
not find help in this chapter. The values of the parameters may be
affecting your configuration.
Figure 6-1 tells you where to find descriptions of the topics covered in
this chapter.
+------------------------------------------------------------------------+
| Figure 6-1. Where to Find Topics in This Chapter |
+------------------------------------+-----------------------------------+
| Topic | See: |
+------------------------------------+-----------------------------------+
| Provide service information | "Service Information" in |
| | topic 6.1. |
+------------------------------------+-----------------------------------+
| Change parameters if an | "Application Requests Too Much |
| application requests too much | Buffer" in topic 6.2. |
| buffer | |
+------------------------------------+-----------------------------------+
| Change NetBIOS parameters to | "Tuning Performance When NetBIOS |
| improve the performance of a | (DXMT0MOD.SYS) Is Used in a |
| token-ring network that uses | Token-Ring Network" in topic 6.3. |
| NetBIOS | |
+------------------------------------+-----------------------------------+
| Set OPEN.ON.LOAD parameter | "Setting the OPEN.ON.LOAD |
| | Parameter in DXMT0MOD.SYS" in |
| | topic 6.4. |
+------------------------------------+-----------------------------------+
| Set OPEN.ON.LOAD parameter with | "Using the DOS LAN Requester with |
| DOS LAN Requester | DXMT0MOD.SYS" in topic 6.5. |
+------------------------------------+-----------------------------------+
| Increase the work space for | "Increasing Work Space for |
| DXME0MOD.SYS (return code X'30' or | DXME0MOD.SYS" in topic 6.6. |
| X'F8' may be returned) | |
+------------------------------------+-----------------------------------+
| Use the SWITCH command with the | "Using the SWITCH Command with |
| Asian versions of DOS | Asian Versions of DOS" in |
| | topic 6.7. |
+------------------------------------+-----------------------------------+
| Change the language in which | "Changing the Language in Which |
| load-time messages are displayed | Load-Time Messages Are Displayed" |
| | in topic 6.8. |
+------------------------------------+-----------------------------------+
| Deal with common NDIS | "Common NDIS Configuration |
| configuration errors | Errors" in topic 6.9. |
+------------------------------------+-----------------------------------+
| Use more than one protocol driver | "Using Multiple Protocol Drivers |
| (multiple protocol stacks) | with NDIS Adapters" in |
| | topic 6.10. |
+------------------------------------+-----------------------------------+
| Correct the problem if the | "Making Corrections When the |
| Installation Aid gives a message | Installation Aid Does Not Find |
| that NIF subdirectories may be | the NIFs" in topic 6.11 |
| missing from the LSP NDIS Install | |
| diskette | |
+------------------------------------+-----------------------------------+
| Reinstall LSP NDIS if it is not | "LSP NDIS Is Not Installed after |
| installed after you run the | Running the Installation Aid" in |
| Installation Aid | topic 6.12 |
+------------------------------------+-----------------------------------+
6.1 Service Information
When you request service for LSP NDIS, gather the following information
before you contact service support. The following facts enable your
service representative to help you better:
1. Adapter name
2. Other adapters in the computer
3. LSP NDIS version number (displayed when LSP NDIS is loaded)
4. Adapter speed
5. PC type and model
6. Monitor type and display adapter
7. Version of DOS
8. Which protocols you are using: NetBIOS, IEEE 802.2, or IEEE 802.5
9. Which application software you are using
10. A description of the problem
11. The contents of CONFIG.SYS
12. The contents of AUTOEXEC.BAT and PROTOCOL.INI.
6.2 Application Requests Too Much Buffer
If the application that issues the open adapter command requests too many
transmit buffers, too many link stations, or transmit buffers that are too
large, LSP NDIS fails. The error message displayed depends on the
application. For example, if you are using the NetBIOS driver
DXMT0MOD.SYS, LSP NDIS will fail if the DS, DN, ST, ES, or EST parameters
are set too high (see "NetBIOS Device Driver Keyword Parameter
Descriptions" in topic 4.4.5 for a description of these parameters). If
you are using Personal Communications/3270, LSP NDIS will fail if the path
information unit (PIU) size or the number of network stations to be
supported by a gateway are too high.
6.3 Tuning Performance When NetBIOS (DXMT0MOD.SYS) Is Used in a Token-Ring Network
This section describes changing the NetBIOS driver parameters to improve
the performance of a token-ring network and its attached computers. For a
description of the parameters discussed in this section, see "NetBIOS
Device Driver Keyword Parameter Descriptions" in topic 4.4.5.
6.3.1 Performance Tuning
No single set of parameters can be optimum for all configurations. You
need to experiment with the parameters to find the best ones for your
configuration. Performance tuning is the process of selecting parameter
values to maximize the performance of your token-ring network. The
following guidelines offer some suggestions to assist you.
6.3.2 Taking Advantage of Large Frame Sizes
Transmitting a frame requires a certain overhead that is fairly constant,
independent of the frame size. Therefore, using larger frame sizes
increases the efficiency of the computer using LSP NDIS.
For applications that can take advantage of large frame sizes, you can
improve the performance of the computer by increasing the DHB.SIZE (DS)
parameter to increase the size of the transmit frame. Final determination
of the NetBIOS session transmit frame size is a function of the value of
DHB.SIZE, the number of receive buffers in the receiver, and the maximum
frame size that can pass through a bridge in the path.
6.3.3 Increasing the Number of Outstanding Frames
The DLC.MAXOUT (MO) parameter allows you to influence the number of
outstanding frames in the network. You can increase the efficiency of the
network by allowing more data to be in transit in the network.
Setting MO to 4 increases the number of outstanding frames per NetBIOS
interface link station from 2 to 4. Increasing MO can improve the
efficiency of your network, especially if bridges are in the link station
traffic path. However, in some rare cases, increasing MO may cause
congestion at these bridges. You may also have congestion problems when
communicating with 8- or 16-KB Token-Ring Network Adapters.
6.3.4 Decreasing the Number of Acknowledgment Frames
The DLC.MAXIN (MI) parameter allows you to influence the number of LLC
acknowledgment frames on the network. Increasing MI increases the number
of frames that are received before an acknowledgment is sent. It is very
important that the MI value of the receiving station be less than the MO
value of the sending station. If the MI value of the receiving station is
greater then the MO value of the sending station, the performance of the
network is significantly degraded. It is recommended that you increase MO
and MI in all the stations in the network (for example, set MO to 4 and MI
to 2), or else allow the MI value to default to 1.
6.3.5 Reducing the Amount of Broadcast Traffic
Reducing the amount of broadcast traffic is especially valuable in
networks with bridges. The REMOTE.NAME.DIRECTORY (RND) parameter can help
reduce broadcast traffic. Setting RND to 17 is suggested. Using this
value for RND requires about 1 KB of memory in the computer.
You can also change the values of the TRANSMIT.TIMEOUT (TT) and
TRANSMIT.COUNT (TC) parameters to reduce network traffic. For example, at
the default value of TC=6, queries will be transmitted 6 times. If you
change TC to equal 3, queries will only be sent 3 times. Since queries
are sent less frequently, the traffic generated when setting up a NetBIOS
session is decreased.
Similarly, if you increase TT, you can spread the traffic load. If you
set TT=6, queries will only be generated at 3-second intervals. A
combination of TT=6 and TC=3 causes only 3 NetBIOS call queries to be
generated at 3-second intervals, instead of the default of 6 call queries
at 1/2 second intervals.
6.3.6 An Example of a NetBIOS Parameter Configuration
As an example, the following LSP NDIS driver command line for DXMT0MOD.SYS
may improve performance for an LSP NDIS adapter configured with NetBIOS:
DEVICE=\LSP\DXMT0MOD.SYS O=N MO=4 RND=17
6.4 Setting the OPEN.ON.LOAD Parameter in DXMT0MOD.SYS
The Installation Aid configures an adapter so that it can be opened on
the network. If an error message indicates that an error occurred while
opening an adapter, use the Installation Aid to reconfigure the adapter,
and then restart LSP NDIS.
If NetBIOS is loaded (DXMT0MOD.SYS) and the following error message is
displayed:
DXMT0 32E: Initialization or open error on adapter 'n'
specify OPEN.ON.LOAD=NO (O=N) for the NetBIOS driver (DXMT0MOD.SYS). If
no NetBIOS new parameter is showing in CONFIG.SYS, the default is O=N.
(This parameter is set to N automatically if you configured LSP NDIS using
the Installation Aid.)
If O=Y, NetBIOS tries to open the adapter at load time, but fails because
NETBIND is not executed until AUTOEXEC.BAT is executed.
6.5 Using the DOS LAN Requester with DXMT0MOD.SYS
During the installation of the DOS LAN Requester, the command line
parameters for the NetBIOS driver, DXMT0MOD.SYS, are added to or updated.
The OPEN.ON.LOAD parameter in NetBIOS must have the value O=N.
If O=N is not present, error message DXMT0 32E: is displayed and the
adapter fails to open. (See "Setting the OPEN.ON.LOAD Parameter in
DXMT0MOD.SYS" in topic 6.4.)
6.6 Increasing Work Space for DXME0MOD.SYS
When using an NDIS adapter, you may need to change the environment when
there is a large amount of data traffic or if many sessions are defined in
one computer, as in a disk server. For this adapter, you may also need
additional work space to accommodate the receive buffers necessary to
receive the largest frame.
One of the following events may indicate that more work space is required:
1. You get the return code:
X'30' Inadequate receive buffers for adapter to open
from the CCB command DIR.OPEN.ADAPTER.
2. You get the return code:
X'F8' Error on implicit DIR.OPEN.ADAPTER
on a NetBIOS command.
3. The application program fails to open the adapter.
A work space parameter in the IEEE 802.2 protocol driver for NDIS MAC
drivers (DXME0MOD.SYS) enables you to change the work space for this
adapter. You can increase the work space to a maximum of 64 KB. You
should increment the work space as little as possible, because it takes up
additional PC memory. See "Work Space" in topic 4.3.10 for more
information about setting the work space parameter.
6.7 Using the SWITCH Command with Asian Versions of DOS
If you plan to use the SWITCH command in DOS Version J4.0 or J5.0, you
must install LSP NDIS two times: once in DOS 3.3 or higher and once in
DOS Version J4.0 or J5.0. Each configuration requires a separate
subdirectory, and each configuration must match the language specified by
the COUNTRY command in its version of DOS.
For example, install the program in single-byte mode (U.S. English) using
DOS 3.3 or higher. Then, install it a second time in double-byte mode
(one of the Asian languages, such as Japanese or Chinese) using DOS J4.0
or J5.0. When you use the Installation Aid, specify a different target
subdirectory for each installation.
If you do a manual configuration, you must also do two configurations.
Each configuration must be located in a separate subdirectory. For
example, the configuration for DOS 3.3 or above might be in \LSP and the
configuration for DOS J4.0 or J5.0 might be in \DBLSP. One configuration
is installed in single-byte mode (U.S. English), using DOS 3.3 or higher.
The other is installed in double-byte mode using DOS J4.0 or J5.0. In
each configuration, the language in the message file must match the DOS
COUNTRY code entered as a parameter on the DXMA0MOD.SYS DEVICE= line.
(See "Selecting and Copying the Files" in topic 3.3.)
If you use the SWITCH command and do not have a configuration of LSP NDIS
that matches the new mode (whether single-byte or double-byte) and
language, the program does not run and you may get the following message:
06E: Error reading message file (DXM.MSG)
6.8 Changing the Language in Which Load-Time Messages Are Displayed
To change the language for load-time messages, you must first use the
COUNTRY command to change the language used by DOS in your computer.
Then, reconfigure LSP NDIS.
If you use the Installation Aid, it automatically makes the language for
LSP NDIS match the language specified by the DOS COUNTRY command. If you
do a manual configuration, see "Selecting and Copying the Files" in
topic 3.3 for instructions on how to make the LSP NDIS language and the
language in DOS match.
If you change the language in DOS and do not reconfigure LSP NDIS, the
program does not run and you may get the following message:
06E: Error reading message file (DXM.MSG)
6.9 Common NDIS Configuration Errors
This section describes some common NDIS configuration errors found when
using the protocol driver DXME0MOD.SYS. You can correct many of these
errors by using the Installation Aid to reconfigure the program. If
reconfiguration does not work, you may try some of the other suggestions
included with the descriptions of the errors.
The error messages from PROTMAN.DOS, NETBIND, DXME0MOD.SYS, and
DXMT0MOD.SYS are shown along with the descriptions of the errors. In the
following examples, messages generated by PROTMAN.DOS or NETBIND start
with PRO00. Refer to the descriptions of the error messages in
Appendix A, "Messages," for more information about messages from
DXME0MOD.SYS or DXMT0MOD.SYS.
Use Figure 6-2 to identify the problems associated with the error
messages. Note that error messages beginning with DXMT0 appear only if
you have configured for NetBIOS, and are not included in the table.
+------------------------------------------------------------------------+
| Figure 6-2. Where to Find Information about Error Messages |
+------------------------------------+-----------------------------------+
| For Error Message: | See: |
+------------------------------------+-----------------------------------+
| DXME0 22E: Error communicating | "The /I: Parameter Is Incorrectly |
| with Protocol Manager | Entered" in topic 6.9.2; |
| | "PROTMAN.DOS Is Not Entered in |
| | CONFIG.SYS" in topic 6.9.3; |
| | "PROTOCOL.INI File Is Not Found" |
| | in topic 6.9.6. |
+------------------------------------+-----------------------------------+
| DXME0 23E: Error reading | "Parameters in PROTOCOL.INI Are |
| PROTOCOL.INI | Missing" in topic 6.9.4. |
+------------------------------------+-----------------------------------+
| PRO0003E: PROTOCOL.INI file open | "PROTOCOL.INI File Is Not Found" |
| failure | in topic 6.9.6. |
+------------------------------------+-----------------------------------+
| PRO0010E: Invalid option | "The /I: Parameter Is Incorrectly |
| | Entered" in topic 6.9.2. |
+------------------------------------+-----------------------------------+
| PRO0023E: Cannot find Protocol | "The /I: Parameter Is Incorrectly |
| Manager | Entered" in topic 6.9.2; |
| | "PROTMAN.DOS Is Not Entered in |
| | CONFIG.SYS" in topic 6.9.3; |
| | "PROTOCOL.INI File Is Not Found" |
| | in topic 6.9.6. |
+------------------------------------+-----------------------------------+
| PRO0025E: Fail to bind | "Error in Editing PROTOCOL.INI, |
| | or Missing NDIS MAC Driver" in |
| | topic 6.9.5; |
| | "Parameters in PROTOCOL.INI Are |
| | Missing" in topic 6.9.4. |
+------------------------------------+-----------------------------------+
6.9.1 Errors Involving the NDIS MAC Driver
You will get an error message from the NDIS MAC driver if:
° The NDIS adapter is not installed in the computer
° The NDIS adapter is not functioning correctly
° Your NDIS MAC driver does not support the adapter that is installed
° The NDIS MAC driver parameters are not specified correctly in
PROTOCOL.INI.
Refer to the Installation and Testing Instructions for your adapter for
more information about the specific error messages that the NDIS MAC
driver generates.
6.9.2 The /I: Parameter Is Incorrectly Entered
If you have made a syntax mistake entering the /I: parameter, you will
receive the following error messages:
PRO0010E: Invalid option
PRO0023E: Cannot find Protocol Manager
DXME0 22E: Error communicating with Protocol Manager
DXMT0 37E: Adapter support required
To correct this error, check the syntax of the DEVICE= command line for
PROTMAN.DOS. Make sure that the command line is entered in CONFIG.SYS and
that the /I: parameter is correct. Furthermore, make sure that the
command line for PROTMAN.DOS is entered before the command lines for the
LSP NDIS drivers, as shown in"Editing CONFIG.SYS" in topic 3.3.2. See
"Using the /I: Parameter" in topic 3.3.4 for information about how to
configure the /I: parameter.
6.9.3 PROTMAN.DOS Is Not Entered in CONFIG.SYS
If PROTMAN.DOS is not entered in CONFIG.SYS, you will receive the
following error messages:
DXME0 22E: Error communicating with Protocol Manager
DXMT0 37E: Adapter support required
PRO0023E: Cannot find Protocol Manager
Refer to "Using the /I: Parameter" in topic 3.3.4 and "Editing CONFIG.SYS"
in topic 3.3.2 for information about editing CONFIG.SYS to include the
command line for PROTMAN.DOS.
6.9.4 Parameters in PROTOCOL.INI Are Missing
Several errors can be made when entering the parameters for PROTOCOL.INI,
including:
° Failing to enter the Bindings = parameter in PROTOCOL.INI
° In the named section [DXME0_MOD], not setting DriverName equal to
DXME0$ when using DXME0MOD.SYS. If you are using DXMJ0MOD.SYS,
DriverName in the named section [DXMJ0MOD_MOD] must be set equal to
NETBEUI$.
° Failing to enter the DriverName parameter.
If one of these errors has occurred, the following messages are displayed:
DXME0 23E: Error reading PROTOCOL.INI
DXMT0 37E: Adapter support required
PRO0025E: Fail to bind
Check PROTOCOL.INI if you receive these messages.
6.9.5 Error in Editing PROTOCOL.INI, or Missing NDIS MAC Driver
If the value set for Bindings = does not match the adapter and NDIS MAC
driver installed, or no NDIS MAC driver is installed, you will receive the
following error message:
PRO0025E: Fail to bind
Make sure that the module name for your adapter is contained in the
Bindings = statement.
6.9.6 PROTOCOL.INI File Is Not Found
The PROTOCOL.INI file stores configuration and binding information for all
the LSP NDIS drivers in the system and for the NDIS MAC driver. If this
file is not found by PROTMAN.DOS, PROTMAN.DOS does not load. The
following messages are displayed:
PRO0003E: PROTOCOL.INI file open failure
PRO0023E: Cannot find Protocol Manager
DXME0 22E: Error communicating with Protocol Manager
DXMT0 37E: Adapter support required
To correct this situation, reconfigure LSP NDIS using the Installation Aid
(the Installation Aid will maintain all your current LSP NDIS driver
parameter values if you specify an update to the current configuration).
If reconfiguration fails, check to see that the PROTOCOL.INI file is on
the current drive and that it is in the \LANMAN directory (the default
directory) or in a directory that you have specified using the /I:
parameter. You must add the /I: parameter to the following statement:
DEVICE=\LSP\PROTMAN.DOS
in CONFIG.SYS if PROTOCOL.INI is not in the \LANMAN directory. (See
"Using the /I: Parameter" in topic 3.3.4 for more information.)
If the problem persists, see the description of LSP NDIS driver error
message 22E: in Appendix A, "Messages."
6.10 Using Multiple Protocol Drivers with NDIS Adapters
If you plan to use more than one protocol stack with LSP NDIS, follow
these installation procedures:
1. Configure and install the other protocol stack first.
2. Use the Installation Aid to install LSP NDIS and specify that you are
updating an existing configuration. The Installation Aid will not
disturb the files from the other protocol stack if you choose to
update.
3. After LSP NDIS is installed, if the other protocol driver is a
terminate and stay resident (TSR) program, move NETBIND in
AUTOEXEC.BAT so that it is placed behind the other protocol driver.
For an example of a configuration with two protocol stacks, suppose you
have a configuration that includes IBM TCP/IP Version 2.1 for DOS, LSP
NDIS, and a Streamer Family adapter. The protocol driver for TCP/IP is
DOSTCP.SYS, which is not a TSR program. Suppose that the LSP NDIS drivers
are in the directory \LSP on the working copy and that DOSTCP.SYS is in a
path represented by \path. The Installation Aid updates AUTOEXEC.BAT,
CONFIG.SYS, and PROTOCOL.INI.
AUTOEXEC.BAT is updated to include \LSP\NETBIND. The Installation Aid
places NETBIND first in AUTOEXEC.BAT, but this location is acceptable
because DOSTCP.SYS is not a TSR program.
A sample of CONFIG.SYS might look as follows:
DEVICE=\LSP\PROTMAN.DOS /I:\LSP
DEVICE=\LSP\IBMMPC.DOS
DEVICE=\LSP\DXMA0MOD.SYS 001
DEVICE=\LSP\DXME0MOD.SYS
DEVICE=\LSP\DXMT0MOD.SYS
DEVICE=\path\DOSTCP.SYS
PROTOCOL.INI might look like this:
[PROTMAN_MOD]
DriverName = PROTMAN$
[DXME0_NIF]
DriverName = DXME0$
Bindings = IBMMPC_NIF
[TCPIP_V2]
DriverName = DOSNDIS$
Bindings = IBMMPC_NIF
[IBMMPC_NIF]
DriverName = IBMMPC$
MAXTRANSMITS = 4
MAXTXFRAMESIZE = 4216
MINRCVBUFFS = 8
SIZWORKBUF = 1120
MULTICASTNUM = 16
ENABLETXEOFINT = "YES"
ENET2OUTP = "NO"
USEVDS = "NO"
ENABLEHIPRITX = "NO"
HIPRITXACCESS = 5
HIPRITXTHRESH = 4
In this configuration, DOSTCP.SYS and DXME0MOD.SYS bind to the same NDIS
adapter. If you need to specify a locally administered address, do not
use the command line parameter ADDR with DXME0MOD.SYS. Instead specify
the address in the MAC section of the PROTOCOL.INI file, as described in
"Network Adapter Address Configuration" in topic 4.7.1.
6.11 Making Corrections When the Installation Aid Does Not Find the NIFs
The Installation Aid displays this message when the NIFs are not found:
Network Information Files (NIFs) not found on LSP Install diskette.
NIF subdirectories may be missing from your LSP Install diskette.
If you see this message, the Installation Aid has failed to access the
NIFs. The NIFs are in a subdirectory of the \NIF subdirectory of the root
directory of the LSP NDIS diskette (see Appendix D, "Contents of the LAN
Support Program NDIS Version 1.0"). Make sure that your backup copy of
the LSP NDIS diskette has the same directory structure as the original LSP
NDIS diskette and reconfigure using the Installation Aid.
6.12 LSP NDIS Is Not Installed after Running the Installation Aid
The DOS NDIS driver files for your adapter are located in the directory
\DOS on the same diskette as LSP NDIS. Therefore, for the Installation
Aid, the driver diskette it requests is the same as the LSP NDIS diskette.
If you had difficulty with installation, be sure you accepted the default
answer Yes to the question Do you have driver diskettes?. Then, when the
Installation Aid prompts you for the driver diskette, simply press Enter,
because the diskette the Installation Aid needs is already inserted.
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.