home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
DOSNDI.FAX
< prev
next >
Wrap
Text File
|
1994-11-28
|
4KB
|
112 lines
Changing Config params for LANStream, DO 2/25/94..
DOS NDIS procedure - LANStreamer (Version 1.0)
The following instructions are to be used to change the customer's
configuration parameters for the IBMTRDB NDIS device driver. These
instructions apply to the adapters listed here:
IBM LANStreamer (TM) MC 32
IBM LANStreamer (TM) MC 16
----------------------------------------------------------------------
DOS Users (IBMTRDB.DOS)
-----------------------
1) Locate the PROTOCOL.INI file being used by the system:
a) Look in the CONFIG.SYS file on the boot drive (usually C:)
for the statement that loads the Protocol Manager device
driver. Note that in the customer's CONFIG.SYS file, the
directory xxxxxx may be the same as directory yyyyyy, which
is a normal occurrence.
Example:
DEVICE=C:\xxxxxx\PROTMAN.DOS /I:C:\yyyyyy
b) If the /I: parameter exists in the customer's CONFIG.SYS
file, the PROTOCOL.INI file is located in the drive and
directory specified by it, such as C:\yyyyyy used above.
Make a note of this location (drive and directory) and
proceed to step 2.
c) If the /I: parameter does not exist in the customer's
CONFIG.SYS, the PROTOCOL.INI file is located in the same
directory as the PROTMAN.DOS file, such as C:\xxxxxx used
above. Make a note of this location (drive and directory)
and proceed to step 2.
2) At the command prompt, change to the location (drive and
directory) of the PROTOCOL.INI file.
Example:
C: <Enter>
cd \yyyyyy <Enter>
3) Make a backup copy of the PROTOCOL.INI file.
4) Edit the PROTOCOL.INI file.
5) Locate the first section of the PROTOCOL.INI file that contains
the name of the device driver (IBMTRDB$).
Example:
DriverName = IBMTRDB$
6) In the current section, Add/Change the LOOPBACK parameter setting
to 0 (zero).
Example:
LOOPBACK = 0
7) If you have a LANStreamer MC 16, complete this step. If you
have a LANStreamer MC 32, skip to step 8.
Modify the receive buffer size so that it will hold an entire
frame:
a) Add/Change the SIZWORKBUF parameter setting to the value of
the largest expected receive frame size plus 4 (four).
Example: - for largest expected receive frame of 4250
(including both user data and headers)
SIZWORKBUF = 4254
If you are unsure of the largest receive frame size you
can guarantee any frame will fit in the buffer by setting
the buffer size to 18000 (Token-Ring maximum frame size).
SIZWORKBUF = 18000
b) If you are **ABSOLUTELY CERTAIN** that the value used in
Step 7a is the largest frame size that will EVER be received
from the network, proceed to step 8.
NOTE: if the value of the SIZWORKBUF that was used in
Step 7a is considerably larger than the value
that was previously used, you may need to reduce
the MINRCVBUFFS parameter setting if you encounter
problems with not having enough memory. Make sure
that the product of SIZWORKBUF and MINRCVBUFFS is
less than 60,000 bytes. See the example in Step 7c
(below) for an illustration of setting this parameter
c) If unsure of the largest frame size that will ever be
received, Add/Change the MINRCVBUFFS parameter setting to
1 (one). (Note that this may cause a noticeable performance
degradation).
Example:
MINRCVBUFFS = 1
8) Repeat steps 6 and 7 for all remaining sections of the
PROTOCOL.INI file that contain the DriverName = IBMTRDB$ line.
9) When finished, save the changed PROTOCOL.INI file. It should
remain located in the current directory (from step 2).
10) Reboot the computer.
Last Updated: 12/16/93
12/31/99