README.CID OS/2 OS/2 OS/2 Warp Server for e-business CONTENTS _________ 1.0 PREFACE 2.0 INTRODUCTION 2.1 Important Notes 3.0 CODE SERVER SETUP 3.1 Loading the Diskette Images on the Code Server 3.2 Extracting the CID Utilities from the OS/2 Images 3.3 Extracting the SETBOOT and XCOPY Programs from the OS/2 Images 3.4 Extracting the REXX files from the OS/2 Images 4.0 CREATING CID BOOT DISKETTES 5.0 CREATING HARD DISK BASED MAINTENANCE ENVIRONMENTS 5.1 PREPMNT.CMD 5.2 CHKINST.EXE 5.3 SEMAINT.EXE 6.0 INSTALLING OS/2 ON THE CLIENT (SEINST.EXE) 7.0 SVGA CID UTILITY 7.1 SVGA/GRADD Installation in a CID Environment (DSPINSTL) 7.2 Video Configuration in a CID Environment (VCFGCID) 8.0 CID ENABLED MULTIMEDIA 9.0 NEW VERSIONS OF THE GET UTILITIES 10.0 USING A RESPONSE FILE TO INSTALL OS/2 10.1 Modifying the Sample Response File 10.2 New Keywords 10.3 RSPINST Return Codes 11.0 INSTALLATION OF 386 HPFS 12.0 NetView DM/2 INSTALL CLIFI NOTES 13.0 TRADEMARKS 1.0 PREFACE _______________ This readme file refers to several IBM products that support the execution of OS/2 CID installs: o LAN CID Utility -- a lightly attended installation mechanism that ships with Network Transport Servers/2 (NTS/2) and the Multi-Protocol Transport Services (MPTS) program available with LAN Server 4.0. o NetView Distribution Manager (NetView DM) OS/2 Products -- the NetView DM family of products provides a cross platform software distribution mechanism. The OS/2 components of NetView DM are NetView Distribution Manager/2 (NVDM/2) and NetView Distribution Manager Agent/2 (NVDMA/2). NVDM/2 provides for software distribution from OS/2 code servers and NVDMA/2 provides for software distribution from AIX or NetWare code servers. 2.0 INTRODUCTION ____________________ You can do a redirected or CID installation of OS/2 to a client workstation from a code server. The three basic steps to do this are: 1. Code server setup. 2. Boot diskette or maintenance environment creation. 3. CID installation of OS/2. The first step, "Code server setup" can be further broken down into the following steps: 1. Copy the diskette images to the code server. 2. Extract the CID utilities from the OS/2 images. 3. If LAN CID Utility is being used: a) Extract the SETBOOT and XCOPY programs from the OS/2 images b) Extract the REXX files from the OS/2 images 2.1 Important Notes --------------------- 1. If you are planning to install OS/2 Warp Server for e-business via CID and will be using a Maintenance partition, Please be sure to read Section 5 of this file. 2. Please be sure to check the Sample.rsp file for OS/2 Base and Feature Install components, along with Section 10.0 of this file. The response files that you have used to install previous versions of OS/2 may not work, and there are a number of new components in this version that you may wish to install. Values for some keywords have changed too. 3. If you are planning to install 386 HPFS or do have 386 HPFS installed on your system, please read section 11.0 before you begin installation 3.0 CODE SERVER SETUP _______________________ 3.1 Loading the Diskette Images on the Code Server ---------------------------------------------------- In order to CID install OS/2, the OS/2 installation diskette images must be accessible to the client workstations from the code server. If you have OS/2 on a CDROM, then you can either share the CDROM directly to the client workstations or use the procedures outlined in "LOADING THE DISKETTE IMAGES ON THE CODE SERVER FROM CDROM" to copy the diskette images from the CDROM to the hard disk of the code server. To load the diskette images on the code server from a CDROM, run the following command: XCOPY source_path target_path /S Parameters: source_path the path to the "root" of the OS/2 diskette images on the CDROM. For example, if the files from the OS/2 installation diskette #1 are in the directory G:\OS2IMAGE\DISK_1 on the CDROM, then this parameter would be G:\OS2IMAGE. target_path the path to the target subdirectory to which the OS/2 diskette images are to be copied. Example: XCOPY G:\OS2IMAGE C:\CID\IMG\WSEBUS /S Note: The /S parameter copies everything including the files and subdirectories residing within subdirectories of the source path. 3.2 Extracting the CID Utilities from the OS/2 Images ------------------------------------------------------- The programs and files required for the redirected installation of OS/2 are packed in files on the diskettes that were copied to the code server in "LOADING THE DISKETTE IMAGES ON THE CODE SERVER ". The GETOSCID command file unpacks the following files from the OS/2 diskette images: RSPINST.EXE SAMPLE.RSP SEDISK.EXE SEIMAGE.EXE SEINST.EXE SEMAINT.EXE UNPACK.EXE UNPACK2.EXE GETOSCID syntax: GETOSCID source_path <target_path> Parameters: source_path The path where the OS/2 product images have been placed. This parameter is required. <target_path> The path to the subdirectory where the files should be placed. This path must be accessible to the client through a redirector such as SRVIFS. This parameter is optional and defaults to the current directory. Example: GETOSCID G:\OS2IMAGE D:\CID\EXE\WSEBUS Note: The GETOSCID command file is in "NEW VERSIONS OF THE GET UTILITIES". You can also use the GETOSCID.CMD provided with the LAN CID Utility 2.0 program included with MPTS. If you are using NVDM or the LAN CID Utility program included with NTS/2, then you should use the GETOSCID provided in this readme. 3.3 Extracting SETBOOT and XCOPY from the OS/2 Images ------------------------------------------------------- If you are using LAN CID Utility to install OS/2 on your client workstations, you must obtain the SETBOOT and XCOPY programs from the OS/2 diskette images on the code server. The GETBOOT utility unpacks SETBOOT.EXE and XCOPY.EXE from the OS/2 diskette images: GETBOOT Syntax: GETBOOT source_path <target_path> Parameters: source_path The path where the OS/2 product images have been placed. This parameter is required. <target_path> The path to the subdirectory where the files should be placed. This path must be accessible to the client through a redirector such as SRVIFS. This parameter is optional and defaults to the current directory. Example: GETBOOT G:\OS2IMAGE D:\CID\EXE\WSEBUS Note: The GETBOOT command file is in "NEW VERSIONS OF THE GET UTILITIES". You can also use the GETBOOT.CMD provided with the LAN CID Utility 2.0 program included with MPTS. If you are using NVDM or the LAN CID Utility program included with NTS/2, then you should use the GETOSCID provided in this readme. 3.4 EXTRACTING THE REXX FILES FROM THE OS/2 IMAGES ---------------------------------------------------- If you are using LAN CID Utility to install OS/2 on your client workstations, you must obtain the REXX files from the OS/2 diskette images on the code server. The GETREXX command unpacks the following files from the OS/2 diskette images: INSCFG32.DLL OSO001.MSG SHPIINST.DLL REX.MSG REXH.MSG REXX.DLL REXXAPI.DLL REXXINIT.DLL REXXTRY.CMD REXXUTIL.DLL RXQUEUE.EXE GETREXX Syntax: GETREXX source_path <target_path> Parameters: source_path The path where the OS/2 product images have been placed. This parameter is required. <target_path> The path to the subdirectory where the files should be placed. This path must be accessible to the client through a redirector such as SRVIFS. This parameter is optional and defaults to the current directory. Example: GETREXX G:\OS2IMAGE D:\CID\DLL\WSEBUS Note: The GETREXX command file is in "NEW VERSIONS OF THE GET UTILITIES". Use this version of GETREXX. 4.0 CREATING CID BOOT DISKETTES _________________________________ When installing OS/2 it is often necessary to create boot diskettes for use at the client workstation. There are several steps required for creating the CID boot diskettes. The first step is to run the SEDISK program provided with OS/2. This command must be run on a system with the same version. SEDISK syntax: SEDISK /S:source_path /T:target_path /P:<pcmcia_id#> Parameters: /S:source_path The fully qualified path to the OS/2 images. This parameter is required. /T:target_path The drive indicator of the diskette drive where the boot diskettes will be created. This parameter is required. /P:<pcmcia_id#> Use this optional parameter when pcmcia driver support is needed. When the /P: option is used, the PCMCIA.SYS driver (as well as the appropriate socket driver) is copied to diskette one. The pcmcia_id# represents a number associated with the computer desired. Look at the default response file at the keyword PCMCIA to find the number to put in here. For example, use /P:1 if you need to boot on an AMBRA486 SN425C. The pcmcia_id# must be a number representing a valid parameter of keyword PCMCIA in the default response file. It cannot be 0. Example: SEDISK /S:D:\CID\IMG\WSEBUS /T:A: Note: Because boot diskettes are specific to the software distribution manager being used, to complete the boot diskette creation, follow the instructions provided by your software distribution manager. 5.0 CREATING HARD DISK BASED MAINTENANCE ENVIRONMENTS _______________________________________________________ IMPORTANT -- CHANGES FOR OS/2 Warp Server for e-business There are 2 new utilities that have an impact on CID installation of OS/2 Warp Server for e-business. These utlities are PREPMNT.CMD and CHKINST.EXE. 5.1 PREPMNT.CMD: ------------------ There is a step you will need to take if running SEMAINT on a system on which you have never installed OS/2 Warp Server for e-business. You must copy a new version of the Device drivers from the OS/2 Warp Server for e-business CDROM. These drivers are located in the \OS2IMAGE\DISK_1 directory on the CDROM and need to be copied to the \OS2\BOOT directory of the partition from which you have booted up. This step can be done manually or by running a new REXX utility called PREPMNT.CMD available in the \CID\EXE\OS2 directory. Prepmnt will backup the current device drivers and then copy the new drivers to \OS2\BOOT. Prepmnt uses an executable called findboot.exe to determine the Boot Drive. PREPMNT can be run from LCU or a Software Distribution Manager environment. After running Prepmnt, you will need to reboot the system before running CHKINST or SEMAINT. PREPMNT syntax: Prepmnt <Source_path> [Logfile] where Source_path The fully qualified path to the OS/2 images. This parameter is required. Logfile The fully qualified name of the file into which log information is to be placed. The directory in which the log file is to be placed must already exist. This parameter is optional. Example : Prepmnt f:\os2image W:\logs\prepmnt.log 5.2 CHKINST.EXE: ------------------- The CHKINST utility checks the system to determine what preparation is required before installation and then reports the results. CHKINST checks for any Software or Software component installed on a Target drive that must be removed to ensure a successful OS/2 installation. CHKINST will also check for and report any inconsistencies in the current hard disk partitioning that may be incompatible with LVM. By running CHKINST, CID administrators and users are thus given an opportunity to back up their systems before running SEMAINT and SEINST. Note that CHKINST is CID enabled and can hence be executed in a LCU or Software Distribution Manager environment. CHKINST will return a CID return code of 0000, if CHKINST did not find any serious potential problems that may cause problems during installation. The log may contain other warning messages. If CHKINST encounters either of the following conditions, a CID return code of 0008 is returned : 1. CHKINST detects components in use that you must remove prior to installation if you choose not to format the specified Target drive. Such components include : LAN Distance, IBM Peer, Local Security, and 386 HPFS ACLs. 2. CHKINST has detected inconsistencies in the current hard disk partitioning that may be incompatible with LVM or corrupt partitions on your hard disk. If CHKINST returns a return code of 0008, refer to the Log file for more information. CHKINST syntax: CHKINST /T:<Target_drive> /L1:<Logfile> Example : chkinst /T:G: /L1:W:\logs\chkinst.log If CHKINST fails with a return code of 0x1600 or 0x1604, make sure the arguments passed in are correct. Note that both arguments are required. Also, check to make sure that the files VCU.EXE and VCU.MSG exist in the same directory as CHKINST.exe. NOTE: You may need to run Prepmnt.cmd before running CHKINST. Read Section 5.1 for more information. 5.3 SEMAINT: ------------ The SEMAINT command installs a minimal version of the OS/2 program on a workstation hard disk. This minimal OS/2, also known as a maintenance system, does not contain the Presentation Manager or Workplace Shell features of the OS/2 program. When booted on a maintenance system, the normal system files are not locked. The OS/2 install program (SEINST) and Service Pak install program (FSERVICE) run under the maintenance system created by SEMAINT or on boot diskettes created by SEDISK. NOTE: Before running SEMAINT on a system on which you have never installed OS/2 Warp Server for e-business, it is important to run PREPMNT.CMD. Read Section 5.1 for more information. SEMAINT syntax: SEMAINT /S:source_path /T:target_path /B:boot_drive /L1:log_file /P:<pcmcia_id#> /F Parameters: /S:source_path The fully qualified path to the OS/2 images. This parameter is required. /T:target_path The fully qualified target directory name. The maintenance system will be installed in this directory on one of the workstation's local drives.This parameter is required. /B:boot_drive The drive from which the seed system will boot. This must be on a local drive. This parameter is required. If the target directory (/T:) is an HPFS drive, then the boot drive (/B:) must also be an HPFS drive. /L1:log_file The fully qualified name of the file into which log information is to be placed. The directory in which the log file is to be placed must already exist. This parameter is required. /P:<pcmcia_id#> Use this optional parameter when pcmcia driver support is needed. When the /P: option is used, the PCMCIA.SYS driver and the appropriate socket driver are copied to the boot drive. The pcmcia_id# represents a number associated with the computer desired. Look at the default response file at the keyword PCMCIA to find the number to put here. For example /P:1 would be used if you need to boot on an AMBRA486 SN425C. The pcmcia_id# must be a number representing a valid parm of keyword PCMCIA in the default response file. The pcmcia_id# cannot be 0. /F Use this optional parameter to Force Volume conversion. This is to be used when the target system may have corrupt partitions on 1 or more hard drives, and you wish to Force volume creation on the hard drives. It is extremely important that you back up all the hard drives on the system before invoking SEMAINT using this parameter because if the Volume Creation Utility that SEMAINT uses encounters corrupt partitions, it will delete them, and you will lose all data on these partitions. Note that if this switch is not used, volumes will be created as long as the Volume Creation utility used by SEMAINT does not encounter corrupt partitions in which case SEMAINT will abort without creating any new volumes. These corrupt partitions and /or LVM incompatible partitions will be detected by CHKINST if it is run. Example: To build a maintenance system for installing OS/2 Warp Server for e-business: X:\EXE\WSEBUS\SEMAINT /S:X:\IMG\WSEBUS /T:C:\SERVICE /B:C: /L1:X:\LOG\WSEBUS\SEMAINT.LOG Note: Because boot diskettes are specific to the software distribution manager being used, to complete the boot diskette creation, follow the instructions provided by your software distribution manager. 6.0 INSTALLING OS/2 ON THE CLIENT ___________________________________ The SEINST program installs the OS/2 program on the client workstation. SEINST is normally run under a maintenance system created by SEMAINT or on boot diskettes created by SEDISK. SEINST runs RSPINST.EXE, which reads the named response file and performs the installation. If SEINST is run under a maintenance system created by SEMAINT, SEINST also cleans up the directory from which the system was booted. SEINST syntax: SEINST /S:source_path /T:<target_path> /B:boot_drive /L1:log_file /R:response_file /S:source_path The fully qualified path to the OS/2 images. This parameter is required. /T:target_path The fully qualified target directory name from which the system was booted. If the system was booted from a maintenance system on the hard disk, this path matches the /T: parameter passed on the previous invocation of the SEMAINT program. This parameter is required if booted from the hard disk, but optional if booted from diskette. If this parameter is specified when booted from diskette, no parameter validation is done on its value. WARNING: Because SEINST deletes all files as it cleans up this subdirectory, back up the files you want to save. /B:boot_drive The drive from which the seed system will boot. This must be on a local drive. This parameter is required. /L1:log_file The fully qualified name of the file into which log information is to be placed. The directory in which the log file is to be placed must already exist. This parameter is required. /R:response_file The fully qualified file name of the response file supported by RSPINST. This parameter is required. Example when booted from boot diskettes: X:\EXE\WSEBUS\SEINST /S:X:\IMG\WSEBUS /B:C: /R:X:\RSP\WSEBUS\RESPONSE.FIL /L1:X:\LOG\WSEBUS\CLIENT.LOG Example when booted from maintenance system: X:\EXE\WSEBUS\SEINST /S:X:\IMG\WSEBUS /B:C: /R:X:\RSP\WSEBUS\RESPONSE.FIL /L:X:\LOG\WSEBUS\CLIENT.LOG /T:C:\SERVICE NOTE: For more information about the program RSPINST, look at the section "USING A RESPONSE FILE TO INSTALL OS/2". This section describes running response file install from diskette and can help you understand response file installation. RSPINST error codes are listed in the section "RSPINST RETURN CODES". 7.0 SVGA and GRADD CID UTILITIES __________________________________ To install SVGA/GRADD support in a CID environment, you will need to run a utility called DSPINSTL. For monitor, resolution and refresh rate configuration, the utility called VCFGCID should be used. This section discusses these two utilities. 7.1 SVGA/GRADD Installation in a CID Environment (DSPINSTL) ------------------------------------------------------------ Invoke SVGA/GRADD CID installation as a post install method after booting into a PM based environment. DSPINSTL.EXE is in the OS2\INSTALL directory. DSPINSTL syntax: DSPINSTL /PD:dsc_file /S:source_path /T:target_drive /RES:resolution /U Parameters: /PD:dsc_file The fully qualified .DSC file name. /S:source_path The fully qualified path to the OS/2 images. /T:target_drive The target drive or bootdrive. /RES:resolution The resolution to come up in after reboot. /U Indicates unattended installation. Notes: 1. If a resolution was passed in that is not supported in the .PMI file then an error will occur. 2. If a resolution was passed in that is in the .PMI and not supported by the driver, then driver should default to low resolution. Example of installing S3** CHIP 86C805 at resolution 1024x768x256 with CID: DSPINSTL /PD:C:\OS2\INSTALL\PSS3.DSC /S:X:\IMG\WSEBUS /T:C: /RES:1024x768x256 /U The following is a list of .DSC files and the chip sets. pshead.dsc "Headland Technology HT209" VIDEO7_HT205_CHIP = 1 VIDEO7_HT208_CHIP = 2 VIDEO7_HT209_CHIP = 3 pstrid.dsc "Trident Microsystems TVGA8900c" TRIDENT_8800_CHIP = 1 TRIDENT_8900_CHIP = 2 pstseng.dsc "Tseng Laboratories ET4000" TSENG_ET3000_CHIP = 1 TSENG_ET4000_CHIP = 2 tliw32.dsc "Tseng Laboratories ET4000/W32, /W32i, /W32p" TSENG_ET4000W32_CHIP = 3 TSENG_ET4000W32I_CHIP = 4 TSENG_ET4000W32IB_CHIP = 5 TSENG_ET4000W32IC_CHIP = 6 TSENG_ET4000W32PA_CHIP = 7 TSENG_ET4000W32PB_CHIP = 8 TSENG_ET4000W32PC_CHIP = 9 pswd.dsc "Western Digital WD90C11, C30, C31 (C30 mode only)" WESTERNDIG_PVGA1A_CHIP = 1 WESTERNDIG_WD9000_CHIP = 2 WESTERNDIG_WD9011_CHIP = 3 WESTERNDIG_WD9030_CHIP = 4 WESTERNDIG_WD9026_CHIP = 5 WESTERNDIG_WD9027_CHIP = 6 pswdc31.dsc "Western Digital 90C31" WESTERNDIG_WD9031_CHIP = 7 pswdc24.dsc "Western Digital 90C24" WESTERNDIG_WD9024_CHIP = 8 wdc33.dsc "Western Digital 90C33" WESTERNDIG_WD9033_CHIP = 9 psati.dsc "ATI Mach8, ATI 28800" ATI_18800_CHIP = 1 ATI_28800_CHIP = 2 ATI_38800_CHIP = 3 8514 CHIP not SVGA atim32.dsc "ATI Mach32" ATI_68800_CHIP = 4 psspdw.dsc "IBM VGA 256c " IBM_SVGA_CHIP = 1 pscl.dsc "Cirrus Logic** 5422, 5424" CIRRUS_5420_CHIP = 1 CIRRUS_5422_CHIP = 2 CIRRUS_5424_CHIP = 3 cl54x.dsc "Cirrus Logic 5426, 5428, 5430, 5434" CIRRUS_5426_CHIP = 4 CIRRUS_5428_CHIP = 5 CIRRUS_5429_CHIP = 6 CIRRUS_543X_CHIP = 7 CIRRUS_5434_CHIP = 8 pss3.dsc "S3 86C801, 86C805, 86C928" S3_86C805_CHIP = 1 S3_86C928_CHIP = 2 s38641m.dsc "S3 864 (16M colors with 1MB of Video Mem)" #define S3_86C864_CHIP = 4 #define S3_86C964_CHIP = 5 wp9000.dsc "Weitek Power 9000" WEITEK_P9000_CHIP = 1 wp9100.dsc "Weitek Power 9100" WEITEK_W5186_CHIP = 2 WEITEK_W5286_CHIP = 3 WEITEK_P9100_CHIP = 4 gengradd.dsc "Generic VESA Unaccelerated GRADD" Most adapters for which the "Super VGA" or "VGA" driver is selected by default requires VESA BIOS. m64gradd.dsc "ATI Mach 64/Rage Family GRADD" 17236 = ATI Mach64 CT 17240 = ATI Mach64 CX 17752 = ATI Mach64 EX 18242 = ATI 3D Rage Pro (BGA, AGP) 18260 = ATI 3D Rage (GT) 18264 = ATI Mach64 GX 22100 = ATI Mach64 VT 18244 = ATI 3D Rage Pro (BGA, AGP 1X only) 18249 = ATI 3D Rage Pro (BGA, PCI) 18256 = ATI 3D Rage Pro (PQFP, PCI) 18257 = ATI 3D Rage Pro (PQFP, limited 3D) 18261 = ATI 3D Rage II+ (GTB) 18262 = GV = = ATI 3D Rage IIC 22101 = ATI Mach64 VTB 22102 = ATI Mach64 VT4 mgagradd.dsc "Matrox Millenium/Mystique Family GRADD" 1305 = Millenium 1306 = Mystique 1307 = Millenium II s3dgradd.dsc "S3 Virge/Trio3D Family GRADD" 22065 = Virge 34877 = Virge VX 35076 = Trio 3D 35329 = Virge DX 35344 = Virge GX2 s3gradd.dsc "S3 86x/96x/Trio Family GRADD" 35009 = 4 = S3 864 5 = S3 964 6 = S3 868 7 = S3 968 34832 = 8 = S3 Trio32 (732) 34833 = 9 = S3 Trio64 (764) 34833 = 10 = S3 Trio64V+ (765) 15 = S3 Trio65V+ (765 Family) vgagradd.dsc "VGAGRADD" most adapters for which the "Super VGA" or "VGA" driver is selected by default chpgradd.dsc "Chips & Technology 6555x Family GRADD" 224 = 65550 225 = 65551 226 = 65552 227 = 65553 228 = 65554 229 = 65555 Resolutions supported by each driver depend on factors such as the amount of video memory and the resolutions supported by the driver. 7.2 Video Configuration in a CID Environment (VCFGCID) ------------------------------------------------------- This utility will allow for you to select a monitor, resolution and refresh rate as part of a CID installation. The utility "VCFGCID.CMD" is a command file which is called from a SDM (Software Distribution Manager) and which takes the following parameters: vcfgcid /L1:<Error Log> - Name of error log file /L2:<History Log> - Name of history log file /RES:<HORIZONTALxVERTICALxCOLORS> - Resolution i.e. 1024x768x256 /MON:<Monitor Index> - Index of selected monitor in "MONITOR.DIF" file (see below) /PMI - Indicates that the utility should regenerate the svgadata.pmi file if selected monitor has greater capabilities than default monitor /RR:<Refresh Rate> - Desired refresh rate for selected resolution "/L1:" and "/L2:" are optional. You must specify at least one of "/RES:", "/MON:" or "/RR:" The monitor "Index" passed as the value for parameter "/MON:" needs to be obtained from the "monitor.dif" file installed on the client system. A utility has been included "getmonid.cmd" which will search the monitor.dif file for specified keywords and return the index values. getmonid <key word> [<key word> ...] [-d <Monitor dif file>] where "-d <Monitor dif file>" is optional and allows for the specification of a an explicit "monitor.dif" file. If not specified than the DPATH is searched for "monitor.dif" example: getmonid ibm 15p -d monitor.dif returns: Index: 136 OEMString = "IBM 15PT/15XT TouchScreen Color Monitor 15 inch, IBM Corporation" Index: 135 OEMString = "IBM 15P/15X/15XG Color Monitor 15 inch, IBM Corporation" Choose the index which corresponds to the monitor you wish to be selected. To configure video for your system using CID, you must install the appropriate display support and reboot. Then use the following information to modify your LCU (LAN Configuration, Installation and Distribution Utility) command file. Notes 1. LCU and related documentation/utilities are provided as applets included with the IBM MPTS (Multi-Protocol Transport Services) product which is included with IBM Lan Server V3.0, V4.0 and OS/2 Warp server products. Please refer to the documentation which comes with these products for further information on LCU. 2. The following information is meant as a guide. Your LCU command file might be different. 3. You must have already installed and be running the appropriate display driver. You cannot install the display driver and run this utility in one pass. Simply have your cid installation install the driver and then reboot the system before running this configuration utility. Setting up the LCU Command file for VCFGCID /*****************************************************/ /* LCU PRODUCT DATA SECTION */ /*****************************************************/ . . . x.vcfgcid = 15 x.15.name='CID Videocfg' x.15.statevar = 'CAS_' || x.15.name x.15.instprog = bootdrive || '\os2\install\vcfgcid.cmd', ' /l1:' || bootdrive || '\os2\install\vcfgerr.log', ' /l2:' || bootdrive || '\os2\install\vcfghist.log', ' /res:1024x768x256', ' /rr:75', ' /pmi', ' /mon:135' x.15.rspdir = '' x.15.default = '' /*---------------------------------------------------*/ /* NUMBER OF PROGRAMS SET UP IN THE */ /* PRODUCT DATA SECTION */ /*---------------------------------------------------*/ NUM_INSTALL_PROGS = 15 /*****************************************************/ /* INSTALLATION SECTION */ /*****************************************************/ . . . when OVERALL_STATE = 3 then do if RunInstall(x.vcfgcid) == BAD_RC then exit Call CheckBoot end . . . /*****************************************************/ END OF LCU INFORMATION TO BE ADDED /*****************************************************/ The following is an explanation of the line that is executed in the LCU command file: C:\OS2\INSTALL\VCFGCID /l1:c:\os2\install\vcfgerr.log /l2:c:\os2\install\vcfghist.log /res:1024x768x256 /rr:75 /pmi /mon:135 /l1:c:\os2\install\vcfgerr.log is the log file for any errors that may occur /l2:c:\os2\install\vcfghist.log is the log file for documenting results of calls to vcfgcid /res:1024x768x256 is the desired resolution/color depth. If not supported by the current adapter than will default to supported resolution. /rr:75 set the vertical refresh rate to 75hz. If not supported than will default to supported resolution /pmi tells utility to regenerate the svgadata.pmi file with new monitor capabilities /mon:135 select monitor corresponding to index 135. In this case we choose "IBM 15P/15X/15XG Color Monitor 15 inch, IBM Corporation" NOTE: If by selecting a new monitor a new svgadata.pmi file is generated, the utility will cause a "reboot with callback" and then configure resolution/refresh rate if needed. 8.0 CID ENABLED MULTIMEDIA ____________________________ Multimedia is enabled for CID. Choose MULTIMEDIASUPPORT=1 in the OS/2 response file to specify installing the multimedia files during the install. Multimedia CID installation is invoked as a post install method after booting into a PM based environment. MINSTALL.EXE is in the MMTEMP directory. MINSTALL must be run from the MMTEMP subdirectory. MINSTALL syntax: MINSTALL /M /C:<response_file> /R:<response_file> Parameters: /M This parameter tells MINSTALL.EXE to transfer files from the MMTEMP directory to the directory where the files need to be for multimedia IPL. This is required for CID. /C:<response_file> Use this parameter to create a response file for unattended multimedia installation of other machines using the /R parameter. /R:<response_file> Use this parameter when you have already created a response file using the /C parameter. Use a response file with multimedia install only if the machine's hardware setup is the same as the hardware setup of the machine the response file was created on. Recommended invocation of MINSTALL: MINSTALL /M Example of invoking MINSTALL while creating a response file: MINSTALL /M /C:MEDIA.RSP 9.0 NEW VERSIONS OF THE GET UTILITIES ______________________________________ The GETOSCID, GETBOOT, and GETREXX command files mentioned earlier in this readme are in the \CID\LOCINSTU directory. 10.0 USING A RESPONSE FILE TO INSTALL OS/2 ____________________________________________ This section describes how to use a response file to install OS/2. It is intended primarily for people who will be setting up workstations for others to use. If you have installed previous versions of OS/2 or other operating systems, you are familiar with installation procedures that require you to insert and remove a series of diskettes and answer screen prompts. When you use a response file to install, it is not necessary to answer any screen prompts. All the answers are in a response file that you have created. The Installation program reads this response file instead of prompting you for the installation information. A sample response file is included on the OS/2 installation diskettes. When you install the operating system, this response file (called SAMPLE.RSP) is placed in the OS2\INSTALL directory. The SAMPLE.RSP file and other files needed for a response file installation are not automatically installed on your system if you installed OS/2 using the default Installation. You must add these files to your system in order to use them. Follow these steps: 1. Open OS/2 System on your Desktop. 2. Open System Setup. 3. Open Selective Install. The Software Configuration screen appears. 4. Select Optional System Utilities. 5. Select the More push button to the right of Optional System Utilities. A window appears with a list of utilities. 6. Place a check mark next to Installation Utilities; then select Install. 7. When prompted to do so, insert the requested installation diskettes. Select OK when you are done. 10.1 Modifying the Sample Response File ----------------------------------- After you install the SAMPLE.RSP file on your own system, you can modify the SAMPLE.RSP file and use it to install OS/2 on another workstation. Use an editor (such as the System Editor) to modify the sample response file. The following is an excerpt from the sample response file: ************************************* *AlternateAdapter *; * Specifies secondary adapter for two display systems. * This should be a lower or equal resolution display since * the highest resolution display will be primary for PM. * * Valid Parms * * 0=None (DEFAULT) * 1=Other than following (DDINSTAL will handle) * 2=Monochrome /Printer Adapter * 3=Color Graphics Adapter * 4=Enhanced Graphics Adapter * 5=PS/2 Display Adapter * 6=Video Graphics Adapter * 7=8514/A Adapter * 8=XGA Adapter * 9=SVGA Adapter ************************************* 10.2 New Keywords Some new keywords have been added to SAMPLE.RSP for OS/2 Warp Server for e-business to provide support for new features. Some of these new keywords are processed by SEINST.EXE while others are processed by Feature Installer (FI) using a utility called CLIFI.EXE. SMP support is selectable using the SMP and SMPPath keywords described below. For Full SMP support, one needs to select SMP and run SEINST as well as CLIFI. The new keywords added to Sample.rsp that are processed by SEINST include: * Format Partition with JFS FormatJFS= * Perform Quick Format of Partitions FormatQuick= * Specify Name of Locale to be installed Locale=en_us * Install SMP Support (Run CLIFI for complete SMP support) SMP=1 * Path to SMP (PSD) Support Files SMPPath=C:\OS2\BOOT The Sample.rsp file provided contains some keywords that are not processed by SEINST. These keywords along with other keywords noted in the following section are processed by CLIFI. Note that the same response file can be used by SEINST and CLIFI. The syntax for these keywords is KEYWORD.Selection=? Where KEYWORD is the new software selection and ? is: 0 - do not install 1 - install Some of these keywords are followed by KEYWORD.TarDrv=? Select the drive you want this software selection to be installed to. Replace the ? with a standard drive letter designator such as C: or D: (the colon is required). In order to install the software selection to the specified drive, the drive must have been previously formatted. (See the FormatFAT=/FormatHPFS= keyword in SAMPLE.RSP.) The CLIFI utility is installed when response file install (SEINST) is run, and is located on the target machine's \OS2\INSTALL directory. Note that to run CLIFI, Presentation Manager (PM) needs to be running. Run CLIFI as soon as possible after the base install, even if you do not want to install certain new software options, because some other applications such as CM/2 depend on Systems Management being present when they are installed. Systems Management is installed by default when CLIFI is run, as are several other options. (Refer to the second list of keywords below for these features). Several of these options are default selected in a non-CID environment, and are recommended for installation in a CID environment by using one of the methods below to run CLIFI.EXE after the response file install. Lan Configuration Utility (LCU) and Netview DM/2 users can create LCU program definitions and Netview DM/2 program profiles that will execute CLIFI in an unattended install. The syntax required to execute CLIFI and install the selected new software unattended is as follows: CLIFI /a:c /s:<OS/2 CID Image Directory for FI components> (for example, Z:\OS2IMAGE\FI) /b:<OS/2 BOOTDRIVE> (for example, C:) /r:BOOTDRIVE:\OS2\INSTALL\FIBASE.RSP> (for example, C:\OS2\INSTALL\FIBASE.RSP) /r2:<Partial Response File> (for example, Z:\CID\RSP\WSEBUS\SAMPLE.RSP) /f:<BOOTDRIVE:\OS2\INSTALL (for example, C:\OS2\INSTALL) /l1:<PATH TO YOUR ERROR LOGGING DIRECTORY> (for example, Z:\LOG\WSEBUS\BASE.ERR) /l2:<PATH TO YOUR PROGRESS LOGGING DIRECTORY> (for example, Z:\LOG\WSEBUS\BASE.LOG) The following keywords have been added to SAMPLE.RSP for processing by CLIFI. * External Floppy Drive (Laptop) HOTPLUG.Selection=0 * Floppy/CDROM swapping for Ultra Bay devices WARMSWAP.Selection=0 WARMSWAP.ThinkPad=IBM ThinkPad 755CD/CDV WARMSWAP.ThinkPad=IBM ThinkPad 760C/CD WARMSWAP.ThinkPad=IBM ThinkPad 760E WARMSWAP.ThinkPad=IBM ThinkPad 760ED WARMSWAP.ThinkPad=IBM ThinkPad 760EL/ELD WARMSWAP.ThinkPad=IBM ThinkPad 760X/XD WARMSWAP.S506Parm=/A:1 /U:0 * MarkNet Port Driver Support PUMARKNET.Selection=0 PUMARKNET.TarDrv=C: * MarkVision Support PUMARKVIS.Selection=0 PUMARKVIS.TarDrv=C: * Extra Font Support IBMFONTA.Selection=0 IBMFONTG.Selection=0 IBMFONTT.Selection=0 IBMFONTJ.Selection=0 IBMFONTC.Selection=0 IBMFONTS.Selection=0 IBMFONTK.Selection=0 IBMFONTU.Selection=1 XIBMFONT.InstDrive=C: * Logical Volume Manager Support LVMGUI.Selection=1 The following keywords are NOT included in SAMPLE.RSP but provide a means for you to select or deselect other software selections that are installed based on a default setting when CLIFI is used. * Application Registration ART.Selection=1 * Dax Base DAXCOMP1.Selection=1 DAXCOMP1.TarDrv=C: * Serviceability and Diagnostic Aids Option SRVDIAG.Selection=1 * Serviceability Documentation Option SRVDOC.Selection=1 * Security Base ODSECBASE.Selection=1 ODSECBASE.TarDrv=C: * Runtimes for Sun's Java Programming Environment Java11.Selection=1 Runtime.Selection=1 Samples.Selection=0 Toolkit.Selection=0 Debugger.Selection=0 TlktDoc.Selection=0 Note that if the Java Samples or the Java Toolkit is selected that the Java Runtimes must also be selected or the Java Samples and the Java Toolkit will not be installed correctly. In addition, in order to install Java support the target drive must be formatted using HPFS or JFS. If your bootdrive is not HPFS or you have another HPFS or JFS drive that you want to use for the Java selections, then add the following keyword on a new line after the Java11.Selection keyword. FIBASE.JavaDrive=E: (where E: is the HPFS drive you want to use) If this keyword is specified, CLIFI will install all selected JAVA components (i.e. Runtime, Samples,Toolkit, Toolkit Doc., and Debugger) on the same drive (E: in above example). If you wish to install the above components in different drives, use the following keywords : Java11.RUNDRV=C: Samples.SMPDRV=E: Toolkit.TKTDRV=D: Debugger.DBGDRV=D: TlktDoc.TDOCDRV=F: 10.3 RSPINST Return Codes --------------------------- When RSPINST encounters an error, it returns a non-zero return code to SEINST. SEINST displays this return code. The following is a list of some of those return codes. For a complete list, refer to the "LAN CID Utility Guide." Return Code Definition 702 Invalid Line in response file. 707 Invalid Key Value. 708 No response file found. 712 Response file keyword conflict. 715 Not enough free space on the targetdrive. 921 Target Drive Error. Use LVM to add target drive to Boot Manager Menu. 948 Error accessing OS/2 ini file. 1066 Invalid Base Product Level 1067 Invalid File System 1068 Microsoft Windows NT Files Found 1069 The version of OS/2 on the target system is newer than the OS/2 Installation files. 11.0 INSTALLATION OF 386 HPFS ______________________________ 386 HPFS is available as a separate feature. For information about 386 HPFS, see the README on the 386 HPFS Upgrade for OS/2 Warp Server for e-business CD. 12.0 NetView DM/2 INSTALL USING CLIFI ________________________________________ If you are using NVDM/2, follow these steps to ensure a successful installation: 1. Install OS/2, MPTS and NVDM/2 agent as a co-requisite group on the target machine. 2. After the target system comes up, reboot the target system either by shutting down the system locally, or initiating a 'CDM Activate' command on the target machine. Refer to the NVDM/2 documentation for details about activating a client. A CDM activate can be scheduled right after initiating step 1. 3. Schedule CLIFI.EXE after steps 1 and 2 above. See Section 10.0 for more information about installation of OS/2 Base components using CLIFI. 13.0 TRADEMARKS ___________________ The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both: AIX IBM NetView OS/2 Presentation Manager ThinkPad Workplace Shell TME 10 is a trademark of Tivoli Systems Inc. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. (C) Copyright IBM Corporation 1999. All rights reserved.