Remote booting OS/2 workstations from Microsoft LAN Manager

To configure a server running LAN Manager version 2.2 or 2.1 to perform Remote Program Load for OS/2 workstations, do the following:

1 Set up and install the RPL service on the server according to the instructions in the Microsoft LAN Manager Administrator’s Guide.

2 From the release disk, copy the file MDGND.DOS to the directory:

C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE

Create the directory: C:\LANMAN\RPL\RPLFILES\BINFILES\LANMAN\DRIVERS\TOKENRNG\MADGE

Copy the MDGND.OS2 device driver to this directory.

3 Create the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE

4 Copy all the files in the directory:

C:\LANMAN\RPL\BBLOCK\NETBEUI\IBMTOK

to the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE

The files you need to copy are:

OS2121BB.CNF
OS213BB.CNF
PROTOCOL.INI

5 In the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE edit the files OS2121BB.CNF and/or OS213BB.CNF as follows:

a) Replace the line:
DAT BBLOCK\NETBEUI\IBMTOK\PROTOCOL.INI
with the line: DAT BBLOCK\NETBEUI\MADGE\PROTOCOL.INI
b) Replace the lines:
DRV BBLOCK\NDIS\IBMTOK.DOS ~ 2 M
DRV BBLOCK\PROTMAN.DOS /I: ~ M
with the lines: DRV BBLOCK\NETBEUI\MADGE\MDGND.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:~ ~

Your OS2121BB.CNF or (or OS213BB.CNF) file should look similar to the example shown below:

; OS/2 version 1.3 on IBM Token Ring RPL BBLOCK\RPLBOOT.SYS DAT BBLOCK\RPLMFSD.SYS ORG 1000H DAT BBLOCK\OS213\OS2KRNL LDR BBLOCK\OS213\OS2LDR ~ OS2LDR OS2KRNL RPLMFSD.SYS ;DAT BBLOCK\NETBEUI\IBMTOK\PROTOCOL.INI DAT BBLOCK\NETBEUI\MADGE\PROTOCOL.INI EXE BBLOCK\RPLBIND2.EXE ~ ~ EXE BBLOCK\PROTMAN.EXE ~ ~ EXE BBLOCK\RPLBIND1.EXE ~ ~ EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~ ;DRV BBLOCK\NDIS\IBMTOK.DOS ~ 2 M ;DRV BBLOCK\PROTMAN.DOS /I:~ M DRV BBLOCK\NETBEUI\MADGE\MDGND.DOS ~ ~ ~ DRV BBLOCK\PROTMAN.DOS /I: ~ ~

Sample OS2121BB.CNF (or OS213BB.CNF) file

6 Modify the PROTOCOL.INI file to ensure that:

a) The "bindings=" entry in each section is: bindings=MDGND
b) The final section is:
[MDGND]
drivername = MDGND$
PIO=YES

You do not need the PIO parameter for workstations with Smart 16/4 EISA Ringnodes installed

7 Edit the file C:\LANMAN\RPL\RPL.MAP by adding boot block records for the Smart 16/4 Ringnode:

For users who boot using OS/2 version 1.3 workstations, add the following lines to the OS/2 version 1.3 boot block configuration file OS213BB.CNF (the line has wrapped, it includes no carriage returns):
yyyyyyyyyyyy BBLOCK\NETBEUI\MADGE\OS213BB.CNF ~ ~ N ~ OS/2~1.3~ Madge~Ringnodes 0000F6 ~ ,,, ~ ROS2M13 ~ ~ ~ ~ ~ ~
For users who boot using OS/2 version 1.21 workstations, add the following lines to the OS/2 version 1.21 boot block configuration file OS2121BB.CNF (the line has wrapped, it includes no carriage returns):
yyyyyyyyyyyy BBLOCK\NETBEUI\MADGE\OS2121BB.CNF ~ ~ N ~OS/2~1.21~ Madge~Ringnodes 0000F6 ~ ,,, ~ ROS2M121 ~ ~ ~ ~ ~ ~

8 Define new booting profiles for your Smart 16/4 Ringnodes. To do this, edit the RPLMGR.INI file (in the directory C:\LANMAN\RPL) as follows:

a) By copying existing sections, create four new [configuration] sections for the Smart 16/4 Ringnode, so that it will work with workstations that have the following configurations: OS/2 version 1.21 with EGA; OS/2 version 1.21with VGA; OS/2 version 1.3 with EGA; and OS/2 version 1.3 with VGA. If your network users are all using the same version of OS/2, only create two new [configuration] sections. The new [configuration] sections have the same structure as the existing ones, except that:

The "name=" entries must each be unique. The "name=" entry specifies the name of the profile RPLMGR.EXE creates and assigns to workstations.

The "bblink=" entries must correspond to the fields in the new RPL.MAP records ROS2M121 and ROS2M13. The "comment=" entry can be completed as you like, for example: comment= OS/2 1.3 Madge Ringnode EGA

The "adapter=" entry must be 0000F6??????

This is the identification number for Madge Ringnodes.

The example below, for a Smart 16/4 Ringnode using OS/2 version 1.3 with EGA, shows what a new [configuration] section should look like.
[configuration]	 
	name = O13MTE     ; The profile name
	os = OS213		  ; Directory containing OS2
	dirname = OS2		
	dirname2 = OS2MT 	  ; Directory containing PROTOCOL.INI
	dirname3 = OS2MTE ; Directory containing CONFIG.SYS
	dirname4 = OS213 
	bblink = ROS2M13			  ; Link to  boot block
	fitfileshared = fits\os213e	  ; Fit file
	fitfilepersonal = fits\os213ep 
	comment = OS/2 1.3 Madge Ringnode EGA 		
	adapter = 0000F6?????? 
	memorysize = 3072 
	videotype = EGA 
	cputype = 286|386|486
Sample [configuration] section of the RPLMGR.INI file
b) Add the following comment to the end of the file, to define the Smart 16/4 Ringnode ;0000F6 = Madge

9 Go to the directory C:\LANMAN\RPL\RPLFILES\CONFIGS

Create the following directories \OS2MT, \OS2MTE, \OS2MTV.

Copy all the files (and any subdirectories) in the directory:

OS2IT to the directory: OS2MT

OS2ITE to the directory: OS2MTE

OS2ITV to the directory: OS2MTV

10 Go to the directory OS2MT\LANMAN and edit the PROTOCOL.INI by replacing all occurrences of IBMTOK with MDGND.

11 In the subdirectories \OS2MTE and \OS2MTV edit the CONFIG.SYS files by replacing the line:

DEVICE=C:\LANMAN\DRIVERS\TOKENRNG\IBMTOK\IBMTOK.OS2

with the line: DEVICE=C:\LANMAN\DRIVERS\TOKENRNG\MADGE\MDGND.OS2

12 Type rplinst. This customizes the RPL.MAP and RPLMGR.INI files for the particular operating system installed on your server.

13 Run RPLMGR and, if the profiles that you defined in the [configuration] sections in step 8 do not exist, create them. Assign these profiles to the workstations that require them.

You have now finished configuring your LAN Manager server to perform remote booting for OS/2 workstations.