< Installation instructions for Warp 4 FixPak XR_M004 October 7, 1997 Build level 9.028 This FixPak applies to: CSD Level: XR_4000 Component ID: 5639A6100 Version: 4.00 Type: 0C OS/2 Fix Distribution Personal System Products Austin, Tx (c) Copyright International Business Machines Corporation, 1994, 1996. All rights Reserved. October 7, 1997 - Warp 4 FixPak XR_M004  October 7, 1997 - Warp 4 FixPak XR_M004 CONTENTS Terms and Conditions ............................................. 1 Installation Notes ............................................... 2 Standby mode (Power Management) problems ....................... 2 No files to service ............................................ 2 Previous installation interrupted .............................. 3 Unable to open Archive directory ............................... 3 RC 932 doing CID install of Warp 4 ............................. 3 Windows printer drivers leave a zombie thread running .......... 5 Multimedia no longer selectable ................................ 5 If you have installed FixPak XR_M000 ........................... 6 If you have installed controlled FixPak XR_M001 ................ 6 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) ............ 7 MMPARTS.DLL/USER.EXE popup during install ...................... 7 CSF0212 Archive path is shared between mismatched ... ......... 7 CSF0214 Error opening or creating archive file. ............... 7 CSF0208 No products were found on the target system to service . 8 Printer installation process change ............................ 8 Configuration Installation Distribution ( CID ) ................ 8 Do not use your system once the FixPak installation is started . 8 Post Installation Notes .......................................... 9 SYS3170 installing Lotus SmartSuite 96 ......................... 9 Intermittent pause with IBM Thinkpad 760E/ED/ELD/EL ............ 9 New Function .................................................... 10 New (improved) CHKDSK ........................................... 10 Using the new CHKDSK .......................................... 10 CHKDSK log formatter .......................................... 12 Automated Trap Screen Logging ................................. 13 SUPPRESSPOPUPS ................................................ 13 TRAPLOG ....................................................... 13 TRAPDUMP ...................................................... 14 SYSDUMP ....................................................... 14 New README.DBG .................................................. 15 Corrective Service Facility Installation Diskettes .............. 16 Required CSF level ............................................ 16 Where you can find CSF ........................................ 16 Creating FixPak diskettes ..................................... 17 Residual FixPak files from OS/2 2.11 or Warp 3 .................. 17 Read-Only files ................................................. 18 SYSLEVEL file locations ......................................... 18 Relocated OS/2 file support ..................................... 19 Installation Process ............................................ 21 Before installation ............................................. 21 Method 1: Install from booted OS/2 partition. .................. 21 Contents ii  October 7, 1997 - Warp 4 FixPak XR_M004 Method 2: Boot from Corrective Service Disk 1. ................. 23 Additional Corrective Service Facility information .............. 23 CSD level of SYSLEVEL.OS2 ....................................... 24 FixPak Corrective Service levels and disk layouts ............... 25 Space Utilization ............................................... 33 Recovering FixPak ARCHIVE and BACKUP space .................... 33 Contents iii  October 7, 1997 - Warp 4 FixPak XR_M004 TERMS AND CONDITIONS Important - please read the following terms and conditions. Downloading the Service Fixes included in FixPak XR_M004 for Warp 4 indicates your acceptance of the following terms and conditions: 1. You must be, and agree that you are, a current licensee of OS/2 Warp 4. 2. You may make copies of the OS/2 Service Fixes equal to the number of licensed copies of OS/2 Warp 4 you possess. 3. You may only use the OS/2 Warp 4 Service Fixes included with FixPak XR_M004 for maintenance purposes. 4. All other terms and conditions of your OS/2 Warp 4 license agreements apply to the Service Fixes; however, this does not extend any warranty and/or services, including but not limited to the "Initial Installation" period, outlined in such agreements. Terms and Conditions 1  October 7, 1997 - Warp 4 FixPak XR_M004 INSTALLATION NOTES STANDBY MODE (POWER MANAGEMENT) PROBLEMS If your system uses Power Management, please check it after Fixpak 4 is installed. Once Standby mode is entered, you move the mouse (for instance) to return from Standby mode. The display will come on and the harddrive will spin up but as soon as you stop moving the mouse it will return to Standby mode. The only way to recover is to Ctrl+Alt+Del or power the system off and on again. This will be fixed in the next Warp 4 Fixpak. The work around is to disable Power Management. You do this by opening the Properties notebook for the Power object in the System Setup folder and change Power Management from On to Off. 1. Open the OS/2 System folder 2. Open the System Setup folder 3. Click mouse button 2 (right mouse button) on the Power object 4. Select Porperties 5. Click the "Off" radio button 6. Close the Properties notebook NO FILES TO SERVICE If you see a "No files to service" message while applying this FixPak, there is probably a mismatch between the data in \OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this Fixpak. Compare the data for the OS/2 Base Operating System from the SYSLEVEL command output with the same values listed at the end of this document in the "FixPak Corrective Service levels and disk layouts" section. They must be identical. If these values are correct, check for the following files on any OS/2 boot drive in the \OS2\INSTALL directory. LOGF0000.OS2 LOGSTART.OS2 LOGARCH.OS2 Check for the following files in your MMOS2\INSTALL directory. Installation Notes 2  October 7, 1997 - Warp 4 FixPak XR_M004 LOGF0000.MPM LOGSTART.MPM LOGARCH.MPM Also check for the following file: C:\CSF_SEL.000 If these files exist, rename them and try the FixPak installation again. Delete the renamed files after the Fixpak has been applied. PREVIOUS INSTALLATION INTERRUPTED If you get a message that the previous installation of a FixPak was interrupted (whether true or not), check for the following files and directory on all drives: Files: FIXSTART IBMCSFLK.LST IBMCSFLK.CSF CSF_* Directory: IBMCSFLK If any exist, rename them and try the FixPak installation again. Delete the renamed files after the Fixpak has been applied. UNABLE TO OPEN ARCHIVE DIRECTORY If you get a message about problems with the Archive directory (for example, cannot find or unable to open), then the most probable cause is that you applied a previous FixPak and have since deleted the FixPak ARCHIVE or BACKUP directory. To recover from this, follow the "No files to service" and "Previous installation interrupted" steps listed above. RC 932 DOING CID INSTALL OF WARP 4 If you get a RC (Return Code) 932 while doing a CID install of Warp 4 and you are using RSPINST.EXE from Fixpak 3 or later, you will need to do the following. Installation Notes 3  October 7, 1997 - Warp 4 FixPak XR_M004 1. Create a temporary work directory somewhere on your harddrive. assume it's c:\tempwork 2. Locate the section called "FixPak Corrective Service levels and disk layouts". 3. Locate CHKDSK.SYS, CHKDSK32.DLL, CHKDSK32.EXE and UHPFS.DLL and record what disks they are found on. Note: For Fixpak 3, they are on disks 12, 8, 12 and 9 respectively. This will change for later Fixpaks. 4. Place Fixpak disk 12 in A: and enter unpack a:\fix\os2.1\chkdsk.sy_ c:\tempwork 5. Place Fixpak disk 8 in A: and enter unpack a:\fix\os2.1\chkdsk32.dl_ c:\tempwork 6. Place Fixpak disk 12 in A: and enter unpack a:\fix\os2.1\chkdsk32.ex_ c:\tempwork 7. Place Fixpak disk 9 in A: and enter unpack a:\fix\os2.1\uhpfs.dl_ c:\tempwork 8. Make backup copies of CHKDSK.SYS, CHKDSK32.DLL and UHPFS.DLL from the DISK_3 directory of your CID tree. 9. Copy CHKDSK.SYS from c:\tempwork to the DISK_3 directory of your CID tree 10. Copy CHKDSK32.DLL from c:\tempwork to the DISK_3 directory of your CID tree 11. Copy UHPFS.DLL from c:\tempwork to the DISK_3 directory of your CID tree 12. Make a backup copy of the BUNDLE file on DISK_0 13. Copy DISK_0\BUNDLE c:\tempwork 14. Copy PACK2.EXE to c:\tempwork. If you don't have this file you can get it using your Web browser from ftp://ps.software.ibm.com/ps/products/os2/fixes/v4warp 15. PACK2 CHKDSK32.EXE bundle /H:\OS2\CHKDSK32.EXE /A Installation Notes 4  October 7, 1997 - Warp 4 FixPak XR_M004 Note: This adds CHKDSK32.EXE to the bundle file. Enter "unpack bundle /show" to verify it's really there. 16. Copy the updated BUNDLE back to the DISK_0 directory 17. Delete the c:\tempwork directory and files. 18. Do the CID install WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING A problem occurs with some Windows printer drivers where a zombie thread is left running after the program that loaded it is exited. This does not occur when the program is run from a Seamless instance of PROGMAN or from a Full Screen session because when these are exited the whole WINOS2 Subsystem is exited. This problem has been reported for the Adobe and Hewlett Packard Windows printer drivers. To correct this problem for people running with these drivers ONLY who have experienced symptoms such as: Ž exiting a program running seamlessly after printing or Ž setting up a printer and seeing the icon not being unhatched and/or Ž not being able to start another copy of the program Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot* section: Ž backgroundtasks=run_enum.exe,hpfbkg02.exe then restart WINOS2. Note: There may be other drivers that have the same problem. If you experiences a similar problem with other drivers, please report it so the correct SYSTEM.INI entry can be determined. MULTIMEDIA NO LONGER SELECTABLE IBM Multimedia Presentation Manager/2 (MPM) is now fully integrated into the base OS/2. As part of this change, the \MMOS2\INSTALL\SYSLEVEL.MPM file has been deleted. This means you will no longer see it as a selectable entry in the Serviceable Products window when using the A:SERVICE method of installation. Installation Notes 5  October 7, 1997 - Warp 4 FixPak XR_M004 IF YOU HAVE INSTALLED FIXPAK XR_M000 If you have installed Warp 4 FixPak XR_M000, three files were updated that are not in FixPak XR_M002 and need to be backed out to the Warp 4 GA level. They are: 12-13-96 10:35a 10120 0 \MMOS2\MPPM.EXE 12-05-96 5:12p 34645 0 \OS2\BOOT\KBDBASE.SYS 12-05-96 5:39p 53161 0 \OS2\MDOS\VKBD.SYS The uplevel MPPM.EXE causes the Media Player to fail. The uplevel KBDBASE.SYS results in a local TELNET session not having a keyboard unless the TELNET session on the target system has the focus. The uplevel VKBD.SYS causes NumLock to come without pressing the NumLock key. To fix these problems you can either back out the entire FixPak (VIEW the README.INF file on the first FixPak disk for instructions) or back out just these three files as follows: 1. Rename x:\MMOS2\MPPM.EXE to MPPM.000 2. Rename x:\OS2\BOOT\KBDBASE.SYS to KBDBASE.000 3. Rename x:\OS2\MDOS\VKBD.SYS to VKBD.000 4. Change to your FixPak Archive directory. 5. Use the UNPACK command to restore the saved files to your Warp 4 boot drive UNPACK MPPM.EX_ x:\MMOS2 UNPACK KBDBASE.SY_ x:\OS2\BOOT UNPACK VKBD.SY_ x:\OS2\MDOS 6. Shutdown and reboot your system. Note: x: is your Warp 4 boot drive. IF YOU HAVE INSTALLED CONTROLLED FIXPAK XR_M001 If you have installed the controlled version of Warp 4 FixPak XR_M001, one file was updated that is not in the public FixPak XR_M002 and needs to be backed out to the Warp 4 GA level. It is: 12-05-96 5:39p 53161 0 \OS2\MDOS\VKBD.SYS Installation Notes 6  October 7, 1997 - Warp 4 FixPak XR_M004 The uplevel VKBD.SYS causes NumLock to come without pressing the NumLock key. To fix this problem you can either back out the entire FixPak (VIEW the README.INF file on the first FixPak disk for instructions) or back out just this file as follows: 1. Rename x:\OS2\MDOS\VKBD.SYS to VKBD.000 2. Change to your FixPak Archive directory. 3. Use the UNPACK command to restore the saved file to your Warp 4 boot drive UNPACK VKBD.SY_ x:\OS2\MDOS 4. Shutdown and reboot your system. Note: x: is your Warp 4 boot drive. APAR JR09494 (TRAP EXITING WINOS2 WITH MWAVE AUDIO) The fix for APAR JR09434 (trap exiting winos2 with MWAVE audio) requires a new MWAVEVDD.SYS dated 11/96 or later. This file is available from the IBM PC Company web site at http://www.pc.ibm.com. MMPARTS.DLL/USER.EXE POPUP DURING INSTALL If you get a popup about MMPARTS.DLL or USER.EXE during install, reply "Yes" to replace it. *====================================================================== CSF0212 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED ... The Archive path you specified (or was previously specified) contains files from a different release of OS/2. You need to specify a different Archive path. CSF0214 ERROR OPENING OR CREATING ARCHIVE FILE. Also CSF0215, CSF0216, CSF0217 and CSF0249. Typically this means the Fixpak Archive directory has been deleted but the files that point to it still exist. You need to delete the LOGF000.OS2 and LOGSTART.OS2 files from your OS2/INSTALL directory. LOGSTART.OS2 has the R/O attribute set and it needs to be reset before the file can be deleted. Installation Notes 7  October 7, 1997 - Warp 4 FixPak XR_M004 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET SYSTEM TO SERVICE This means no SYSLEVEL files was found that had a CSD Level, COMPID, Version and Type that matched any of the SYSLEVEL files supported by this FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2 in the OS2/INSTALL directory on your boot drive. Compare this data with the data contained in the README.1ST file on FixPak disk 1. To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2 and copy SYSLEVEL.OS2 from your Warp 4 installation DISK 1. PRINTER INSTALLATION PROCESS CHANGE If you install a new printer by clicking MB2 on the Printer icon in the templates folder then clicking on Install, the printer object will now be created in the Printer folder, not on the Desktop. CONFIGURATION INSTALLATION DISTRIBUTION ( CID ) Read the README.CID on Disk # 1 for an example of how to set up a response file to do a CID install. DO NOT USE YOUR SYSTEM ONCE THE FIXPAK INSTALLATION IS STARTED Once you begin a FixPak installation, do not try to use your system for any other purpose. Doing so may yield unexpected problems which can cause the FixPak installation to fail. Installation Notes 8  October 7, 1997 - Warp 4 FixPak XR_M004 POST INSTALLATION NOTES SYS3170 INSTALLING LOTUS SMARTSUITE 96 A problem was discovered when attempting to install Lotus SmartSuite 96 with a early version of the Matrox video driver. A SYS3170 occurs after pressing the button to start copying the files to the hard disk. The problem does not occur with the current Matrox driver available on the Web at http://www.matrox.com/mgaweb/drivers/ftp_os2.htm A work around that does not involve downloading files from the web, is to switch your display driver to VGA during the install and after it has completed, restore the Matrox driver. INTERMITTENT PAUSE WITH IBM THINKPAD 760E/ED/ELD/EL If you have an IBM Thinkpad 760E/ED/ELD/EL that exhibits sluggish harddisk behavior (pausing intermittently with hard drive light on) after this FixPak has been applied, add the /!BM parameter to the BASEDEV=IBM1S506.ADD statement (if present) in your CONFIG.SYS. This will disable the Bus Mastering function whose default has been changed from OFF to ON. If your CONFIG.SYS has the statement BASEDEV=PIIXIDE.ADD you must remark out the statement by inserting REM as the first characters on the line as shown below. REM BASEDEV=PIIXIDE.ADD BASEDEV=IBM1S506.ADD /A:0 /!BM /U:1 /ATAPI /FORCE Post Installation Notes 9  October 7, 1997 - Warp 4 FixPak XR_M004 NEW FUNCTION It is our policy not to include new function in FixPaks. However, as with any policy there may be exceptions. If any exception occurs in the future, we will communicate them to you in this section of the README.1ST. NEW (IMPROVED) CHKDSK This version of CHKDSK offers significant improvements for High Performance File System (HPFS) drives. CHKDSK now fixes all errors found on HPFS drives in a single pass, operating faster, and with less memory than previous versions. It contains better error detection and correction algorithms, and creates a log file so service personnel can determine what errors it found and how it corrected them. Finally, only the amount of physical memory in your system limits the size of the largest drive CHKDSK can check at boot time (autocheck). Improvements in this version of CHKDSK are for HPFS drives only. No changes occurred to checking File Allocation Table (FAT) drives. This enhanced CHKDSK operates on IBM OS/2 Warp 3.0 and higher, including IBM Warp 4, IBM Warp Server 4 and IBM Warp Server 4 SMP. This new CHKDSK version will not run on version of OS/2 before OS/2 Warp 3.0. USING THE NEW CHKDSK The interface to CHKDSK remains CHKDSK.COM and PMCHKDSK. No changes occurred to the CHKDSK command line parameters or messages. The first time this version of CHKDSK runs on a fast formatted drive, it will report harmless errors. These errors go away once CHKDSK is run with the /F option. Note: OS/2 Warp Install uses fast format. Unlike prior versions of CHKDSK, large drives ( > 8GB) may be autochecked if sufficient memory is available. The amount of memory required can vary between 16MB and 48MB depending on the size of the drive. To enable the autochecking of large drives, the following line must be added to your config.sys: BASEDEV=CHKDSK.SYS This device driver allows CHKDSK to access memory normally reserved for the system during the boot process. Due to this, if CHKDSK has to use this memory: Ž The memory will not be available for the system to use in New Function 10  October 7, 1997 - Warp 4 FixPak XR_M004 completing the boot process Ž Errors may occur later in the boot process. Hence, the chkdsk.sys device driver is smart enough to recognize when CHKDSK has used this reserved memory and will reboot the system automatically after all HPFS drives have been checked. Since the drives were checked before the reboot, CHKDSK will not have to check them after the reboot and the system will boot normally. Note: For those wishing to run unattended: In order to prevent the system from pausing between autocheck and the reboot, we recommend that the statement PAUSEONERROR=NO be in the CONFIG.SYS. When you don't have enough physical (real) memory to autocheck large drives, you must use virtual memory from SWAPPER.DAT. The technique is to check the large drives between the time OS/2 starts and PM begins. To start OS/2, the swap file and device drivers must reside on an unaffected drive. The drives to be checked must not appear in the autocheck list in the IFS statement for HPFS (or HPFS386). This technique involves the following steps: 1. Remove the drive letter of the affected drive(s) from the autocheck list in the IFS statement for HPFS (or HPFS386). 2. If you are using HPFS, add /QUIET to the IFS statement for HPFS. 3. If you are using HPFS386, add POPUPERRORRS=NO to the HPFS386.INI file. 4. Add a CALL statement to your config.sys. This CALL statement will call CHKDSK.COM, and will tell it what drive to check. This CALL statement must appear after the LIBPATH=, SET PATH=, and SET DPATH= statements, but before any other CALL statements in your CONFIG.SYS file. Calls to CHKDSK in STARTUP.CMD are not necessary, when using this method or the base device driver (chkdsk.sys) method. Example: The computer boots from drive C (moderate HPFS or FAT sized drive). Drive D (large HPFS) requires more RAM to check than installed in the machine. New Function 11  October 7, 1997 - Warp 4 FixPak XR_M004 Original IFS statement: IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:CD New IFS statement: IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:C /QUIET The CALL statement to use is: CALL=C:\OS2\CHKDSK.COM D: /C The /C option tells CHKDSK to check the drive only if it is "dirty" and it needs checking. If you need to boot from diskettes to check an HPFS drive, you must have the following files on the diskette you wish to run CHKDSK from: CHKDSK.COM CHKDSK32.DLL UHPFS.DLL The BOOTDISK.EXE program has been updated to create new utility diskettes with the proper files. CHKDSK LOG FORMATTER CHKDSK creates a binary service log file (chkdsk.log) on the root of the drive being checked during autocheck or whenever the /F option is invoked. The previous log file is saved as chkdsk.old. A formatter for this log file can be found at: ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe This is a self extracting ZIP file. Place it in a directory in your path and enter CHKLOGPK. This will create the following files: message.txt msghdr.txt pmchklog.exe range.txt readme They should all have a date of 05/14/97 or later (May 14, 1997). New Function 12  October 7, 1997 - Warp 4 FixPak XR_M004 This is a tool used by OS/2 service to format and view the new CHKDSK log entries. There is no support for this tool. You are welcome to use it but if you have problems with it or do not understand the output DO NOT contact IBM for assistance as none will be provided. AUTOMATED TRAP SCREEN LOGGING Whenever an application program traps, the trap information is (now) automatically logged in the POPUPLOG.OS2 file. This is a cumulative file that is by default located in the root directory of the bootable partition. Should this file become too large then it may be erased or pruned (reduced in size). The system will automatically re-create it if it does not exist. The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used to control trap screen behavior (see below). SUPPRESSPOPUPS SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior. That is, to disable logging and to have trap screens displayed unless specifically overridden by an application's use of the DosError API. SUPPRESSPOPUPS=x: will disable trap screen display for all processes and will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or partition. If SUPPRESSPOPUPS is omitted then the behavior is as described above under "Automated Trap Screen Logging". TRAPLOG The TRAPLOG command allows dynamic control of trap information logging. The command syntax is: TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS] where: Ž x: specifies that trap information is to be logged in x:\POPUPLOG.OS2, x: being any partition drive letter. Ž NOLOG disables logging of trap information. Ž POPUPS enables the trap information pop-up message (SYS3175). Ž NOPOPUPS disables the trap information pop-up message. New Function 13  October 7, 1997 - Warp 4 FixPak XR_M004 TRAPDUMP The TRAPDUMP command allows the conditions under which a trap will initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak 29, the System Dump setting could only be manipulated from CONFIG.SYS by use of the TRAPDUMP statement. Use of this command should be made under the direction of service personnel. Warning: The initiation of a System Dump causes an immediate termination of the system without any shutdown. No file system shutdown is performed. The system behaves as if a fatal crash has occurred, thus under rare circumstances data can be lost. The command syntax is: TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK] where: Ž ON enables all application and system traps to initiate a System Dump. Ž OFF disables automatic dump initiation. Ž R0 enables only Ring 0 traps to initiate a System Dump. Ž x: specifies the Dump Partition. Ž NOCHECK overrides the system level check for WARP 4.0, since use of this command on a system level prior to FixPak 29 is equivalent to the SYSDUMP command. SYSDUMP The SYSDUMP command forces a System Dump to be initiated, regardless of the TRAPDUMP settings. This command is provided for the use of service personnel to allow Dump Initiation to be automated through use of a command file. Warning: The initiation of a System Dump causes an immediate termination of the system without any shutdown. No file system shutdown is performed. The system behaves as if a fatal crash has occurred thus under rare circumstances data can be lost. The command syntax is: SYSDUMP [/NOPROMPT] New Function 14  October 7, 1997 - Warp 4 FixPak XR_M004 where: Ž NOPROMPT allows the Dump to proceed without the prompt and response to message: "Do you want to force a system dump? (Y/N)" NEW README.DBG This FixPak introduces a new README.DBG file which contains information on debugging OS/2 Warp 3.0 or 4.0. New Function 15  October 7, 1997 - Warp 4 FixPak XR_M004 CORRECTIVE SERVICE FACILITY INSTALLATION DISKETTES REQUIRED CSF LEVEL You must use release level F.133 or later of the OS/2 Corrective Service Facility Diskettes to install this FixPak. Check the BUILD.LVL file on the first CSF disk for the level you are using. If it does not have a BUILD.LVL file then it is older than the F.133 level and should not be used. WHERE YOU CAN FIND CSF The Corrective Service Facility disk images are available in the WKICKR.ZIP file from many places, including, but not limited to, the following: Source How to access CompuServe Subscribers can download from the OS/2 Support Forum (GO OS2SUPPO), in Library 23, IBM FILE. IBM OS/2 BBS Subscribers can download from the Software Download Library. U.S. customers who are not subscribers can call 1-800-547-1283 for information on how to subscribe. Internet(FTP) Anonymous FTP to ftp.software.ibm.com (IP Address 198.17.57.66) in the "/ps/products/os2/fixes" directory. Internet(WWW) Point your Web Browser at ftp://service.boulder.ibm.com/ps/products/os2/fixes PCC BBS Customers can call the IBM Personal Computer Company BBS In Raleigh NC, and download from the public area. You can access this BBS at 1-919-517-0001. AOL America OnLine subscribers can download from the OS/2 Area. Follow the instructions contained in the WKICKR.TXT file to create the Corrective Service Facility disks. Label them (write) as: Corrective Service Facility Installation Diskettes 16  October 7, 1997 - Warp 4 FixPak XR_M004 CSF DISK Diskette 1 (SP DISK 1) CSF DISK Diskette 2 (SP DISK 2) CREATING FIXPAK DISKETTES Use LOADDSKF.EXE to create the diskettes. For each disk image, place a 2MB HD (1.44MB formatted) diskette in A:. Warning: DO NOT use a 1MB (720KB formatted) diskette because you might have problems trying to install this FixPak. For each diskette image in the FixPak, do the following: Enter LOADDSKF XR_M004.?DK A: /F (? can be 1 through 9, A through Z). Label the diskette as FixPak XR_M004 Corrective Service Diskette ? (CSF DISK ?) Note: For diskette images ADK through ZDK, use the numbers 10 through 26. Examples: XR_M004.ADK = 10 XR_M004.FDK = 15 XR_M004.LDK = 21 etc. RESIDUAL FIXPAK FILES FROM OS/2 2.11 OR WARP 3 If the following is true: 1. You upgraded your system from OS/2 2.11 or Warp 3 2. You applied one or more FixPaks to the previous system 3. You HAVE NOT applied a Warp 4 FixPak You will have files and directories left on your harddisk that will cause problems when installing a Warp 4 FixPak. Corrective Service Facility Installation Diskettes 17  October 7, 1997 - Warp 4 FixPak XR_M004 To prevent these problems from occurring, do the following before applying your first Warp 4 FixPak. On your Warp 4 boot drive: Ž Delete \OS2\INSTALL\LOGF0000.OS2 Ž ATTRIB -R \OS2\INSTALL\LOGSTART.OS2 Ž Delete \OS2\INSTALL\LOGSTART.OS2 On the drive where Multimedia Presentation Manager is installed: Note: This can be your Warp 4 boot drive or any other drive on your system. Check the "SET MMBASE=" statement in CONFIG.SYS to determine which drive this is. Ž Delete \MMOS2\INSTALL\LOGF0000.MPM Ž ATTRIB -R \MMOS2\INSTALL\LOGSTART.MPM Ž Delete \MMOS2\INSTALL\LOGSTART.MPM Remove the old Archive and Backup directories and SERVICE.LOG file to recover the space they are using. You should also remove the FixPak Archive and Backup directories left over from your updated OS/2 2.11 or Warp 3 system at this time as well as the \OS2\INSTALL\SERVICE.LOG file. READ-ONLY FILES Some files being updated by this FixPak may have the Read-Only attribute set. If you are using the A:SERVICE method to install this FixPak you will be asked if you want the files replaced. Press the "OK" button. SYSLEVEL FILE LOCATIONS This FixPak will service directories based on the location of a supported SYSLEVEL.OS2 file. Please check your system to make sure extra copies of this file are not located in directories other than: \OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s) If additional copies of these files are found in other locations on your hard disk then CSF will try to service files as follows: For \OS2\INSTALL\SYSLEVEL.OS2 Corrective Service Facility Installation Diskettes 18  October 7, 1997 - Warp 4 FixPak XR_M004 ..\..\ all files in a directory two levels above (toward the root). This should be the root directory of your boot drive. ..\* all files in a directory one level above (toward the root) and all subdirectories below. This should be the OS2 directory and subdirectories. ..\..\VT\ all files in the VT directory under the root directory. ..\..\VT\* all files in all subdirectories under the VT directory. RELOCATED OS/2 FILE SUPPORT If you have moved OS/2 files or directories to a drive other than the one the SYSLEVEL.OS2 file is on, do the following in order to have them serviced: Ž Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the OS\2 Warp 4 partition to be serviced. In this file, place the full path to the directories you want to be serviced. Assuming your boot drive is C: and you installed Multimedia on the D: drive and manually moved WINOS2 support to the E: drive: D:\MMOS2 D:\MMOS2\DLL D:\MMOS2\DSP D:\MMOS2\HELP D:\MMOS2\IMAGES D:\MMOS2\INETTEMP D:\MMOS2\INSTALL D:\MMOS2\MACROS D:\MMOS2\MOVIES D:\MMOS2\SOUNDS D:\MMOS2\SOUNDS\DESKTOP D:\MMOS2\SOUNDS\GARDEN D:\MMOS2\SOUNDS\OCEAN D:\MMOS2\SOUNDS\SPACE E:\OS2\MDOS\WINOS2 E:\OS2\MDOS\WINOS2\SYSTEM E:\OS2\MDOS\WINOS2\TEMP Note: Leave this file for any future OS/2 Warp 4 FixPaks you might apply. The easy way to create this file is to use the DIR command with the /A:D /S /B parameters and pipe the output to a file. Corrective Service Facility Installation Diskettes 19  October 7, 1997 - Warp 4 FixPak XR_M004 dir d:\mmos2 /a:d /s /b > anyfile Then copy that data into the USERDIRS.OS2 file. With CSF release level F.137B or later, you can use wildcards, so your USERDIRS.OS2 file would be much simpler and would look like: D:\MMOS2\* E:\OS2\MDOS\WINOS2\* Corrective Service Facility Installation Diskettes 20  October 7, 1997 - Warp 4 FixPak XR_M004 INSTALLATION PROCESS BEFORE INSTALLATION Before installing any FixPak, run CHKDSK /F against all drives on your system to correct any file system errors that might be present. You cannot do this while OS/2 is active. You must shut down and run CHKDSK by one of the following methods: Ž Boot from your Installation, DISK 1 and DISK 2 diskettes. If your file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL on it in your A: drive before issuing the CHKDSK command. Ž Boot from the Utilities disk you created via the "Create Utility Diskettes" icon in the System Setup folder. Ž Boot from a different OS/2 partition. Reboot your system then shutdown all running applications. METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION. This method allows you to select the products (partitions) to be serviced. This is the method you should use if you have more than one OS/2 partition and want to control which one is serviced. Note: You can use a diskette drive other than A: with this method. If your 3.5" diskette drive is B:, use B: where A: is mentioned in the following steps. (this method only). 1. Insert CSF DISK Diskette 1 in drive A. 2. Open an OS/2 window or full-screen session. 3. Type A:\SERVICE and press the Enter key. Note: You could also use the "Drives" object for A: and double click on the "SERVICE.EXE" Icon to start the install. 4. Follow the displayed instructions. When prompted to insert Corrective Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_M004 Corrective Service Diskette 1 in drive A. Repeat for the rest of the FixPak disks when requested to do so. Note: It can take a considerable length of time for the Corrective Service Facility to scan your hard disk for serviceable files. In some cases, it has taken as long as 40 minutes. Please be patient and allow this process to complete. 5. If this is the first OS/2 Warp FixPak you have applied to this system, then enter the path to the ARCHIVE directory where a copy Installation Process 21  October 7, 1997 - Warp 4 FixPak XR_M004 of replaced files will be stored (for example, D:\ARCHIVE). Note: This ARCHIVE directory is not related to the ARCHIVES directory built into OS/2 Warp 3.0. Please specify a different path. You must specify a different ARCHIVE directory for each product to be serviced. If this is not the first OS/2 Warp FixPak, then enter the path to the BACKUP directory where a copy of replaced files will be stored (for example, D:\BACKUP). Note: You must specify a different BACKUP directory for each product to be serviced. For either case, make sure there is sufficient space available on the drive you specify. Even though these files are kept in compressed (PACK2) format, they require between 7 and 12 MB of disk space. 6. Click on "OK". 7. You will see an "Application in use" dialog box showing a list of locked files that cannot be serviced while the system is running. You are given two choices - to Continue or Reboot. Select Continue. 8. During the installation process you might see messages about Archiving, Updating and Deferring service. Ž Archiving saves a compressed copy of the original file in the ARCHIVE or BACKUP path you specified. Ž Updating means the original files are replaced with the new ones from this FixPak. Ž Deferring service means the file to be updated is currently in use by the system and cannot be updated. The new files from the FixPak are placed in unpacked format in the \IBMCSFLK\FIX directory on the drive with the most free space. They are processed by the locked file device driver during reboot after you shut down the system. 9. Select NO for a redisplay of the "Product List" after the first part of the FixPak application process has completed if this message is displayed. 10. Click Cancel and Exit to close the Corrective Service Facility window if necessary. 11. Shut down and reboot your system. You will see the following during reboot of the system if you applied service to the OS/2 partition you were booted from. The locked file driver is loaded. Processing locked files Processing complete Installation Process 22  October 7, 1997 - Warp 4 FixPak XR_M004 The system will do one automatic reboot after the Locked File Device Driver has completed. METHOD 2: BOOT FROM CORRECTIVE SERVICE DISK 1. This method does not prompt the user for any information. No interaction with the user takes place other than requests to put the next diskette in drive A. All serviceable partitions on your system will be updated automatically. Be especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using this method because they can cause CSF to apply service to directories you do not want serviced. 1. Shut down your OS/2 system. 2. Insert CSF DISK Diskette 1 in drive A. 3. Press Ctrl+Alt+Del to boot the disk in drive A. Service will be applied to ALL partitions that contain a version of OS/2 that is supported by this FixPak. See the section "FixPak Corrective Service levels and disk layouts" for the CSD levels this FixPak applies to. Note: It can take a considerable length of time for the Corrective Service Facility to scan your hard disk for serviceable files. Please be patient and allow this process to complete. Note: You can edit the RESPONSE.FIL on CSF Disk 1 to control some of the actions taken by FSERVICE.EXE while applying a FixPak. Use the VIEW command to look at the file README.INF on the first CSF disk for more information on this. ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION Additional information on the Corrective Service Facility, like how to backout a FixPak, is available from the README.INF file on the first Corrective Service Facility disk. To view this file, place CSF disk 1 in drive A and enter VIEW A:\README.INF. Installation Process 23  October 7, 1997 - Warp 4 FixPak XR_M004 CSD LEVEL OF SYSLEVEL.OS2 The Current CSD level for the "IBM OS/2 Base Operating System" will not be changed by installation of this FixPak even though the SERVICE.LOG file indicates it will. This FixPak is not a Service Level change. It upgrades the existing service level (XR_4000); therefore the SYSLEVEL is not changed. All fix information is recorded in the SERVICE.LOG file. Look at the file \OS2\INSTALL\SERVICE.LOG on your boot drive for information relating to the installation of this (or any) FixPak on your system. To see the current level and other related information use the SYSLEVEL command. Use the VER /R command to see the current revision of OS/2 installed. The response will look like the following for this FixPak: The Operating System/2 Version is 4.00 Revision 9.028 The first page of this document has a line that looks like: Build Level: n.nnn That is the number you should see for this FixPak when you issue the VER /R command. CSD level of SYSLEVEL.OS2 24  October 7, 1997 - Warp 4 FixPak XR_M004 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS Build Level: 9.028 Product location on CSD: A:\FIX\OS2.1 Product name: "IBM OS/2 Base Operating System" Standard Edition 4.00 Fixpak name: XR_M004_ (Country = Generic) Pre-requisite CSD Level: XR_4000_ System Id: 1000 Component Id: 5639A6100 Archive is ON for this product. _____________________________________________________________ Default directories: ..\..\ ..\* ..\..\VT ..\..\VT\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size ------------ ------------ ----- -------- ----- ------- AHA152X.ADD AHA152X.AD_ 11 08/18/97 18:54 44208 AHA164X.ADD AHA164X.AD_ 12 08/18/97 18:53 20022 AHA6360.SNP AHA6360.SN_ 11 08/18/97 19:45 27395 AIC7770.ADD AIC7770.AD_ 10 08/18/97 18:55 42558 AIC7870.ADD AIC7870.AD_ 11 04/10/97 16:52 39870 AIC7870.SNP AIC7870.SN_ 12 08/18/97 19:47 9104 APM.SYS APM.SY_ 12 08/18/97 18:43 9922 APMDAEMN.EXE APMDAEMN.EX_ 12 08/18/97 20:25 2733 ART.DLL ART.DL_ 7 06/17/97 10:15 202952 ART.HLP ART.HL_ 12 04/18/97 16:16 11980 ARTADMIN.EXE ARTADMIN.EX_ 10 06/17/97 10:15 78693 ARTCHRON.EXE ARTCHRON.EX_ 11 07/25/97 10:01 58994 ARTFI.EXE ARTFI.EX_ 11 06/17/97 10:15 61482 ARTFIR.DLL ARTFIR.DL_ 12 04/18/97 16:16 30614 ARTINET.DLL ARTINET.DL_ 10 06/17/97 10:15 66252 ARTR.DLL ARTR.DL_ 10 04/18/97 16:16 80629 ARTREG.EXE ARTREG.EX_ 10 06/17/97 10:15 66193 ARTREGR.DLL ARTREGR.DL_ 12 04/18/97 16:16 38138 ARTSTART.DLL ARTSTART.DL_ 12 11/12/96 13:43 17419 ASIACOL.DLL ASIACOL.DL_ 6 09/03/97 22:19 158732 BLDLEVEL.EXE BLDLEVEL.EX_ 12 09/07/97 22:55 21523 BOOTDISK.EXE BOOTDISK.EX_ 11 08/14/97 09:05 61453 BOOTDISK.HLP BOOTDISK.HL_ 12 08/14/97 09:05 10892 BSAUDIO.SNP BSAUDIO.SN_ 12 08/18/97 19:49 5756 BTSCSI.ADD BTSCSI.AD_ 12 08/18/97 18:59 26569 BVSCALLS.DLL BVSCALLS.DL_ 12 11/07/96 20:54 512 FixPak Corrective Service levels and disk layouts 25  October 7, 1997 - Warp 4 FixPak XR_M004 CDFS.IFS CDFS.IF_ 11 09/13/97 17:23 45166 CDROM.TBL CDROM.TB_ 12 11/12/96 13:38 4365 CHKDSK.COM CHKDSK.CO_ 10 09/07/97 22:50 70208 CHKDSK.SYS CHKDSK.SY_ 12 06/16/97 14:37 747 CHKDSK32.DLL CHKDSK32.DL_ 8 07/25/97 11:55 121383 CHKDSK32.EXE CHKDSK32.EX_ 12 07/25/97 11:45 6417 CLOCK01.SYS CLOCK01.SY_ 12 08/18/97 20:05 4160 CLOCK02.SYS CLOCK02.SY_ 12 08/18/97 20:05 4040 CMD.EXE CMD.EX_ 9 09/07/97 22:51 74680 CMD640X.ADD CMD640X.AD_ 11 08/18/97 19:01 36038 CMDATAPI.FLT CMDATAPI.FL_ 12 08/18/97 19:01 21724 COM.SYS COM.SY_ 12 04/11/97 12:26 18751 COMMAND.COM COMMAND.CO_ 11 09/07/97 22:50 53375 COUR.OFM COUR.OF_ 12 04/30/97 11:59 4237 COUR.PFB COUR.PF_ 9 04/30/97 11:59 62921 COUR.PFM COU1.PF_ 12 04/30/97 11:59 674 COURB.OFM COURB.OF_ 12 04/30/97 11:59 4245 COURB.PFB COURB.PF_ 9 04/30/97 11:59 62399 COURB.PFM COUR1.PF_ 12 04/30/97 11:59 679 COURBI.OFM COURBI.OF_ 12 04/30/97 11:59 4259 COURBI.PFB COURBI.PF_ 9 04/30/97 11:59 64511 COURBI.PFM COURB1.PF_ 12 04/30/97 11:59 685 COURI.OFM COURI.OF_ 12 04/30/97 11:59 4252 COURI.PFB COURI.PF_ 9 04/30/97 11:59 65056 COURI.PFM COUR2.PF_ 12 04/30/97 11:59 681 CREX.MSG CREX.MS_ 12 09/19/96 15:44 2865 CREXUTIL.DLL CREXUTIL.DL_ 11 06/11/97 00:34 29689 CREXX.DLL CREXX.DL_ 8 06/11/97 00:34 266015 DETNE2.SYS DETNE2.SY_ 12 08/18/97 18:42 5658 DF_DEB.EXE DF_DEB.EX_ 9 08/14/97 12:56 150579 DF_RET.EXE DF_RET.EX_ 9 08/14/97 18:09 149581 DICTATE.EXE DICTATE.EX_ 10 04/01/97 15:36 51523 DICTDLL.DLL DICTDLL.DL_ 11 07/23/97 11:57 51179 DISPLAY.DLL DISPLAY.DL_ 11 07/30/97 16:06 46574 DIVE.DLL DIVE.DL_ 10 07/23/97 16:41 69640 DMQSPROF.DLL DMQSPROF.DL_ 11 07/30/97 16:27 43533 DOSCALL1.DLL DOSCALL1.DL_ 8 09/07/97 22:48 124228 DOSCALL1.SYM DOSCALL1.SY_ 11 09/07/97 22:48 41540 DOSCALL1.TDF DOSCALL1.TD_ 12 09/07/97 22:48 2312 DOSKRNL DOSKRNL.___ 12 09/13/97 17:22 30553 DRVMAP.INF DRVMAP.IN_ 12 04/03/97 13:54 12986 DSPINSTL.EXE DSPINSTL.EX_ 8 07/25/97 11:31 117832 E.EXE E.EX_ 10 07/23/97 20:58 61719 EAUTIL.EXE EAUTIL.EX_ 11 09/07/97 22:51 37984 ENGINE.EXE ENGINE.EX_ 4 07/23/97 11:39 440424 EPM.EXE EPM.EX_ 12 11/08/96 12:32 19684 ERLOGGER.EXE ERLOGGER.EX_ 11 09/18/97 00:31 34320 ERRLOG.DLL ERRLOG.DL_ 9 09/18/97 00:31 72594 FD16-700.ADD FD16-700.AD_ 12 08/18/97 18:57 34152 FD7000EX.ADD FD7000EX.AD_ 12 08/18/97 18:57 20758 FD8XX.ADD FD8XX.AD_ 12 08/18/97 18:58 29954 FixPak Corrective Service levels and disk layouts 26  October 7, 1997 - Warp 4 FixPak XR_M004 FDISK.COM FDISK.CO_ 10 09/07/97 22:56 110520 FFST.DLL FFST.DL_ 12 04/03/97 19:03 11425 FFSTCONF.EXE FFSTCONF.EX_ 9 09/18/97 00:39 68669 FFSTPCT.EXE FFSTPCT.EX_ 9 09/18/97 00:39 69583 FILT.DLL FILT.DL_ 12 06/16/97 13:37 22864 FORMAT.COM FORMAT.CO_ 11 09/07/97 22:52 69408 FSFILTER.SYS FSFILTER.SY_ 12 09/13/97 17:25 12988 GDI.EXE GDI.EX_ 7 08/22/97 17:14 225312 GRADD.SYS GRADD.SY_ 12 11/06/96 11:47 1259 GRE2VMAN.DLL GRE2VMAN.DL_ 12 07/30/97 16:42 16230 HELPMGR.DLL HELPMGR.DL_ 6 07/23/97 17:53 249623 HELPMSG.EXE HELPMSG.EX_ 11 09/07/97 22:52 36256 HELV.OFM HELV.OF_ 12 07/23/97 11:03 4873 HELV.PFB HELV.PF_ 10 04/30/97 11:59 58156 HELV.PFM HEL1.PF_ 12 04/30/97 11:59 1100 HELVB.OFM HELVB.OF_ 12 07/23/97 11:03 4857 HELVB.PFB HELVB.PF_ 10 04/30/97 11:59 59821 HELVB.PFM HELV1.PF_ 12 04/30/97 11:59 1089 HELVBI.OFM HELVBI.OF_ 12 07/23/97 11:03 4859 HELVBI.PFB HELVBI.PF_ 9 04/30/97 11:59 61860 HELVBI.PFM HELVB1.PF_ 12 04/30/97 11:59 1087 HELVI.OFM HELVI.OF_ 12 07/23/97 11:03 4844 HELVI.PFB HELVI.PF_ 9 04/30/97 11:59 61367 HELVI.PFM HELV2.PF_ 12 04/30/97 11:59 1079 HPFS.IFS HPFS.IF_ 9 07/25/97 11:41 141378 IBM16AFS.EXE IBM16AFS.EX_ 12 08/18/97 18:58 3177 IBM1FLPY.ADD IBM1FLPY.AD_ 11 08/18/97 18:49 35318 IBM1S506.ADD IBM1S506.AD_ 11 08/18/97 19:13 65272 IBM2AMB1.SYS IBM2AMB1.SY_ 12 08/18/97 19:24 12453 IBM2AST1.SYS IBM2AST1.SY_ 12 08/18/97 19:24 10047 IBM2CAD1.SYS IBM2CAD1.SY_ 12 08/18/97 19:26 12495 IBM2CMQ1.SYS IBM2CMQ1.SY_ 12 08/18/97 19:24 10101 IBM2FLPY.ADD IBM2FLPY.AD_ 12 08/18/97 18:49 14420 IBM2MAT1.SYS IBM2MAT1.SY_ 12 08/18/97 19:25 10083 IBM2NCR1.SYS IBM2NCR1.SY_ 12 08/18/97 19:25 10063 IBM2NEC1.SYS IBM2NEC1.SY_ 12 08/18/97 19:25 10063 IBM2SCSI.ADD IBM2SCSI.AD_ 12 08/18/97 18:50 33161 IBM2SS01.SYS IBM2SS01.SY_ 12 08/18/97 20:18 27087 IBM2SS02.SYS IBM2SS02.SY_ 12 08/18/97 20:18 22835 IBM2TOS1.SYS IBM2TOS1.SY_ 12 08/18/97 19:24 10054 IBM2ZEN1.SYS IBM2ZEN1.SY_ 12 08/18/97 19:23 10047 IBM2ZOS1.SYS IBM2ZOS1.SY_ 12 08/18/97 19:25 10079 IBM4612.SYS IBM4612.SY_ 12 05/01/97 11:43 10180 IBMIDECD.FLT IBMIDECD.FL_ 12 08/18/97 19:14 23900 IBMKBD.SYS IBMKBD.SY_ 12 11/14/96 10:47 7770 ICMEMCDD.SYS ICMEMCDD.SY_ 12 08/18/97 19:28 13932 ICMEMFMT.EXE ICMEMFMT.EX_ 11 08/18/97 19:29 50932 ICMEMMTD.SYS ICMEMMTD.SY_ 12 08/18/97 19:29 7788 INSTALL.EXE INSTALL.EX_ 5 08/19/97 15:52 382690 INST_DOS.EXE INST_DOS.EX_ 11 08/13/97 18:07 36522 IPSRAID.ADD IPSRAID.AD_ 12 06/28/97 11:01 19894 FixPak Corrective Service levels and disk layouts 27  October 7, 1997 - Warp 4 FixPak XR_M004 ISGDI2VM.DRV ISGDI2VM.DR_ 11 07/30/97 16:38 86000 KBDBASE.SYS KBDBASE.SY_ 12 07/25/97 16:15 34133 KERNEL.SDF KERNEL.SD_ 11 11/07/96 21:11 467330 KERNELD.SDF KERNELD.SD_ 11 11/07/96 21:12 468657 KEYBOARD.DCP KEYBOARD.DC_ 12 09/04/97 10:50 275644 LIBAUX.DLL LIBAUX.DL_ 11 09/19/96 15:46 47104 LIBC.MSG LIBC.MS_ 12 09/03/97 22:19 9590 LIBCM.DLL LIBCM.DL_ 7 08/29/97 16:17 210916 LIBCN.DLL LIBCN.DL_ 10 08/29/97 16:17 57340 LIBCREG.MSG LIBCREG.MS_ 12 09/03/97 22:19 760 LIBCS.DLL LIBCS.DL_ 7 08/29/97 16:17 192386 LIBTK.DLL LIBTK.DL_ 8 09/19/96 15:47 147002 LIBUNI.DLL LIBUNI.DL_ 10 09/04/97 10:48 80138 LMS206.ADD LMS206.AD_ 12 08/18/97 19:15 38706 LOCALE.DLL LOCALE.DL_ 10 09/04/97 10:49 67032 MIGRATE.EXE MIGRATE.EX_ 8 07/25/97 11:31 118284 MINXOBJ.DLL MINXOBJ.DL_ 11 07/23/97 20:01 31746 MIRRORS.DLL MIRRORS.DL_ 5 09/19/96 15:53 444744 MITFX001.ADD MITFX001.AD_ 12 08/18/97 19:09 20492 MMODPTS.DLL MMODPTS.DL_ 4 07/23/97 16:49 186716 MMPARTS.DLL MMPARTS.DL_ 1 07/24/97 10:23 1532318 MMPM.DLL MMPM.DL_ 5 06/16/97 13:46 430753 MOUSE.SYS MOUSE.SY_ 12 08/18/97 19:15 19587 NAMECSSP.DLL NAMECSSP.DL_ 10 09/03/97 22:02 61155 NAMEDSP.DLL NAMEDSP.DL_ 8 09/03/97 22:00 123411 NAMEFT.DLL NAMEFT.DL_ 10 09/03/97 22:04 66306 NAMEFW.DLL NAMEFW.DL_ 9 09/03/97 22:00 72312 NAMEINFO.DLL NAMEINFO.DL_ 11 09/03/97 22:03 47941 NAMEINI.DLL NAMEINI.DL_ 10 09/03/97 22:03 59011 NAMEOSP.DLL NAMEOSP.DL_ 10 09/03/97 22:02 52725 NAMEREXX.DLL NAMEREXX.DL_ 8 09/03/97 22:04 97811 NAMEREXX.MSG NAMEREXX.MS_ 12 09/03/97 22:04 4257 OREXUTIL.DLL ORXUTIL2.DL_ 11 06/06/97 13:17 28885 OS2ASPI.DMD OS2ASPI.DM_ 12 08/18/97 18:47 11096 OS2CDROM.DMD OS2CDROM.DM_ 12 08/18/97 19:06 27356 OS2CHAR.TDF OS2CHAR.TD_ 12 09/07/97 22:48 13194 OS2DASD.DMD OS2DASD.DM_ 12 08/18/97 18:46 35434 OS2DUMP OS2DUMP.___ 12 09/13/97 17:19 17335 OS2K386.EXE OS2K386.EX_ 9 08/22/97 17:15 80274 OS2KRNL OS2KRNL.___ 3 09/13/97 17:20 599441 OS2KRNL.TDF OS2KRNL.TD_ 12 09/13/97 17:20 13992 OS2KRNLD.SYM OS2KRNLD.SY_ 8 09/13/97 17:21 180628 OS2KRNLR.SYM OS2KRNLR.SY_ 8 09/13/97 17:20 163348 OS2LDR OS2LDR.___ 12 07/29/97 11:07 33280 OS2LDR.MSG OS2LDR.MS_ 12 07/25/97 10:13 8368 OS2NS.EXE OS2NS.EX_ 11 09/03/97 22:03 44964 OS2SCSI.DMD OS2SCSI.DM_ 12 08/18/97 18:46 11614 OSO001.MSG OSO001.MS_ 10 07/28/97 16:31 178141 OSO001H.MSG OSO001H.MS_ 9 07/28/97 16:31 241582 PCIBUS.SNP PCIBUS.SN_ 12 08/18/97 19:39 2496 PCM2ATA.ADD PCM2ATA.AD_ 12 08/18/97 20:14 27938 FixPak Corrective Service levels and disk layouts 28  October 7, 1997 - Warp 4 FixPak XR_M004 PCMCIA.SYS PCMCIA.SY_ 11 08/18/97 20:12 48646 PCMCIA.TBL PCMCIA.TB_ 12 04/03/97 13:55 4100 PMATM.DLL PMATM.DL_ 7 06/03/97 14:51 233651 PMCHKDSK.DLL PMCHKDSK.DL_ 12 11/04/96 16:44 4127 PMCLIP.DLL PMCLIP.DL_ 12 04/08/97 17:36 21189 PMCTLS.DLL PMCTLS.DL_ 4 08/14/97 11:21 582008 PMCTLS.SYM PMCTLS.SY_ 11 08/14/97 11:21 43860 PMDDE.DLL PMDDE.DL_ 11 04/10/97 11:06 28264 PMDDEML.DLL PMDDEML.DL_ 11 07/23/97 17:17 27210 PMDF.EXE PMDF.EX_ 7 09/18/97 00:42 232952 PMDRAG.DLL PMDRAG.DL_ 12 08/14/97 11:21 1731 PMGPI.DLL PMGPI.DL_ 7 06/16/97 14:18 228570 PMGPI.TDF PMGPI.TD_ 12 06/16/97 14:18 10913 PMGRE.DLL PMGRE.DL_ 12 06/16/97 23:52 2231 PMGRE.TDF PMGRE.TD_ 12 08/13/97 17:53 1062 PMMERGE.DLL PMMERGE.DL_ 2 08/13/97 17:53 1163179 PMMERGE.SYM PMMERGE.SY_ 9 08/13/97 17:53 114420 PMMLE.DLL PMMLE.DL_ 12 08/14/97 11:21 673 PMPRINT.QPR PMPRINT.QP_ 12 07/23/97 20:17 11729 PMSDMRI.DLL PMSDMRI.DL_ 12 08/13/97 17:52 13312 PMSEEK.EXE PMSEEK.EX_ 11 09/07/97 22:57 31285 PMSHAPI.DLL PMSHAPI.DL_ 12 04/08/97 16:45 4549 PMSHAPI.TDF PMSHAPI.TD_ 12 08/13/97 17:53 6187 PMSPL.DLL PMSPL.DL_ 6 07/23/97 20:15 266682 PMSPL.SYM PMSPL.SY_ 12 07/23/97 20:15 31908 PMSPL.TDF PMSPL.TD_ 12 07/23/97 20:15 4483 PMVDMP.DLL PMVDMP.DL_ 11 08/13/97 18:09 43119 PMVIOP.DLL PMVIOP.DL_ 10 08/13/97 18:09 58892 PMVIOP.SYM PMVIOP.SY_ 12 08/13/97 18:09 6596 PMWIN.DLL PMWIN.DL_ 12 08/13/97 17:48 11264 PMWIN.TDF PMWIN.TD_ 12 08/13/97 17:53 12612 PMWIN32.SDF PMWIN32.SD_ 11 06/06/97 19:11 299485 PMWINX.DLL PMWINX.DL_ 4 08/13/97 18:07 578159 PMWP.DLL PMWP.DL_ 3 07/23/97 19:53 922159 PMWP.SYM PMWP.SY_ 10 07/23/97 19:53 100276 PMWPMRI.DLL PMWPMRI.DL_ 11 10/17/96 14:00 54309 PNP.DLL PNP.DL_ 11 07/23/97 20:27 28297 PNP.SYS PNP.SY_ 12 08/18/97 19:39 2152 POINTDD.SYS POINTDD.SY_ 12 08/18/97 19:29 2823 PRINT01.SYS PRINT01.SY_ 12 07/25/97 16:26 12590 PRINT02.SYS PRINT02.SY_ 12 07/25/97 16:26 11766 PSSDMON.EXE PSSDMON.EX_ 11 07/23/97 18:39 25981 PSTAT.EXE PSTAT.EX_ 12 09/07/97 22:53 10339 QUECALLS.DLL QUECALLS.DL_ 12 11/07/96 20:51 1024 QUECALLS.TDF QUECALLS.TD_ 12 09/07/97 22:48 1299 RAS001.MSG RAS001.MS_ 12 07/23/97 18:57 25739 README.CID README.CI_ 12 06/17/97 10:14 60916 REGEDIT.HLP REGEDIT.HL_ 12 08/22/97 18:24 22682 RESERVE.SYS RESERVE.SY_ 12 08/18/97 18:42 5704 RESTORE.EXE RESTORE.EX_ 12 09/07/97 22:58 36256 REX.MSG REX.MS_ 12 09/19/96 15:44 2865 FixPak Corrective Service levels and disk layouts 29  October 7, 1997 - Warp 4 FixPak XR_M004 REXX.DLL REXX.DL_ 8 06/11/97 00:34 266015 REXX.IMG REXX.IM_ 10 03/31/97 17:35 274220 REXXAPI.DLL REXXAPI.DL_ 11 03/31/97 17:35 29091 REXXC.EXE REXXC.EX_ 12 03/31/97 17:35 1980 REXXCRT.DLL REXXCRT.DL_ 10 03/31/97 17:35 61195 REXXUTIL.DLL REXXUTIL.DL_ 11 06/11/97 00:34 29689 REXXUTIL.DLL ORXUTIL1.DL_ 11 06/06/97 13:17 28885 RSPDSPI.EXE RSPDSPI.EX_ 8 07/25/97 11:31 95304 RSPINST.EXE RSPINST.EX_ 6 08/19/97 16:01 427008 RSRV.EXE RSRV.EX_ 9 09/03/97 22:01 77955 SBCD2.ADD SBCD2.AD_ 12 08/18/97 19:09 18820 SCENTER.DLL SCENTER.DL_ 6 07/23/97 20:53 291535 SEAMLESS.DLL SEAMLESS.DL_ 11 08/13/97 18:09 49167 SECUTIL.DLL SECUTIL.DL_ 12 03/31/97 21:54 21468 SEINST.EXE SEINST.EX_ 11 07/25/97 11:05 37441 SEMAINT.EXE SEMAINT.EX_ 11 07/25/97 11:05 67376 SESAPI.DLL SESAPI.DL_ 12 07/23/97 18:38 24283 SESDD32.SYS SESDD32.SY_ 10 07/23/97 18:39 127536 SESMGR.DLL SESMGR.DL_ 12 11/07/96 20:45 1536 SESMGR.TDF SESMGR.TD_ 12 09/07/97 22:48 1643 SETBOOT.EXE SETBOOT.EX_ 12 09/07/97 22:56 16546 SETDEFV.CMD SETDEFV.CM_ 12 12/13/96 11:23 1652 SOFTDRAW.DLL SOFTDRAW.DL_ 6 04/30/97 14:44 409595 SONY31A.ADD SONY31A.AD_ 12 08/18/97 19:11 32738 SPCHOBJ.DLL SPCHOBJ.DL_ 7 04/01/97 15:35 132899 SS2PCIC1.SYS SS2PCIC1.SY_ 12 08/18/97 20:17 19087 SS2TCIC1.SYS SS2TCIC1.SY_ 12 08/18/97 20:17 22824 SVMC.DLL SVMC.DL_ 8 06/16/97 13:39 97785 SVSH.DLL SVSH.DL_ 12 06/16/97 13:39 23452 SYMB.PFM SYM1.PF_ 12 04/30/97 11:59 679 SYSINSTX.COM SYSINSTX.CO_ 11 09/07/97 22:53 39472 SYSLEVEL.FPK SYSLEVEL.FP_ 12 08/29/97 14:00 165 SYSLOGPM.EXE SYSLOGPM.EX_ 5 09/18/97 00:30 138955 SYSTEM.TDF SYSTEM.TD_ 12 09/07/97 22:58 18358 SYSTEM.TFF SYSTEM.TF_ 12 09/07/97 22:58 45067 TEDIT.EXE TEDIT.EX_ 2 11/04/96 16:50 9390 TEDIT.HLP TEDIT.HL_ 12 11/04/96 14:56 14596 TESTCFG.SYS TESTCFG.SY_ 12 08/18/97 19:31 9808 TNR.OFM TNR.OF_ 12 04/30/97 11:59 4940 TNR.PFB TNR.PF_ 9 04/30/97 11:59 74248 TNR.PFM TN1.PF_ 12 04/30/97 11:59 1144 TNRB.OFM TNRB.OF_ 12 04/30/97 11:59 4950 TNRB.PFB TNRB.PF_ 9 04/30/97 11:59 68902 TNRB.PFM TNR1.PF_ 12 04/30/97 11:59 1149 TNRBI.OFM TNRBI.OF_ 12 04/30/97 11:59 4964 TNRBI.PFB TNRBI.PF_ 9 04/30/97 11:59 73914 TNRBI.PFM TNRB1.PF_ 12 04/30/97 11:59 1155 TNRI.OFM TNRI.OF_ 12 04/30/97 11:59 4955 TNRI.PFB TNRI.PF_ 9 04/30/97 11:59 73592 TNRI.PFM TNR2.PF_ 12 04/30/97 11:59 1151 TRACEDLL.DLL TRACEDLL.DL_ 8 09/18/97 00:36 44555 FixPak Corrective Service levels and disk layouts 30  October 7, 1997 - Warp 4 FixPak XR_M004 TRACEFMT.EXE TRACEFMT.EX_ 1 09/18/97 00:37 127972 TRC0003.TFF TRC0003.TF_ 12 12/12/96 17:56 1503 TRC0004.TFF TRC0004.TF_ 12 06/16/97 13:23 4754 TRC0005.TFF TRC0005.TF_ 12 09/13/97 17:21 30574 TRC0006.TFF TRC0006.TF_ 12 12/12/96 17:19 12356 TRC0007.TFF TRC0007.TF_ 12 08/18/97 18:46 1394 TRC0008.TFF TRC0008.TF_ 12 08/18/97 18:39 544 TRC0010.TFF TRC0010.TF_ 12 09/07/97 22:48 3638 TRC0016.TFF TRC0016.TF_ 12 09/07/97 22:48 1673 TRC0017.TFF TRC0017.TF_ 12 09/07/97 22:48 4799 TRC0018.TFF TRC0018.TF_ 12 09/07/97 22:48 37028 TRC006D.TFF TRC006D.TF_ 12 10/16/96 13:16 24181 TRC00C0.TFF TRC00C0.TF_ 12 08/13/97 17:53 13791 TRC00C2.TFF TRC00C2.TF_ 12 08/13/97 17:53 29873 TRC00C3.TFF TRC00C3.TF_ 12 08/13/97 17:53 3984 TRC00C4.TFF TRC00C4.TF_ 12 07/23/97 17:51 242 TRC00C5.TFF TRC00C5.TF_ 12 06/16/97 14:18 26439 TRC00C6.TFF TRC00C6.TF_ 12 07/23/97 20:15 6179 TRUETYPE.DLL TRUETYPE.DL_ 10 07/29/97 17:08 67416 UCDFS.DLL UCDFS.DL_ 11 10/21/96 09:24 13264 UCONV.DLL UCONV.DL_ 12 09/04/97 10:48 23841 UHPFS.DLL UHPFS.DL_ 10 07/25/97 11:54 105488 ULSACT01.MSG ULSACT01.MS_ 12 09/03/97 22:15 907 ULSCAU01.MSG ULSCAU01.MS_ 12 09/03/97 22:15 899 ULSDET01.MSG ULSDET01.MS_ 4 09/03/97 22:15 903 ULSERR01.MSG ULSERR01.MS_ 12 09/03/97 22:15 1967 USER.EXE USER.EX_ 7 08/25/97 13:09 277808 VBIOS.SYS VBIOS.SY_ 12 07/25/97 12:13 8192 VCDROM.SYS VCDROM.SY_ 12 08/18/97 19:49 6880 VCMOS.SYS VCMOS.SY_ 10 07/29/97 11:15 2272 VCOM.SYS VCOM.SY_ 12 08/18/97 19:50 12384 VDPMI.SYS VDPMI.SY_ 12 07/29/97 11:25 30624 VDPX.SYS VDPX.SY_ 12 07/30/97 14:56 26112 VDSK.SYS VDSK.SY_ 12 08/18/97 19:50 10384 VIDEOPMI.DLL VIDEOPMI.DL_ 11 07/30/97 16:28 42439 VIOCALLS.DLL VIOCALLS.DL_ 9 04/08/97 17:36 2048 VKBD.SYS VKBD.SY_ 12 08/18/97 19:51 25292 VLPT.SYS VLPT.SY_ 12 08/18/97 19:51 10113 VMAN.DLL VMAN.DL_ 12 08/21/97 09:03 25221 VMANWIN.SYS VMANWIN.SY_ 6 07/30/97 16:26 2880 VMOUSE.SYS VMOUSE.SY_ 12 08/18/97 19:52 18704 VPIC.SYS VPIC.SY_ 12 07/29/97 11:27 9894 VTIMER.SYS VTIMER.SY_ 12 07/29/97 11:18 9936 VW32S.SYS VW32S.SY_ 12 07/29/97 11:28 18288 VWIN.SYS VWIN.SY_ 12 07/25/97 12:19 26896 WD24B.DSP WD24B.DS_ 1 04/03/97 13:55 12050 WINSCLIP.DLL WINSCLIP.DL_ 12 08/22/97 17:20 14848 WINSDDE.DLL WINSDDE.DL_ 7 08/22/97 17:20 17408 WINSHELD.EXE WINSHELD.EX_ 12 08/22/97 17:20 22016 WINSMSG.DLL WINSMSG.DL_ 12 08/22/97 17:20 27929 WPCLS.IMP WPCLS.IM_ 12 03/31/97 17:35 8661 FixPak Corrective Service levels and disk layouts 31  October 7, 1997 - Warp 4 FixPak XR_M004 WPCONFIG.DLL WPCONFIG.DL_ 3 07/23/97 20:00 229702 WPHELP.HLP WPHELP.HL_ 2 07/23/97 16:27 826713 WPINET.DLL WPINET.DL_ 8 07/23/97 20:47 115384 WPPRINT.DLL WPPRINT.DL_ 5 07/23/97 20:11 362918 WPPRINT.HLP WPPRINT.HL_ 10 07/23/97 20:11 71408 WPPRTMRI.DLL WPPRTMRI.DL_ 10 07/23/97 20:11 66681 WPREXX.IMP WPREXX.IM_ 12 03/31/97 17:35 6313 WPSINIT.WPS WPSINIT.WP_ 12 03/31/97 17:35 15877 WW.EXE WW.EX_ 12 04/01/97 15:37 8305 WWDLL.DLL WWDLL.DL_ 6 04/01/97 15:42 276905 WWHOOK.DLL WWHOOK.DL_ 12 07/23/97 11:58 27230 XCOPY.EXE XCOPY.EX_ 11 09/07/97 22:54 51152 FixPak Corrective Service levels and disk layouts 32  October 7, 1997 - Warp 4 FixPak XR_M004 SPACE UTILIZATION The FixPak installation process requires free space on the following drives: Space needed Drive Up to 2MB C: Up to 2MB Boot drive (4MB if boot is C:) Up to 12MB Drive with most free space, holds deferred files RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE Warning: Make sure you read and understand the following before removing the Archive and Backup files and directories. You can recover the space used for FixPak Archive and Backup files as long as you understand that doing this prevents you from being able to backout to the previous Backup or Archive level. If it becomes necessary at a later time to backout a FixPak, the only way you can do this is to reinstall Warp. Do the following to delete the FixPak Backup and Archive files and remove the files used by CSF to keep track of what service has been applied to your system. 1. Delete every instance of the following files on your system (search every drive and every directory they contain). Ž LOGF0000.* (can be OS2 or MPM) Ž LOGSTART.* (can be OS2 or MPM) Ž LOGARCH.* (can be OS2 or MPM) Ž CSF_*.* Ž FIXSTART 2. Delete the files in the FixPak Archive and Backup directories on your harddisk. 3. Remove the FixPak Archive and Backup directories with the RMDIR command. Space Utilization 33