OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / network / ripl / readme < prev next >

Wrap

Text File | 1993-05-28 | 33.6 KB | 849 lines

REMOTE IPL SUPPORT FOR OS/2 2.1 INTRODUCTION ------------ OS/2 2.1 implements several system changes that require significant changes to the LAN Server Remoteboot service. This document describes how to install the LAN Server upgrades, how to update the Remote IPL (RIPL) client definitions for different display types, and how to support multiple versions of the OS/2 operating system in the RIPL directory structure. Know problems are also described. LAN Server 2.0 or LAN Server 3.0 with the OS/2 Remote IPL service must already be installed before applying these updates. Updates are provided for both LAN Server 2.0 and 3.0. The following files are provided on the Remote IPL Service diskette: - RPLMIG21.CMD Installation/migration procedure - IBMLS.ZIP Updates common to LAN Server 2.0 and 3.0 - IBMLS20.ZIP Updates specific to LAN Server 2.0 - IBMLS30.ZIP Updates specific to LAN Server 3.0 This version of the Remote IPL support for OS/2 2.1 is only valid for the May Beta and GA versions of OS/2 2.1. VALID OS/2 / REMOTE IPL CONFIGURATIONS -------------------------------------- The following table identifies valid OS/2 / Remote IPL configurations: ┌──────────┬───────────────────────────────────────────────────┐ │ Server │ Operating System to be RIPLed │ │ Operating│ 2.0+ │ │ System │ 1.3.2 2.0 Service Pak 2.00.1 2.1 │ ├──────────┼──────────┼───────┼─────────────┼─────────┼────────┤ │ 1.3.2 │ Yes │ Yes │ Yes │ Yes │ Yes │ │ │ │ │ │ │ │ │ 2.x │ No │ Yes │ Yes │ Yes │ Yes │ └──────────┴──────────┴───────┴─────────────┴─────────┴────────┘ LAN SERVER REMOTE IPL SERVICE UPGRADES -------------------------------------- The following changes/additions have been made to Remote IPL: - A new rexx procedure, RPLMIG21.CMD, has been provided to install the new Remote IPL support for OS/2 2.1. - The Full Screen interface was updated to default the 'File Index Table to model' parameter to DEFALT21.FIT when a OS/2 2.1 server record is selected. Changes were also made to remove the 'Read' attribute on OS/2 2.1 client INI files before attempting to delete them. The client file AUTOEXEC.20 is updated to reflect the boot drive id. - The RPLSETD.CMD rexx procedure (shipped with LAN Server 3.0) has been updated to support the following OS/2 RIPL client upgrades: Current Client New Client Operating System Operating System ---------------- ---------------- 1.3.2 No updates supported 2.0 2.0+SP, 2.00.1, or 2.1 2.0+SP 2.1 2.00.1 2.1 The following option changes/additions have been made to RPLSETD.CMD: /D: No longer a required parameter. /O: If not specified, the operating system directory is determined for the client being updated. /B: New. Specifies the bus type of a client (MCA or ISA/EISA). /S: New. Specifies whether the SWAPPATH is on a local drive or the RIPL server. RPLSETD.CMD has been moved from the \IBMLAN\RPL directory to the \IBMLAN\NETPROG directory so that is can be located via the PATH statement and executed from any directory. The LANINST program requires that a copy of RPLSETD.CMD be located in \IBMLAN\RPL. For this reason, a dummy version of RPLSETD.CMD is installed in the \IBMLAN\RPL directory. This dummy version will invoke the version in \IBMLAN\NETPROG. - Several new routines have been added to support the new RPLSETD.CMD procedure: RPLRXUTL.EXE RPLUCC20.CMD RPLUCFIT.CMD RPLSDMSG.CMD - Default 2.1 WINOS2 INI files are provided that are preconfigured for VGA display support. XGA and 8514 support statements are also present but commented out. When the /D option is specified on RPLSETD.CMD, the client copy of the SYSTEM.INI file will be updated to reflect the display type specified. The /S option will also cause the client copy of the SYSTEM.INI file to be updated. KNOWN PROBLEMS -------------- None. UPGRADING EXISTING REMOTE IPL SERVERS ------------------------------------- To upgrade existing RIPL servers, use the following procedure: 1. Determine if the prior versions of OS/2 in the RIPL tree are still required. If they are not required, delete the appropriate OS2.20 or OS2.20a directory tree to recovery the hardfile space. 2. Use the OS/2 2.1 utility RIPLINST to install the OS/2 2.1 code. Refer to the section 'OS/2 2.1 RIPLINST UTILITY' for additional information. 3. Install Remote IPL upgrades. Refer to the section 'INSTALLATION OF LAN SERVER REMOTE IPL UPGRADES' for information on installing the upgrades. 4. Run the LAN Server utility GETRPL.EXE. 5. If the server will only be RIPLing OS/2 2.1 clients, use the RPLSETD.CMD procedure to update the client DEFALT20 to support OS/2 2.1. Refer to the section 'RPLSETD.CMD REXX PROCEDURE' for information on RPLSETD.CMD. Do not update the client DEFALT20 if prior versions of OS/2 will be RIPLed from the RIPL server. If the server will be supporting prior versions of OS/2 in addition to 2.1, refer to the section 'SUPPORTING MULTIPLE LEVELS OF THE OS/2 OPERATING SYSTEM' for details on how to support multiple version of OS/2. 6. Use the RPLSETD.CMD procedure to update existing RIPL clients that are to RIPL the OS/2 2.1 operating system. When updating existing RIPL clients, you must specify both the /C and /D parameters. When RIPL clients are updated to OS/2 2.1, all of the existing client WINOS2 *.INI and *.GRP files must be replaced with 2.1 versions of those files. The existing *.INI files are renamed *.IBK and the existing *.GRP files are renamed *.GBK. When the user is satisfied that these old files are no longer needed for reference, they should be deleted. 7. If you have any customized workplace shell OS2 INI files, refer to the section 'UPDATING MASTER WORKPLACE SHELL OS2.INI FILES' for additional information. INSTALLING NEW REMOTE IPL SERVERS --------------------------------- To install new RIPL servers, use the following procedure: 1. Install the LAN Server as described in the LAN Server documentation. 2. Follow the procedure described above for upgrading Remote IPL servers. 3. If you plan to support multiple versions of OS/2 in the RIPL tree, refer to the section 'SUPPORTING MULTIPLE LEVELS OF THE OS/2 OPERATING SYSTEM ' for additional information. INSTALLATION OF LAN SERVER REMOTE IPL UPGRADES ---------------------------------------------- The LAN Server Remote IPL upgrades are provided on a LAN Server Remote IPL Service diskette. A rexx procedure, RPLMIG21.CMD, is provided that will install the LAN Server upgrades. The upgrades can be installed from the diskette or the upgrades can be copied to a hardfile and installed from the hardfile. The RPLMIG21.CMD procedure performs the following functions: 1. Creates new RIPL subdirectories to support OS/2 2.1 and OS/2 2.00.1. The OS/2 2.00.1 subdirectories are created even if you do not have 2.00.1 installed so that 2.00.1 could be installed and supported at a later date if required. 2. Copies several master files from the RIPL OS/2 2.0 directories into the new RIPL OS/2 2.1 directories. 3. Installs the LAN Server upgrade files to the appropriate directories. RPLMIG21 will determine which version of LAN Server is installed and copy the appropriate update files. 4. Upgrades the RPL.MAP file to add server records to support OS/2 2.1. 5. Creates OS221*.CNF files to support the server records created in step 4. 6. Update the server name references in the DEFALT21.FIT file installed as part of step 3. 7. Update the master CONFIGRI.20 files to add the DEVICE=Z:\OS2\TESTCFG.SYS statement required for OS/2 2.1 remote install. Note: RPLMIG21.CMD creates a file called \IBMLAN\RPL\RPLMIG21.$$$ which is 'Read-only'. If RPLMIG21.CMD detects that this file is already present, the user will be prompted to verify whether to rerun RPLMIG21.CMD or not. The procedure RPLSETD.CMD will not execute if the RPLMIG21.$$$ file is not present and the client operating system is OS/2 2.1. To install from the diskette, do the following: 1. Insert the diskette in drive A. 2. At an OS/2 prompt, enter the following command A:\RPLMIG21 To install from a hardfile, do the following: 1. Create a subdirectory, for example d:\RPLOS221. 2. Copy the files on the RIPL Service diskette to the subdirectory created in step 1. 3. At a OS/2 prompt, enter the command: d:\RPLOS221\RPLMIG21 /S:d:\RPLOS221 The /S parameter specifies the path to the directory created in step 1. The complete syntax for the RPLMIG21.CMD procedure is given below: RPLMIG21.CMD [ ? | /h | /H] [/S:Sourcepath] [/L:Logfile] where ? or /h or /H is a request for this help panel. If specified, it must be first parameter. /S:Sourcepath is the fully qualified path to the directory which contains the files to be installed by RPLMIG21. The default value is A:\. /L:Logfile is the fully qualified name of a file to which all messages and errors are to be logged. If Logfile is specified, no messages or errors will be displayed on the screen. OS/2 2.1 RIPLINST UTILITY ------------------------- The RIPLINST utility used to install the OS/2 2.1 code for LAN Server OS/2 Remote IPL is located (in packed format) on diskette 7 of the OS/2 2.1 Installation diskettes. Use one of the following procedures to install and execute RIPLINST: a. Operating system of LAN Server is OS/2 2.1. 1. Insert OS/2 2.1 Install diskette 7 into drive A. 2. Install RIPLINST by entering the following command: UNPACK A:\RIPLINST The RIPLINST files will be unpacked to the \OS2\INSTALL directory. 3. To start the RIPLINST program go to an OS/2 window or full screen session an enter the command: RIPLINST 4. Press Enter to clear the title panel. 5. The Change Source/Target panel is displayed. The Source path should be left as A:\. If necessary, the target directory can be updated to change the drive id of the target. Only the drive id should be changed, do not change the default directory paths. The OS/2 2.1 code must be installed on the same drive that the OS/2 Remote IPL support was installed on during LAN Server Installation. 6. Select the 'Install' button. 7. Insert diskettes as prompted. b. Operating system of LAN Server is OS/2 1.3.2, 2.0, 2.0+Service Pak, or 2.00.1. 1. Create a temporary subdirectory by entering the command: MD TEMPRIPL 2. Change to the temporary subdirectory by entering the command: CD TEMPRIPL 3. Insert OS/2 diskette 2 into drive A. 4. Copy UNPACK.EXE to TEMPRIPL by entering the command: COPY A:UNPACK.EXE 5. Check the OS/2 2.1 install diskette 2. If the file UNPACK2.EXE is present, copy UNPACK2.EXE to TEMPRIPL by entering the command: COPY A:UNPACK2.EXE Note: UNPACK2.EXE may or may not be present. If is is not on your diskette 2, then you do not need it. 6. Insert OS/2 diskette 7 into drive A. 7. Install the RIPLINST files by entering the command: UNPACK A:\RIPLINST d:\TEMPRIPL where d: is the drive id where TEMPRIPL is located. 8. Start the RIPLINST program by entering the command: RIPLINST Note: The OS/2 2.1 version of RIPLINST must use the OS/2 2.1 version of UNPACK and UNPACK2. Failure to do so will result in one of the following error conditions: - RIPLINST will hang while copying the W0F0000.BIO file. - The system will lock up after displaying the copy panel. Reboot is the only recover. 9. Press Enter to clear the title panel. 10. The Change Source/Target panel is displayed. The Source path should be left as A:\. If necessary, the target directory can be updated to change the drive id of the target. Only the drive id should be changed, do not change the default directory paths. The OS/2 2.1 code must be installed on the same drive that the OS/2 Remote IPL support was installed on during LAN Server Installation. 11. Select the 'Install' button. 12. Insert diskettes as prompted. Previous versions of RIPLINST had a default target install directory of: d:\IBMLAN\RPL\OS2.20 (OS/2 2.0 and Service Pak) or d:\IBMLAN\RPL\OS2.20a (OS/2 2.00.1) where d: indicates the drive where OS/2 is installed.) The RIPLINST for OS/2 2.1 has a new default target install directory. The new default target install directory is: d:\IBMLAN\RPL\OS2.21 This was done so that an existing ..\OS2.20 directory tree would not be automatically overwritten. If you wish to upgrade an existing ..\OS2.20 directory tree, the target install directory must be updated before starting the install process. The target directory must be on the same drive where OS/2 Remote IPL was installed (this can be different from where LAN Server is installed). After using RIPLINST to install OS/2 2.1 for Remote IPL, the updated version of the LAN Server utility, GETRPL.EXE, must be run. Refer to the LAN Server documentation for information on running GETRPL. RPLSETD.CMD REXX PROCEDURE -------------------------- The RPLSETD.CMD procedure provides the following functions: - Upgrade existing RIPL clients that use 16 bit display drivers to use the new 32 bit VGA, XGA, and 16 bit 8514 display drivers provided in OS/2 2.00.1, 2.0 + Service Pak. It also supports the 32 bit 8514 display driver in 2.1. - Can be used in some cases to change the display type (32 bit VGA,XGA, or 8514) that a RIPL client is using. RPLSETD does not support converting from the new 32 bit drivers back to the old 16 bit display drivers. If a Desktop exists for the RIPL client, changing to a higher resolution display type can cause unpredictible results. If a Desktop exists, it is highly recommended that the client definition be deleted, recreated, use RPLSETD to change to the higher resolution display type, and then boot the client and let it create a new Desktop. - Can be used to update a RIPL client to boot a different version of OS/2 2.x. The OS/2 2.x code must be installed in the RIPL directory structure. The following OS/2 2.x versions conversions are supported: old version new version 2.0 2.00.1 2.0+Service Pak 2.1 2.00.1 2.0+Service Pak 2.1 2.0+Service Pak 2.1 Note that there is no support for converting any of the newer versions back to the original OS/2 2.0. After a client is converted to OS/2 2.1, RPLSETD cannot be used to convert back to 2.0+Service Pak or 2.00.1. - Can be used to update a RIPL client to change the bus type, i.e. MCA or ISA/EISA. - Can be used to update a RIPL client to specify whether the SWAPPATH and WIN-OS2 'PagingFile' will be on a local hardfile or on the RIPL server. Client definitions can be updated individually or in a group (grouped by common attributes such as display type, bus type, and operating system). The client name DEFALT20 is a special client name used by the OS/2 Remote IPL support as a default when creating a new client (not modelling an existing client). If you are supporting prior versions of OS/2 (i.e. 2.0, 2.00.1, or 2.0 + Service Pack) in the RIPL directory tree, do not update DEFALT20 to support OS/2 2.1. You must leave DEFALT20 at its current level to support the prior version(s) of OS/2. To support OS/2 2.1 RIPL clients do the following: - Create a 'new' RIPL client, for example, MODEL21, using the defaults. - Use RPLSETD to update MODEL21 to support OS/2 2.1. Then use MODEL21 as a model client to create all future 2.1 clients. - You may need to create multiple 2.1 models, one for each LAN type you support. The client name DEFALT21 is reserved. Do not create a client by this name. DEFALT21 is not a complete client definition like DEFALT20. It is used in conjunction with DEFALT20 to support OS/2 2.1 clients. Do not attempt to update the DEFALT21 client with RPLSETD.CMD. If the only version of OS/2 that will be installed in the RIPL directory tree is OS/2 2.1, you should update the client DEFALT20. Then all future default clients will automatically support OS/2 2.1. The syntax of RPLSETD.CMD is: RPLSETD [/H] [/C:CLIENT[,CLIENT2,CLIENT3,...]] [/D:DISPLAY_DRIVER] [/O:CURRENT_OS2] [/N:NEW_OS2] [/B:BUSTYPE] [/S:SWAPTARGET] [/L:LOGFILE] [/R:RESPONSE_FILE] where: /H displays the syntax on screen. If specified, it must be the first parameter. /C:CLIENT[,CLIENT2,CLIENT3,...] (CLIENT or CLIENTLIST) is the name of one or more OS/2 remote IPL client workstations that are to be updated. If multiple client names are specified, each client name must be separated with a comma. Imbedded blanks are not allowed. The response file keywords CLIENT and CLIENTLIST are equivalent to each other. They may be specified as many times times as necessary. This is a required parameter if the /R parameter is not specified. When specified, at least one other parameter must also be specified. /D:DISPLAY_DRIVER (DISPLAYDRIVER) is the new display type for the client definition. The following display types are valid: IBMVGA32 32-bit VGA display driver IBMXGA32 32-bit XGA display driver IBM8514 16-bit 8514 display driver (2.0+SP or 2.00.1) 32-bit 8514 display driver (2.1) 8514_32 Alternate 32-bit 8514 display driver name (2.1) This parameter is normally optional, however, it must be specified when an existing 2.0 or 2.00.1 RIPL client is converted to 2.1 by specifying the /N parameter. When upgrading the display type of an existing RIPL client (it has booted at least one time and has a Desktop) from VGA to XGA or 8514, you must delete and recreated the RIPL client and then run RPLSETD.CMD. If you update the existing client to a higher resolution display type, many of the display sizing characterics in OS2.INI do not get updated. As a result you end up with some objects in VGA resolution and some in the higher resolution. If no Desktop exists for the client, it can be updated to change to a higher resolution. When the Desktop is created during the first boot, it will reflect the display characteristics for which it is configured. /O:CURRENT_OS2 (CURRENTOS2DIR) is the root directory under \IBMLAN\RPL for the current version of OS/2 2.0 that the client is using. This parameter is case sensitive. The /O parameter should only be specified when you want the client operating system type verified before updating to a new operating system type. If /O is not specified, the current operation system being used by the RIPL client is determined from the client.FIT file. If the /O parameter is specified, then the /N parameter must also be specified. /N:NEW_OS2 (NEWOS2DIR) is the root directory under \IBMLAN\RPL for the version of OS/2 2.0 that the client is to be switched to. This parameter is case sensitive. The default is OS2.21. The /O and/or /N parameters should only be specified when you need to switch a client from one OS version to another OS version. When an existing RIPL client is updated to OS/2 2.1, the client WINOS2 *.INI and *.GRP files must be replace with the 2.1 versions of these files. The old files are renamed to *.IBK and *.GBK. When the user is satisfied that these old files are no longer needed for reference, they should be deleted. /B:BUSTYPE (BUSTYPE) is the type of I/O bus used by the RIPL client machine. Valid types are: MCA - Micro-channel ISA - AT compatable EISA - AT compatable /S:SWAPTARGET (SWAPTARGET) is an indicator of where the SWAPPER.DAT file will reside: Valid values are: L - file will reside on local hardfile of RIPL client S - file will reside on RIPL server This parameter also control the location (local/server) of the 'PagingFile' parameter in the OS/2 2.1 WIN-OS2 SYSTEM.INI file. /L:LOGFILE (LOGFILE) is the drive, path, and filename of a file to which all messages and errors are to be logged. If this parameter is specified, the only errors displayed on the screen will be for a failure to open the logfile or for missing required parameters in the response file. /R:RESPONSE_FILE is the drive, path, and filename of a file that contains the command inputs in keyword form (keyword=value). The valid keywords are indicated above in () following each /X: syntax. Only one keyword can be specified per line in the response file. The CLIENT or CLIENTLIST parameter and at least one other parameter are required when using a response file. If the /R parameter is specified, all other parameters specified on the command line are ignored. Examples: - To update the DEFALT20 client to use the 32 bit VGA display driver and switch the operating system from OS2.20 to OS2.21, type: RPLSETD /C:DEFALT20 /D:IBMVGA32 /N:OS2.21 This will update the default files to support OS/2 2.1 and the new VGA display driver. These files are used when defining clients using the default configuration. Note: If you plan to also support previous versions of OS/2 (i.e. 2.0, 2.00.1, or 2.0 + Service Pak), do not update the DEFALT20 client. - To update the MACH001 client to use the 32 bit XGA display driver and switch the operating system to OS2.21, type: RPLSETD /C:MACH001 /D:IBMXGA32 /N:OS2.21 - To update the MACH001 client to use the 32 bit XGA display driver, verify the current operating system is OS2.20a, and switch the operating system to OS2.21, type: RPLSETD /C:MACH001 /D:IBMXGA32 /O:OS2.20a /N:OS2.21 - To update the MACH001 client to specify a bus type of ISA and set the SWAPPATH/PagingFile to the RIPL server, type: RPLSETD /C:MACH001 /B:ISA /S:S - To update the MACH001 client to use the 32 bit VGA display driver, verify the current operating system is OS2.20, switch the operating system to OS2.21, specify a bus type of ISA, and set the SWAPPATH/ PagingFile to the RIPL server, type: RPLSETD /C:MACH001 /D:IBMVGA32 /O:OS2.20 /N:OS2.21 /B:ISA /S:S - To update multiple clients, MACH001 and MACH002, to use the 32 bit VGA display driver and switch the operating system to OS2.21, type: RPLSETD /C:MACH001,MACH002 /D:IBMVGA32 /N:OS2.21 RPLSETD RESPONSE FILE KEYWORDS ------------------------------ The valid response file entries/keywords are: ; Comment line [GROUP] (this statement is optional for the first group and required for all subsequent groups) DISPLAYDRIVER= CLIENT= CLIENTLIST= CURRENTOS2DIR= NEWOS2DIR= BUSTYPE= SWAPTARGET= A ';' in column 1 indicates the line is a comment. Leading blanks are allowed on keyword statements. The keywords are defined above in the RPLSETD syntax description. [GROUP] designates the start of a RIPL client or group of clients that share the same configuration characteristics. When the [GROUP] statement is encountered, the client machine(s) in the previous group are updated according to the specified keyword(s). Multiple [GROUP]s can appear in the response file. This allows a single response file to process a number of different configurations. The [GROUP] statement is optional for the first group in the response file but is required for all subsequent groups. CLIENT and CLIENTLIST are equivalent and multiple entries can be specified on either. Multiple CLIENT and CLIENTLIST keywords can be specified per group. Only one of each of the other keywords is allowed per group. Example: To use the response file option, do the following: 1. Create an ASCII file that contains the appropriate keyword values. For example: [GROUP] (optional) ; Update existing clients to support the IBMXGA32 display driver, ; switch from OS2.20 to OS2.21, support the MCA bus, and put the ; swappath on a local hardfile. CLIENT=DEFALT20 CLIENT=MACH001,MACH002 CLIENTLIST=MACH003,MACH004 DISPLAYDRIVER=IBMXGA32 CURRENTOS2DIR=OS2.20 NEWOS2DIR=OS2.21 BUSTYPE=MCA SWAPTARGET=L [GROUP] (required) ; Update client for ISA bus and put the swappath on the RIPL ; server (no local hardfile). no hardfile CLIENT=MACH005 BUSTYPE=ISA SWAPTARGET=S 2. Type the following command: RPLSETD /R:d:\path\response_filename where d:\path\response_filename is the fully qualified file name of the resonse file. CREATING NEW OS/2 2.1 RIPL CLIENTS ---------------------------------- The menu interface has been updated to automatically select the FITS\DEFALT21.FIT entry when a 'NEW' client is created using an OS/2 2.1 server record id. However, the master CONFIG.20 files have not been updated to OS/2 2.1 level so that back level versions of OS/2 can also be supported. The differences between an OS/2 2.0 and OS/2 2.1 CONFIG.20 file are minor, mainly new SET statements. In most cases the CONFIG.20 file will work for OS/2 2.1 as is. However, if you wish to convert the client CONFIG.20 to the OS/2 2.1 level, run the RPLSETD command against the client. RPLSETD will update the CONFIG.20 file to the OS/2 2.1 level. A new client created using the defaults, will be configured to support the IBMVGA32 display drivers. If the client has an XGA or 8514 display attached, RPLSETD must be run against the client to reconfigure the client for the correct display type. UPDATING MASTER WORKPLACE SHELL OS2.INI FILES --------------------------------------------- Some users have a master customized OS2.INI file that is copied to the client directory each time the client is remote booted. This master file must also be update to identify the type of display driver that the client workstation is using. Clients with different display types (i.e. vga, xga, 8514) MUST use different master OS2.INI files. To update a master OS2.INI file, enter the following command: RPLRXUTL /D:DISPLAY_DRIVER /C:INI_FILENAME where: /D:DISPLAY_DRIVER is the same as for RPLSETD. /C:INI_FILENAME is the drive, path, and filename of the master OS2.INI file to be updated. For example: RPLRXUTL /D:IBMVGA32 /C:E:\IBMLAN\RPL\MASTER\VGAOS2.INI The RPLRXUTL utility will not display any error information. It does return with a non-zero return code if there was an error. If you need to verify error information, invoke RPLRXUTL from a CMD procedure (batch file or Rexx) so that the return code can be tested. SUPPORTING MULTIPLE LEVELS OF THE OS/2 OPERATING SYSTEM ------------------------------------------------------- It is possible to install and support multiple levels of the OS/2 2.x operating system on a RIPL server. This section documents the correct procedure to use to support such an environment. It is assumned that the OS/2 2.1 Remote IPL Support updates have already been installed. The basic procedure is as follows: 1. Run the OS/2 utility RIPLINST to install the OS/2 code in the RIPL directory tree. You must be carefully to use the version of RIPLINST that matches the level of code to be installed. RIPLINST is located on diskette 7 of all OS/2 2.x installation diskettes. RIPLINST is unique for each version of OS/2. 2. After running RIPLINST for OS/2 2.1, run the RPLMIG21.CMD procedure to install the 2.1 RIPL support. 3. After running RIPLINST, run the LAN Server utility, GETRPL. GETRPL uses information stored in the OS2SYS.INI file by RIPLINST so it is very important that GETRPL be run before using RIPLINST to install another version of OS/2. 4. Repeat steps 1, 2, and 3 for each version of OS/2 that will be RIPLed. 5. Check the \IBMLAN\RPL\RPL.MAP file. Look for the OS/2 server records, they start with yyyyyyyyyyyy or ;yyyyyyyyyyyy and field two will contain a name like OS220*.CNF or OS221*.CNF. A comment in column 1 indicates the record is disabled. Make sure that the appropriate records are enabled/disabled based on what OS/2 version(s) you installed. 6. Determine whether the special RIPL client, DEFALT20, should be updated by RPLSETD. This depends on what OS/2 versions are installed. OS/2 version 2.0 uses 16 bit display drivers. OS/2 versions 2.00.1, 2.0+Service Pak, and 2.1 use 32 bit display drivers for VGA and XGA support. However, there are slight differences in the XGA support between 2.00.1 and 2.0+Service Pak/2.1. If OS/2 2.0 is present, DEFALT20 must not be updated. It must remain as is to allow the creation of future 2.0 clients. If OS/2 2.0 is not present, then DEFALT20 could be updated with RPLSETD to support either 2.00.1 or 2.0+Service Pak/2.1. To update DEFALT20 to support 2.0+Service Pack, enter the command: RPLSETD /D:IBMVGA32 /C:DEFALT20 To update DEFALT20 to support 2.00.1, enter the command: RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.20a The /N parameter indicates that the new default target operating system will be \IBMLAN\RPL\OS2.20a. The RIPLINST for OS/2 2.00.1 defaulted to a target directory of \IBMLAN\RPL\OS2.20a. To update DEFALT20 to support 2.1, enter the command: RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.21 The /N parameter indicates that the new default target operating system will be \IBMLAN\RPL\OS2.21. The RIPLINST for OS/2 2.1 defaults to a target directory of \IBMLAN\RPL\OS2.21. 7. Since the special RIPL client DEFALT20 must be associated with a specific OS/2 version, it is recommended that model clients be created for the other OS/2 versions installed in the RIPL tree. RPLSETD can be used to update the model client definitions to point to the correct operating system. Then these model clients can be used to create future clients for each operating system type.