# Remote Booting OS/2 workstations

This section explains the procedure required to boot OS/2 from a WARP Server.

1. Stop the RPL server if it is currently running. Either use the SERVICES utility or type NET STOP RPL.

2. Copy MDGND.OS2 from the release disks to C:\IBMLAN\RPL\IBMCOM\MACS\.

3. Go to the directory C:\IBMLAN\RPL\ and copy the file OS230TR.CNF to OS230MR.CNF.

4. Add a server record to the RPL.MAP file to allow access to this new file by inserting the line in the server entry section.:
yyyyyyyyyyyy OS230MR.CNF 3 10 N ~ OS2~230~TOKEN~RING ~ ~ ,,, ~ R_230_MDG_TOK ~ ~

5. Use the Remote Program Load Requester to create a new requester file. Give it the correct MAC address for the machine you wish to boot, select Enable OS/2 requester and enter a description. On the next page select the R_230_MDG_TOK as the boot image and select drive C.
Select create.

If this fails, make sure that the file OS230MR.CNF exists and that it is spelt correctly in the RPL.MAP file.

6. Copy MND.MSG from the release disk into directory C:\IBMLAN\DOSLAN\LSP\
Edit the OS230MR.CNF file, note that all entries must be in upper case.

7 Copy MDGND.DOS and MDGND30.BIN from the Madge release disk to the following directory on your server:
C:\IBMLAN\RPL\DOS\TOKENRNG\MADGE

8 Edit your OS220MR.CNF file to look like the example in the following figure:

>     ;	OS/2 Boot Block Configuration (Madge Smart Ringnode)
>     ;
>     RPL DOS\RPLBOOT.SYS
>     DAT DOS\MFSD20.SYS
>     ORG 1000H

>     LDR OS2.30a\OS2LDR ~ OS2LDR UFSD.SYS MFSD20.SYS
>     DAT DOS\UFSD.SYS

>     DAT DOS\TOKENRNG\MADGE\MDGND30.BIN

>     DAT C:\IBMLAN\DOSLAN\LSP\DXM.MSG
>     DAT C:\IBMLAN\DOSLAN\LSP\MND.MSG
>     DAT DOS\MADGE\PROTOCOL.INI

>     EXE C:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~
>     DRV DOS\TOKENRNG\MADGE\MDGND.DOS ~ ~
>     DRV C:\IBMLAN\DOSLAN\LSP\DXMJ0MOD.SYS ~ 14 ~
>     DRV C:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS ~ ~ ~
>     DRV C:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~

Sample OS230MR.CNF file

9 Copy the following file:
C:\IBMLAN\RPL\DOS\PROTOCOL.INI
to the new directory:
C:\IBMLAN\RPL\DOS\MADGE

10 Edit the PROTOCOL.INI file to look like the example below.

>     	[PROTMAN_MOD]
>     		DriverName = PROTMAN$
>     	[DXMJ0_MOD]
>     		DriverName = NETBEUI$
>     		BINDINGS = MDGND_MOD
>     	[MDGND_MOD]
>     		DriverName = MDGND$
>     		PIO=YES

Sample PROTOCOL.INI file

11 The process of creating a requester response file (step5) should have created some configuration files in the path:

C:\IBMLAN\RPL\MACHINES\<MACHINE NAME>

In the CONFIG.SYS and CONFIGRI.SYS files change the line:

DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 to DEVICE=C:\IBMCOM\MACS\MDGND.OS2

If the computer you are remote booting is significantly different from the server it may be necessary to make further changes to this file. Particularly with respect to video drivers and SCSI drivers.

| The default LanServer RPL computer is a PS/2, even if the server is AT-based. Hence, for AT-based clients, the following lines need to be modified: BASEDEV=IBM2FLPY.ADD modified to BASEDEV=IBM1FLPY.ADD BASEDEV=PRINT02.SYS modified to BASEDEV=PRINT01.SYS BASEDEV=IBM2ADSK.ADD modified to BASEDEV=IBMIS506.ADD

12 In the file PROTOCOL.INI locate the line:
DriverName=IBMTOK$
and replace with:
DriverName=MDGND$
and delete all the lines in the related section. That is, lines up to the next [SECTION]

13 Run GETRPL from the command line.

14. Shut down and restart the computer.

15. It is now possible to start the services with either:

NET START RPL from the command line

or by using the SERVICES utility.