home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
NEWADA.FAX
< prev
next >
Wrap
Text File
|
1994-11-28
|
14KB
|
399 lines
Customizing LS30 Ripl Servers to support n 4/20/94
HOW TO CUSTOMIZE AN EXISTING IBM OS/2 LAN SERVER
VERSION 3.0 RIPL SERVER TO SUPPORT NEW NDIS-TYPE ADAPTERS
DESCRIPTION OF SYMPTOMS:
Need to customize an existing IBM OS/2 LAN Server Version
3.0 RIPL server to support new NDIS-type adapters.
SUMMARY OF RESOLUTION:
Follow the instructions below.
DETAILS OF RESOLUTION:
****NOTE: Throughout this document some code strings are
presented on two lines because of space constraints.
They are indicated by "(con't on next line)".
When copying these lines, they should be written
as one continous line.
This document describes how to customize an existing OS/2 LAN
Server version 3.0 RIPL server to attempt to support new
NDIS-type adapters. This document does not imply that IBM
will officially support such new adapters. The only adapters
that are officially supported are those listed in the "IBM
OS/2 Network Administrator Reference Volume 1: Planning and
Installation Version 3.0".
The following description uses "IBM16TR" to represent the new
adapter being added to the RIPL support.
1. Create the following new subdirectories:
\IBMLAN\RPL\DOS\IBM16TR
\IBMLAN\RPL\IBMCOM\IBM16TR
NOTE: The subdirectory name can be anything that is
unique. "IBM16TR" is used here for example
purposes.
2. From the adapter Diagnostics diskette, copy the
following files (for example purposes, the device
driver name is assumed to be "IBM16TR" and the
drive is assumed to be "C"):
a) from the \DOS subdirectory copy the DOS device
driver file(s):
IBM16TR.DOS
(copy to C:\IBMLAN\RPL\DOS subdirectory)
IBM16TR.MSG
(copy to C:\IBMLAN\RPL\DOS subdirectory)
b) from the \OS2 subdirectory copy the OS/2 device
driver file(s)
IBM16TR.OS2
(copy to C:\IBMLAN\RPL\IBMCOM\MACS subdirectory)
IBM16TR.MSG
(copy to C:\IBMLAN\RPL\IBMCOM subdirectory)
IBM16TRH.MSG
(copy to C:\IBMLAN\RPL\IBMCOM subdirectory)
NOTE: Some adapter might not have *.MSG files.
3. Create a new DOS PROTOCOL.INI file in the subdirectory
created in step 1. A sample PROTOCOL.INI for the
IBM16TR adapter follows:
PROTMAN_MODU
DriverName = PROTMAN$
DXMAIDXCFGU
DXME0_MOD = DXME0.NIF
IBM16TR_MOD = IBM16TR.NIF
DXME0_MODU
DriverName = DXME0$
Bindings = IBM16TR_NIF
IBM16TR_NIFU
DRIVERNAME = IBM16TR$
(Add any additional parameters required by the new
adapter.)
4. Copy the file CONFIG.20 from the \IBMLAN\RPL\IBMCOM\IBM16TR
directory into the \IBMLAN\RPL\IBMCOM\IBM16TR directory.
5. Edit C:\IBMLAN\RPL\IBMCOM\IBM16TR\CONFIG.20 file and make
the following change:
- Locate the following statement:
DEVICE=Z:\IBMCOM\MACS\IBMTOK.OS2
and change it to
DEVICE=Z:\IBMCOM\MACS\IBM16TR.OS2
6. Create a new OS/2 PROTOCOL.INI file in the
\IBMLAN\RPL\IBMCOM\IBM16TR directory. A sample
PROTOCOL.INI file follows:
PROT_MANU
DriverName = PROTMAN$
IBMLXCFGU
IBM16TR_nif = IBM16TR.nif
LANDD_nif = LANDD.nif
NETBEUI_nif = NETBEUI.nif
;*----------------------------------------------*
;*------------- PROTOCOL SECTION ---------------*
;*----------------------------------------------*
LANDD_nifU
DriverName = LANDD$
Bindings = IBM16TR_nif
ETHERAND_TYPE = "I"
SYSTEM_KEY = 0x0
OPEN_OPTIONS = 0x2000
TRACE = 0x0
LINKS = 8
MAX_SAPS = 3
MAX_G_SAPS = 0
USERS = 3
TI_TICK_G1 = 255
T1_TICK_G1 = 15
T2_TICK_G1 = 3
TI_TICK_G2 = 255
T1_TICK_G2 = 25
T2_TICK_G2 = 10
IPACKETS = 250
UIPACKETS = 100
MAXTRANSMITS = 6
MINTRANSMITS = 2
TCBS = 64
GDTS = 30
ELEMENTS = 800
NETBEUI_nifU
DriverName = netbeui$
Bindings = IBM16TR_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
SESSIONS = 40
NCBS = 85
NAMES = 17
SELECTORS = 5
USEMAXDATAGRAM = "NO"
ADAPTRATE = 1000
WINDOWERRORS = 0
TI = 30000
T1 = 500
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 8
NAMECACHE = 0
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 2
PACKETS = 350
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 5
;*----------------------------------------------*
;*--------------- MAC SECTION ------------------*
;*----------------------------------------------*
IBM16TR_nifU
DriverName = IBM16TR$
(add any addition parameters needed by the adapter)
7. Edit the file \IBMLAN\RPL\NDISDD.PRO and add an entry for
the IBM16TR adapter. If the new entry is added to the
end of the file, add a blank line as the last record in
the file.
A sample entry follows:
IBM16TR.DOS IBM16TR
>>>> NOTE: Be sure you add a blank line at the <<<< <<
>>>> end of this file as stated above. <<<< <<<<<<<
The first field is the name of the DOS device driver.
The second field is the name of the directories that
contain the default configuration information for the
adapter. In this case,
\IBMLAN\RPL\DOS\IBM16TR
(contains DOS PROTOCOL.INI)
\IBMLAN\RPL\IBMCOM\IBM16TR
(contains OS2 CONFIG.20 and PROTOCOL.INI files)
NOTE: The assumption is that each adapter has a unique
DOS device driver name.
8. In the C:\IBMLAN\RPL directory, create a new DOS CNF
file for the adapter. It is recommended that the first
three characters of the name be 'DOS'. A sample CNF file,
called DOSND16T.CNF, follows for the IBM16TR adapter:
; DOS Boot Block Configuration (adapter xxxxxxx)
BASE 7C0H
RPL DOS\RPLBOOT.SYS
LDR DOS\RPLLOADR.COM ~
EXE d:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~
DAT DOS\IBM16TR\PROTOCOL.INI
DAT DOS\IBM16TR.MSG
DAT d:\IBMLAN\DOSLAN\LSP\DXM.MSG
DRV d:\IBMLAN\DOSLAN\LSP\DXMT0MOD.SYS (con't on next line)
PBA=0~S=12~ST=12~C=14~O=N ~
DRV d:\IBMLAN\DOSLAN\LSP\DXME0MOD.SYS ~ 10 ~
DRV d:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS ccc ~ ~
DRV DOS\IBM16TR.DOS ~ n ~
DRV d:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~
d: = the drive id where IBMLAN is installed,
ccc = the country code and
n = the amount of optional additional memory
required by the device driver. If no additional
memory is required, replace n with the '~' (tilde)
character. This value, if required, will have to
be determined by trial and error.
The statement 'DAT DOS\IBM16TR.MSG' is only needed if
*.MSG files exist for the device driver.
9. In the C:\IBMLAN\RPL directory, create a new OS2 CNF
file for the adapter. The following naming convention
should be used:
a. First three characters, 'OS2'.
b. Characters 4 and 5 identify the OS/2 operating
system type:
20 - OS/2 2.0
2A - OS/2 2.00.1
21 - OS/2 2.1
c. Characters 6-8 can be any unique characters.
A sample CNF file, called OS22116T.CNF, follows for the
IBM16TR adapter:
; OS/2 Boot Block Configuration (Adapter IBM16TR)
;
RPL DOS\RPLBOOT.SYS
DAT DOS\MFSD20.SYS
ORG 1000H
LDR OS2.20\OS2LDR ~ OS2LDR UFSD.SYS MFSD20.SYS
DAT DOS\UFSD.SYS
DAT DOS\IBM16TR\PROTOCOL.INI
DAT DOS\IBM16TR.MSG
DAT d:\IBMLAN\DOSLAN\LSP\DXM.MSG
EXE d:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~
DRV d:\IBMLAN\DOSLAN\LSP\DXMT0MOD.SYS PBA=0~O=N ~ ~
DRV d:\IBMLAN\DOSLAN\LSP\DXME0MOD.SYS ~ 6 ~
DRV d:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS ccc ~
DRV DOS\IBM16TR.DOS ~ n ~
DRV d:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~
d: = the drive id where IBMLAN is installed
ccc = the country code
n = the amount of optional additional memory required
by the device driver. If no additional memory is
required, replace n with the '~' (tilde) character.
This value, if required, will have to be determined
by trial and error.
The statement 'LDR OS2.21\OS2LDR ~ OS2LDR UFSD.SYS
MFSD21.SYS' should be updated to reflect the approriate
type OS/2 operating system, i.e. OS2.20, OS2.20a, or OS2.21.
The statement 'DAT DOS\IBM16TR.MSG' is only needed if *.MSG
files exist for the device driver.
10. Edit the \IBMLAN\RPL\RPL.MAP file and add both DOS and OS2
server records to the file.
The following is a sample DOS server record:
yyyyyyyyyyyy dosnd16T.cnf 3 10 N (con't on next line)
IBMLAN$ DOS~IBM~16/4~II ~ ~ ,,, Z R_DIBM16TR ~ ~
'dosnd16T.cnf' = the CNF file created in step 9.
'DOS~new~adapter~description' can be any
descriptive string you want. It is recommended
that the first three characters be 'DOS'.
Embedded blanks are not allowed and must be
replaced with the '~' (tilde) character.
'R_DIBM16TR' is a unique string that does not
appear in any other field 12 server record.
The first three characters should be 'R_D'.
The remaining characters can be anything you wish.
The following is a sample OS2 server record:
yyyyyyyyyyyy os22116T.cnf 3 10 N ~ (con't on next line)
OS2~IBM~16/4~II ~ ~ ,,, ~ R_21_O16 ~ ~
'os22116T.cnf' = the CNF file created in step 9.
'OS2~new~adapter~description' can be any descriptive
string you want. It is recommended that the first
three characters be 'OS2'. Embedded blanks are not
allowed and must be replace with the '~' (tilde)
character.
'R_20_OIBM16TR' is a unique string that does not appear in
any other field 12 server record. The first six
characters should be 'R_21_O' where 21 indicates the
OS/2 operating system type, i.e. 20, 2A, or 21.
The remaining characters can be anything you wish.
Note: The sample server records have been split into two lines
for readablility. The server record in RPL.MAP must be
a single line of data.
It will now be possible to select the new server records when
defining RIPL clients. The server record selected determines
what files are used to configure the RIPL client.
Default RIPL clients are configured for family 2(MCA) machines
with VGA displays. If the adapter added is for an ISA/EISA
type machine, then do the following:
a. Create a RIPL client model machine for the adapter. For
example, MODEL16T.
b. If you do not have the new RIPL Support updates for OS/2 2.1,
do the following:
- Update the file \IBMLAN\RPL\FITS\MODEL16T.FIT. Locate the
following entries:
; PS/2 MACHINES
; d:\OS2\MDOS\VDMA.SYS OS2.2x\OS2\MDOS\VDMAPS2.SYS
; AT MACHINES
; d:\OS2\MDOS\VDMA.SYS OS2.2x\OS2\MDOS\VDMAAT.SYS
and change them to:
; PS/2 MACHINES
; d:\OS2\MDOS\VDMA.SYS OS2.2x\OS2\MDOS\VDMAPS2.SYS
; AT MACHINES
; d:\OS2\MDOS\VDMA.SYS OS2.2x\OS2\MDOS\VDMAAT.SYS
d: = the RIPL boot drive id
OS2.2x identifies the OS/2 being booted
- Update the file \IBMLAN\RPL\MACHINES\MODEL16T\CONFIG.20.
Locate the following entries:
REM SELECT EITHER THE FAMLIY 1 OR PS/2 BASE DEVICE DRIVERS,...
REM BASE DEVICE DRIVER STATEMENTS FOR IBM FAMILY 1 AND ...
REM BASEDEV=PRINT01.SYS
REM BASEDEV=IBM1FLPY.ADD
REM BASEDEV=IBM1S506.ADD
REM BASE DEVICE DRIVER STATEMENTS FOR IBM PS/2 COMPUTERS ONLY:
BASEDEV=PRINT02.SYS
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2ADSK.ADD
BASEDEV=IBM2SCSI.ADD /LED
and change them to:
REM SELECT EITHER THE FAMLIY 1 OR PS/2 BASE DEVICE DRIVERS,...
REM BASE DEVICE DRIVER STATEMENTS FOR IBM FAMILY 1 AND ...
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM1S506.ADD
REM BASE DEVICE DRIVER STATEMENTS FOR IBM PS/2 COMPUTERS ONLY:
REM BASEDEV=PRINT02.SYS
REM BASEDEV=IBM2FLPY.ADD
REM BASEDEV=IBM2ADSK.ADD
REM BASEDEV=IBM2SCSI.ADD /LED
c. If you do have the new RIPL Support updates for OS/2 2.1,
then use the RPLSETD.CMD procedure to update the client
definition for MODEL16T. For example,
RPLSETD /C:MODEL16T /B:ISA
Authored by LS
Date last updated: 03/31/94
XA25027
12/31/99