═══ 1. Users Guide ═══ OS2SERV v1.35 November 23, 1998 by Dick Kurtz NCSD Fix Distribution; Austin, Tx (c) Copyright International Business Machines Corporation, 1996, 1998. All rights Reserved. ═══ 2. Overview ═══ This program will install or backout a OS/2 Base or LAN FixPak. The only information you may be asked for is where to save files that are replaced by a FixPak and this only if you have never applied a FixPak before. You select the partition or partitions you want to service based on what is presented to you in the "Serviceable Products" window. You can check the "Advanced" checkbox to use SERVICE.EXE rather than FSERVICE.EXE if you want to have more control over the FixPak process. You then press "Install" or "Uninstall" to begin. If you are using "Advanced" then SERVICE.EXE is called and you use it's GUI to Install (Apply) or Uninstall (Backout) a FixPak. Otherwise a response file is built and passed to FSERVICE.EXE. SERVICE or FSERVICE do the actual FixPak processing and return to OS2SERV.EXE when done. Before SERVICE or FSERVICE is called, the free space on your harddisk is checked to make sure there is enough room to apply this FixPak to one or more partitions. This program is provided "ASIS". There is no official support. ═══ 2.1. Revisions ═══ 1.00 - 1st release. 1.01 - First release for Internet use. 1.02 - Cleanup and add "Advanced" option. 1.03 - Add Menu pulldown selections. 1.04 - Fix bug in freespace calculations. 1.05 - v1.08 info lost. 1.09 - Correct bug in SRV_PROD processing. 1.10 - v1.19 Skipped, jumped to v1.20 due to major change. 1.20 - Support CSF F.138 build changes in SRV_PROD file. 1.21 - Support target drive as 3rd parameter. 1.22 - Enforce NLS character restrictions. 1.23 - Handle multiple SYSLEVEL.xxx files on same drive in different dirs. 1.24 - Add message about Ctrl+Esc if using FSERVICE. 1.25 - ? 1.26 - Limit multiple syslevel error to OS2 only. 1.27 - Correct message about Ctrl+Esc. 1.28 - Y2K use date(S) for 4 digit year in Logger. 1.29 - use common Wincent routine. 1.30 - added more debug log entries. 1.31 - allow Backup if Archiving off for fixpak. 1.32 - add /B:x to FSERVICE call (x is the boot drive). 1.33 - implement use of csfdriveapply variable. 1.34 - Use SysDriveMap instead of FDISK which Aurora no longer supports. 1.35 - Force "Cleanup" to start over. ═══ 3. Requirements ═══ You can point to your own directory to install a FixPak from as long as you follow the guidelines for directory structure and content described in Creating the FixPak Source and CSF Source directories Place all the OS2SERV files in the same directory: OS2SERV.EXE OS2SERV.MSG OS2SERV.INF OS2SERV.ICO You then call OS2SERV and pass it the following parameters: OS2SERV x:\path x:\aaa\bbbbbbb s: "x:\path" is where the Corrective Service Facility files are located. This must be the first parameter passed to OS2SERV. "x:\aaa\bbbbbbb" is the path of the FixPak you want to apply. "aaa" is either OS2 or LAN. "bbbbbbb" is the name of the FixPak This must be the second parameter passed to OS2SERV. "s:" is the drive you want to service. This is an optional parameter. If not specified all drives are searched for products supported by this FixPak. So, if you put the CSF code in G:\CSF and the Fixpak in G:\FIXPAK\XR_W033 you would enter: OS2SERV G:\CSF G:\FIXPAK\XR_W033 This will search all drives for serviceable products. If you know you want to service only the E: drive then you could enter: OS2SERV G:\CSF G:\FIXPAK\XR_W033 E: OS2SERV.EXE is used by the Remote Software Update application available with Warp 3 and Warp 4. It allows you to download a FixPak from the Internet and have it applied to your system directly, rather than having to make diskettes. OS2SERV is the installation program that is called by RSUINST.EXE once all the FixPak files have been download and unzipped. When called without the above parameters, it expects the CSF and FixPak directories to be on the same drive as OS2SERV and nested one directory deeper (under) where OS2SERV is running. For RSU this will be: $pmtusr$\os2serv.exe $pmtusr$\os2serv.msg Message file. Can be translated for NLS use $pmtusr$\os2serv.inf The file you are viewing $pmtusr$\os2serv.ico Icon file $pmtusr$\os2serv FixPak base directory $pmtusr$\os2serv\fix $pmtusr$\os2serv\fix\os2.1 1st OS2 product in fixpak $pmtusr$\os2serv\fix\os2.2 2nd OS2product in fixpak $pmtusr$\os2serv\fix\os2.n nth OS2 product in fixpak $pmtusr$\os2serv\fix\mpm.n nth MMOS2 product in fixpak $pmtusr$\csf\......... Corrective Service Facility files By passing parameters to OS2SERV, you can maintain your own set of FixPaks, perhaps on a LAN drive, and allow others to install from that LAN drive. ═══ 4. Features ═══ 1. Archive/Backup paths extracted from previous FixPak service if available. Also checked to make sure they exist since FSERVICE.EXE will die if they are indicated as available when not really there. 2. New Archive/Backup paths created if they do not exist. 3. Backout to previous BacKup or Archive level. 4. Adds additional information to \OS2\INSTALL\SERVICE.LOG on the boot drive about what you have done. 5. Provides a display of existing free disk space when asking you to choose where to place saved files. 6. Prechecks harddisk freespace before running FSERVICE.EXE. ═══ 5. Installing a Fixpak to one or more partitions ═══ Follow these steps to install a FixPak to one or more partitions on your harddisk. When the FixPak Installation window appears and the Install button has been enabled (this can take a few minutes), select one or more products from the "Serviceable Products" window then press the "Install" button to begin. You can use "Advanced" to use SERVICE.EXE rather than FSERVICE.EXE if you prefer. ═══ 6. Backing out a FixPak from one partition ═══ Follow these steps to backout a FixPak from one partition. When the FixPak Installation window appears and the Uninstall button has been enabled (this can take a few minutes), select one or more products from the "Serviceable Products" window then press the "Uninstall" button to begin. You can use "Advanced" to use SERVICE.EXE rather than FSERVICE.EXE if you prefer. ═══ 7. Error recovery ═══ If you experience any of these problems, follow the recovery procedure outlined to get your system back to a normal, working state. ═══ 7.1. Application Interrupted ═══ Something happened during the application of a previous FixPak. You need to complete that installation before starting another. You can use this program to continue (RETRY) the interrupted FixPak apply. The correct program (SERVICE.EXE or FSERVICE.EXE) will be called. If this fails then you need to resolve the problem causing the failure before continuing. ═══ 7.2. Previous FixPak not complete ═══ The previous FixPak completed but there were files deferred until you reboot your system at which time the IBM Locked File Device Driver (IBMCSFLK) would copy the deferred files from the staging area to the correct location on your harddisk. You must reboot before you can attempt any other FixPak services. Shutdown your system and press Ctrl+Alt+Del and let this occur. ═══ 7.3. Syntax error on line n of response file ═══ This is usually caused by not specifying a fully qualified path for the Archive and/or Backup directories. Since this program handles this for you, you should never see this message. The only time it would occur is if you have manually edited the response file before doing a RETRY run or you used the "Advanced" method and did specified a Archive and/or Backup directory incorrectly. ═══ 8. Components of the FixPak Installation window ═══ This is what the OS2SERV window looked like when installing Warp 4 FixPak 7 to my work system. Window Component Component Description View Readme Uses the E editor (E.EXE) to look at README.1ST of the FixPak being installed. View Log Uses the E editor (E.EXE) to look at \OS2\INSTALL\SERVICE.LOG file. This is where all FixPak activity is recorded. About Displays the build version and date information for this program. Status window Keeps you informed of what is currently going on. It will also prompt you when necessary. Serviceable Products window Displays the list of products found on your harddrive(s) that can be serviced by a this FixPak. Select the product or products you want to apply this FixPak to then press "Install" or "Uninstall" button. Advanced check box Select this box to use the SERVICE.EXE GUI rather than run FSERVICE.EXE with a response file. This allows you a little more control over the Fixpak Install or Uninstall process. Replace Newer check box Select this box to automatically replace files on your harddisk which have a later date/time or revision level. Leave unchecked to not replace newer files. (This option is not available yet, waiting on a CSF change to support it.) Install button Disabled until all preliminary work has been done. Checks to make sure you have enough free space on the required drives, builds a response file and calls FSERVICE.EXE. See the README.1St file of each FixPak for harddisk space requirements. Uninstall button Disabled until all preliminary work has been done. Only enabled if there is a Archive/Backout directory that alredy exists from a previous FixPak install on one of the drives where a supported product was found. Builds a response file and calls FSERVICE.EXE. If there is an existing Backout directory then it will backout to that level. If not then it will backout to the Archive directory level. Help button Displays this online INF file via the View command. Exit button Closes the window and exits the program. ═══ 9. Creating the FixPak Source and CSF Source directories ═══ The easiest way to create the FixPak source and CSF source directories is to LOADDSKF each FixPak disk image to a VFDISK (Virtual Floppy Disk) then XCOPY the VFDISK to a partition on your harddisk. VFDISK is available internally from the OS2TOOLS repository. Externally there are several VFDISK-like programs available. In these examples, I: is the VFDISK, F:\FIXPAKS is the root directory where the OS2SERV and CSF code will be placed and XR_W036 is a FixPak we are working with. Follow these steps to create the FixPak directory: 1. LOADDSKF XR_W036.1DK I: /f/y/q 2. XCOPY I:\*.* F:\FIXPAKS\XR_W036\ /h/o/t/s/e/r/v 3. LOADDSKF XR_W036.2DK I: /f/y/q 4. XCOPY I:\*.* F:\FIXPAKS\XR_W036\ /h/o/t/s/e/r/v 5. repeat for remainder of FixPak disks Follow these steps to create the CSF redirected install directory: CSF F.137B build: 1. LOADDSKF CSFBOOT.1DK I: /f/y/q 2. XCOPY I:\*.* F:\FIXPAKS\CSF\ /h/o/t/s/e/r/v 3. LOADDSKF CSFBOOT.2DK I: /f/y/q 4. XCOPY I:\*.* F:\FIXPAKS\CSF\ /h/o/t/s/e/r/v CSF F.138B build: 1. Copy FIXT138B.EXE to the F:\FIXPAKS\CSF directory 2. Enter FIXT138B 3. Delete FIXT138B.EXE This will end up creating a directory structure that looks like this: F:\FIXPAKS\ Holds OS2SERVICE files F:\FIXPAKS\CSF Holds CSF code F:\FIXPAKS\XR_W036 Root of FixPak 36, readmes F:\FIXPAKS\XR_W036\FIX F:\FIXPAKS\XR_W036\FIX\OS2.1 Common files F:\FIXPAKS\XR_W036\FIX\OS2.2 UNI files F:\FIXPAKS\XR_W036\FIX\OS2.3 Warp for Windows (red) files F:\FIXPAKS\XR_W036\FIX\OS2.4 Warp with WINOS2 (blue) files F:\FIXPAKS\XR_W036\FIX\OS2.5 SMP files F:\FIXPAKS\XR_W036\FIX\MPM.6 Multimedia files F:\FIXPAKS\XR_W036\FIX\OS2.7 WINOS2 UNI files F:\FIXPAKS\XR_W036\FIX\OS2.8 ULS/Registry UNI files For a Warp 4 FixPak like 7, the directory structure would be: F:\FIXPAKS\ Holds OS2SERVICE files F:\FIXPAKS\CSF Holds CSF code F:\FIXPAKS\XR_M007 Root of FixPak 7, readmes F:\FIXPAKS\XR_M007\FIX F:\FIXPAKS\XR_M007\FIX\OS2.1 Common files F:\FIXPAKS\XR_M007\FIX\OS2.2 Warp 4 (Merlin) files F:\FIXPAKS\XR_M007\FIX\OS2.3 WSOD files