< Installation instructions for Warp 4 FixPak XR_M015 December 4, 2000 This FixPak makes the products it services Year 2000 ready Build level 14.04? This FixPak applies to: CSD Level: XR_4000 Warp 4 Component ID: 5639A6100 Version: 4.00 Type: 0C CSD Level: XR_4010 WorkSpace On Demand Release 1 Component ID: 5639A6100 Version: 4.01 Type: 0C CSD Level: XR_4010 WorkSpace On Demand Release 2 Component ID: 5639A6120 Version: 4.01 Type: 0C Requires Corrective Service Facility release f.143 or later OS/2 Fix Distribution Personal System Products Austin, Tx (c) Copyright International Business Machines Corporation, 1981, 1998. All rights Reserved.  December 4, 2000 - Warp 4 FixPak XR_M015 December 4, 2000 - Warp 4 FixPak XR_M015 Page ii  December 4, 2000 - Warp 4 FixPak XR_M015 CONTENTS 1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1 2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2 3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3 3.0.1 Audio CD does not play . . . . . . . . . . . . . . . . . . . 3 3.0.2 Out of memory or System error SYS0008 - FP13+ . . . . . . . 3 3.0.3 Warp 4 Revision number changed . . . . . . . . . . . . . . . 3 3.0.4 Changes you may see due to source convergence . . . . . . . 4 3.0.5 Security Applications Work Around . . . . . . . . . . . . . 4 3.0.6 Cannot install on WSoD Release 2 . . . . . . . . . . . . . . 4 3.0.7 New PopUps During FixPak 12 Install . . . . . . . . . . . . 4 3.0.8 Device Drivers removed from Fixpak . . . . . . . . . . . . . 5 3.0.9 Can't install Warp 4 . . . . . . . . . . . . . . . . . . . . 5 3.0.10 Please use Fixtool f.143 or later . . . . . . . . . . . . . 5 3.0.11 OS2DUMP split into two versions . . . . . . . . . . . . . . 5 3.0.12 TRAP in ES16881$ after FP10 applied . . . . . . . . . . . . 6 3.0.13 System Sounds not working after FixPak applied . . . . . . 6 3.0.14 Using Display Recovery Choices . . . . . . . . . . . . . . 7 3.0.15 Installation of Java 1.1.4 . . . . . . . . . . . . . . . . 8 3.0.16 DSPRES.DLL included in this FixPak . . . . . . . . . . . . 8 3.0.17 No products found . . . . . . . . . . . . . . . . . . . . . 8 3.0.18 Previous installation interrupted . . . . . . . . . . . . . 9 3.0.19 Unable to open Archive directory . . . . . . . . . . . . . 9 3.0.20 RC 932 doing CID install of Warp 4 . . . . . . . . . . . . 9 3.0.21 Multimedia no longer selectable . . . . . . . . . . . . . 11 3.0.22 MMPARTS.DLL/USER.EXE popup during install . . . . . . . . 11 3.0.23 CSF0208 No products were found on the target ... . . . . 11 3.0.24 CSF0248 Archive path is shared between mismatched . . . . 11 3.0.25 CSF0249 Error opening or creating archive file. . . . . . 11 3.0.26 Printer installation process change . . . . . . . . . . . 12 3.0.27 Configuration Installation Distribution ( CID ) . . . . . 12 4.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 13 4.0.1 Enabling client updates to the WSOD 2.0 GRADD.MOD file . . 13 4.0.2 Print Screen SET parameter for APAR JR11837 . . . . . . . . 13 4.0.3 New Message Box in fix for APAR JR12954 . . . . . . . . . . 14 4.0.4 RAS file changes . . . . . . . . . . . . . . . . . . . . . 14 4.0.5 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 15 4.0.6 Windows printer drivers leave a zombie thread running . . . 15 4.0.7 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . . . . 16 4.0.8 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . . . 16 4.0.9 Intermittent hangs . . . . . . . . . . . . . . . . . . . . 16 5.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.1 System Boot Message enhancements . . . . . . . . . . . . . . . 17 5.2 Intel's new SpeedStep . . . . . . . . . . . . . . . . . . . . . 17 5.3 New RAS Utilities added . . . . . . . . . . . . . . . . . . . . 17 Contents iii  December 4, 2000 - Warp 4 FixPak XR_M015 5.4 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 17 5.5 Querying file dates for files after Dec 31, 1999 in REXX . . . 18 5.6 Enhanced support for Workspace On-Demand . . . . . . . . . . . 19 5.6.1 PMLOGON user exits . . . . . . . . . . . . . . . . . . . . 19 5.6.2 Setup strings for public applications . . . . . . . . . . . 21 5.6.3 Command line options for TLOGOFF and TSHUTDWN . . . . . . . 22 5.6.4 PMLOGON No Progress Indicator option . . . . . . . . . . . 22 5.6.5 PMLOGON No System Modal Window option . . . . . . . . . . . 23 5.7 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.7.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 23 5.7.2 Where Euro is not supported . . . . . . . . . . . . . . . . 24 5.7.3 Printing the Euro . . . . . . . . . . . . . . . . . . . . . 25 5.8 New Warp Registry Editor . . . . . . . . . . . . . . . . . . . 25 5.9 WorkSpace On Demand . . . . . . . . . . . . . . . . . . . . . . 25 5.10 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.11 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . 26 5.12 Joliet-2 support in CDFS.IFS . . . . . . . . . . . . . . . . . 26 5.13 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 26 5.13.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 26 5.13.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 28 5.14 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 29 5.14.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 29 5.14.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.14.3 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.14.4 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.15 REXX New Fuction . . . . . . . . . . . . . . . . . . . . . . . 31 5.16 Other README files . . . . . . . . . . . . . . . . . . . . . . 31 6.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 32 6.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 32 6.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 32 6.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 33 6.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . . . . 33 6.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 34 6.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 34 6.4 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 35 7.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 37 7.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 37 7.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 37 7.3 Method 2: Install from alternate bootable media . . . . . . . . 38 7.4 Additional Corrective Service Facility information . . . . . . 39 8.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 40 8.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 41 9.0 FixPak Corrective Service levels and disk layouts . . . . . . . 42 10.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 57 10.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 57 10.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 58 Contents iv  December 4, 2000 - Warp 4 FixPak XR_M015 1.0 TERMS AND CONDITIONS Important - please read the following terms and conditions. Downloading the Service Fixes included in FixPak XR_M015 for OS/2 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_M015 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  December 4, 2000 - Warp 4 FixPak XR_M015 2.0 DO NOT USE YOUR SYSTEM 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. Do not use your system 2  December 4, 2000 - Warp 4 FixPak XR_M015 3.0 INSTALLATION NOTES 3.0.1 AUDIO CD DOES NOT PLAY On some systems, after installing Warp 4 FixPak XR_M014, your audio CD may no longer play. The Multimedia CD applet will display a message with a RC of 5060. To correct this problem, perform the following steps : 1. Right mouse click on your desktop. 2. Left mouse click on System setup. 3. Double left mouse click on the Multimedia Setup icon. 4. Left mouse click on the Compact Disc tab. 5. Left mouse click on "+" sign in the right corner. 6. Change the Drive Letter to the Drive Letter where your CD is located. 7. Save change. Your CD should now be able to play CDs. 3.0.2 OUT OF MEMORY OR SYSTEM ERROR SYS0008 - FP13+ Customers who have had an "Out of memory" or SYS0008 problems on systems using Java should add the following line to the CONFIG.SYS file: Ž SET JAVA_HIGH_MEMORY=1 This will allow Java to move it't buffers to a lesser-used region of memory and may alleviate some memory constraints. There are no known unwanted side-effects to doing this. 3.0.3 WARP 4 REVISION NUMBER CHANGED As of FixPak XR_M013 we've converged the souce lines with Warp Server for e-business. This is what causes the initial boot screen to display as 14.040_W4 and the internal version to be reported as 4.50 as well. Some program might interpret this as you not running the correct version of OS/2. If this occurs, please use OS2VER to set the proper version number to be reported to the program. To do so, you must edit a SYSTEM HIDDEN READONLY file, OS2VER, in the root of the boot drive. Then add a line in the format of 40=executable file name and save the file and reset the attributes. Note: To unhide the file OS2VER, perform the following steps: 1. Open an OS/2 window. Installation Notes 3  December 4, 2000 - Warp 4 FixPak XR_M015 2. Change to drive letter where OS/2 is installed. 3. Enter "cd\" to get to the root directory. 4. Enter OS/2 command "attrib -s -h -r os2ver" to unhide OS2VER. 5. Edit OS2VER to add line above ; save 6. Enter OS/2 command "attrib +r +s +h os2ver" to hide OS2VER. 7. Reboot system. 3.0.4 CHANGES YOU MAY SEE DUE TO SOURCE CONVERGENCE Due to the Source Line convergence for OS/2 Warp 4 with the Warp Server for e-Business source code, you might see references to Warp Server for e-business being reported by some device drivers or executables. This is not a problem and may be ignored. 3.0.5 SECURITY APPLICATIONS WORK AROUND Users of some security-related ISS (security) packages such as Utimaco's SafeGuard Professional, will have to add a new line to config.sys: Ž FAKEISS=YES This works around a limitiation of some legacy ISS drivers. This is not a problem for the Tivoli ISS driver. 3.0.6 CANNOT INSTALL ON WSOD RELEASE 2 If you get a message stating "No products found to service" when trying to install on WorkSpace on-Demand Release 2, you may have a corrupted syslevel.os2 file. Copy the syslevel.os2 file from the installation CD or from a working WSoD R2 system and retry the installation. Be sure to use Fixtool 1.42 to service your WSoD R2 system. This will prevent the syslevel.os2 file corruption. Previous versions of the Fixtool fail to correct a problem with the previous CSD level field in the syslevel.os2 file. 3.0.7 NEW POPUPS DURING FIXPAK 12 INSTALL If you get a popup for module VIOTBL.ISO, VIOTBL.DCP, BDIME.DLL, or COUNTRY.SYS during installation of this FixPak, reply "OK" to replace these modules with the ones in this FixPak. Installation Notes 4  December 4, 2000 - Warp 4 FixPak XR_M015 3.0.8 DEVICE DRIVERS REMOVED FROM FIXPAK Beginning with Warp 4 FixPak XR_M011 and Warp 3 FixPak 41, most OS/2 Device Drivers have been moved to a separate Device Driver FixPak. The first Device Driver FixPak, XR_D001, is now available where this FixPak is available. 3.0.9 CAN'T INSTALL WARP 4 If you can't get Warp 4 installed, check the OS/2 Device Driver Pak Online at: http://service.software.ibm.com/os2ddpak/readme.htm#disk1 for the latest available device drivers to update your Installation disks with. 3.0.10 PLEASE USE FIXTOOL F.143 OR LATER Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use Corrective Service Facility f.143 or later. It has fixes for problems found in previous CSF builds as well as a fix to support RIPL servers where there may be in excess of 250 SYSLEVEL files. It also handles the type 1 (All FixPaks prior to 10 and 40) and type 2 (FixPaks 10 and 40 and later) FixPaks. If you try to use a CSF level prior to f.143 you will get a "CSF0208 No products were found on the target system to service" message. 3.0.11 OS2DUMP SPLIT INTO TWO VERSIONS OS2Dump has been split into two versions. If you are installing this fixpak on PS/2 model 9595 machines, use the version located on the last fixpak diskette. Also, if you are running older hardware (486s or early Pentiums), you may wish to use the OS2Dump located on the last fixpak diskette. We have encountered some problems with early implementations of the PCI Bus BIOS extensions (INT 1A) on certain processors and BIOS levels. We are not sure how many different machines and BIOSes are affected. We do know many of the PS/2 model 9595s have the problem. The end result of this is that the version of OS2Dump which supports PCI Bus machines does not work on some older hardware. In order to continue to support the full range of hardware that OS/2 runs on, we have divided OS2Dump into a PCI version and an non-PCI version. If you are running fairly recent hardware, the PCI version of OS2Dump will work on your machine whether or Installation Notes 5  December 4, 2000 - Warp 4 FixPak XR_M015 not it has a PCI bus. All BIOS problems have been worked out. To reiterate, the problem occurs only on older hardware. If you are running a 486 or early Pentium (P60 or less), you may wish to use the non-PCI version located on the last fixpak diskette. If you are running a 9595, you must use the non-PCI version located on the last fixpak diskette. If, after installing this FixPak, you encounter problems taking a standalone dump and your system fits description above, perform the following steps to install the non-PCI version of OS2DUMP located on last disk of this FixPak: 1. Open an OS/2 window. 2. Change to drive letter where OS/2 is installed. 3. Enter "cd\" to get to the root directory. 4. Enter OS/2 command "attrib -s -h -r os2dump" to unhide OS2DUMP. 5. Enter "ren os2dump os2dump.pci"; save PCI version of OS2DUMP. 6. Insert last disk of FixPak in drive A. 7. Copy a:\os2dump 8. Enter OS/2 command "attrib +r +s +h os2dump" to hide OS2DUMP. 9. Reboot system. 3.0.12 TRAP IN ES16881$ AFTER FP10 APPLIED We do not ship any of the ESS sound card drivers in this Fixpak. To corrrect the problem, get the latest ESS device driver for your card from the OS/2 Device Driver Pak online at http://service.software.ibm.com/os2ddpak/html/multimed/esstechn Do this before you install the FixPak. 3.0.13 SYSTEM SOUNDS NOT WORKING AFTER FIXPAK APPLIED If, after applying a FixPak, your System Sounds no longer work or you get an error message stating "Error in closing CD device: Invalid device ID given" when you close the CD Player, it may be caused by the FixPak replacing the following files in your MMOS2 directory tree: \MMOS2\DLL\DIVE.DLL \MMOS2\DLL\MMPM.DLL \MMOS2\DLL\MPGIO.DLL \MMOS2\SSMDD.SYS \MMOS2\DLL\SVMC.DLL \MMOS2\DLL\SVSH.DLL Installation Notes 6  December 4, 2000 - Warp 4 FixPak XR_M015 To recover, restore these files from your FixPak Backup or Archive directory. 1. Boot from another partition, your Installation or Utility disks. 2. Rename the existing files in the MMOS2 directory tree so they will not be overlayed when you restore the older files. 3. Change to the FixPak Backup directory if there is one. If not then change to the FixPak Archive directory. Note: The names may not be Backup or Archive. They will be whatever you called them when you applied a FixPak. 4. For each of the above files, enter UNPACK source target Where "source" is the filename.ext of the file in the Backup or Archive directory, like DIVE.DL_ or SSMDD.SY_ "target" is the fully qualified path of where to place the file, like C:\MMOS2\DLL or C:\MMOS2 5. Repeat for each of the above files 6. Reboot your system. This resolved the problem on a TP760 and may also resolve the problem on other hardware. 3.0.14 USING DISPLAY RECOVERY CHOICES If you have the "Display Recovery Choices at each system startup" function active on your system, you need to disable it before you apply a FixPak if Ž The system is running Ž The boot partition will be serviced. The problem with using this function is that the Corrective Service Facility (CSF) updates the current CONFIG.SYS with entries to run the Locked File Device Driver (LFDD) the next time you boot the system. This is done to replace files that are currently in use (locked) by the system. The Recovery choices function replaces the current CONFIG.SYS with the one that is associated with the recovery choice you select, wiping out the LFDD entries. This means the LFDD does not run at boot time and the deferred files will not get updated, therefore the FixPak does not get completely applied. Note: It is not necessary to disable this function if you install a FixPak by booting from the CSF disks or from another OS/2 partition. Installation Notes 7  December 4, 2000 - Warp 4 FixPak XR_M015 3.0.15 INSTALLATION OF JAVA 1.1.4 Installation of Java 1.1.4 on top of this FixPak will down-level portions of the ULS support. If this occurs, Euro currency support will not work correctly. To recover, re-install this FixPak. This will allow both Java 1.1.4 and Euro support to work correctly. 3.0.16 DSPRES.DLL INCLUDED IN THIS FIXPAK DSPRES.DLL has been added to this FixPak for support for Euro character display. This file can sometimes be overwritten by video device driver installation. If this occurs, an updated version is located in \OS2\INSTALL\VGA. This updated file can be copied into the \OS2\DLL directory. 3.0.17 NO PRODUCTS FOUND If you see a "No products were found on the target system 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. 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. Installation Notes 8  December 4, 2000 - Warp 4 FixPak XR_M015 3.0.18 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. 3.0.19 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. 3.0.20 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. 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. Installation Notes 9  December 4, 2000 - Warp 4 FixPak XR_M015 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 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.Copy the files SCSIADDS and PRESCHEK from DISK_4 to DISK_5. 19.Do the CID install Installation Notes 10  December 4, 2000 - Warp 4 FixPak XR_M015 3.0.21 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. 3.0.22 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL If you get a popup about MMPARTS.DLL or USER.EXE during install, reply "OK" to replace it. 3.0.23 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET ... 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. 3.0.24 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED 1. 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. 2. You have a bad SYSLEVEL.OS2 or SYSLEVEL.MPM file. Both must have the same Current CSD Level, Version, Type and Component ID if you point both Fixpak Archives to the same location. Check \OS2\INSTALL\SYSLEVEL.OS2 and \MMOS2\INSTALL\SYSLEVEL.MPM. If either is wrong, place the last FixPak disk in A: and run FIXSYSL.CMD to correct SYSLEVEL.OS2 problems or SYSZMPM.CMD to fix SYSLEVEL.MPM problems. 3.0.25 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE. 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. There may also be a LOGARCH.OS2 file that needs to be deleted. Installation Notes 11  December 4, 2000 - Warp 4 FixPak XR_M015 This can also occur for Multi Media Presentation Manager/2 (MMPM). You would then need to delete the LOGF0000.MPM and LOGSTART.MPM files from the \MMOS2\INSTALL directory and possibly LOGARCH.MPM if it exists. 3.0.26 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. 3.0.27 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. Installation Notes 12  December 4, 2000 - Warp 4 FixPak XR_M015 4.0 POST INSTALLATION NOTES 4.0.1 ENABLING CLIENT UPDATES TO THE WSOD 2.0 GRADD.MOD FILE IBM WorkSpace On-Demand 2.0 now supports all resolutions and color depths for GRADD model video drivers (this includes the GENGRADD and IBM300G2 machine classes). To enable this support, modify the client's FIT file to enable the client to rewrite the GR ADD.MOD file in the client's OS2 directory. For existing clients, edit the client's FIT file \IBMLAN\RPL\FITS\. FIT, where represents the NetBIOS name of the client machine. Change the following entry: Ž Z:\OS2\GRADD.MOD \\\WRKFILES\\OS2 Ž to Ž Z:\OS2\GRADD.MOD \\\WRKFILES\\OS2\GRADD.MOD where represents the NetBIOS name of the RPL server, and represents the NetBIOS name of the client machine. To enable this capability for all subsequently created clients, perform a similiar modification on the machine class template FIT file, as follows: \IBMLAN\RPL\MACHINES\BB20.\.MC\.FIT, where represents the country code, and represents the name of the machine class. Update both the GENGRADD and IBM300G2 machine class FIT files as follows: Change the following entry: Ž Z:\OS2\GRADD.MOD \\\WRKFILES\DEFAULT\OS2 Ž to Ž Z:\OS2\GRADD.MOD \\\WRKFILES\DEFAULT\OS2\GRADD.MOD where represents the NetBIOS name of the RPL server. 4.0.2 PRINT SCREEN SET PARAMETER FOR APAR JR11837 Add the following environment varible line to CONFIG.SYS to print active window during Print Screen operation: Post Installation Notes 13  December 4, 2000 - Warp 4 FixPak XR_M015 SET PM_PRINTSCREEN_ACTIVE_WINDOW=ON The WINDOW with focus will print when a Print Screen operation is initiated. For the default Print Screen operatin, perform either of these steps: Remove line "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=ON" from CONFIG.SYS or change the line to read: "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=OFF" Note: System must be re-booted after any CONFIG.SYS changes. 4.0.3 NEW MESSAGE BOX IN FIX FOR APAR JR12954 With FixPak 10 installed, if you tried to create Utility Disks and selected "Use files from hard disk if they exist" you would get a SYS3175 trap. This was caused by a much larger AIC7870.ADD file causing the diskette to fill up before all files were copied to it. With FixPak 11 you will now get a "Diskette Full" message box that says "Remove unwanted files and press OK.". This means you should delete from the diskette in your A: drive, files that are not needed on your system. Good candidates for deletion are the CD-ROM drivers and harddisk drivers you do not need. You can check CONFIG.SYS in the root of your boot drive to see if a file is used. If not it can be deleted. When you delete a file, also delete or REM out that line in CONFIG.SYS on the diskette in A:. 4.0.4 RAS FILE CHANGES Beginning with FixPak 11, the following files are being added to the \OS2\SYSTEM directory. If they also exist in the \OS2 directory you can delete them as they are no longer needed there. Ž DTRACE.EXE Ž TRACEFMT.EXE Ž TRSPOOL.EXE If you do not delete them from the \OS2 directory, they will be serviced the same as the ones in the \OS2\SYSTEM directory to keep them current. Also, the following files in the \OS2\SYSTEM\RAS directory can be deleted as they have been superseded as shown: Post Installation Notes 14  December 4, 2000 - Warp 4 FixPak XR_M015 File Superseded by MDTRACE.doc DTRACE.DOC MTRSPOOL.DOC TRSPOOL.DOC 4.0.5 SETTING IRQ9 PROCESSING IN CONFIG.SYS FOR VPIC.SYS Some applications like PCAS (and some terminal emulators) have problems sharing IRQ9 in a VDM. Since the DOS Virtual Device drivers are not loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added starting with Warp 3 FixPak 38 and Warp 4 FixPak 8. To prevent sharing of IRQ9 in a VDM, add the following statement in config.sys: device=x:\os2\mdos\vpicparm.sys irq9_off (x: is your OS/2 boot drive) Next, in the settings for the program that requires exclusive access to IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON. When you next boot your system, VDMs will not share IRQ9. 4.0.6 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 Post Installation Notes 15  December 4, 2000 - Warp 4 FixPak XR_M015 experiences a similar problem with other drivers, please report it so the correct SYSTEM.INI entry can be determined. 4.0.7 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. 4.0.8 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. 4.0.9 INTERMITTENT HANGS If you experience intermittent hangs of your system, check your LIBPATH statement in CONFIG.SYS to see if SOM.DLL is in a directory other than, and ahead of, OS2\DLL. If yes, either change the LIBPATH statement to move the directory after OS2\DLL or try renaming SOM.DLL to SOM.DLO. One known cause of this is VisualAge C++. It has a version of SOM.DLL in its DLL library and the installation puts this library ahead of OS2\DLL in the LIBPATH statement. Post Installation Notes 16  December 4, 2000 - Warp 4 FixPak XR_M015 5.0 NEW FUNCTION 5.1 SYSTEM BOOT MESSAGE ENHANCEMENTS An enhancement has been made to the functions available at system boot time when the "white blob OS/2" appears in the upper left corner of the screen. Ž Alt+F3 - is the equivalent of Alt+F1 plus Alt+F2 This will always display the device driver load information irregardless of what action you specify on the menu. Alt+F2 is automatically enabled if you create a file named ALTF2ON.$$$ in the root or OS2\BOOT directory of the boot drive. The content of this file does not matter. 5.2 INTEL'S NEW SPEEDSTEP The support for Intel's new SpeedStep (a.k.a. Geyserville) included in this FixPak. 5.3 NEW RAS UTILITIES ADDED Two new RAS utilities are included for Pak 13: PSFILES.EXE and PSSEMS.EXE. PSFILES.EXE can dump out information about open files on the system. By default, it dumps out the information for all processes. Alternately, "PSFILES xxx" will dump out information for PID xxx (xxx is a hex number, e.g. from PSTAT). PSSEMS.EXE can dump out information about open 32 bit semaphores on the system. By default it prints out all the shared (i.e. system-wide) semaphores. Usage is: pssems [/n] [hex_pid | /a] ; where /n suppresses shared semaphores and /a prints pruivate sems for all system processes. Note: These RAS Utilities are added to the OS2 directory on your system. 5.4 SERVICEABILITY (RAS) ENHANCEMENTS With FixPak 35 for Warp 3.0 and FixPak 10 for Warp 4.0 major enhancements were provided to the system diagnostic tools (RAS Enhancements). They provide major functional enhancements to the System Trace and Process Dump facilities. Full details of these enhancements can be found in the README.DBG file that will be found in the \OS2\INSTALL directory after New Function 17  December 4, 2000 - Warp 4 FixPak XR_M015 this FixPak is installed. Other associated documentation may be found in: Ž OS2\SYSTEM\RAS\TRACE.DOC Ž OS2\SYSTEM\RAS\DTRACE.DOC Ž OS2\SYSTEM\RAS\PROCDUMP.DOC Ž OS2\SYSTEM\RAS\TRSPOOL.DOC Always refer to README.DBG for details of any RAS enhancements delivered with a FixPak. 5.5 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX Existing REXX functions return file dates with a two digit year only. While these functions are Year 2000 tolerant (i.e. the results will be correct for files dated after Dec 31, 1999) they require some additional logic in existing programs to handle the returned date correctly when they are compared with other file dates. Since the output format of the existing functions could not be changed for compatibility reasons, new options have been added to the REXX interpreter to return file dates with the year formatted with 4 digits. Two functions have been extended to support the new format. The syntax to retrieve the file date in 4 digit format is as follows: /********************************************/ /* Use STREAM QUERY TIMESTAMP to query file */ /* date in 4 digit format */ /********************************************/ Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP") /***********************************************/ /* Use option "L" with SysFileTree to return a */ /* list of files with long date format */ /***********************************************/ Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs" Call SysLoadFuncs Call SysFileTree "C:\*.*", "Files", "L" Do i = 1 To Files.0 Say Files.i End These extensions are available in both classic REXX and Object REXX on OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these extensions in your program you have to make sure that you are running the right level of REXX New Function 18  December 4, 2000 - Warp 4 FixPak XR_M015 5.6 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND 5.6.1 PMLOGON USER EXITS This function, provided by PMLOGON, allows system integrators to have REXX code executed at specific points during the startup and logon sequence. By default, user exits are disabled in PMLOGON.EXE. To enable user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the CONFIG.SYS file must be added. The /URX parameter specifies the location and name of the user exit command file: Execution Parameter User Exit command file that will be executed ------------------- ----------------------------------- /URX \OS2\PMLOGURX.CMD /URX:.CMD .CMD located in one of the locations specified by the PATH environment variable /URX:d:\\.CMD d:\\.CMD The same command file is called for ALL user exits. The FIRST parameter supplied to the command file indicates the exit that it is being called for. The REXX command file is called for all these exits, even if it does not need to process all of the exits. The REXX command file must be able to return error free if it receives an exit number that it does not need to handle. The following user exits are available: New Function 19  December 4, 2000 - Warp 4 FixPak XR_M015 First Parameter Exit Description --------------- ---------------- 0 Executes ONCE per boot, before the requester is started. There is no user logged on at this time. This exit may return a string that is processed exactly as the following execution parameters set in RUNWORKPLACE of CONFIG.SYS: /U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE It is processed immediately after the execution parameters. See Note 2 below on /AUTO processing. 1 Executes ONCE per logon, after the requester is started, but before logon occurs. There is no user logged on at this time. This exit may return a string that is processed exactly as the following execution parameters set in RUNWORKPLACE of CONFIG.SYS: /U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE It is processed immediately before logon. See Note 2 below on /AUTO processing. 2 Executes ONCE per logon, after the requester is started and after logon occurs. There is a user logged on at this time, but the Desktop has not been started and the objects are not displayed. No returns are processed. 3 Executes ONCE per logon, after the Desktop has been started and the objects are created but not currently displayed, but immediately before control is passed to the Desktop. The icons are fixed at this point. There is a user logged on at this time. No returns are processed. 4 Executes immediately after a failed logon. The second parameter passed to the exit contains the return code from the logon API. This exit may return a string that is processed exactly as the execution parameters set in RUNWORKPLACE of CONFIG.SYS for the following parameters only: /U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE This exit is processed immediately and logon is retried with the new parameters regardless of the /AUTO switch. See Note 2 below on /AUTO New Function 20  December 4, 2000 - Warp 4 FixPak XR_M015 processing. If no string is returned, then the normal logon failure or password expired message box is displayed. Note 1: The session environment for the REXX command file is that of PMLOGON.EXE and, therefore, does not contain any input or output facility. For example, "PULL" from the keyboard and "SAY" to the console do not work. Note 2: The /AUTO parameter is validated at every step (for example, after command line processing, after exit 0 returns, and after exit 1 returns). It is turned off if insufficient information (such as no user ID) is provided at that stage for an automatic logon. If the user ID is supplied by the exit, that exit must also provide the /AUTO parameter in order for an auto logon to work. 5.6.2 SETUP STRINGS FOR PUBLIC APPLICATIONS The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific Workplace Shell WPProgram setup strings that are provided when creating public applications on the WorkSpace On-Demand Desktop. In particular, the ICONPOS setup string can be defined for a public application so that the Administrator can identify where application icons are placed on the WorkSpace On-Demand Desktop. When a WorkSpace On-Demand Administrator creates a public application, a new environment variable must be added to the application to provide a setup string. The parameter name is NCC_SETUP_POST and the parameter value can consist of any of the setup strings specified below. Each setup string consists of a KEYNAME, followed immediately by an equal ('=') sign and a VALUE. Multiple setup strings can be passed in the NCC_SETUP_POST environment variable by separating each setup string with a semicolon (';'). The creation of this parameter can be performed either using the WorkSpace On-Demand Public Applications Notebook (on the Parameters page) or using a Command Line Interface (CLI). The following is an example of one parameter: NCC_SETUP_POST=ICONPOS=10,10; The NCC_SETUP_POST environment variable will be searched for when each WorkSpace On-Demand public application is created. If it is found, its value will be used when creating the public application on the WorkSpace On-Demand Desktop. The following KEYNAME values are permitted for setup strings: New Function 21  December 4, 2000 - Warp 4 FixPak XR_M015 Keyname Value Description ------- ----- ----------- CCVIEW DEFAULT Specifies the default value for concurrent views YES Creates new views NO Displays the open view ICONFILE filename Sets the object's icon. ICONPOS x,y Sets the initial icon position in a folder. The "x" and "y" values represent the position in the object's folder in percentage coordinates. ICONRESOURCE id,module Sets the object's icon. The "id" is the icon resource ID in the dynamic link library (DLL) "module." Refer to the Workplace Shell Programming Reference for a description and definition of the above setup strings. Note: The NCC_SETUP_POST environment variable exists in the current environment when the public application with which it is associated is running. 5.6.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN Three command line options have been added to both TLOGOFF.EXE and TSHUTDWN.EXE: 1. /Q -- causes these programs not to display the UPM/LAN copyright window. 2. /N -- causes no confirmation message boxes to be displayed. Note: If these parameters are not capitalized, they are ignored. 5.6.4 PMLOGON NO PROGRESS INDICATOR OPTION An execution parameter has been added to PMLOGON that causes the progress indicator window not to be displayed during all of logon processing. That parameter is /NOPI and can be specified only from the RUNWORKPLACE line in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit, it is ignored. New Function 22  December 4, 2000 - Warp 4 FixPak XR_M015 5.6.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION An execution parameter has been added to PMLOGON which prevents PMLOGON from setting any of its windows to be system modal after user exit 1 is executed on the first boot or anytime after a logoff. The parameter is /NOSM1 and can only be specified from the RUNWORKPLACE line in CONFIG.SYS. If /NOSM1 is returned as a parameter from a user REXX exit, it is ignored. 5.7 EURO SUPPORT The European Monetary Union is creating the Euro as a new common currency for Europe. As part of this effort the European Commission has introduced a new character which represents the Euro. This character looks like an uppercase C with two horizontal lines through it. The Euro will come into existence on January 1, 1999 for use in banking. Euro notes and coins will be issued starting January 2002. 5.7.1 BASE OS/2 SUPPORT The OS/2 basic support for Euro consists of adding the Euro character to fonts, codepages, and keyboards. The Euro is added to all display and ATM fonts and to the Times New Roman MT 30 TrueType font which is available with Java 1.1. The Euro is added to all western European keyboards and the US International keyboard. The Euro can be used in base OS/2, Presentation Manager, and in DOS. The Euro is not supported in WinOS2. The Euro character is added to these OS/2 base and PM codepages: 850 0xD5 PC Latin 1 base + PM 857 0xD5 PC Turkish base + PM 1004 0x80 Windows Extended base + PM 1250 0x80 Windows Latin 2 PM 1251 0x88 Windows Cyrillic PM 1252 0x80 Windows Latin 1 PM 1254 0x80 Windows Turkish PM 1257 0x80 Windows Baltic PM The Euro character is added to these fonts. New Function 23  December 4, 2000 - Warp 4 FixPak XR_M015 Courier (bitmap) Courier (ATM) Helv (bitmap) Helvetica (ATM) System Monospace (bitmap) System Proportional (bitmap) System VIO (bitmap) Times New Roman (ATM) Times New Roman MT 30 (TrueType - Java 1.1) Tms Rmn (bitmap) WarpSans (bitmap) The Euro character is added to these OS/2 keyboards: Belgium be altgr-e Canada ca altgr-e Canadian French cf altgr-e Denmark dk altgr-5 Finland su (fi) altgr-5 France fr altgr-e Germany gr (de) altgr-e Germany(453) de453 altgr-e Iceland ic (is) altgr-5 Iceland 101 is458 altgr-5 Italy it altgr-5 Italy extended itn142 altgr-5 Latin America la altgr-e Netherlands nl altgr-e Norway no altgr-5 Portugal po altgr-5 Spain sp (es) altgr-5 Sweden sv altgr-5 Swiss French sf altgr-e Swiss German sg (sd) altgr-e Turkey tr179 altgr-e Turkey 440 tr440 altgr-e UK uk altgr-4 UK 168 uk168 altgr-e US International ux altgr-e 5.7.2 WHERE EURO IS NOT SUPPORTED The Euro is not supported in WinOS2. This character is not supported in the Windows-1252 codepage used in WinOS2. This character is not available on the WinOS2 keyboards. This character is not available in the WinOS2 supplied TrueType fonts: New Function 24  December 4, 2000 - Warp 4 FixPak XR_M015 Arial (Windows TrueType) Courier New (Windows TrueType) The Euro is not in the 437 (US English) or 863 (Canadian French) codepages. You must use codepage 850 to get the Euro. The Euro is not on the US keyboard. You can use the US International (ux) keyboard instead. 5.7.3 PRINTING THE EURO Existing printers do not support the Euro in device fonts. You need to select a font which is not mapped to a device font in order to print the Euro. The Euro will print correctly on printers where the system fonts are used. When there are problems, a dotless-i is normally printed instead of the Euro. For PostScript printers, it is necessary to disable device fonts to print the Euro in one of the base PostScript fonts (Helvetica, Times Roman, Courier). To do this: 1. Open the properties of the Printer object 2. Select the Print Driver tab 3. Select Job Properties 4. Select the Output tab 5. Deselect "Use printer device fonts" 5.8 NEW WARP REGISTRY EDITOR See the README.REG file on the first FixPak disk for details. 5.9 WORKSPACE ON DEMAND WorkSpace on Demand Release 1 is supported starting with FixPak 5 (XR_M005). WorkSpace on Demand Release 2 is supported starting with FixPak 11 (XR_M011). 5.10 IBM OPEN32 This FixPak includes updates to the IBM Open32 Application Programming Interfaces (APIs). New Function 25  December 4, 2000 - Warp 4 FixPak XR_M015 5.11 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD) Future updates for GRADD and other video drivers (when they are released) will be found via the internet at: Ž http://service.software.ibm.com/pslaunch.html 5.12 JOLIET-2 SUPPORT IN CDFS.IFS Joliet is a Microsoft extension to the ISO 9660 CD-ROM file system which adds Unicode and longname support. Presently both Windows 95 and Windows NT 4.0 support the Joliet-2 and Joilet-3 formats. Beginning with Warp 3 Fixpak 32 and Warp 4 Fixpak 4, you can enable the Joliet-2 support by adding the '/w' option to the CDFS.IFS statement in CONFIG.SYS. Joilet-3 format is not supported. 5.13 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. 5.13.1 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. New Function 26  December 4, 2000 - Warp 4 FixPak XR_M015 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 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.IFS, add POPUPERRORS=NO below the [filesystem] section of the HPFS386.INI file. Support for the POPUPERRORS parameter requires OS/2 LAN Server FixPak IP08265 or higher for LS 5.0 or FixPak IP08503 or higher for LS 5.1. In addition, the POPUPERRORS parameter ONLY suppresses HFS0102 messages. 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. New Function 27  December 4, 2000 - Warp 4 FixPak XR_M015 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. 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. 5.13.2 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: New Function 28  December 4, 2000 - Warp 4 FixPak XR_M015 message.txt msghdr.txt pmchklog.exe range.txt readme They should all have a date of 05/14/97 or later (May 14, 1997). 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. 5.14 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). 5.14.1 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". 5.14.2 TRAPLOG The TRAPLOG command allows dynamic control of trap information logging. The command syntax is: TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS] New Function 29  December 4, 2000 - Warp 4 FixPak XR_M015 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. 5.14.3 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. 5.14.4 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. New Function 30  December 4, 2000 - Warp 4 FixPak XR_M015 The system behaves as if a fatal crash has occurred thus under rare circumstances data can be lost. The command syntax is: SYSDUMP [/NOPROMPT] where: Ž NOPROMPT allows the Dump to proceed without the prompt and response to message: "Do you want to force a system dump? (Y/N)" 5.15 REXX NEW FUCTION New Function has been added in REXX. Please see the "Other README Files" for documentation pointers. This new function was added to FP 13 and later. 5.16 OTHER README FILES There are other README files containing information you may want to review. All except README.DBG are found on the first FixPak disk and are not copied to your system when the Fixpak is installed. README.DBG will be copied to the \OS2\INSTALL directory during installation beginning with Fixpak 10 and Fixpak 41. File Use README2 Problems fixed in each FixPak (APAR list) README.CID Installing FixPaks via CID README.REG Use of the Warp Registry Editor REGEDIT2.EXE README.DBG Tips on debugging OS/2 Warp and details on the latest Serviceability (RAS) Enhancements (3.0 and 4.0). READREXX.TXT New RexxUtil Function documentation added in this FixPak. New Function 31  December 4, 2000 - Warp 4 FixPak XR_M015 6.0 CORRECTIVE SERVICE FACILITY 6.0.1 REQUIRED CSF LEVEL You should use release level f.143 or later of the OS/2 Corrective Service Facility to install this FixPak. Bootable diskettes are no longer provided starting with the F.138B CSF build. Instead, you now get a self-extracting ZIP file which contains the following: archctl.cmd build.lvl csfpans.dll filefix.dll fpinst.cmd fservice.exe fservice.msg ibmcsflk.dll ibmcsflk.exe ibmcsflk.msg ibmcsflk.sys msg.dll nls.dll pack.exe read.me readme.inf response.lan response.wp3 response.wp4 service.exe service.hlp shpiinst.dll unpack.exe unpack2.exe viocalls.dll Follow the directions in the READ.ME file to use the new CSF code. It covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or from one of several alternative boot methods. 6.0.2 WHERE YOU CAN FIND CSF CODE The Corrective Service Facility code is available from many places, including, but not limited to, the following: Source How to access Corrective Service Facility 32  December 4, 2000 - Warp 4 FixPak XR_M015 Internet(FTP) Anonymous FTP to ftp.software.ibm.com in the "/ps/products/os2/fixtool" directory. Internet(WWW) Point your Web Browser at ftp://service.boulder.ibm.com/ps/products/os2/fixtool Intranet(FTP) Anonymous FTP to os2service.austin.ibm.com in the "f:\fixpacks\fixtool" directory. 6.0.3 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_M015.?DK A: /F (? can be 1 through 9, A through Z). Label the diskette as FixPak XR_M015 Corrective Service Diskette ? (CSF DISK ?) Note: For diskette images ADK through ZDK, use the numbers 10 through 35. Examples: XR_M015.ADK = 10 XR_M015.FDK = 15 XR_M015.LDK = 21 etc. 6.1 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 Corrective Service Facility 33  December 4, 2000 - Warp 4 FixPak XR_M015 You will have files and directories left on your harddisk that will cause problems when installing a Warp 4 FixPak. 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. 6.2 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. 6.3 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: Corrective Service Facility 34  December 4, 2000 - Warp 4 FixPak XR_M015 For \OS2\INSTALL\SYSLEVEL.OS2 ..\..\ 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 and subdirectories. ..\..\PSFONTS\* all files in the PSFONTS directory and subdirectories. ..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories. ..\..\OPENDOC\* all files in the OPENDOC directory and subdirectories. 6.4 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: Corrective Service Facility 35  December 4, 2000 - Warp 4 FixPak XR_M015 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. 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 36  December 4, 2000 - Warp 4 FixPak XR_M015 7.0 INSTALLATION PROCESS 7.1 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. Once CHKDSK has completed, reboot your system then shutdown all running applications before starting the FixPak installation. 7.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION. Note: CS_???.EXE below means CS_143 or later. Follow the instructions in the READ.ME file that comes in the CS_???.EXE self-extracting zip file. This explains how to use the CS_???.EXE file and the various ways you can install a FixPak with this level of CSF code. Here are some additional notes: Follow the displayed instructions. When prompted to insert Corrective Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_M015 Corrective Service Diskette 1 in drive A. Repeat for the rest of the FixPak disks when requested to do so. 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. If this is the first OS/2 Warp FixPak you have applied to this system, then enter the path to the directory where a copy of replaced files will be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.) Note: This ARCHIVE directory is not related to the ARCHIVES directory built into OS/2 Warp 3 and Warp 4. Please specify a different path. You must specify a different ARCHIVE directory for each product to be serviced. Installation Process 37  December 4, 2000 - Warp 4 FixPak XR_M015 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. Make sure there is sufficient space available on the drive you specify for archive or backup. Even though these files are kept in compressed (PACK2) format, they can take up a lot of space on the drive. During the installation process you may 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. See the section "FixPak Corrective Service levels and disk layouts" for the CSD levels this FixPak applies to. 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 The system will do one automatic reboot after the Locked File Device Driver has completed. 7.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA Note: CS_???.EXE below means CS_143 or later. Follow the instructions in the READ.ME file that comes in the CS_???.EXE self-extracting zip file. This explains how to use the CS_???.EXE file and the various ways you can install a FixPak with this level of CSF code. Installation Process 38  December 4, 2000 - Warp 4 FixPak XR_M015 Here are some additional notes: 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 unless you have modified the default response file. 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. 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 file to control some of the actions taken by FSERVICE.EXE while applying a FixPak. See the READ.ME file or use the VIEW command to look at the file README.INF. They are part of CS_???.EXE. 7.4 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. There is also some additional information in the READ.ME file. Installation Process 39  December 4, 2000 - Warp 4 FixPak XR_M015 8.0 CSD LEVEL OF SYSLEVEL.OS2 The Current CSD level field of the SYSLEVEL.OS2 file in each serviced partition will be updated with the name of the FixPak when it is applied. This is a major change from previous CSF releases. The Prior CSD level field will be left asis. This means when you use the SYSLEVEL command to look at the release levels of products on your system, you will see the following for SYSLEVEL.OS2. Before a FixPak is applied using the F.138B CSF build (or later) E:\OS2\INSTALL\SYSLEVEL.OS2 IBM OS/2 Base Operating System Version 4.00 Component ID 5639A6100 Type 0C Current CSD level: XR04000 Prior CSD level: XR04000 After a FixPak is applied using the F.138B CSF build (or later) E:\OS2\INSTALL\SYSLEVEL.OS2 IBM OS/2 Base Operating System Version 4.00 Component ID 5639A6100 Type 0C Current CSD level: XR0M008 Prior CSD level: XR04000 All fix information is recorded in SERVICE.LOG. Look at the file \OS2\INSTALL\SERVICE.LOG on your boot drive for information relating to the installation of FixPaks on your system. Additionally, you can 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.50 Revision 14.044 The first page of this document has a line that looks like: Build Level: nn.nnn CSD level of SYSLEVEL.OS2 40  December 4, 2000 - Warp 4 FixPak XR_M015 That is the number you should see for this FixPak when you issue the VER /R command. 8.0.1 NEW SYSLEVEL.FPK A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning with XR_M004. It is titled "OS/2 Warp 4 Service Level". It contains the name of the currently installed FixPak in both the Current and Previous CSD level fields and is located in the same directory the SYSLEVEL.OS2 file is located in which should be \OS2\INSTALL. The easiest way to look at SYSLEVEL information is to use the SYSLEVEL command and redirect the output to a file then edit the file and search for SYSLEVEL.FPK. CSD level of SYSLEVEL.OS2 41  December 4, 2000 - Warp 4 FixPak XR_M015 9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS Build Level: 14.04? Product location on CSD: A:\FIX\OS2.1 Product name: "IBM OS/2 Base Operating System" Standard Edition 4.00 Fixpak name: XR_M015_ (Country = Generic) Pre-requisite CSD Level: XR_4000_ System Id: 1000 Component Id: 5639A6100 Archive is ON for this product. ________________________________________________________________________ Product name: "IBM OS/2 Base Operating System" Standard Edition 4.01 Fixpak name: XR_M015_ (Country = Generic) Pre-requisite CSD Level: XR_4010_ System Id: 1000 Component Id: 5639A6100 Archive is ON for this product. ________________________________________________________________________ Product name: "IBM OS/2 Base Operating System" Standard Edition 4.01 Fixpak name: XR_M015_ (Country = Generic) Pre-requisite CSD Level: XR_4010_ System Id: 1000 Component Id: 5639A6120 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* ..\..\MMOS2 ..\..\MMOS2\* ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Will create the following directories ..\..\OS2 Stub File: @OS2DIR ..\..\OS2\DLL Stub File: @DLLDIR ..\..\OS2\BOOT Stub File: @BOOTDIR ..\..\OS2\SYSTEM Stub File: @SYSTDIR FixPak Corrective Service levels and disk layouts 42  December 4, 2000 - Warp 4 FixPak XR_M015 ..\..\OS2\INSTALL Stub File: @INSTDIR ..\..\OS2\INSTALL\BOOTDISK Stub File: @INBTDIR ..\..\OS2\APPS Stub File: @APPSDIR ..\..\OS2\SYSTEM\RAS Stub File: @RASDIR ..\..\OS2\SYSTEM\TRACE Stub File: @TRACDIR ..\..\LANGUAGE\CODEPAGE Stub File: @CDPGDIR Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- APPEND.EXE APPEND.EX_ 18 11/15/2000 19:32 7602 0FFAE60E ARACONV.EXE ARACONV.EX_ 16 11/23/1999 20:12 62151 F784F7D0 ASIACOL.DLL ASIACOL.DL_ 11 10/12/2000 15:54 158758 1ECA61A1 ASSIGN.COM ASSIGN.CO_ 18 11/15/2000 19:33 2684 13D52846 ATTRIB.EXE ATTRIB.EX_ 16 11/15/2000 19:33 37789 BE52FFB9 AVIO.DLL AVIO.DL_ 15 10/13/2000 10:12 53921 F4FA279B BACKUP.EXE BACKUP.EX_ 17 11/15/2000 19:36 35040 278F38EC BDCALL32.DLL BDCALL32.DL_ 16 11/23/1999 20:11 33519 7B24A009 BDIME.DLL BDIME.DL_ 17 11/23/1999 20:12 11911 1CA663B5 BDVIEW.DLL BDVIEW.DL_ 16 11/15/2000 02:59 34888 FF485512 BDWPCLS.DLL BDWPCLS.DL_ 17 11/15/2000 02:58 20144 A5A0A30E BE.KBL BE.KB_ 18 10/12/2000 16:00 972 9473C4B2 BLDLEVEL.EXE BLDLEVEL.EX_ 16 10/06/2000 14:52 57842 DA887122 BOOTDISK.EXE BOOTDISK.EX_ 15 07/13/2000 11:04 61563 C95D3588 BOOTDISK.HLP BOOTDISK.HL_ 17 07/12/2000 15:43 11575 B23CED74 BVHINIT.DLL BVHINIT.DL_ 17 09/15/2000 17:09 11158 18E60E11 BVHMPA.DLL BVHMPA.DL_ 17 09/15/2000 16:10 15293 6169D262 BVHVGA.DLL BVHVGA.DL_ 16 09/15/2000 16:09 31875 3C904D4F BVHWNDW.DLL BVHWNDW.DL_ 17 09/15/2000 17:09 16797 DDF61B0D BVSCALLS.DLL BVSCALLS.DL_ 18 11/15/2000 18:31 512 8EB3628F BY.KBL BY.KB_ 18 10/12/2000 16:00 1292 11BE6C9F CA.KBL CA.KB_ 18 10/12/2000 16:00 1214 8C1C9E65 CACHE.EXE CACHE.EX_ 17 10/06/2000 13:51 13870 A4D8044D CARDINFO.DAT CARDINFO.DA_ 17 10/06/2000 09:17 54979 C547B548 CCHMAIN.EXE CCHMAIN.EX_ 9 11/14/2000 19:38 199408 8D0A6E74 CCHUSER.DLL CCHUSER.DL_ 14 11/14/2000 19:37 63763 24B23C1B CDFS.IFS CDFS.IF_ 16 10/06/2000 14:05 45159 D579671E CDFS.TDF CDFS.TD_ 18 10/06/2000 14:05 2113 779C2068 CDROM.TBL CDROM.TB_ 18 09/05/2000 11:54 4371 EF56BE58 CF.KBL CF.KB_ 18 10/12/2000 16:00 956 C70BE074 CHKDSK.COM CHKDSK.CO_ 15 11/15/2000 19:33 70720 1FDCA370 CHKDSK.SYS CHKDSK.SY_ 18 10/06/2000 13:52 795 3BAC1F48 CHKDSK32.DLL CHKDSK32.DL_ 12 10/06/2000 14:03 139227 4C293DE7 CHKDSK32.EXE CHKDSK32.EX_ 18 10/06/2000 13:52 6417 43F31C60 FixPak Corrective Service levels and disk layouts 43  December 4, 2000 - Warp 4 FixPak XR_M015 CLOCK01.SYS CLOCK01.SY_ 18 09/22/2000 08:12 4560 E501D1AB CLOCK02.SYS CLOCK02.SY_ 18 09/22/2000 08:12 4318 352B3AE2 CMD.EXE CMD.EX_ 13 11/15/2000 19:34 100108 33896E5F COMM.DRV COMM.DR_ 17 12/02/1999 17:56 9552 2944F5F2 COMMAND.COM COMMAND.CO_ 16 11/15/2000 19:34 42763 7A5B986E COMP.COM COMP.CO_ 16 11/15/2000 19:34 35881 4C41A9F0 CONTROL.PM CONTROL.PM_ 18 09/05/2000 12:10 8474 E9A71A82 COUNTRY.SYS COUNTRY.SY_ 17 09/05/2000 16:31 50947 1937440B COUR.OFM COUR.OF_ 18 11/22/1999 11:22 6163 8932E1ED COUR.PFB COUR.PF_ 11 11/22/1999 11:23 137111 48043987 COUR.PFM COU1.PF_ 18 11/22/1999 11:22 674 EB14B168 COURB.OFM COURB.OF_ 18 11/22/1999 11:22 6173 30530A2B COURB.PFB COURB.PF_ 10 11/22/1999 11:23 140829 503DA489 COURB.PFM COUR1.PF_ 18 11/22/1999 11:22 679 1EF9C4BB COURBI.OFM COURBI.OF_ 18 11/22/1999 11:22 6187 0F59E5D1 COURBI.PFB COURBI.PF_ 11 11/22/1999 11:23 136240 56421E00 COURBI.PFM COURB1.PF_ 18 11/22/1999 11:22 685 A4390DF0 COURI.OFM COURI.OF_ 18 11/22/1999 11:22 6178 1CEF133A COURI.PFB COURI.PF_ 10 11/22/1999 11:23 137394 715E75E2 COURI.PFM COUR2.PF_ 18 11/22/1999 11:22 681 A6EEB6A2 COURIER.FON COURIER.FO_ 15 10/19/2000 13:03 77826 6ED05C3A COURIERI.FON COURIERI.FO_ 15 10/19/2000 12:59 86641 C6745C2D CPG01256.TBL CPG01256.TB_ 18 11/22/1999 12:17 27264 A5C721BD CREX.MSG CREX.MS_ 18 09/06/2000 12:42 2865 8188DE0E CREXUTIL.DLL CREXUTIL.DL_ 14 09/06/2000 12:42 68119 4D4A96EB CREXX.DLL CREXX2.DL_ 10 09/06/2000 12:42 266031 C716AA5F CYRIME.DLL CYRIME.DL_ 17 10/19/2000 12:43 21529 4ED04128 CZ.KBL CZ.KB_ 18 10/12/2000 16:00 1014 E4EC6917 DDINSTAL.EXE DDINSTAL.EX_ 16 11/15/2000 19:52 52263 70B2EA28 DE.KBL DE.KB_ 18 10/12/2000 16:00 958 28E8DC29 DE453.KBL DE453.KB_ 18 10/12/2000 16:00 1354 1CF79BBC DEBUG.EXE DEBUG.EX_ 17 11/15/2000 19:34 27233 32432531 DF_DEB.EXE DF_DEB.EX_ 13 11/15/2000 18:05 135989 D2462C66 DF_RET.EXE DF_RET.EX_ 13 11/15/2000 16:51 135957 94CE7FB8 DIBDRVR.DLL DIBDRVR.DL_ 18 10/19/2000 14:02 5627 7A65141B DICTATE.EXE DICTATE.EX_ 15 05/06/1998 11:58 59315 50477D97 DICTDLL.DLL DICTDLL.DL_ 15 12/21/1997 01:28 51187 2DAC90F6 DISKCOMP.COM DISKCOMP.CO_ 16 11/15/2000 19:36 41697 FF09A6BF DISKCOPY.COM DISKCOPY.CO_ 16 11/15/2000 19:36 46196 F0610E9D DISPLAY.DLL DISPLAY.DL_ 15 09/15/2000 15:58 46574 F71EB0D6 DIVE.DLL DIVE.DL_ 14 10/06/2000 08:13 69662 B5D13AA0 DK.KBL DK.KB_ 18 10/12/2000 16:00 928 CAEC9535 DMISL.EXE DMISL.EX_ 13 10/06/2000 21:03 144918 ADD48904 DMQSPROF.DLL DMQSPROF.DL_ 15 09/15/2000 16:07 39033 6D5BE86E DOSCALL1.DLL DOSCALL1.DL_ 12 11/15/2000 16:50 137327 AAA5E09D DOSCALL1.SYM DOSCALL1.SY_ 16 11/15/2000 16:50 43476 125A8993 DOSCALL1.TDF DOSCALL1.TD_ 18 11/15/2000 16:50 5534 A9AE23D5 DOSKEY.COM DOSKEY.CO_ 18 11/15/2000 19:34 6243 0A55A9C9 DOSKRNL DOSKRNL.___ 17 11/15/2000 16:51 31497 C8EB625C DRVMAP.INF DRVMAP.IN_ 18 09/05/2000 12:07 12986 0AD60C88 DSPIMRI.DLL DSPIMRI.DL_ 17 09/15/2000 16:24 17446 F1DB9A5C FixPak Corrective Service levels and disk layouts 44  December 4, 2000 - Warp 4 FixPak XR_M015 DSPINSTL.EXE DSPINSTL.EX_ 13 10/02/2000 15:46 175640 C665A00A DSPRES.DLL DSPRES1.DL_ 8 10/19/2000 12:59 376488 C8BB2ACB DSPRES.DLL DSPRES.DL_ 8 10/19/2000 12:59 376488 C8BA06CB DTRACE.DOC DTRACE.DO_ 17 11/22/1999 11:25 75371 5B1E5F89 DTRACE.EXE DTRACE1.EX_ 15 10/06/2000 21:10 74850 254E4F97 DTRACE.EXE DTRACE.EX_ 15 10/06/2000 21:10 74850 254E7A17 E.EXE E.EX_ 14 11/14/2000 18:09 63383 980358B2 EAUTIL.EXE EAUTIL.EX_ 16 11/15/2000 19:34 38000 6F0A15D3 EDLIN.COM EDLIN.CO_ 18 11/15/2000 19:34 8348 8F53CDF6 EHXDLMRI.DLL EHXDLMRI.DL_ 17 11/14/2000 18:09 13861 56CE6365 EJECT.EXE EJECT.EX_ 17 09/05/2000 16:39 29746 40E33693 EL.KBL EL.KB_ 18 10/12/2000 16:00 1396 610DE7D0 EL459.KBL EL459.KB_ 18 10/12/2000 16:00 1372 797B7C72 ENGINE.EXE ENGINE.EX_ 7 07/23/1997 11:39 440424 CA47CBAA EPM.EXE EPM.EX_ 17 11/23/1999 17:44 24032 1787F472 ERLOGGER.EXE ERLOGGER.EX_ 16 10/06/2000 14:10 48608 5EB8C0E1 ERRLOG.DLL ERRLOG.DL_ 12 10/06/2000 14:09 72806 CF92B384 ERRTXT.DLL ERRTXT.DL_ 17 11/15/2000 13:40 26714 741E43EA ES.KBL ES.KB_ 18 10/12/2000 16:00 920 3744F42A ETKC603.DLL ETKC603.DL_ 12 11/23/1999 16:02 136124 B18E8724 ETKE603.DLL ETKE603.DL_ 6 11/23/1999 16:02 767421 C1741876 EZP2MRI.DLL EZP2MRI.DL_ 15 11/14/2000 18:10 95262 C935A4E3 FDISK.COM FDISK.CO_ 14 11/15/2000 19:37 114878 3417828F FDISKPM.DLL FDISKPM.DL_ 18 09/05/2000 16:37 10805 49CF08F4 FDISKPM.EXE FDISKPM.EX_ 15 11/15/2000 19:38 78404 C97B2663 FDISKPMH.HLP FDISKPMH.HL_ 17 09/05/2000 16:37 14372 9BD0DEBB FFCONFIG.DLL FFCONFIG.DL_ 17 10/06/2000 14:13 20551 485CCA4D FFDUMP.DLL FFDUMP.DL_ 15 10/06/2000 15:21 41217 D920B1D1 FFGUI.DLL FFGUI.DL_ 17 10/06/2000 14:13 18683 401C58E3 FFIPC.DLL FFIPC.DL_ 17 10/06/2000 14:13 27201 F86D8B12 FFPCT.DLL FFPCT.DL_ 17 10/06/2000 14:13 21588 96F267FD FFPROBE.DLL FFPROBE.DL_ 17 10/06/2000 14:50 24680 77EEB333 FFST.DLL FFST.DL_ 17 10/06/2000 14:13 11425 B9B55D0A FFSTCONF.EXE FFSTCONF.EX_ 14 10/06/2000 15:21 104505 9E8F8833 FFSTPCT.EXE FFSTPCT.EX_ 14 10/06/2000 15:21 105143 76829336 FI.KBL FI.KB_ 18 10/12/2000 16:00 940 F49DDB21 FILT.DLL FILT.DL_ 17 10/13/2000 10:07 22890 F997AE11 FIND.EXE FIND.EX_ 4 11/15/2000 19:34 31085 69206775 FKA.DLL FKA.DL_ 17 11/22/1999 11:46 13997 66D06B79 FORMAT.COM FORMAT.CO_ 15 11/15/2000 19:35 72064 1727BC4E FR.KBL FR.KB_ 18 10/12/2000 16:00 950 BC615CC6 FSFILTER.SYS FSFILTER.SY_ 17 11/15/2000 16:52 12714 66391A78 GDI.EXE GDI.EX_ 10 12/02/1999 16:20 225776 8E4C99DC GRADD.SYS GRADD.SY_ 18 09/15/2000 17:12 2754 03EBF6B1 GRAFTABL.COM GRAFTABL.CO_ 18 11/15/2000 19:35 9648 ECC35C7C GRE2VMAN.DLL GRE2VMAN.DL_ 17 09/15/2000 22:04 18189 1874FBCE GSVDAEMN.EXE GSVDAEMN.EX_ 18 07/19/2000 11:27 4848 6C7ECB27 GSVINST.EXE GSVINST.EX_ 16 11/14/2000 19:01 34351 F6E06023 HARDERR.EXE HARDERR.EX_ 17 11/15/2000 16:50 14889 E9868FCF HDMON.EXE HDMON.EX_ 14 10/06/2000 14:19 112055 A493AFB8 HELPMGR.DLL HELPMGR.DL_ 9 10/19/2000 13:01 250157 0A772627 FixPak Corrective Service levels and disk layouts 45  December 4, 2000 - Warp 4 FixPak XR_M015 HELPMSG.EXE HELPMSG.EX_ 16 11/15/2000 19:35 37280 BDBF39F1 HELV.FON HELV.FO_ 11 10/19/2000 13:03 171252 BE4D4630 HELV.OFM HELV.OF_ 18 11/22/1999 11:22 6793 9CE6E30D HELV.PFB HELV.PF_ 11 11/22/1999 11:23 120578 014F23CF HELV.PFM HEL1.PF_ 18 11/22/1999 11:22 1096 6F229952 HELVB.OFM HELVB.OF_ 18 11/22/1999 11:22 6785 54469E79 HELVB.PFB HELVB.PF_ 11 11/22/1999 11:23 123085 0037C9CB HELVB.PFM HELV1.PF_ 18 11/22/1999 11:22 1089 84484E9F HELVBI.OFM HELVBI.OF_ 18 11/22/1999 11:22 6787 41065DD9 HELVBI.PFB HELVBI.PF_ 11 11/22/1999 11:23 124245 46A1595C HELVBI.PFM HELVB1.PF_ 18 11/22/1999 11:22 1087 06B4029D HELVI.FON HELVI.FO_ 11 10/19/2000 12:59 199523 A1519D3F HELVI.OFM HELVI.OF_ 18 11/22/1999 11:22 6772 3B1431CD HELVI.PFB HELVI.PF_ 11 11/22/1999 11:24 123355 48DC6098 HELVI.PFM HELV2.PF_ 18 11/22/1999 11:22 1079 A1475F00 HPFS.IFS HPFS.IF_ 13 10/06/2000 13:49 141378 4A0DA275 HPFS.TDF HPFS.TD_ 18 10/06/2000 13:49 1620 FE70C493 HPMGRMRI.DLL HPMGRMRI.DL_ 17 10/19/2000 13:01 21881 1A3751B6 HR.KBL HR.KB_ 18 10/12/2000 16:00 982 4371550F HU.KBL HU.KB_ 18 10/12/2000 16:00 1006 5894479F IBM1004 IBM1004.___ 18 10/12/2000 15:51 3584 9FB42D9E IBM1125 IBM1125.___ 18 10/12/2000 15:51 4320 DB8513DC IBM1131 IBM1131.___ 18 10/12/2000 15:51 4320 8669A2E6 IBM1140 IBM1140.___ 18 10/12/2000 15:51 2816 776F51FA IBM1141 IBM1141.___ 18 10/12/2000 15:51 2784 9B08CF2D IBM1142 IBM1142.___ 18 10/12/2000 15:51 2816 7C6BA473 IBM1143 IBM1143.___ 18 10/12/2000 15:51 2816 FB88C823 IBM1144 IBM1144.___ 18 10/12/2000 15:51 2784 4087FB0E IBM1145 IBM1145.___ 18 10/12/2000 15:51 2784 81D24DF7 IBM1146 IBM1146.___ 18 10/12/2000 15:51 2816 85F1F6E5 IBM1147 IBM1147.___ 18 10/12/2000 15:51 2784 7A2A00FC IBM1148 IBM1148.___ 18 10/12/2000 15:51 2816 6114895E IBM1250 IBM1250.___ 18 10/12/2000 15:51 3552 E91C78A4 IBM1251 IBM1251.___ 18 10/12/2000 15:51 3328 3AC2A11F IBM1252 IBM1252.___ 18 10/12/2000 15:51 3552 BAEEE0FD IBM1253 IBM1253.___ 18 10/12/2000 15:51 3552 9FCC3C7E IBM1254 IBM1254.___ 18 10/12/2000 15:51 3552 65DB7A68 IBM1255 IBM1255.___ 18 10/12/2000 15:51 3808 EEB4CAF7 IBM1256 IBM1256.___ 18 10/12/2000 15:51 4320 3DBDA3E8 IBM1257 IBM1257.___ 18 10/12/2000 15:51 3296 9D4AD72D IBM813 IBM813.___ 18 10/12/2000 15:51 3072 08A2984D IBM850 IBM850.___ 18 10/12/2000 15:51 4320 C9955D45 IBM852 IBM852.___ 18 10/12/2000 15:51 4608 FB8DC70F IBM857 IBM857.___ 18 10/12/2000 15:51 4352 2B09830F IBM859 IBM859.___ 18 10/12/2000 15:51 4320 0EF4A493 IBM862 IBM862.___ 18 10/12/2000 15:51 4576 96A84D36 IBM864 IBM864.___ 18 10/12/2000 15:51 4576 F9F0D5CC IBM869 IBM869.___ 18 10/12/2000 15:51 4320 12FBFC5A IBM923 IBM923.___ 18 10/12/2000 15:51 2784 6DCE74D1 IBM924 IBM924.___ 18 10/12/2000 15:51 2784 036319A7 IBMOPTNS.DLL IBMOPTNS.DL_ 17 10/06/2000 09:17 22330 0EB8E86B FixPak Corrective Service levels and disk layouts 46  December 4, 2000 - Warp 4 FixPak XR_M015 ICONEDIT.EXE ICONEDIT.EX_ 13 11/23/1999 15:50 162864 1B4E9380 IFGDI2VM.DRV IFGDI2VM.DR_ 15 09/15/2000 17:12 93136 7268974F INSCFG32.DLL INSCFG32.DL_ 16 11/15/2000 19:37 32098 47FB5EAB INST_DOS.EXE INST_DOS.EX_ 16 10/19/2000 14:00 39114 80A38780 INSTALL.EXE INSTALL.EX_ 7 07/13/2000 11:04 384264 E8B8AA4A IOPROC.DLL IOPROC.DL_ 16 10/13/2000 10:16 37880 91C2CA33 IS.KBL IS.KB_ 18 10/12/2000 16:00 940 86D694EE IS458.KBL IS458.KB_ 18 10/12/2000 16:00 928 1A3415EB ISGDI2VM.DRV ISGDI2VM.DR_ 15 09/15/2000 16:14 92048 C14AB2C9 IT.KBL IT.KB_ 18 10/12/2000 16:00 876 B83B7729 IT142.KBL IT142.KB_ 18 10/12/2000 16:00 854 901F665B JOIN.EXE JOIN.EX_ 18 11/15/2000 19:35 4520 77E938E4 JPEGIO.DLL JPEGIO.DL_ 15 10/13/2000 10:19 44357 B48913B3 KERNEL.SDF KERNEL.SD_ 14 11/15/2000 16:51 59155 C9F9282D KERNELD.SDF KERNELD.SD_ 14 11/15/2000 16:51 59147 E97AEF18 KEYBOARD.DCP KEYBOARD.DC_ 16 10/12/2000 16:03 315109 33BC80C8 KRNLBDEV.TDF KRNLBDEV.TD_ 18 11/15/2000 18:02 4232 16DDF047 KRNLBFS.TDF KRNLBFS.TD_ 18 11/15/2000 18:02 4793 530637E7 KRNLBLDR.TDF KRNLBLDR.TD_ 18 11/15/2000 18:02 5384 65CAE2B6 KRNLBPG.TDF KRNLBPG.TD_ 18 11/15/2000 18:02 3209 0C916C32 KRNLBSEL.TDF KRNLBSEL.TD_ 18 11/15/2000 18:02 2783 09883DE5 KRNLBSEM.TDF KRNLBSEM.TD_ 18 11/15/2000 18:02 1792 EBE89963 KRNLBSM.TDF KRNLBSM.TD_ 18 11/15/2000 18:02 1196 9D39F161 KRNLBTK.TDF KRNLBTK.TD_ 18 11/15/2000 18:02 13005 AB5AB775 KRNLBTOM.TDF KRNLBTOM.TD_ 18 11/15/2000 18:02 1012 66449028 KRNLBVDM.TDF KRNLBVDM.TD_ 18 11/15/2000 18:02 15570 0BD16AD8 KRNLBVM.TDF KRNLBVM.TD_ 18 11/15/2000 18:02 5542 A91BEA19 KRNLDDEV.TDF KRNLDDEV.TD_ 18 11/15/2000 17:54 4232 F8A23583 KRNLDFS.TDF KRNLDFS.TD_ 18 11/15/2000 17:54 4734 8C388542 KRNLDLDR.TDF KRNLDLDR.TD_ 18 11/15/2000 17:54 5387 37558BB2 KRNLDPG.TDF KRNLDPG.TD_ 18 11/15/2000 17:54 3265 97A09AEB KRNLDSEL.TDF KRNLDSEL.TD_ 18 11/15/2000 17:54 2895 2253AD29 KRNLDSEM.TDF KRNLDSEM.TD_ 18 11/15/2000 17:54 1932 A308CB1C KRNLDSM.TDF KRNLDSM.TD_ 18 11/15/2000 17:54 1221 B449F170 KRNLDTK.TDF KRNLDTK.TD_ 18 11/15/2000 17:54 13033 0D3FB67B KRNLDTOM.TDF KRNLDTOM.TD_ 18 11/15/2000 17:54 1040 4A0460AA KRNLDVDM.TDF KRNLDVDM.TD_ 18 11/15/2000 17:54 15795 EA01694B KRNLDVM.TDF KRNLDVM.TD_ 18 11/15/2000 17:54 5654 2826950E KRNLRDEV.TDF KRNLRDEV.TD_ 18 11/15/2000 17:11 4232 C5B483F5 KRNLRFS.TDF KRNLRFS.TD_ 18 11/15/2000 17:11 4793 A729B211 KRNLRLDR.TDF KRNLRLDR.TD_ 18 11/15/2000 17:11 5384 0E5C5AAA KRNLRPG.TDF KRNLRPG.TD_ 18 11/15/2000 17:11 3209 2CAD0A4E KRNLRSEL.TDF KRNLRSEL.TD_ 18 11/15/2000 17:11 2783 79FE2812 KRNLRSEM.TDF KRNLRSEM.TD_ 18 11/15/2000 17:11 1792 E4675F66 KRNLRSM.TDF KRNLRSM.TD_ 18 11/15/2000 17:11 1196 2CD94AC0 KRNLRTK.TDF KRNLRTK.TD_ 18 11/15/2000 17:11 12921 4862FE17 KRNLRTOM.TDF KRNLRTOM.TD_ 18 11/15/2000 17:11 984 7D8D4AD6 KRNLRVDM.TDF KRNLRVDM.TD_ 18 11/15/2000 17:11 15405 13A549D9 KRNLRVM.TDF KRNLRVM.TD_ 18 11/15/2000 17:11 5542 53DA5C5F LABEL.COM LABEL.CO_ 17 11/15/2000 19:37 33805 AFA130CA LFAPI.DLL LFAPI.DL_ 17 10/06/2000 14:09 21178 EEE925A9 FixPak Corrective Service levels and disk layouts 47  December 4, 2000 - Warp 4 FixPak XR_M015 LIBCM.DLL LIBCM.DL_ 9 11/22/1999 11:45 210916 5BC599EE LIBCN.DLL LIBCN.DL_ 15 11/22/1999 11:45 57340 676A0B04 LIBCS.DLL LIBCS.DL_ 10 11/22/1999 11:45 192386 7E2C4E24 LIBUNI.DLL LIBUNI.DL_ 14 10/12/2000 16:00 81372 C1127F47 LMDLL.DLL LMDLL.DL_ 15 08/14/2000 19:20 76973 D73954B0 LOCALE.DLL LOCALE.DL_ 13 10/12/2000 16:00 107901 15E56505 MAIN.CPL MAIN.CP_ 13 12/02/1999 16:32 147680 00423A80 MAKETSF.EXE MAKETSF.EX_ 16 10/06/2000 21:10 51928 63B9D0FE MAPTSF.CMD MAPTSF.CM_ 18 11/22/1999 11:25 16803 1F2B489D MEM.EXE MEM.EX_ 16 11/15/2000 19:38 39716 876438D6 MIDI.SYS MIDI.SY_ 17 08/14/2000 18:53 26328 FA7C8AD0 MIDIMCD.DLL MIDIMCD.DL_ 18 10/13/2000 10:14 4118 1D3375FA MIGRATE.EXE MIGRATE.EX_ 13 11/15/2000 20:01 174443 3A7F6011 MINSTALL.EXE MINSTALL.EX_ 11 10/06/2000 09:18 191774 8CE71FE2 MINXOBJ.DLL MINXOBJ.DL_ 16 11/14/2000 19:31 31886 BD6028F9 MIRRORS.DLL MIRRORS.DL_ 3 09/06/2000 12:44 444744 4D9369F8 MMODPTS.DLL MMODPTS.DL_ 9 10/13/2000 10:46 184022 12635668 MMPARTS.DLL MMPARTS.DL_ 2 10/13/2000 10:45 1532232 EEF994D0 MMPM.DLL MMPM.DL_ 7 10/13/2000 10:50 432003 CD8DD638 MMPTMRI.DLL MMPTMRI.DL_ 12 10/06/2000 09:06 229394 147D4A64 MMSNIFF.DLL MMSNIFF.DL_ 16 07/19/2000 13:32 33298 5D864972 MMSOUND.DRV MMSOUND.DR_ 18 12/02/1999 16:48 3456 97C7CFF0 MODE.COM MODE.CO_ 7 11/15/2000 19:35 64245 21A737BA MONCALLS.DLL MONCALLS.DL_ 18 11/15/2000 18:31 5536 3EDB689D MONCALLS.TDF MONCALLS.TD_ 18 11/15/2000 18:31 1139 A167041D MORE.COM MORE.CO_ 16 11/15/2000 19:35 34855 E4577659 MPGIO.DLL MPGIO.DL_ 14 10/13/2000 10:20 59269 C5A5BB04 MSG.DLL MSG.DL_ 18 11/15/2000 18:31 512 CCB1ED52 NAMEADD.EXE NAMEADD.EX_ 17 11/24/1999 13:10 23040 3DC869A2 NAMECOPY.EXE NAMECOPY.EX_ 17 11/24/1999 13:10 23040 1C05214E NAMEDEL.EXE NAMEDEL.EX_ 17 11/24/1999 13:10 23040 65C869A3 NAMEDSP.DLL NAMEDSP.DL_ 12 09/06/2000 12:45 123411 678C3C12 NAMEEXT.EXE NAMEEXT.EX_ 17 11/24/1999 13:10 23040 9DC869A5 NAMEFW.DLL NAMEFW.DL_ 14 09/06/2000 12:45 72312 04C6E184 NAMEMOD.EXE NAMEMOD.EX_ 17 11/24/1999 13:10 23040 4DC869A3 NAMEMOVE.EXE NAMEMOVE.EX_ 17 11/24/1999 13:10 23040 2405214C NAMEREXX.DLL NAMEREXX.DL_ 13 09/06/2000 12:45 97811 93EAB10C NAMPIPES.DLL NAMPIPES.DL_ 18 11/15/2000 18:31 1024 5FCACCD0 NL.KBL NL.KB_ 18 10/12/2000 16:00 954 431DC1DE NLS.DLL NLS.DL_ 18 11/15/2000 18:31 512 B0628263 NO.KBL NO.KB_ 18 10/12/2000 16:00 920 2555DC36 NWIAPI.DLL NWIAPI.DL_ 17 11/15/2000 03:05 14770 3FA6E7D6 OREXUTIL.DLL ORXUTIL2.DL_ 15 09/06/2000 12:43 41175 9BC71149 OREXX.DLL OREXX2.DL_ 7 09/06/2000 12:43 490355 38E21AD5 OS2CHAR.DLL OS2CHAR.DL_ 18 11/15/2000 18:31 512 896DE743 OS2CHAR.TDF OS2CHAR.TD_ 18 11/15/2000 16:50 13889 D4E1119B OS2DASD.DMD OS2DASD.DM_ 16 09/23/2000 12:16 40910 D834DADD OS2DUMP OS2DUMP.___ 17 11/15/2000 18:32 15101 6F76CFDB OS2K386.EXE OS2K386.EX_ 14 12/02/1999 16:22 80306 CAEDD240 OS2KRNL OS2KRNL.___ 4 11/15/2000 17:11 845682 4E220EE2 OS2KRNLD.SYM OS2KRNLD.SY_ 12 11/15/2000 17:53 189380 1C2E45A7 FixPak Corrective Service levels and disk layouts 48  December 4, 2000 - Warp 4 FixPak XR_M015 OS2KRNLR.SYM OS2KRNLR.SY_ 12 11/15/2000 17:11 167188 2C207A6F OS2KRNLR.TDF OS2KRNLR.TD_ 18 11/15/2000 17:11 21026 5EE5E808 OS2LDR.MSG OS2LDR.MS_ 18 11/15/2000 16:49 8878 9F235F8F OS2MM.DLL OS2MM.DL_ 1 10/06/2000 09:18 219660 0D979E1A OS2SM.DLL OS2SM.DL_ 18 10/19/2000 14:20 1598 87503005 OS2UGL OS2UGL.___ 18 10/12/2000 15:52 15616 42667255 OSO001.MSG OSO001.MS_ 14 11/14/2000 15:59 175354 9ADF69DC OSO001H.MSG OSO001H.MS_ 14 11/14/2000 15:59 240256 24A7FD1A PARALLEL.PDR PARALLEL.PD_ 17 11/14/2000 18:06 15850 04CEA656 PCMCIA.TBL PCMCIA.TB_ 18 04/14/2000 13:27 5114 F9E24825 PDUMPSYS.EXE PDUMPSYS.EX_ 16 10/06/2000 21:17 47165 E603B960 PDUMPUSR.EXE PDUMPUSR.EX_ 16 10/06/2000 21:17 47163 FEE0EF9B PICV.DLL PICV.DL_ 17 10/19/2000 12:59 26200 59732B53 PICVIEW.DLL PICVIEW.DL_ 17 10/19/2000 13:00 13858 0ED37C04 PICVIEW.EXE PICVIEW.EX_ 14 10/19/2000 13:00 95770 217338D2 PL.KBL PL.KB_ 18 10/12/2000 16:00 980 5B4C9089 PL457.KBL PL457.KB_ 18 10/12/2000 16:00 882 F102688A PMATM.DLL PMATM.DL_ 4 04/12/2000 11:39 224343 15C73B97 PMBIDI.DLL PMBIDI.DL_ 17 11/23/1999 20:11 13611 08D96136 PMCHKDSK.DLL PMCHKDSK.DL_ 18 09/11/2000 09:51 7199 81E095EF PMCHKDSK.EXE PMCHKDSK.EX_ 17 11/15/2000 15:39 33303 D79A42D2 PMCLIP.DLL PMCLIP.DL_ 17 10/19/2000 14:01 21253 99EC6E18 PMCTLS.DLL PMCTLS.DL_ 4 10/19/2000 21:02 587798 89320509 PMCTLS.SYM PMCTLS.SY_ 16 10/19/2000 21:02 44660 85EA57A0 PMDDE.DLL PMDDE.DL_ 16 10/19/2000 21:12 28314 9DD53BEF PMDDEML.DLL PMDDEML.DL_ 16 10/19/2000 12:43 27814 82681B42 PMDF.EXE PMDF.EX_ 9 10/06/2000 21:16 393388 B5D0947D PMDFMSG.DLL PMDFMSG.DL_ 15 10/06/2000 14:18 44516 49E84F09 PMDRAG.DLL PMDRAG.DL_ 18 10/19/2000 13:50 1731 8C66B469 PMGPI.DLL PMGPI.DL_ 9 10/19/2000 12:38 248446 C468C795 PMGPI.TDF PMGPI.TD_ 18 10/19/2000 12:38 12338 18BC9677 PMGRE.DLL PMGRE.DL_ 18 10/19/2000 12:35 2231 815A9F54 PMGRE.TDF PMGRE.TD_ 18 10/19/2000 21:04 1062 6013F07E PMMERGE.DLL PMMERGE.DL_ 3 10/19/2000 21:04 1268731 E7D4528F PMMERGE.SYM PMMERGE.SY_ 13 10/19/2000 21:04 117508 573ED03C PMMLE.DLL PMMLE.DL_ 18 10/19/2000 14:25 673 388DB999 PMMRGRES.DLL PMMRGRES.DL_ 13 10/19/2000 12:51 134144 B4E21ABC PMPIC.DLL PMPIC.DL_ 15 10/19/2000 14:00 47206 CDF1F652 PMPIC.TDF PMPIC.TD_ 18 10/19/2000 14:34 400 AAA168A3 PMPRE.DLL PMPRE.DL_ 15 09/15/2000 15:58 46574 37B947EA PMPRINT.QPR PMPRINT.QP_ 17 11/14/2000 17:58 11835 A45B02E0 PMREXX.EXE PMREXX.EX_ 15 10/06/2000 14:50 78885 4AFE664E PMSDMRI.DLL PMSDMRI.DL_ 17 10/19/2000 12:48 15872 01B4F423 PMSEEK.EXE PMSEEK.EX_ 17 11/15/2000 19:38 44597 F017139B PMSHAPI.DLL PMSHAPI.DL_ 18 10/19/2000 12:45 4549 84CA9933 PMSHAPI.TDF PMSHAPI.TD_ 18 10/19/2000 21:04 6726 D94221E4 PMSHELL.EXE PMSHELL.EX_ 18 11/14/2000 18:48 6028 084CA3EC PMSHLTKT.DLL PMSHLTKT.DL_ 15 09/06/2000 12:45 44232 A1FD720F PMSPL.DLL PMSPL.DL_ 8 11/14/2000 17:58 277251 B514352E PMSPL.SYM PMSPL.SY_ 17 11/14/2000 17:58 32340 F1E525D3 PMSPL.TDF PMSPL.TD_ 18 11/14/2000 17:58 4491 6397698E FixPak Corrective Service levels and disk layouts 49  December 4, 2000 - Warp 4 FixPak XR_M015 PMSPOOL.EXE PMSPOOL.EX_ 18 11/14/2000 18:51 9590 5950C3D9 PMUNIF.DLL PMUNIF.DL_ 15 10/19/2000 14:00 43823 54464C46 PMVDMP.DLL PMVDMP.DL_ 15 10/19/2000 13:03 45317 4DB7500D PMVDMP.TDF PMVDMP.TD_ 18 10/19/2000 21:13 2661 081AC164 PMVIOP.DLL PMVIOP.DL_ 14 10/19/2000 13:03 64204 00BA6BC1 PMVIOP.SYM PMVIOP.SY_ 18 10/19/2000 13:03 7620 BDB39940 PMVIOP.TDF PMVIOP.TD_ 18 10/19/2000 21:12 3551 2636316D PMWIN.DLL PMWIN.DL_ 18 10/19/2000 12:41 11264 341D49B1 PMWIN.TDF PMWIN.TD_ 18 10/19/2000 21:04 9567 0EC566C5 PMWIN32.SDF PMWIN32.SD_ 16 10/19/2000 12:43 313392 B4B104AE PMWINX.DLL PMWINX.DL_ 6 10/19/2000 12:58 530827 B94445D5 PMWP.DLL PMWP.DL_ 1 11/15/2000 03:02 1063363 F0D9A67A PMWP.SYM PMWP.SY_ 13 11/15/2000 03:02 103796 036720DF PMWP.TDF PMWP.TD_ 18 11/15/2000 03:02 13825 3CBA6F84 PMWPMRI.DLL PMWPMRI.DL_ 15 11/14/2000 17:52 54311 870D09BC PNP.DLL PNP.DL_ 16 11/14/2000 19:35 28297 9CB5FD75 PNP.SYS PNP.SY_ 18 08/14/2000 18:56 2152 2CA5E770 PNPMRI.DLL PNPMRI.DL_ 17 11/14/2000 18:01 31781 067AF1A8 PO.KBL PO.KB_ 18 10/12/2000 16:00 926 623C72BA PRINT.COM PRINT.CO_ 17 11/15/2000 19:35 34177 540C3271 PROCDUMP.DOC PROCDUMP.DO_ 17 11/22/1999 11:25 62998 5680E87C PROCDUMP.EXE PROCDUMP.EX_ 16 10/06/2000 21:17 66591 F5190C14 PROGMAN.EXE PROGMAN.EX_ 15 12/02/1999 16:29 115328 99CE07B6 PSFILES.EXE PSFILES.EX_ 17 11/15/2000 15:34 10229 000FEF64 PSSDMON.EXE PSSDMON.EX_ 17 10/30/2000 11:25 41533 C52DEA6F PSSEMS.EXE PSSEMS.EX_ 17 11/15/2000 15:34 11717 6273B0FC PSTAT.EXE PSTAT.EX_ 17 11/15/2000 15:34 14661 72ED22EF QUECALLS.DLL QUECALLS.DL_ 18 11/15/2000 18:31 1024 D0C33A6E QUECALLS.TDF QUECALLS.TD_ 18 11/15/2000 16:50 1299 C1001BC9 RAS001.MSG RAS001.MS_ 17 10/06/2000 14:09 26260 905AC57F RASH.MSG RASH.MS_ 18 10/06/2000 14:09 11856 0F823C5B README.DBG README.DB_ 18 09/06/2000 12:44 2463 F82C4618 RECOVER.COM RECOVER.CO_ 16 11/15/2000 19:38 46656 6B3DFB54 REGCONV.EXE REGCONV.EX_ 16 11/24/1999 13:02 52758 410B3D05 REGEDIT.HLP REGEDIT.HL_ 17 12/02/1999 17:59 22682 FEC4ACA5 REGEDIT2.EXE REGEDIT2.EX_ 5 11/24/1999 13:10 970240 E306FD10 REGISTRY.DLL REGISTRY.DL_ 15 11/24/1999 13:02 81440 824B143E REGISTRY.MSG REGISTRY.MS_ 18 11/24/1999 13:10 629 8F2A3623 REGISTRY.TDF REGISTRY.TD_ 18 11/24/1999 13:02 984 E7DBD05C REPLACE.EXE REPLACE.EX_ 16 11/15/2000 19:39 41072 016D12A6 RESTORE.EXE RESTORE.EX_ 15 11/15/2000 19:39 39280 E22E0B85 REX.MSG REX.MS_ 18 09/06/2000 12:42 2865 603C7657 REXX.DLL CREXX1.DL_ 10 09/06/2000 12:42 266031 42250B8E REXX.DLL OREXX1.DL_ 6 09/06/2000 12:43 490355 1A1BDF06 REXX.IMG REXX.IM_ 14 09/06/2000 12:42 283636 D71F239D REXXAPI.DLL REXXAPI.DL_ 16 09/06/2000 12:42 40995 14493324 REXXC.EXE REXXC.EX_ 18 09/06/2000 12:42 2758 D07F5D4F REXXCRT.DLL REXXCRT.DL_ 14 09/06/2000 12:42 79348 C14ED1D8 REXXUTIL.DLL REXXUTIL.DL_ 14 09/06/2000 12:42 68119 4D4EA6EB REXXUTIL.DLL ORXUTIL1.DL_ 15 09/06/2000 12:43 41175 9BC74649 RINSTPRN.EXE RINSTPRN.EX_ 10 11/14/2000 18:11 205268 2B304E57 FixPak Corrective Service levels and disk layouts 50  December 4, 2000 - Warp 4 FixPak XR_M015 RO.KBL RO.KB_ 18 10/12/2000 16:00 944 E33356F6 RSPDDI.EXE RSPDDI.EX_ 17 11/15/2000 19:52 29753 0C264E46 RSPDSPI.EXE RSPDSPI.EX_ 13 10/02/2000 15:46 143398 921C6111 RSPIMRI.DLL RSPIMRI.DL_ 1 08/31/2000 12:46 17455 71B60D9D RSPINST.EXE RSPINST.EX_ 9 02/29/2000 10:05 428896 16D61CCD RSRV.EXE RSRV.EX_ 14 09/06/2000 12:45 77955 DF21E454 RU.KBL RU.KB_ 18 10/12/2000 16:00 1144 0E8C7DDF RXVIDCFG.DLL RXVIDCFG.DL_ 17 09/15/2000 17:10 14741 A1B7AF07 SBFILTER.DLL SBFILTER.DL_ 17 09/15/2000 17:13 14861 EB0E5706 SCENTER.DLL SCENTER.DL_ 8 11/14/2000 18:08 294781 7AACB299 SD.KBL SD.KB_ 18 10/12/2000 16:00 1036 415E88FE SEAMLESS.DLL SEAMLESS.DL_ 16 10/19/2000 21:13 49167 F1F9F519 SECUTIL.DLL SECUTIL.DL_ 17 10/30/2000 11:25 21468 EE20F3E8 SEINST.EXE SEINST.EX_ 16 11/15/2000 19:39 48707 285ACEFA SEMAINT.EXE SEMAINT.EX_ 14 02/18/2000 16:54 67840 947EDB8E SERIAL.PDR SERIAL.PD_ 17 11/14/2000 17:55 19062 1A8AFB96 SESAPI.DLL SESAPI.DL_ 17 10/30/2000 11:24 24203 ED54FAF0 SESDD32.SYS SESDD32.SY_ 11 10/30/2000 11:26 118834 299C986B SESMGR.DLL SESMGR.DL_ 18 11/15/2000 18:31 1536 6534B911 SESMGR.TDF SESMGR.TD_ 18 11/15/2000 16:50 1877 4D4EC693 SESSHELL.EXE SESSHELL.EX_ 17 10/30/2000 11:25 29805 86BACFB0 SETBOOT.EXE SETBOOT.EX_ 17 11/15/2000 19:37 20400 90ED5A1E SETDEFV.CMD SETDEFV.CM_ 18 10/05/2000 13:50 1652 AA7ED994 SF.KBL SF.KB_ 18 10/12/2000 16:00 1036 5CC5BB81 SHPIINST.DLL SHPIINST.DL_ 16 10/19/2000 20:57 37304 5D86AF59 SK.KBL SK.KB_ 18 10/12/2000 16:00 1008 CAB66A86 SL.KBL SL.KB_ 18 10/12/2000 16:00 982 D1DE1E66 SOFTDRAW.DLL SOFTDRAW.DL_ 5 10/19/2000 12:32 416439 5D867332 SOM.DLL SOM.DL_ 13 06/30/1999 16:33 92009 A7AC8525 SORT.EXE SORT.EX_ 17 11/15/2000 19:35 32047 3EBB438E SPCHOBJ.DLL SPCHOBJ.DL_ 12 12/21/1997 01:27 132899 9004B0F7 SPL1B.DLL SPL1B.DL_ 18 11/14/2000 17:58 7125 E590C70C SPOOLCP.DLL SPOOLCP.DL_ 17 11/14/2000 18:05 10210 FF56BF98 SQ.KBL SQ.KB_ 18 10/12/2000 16:00 824 D8F9CFE7 SSM.DLL SSM.DL_ 18 10/06/2000 08:13 4118 C40C804D SSMDD.SYS SSMDD.SY_ 16 10/06/2000 08:12 36813 D4B233BF STRACE.EXE STRACE.EX_ 16 11/15/2000 15:41 56023 F203A918 SUBST.EXE SUBST.EX_ 18 11/15/2000 19:35 4520 24232C44 SV.KBL SV.KB_ 18 10/12/2000 16:00 946 9B897832 SVMC.DLL SVMC.DL_ 13 10/13/2000 10:10 98391 E30AAAF8 SVSH.DLL SVSH.DL_ 17 10/13/2000 10:11 23082 66D71003 SW.DLL SW.DL_ 14 10/06/2000 08:15 66505 2585AB3F SWITCHRX.CMD SWITCHRX.CM_ 18 09/06/2000 12:43 7928 16729FC1 SYMB.PFM SYM1.PF_ 18 11/22/1999 11:22 679 EC2CE0BD SYSDUMP.EXE SYSDUMP.EX_ 17 10/06/2000 21:17 28701 06967DF9 SYSINST2.EXE SYSINST2.EX_ 12 02/29/2000 10:00 184512 17CE2135 SYSINSTX.COM SYSINSTX.CO_ 16 11/15/2000 19:35 40128 9B0096FB SYSLEVEL.EXE SYSLEVEL.EX_ 16 11/15/2000 19:38 44736 CF1DA67A SYSLEVEL.FPK SYSLEVEL.FP_ 18 09/20/2000 11:07 165 3525EAF0 SYSLEVEL.MSG SYSLEVEL.MS_ 18 02/18/2000 17:05 1445 FA952C94 SYSLOGPM.EXE SYSLOGPM.EX_ 12 10/06/2000 14:09 215355 D088C92D FixPak Corrective Service levels and disk layouts 51  December 4, 2000 - Warp 4 FixPak XR_M015 SYSMONO.FON SYSMONO.FO_ 17 10/19/2000 13:03 21294 62FF1AAA SYSMONOI.FON SYSMONOI.FO_ 16 10/19/2000 14:00 35841 3EA946D6 SYSSPLIT.CMD SYSSPLIT.CM_ 18 11/22/1999 11:25 3712 A308EBC8 TDFLST.CMD TDFLST.CM_ 18 11/22/1999 11:25 13564 7BB43592 TEDIT.EXE TEDIT.EX_ 17 09/05/2000 16:41 9390 0F62FBEA TEDIT.HLP TEDIT.HL_ 18 09/05/2000 12:13 14596 29E13771 TESTCFG.SYS TESTCFG.SY_ 17 08/14/2000 18:47 9808 DB2A2545 TEXTCON1.EXE TEXTCON1.EX_ 16 11/23/1999 20:12 49011 9916B6FC TFFLST.CMD TFFLST.CM_ 18 11/22/1999 11:25 4638 E5A615D0 TIMES.FON TIMES.FO_ 12 10/19/2000 13:03 166150 8B4CE282 TIMESI.FON TIMESI.FO_ 11 10/19/2000 12:59 181173 027007EB TNR.OFM TNR.OF_ 18 11/22/1999 11:22 6809 D815154B TNR.PFB TNR.PF_ 10 11/22/1999 11:24 145785 BD3CE8BE TNR.PFM TN1.PF_ 18 11/22/1999 11:22 1103 474C4E38 TNRB.OFM TNRB.OF_ 18 11/22/1999 11:22 6825 BEC21108 TNRB.PFB TNRB.PF_ 10 11/22/1999 11:24 148564 FD47E0FF TNRB.PFM TNR1.PF_ 18 11/22/1999 11:22 1112 604493E3 TNRBI.OFM TNRBI.OF_ 18 11/22/1999 11:22 6839 6E19C7B5 TNRBI.PFB TNRBI.PF_ 9 11/22/1999 11:24 159652 798E8739 TNRBI.PFM TNRB1.PF_ 18 11/22/1999 11:22 1118 62DE75CD TNRI.OFM TNRI.OF_ 18 11/22/1999 11:22 6830 23B85EEE TNRI.PFB TNRI.PF_ 10 11/22/1999 11:24 157010 AE81357B TNRI.PFM TNR2.PF_ 18 11/22/1999 11:22 1114 67AE659D TR.KBL TR.KB_ 18 10/12/2000 16:00 962 4F79408D TR440.KBL TR440.KB_ 18 10/12/2000 16:00 1042 DE3CC0BA TRACE.DOC TRACE.DO_ 17 09/05/2000 12:11 64057 95DDD40E TRACE.EXE TRACE.EX_ 16 11/15/2000 19:39 56064 D4E7C200 TRACEDLL.DLL TRACEDLL.DL_ 15 10/06/2000 21:11 46987 C2341404 TRACEFMT.EXE TRACEFMT.EX_ 12 11/15/2000 15:45 232067 3106C9B9 TRACEGET.EXE TRACGET1.EX_ 17 10/06/2000 21:10 29930 05569661 TRACEGET.EXE TRACEGET.EX_ 17 10/06/2000 21:10 29930 05569661 TRAPDUMP.EXE TRAPDUMP.EX_ 17 10/06/2000 21:17 30236 B9939FF7 TRAPLOG.EXE TRAPLOG.EX_ 17 10/06/2000 21:17 28191 F269D507 TRC0000.TFF TRC0000.TF_ 18 11/15/2000 17:11 189 78DB263E TRC0001.TFF TRC0001.TF_ 18 11/24/1999 13:02 1370 17F81D51 TRC0003.TFF TRC0003.TF_ 18 11/15/2000 17:11 1503 79DD8690 TRC0004.TFF TRC0004.TF_ 18 11/15/2000 17:11 4754 4562826C TRC0005.TFF TRC0005.TF_ 17 11/15/2000 17:11 49321 E063153B TRC0006.TFF TRC0006.TF_ 18 11/15/2000 17:11 12356 B055674E TRC0007.TFF TRC0007.TF_ 18 11/15/2000 19:58 3336 601FB047 TRC0008.TFF TRC0008.TF_ 18 08/14/2000 18:04 544 467A3ED2 TRC0010.TFF TRC0010.TF_ 18 11/15/2000 16:50 13647 C63AD6DD TRC0012.TFF TRC0012.TF_ 18 11/15/2000 18:31 1247 4B138575 TRC0016.TFF TRC0016.TF_ 18 11/15/2000 16:50 1673 8106FBAA TRC0017.TFF TRC0017.TF_ 18 11/15/2000 16:50 5561 28B3BD66 TRC0018.TFF TRC0018.TF_ 18 11/15/2000 16:50 39488 6DC61365 TRC006D.TFF TRC006D.TF_ 18 10/06/2000 09:16 24181 FB89BB28 TRC00C0.TFF TRC00C0.TF_ 3 10/19/2000 21:04 15970 172D7C66 TRC00C2.TFF TRC00C2.TF_ 17 10/19/2000 21:04 25994 38380A06 TRC00C3.TFF TRC00C3.TF_ 18 10/19/2000 21:04 3984 496F4ABD TRC00C4.TFF TRC00C4.TF_ 18 10/19/2000 14:34 288 6225B2A4 FixPak Corrective Service levels and disk layouts 52  December 4, 2000 - Warp 4 FixPak XR_M015 TRC00C5.TFF TRC00C5.TF_ 17 10/19/2000 12:38 32994 87067818 TRC00C6.TFF TRC00C6.TF_ 18 11/14/2000 17:58 7146 F49C8681 TRC0100.TFF TRC0100.TF_ 18 11/15/2000 17:11 7219 FB080949 TRC0101.TFF TRC0101.TF_ 17 11/15/2000 17:11 7968 B4168FEE TRC0102.TFF TRC0102.TF_ 17 11/15/2000 17:11 29256 51C17755 TRC0103.TFF TRC0103.TF_ 18 11/15/2000 17:11 9590 88F67449 TRC0104.TFF TRC0104.TF_ 18 11/15/2000 17:11 5134 61087F62 TRC0105.TFF TRC0105.TF_ 18 11/15/2000 17:11 24421 FE711FDC TRC0106.TFF TRC0106.TF_ 18 11/15/2000 17:11 1549 FBDE5090 TRC0108.TFF TRC0108.TF_ 18 11/15/2000 17:11 9505 42F6E19A TRC0109.TFF TRC0109.TF_ 18 11/15/2000 17:11 2535 CF7DB3E4 TRC010A.TFF TRC010A.TF_ 18 11/15/2000 17:11 1130 33D8C181 TRC0118.TFF TRC0118.TF_ 18 10/06/2000 13:51 2526 46CE4B05 TRC0119.TFF TRC0119.TF_ 18 10/06/2000 14:07 3786 6E20F20C TRC012C.TFF TRC012C.TF_ 18 10/19/2000 21:13 5361 CD6B9471 TRC012D.TFF TRC012D.TF_ 18 10/19/2000 21:12 7870 4DF5F2E1 TRC012E.TFF TRC012E.TF_ 18 11/15/2000 03:02 32972 8DAC7F62 TRCFORMT.DLL TRCFORMT.DL_ 17 09/05/2000 16:46 26647 18BC7E3C TRCUST.EXE TRCUST.EX_ 15 11/15/2000 15:41 98773 190806C1 TREE.COM TREE.CO_ 16 11/15/2000 19:35 34185 A1D5AEBA TRSPOOL.DOC TRSPOOL.DO_ 18 11/22/1999 11:25 6638 7C5EA5A2 TRSPOOL.EXE TRSPOOL1.EX_ 17 10/06/2000 21:10 42054 66643F12 TRSPOOL.EXE TRSPOOL.EX_ 10 10/06/2000 21:10 42054 66643F12 TRSTOP.EXE TRSTOP.EX_ 17 10/06/2000 21:10 23486 4BEB79C7 TRUETYPE.DLL TRUETYPE.DL_ 12 04/12/2000 11:40 128567 2661D3D5 UA.KBL UA.KB_ 18 10/12/2000 16:00 1476 755F2EED UCDFS.DLL UCDFS.DL_ 17 09/05/2000 16:38 13264 D114D77D UCONV.DLL UCONV.DL_ 17 10/12/2000 16:00 22819 052AEC7F UHPFS.DLL UHPFS.DL_ 14 10/06/2000 14:03 104976 A090B430 UK.KBL UK.KB_ 18 10/12/2000 16:00 816 0BA7B2C7 UK168.KBL UK168.KB_ 18 10/12/2000 16:00 850 56B6D36E ULSACT01.MSG ULSACT01.MS_ 18 10/12/2000 15:52 907 CD793741 ULSCAU01.MSG ULSCAU01.MS_ 18 10/12/2000 15:52 899 5C22952F ULSDET01.MSG ULSDET01.MS_ 11 10/12/2000 15:52 903 A12BE1BE ULSERR01.MSG ULSERR01.MS_ 18 10/12/2000 15:52 1967 A7B3FAC9 UNDELETE.COM UNDELETE.CO_ 16 11/15/2000 19:39 36953 0D5A6E8C UNICODE.SYS UNICODE.SY_ 17 10/12/2000 16:00 20014 4983D17F UNIKBD.DLL UNIKBD.DL_ 16 10/12/2000 16:00 28291 EDE015C1 UNINSTAL.EXE UNINSTAL.EX_ 8 07/13/2000 11:04 97177 80B59DB1 UNPACK2.EXE UNPACK2.EX_ 14 11/15/2000 20:05 79888 594A2DC9 USER.EXE USER.EX_ 6 12/02/1999 16:42 281088 453F4D7A USINTER.KBL USINTER.KB_ 18 10/12/2000 16:00 1032 BCA4C15F VBIOS.SYS VBIOS.SY_ 18 11/23/1999 09:17 8816 604099BA VCMOS.SYS VCMOS.SY_ 18 11/23/1999 09:17 2272 93B68EC4 VDMA.SYS VDMAPS2.SY_ 17 11/23/1999 09:17 14329 80562837 VDMA.SYS VDMAAT.SY_ 17 11/23/1999 09:17 11465 50ECE743 VDPMI.SYS VDPMI.SY_ 17 11/23/1999 09:18 30626 DD025F18 VDPX.SYS VDPX.SY_ 17 11/23/1999 09:19 26322 2A1ABE9B VGA.DSP VGA.DS_ 18 09/05/2000 11:59 8731 1FA1842C VIDEOCFG.DLL VIDEOCFG.DL_ 15 09/15/2000 16:08 38126 0315EFBC VIEW.EXE VIEW.EX_ 16 10/19/2000 13:01 33304 85781F60 FixPak Corrective Service levels and disk layouts 53  December 4, 2000 - Warp 4 FixPak XR_M015 VIOCALLS.DLL VIOCALLS.DL_ 18 10/19/2000 14:01 2048 E44756F1 VIOTBL.DCP VIOTBL.DC_ 16 10/12/2000 16:00 225355 40375D9E VIOTBL.ISO VIOTBL.IS_ 16 10/12/2000 16:00 230105 26DA121C VMAN.DLL VMAN.DL_ 5 09/15/2000 22:04 46745 B2C3BA5A VMANWIN.SYS VMANWIN.SY_ 18 07/10/2000 14:07 3040 C2F3E282 VPIC.SYS VPIC.SY_ 17 11/23/1999 09:20 9942 C81F32E4 VPICPARM.SYS VPICPARM.SY_ 18 11/23/1999 09:20 736 8F551DBB VTIMER.SYS VTIMER.SY_ 17 11/23/1999 09:20 10560 68AF4518 VW32S.SYS VW32S.SY_ 6 11/23/1999 09:22 18338 52CBEA9A VWIN.SYS VWIN.SY_ 17 11/23/1999 09:21 27104 94AE4806 WCFGMRI.DLL WCFGMRI.DL_ 18 11/14/2000 17:55 6182 FD1F8141 WD24B.DSP WD24B.DS_ 18 09/05/2000 11:59 32662 66AE35CF WELCMMRI.DLL WELCMMRI.DL_ 17 11/14/2000 18:12 14409 A1CE1A73 WINCFG.DLL WINCFG.DL_ 17 11/15/2000 03:03 13379 5D959672 WINFILE.EXE WINFILE.EX_ 13 12/02/1999 16:31 146960 225456E2 WINSCLIP.DLL WINSCLIP.DL_ 17 12/02/1999 16:27 14848 063E037D WINSDDE.DLL WINSDDE.DL_ 17 12/02/1999 16:27 18432 A6BD0F73 WINSHELD.EXE WINSHELD.EX_ 17 12/02/1999 16:27 22528 F1802A0D WINSMSG.DLL WINSMSG.DL_ 17 12/02/1999 16:27 28441 ED6CB51E WPCLS.IMP WPCLS.IM_ 18 09/06/2000 12:42 8661 DA1CAFC2 WPCOMET.DLL WPCOMET.DL_ 18 10/19/2000 12:52 8656 D885A792 WPCONFIG.DLL WPCONFIG.DL_ 8 11/14/2000 17:54 266408 01860F35 WPCONMRI.DLL WPCONMRI.DL_ 17 11/14/2000 17:55 32304 2831E945 WPDSRVP.DLL WPDSRVP.DL_ 2 11/14/2000 18:05 14194 8F0C425E WPHELP.HLP WPHELP.HL_ 5 02/24/2000 15:36 841366 24FE714B WPINET.DLL WPINET.DL_ 13 11/15/2000 03:10 117180 42DCEA66 WPINTMRI.DLL WPINTMRI.DL_ 17 11/14/2000 18:05 11324 F073EB60 WPMSG.HLP WPMSG.HL_ 16 11/13/2000 07:24 50198 98E8EB75 WPPRINT.DLL WPPRINT.DL_ 2 11/14/2000 19:32 364102 71DB918B WPPRINT.HLP WPPRINT.HL_ 15 11/14/2000 17:57 71408 17006E06 WPPRTMRI.DLL WPPRTMRI.DL_ 15 11/14/2000 17:57 66683 300DA06D WPREXX.IMP WPREXX.IM_ 18 09/06/2000 12:42 6313 5075963F WPSINIT.WPS WPSINIT.WP_ 9 09/06/2000 12:42 15877 ACB13059 WPSINST.CMD WPSINST.CM_ 18 09/06/2000 12:42 2813 7D4D1420 WW.EXE WW.EX_ 18 07/16/1998 14:31 11377 F8082A19 WWDLL.DLL WWDLL.DL_ 8 12/21/1997 01:29 276981 9F80E623 WWHOOK.DLL WWHOOK.DL_ 17 12/21/1997 01:29 27230 5071DBC4 XCOPY.EXE XCOPY.EX_ 16 11/15/2000 19:36 52576 E9190D47 XPG00420.TBL XPG00420.TB_ 18 11/22/1999 12:17 27264 48667C1E XPG00864.TBL XPG00864.TB_ 8 11/22/1999 12:17 27264 76725C6C ************************************************************************ Product location on CSD: A:\FIX\OS2.2 Product name: "IBM OS/2 Base Operating System" Standard Edition 4.00 Fixpak name: XR_M015_ (Country = Generic) Pre-requisite CSD Level: XR_4000_ System Id: 1000 Component Id: 5639A6100 Archive is ON for this product. ________________________________________________________________________ FixPak Corrective Service levels and disk layouts 54  December 4, 2000 - Warp 4 FixPak XR_M015 Default directories: ..\..\ ..\* ..\..\MMOS2 ..\..\MMOS2\* ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- OS2LDR OS2LDR.___ 18 11/15/2000 18:05 45056 FEEF30B9 ************************************************************************ Product location on CSD: A:\FIX\OS2.3 Product name: "IBM OS/2 Base Operating System" Standard Edition 4.01 Fixpak name: XR_M015_ (Country = Generic) Pre-requisite CSD Level: XR_4010_ System Id: 1000 Component Id: 5639A6100 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* ..\..\MMOS2 ..\..\MMOS2\* ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- APPDBUTL.DLL APPDBUTL.DL_ 18 02/25/2000 12:15 25015 46879016 APPSTART.EXE APPSTART.EX_ 18 02/25/2000 12:15 33858 D7711D28 NCAPPUTL.EXE NCAPPUTL.EX_ 18 02/25/2000 12:15 14624 29FB65C8 FixPak Corrective Service levels and disk layouts 55  December 4, 2000 - Warp 4 FixPak XR_M015 OS2LDR OS2LDR.___ 18 11/15/2000 18:06 45056 8EE0F746 PMLOGON.EXE PMLOGON.EX_ 18 01/24/2000 11:20 40109 5D5B81C3 PRNCFG.DLL PRNCFG.DL_ 18 01/24/2000 11:21 58258 E0003042 TDESK.DLL TDESK.DL_ 18 01/25/2000 01:53 6653 0CA23661 TLOGOFF.EXE TLOGOFF.EX_ 18 01/25/2000 01:53 9581 388C409D TOBJECT.DLL TOBJECT.DL_ 18 01/25/2000 01:53 7312 887F372F TSHUTDWN.EXE TSHUTDWN.EX_ 18 01/25/2000 01:53 8695 FEBAC1E2 ************************************************************************ Product location on CSD: A:\FIX\OS2.4 Product name: "IBM OS/2 Base Operating System" Standard Edition 4.01 Fixpak name: XR_M015_ (Country = Generic) Pre-requisite CSD Level: XR_4010_ System Id: 1000 Component Id: 5639A6120 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* ..\..\MMOS2 ..\..\MMOS2\* ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- APPSTART.EXE APPSTART.EX_ 18 03/22/2000 10:08 35022 D8F2F43F NCAPPUTL.EXE NCAPPUTL.EX_ 18 03/22/2000 10:08 21270 DAA7210D NCMONIT.DLL NCMONIT.DL_ 18 07/17/2000 14:14 54395 D9BF3C32 OS2LDR OS2LDR.___ 18 11/15/2000 18:06 45056 8EE0F746 PMLOGON.EXE PMLOGON.EX_ 18 07/17/2000 15:34 57813 452101DF TSHUTDWN.EXE TSHUTDWN.EX_ 18 02/15/2000 12:41 10795 F1099ADA FixPak Corrective Service levels and disk layouts 56  December 4, 2000 - Warp 4 FixPak XR_M015 10.0 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 22MB Drive with most free space, holds deferred files if A:SERVICE method used. Up to 38MB FixPak Archive/Backup for product with CSD level of XR_4000 Up to 38MB FixPak Archive/Backup for product with CSD level of XR_4010 Note: The lines labeled "FixPak Archive/Backup for product with CSD level of" will be on the drive you specify and will occupy up to the size indicated for the Archive and for the Backup directories. If, for example, the indicated size is 30MB then the space actually occupied on the drive can be up to 60MB. 10.0.1 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 57  December 4, 2000 - Warp 4 FixPak XR_M015 10.0.2 TRADEMARKS The following terms are trademarks of the International Business Machines Corporation in the United States or other countries or both: Ž IBM Ž OS/2 Ž WorkSpace On-Demand Other company, product, and service names may be trademarks or service marks of others. Space Utilization 58