Remote booting DOS workstations from Microsoft LAN Manager

This section tells you how to provide remote booting workstations from LAN Manager version 2.2 and 2.1 with:

A Madge Fastmac or Smart NDIS interface.
A Smart NetBIOS interface and, if required, a Smart LLC interface.

To make significant DOS memory savings (especially if you need an LLC interface, for example, for 3270 emulation), use the Smart II Software. If DOS memory is not an issue, the Fastmac driver gives maximum performance.

Remote booting DOS workstations with NDIS

Remote booting DOS workstations with NetBIOS

Remote booting DOS workstations with NDIS

To configure LAN Manager version 2.2 or 2.1 to perform Remote Program Load for DOS workstations, follow the instructions below.

For maximum DOS memory savings, use Smart NetBIOS. However, if you require an NDIS interface, you can save some memory by using Smart NDIS instead of the Fastmac MDGND.DOS driver:

i. Place the file SMTNDIS.BAT in a directory with: SMART.EXE, SMTLINK.EXE, SMART.CFG, NDIS.SMT (and any other Smart modules you require, for example, LLC.SMT).
ii. In the SMART.CFG, include an [NDIS] section, and in the [HOST] section, include the MRPL21 and the FORCELOAD parameters. Include a section for each Smart modules you wish to use.
iii. Type SMTNDIS . . [Enter] at the DOS prompt. This creates a file called SMTNDIS.DOS. (For more information, refer to the SMTLINK.INF file.) In the instructions that follow in this section, substitute SMTNDIS.DOS for MDGND.DOS and smart_ndis$ for MDGND$.

Set up and install the RPL service on the server according to the instructions in the Microsoft LAN Manager Administrator’s Guide.
From the release disk, copy the file MDGND.DOS to the directory
C:\LANMAN\RPL\BBLOCK\NDIS
Create the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE.
From the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\IBMTOK copy the files DOSBB.CNF and PROTOCOL.INI to the directory
C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE
Go to the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE and modify the file DOSBB.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:C:\LANMAN.DOS ~ M
with the lines:
DRV BBLOCK\NDIS\MDGND.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ ~
The DOSBB.CNF should look similar to the example shown below.
```
; DOS on IBM Token Ring
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
;DAT BBLOCK\NETBEUI\IBMTOK\PROTOCOL.INI
DAT BBLOCK\NETBEUI\MADGE\PROTOCOL.INI
DRV BBLOCK\RPLDISK.SYS ~ 4 M
EXE BBLOCK\RPLPRO1.COM ~ 2 ~
EXE BBLOCK\RPLBIND2.EXE ~ ~
EXE BBLOCK\PROTMAN.EXE ~ ~
EXE BBLOCK\RPLBIND1.EXE ~ ~
;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~
;DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
;DRV BBLOCK\NDIS\IBMTOK.DOS ~ 2 M
;DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
DRV BBLOCK\NDIS\MDGND.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ ~
```
Sample DOSBB.CNF file
Modify PROTOCOL.INI to ensure that the "bindings=" entry in each section is: bindings=MDGND and the final section is:
[MDGND]
drivername = MDGND$
Edit the file C:\LANMAN\RPL\RPL.MAP as follows:

a) Add the following line which references the DOS boot block configuration file DOSBB.CNF (the line has wrapped):
yyyyyyyyyyyy BBLOCK\NETBEUI\MADGE\DOSBB.CNF 2 6 N ~
DOS ~ Madge ~ Ringnodes 0000F6 ~ ,,, ~ RDOS ~ ~ ~ ~ ~ ~

b) Create a new default DOS workstation record (the line has wrapped, it includes no carriage returns):
0000F6?????? ???????? D FITS\DEFAULT
(RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOS ~ DEFAULT
*~New~Madge~Ringnode ~ * ~ ~ ~
In the directory C:\LANMAN\RPL edit the file RPLMGR.INI as follows:

a) Locate the [configuration] section where the "name=" entry is:
name=DEFAULT

In the "adapter=" entry, insert the following, if it is not already present: 0000F6??????
This entry may already be correct. Ensure that it reads as follows:
adapter=
0000F6??????|10005A??????|0000C0??????|02608C??????|
00608C??????| 42608C??????|00001B??????|00004B??????
Repeat this "adapter=" entry for the following [configuration] sections:
name=DOS330
name=DOS401
name=DOS500

b) Place the following comment at the end of the file. It identifies the Smart 16/4 Ringnode: ;0000F6 = Madge
Type rplinst

This customizes the RPL.MAP and RPLMGR.INI files for the particular operating system installed on your server. Then create user names for the workstations, granting them the appropriate rights, and assigning profiles to them. For details, refer to the LAN Manager Administrator’s Guide.

You have now finished configuring your LAN Manager server to enable it to perform remote booting for DOS workstations.

Remote booting DOS workstations with NetBIOS

To configure a server running LAN Manager version 2.2 or 2.1 to perform Remote Program Load for DOS 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 Create the directory: C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE

3 In a DOS box on your server, or on a DOS workstation, create a Smart NetBIOS driver by performing the following:

i. Place the file SMTNETB.BAT in a directory with SMART.EXE, SMTLINK.EXE, SMART.CFG, and NETB.SMT.
ii. In SMART.CFG, include a [NETB] section, and, in the [HOST] section, include the MRPL21 parameter (for both LAN Manager version 2.2 and 2.1) and the FORCELOAD parameter.
iii. Type SMTNETB [Enter]at the DOS prompt. For more information about SMTNETB.BAT, refer to the SMTLINK.INF file.

[HOST]
FORCELOAD; Ensure Smart loads onto the Ringnode
MRPL21 ; Remote booting from LAN Manager 2.2 or 2.1
	[CARD]
[NETB]	; Enable a NetBIOS interface

Sample SMART.CFG file for remote booting from LAN Manager

4 Copy the file you have created to the following directory:

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

5 From the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\IBMTOK copy the file DOSBB.CNF to: C:\LANMAN\RPL\BBLOCK\NETBEUI\MADGE

6 Edit DOSBB.CNF to look like the example shown below:

; DOS Boot Block Configuration	BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\IBMTOK\PROTOCOL.INI
DRV BBLOCK\RPLDISK.SYS ~ 4 M
EXE BBLOCK\RPLPRO1.COM ~ 2 ~
;EXE BBLOCK\RPLBIND2.EXE ~
;EXE BBLOCK\PROTMAN.EXE ~ ~
;EXE BBLOCK\RPLBIND1.EXE ~ ~
;EXE BBLOCK\TCPDRV.DOS /I:C: \LANMAN.DOS ~ ~
;EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
;DRV BBLOCK\NDIS\IBMTOK.DOS ~ 2 M
;DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
DRV BBLOCK\NETBEUI\MADGE\SMTNETB.EXE ~ ~

Sample DOSBB.CNF file

7 Edit the file C:\LANMAN\RPL\RPL.MAP as follows:

a) Add the following line which references the DOS boot block configuration file DOSBB.CNF (the line has wrapped, it includes no carriage returns): yyyyyyyyyyyy BBLOCK\NETBEUI\MADGE\DOSBB.CNF 2 6 N ~ DOS~Madge~Ringnodes 0000F6 ~ ,,,~ RDOS ~ ~ ~ ~ ~ ~
b) Create a new default DOS workstation record as follows (the line has wrapped, it includes no carriage returns):
0000F6?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~,,,~ RDOS ~ DEFAULT
*~New~Madge~Ringnode ~ * ~ ~ ~

8 In the directory C:\LANMAN\RPL edit the RPLMGR.INI file as follows:

a) Locate the [configuration] section where the "name=" entry is:
name=DEFAULT
In the "adapter=" entry, insert the following, if it is not already present: 0000F6??????
This entry may already be correct. Ensure that it reads as follows:
adapter=
0000F6??????|10005A??????|0000C0??????|02608C??????|
00608C??????| 42608C??????|00001B??????|00004B??????
Repeat this "adapter=" entry for the following [configuration] sections:
name=DOS330
name=DOS401
name=DOS500

b) Place the following comment at the end of the file, to identify the Smart 16/4 Ringnode: ;0000F6 = Madge

9 Type rplinst

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

You may now create user names for your remote booting workstations, granting them the appropriate rights, and assigning profiles to them. For details, refer to the LAN Manager Administrator’s Guide.

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

Remote booting OS/2 workstations from 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.