< Installation instructions for Warp FixPak XR_W043 October 18, 2000 This FixPak makes the products it services Year 2000 ready Build level 8.267 This FixPak applies to: XR_3005 Warp Server XR_3006 Warp Server SMP 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. October 18, 2000 - Warp 3 FixPak XR_W043 October 18, 2000 - Warp 3 FixPak XR_W043 CONTENTS 1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1 2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2 3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3 3.0.1 Out of memory or System error SYS0008 - Warp Server SMP . . 3 3.0.2 Device Drivers removed from Fixpak . . . . . . . . . . . . . 3 3.0.3 Please use Fixtool f.141 or later . . . . . . . . . . . . . 3 3.0.4 Can't install Warp 3 . . . . . . . . . . . . . . . . . . . . 3 3.0.5 OS2DUMP split into two versions . . . . . . . . . . . . . . 4 3.0.6 Using Display Recovery Choices . . . . . . . . . . . . . . . 5 3.0.7 DSPINSTL.EXE failure . . . . . . . . . . . . . . . . . . . . 5 3.0.8 Additional diskette image for Warp v3 FixPaks . . . . . . . 5 3.0.9 Windows printer drivers leave a zombie thread running . . . 6 3.0.10 Updated Corrective Service Facility (CSF) . . . . . . . . . 6 3.0.11 Syslevel Correction Programs . . . . . . . . . . . . . . . 7 3.0.12 If Installing on a Preloaded System . . . . . . . . . . . . 7 3.0.13 Newer file on harddisk than is in FixPak . . . . . . . . . 7 3.0.14 CSF0208 No products were found . . . . . . . . . . . . . . 8 3.0.15 CSF0248 Archive path is shared between mismatched . . . . . 8 3.0.16 CSF0249 Error opening or creating archive file. . . . . . 8 3.0.17 Configuration Installation Distribution ( CID ) . . . . . . 8 3.0.18 Read-Only files . . . . . . . . . . . . . . . . . . . . . . 9 3.0.19 DATABASE files removed from FixPak . . . . . . . . . . . . 9 4.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 10 4.0.1 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 10 4.0.2 IPE on boot after FixPak 35 installed on UNI systems . . . 10 4.0.3 Installation of Java 1.1.4 or Java 1.1.6 . . . . . . . . . 11 4.0.4 Files removed from FixPaks (33 and up) . . . . . . . . . . 11 4.0.5 DSPRES.DLL included in FixPaks . . . . . . . . . . . . . . 11 4.0.6 DOSCALL1.DLL Trap on Thinkpads that use MWAVE . . . . . . . 11 4.0.7 Trap D or E in LAN Distance . . . . . . . . . . . . . . . . 12 4.0.8 Screen corruption using Lotus Notes 4.1 . . . . . . . . . . 12 4.0.9 Dell machines and font editing . . . . . . . . . . . . . . 13 5.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.1 SES supported on SMP with FP38 or later . . . . . . . . . . . . 14 5.2 Querying file dates for files after Dec 31, 1999 in REXX . . . 14 5.3 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 15 5.4 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 15 5.5 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.5.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 16 5.5.2 Where euro is not supported . . . . . . . . . . . . . . . . 17 5.5.3 Printing the euro . . . . . . . . . . . . . . . . . . . . . 18 5.6 New Print fuctions . . . . . . . . . . . . . . . . . . . . . . 18 5.7 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.8 If you have installed OpenDoc . . . . . . . . . . . . . . . . . 19 Contents ii October 18, 2000 - Warp 3 FixPak XR_W043 5.9 Joliet-2 support in CDFS.IFS . . . . . . . . . . . . . . . . . 19 5.10 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 20 5.10.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 20 5.10.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 22 5.11 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 22 5.11.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 23 5.11.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.12 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.13 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.14 Other README files . . . . . . . . . . . . . . . . . . . . . . 24 5.15 Reserve Drive Letters Added . . . . . . . . . . . . . . . . . 25 5.16 What is the SIQ (Single Input Queue) feature . . . . . . . . . 26 5.16.1 How it works . . . . . . . . . . . . . . . . . . . . . . . 26 5.17 Common File Dialog Interface changes . . . . . . . . . . . . . 27 6.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 28 6.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 28 6.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 28 6.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 28 7.0 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 30 8.0 LAN Server/Warp Server Remote IPL Considerations . . . . . . . 31 9.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 33 9.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 33 9.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 33 9.3 Method 2: Boot from Corrective Service Disk 1. . . . . . . . . 35 9.4 Additional Corrective Service Facility information . . . . . . 35 10.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . 36 10.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 37 11.0 FixPak Corrective Service levels and disk layouts . . . . . . 38 12.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 58 13.0 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . . . 59 14.0 Recovering from problems . . . . . . . . . . . . . . . . . . . 60 Contents iii October 18, 2000 - Warp 3 FixPak XR_W043 1.0 TERMS AND CONDITIONS Important - please read the following terms and conditions. Downloading the Service Fixes included in FixPak XR_W043 for OS/2 Warp 3 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 3. 2. You may make copies of the OS/2 Service Fixes equal to the number of licensed copies of OS/2 Warp 3 you possess. 3. You may only use the OS/2 Warp 3 Service Fixes included with FixPak XR_W043 for maintenance purposes. 4. All other terms and conditions of your OS/2 Warp 3 license agreements apply to the Service Fixes; however, this does not extend any warranty and/or services, including but not limited to the "Initial Installation" period, outlined in such agreements. Terms and Conditions 1 October 18, 2000 - Warp 3 FixPak XR_W043 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 October 18, 2000 - Warp 3 FixPak XR_W043 3.0 INSTALLATION NOTES 3.0.1 OUT OF MEMORY OR SYSTEM ERROR SYS0008 - WARP SERVER SMP 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.2 DEVICE DRIVERS REMOVED FROM FIXPAK Beginning with Warp 4 FixPak XR_M011 and Warp 3 FixPak XR_W041, 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. To avoid potential Device Driver problems with the installation of Warp 4 FixPak XR_M011 and Warp 3 FixPak XR_W041, your system should be at FixPak level XR_M005 or higher for Warp 4 and XR_W032 or higher for Warp 3. 3.0.3 PLEASE USE FIXTOOL F.141 OR LATER Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use Corrective Service Facility f.141 or later. It has fixes for problems found in the F.138B and F.139 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 40 and 10) and type 2 (FixPaks 40 and 10 and later) FixPaks. If you try to use a CSF level prior to F.138B you will get a "CSF0208 No products were found on the target system to service" message. 3.0.4 CAN'T INSTALL WARP 3 If you can't get Warp 3 installed, check the OS/2 Device Driver Pak Online at: Installation Notes 3 October 18, 2000 - Warp 3 FixPak XR_W043 http://service.software.ibm.com/os2ddpak/readme.htm#disk1 for the latest available device drivers to update your Installation disks with. 3.0.5 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 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. Installation Notes 4 October 18, 2000 - Warp 3 FixPak XR_W043 3.0.6 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. 3.0.7 DSPINSTL.EXE FAILURE DSPINSTL.EXE may fail when installing OEM versions of non-IBM video device drivers. For Uni-processor versions of Warp, the archived version of the file can be used as a workaround. For SMP versions, contact IBM for a temporary fix. A subsequent FixPak will correct this problem. 3.0.8 ADDITIONAL DISKETTE IMAGE FOR WARP V3 FIXPAKS We've added an additional diskette image to Warp v3 FixPaks. This disk contains the directories and tools previously found on the last FixPak disk. This disk may contain the following: Ž BETA Ž DIR_ONE Ž DIR_TWO Ž SYSLEVEL Ž FIXSYSL.CMD (US only) Ž SYSZMPM.CMD (non-US only) Ž UPDTRIPL.EXE Note: This DOES NOT increase the size of the FixPak Installation Notes 5 October 18, 2000 - Warp 3 FixPak XR_W043 The SYSLEVEL directory contains corrected SYSLEVEL files for National Language Versions (NLV) of Warp v3 products. The directory names have the following meanings: Ž Directory Product Ž --------- ------------------------------------------------------- Ž WARPSRV XR_3005 Warp Server Ž WRPSVSMP XR_3006 Warp Server SMP 3.0.9 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING A problem occurs with some Windows printer drivers where a zombie thread is left running after the program that loaded it is exited. This does not occur when the program is run from a Seamless instance of PROGMAN or from a Full Screen session because when these are exited the whole WINOS2 Subsystem is exited. This problem has been reported for the Adobe and Hewlett Packard Windows printer drivers. To correct this problem for people running with these drivers ONLY who have experienced symptoms such as: Ž exiting a program running seamlessly after printing or Ž setting up a printer and seeing the icon not being unhatched and/or Ž not being able to start another copy of the program Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot* section: Ž backgroundtasks=run_enum.exe,hpfbkg02.exe then restart WINOS2. Note: There may be other drivers that have the same problem. If you experiences a similar problem with other drivers, please report it so the correct SYSTEM.INI entry can be determined. 3.0.10 UPDATED CORRECTIVE SERVICE FACILITY (CSF) Use CSF level f.141 or later for all Fixpaks. It is contained in CS_140.EXE. This is a self-extracting ZIP file. It is not and does not contain bootable disks. See the READ.ME file for instructions on how to boot with diskettes along with a lot of other useful information. Installation Notes 6 October 18, 2000 - Warp 3 FixPak XR_W043 3.0.11 SYSLEVEL CORRECTION PROGRAMS The FIXSYSL.CMD, located on the last disk of US FixPaks, is included for: 1. Warp systems that have applied an S3 video pak and the Current CSD level is XR02110 (execute the syslevel command to find out); 2. APTIVA systems with a Current CSD level XR03005, Compid 562260100, Type WP. This program will set the Current CSD level to XR03002. Please run the FIXSYSL program before installing this FixPak. The SYSZMPM.CMD, located on the last disk of non-US FixPaks, is included for: 1. Warp Server SMP systems that have a Current CSD Level of XR06200 and a Prior CSD Level of UN09407 in the \MMOS2\INSTALL\SYSLEVEL.MPM file. 2. Other Warp systems with incorrect Multimedia syslevel files. This program will set the Current CSD level to XR03006 to allow service to be applied to Multimedia files. Please run the SYSZMPM program before installing this FixPak on Warp Server SMP systems. 3.0.12 IF INSTALLING ON A PRELOADED SYSTEM Installing this FixPak on systems that were preloaded may cause a pop-up to occur that is invalid. The pop-up claims that the following files have a more recent date and/or version than the ones contained on your system: MMOS2\DLL\IOPRNLS.DLL MMOS2\DLL\AMPMXMCD.DLL MMOS2\DLL\AUDIOMCD.DLL MMOS2\DLL\AUDIOSH.DLL MMOS2\DLL\MMPM.DLL OS2\INSTALL\SYSLEVEL.SUC The proper action is to allow the FixPak installation to overwrite these files with the ones supplied by the FixPak. 3.0.13 NEWER FILE ON HARDDISK THAN IS IN FIXPAK If you get a popup stating that a newer file exists on your harddisk than is in the FixPak. press the "OK" button unless you know for sure the file on your harddisk is newer than the one in the Fixpak. Installation Notes 7 October 18, 2000 - Warp 3 FixPak XR_W043 3.0.14 CSF0208 NO PRODUCTS WERE FOUND 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.15 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.16 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. 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.17 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 8 October 18, 2000 - Warp 3 FixPak XR_W043 3.0.18 READ-ONLY FILES If you installed OS/2 Warp 3.0 from a CD-ROM, some files being updated may have the Read-Only attribute set. This will cause the update program to ask you if you want the files replaced. Answer OK. 3.0.19 DATABASE FILES REMOVED FROM FIXPAK DATABASE.TXT and DATABASE.DAT files have been removed from FixPak 29 and will be left out of all future FixPaks. They are used to control the Notebook settings for migrated applications during initial install or selective install. This has been done to protect customers who have customized these files. Installation Notes 9 October 18, 2000 - Warp 3 FixPak XR_W043 4.0 POST INSTALLATION NOTES 4.0.1 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.2 IPE ON BOOT AFTER FIXPAK 35 INSTALLED ON UNI SYSTEMS If you experience a kernel trap (black screen trap) or get a messages stating that device drivers (such as CLOCK01.SYS) were not able to install at boot time do the following: 1. Reboot and press Alt-F1 when the white block appears 2. Select C for command line 3. From the command line enter: TEDIT CONFIG.SYS 4. Add the following statement to the end of CONFIG.SYS: TRACE=OFF,6 5. Reboot Note: DO NOT use major code 6 trace events either from CONFIG.SYS or from the command line. A fix for this problem will be placed on "ftp://service.boulder.ibm.com" in the "ps/products/os2/fixes/v3.0warp/english-us/xr_w035/" directory and the NCS Support News page at "http://ps.boulder.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa/fixnews.html" will be updated when the fix is available. Post Installation Notes 10 October 18, 2000 - Warp 3 FixPak XR_W043 4.0.3 INSTALLATION OF JAVA 1.1.4 OR JAVA 1.1.6 Installation of Java 1.1.4 or Java 1.1.6 on top of this FixPak will down-level portions of the ULS support if you are not using the 1.2.2 (or later) level of Feature Installer. If this occurs, Euro currency support will not work correctly. To recover, re-install this FixPak. This will allow both Java and Euro support to work correctly. 4.0.4 FILES REMOVED FROM FIXPAKS (33 AND UP) The following files, introduced in FixPak 26, have been merged into LOCALE.DLL and were removed from FixPak 33 and all future Warp 3 FixPaks. AR_AA.DLL EN_CA.DLL FR_CA.DLL LT_LT.DLL SH_BA.DLL BG_BG.DLL EN_GB.DLL FR_CH.DLL LV_LV.DLL SK_SK.DLL C.DLL EN_IE.DLL FR_FR.DLL MK_MK.DLL SL_SI.DLL CA_ES.DLL EN_NZ.DLL HR_HR.DLL NL_BE.DLL SQ_AL.DLL CS_CZ.DLL EN_US.DLL HU_HU.DLL NL_NL.DLL SR_SP.DLL DA_DK.DLL EN_ZA.DLL IS_IS.DLL NO_NO.DLL SV_SE.DLL DE_AT.DLL ES_ES.DLL IT_CH.DLL PL_PL.DLL TH_TH.DLL DE_CH.DLL ES_LA.DLL IT_IT.DLL PT_BR.DLL TR_TR.DLL DE_DE.DLL ET_EE.DLL IW_IL.DLL PT_PT.DLL UNIV.DLL EL_GR.DLL FI_FI.DLL JA_JP.DLL RO_RO.DLL ZH_CN.DLL EN_AU.DLL FR_BE.DLL KO_KR.DLL RU_RU.DLL ZH_TW.DLL Additionally, ENULS.MSG was removed from FixPak 33 (and up) as it is no longer needed. 4.0.5 DSPRES.DLL INCLUDED IN FIXPAKS DSPRES.DLL has been added to FixPak 35 and up for support of 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. 4.0.6 DOSCALL1.DLL TRAP ON THINKPADS THAT USE MWAVE After installing this FixPak on a Thinkpad that uses MWAVE and the LAN while in a docking station you may encounter a DOSCALL1.DLL trap after rebooting when the machine is undocked. A fix has been made to the MWAVE MWNOTOS2.EXE to correct this problem. The MWNOTOS2.EXE file can be found on the Internet along with a readme (.doc file) on how to replace the file. The location is: Post Installation Notes 11 October 18, 2000 - Warp 3 FixPak XR_W043 Point your Web browser at: ftp://www3.pc.ibm.com/pub/pccbbs/mobiles/mwnotos2.exe ftp://www3.pc.ibm.com/pub/pccbbs/mobiles/mwnotos2.doc 4.0.7 TRAP D OR E IN LAN DISTANCE If you get a Trap D or E in the MACFH$1 device driver, at offset 126C, while running LAN Distance, please call IBM Service for the LAN Distance APAR IC14228. 4.0.8 SCREEN CORRUPTION USING LOTUS NOTES 4.1 There is a screen corruption problem when running Lotus Notes 4.1 in 256 colors on OS/2. This problem has been corrected in version 4.1.2. Symptoms normally appear as anomilies in the fonts, such as parts of characters or entire characters disappearing. This corruption can occur at any resolution. Since this only occurs when using 256 colors, an immediate work around is to not use 256 colors. To change the number of colors displayed: 1. open the OS/2 System folder 2. open the System Setup folder 3. double click on the System icon in the System Setup folder 4. select a resolution that does not use 256 colors 5. close the folders 6. shutdown and reboot the machine The fix for this problem is in the display device drivers. IBM supported display device drivers will be available on the PCCBBS and Internet as "Controlled" fixes. You should contact the IBM PSP Software Solution Center at 1-800-992-4777 to obtain PCCBBS and Internet logon information for display device drivers needed. The build level should be 0.041 or above. See "Where Fixes can be found" for where display device drivers can be found once they have been publically released. Post Installation Notes 12 October 18, 2000 - Warp 3 FixPak XR_W043 4.0.9 DELL MACHINES AND FONT EDITING When editing fonts, users of Dell machines may discover a slight regression. When a font size is edited, the Font Palette is updated correctly; however, should users browse (select around) the palette, they might, at times, notice an inconsistency between the font size displayed on the palette and the one that is displayed on the font editor. In all cases, the font size displayed on the Font Palette is the correct size for the font when it is dragged to the target (for example, the desktop, folder, or application). Post Installation Notes 13 October 18, 2000 - Warp 3 FixPak XR_W043 5.0 NEW FUNCTION It is our policy not to include new function in FixPaks. However, as with any policy there may be exceptions. If any exception occurs in the future, we will communicate them to you in this section of the README.1ST. We apologize for not communicatiing this more clearly earlier and specifically for not including information on IBM Open32 in the FixPak 26 (and subsequent) README.1ST. 5.1 SES SUPPORTED ON SMP WITH FP38 OR LATER SES is supported on systems running Warp Server SMP once FixPak 38 or later is installed. You can get the IBM OS/2 Security Enabling Services from the Web at: ftp://service.boulder.ibm.com/ps/products/os2/warp.update.kit/warpses/ 5.2 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 exisiting 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: New Function 14 October 18, 2000 - Warp 3 FixPak XR_W043 /********************************************/ /* 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 5.3 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD) GRADD is supported on all Warp 3 releases beginning with FixPak 35. 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.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 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 New Function 15 October 18, 2000 - Warp 3 FixPak XR_W043 Always refer to README.DBG for details of any RAS enhancements delivered with a FixPak. 5.5 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.5.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. 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) New Function 16 October 18, 2000 - Warp 3 FixPak XR_W043 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 it142 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.5.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: 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. New Function 17 October 18, 2000 - Warp 3 FixPak XR_W043 5.5.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.6 NEW PRINT FUCTIONS The following print functions have been added starting at FixPak XR_W031 level: Ž Allow moving a print job from one print server to another server. Ž Allow moving all print jobs at once. Ž Define a backup print queue so that when a printer has problems, all jobs will be sent to a backup print queue if the problem persists for a specified number of minutes. Ž When creating a network print object, user will be prompted to create a WINOS2 print configuration. 5.7 IBM OPEN32 Open32 is a new API set provided in OS/2 Warp 3 beginning with FixPak 26 to help ISVs migrate their Windows 32-bit applications to OS/2. Approximately 750 APIs from the Win32 API set are included and provide essentially the same functionality as the Windows NT 3.51 APIs of the same name. Applications such as Lotus SmartSuite 96 are enable by this set of APIs. It is required that Open32 support be installed on OS/2 Warp 3 systems that have FixPak 26 or higher installed. The Open32 code requires 20MB of disk space on your OS/2 Warp 3 boot drive. New Function 18 October 18, 2000 - Warp 3 FixPak XR_W043 It also creates a new \LANGUAGE directory on your boot drive and adds SET ULSPATH=x:\LANGUAGE to CONFIG.SYS (x: is your boot drive). If you are installing this FixPak on a machine that has an older version of IBM Open32 (formerly known as Developer API Extensions or DAX) from either FixPak 17 Special Edition or DevCon 9, then you must uninstall the older version of Open32 before starting to install this new version. If you no longer have the CD or diskettes to uninstall the older version of Open32 then you must follow these steps: 1. In config.sys, delete the following line: RUN=x:\OS2\RSRV.EXE where x: is your boot drive. 2. Reboot your system 3. Delete the following files from your machine, where x: is your boot drive. x:\boot.dat x:\registry.dat x:\dos.dat x:\os2\rsrv.exe x:\os2\install\inst_dos.exe x:\os2\install\reginit exe 5.8 IF YOU HAVE INSTALLED OPENDOC If you have installed OpenDoc parts for Multimedia and you wish to keep your OpenDOc support then DO NOT update Multimedia at all. To do this, use the A:\SERVICE installation method and do not select Multimedia as a product to be serviced. 5.9 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. New Function 19 October 18, 2000 - Warp 3 FixPak XR_W043 5.10 NEW (IMPROVED) CHKDSK This new 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.10.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. 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. New Function 20 October 18, 2000 - Warp 3 FixPak XR_W043 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. 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. New Function 21 October 18, 2000 - Warp 3 FixPak XR_W043 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 Note: CHKDSK.COM, CHKDSK32.DLL and UHPFS.DLL from FixPak 30 will not work on a Warp system with a service level prior to FixPak 29. This is because of a new pack program introduced at FixPak 29 level. 5.10.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: 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.11 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. New Function 22 October 18, 2000 - Warp 3 FixPak XR_W043 The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used to control trap screen behavior (see below). 5.11.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.11.2 TRAPLOG The TRAPLOG command allows dynamic control of trap information logging. The command syntax is: TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS] where: Ž x: specifies that trap information is to be logged in x:\POPUPLOG.OS2, x: being any partition drive letter. Ž NOLOG disables logging of trap information. Ž POPUPS enables the trap information pop-up message (SYS3175). Ž NOPOPUPS disables the trap information pop-up message. 5.12 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. New Function 23 October 18, 2000 - Warp 3 FixPak XR_W043 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.13 SYSDUMP The SYSDUMP command forces a System Dump to be initiated, regardless of the TRAPDUMP settings. This command is provided for the use of service personnel to allow Dump Initiation to be automated through use of a command file. Warning: The initiation of a System Dump causes an immediate termination of the system without any shutdown. No file system shutdown is performed. The system behaves as if a fatal crash has occurred thus under rare circumstances data can be lost. The command syntax is: SYSDUMP [/NOPROMPT] 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.14 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. New Function 24 October 18, 2000 - Warp 3 FixPak XR_W043 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). 5.15 RESERVE DRIVE LETTERS ADDED The Reserve Drive Letters feature has been added at Warp FixPak level XR_W024 for Uni Processor versions of Warp 3. It is not included in the SMP (Symmetric Multi Processors) version of Warp 3. A modification has been made to the OS/2 kernel that will allow the user to specify, through a CONFIG.SYS parameter, specific drive letters that will not be allocated for local block mode devices during the processing of CONFIG.SYS. Currently, all versions of OS/2 assign drive letters sequentially starting from drive C: for all local devices or disk partitions. Any network use of drive letters starts after the last drive letter used for local devices/partitions. RESERVEDRIVELETTER can be used to force a specific drive letter to be allocated to a network drive or a CDROM for example. SYNTAX: RESERVEDRIVELETTER=x, where "x" is letter D thru Z. Note: Multiple RESERVEDRIVELETTER statements are allowed but only the last one is used. During the processing of CONFIG.SYS, OS/2 allocates drive letters for all BASEDEV= statements. In general, the only BASEDEV= statements that allocate drive letters are those for the Disk Device Driver, which will allocate 1 drive letter sequentially for each local disk partition. Three local disk partitions would allocate C:,D:,E:. After processing BASEDEV= statements, the system will honor the RESERVEDRIVELETTER statement(s). If the RESERVEDRIVELETTER statement conflicts with any drive letter already assigned to a local disk partition, an error message will be generated and that RESERVEDRIVELETTER statement will be ignored. New Function 25 October 18, 2000 - Warp 3 FixPak XR_W043 The next processing occurs for DEVICE= statements. DEVICE= statements for local block mode devices will assign drive letters, starting sequentially immediately after the highest drive letter specified in a RESERVEDRIVELETTER statement. Examples of local devices which use drive letters are CDROM, R/W OPTICAL, TAPE, Virtual Disks (VDISK). EXAMPLE: User has 2 local disk partitions, wants the E: drive letter to be used as a network drive, has both a CDROM and a R/W optical drive, and wants the CDROM drive letter to be K:. Specify a RESERVEDRIVELETTER=J statement and insure that the DEVICE= statement for the CDROM preceeds the DEVICE= statement for OPTICAL in CONFIG.SYS. Note that all drive letters between E and J will be available for use by programs or device drivers, which allocate drive letters for non-local use like network redirectors. 5.16 WHAT IS THE SIQ (SINGLE INPUT QUEUE) FEATURE The "SIQ" feature is new with FixPak XR_W017. It allows the user to take focus away from an application that is monopolizing the message queue. When the FixPak is installed, the SIQ feature is disabled (OFF). 5.16.1 HOW IT WORKS When you request a focus change for example, by clicking on another application or pressing Ctl+Esc the application that has the focus should respond to the message in x milliseconds. If the application does not respond within that time, OS/2 determines that the application is not responding to messages and flags the application queue as bad. It then switches focus to the desired application. OS/2 will monitor the queue marked as bad to see when it does start responding to messages. It will mark the queue as good when this occurs. To enable the SIQ feature, put a SET PM_ASYNC_FOCUS_CHANGE statement in CONFIG.SYS and reboot. The parameters to the SET command are: SET PM_ASYNC_FOCUS_CHANGE=ON | ON x | OFF The default is OFF (disabled). To turn it on (enable) put the following in the CONFIG.SYS file and reboot: SET PM_ASYNC_FOCUS_CHANGE=ON New Function 26 October 18, 2000 - Warp 3 FixPak XR_W043 To change the timeout value put the following in the CONFIG.SYS file and reboot: SET PM_ASYNC_FOCUS_CHANGE=ON x where x is in milliseconds (default is 2000 (2 seconds)) If you think you are having problems with SIQ, a way to isolate a problem is to raise the timeout to 5000 milliseconds (5 seconds). If that does not help, turn it off. If there is a SIQ feature problem, this will help us (IBM) isolate it. 5.17 COMMON FILE DIALOG INTERFACE CHANGES Beginning with FixPak XR_W017, the Common File Dialog interface has been rearranged to improve usability. The changes are: Ž "Type of file" field moved below the Open filename. Ž "Drive" and "Directory" controls were swapped with the "File" control. New Function 27 October 18, 2000 - Warp 3 FixPak XR_W043 6.0 CORRECTIVE SERVICE FACILITY 6.0.1 REQUIRED CSF LEVEL You must use release level f.143 or later of the OS/2 Corrective Service Facility to install this FixPak. Check the BUILD.LVL file for the level you are using. If it does not have a BUILD.LVL file then it is old and cannot be used. 6.0.2 WHERE YOU CAN FIND CSF CODE The latest Corrective Service Facility code is available from: ftp://service.boulder.ibm.com/ps/products/os2/fixtool/ Select the required language then the latest fixtool release (CS?140 at the time this Fixpak was released). The .TXT file has instructions. The .EXE is a self-extracting ZIP file that contains the CSF code. See the READ.ME file contained in .EXE for information on how to use the new CSF. 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_W043.?DK A: /F (? can be 1 through 9, A through Z). Label the diskette as FixPak XR_W043 Corrective Service Diskette ? (CSF DISK ?) Note: For diskette images ADK through ZDK (if they exist), use the numbers 10 through 36. Corrective Service Facility 28 October 18, 2000 - Warp 3 FixPak XR_W043 Examples: XR_W043.ADK = Corrective Service Diskette 10 (CSF DISK 10) XR_W043.BDK = Corrective Service Diskette 11 (CSF DISK 11) XR_W043.CDK = Corrective Service Diskette 12 (CSF DISK 12) XR_W043.DDK = Corrective Service Diskette 13 (CSF DISK 13) etc. Corrective Service Facility 29 October 18, 2000 - Warp 3 FixPak XR_W043 7.0 RELOCATED OS/2 FILE SUPPORT This FixPak will service directories based on the location of supported SYSLEVEL.OS2 and SYSLEVEL.MPM files. Please check your system to make sure extra copies of these files are not located in directories other than: \OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s) \MMOS2\INSTALL\SYSLEVEL.MPM on any partition If additional copies of these files are found in other locations on your hard disk then CSF will try to service files as follows: For 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. For SYSLEVEL.MPM ..\* all files in a directory one level above (toward the root) and all subdirectories below. This should be the MMOS2 directory and subdirectories. If you have moved OS/2 files or directories, do the following in order to have them serviced: 1. Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the OS\2 Warp partition to be serviced. In this file, place the full path to the directory you want to be serviced. Examples would be: C:\JSI\* D:\JSI\SH\* Be sure to include the trailing * (asterisk) after the last backslash. Note: Leave this file for any future OS/2 Warp FixPaks you might apply. Relocated OS/2 file support 30 October 18, 2000 - Warp 3 FixPak XR_W043 8.0 LAN SERVER/WARP SERVER REMOTE IPL CONSIDERATIONS The utility mentioned in this section is on the last FixPak disk. Ž UPDTRIPL.EXE To support the OS/2 3.0 DAX function, the following updates must be made to the Remote IPL(RIPL) control files: Ž Update the d:\IBMLAN\RPL\FITS\DEFALT30.FIT file to add the following entry to the end of the file: Z:\*.DAT OS2.30 Ž For each RIPL client that is defined to boot OS/2 3.0, update the d:\IBMLAN\RPL\FITS\client.FIT file to add the following entry to the end of the file: Z:\*.DAT OS2.30 Note: In the file name client is the name of the RIPL machine. Ž For each RIPL client that is defined to boot OS/2 3.0, run the utility UPDTRIPL.EXE to update the client CONFIG.SYS and OS2.INI files. You must specify the fully qualified path for both files as parameters to UPDTRIPL.EXE. The syntax of UPDTRIPL is: UPDTRIPL client_config_sys client_os2_ini Each client copy of OS2.INI will be located in the d:\IBMLAN\RPLUSER\client\OS2 directory. The os2.INI path parameter for UPDTRIPL.EXE will be d:\IBMLAN\RPLUSER\client\OS2\OS2.INI. Each client copy of CONFIG.SYS can be in two different directories, depending on what type of video support the client is configured to use. The two possibilites are: 1. If the client is configured for SVGA or S3SVGA support, the CONFIG.SYS file will be located in the d:\IBMLAN\RPLUSER\client directory. Note: There will be a CONFIG.SYS file in the d:\IBMLAN\RPL\MACHINES\client directory. However, it is not used when the client is configured for SVGA or S3SVGA support. 2. If the client is configured for any other video type, the CONFIG.SYS file will be located in the d:\IBMLAN\RPL\MACHINES\client directory. LAN Server/Warp Server Remote IPL Considerations 31 October 18, 2000 - Warp 3 FixPak XR_W043 If you are not sure which video type the client is configured to use, do the following to determine which CONFIG.SYS the client is using: a. Edit the d:\IBMLAN\RPL\FITS\client.FIT file. b. Search for the line that starts with Z:\CONFIG.SYS (assumes that the client is using the default boot drive of Z:). c. If the second field (target file name) is MACHINES\client\CONFIG.SYS, the path is d:\IBMLAN\RPL\MACHINES\client\CONFIG.SYS. If the second field is \\servername\WRKFILES\client\CONFIG.SYS, the path is d:\IBMLAN\RPLUSER\client\CONFIG.SYS. Note: servername is the LAN server name. Ž Run the UPDTRIPL.EXE utility and update the default OS/2 3.0 CONFIG.SYS and OS2.INI files. The actual file names to update are d:\IBMLAN\RPL\MACHINES\DEFALT30\CONFIG.DEF and d:\IBMLAN\RPLUSER\DEFALT30\OS2\OS2.INI. Ž Check the Access Control Profile (ACP) for the C:\IBMLAN\RPL\OS2.30\LANGUAGE directory. The RPLGROUP ID should have RX access. Follow these steps to check the ACP: 1. Logon as administrator . 2. Open the drives folder under OS/2 system 3. Find the OS2.30\LANGUAGE folder under \IBMLAN\RPL 4. Select (Single-click with Left mouse button) the OS2.30\LANGUAGE folder 5. From the pop-up menu (Single click with Right mouse button), select "Manage Access" 6. Click on the Permissions Tab . If the RPLGROUP ID does not have RX permissions, do the following: 1. Click on the Add button and select RPLGROUP, and click on OK 2. Add permissions Read and Execute and click on Change. 3. Click on Set (Bottom of the window) 4. Click on OK to propagate this Access Control Profile to all of the resource's subdirectories. LAN Server/Warp Server Remote IPL Considerations 32 October 18, 2000 - Warp 3 FixPak XR_W043 9.0 INSTALLATION PROCESS 9.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 and DISK 1 diskettes you used to install OS/2 with. 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. 9.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION. This method allows you to select the products (partitions) to be serviced. This is the method you should use if you have more than one OS/2 partition and want to control which one is serviced. Note: You can use a diskette drive other than A: with this method. If your 3.5" diskette drive is B:, use B: where A: is mentioned in the following steps. (this method only). 1. Insert CSF DISK Diskette 1 in drive A. 2. Open an OS/2 window or full-screen session. 3. Type A:\SERVICE and press the Enter key. Note: You could also use the "Drives" object for A: and double click on the "SERVICE.EXE" Icon to start the install. 4. Follow the displayed instructions. When prompted to insert Corrective Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_W043 Corrective Service Diskette 1 in drive A. Repeat for the rest of the FixPak disks when requested to do so. Note: It can take a considerable length of time for the Corrective Service Facility to scan your hard disk for serviceable files. In some cases, it has taken as long as 40 minutes. Please be patient and allow this process to complete. 5. If this is the first OS/2 Warp FixPak you have applied to this system, then enter the path to the ARCHIVE directory where a copy of replaced files will be stored (for example, D:\ARCHIVE). Installation Process 33 October 18, 2000 - Warp 3 FixPak XR_W043 Note: This ARCHIVE directory is not related to the ARCHIVES directory built into OS/2 Warp 3.0. Please specify a different path. You must specify a different ARCHIVE directory for each product to be serviced. If this is not the first OS/2 Warp FixPak, then enter the path to the BACKUP directory where a copy of replaced files will be stored (for example, D:\BACKUP). Note: You must specify a different BACKUP directory for each product to be serviced. For either case, make sure there is sufficient space available on the drive you specify. Even though these files are kept in compressed (PACK2) format, they require between 7 and 12 MB of disk space. 6. Click on "OK". 7. You will see an "Application in use" dialog box showing a list of locked files that cannot be serviced while the system is running. You are given two choices - to Continue or Reboot. Select Continue. 8. During the installation process you might see messages about Archiving, Updating and Deferring service. Ž Archiving saves a compressed copy of the original file in the ARCHIVE or BACKUP path you specified. Ž Updating means the original files are replaced with the new ones from this FixPak. Ž Deferring service means the file to be updated is currently in use by the system and cannot be updated. The new files from the FixPak are placed in unpacked format in the \IBMCSFLK\FIX directory on the drive with the most free space. They are processed by the locked file device driver during reboot after you shut down the system. 9. Select NO for a redisplay of the "Product List" after the first part of the FixPak application process has completed if this message is displayed. 10.Click Cancel and Exit to close the Corrective Service Facility window if necessary. 11.Shut down and reboot your system. You will see the following during reboot of the system if you applied service to the OS/2 partition you were booted from. The locked file driver is loaded. Processing locked files Processing complete The system will do one automatic reboot after the Locked File Device Driver has completed. Installation Process 34 October 18, 2000 - Warp 3 FixPak XR_W043 9.3 METHOD 2: BOOT FROM CORRECTIVE SERVICE DISK 1. This method does not prompt the user for any information. No interaction with the user takes place other than requests to put the next diskette in drive A. All serviceable partitions on your system will be updated automatically. Be especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using this method because they can cause CSF to apply service to directories you do not want serviced. 1. Shut down your OS/2 system. 2. Insert CSF DISK Diskette 1 in drive A. 3. Press Ctrl+Alt+Del to boot the disk in drive A. Service will be applied to ALL partitions that contain a version of OS/2 that is supported by this FixPak. See the section "FixPak Corrective Service Notes" 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. In some cases it has taken as long as 40 minutes. Please be patient and allow this process to complete. 9.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION Additional information on the Corrective Service Facility is available from the README.INF file on the first Corrective Service Facility disk. To view this file, place CSF disk 1 in drive A and enter VIEW A:\README.INF. Installation Process 35 October 18, 2000 - Warp 3 FixPak XR_W043 10.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 something like the following for SYSLEVEL.OS2. Before a FixPak is applied using the F.138B CSF build (or later) to a Warp Connect system. E:\OS2\INSTALL\SYSLEVEL.OS2 IBM OS/2 Base Operating System Version 3.0 Component ID 562274700 Type 0C Current CSD level: XR03003 Prior CSD level: XR03003 After a FixPak is applied using the F.138B CSF build (or later) to a Warp Connect system. E:\OS2\INSTALL\SYSLEVEL.OS2 IBM OS/2 Base Operating System Version 3.0 Component ID 562274700 Type 0C Current CSD level: XR0W040 Prior CSD level: XR03003 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 3.00 Revision n.nnn The first page of this document has a line that looks like: CSD level of SYSLEVEL.OS2 36 October 18, 2000 - Warp 3 FixPak XR_W043 Build Level: n.nnn That is the number you should see for this FixPak when you issue the VER /R command. 10.0.1 NEW SYSLEVEL.FPK A SYSLEVEL.FPK file has been added to all Warp 3 FixPaks, beginning with XR_W032. It is titled "OS/2 Warp 3 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 37 October 18, 2000 - Warp 3 FixPak XR_W043 11.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS Build Level: 8.267 Product location on CSD: A:\FIX\OS2.1 Product name: "IBM OS/2 Base Operating System" Standard Edition 3.01 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3005_ System Id: 1000 Component Id: 562274700 Archive is ON for this product. ________________________________________________________________________ Product name: "IBM OS/2 Base Operating System" Standard Edition 3.02 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3006_ System Id: 1000 Component Id: 5639A5500 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Will create the following directories ..\..\OS2\BOOK Stub File: @BOOKDIR ..\..\OS2\BOOT Stub File: @BOOTDIR ..\..\LANGUAGE\CODEPAGE Stub File: @CDEPDIR ..\..\OS2\DLL Stub File: @DLLDIR ..\..\OS2\HELP Stub File: @HELPDIR ..\..\OS2\INSTALL Stub File: @INSTDIR ..\..\OS2\APPS Stub File: @APPSDIR ..\..\LANGUAGE\KEYBOARD Stub File: @KEYBDIR ..\..\LANGUAGE\LOCALE Stub File: @LOCLDIR FixPak Corrective Service levels and disk layouts 38 October 18, 2000 - Warp 3 FixPak XR_W043 ..\..\OS2\MDOS Stub File: @MDOSDIR ..\..\OS2 Stub File: @OS2DIR ..\..\OS2\SYSTEM\PMDF Stub File: @PMDFDIR ..\..\OS2\SYSTEM\RAS Stub File: @RASDIR ..\..\OS2\SYSTEM Stub File: @SYSTDIR ..\..\OS2\SYSTEM\TRACE Stub File: @TRACDIR Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- AA.KBL AA.KB_ 11 12/02/1999 14:19 1200 41C9ECA1 AA470.KBL AA470.KB_ 11 12/02/1999 14:19 1212 7FBC26F6 ARACONV.EXE ARACONV.EX_ 9 11/23/1999 20:12 62151 F784F7D0 ARCINST.EXE ARCINST.EX_ 10 07/25/2000 00:06 19798 85C8158D ARCRECOV.EXE ARCRECOV.EX_ 10 07/25/2000 00:07 21871 D6E7ECCB ASIACOL.DLL ASIACOL.DL_ 5 12/02/1999 14:20 158758 3988EF24 BA.KBL BA.KB_ 11 12/02/1999 14:19 980 CAEB4F87 BACKUP.EXE BACKUP.EX_ 10 07/24/2000 22:17 32736 657A9C9D BDCALLS.DLL BDCALLS.DL_ 10 01/08/1998 18:09 37594 F7D833A0 BDIME.DLL BDIME.DL_ 10 04/13/1999 08:18 33239 BC50FC0E BE.KBL BE.KB_ 11 12/02/1999 14:19 972 B9CF6F4D BG.KBL BG.KB_ 11 12/02/1999 14:19 1152 3B11B14E BG241.KBL BG241.KB_ 11 12/02/1999 14:19 1372 B79DBAB4 BLDLEVEL.EXE BLDLEVEL.EX_ 11 07/24/2000 23:37 21523 ED40532C BOOT.COM BOOT.CO_ 10 07/24/2000 22:38 43056 CB48623E BOOTDISK.EXE BOOTDISK.EX_ 9 07/25/2000 00:47 48777 E89F5429 BR.KBL BR.KB_ 11 12/02/1999 14:19 932 12509F8B BR274.KBL BR274.KB_ 11 12/02/1999 14:19 852 875F122C BVHWNDW.DLL BVHWNDW.DL_ 11 02/17/1998 15:37 14233 665B49D8 BVSCALLS.DLL BVSCALLS.DL_ 11 08/26/1998 01:32 512 4062D2D3 BY.KBL BY.KB_ 11 12/02/1999 14:19 1292 7E1B2D68 CA.KBL CA.KB_ 11 12/02/1999 14:19 1214 153AD27D CALC.EXE CALC.EX_ 10 07/19/1999 16:14 43056 A1BB49B5 CALENDAR.EXE CALENDAR.EX_ 9 07/19/1999 16:15 59808 65473CF6 CARDFILE.EXE CARDFILE.EX_ 9 07/19/1999 16:16 93184 8AB13196 CARDINFO.DAT CARDINFO.DA_ 2 12/07/1998 10:00 29787 BD0C262B CDFS.IFS CDFS.IF_ 10 07/24/2000 21:37 45151 9D7BDB8A CDFS.TDF CDFS.TD_ 11 07/24/2000 21:37 2113 81DC2068 CDROM.TBL CDROM.TB_ 11 03/12/1997 17:33 3658 2E96808F CF.KBL CF.KB_ 11 12/02/1999 14:19 956 B1186AE5 CHARMAP.EXE CHARMAP.EX_ 11 07/19/1999 16:28 22016 6022A98C CHKDSK.COM CHKDSK.CO_ 9 07/24/2000 22:21 68656 9453C617 CHKDSK.SYS CHKDSK.SY_ 11 08/24/2000 09:38 762 8FBB6856 CHKDSK32.DLL CHKDSK32.DL_ 7 08/18/2000 15:31 170023 B8765BDE FixPak Corrective Service levels and disk layouts 39 October 18, 2000 - Warp 3 FixPak XR_W043 CHKDSK32.EXE CHKDSK32.EX_ 11 08/18/2000 15:02 6417 DDDF2ADB CLDAPI.DLL CLDAPI.DL_ 10 07/24/2000 23:52 22217 C0E59D60 CLIPBRD.EXE CLIPBRD.EX_ 11 07/19/1999 16:16 18496 B3F5949C CLOCK.EXE CLOCK.EX_ 11 07/19/1999 16:17 16400 E74F144F CLOCK01.SYS CLOCK01.SY_ 11 08/14/2000 19:15 4560 C92593EC CLOCK02.SYS CLOCK02.SY_ 11 08/14/2000 19:15 4318 FBE906A4 CMD.EXE CMD.EX_ 3 07/24/2000 22:26 71556 A506F0B8 COMM.DRV COMM.DR_ 11 07/19/1999 18:10 9552 353CF5F2 COMMAND.COM COMMAND.CO_ 9 07/24/2000 22:24 53014 66A8CCDB COMMDLG.DLL COMMDLG.DL_ 8 07/19/1999 16:12 87072 B987A798 COMMONA.DSP COMMONA.DS_ 11 03/27/1998 14:21 429 CD1C47BE CONTROL.EXE CONTROL.EX_ 11 07/19/1999 16:54 15856 CFA1BC10 COUNTRY.SYS COUNTRY.SY_ 11 07/24/2000 22:53 50932 CD0A6677 COUR.OFM COUR.OF_ 11 01/13/1998 14:37 4236 61F7551D COUR.PFB COUR.PF_ 5 01/13/1998 14:37 112702 F4783159 COUR.PFM COUR1.PF_ 11 01/13/1998 14:37 674 EB15B168 COURB.OFM COURB.OF_ 11 01/13/1998 14:37 4246 1F31D3E4 COURB.PFB COURB.PF_ 5 01/13/1998 14:37 116938 114C7222 COURB.PFM COU1.PF_ 11 01/13/1998 14:37 679 1EF9C6BB COURBI.OFM COURBI.OF_ 11 01/13/1998 14:37 4260 8CFE6AF3 COURBI.PFB COURBI.PF_ 5 01/13/1998 14:37 112484 875E9829 COURBI.PFM COURB1.PF_ 11 01/13/1998 14:37 685 D0390DEF COURI.OFM COURI.OF_ 11 01/13/1998 14:37 4251 4253A3B8 COURI.PFB COURI.PF_ 5 01/13/1998 14:37 113244 48B65D0F COURI.PFM COUR2.PF_ 11 01/13/1998 14:37 681 A6EEB717 COURIER.FON COURIER.FO_ 10 01/19/1998 13:35 104183 CE3E3300 CPG01256.TBL CPG01256.TB_ 11 11/22/1999 12:17 27264 A5C721BD CZ.KBL CZ.KB_ 11 12/02/1999 14:19 1014 B5779D23 DDEML.DLL DDEML.DL_ 10 07/19/1999 16:11 36864 0FC24679 DDINSTAL.EXE DDINSTAL.EX_ 9 07/24/2000 22:56 35879 8539CF2C DE.KBL DE.KB_ 11 12/02/1999 14:19 958 96E0DDA3 DE453.KBL DE453.KB_ 11 12/02/1999 14:19 1354 B6DDE2E1 DISPLAY.DLL DISPLAY.DL_ 9 07/10/2000 13:48 44198 48E36628 DK.KBL DK.KB_ 11 12/02/1999 14:19 928 46C631AF DMCOLOR.DLL DMCOLOR.DL_ 11 07/19/1999 17:20 18480 B716CA14 DMQSPROF.DLL DMQSPROF.DL_ 9 07/26/1999 20:55 43278 A37752D3 DRWATSON.EXE DRWATSON.EX_ 10 07/19/1999 17:05 26864 2F1B8E14 DSPINSTL.EXE DSPINSTL.EX_ 6 07/24/2000 23:47 112216 358BAA09 DSPRES.DLL DSPRES2.DL_ 4 01/19/1998 13:35 250598 F6022627 DSPRES.DLL DSPRES1.DL_ 4 01/19/1998 13:35 250598 F6022627 DSPRES.DLL DSPRES.DL_ 4 01/19/1998 13:35 250598 F604CE27 DTRACE.DOC DTRACE.DO_ 10 01/07/1998 17:11 75371 761E5F8B DTRACE.EXE DTRACE.EX_ 9 07/24/2000 19:56 48906 AED7058C E.EXE E.EX_ 9 07/24/2000 22:15 48389 EA061208 EAUTIL.EXE EAUTIL.EX_ 10 07/24/2000 22:38 37984 F22463FC EE.KBL EE.KB_ 11 12/02/1999 14:19 932 ACF9C974 EJECT.EXE EJECT.EX_ 10 01/14/1998 16:27 25649 5A75A5C8 EL.KBL EL.KB_ 11 12/02/1999 14:19 1396 D4F7753C EL220.KBL EL220.KB_ 11 12/02/1999 14:19 1428 DD7C28CB EL459.KBL EL459.KB_ 11 12/02/1999 14:19 1372 B9F1C4D2 ES.KBL ES.KB_ 11 12/02/1999 14:19 920 9E1D8E87 FixPak Corrective Service levels and disk layouts 40 October 18, 2000 - Warp 3 FixPak XR_W043 EXPAND.EXE EXPAND.EX_ 10 07/19/1999 16:07 25432 C8750CF8 FDISK.COM FDISK.CO_ 7 07/24/2000 21:46 113658 E3D7E1B2 FDISKPM.DLL FDISKPM.DL_ 11 03/24/1998 16:10 8244 08483FBF FDISKPM.EXE FDISKPM.EX_ 8 07/24/2000 21:46 63043 ED274E45 FI.KBL FI.KB_ 11 12/02/1999 14:19 940 6D873B78 FINSTALL.DLL FINSTALL.DL_ 6 07/19/1999 17:26 200368 11980150 FORMAT.COM FORMAT.CO_ 9 07/24/2000 22:47 69920 90976D55 FR.KBL FR.KB_ 11 12/02/1999 14:19 950 2F060403 FSFILTER.SYS FSFILTER.SY_ 11 07/24/2000 22:59 12988 428292C1 GDI.EXE GDI.EX_ 4 07/19/1999 16:42 225744 FC21FFD9 GRADD.SYS GRADD.SY_ 11 05/15/2000 16:23 2754 05B49EB1 GRE2VMAN.DLL GRE2VMAN.DL_ 11 08/06/2000 12:13 20653 147372EC HARDERR.EXE HARDERR.EX_ 11 07/24/2000 21:52 9416 D02B9D05 HELPMGR.DLL HELPMGR.DL_ 4 07/24/2000 22:43 175874 7D1CA539 HELPMSG.EXE HELPMSG.EX_ 10 07/24/2000 22:47 36256 5C784A59 HELV.FON HELV.FO_ 6 01/19/1998 13:36 264425 4DFE4FF3 HELV.OFM HELV.OF_ 11 03/12/1998 09:41 4865 E6B9D229 HELV.PFB HELV.PF_ 6 03/12/1998 09:41 101942 076D61BB HELV.PFM HEL1.PF_ 11 03/12/1998 09:41 1096 6F22965A HELVB.OFM HELVB.OF_ 11 03/12/1998 09:41 4857 C06526BD HELVB.PFB HELVB.PF_ 6 03/12/1998 09:41 104404 D1A162E1 HELVB.PFM HELV1.PF_ 11 03/12/1998 09:41 1089 84484DE1 HELVBI.OFM HELVBI.OF_ 11 03/12/1998 09:41 4859 F81293F7 HELVBI.PFB HELVBI.PF_ 6 03/12/1998 09:41 105074 CEC8B328 HELVBI.PFM HELVB1.PF_ 11 03/12/1998 09:41 1087 0655029D HELVI.OFM HELVI.OF_ 11 03/12/1998 09:41 4844 499A0362 HELVI.PFB HELVI.PF_ 6 03/12/1998 09:41 103996 73AEF6AC HELVI.PFM HELV2.PF_ 11 03/12/1998 09:41 1079 A1475D84 HPFS.IFS HPFS.IF_ 7 08/24/2000 09:41 144450 4F8FEB3E HPFS.TDF HPFS.TD_ 11 08/24/2000 09:41 1620 1DAFFFA7 HR.KBL HR.KB_ 11 12/02/1999 14:19 982 F9ACEEBA HU.KBL HU.KB_ 11 12/02/1999 14:19 1006 C7C7BFEE IBM1004 IBM1004.___ 11 12/02/1999 14:12 3584 7FAB8F9A IBM1006 IBM1006.___ 11 12/02/1999 14:12 3040 A9881646 IBM1008 IBM1008.___ 11 12/02/1999 14:12 2816 98C46AD8 IBM1025 IBM1025.___ 11 12/02/1999 14:12 2560 A433126E IBM1026 IBM1026.___ 11 12/02/1999 14:12 2560 E64DA7D4 IBM1027 IBM1027.___ 11 12/02/1999 14:12 2304 5D7AF143 IBM1028 IBM1028.___ 11 12/02/1999 14:12 3072 599DF53B IBM1038 IBM1038.___ 11 12/02/1999 14:12 4608 47438A35 IBM1041 IBM1041.___ 11 12/02/1999 14:12 3296 87214004 IBM1043 IBM1043.___ 11 12/02/1999 14:12 3040 3E696709 IBM1046 IBM1046.___ 11 12/02/1999 14:12 3040 DF209620 IBM1047 IBM1047.___ 11 12/02/1999 14:12 2304 5ABDADBB IBM1051 IBM1051.___ 11 12/02/1999 14:12 3296 2FAFD338 IBM1088 IBM1088.___ 11 12/02/1999 14:12 3552 6597710E IBM1089 IBM1089.___ 11 12/02/1999 14:12 2560 2AA878BA IBM1092 IBM1092.___ 11 12/02/1999 14:12 4832 1A30D736 IBM1097 IBM1097.___ 11 12/02/1999 14:12 3040 C5F3B6F2 IBM1098 IBM1098.___ 11 12/02/1999 14:12 4576 ECC99645 IBM1112 IBM1112.___ 11 12/02/1999 14:12 2528 EC54FF2C FixPak Corrective Service levels and disk layouts 41 October 18, 2000 - Warp 3 FixPak XR_W043 IBM1114 IBM1114.___ 11 12/02/1999 14:12 3552 271C28B0 IBM1115 IBM1115.___ 11 12/02/1999 14:12 3296 EA0A2457 IBM1116 IBM1116.___ 11 12/02/1999 14:12 3808 BD0A0FFF IBM1117 IBM1117.___ 11 12/02/1999 14:12 3552 3E16B694 IBM1118 IBM1118.___ 11 12/02/1999 14:12 4320 876D28FF IBM1119 IBM1119.___ 11 12/02/1999 14:12 4096 44C1FB27 IBM1122 IBM1122.___ 11 12/02/1999 14:12 2560 86E90FDC IBM1123 IBM1123.___ 11 12/02/1999 14:12 2528 6C07803F IBM1124 IBM1124.___ 11 12/02/1999 14:12 2528 98A6A477 IBM1125 IBM1125.___ 11 12/02/1999 14:12 4320 4929BB62 IBM1131 IBM1131.___ 11 12/02/1999 14:12 4320 41CEE2D2 IBM1200 IBM1200.___ 11 12/02/1999 14:12 2784 359D78D5 IBM1207 IBM1207.___ 11 12/02/1999 14:12 704 0EDFF9F3 IBM1208 IBM1208.___ 11 12/02/1999 14:12 720 9BAC6045 IBM1250 IBM1250.___ 11 12/02/1999 14:12 3552 E5F918EF IBM1251 IBM1251.___ 11 12/02/1999 14:12 3328 82759905 IBM1252 IBM1252.___ 11 12/02/1999 14:12 3552 9E4CF21E IBM1253 IBM1253.___ 11 12/02/1999 14:12 3552 CAC6863D IBM1254 IBM1254.___ 11 12/02/1999 14:12 3552 6E1D9E60 IBM1255 IBM1255.___ 11 12/02/1999 14:12 3808 D4DB82B0 IBM1256 IBM1256.___ 11 12/02/1999 14:12 4320 87492B76 IBM1257 IBM1257.___ 11 12/02/1999 14:12 3296 71DAE5AE IBM1275 IBM1275.___ 11 12/02/1999 14:12 5600 E5D0DA17 IBM1276 IBM1276.___ 11 12/02/1999 14:12 3072 EC090CD0 IBM1277 IBM1277.___ 11 12/02/1999 14:12 2816 50AEF570 IBM1280 IBM1280.___ 11 12/02/1999 14:12 4832 679B7A30 IBM1281 IBM1281.___ 11 12/02/1999 14:12 5344 DB2812A0 IBM1282 IBM1282.___ 11 12/02/1999 14:12 5120 BD286894 IBM1283 IBM1283.___ 11 12/02/1999 14:12 4832 DA04CBA8 IBM1381 IBM1381.___ 8 12/02/1999 14:12 109792 FA0FD3BB IBM1383 IBM1383.___ 8 12/02/1999 14:12 127344 42D69E6B IBM1386 IBM1386.___ 4 12/02/1999 14:12 125200 1515092C IBM259 IBM259.___ 11 12/02/1999 14:12 4864 46730DBB IBM273 IBM273.___ 11 12/02/1999 14:12 2304 1DB8EBEB IBM277 IBM277.___ 11 12/02/1999 14:12 2304 E20FE11A IBM278 IBM278.___ 11 12/02/1999 14:12 2304 0B4EEC3E IBM280 IBM280.___ 11 12/02/1999 14:12 2272 EB03021A IBM282 IBM282.___ 11 12/02/1999 14:12 2272 B5CBF4B5 IBM284 IBM284.___ 11 12/02/1999 14:12 2304 BE576FC1 IBM285 IBM285.___ 11 12/02/1999 14:12 2304 89BF65BD IBM290 IBM290.___ 11 12/02/1999 14:12 2272 519B5927 IBM293 IBM293.___ 11 12/02/1999 14:12 3040 C02BE129 IBM297 IBM297.___ 11 12/02/1999 14:12 2272 107DE98C IBM2TI1.EXE IBM2TI1.EX_ 11 05/13/1996 21:15 9886 E248A23F IBM2TI1.SYS IBM2TI1.SY_ 11 05/13/1996 21:15 9886 E251A23F IBM300 IBM300.___ 8 12/02/1999 14:12 94432 97C181F2 IBM301 IBM301.___ 9 12/02/1999 14:12 83168 3979EBA1 IBM361 IBM361.___ 11 12/02/1999 14:12 3584 8AD912EE IBM363 IBM363.___ 11 12/02/1999 14:12 4864 D657D238 IBM367 IBM367.___ 11 12/02/1999 14:12 2016 846429C5 IBM37 IBM37.___ 11 12/02/1999 14:12 2304 E3CB40FF FixPak Corrective Service levels and disk layouts 42 October 18, 2000 - Warp 3 FixPak XR_W043 IBM382 IBM382.___ 11 12/02/1999 14:12 3584 5489972C IBM383 IBM383.___ 11 12/02/1999 14:12 3584 1C23D7D0 IBM385 IBM385.___ 11 12/02/1999 14:12 3584 8392F43A IBM386 IBM386.___ 11 12/02/1999 14:12 3584 D9E3DFB8 IBM387 IBM387.___ 11 12/02/1999 14:12 3584 866E8F16 IBM388 IBM388.___ 11 12/02/1999 14:12 3584 714861F0 IBM389 IBM389.___ 11 12/02/1999 14:12 3584 85403B11 IBM391 IBM391.___ 11 12/02/1999 14:12 3584 5EF82797 IBM392 IBM392.___ 11 12/02/1999 14:12 3584 BDECF0ED IBM393 IBM393.___ 11 12/02/1999 14:12 3584 E30AC396 IBM394 IBM394.___ 11 12/02/1999 14:12 3584 CE4856EB IBM395 IBM395.___ 11 12/02/1999 14:12 3584 EC75516B IBM420 IBM420.___ 11 12/02/1999 14:12 3040 9731D534 IBM424 IBM424.___ 11 12/02/1999 14:12 2528 DA18519E IBM437 IBM437.___ 11 12/02/1999 14:12 4576 9CBD81AC IBM500 IBM500.___ 11 12/02/1999 14:12 2304 14F6E36A IBM813 IBM813.___ 11 12/02/1999 14:12 3072 6FC30F3A IBM819 IBM819.___ 11 12/02/1999 14:12 2816 7FAABF61 IBM829 IBM829.___ 11 12/02/1999 14:12 3840 9E62075D IBM833 IBM833.___ 11 12/02/1999 14:12 2272 424878C0 IBM834 IBM834.___ 8 12/02/1999 14:12 148704 C81D3534 IBM835 IBM835.___ 7 12/02/1999 14:12 125152 914F0E72 IBM836 IBM836.___ 11 12/02/1999 14:12 2272 37B66B24 IBM837 IBM837.___ 9 12/02/1999 14:12 84704 811F08FD IBM838 IBM838.___ 11 12/02/1999 14:12 2272 07CF40C6 IBM850 IBM850.___ 11 12/02/1999 14:12 4320 711FAC6A IBM851 IBM851.___ 11 12/02/1999 14:12 3840 6D400DD8 IBM852 IBM852.___ 11 12/02/1999 14:12 4608 A76091E3 IBM855 IBM855.___ 11 12/02/1999 14:12 4320 59F2A793 IBM856 IBM856.___ 11 12/02/1999 14:12 4064 448411D2 IBM857 IBM857.___ 11 12/02/1999 14:12 4352 1C9D6DB1 IBM860 IBM860.___ 11 12/02/1999 14:12 4320 6009A314 IBM861 IBM861.___ 11 12/02/1999 14:12 4064 4B58AAD3 IBM862 IBM862.___ 11 12/02/1999 14:12 4576 C2540C60 IBM863 IBM863.___ 11 12/02/1999 14:12 4096 471D68A9 IBM864 IBM864.___ 11 12/02/1999 14:12 4576 017C361E IBM865 IBM865.___ 11 12/02/1999 14:12 4064 45E22FC9 IBM866 IBM866.___ 11 12/02/1999 14:12 4320 2DA50F82 IBM868 IBM868.___ 11 12/02/1999 14:12 4576 CEB47754 IBM869 IBM869.___ 11 12/02/1999 14:12 4320 3123486D IBM870 IBM870.___ 11 12/02/1999 14:12 2560 66654884 IBM871 IBM871.___ 11 12/02/1999 14:12 2304 54DB4772 IBM874 IBM874.___ 11 12/02/1999 14:12 2784 98AEE14B IBM875 IBM875.___ 11 12/02/1999 14:12 2528 0B7F3150 IBM878 IBM878.___ 11 12/02/1999 14:12 3328 8EEACD2D IBM891 IBM891.___ 11 12/02/1999 14:12 3296 F14C1E09 IBM895 IBM895.___ 11 12/02/1999 14:12 2304 D8B7F493 IBM896 IBM896.___ 11 12/02/1999 14:12 2048 F849993B IBM897 IBM897.___ 11 12/02/1999 14:12 3296 8DF97279 IBM903 IBM903.___ 11 12/02/1999 14:12 3296 D30CDC23 IBM904 IBM904.___ 11 12/02/1999 14:12 3040 C59759B4 FixPak Corrective Service levels and disk layouts 43 October 18, 2000 - Warp 3 FixPak XR_W043 IBM907 IBM907.___ 11 12/02/1999 14:12 3808 EF365739 IBM909 IBM909.___ 11 12/02/1999 14:12 3808 CDE491F3 IBM910 IBM910.___ 11 12/02/1999 14:12 3808 0623B68C IBM912 IBM912.___ 11 12/02/1999 14:12 2560 3D919694 IBM913 IBM913.___ 11 12/02/1999 14:12 2560 AB1EE7D8 IBM914 IBM914.___ 11 12/02/1999 14:12 2560 2B0EC03E IBM915 IBM915.___ 11 12/02/1999 14:12 2560 AA72BEC4 IBM916 IBM916.___ 11 12/02/1999 14:12 2560 D6D5399B IBM918 IBM918.___ 11 12/02/1999 14:12 3040 EA1673D7 IBM920 IBM920.___ 11 12/02/1999 14:12 2560 C8191BF2 IBM921 IBM921.___ 11 12/02/1999 14:12 3040 0F0689F3 IBM922 IBM922.___ 11 12/02/1999 14:12 3040 71D4196C IBM930 IBM930.___ 8 12/02/1999 14:12 94976 03764A56 IBM931 IBM931.___ 8 12/02/1999 14:12 94976 29B23D1C IBM933 IBM933.___ 8 12/02/1999 14:12 149248 BF295A91 IBM935 IBM935.___ 8 12/02/1999 14:12 85248 54AA5F43 IBM937 IBM937.___ 7 12/02/1999 14:12 125696 9D8D65F3 IBM939 IBM939.___ 8 12/02/1999 14:12 94976 80873AC2 IBM941 IBM941.___ 8 12/02/1999 14:12 87264 0625D486 IBM942 IBM942.___ 8 12/02/1999 14:12 83712 E248EAFD IBM943 IBM943.___ 8 12/02/1999 14:12 87808 28F19668 IBM944 IBM944.___ 8 12/02/1999 14:12 112896 A121A5E3 IBM946 IBM946.___ 8 12/02/1999 14:12 84736 7CE15C28 IBM947 IBM947.___ 7 12/02/1999 14:12 131808 F8506FE4 IBM948 IBM948.___ 7 12/02/1999 14:12 125696 F1BAF9FC IBM949 IBM949.___ 8 12/02/1999 14:12 136448 8ECE1DF1 IBM950 IBM950.___ 6 12/02/1999 14:12 132352 69539457 IBM952 IBM952.___ 9 12/02/1999 14:12 89856 FC2DE730 IBM953 IBM953.___ 10 12/02/1999 14:12 83200 2E9BD4DE IBM954 IBM954.___ 8 12/02/1999 14:12 140864 8321F0E0 IBM955 IBM955.___ 9 12/02/1999 14:12 89856 1FEF8CB2 IBM964 IBM964.___ 6 12/02/1999 14:12 174456 8767C8E3 IBM970 IBM970.___ 8 12/02/1999 14:12 169776 CD700829 IBM971 IBM971.___ 9 12/02/1999 14:12 124160 9D1C4C4C IFGDI2VM.DRV IFGDI2VM.DR_ 9 05/15/2000 16:23 93136 7268D00F IL.KBL IL.KB_ 11 12/02/1999 14:19 1232 21533791 INSCFG32.DLL INSCFG32.DL_ 10 07/24/2000 19:15 31938 39D9CE7E INSPGM32.DLL INSPGM32.DL_ 9 07/24/2000 19:16 41504 DD5E5A69 IS.KBL IS.KB_ 11 12/02/1999 14:19 940 552D9687 IS458.KBL IS458.KB_ 11 12/02/1999 14:19 928 7634464C ISGDI2VM.DRV ISGDI2VM.DR_ 9 05/15/2000 16:07 92048 414AB307 IT.KBL IT.KB_ 11 12/02/1999 14:19 876 6AF08922 IT142.KBL IT142.KB_ 11 12/02/1999 14:19 854 FF50D3D2 JP.KBL JP.KB_ 11 12/02/1999 14:19 6374 FA7C15A1 KEYB.COM KEYB.CO_ 11 07/24/2000 22:49 11573 BD4A8679 KEYBOARD.DCP KEYBOARD.DC_ 10 12/02/1999 14:21 315109 643C80C8 KEYBOARD.DRV KEYBOARD.DR_ 11 07/19/1999 18:07 7568 DF5D49D9 KR.KBL KR.KB_ 11 12/02/1999 14:19 724 0E4CB12A LA.KBL LA.KB_ 11 12/02/1999 14:19 916 BC6BAEDC LIBCM.DLL LIBCM.DL_ 4 11/22/1999 11:45 210916 98DAC320 LIBCN.DLL LIBCN.DL_ 8 11/22/1999 11:45 57340 201E3106 FixPak Corrective Service levels and disk layouts 44 October 18, 2000 - Warp 3 FixPak XR_W043 LIBCS.DLL LIBCS.DL_ 4 11/22/1999 11:45 192386 978DE493 LIBUNI.DLL LIBUNI.DL_ 7 12/02/1999 14:22 81372 F5860058 LINK386.EXE LINK386.EX_ 6 07/24/2000 22:59 154164 3609A24F LOCALE.DLL LOCALE.DL_ 6 12/02/1999 14:19 107901 50C0AEB5 LT.KBL LT.KB_ 11 12/02/1999 14:19 1972 9614DF50 LV.KBL LV.KB_ 11 12/02/1999 14:19 1404 07BED725 LZEXPAND.DLL LZEXPAND.DL_ 10 07/19/1999 16:08 69040 482B530E MAIN.CPL MAIN.CP_ 7 07/19/1999 16:53 147680 C0023A80 MAKETSF.EXE MAKETSF.EX_ 9 08/18/2000 15:38 43104 094AD175 MAPTSF.CMD MAPTSF.CM_ 11 04/05/1999 09:56 16803 EA6B489C MCICDA.DRV MCICDA.DR_ 11 07/19/1999 17:11 13824 2E244338 MCISEQ.DRV MCISEQ.DR_ 10 07/19/1999 17:11 25328 F76B8FE4 MCIWAVE.DRV MCIWAVE.DR_ 10 07/19/1999 17:10 28160 8084128C MIDIMAP.DRV MIDIMAP.DR_ 9 07/19/1999 17:12 52800 4DCC5455 MIGRATE.EXE MIGRATE.EX_ 6 07/24/2000 23:16 119434 C62DBE66 MINXOBJ.DLL MINXOBJ.DL_ 10 07/25/2000 00:26 27423 BD6551E5 MIRRORS.DLL MIRRORS.DL_ 2 03/12/1997 16:38 444744 4D9372B8 MK.KBL MK.KB_ 11 12/02/1999 14:19 1302 1A6EFDD9 MMSOUND.DRV MMSOUND.DR_ 11 07/19/1999 17:07 3456 97D7CBF0 MMSYSTEM.DLL MMSYSTEM.DL_ 9 07/19/1999 17:06 61648 254ECC2F MMTASK.TSK MMTASK.TS_ 11 07/19/1999 17:06 1104 DCB8FD5B MOUSE.DRV MOUSE.DR_ 11 07/19/1999 18:10 10896 46184662 MPLAYER.EXE MPLAYER.EX_ 10 07/19/1999 17:14 33312 C3711B4D MPU401.DRV MPU401.DR_ 11 07/19/1999 17:10 7088 BDC7982B MSADLIB.DRV MSADLIB.DR_ 11 07/19/1999 17:07 22048 82A78A36 NL.KBL NL.KB_ 11 12/02/1999 14:19 954 87DF7272 NO.KBL NO.KB_ 11 12/02/1999 14:19 920 54ED117D NOTEPAD.EXE NOTEPAD.EX_ 10 07/19/1999 16:17 32736 2788556F NPXEMLTR.DLL NPXEMLTR.DL_ 10 07/26/1999 20:55 21812 55B4EC1C NWIAPI.DLL NWIAPI.DL_ 11 07/24/2000 19:11 9149 5423C7DC OLECLI.DLL OLECLI.DL_ 9 07/19/1999 16:10 83456 30C78576 OS2CHAR.DLL OS2CHAR.DL_ 11 08/26/1998 00:50 512 6828A757 OS2DASD.DMD OS2DASD.DM_ 10 08/14/2000 18:07 40910 CED15CB1 OS2DUMP OS2DUMP.___ 11 09/23/2000 17:55 14301 D86D377B OS2K386.EXE OS2K386.EX_ 8 07/19/1999 16:44 80306 BBCDD240 OS2LDR.MSG OS2LDR.MS_ 11 09/23/2000 17:55 8737 DE8E117C OS2MM.DLL OS2MM.DL_ 3 12/07/1998 10:04 243830 D70109A0 OS2UGL OS2UGL.___ 11 12/02/1999 14:12 15616 ACFC69CA OSO001.MSG OSO001.MS_ 8 12/04/1998 17:55 175769 8BFA1642 OSO001H.MSG OSO001H.MS_ 7 12/04/1998 17:55 241212 303B0481 PACKAGER.EXE PACKAGER.EX_ 9 07/19/1999 16:18 76464 B1B475D6 PBRUSH.EXE PBRUSH.EX_ 7 07/19/1999 16:20 183360 DD6BEB29 PDFSLA.EXE PDFSLA.EX_ 10 07/25/2000 00:00 18226 9FBE5971 PDUMPSYS.EXE PDUMPSYS.EX_ 10 07/25/2000 00:58 34365 50AC8CDD PDUMPUSR.EXE PDUMPUSR.EX_ 10 07/25/2000 00:58 34363 2573EC10 PL.KBL PL.KB_ 11 12/02/1999 14:19 980 F2F9E5B5 PL457.KBL PL457.KB_ 11 12/02/1999 14:19 882 AECFDA03 PMATM.DLL PMATM.DL_ 2 03/15/1999 18:36 224319 11C7F570 PMBIND.DLL PMBIND.DL_ 10 07/24/2000 22:55 60162 7B6ABDDC PMCHKDSK.EXE PMCHKDSK.EX_ 10 07/24/2000 23:01 28183 FB650FB5 PMCLIP.DLL PMCLIP.DL_ 10 07/24/2000 23:48 21315 D7548647 FixPak Corrective Service levels and disk layouts 45 October 18, 2000 - Warp 3 FixPak XR_W043 PMCTLS.DLL PMCTLS.DL_ 2 07/24/2000 21:20 568344 74C0EE34 PMDDE.DLL PMDDE.DL_ 10 07/24/2000 23:49 28170 9353EBCF PMDF.HLP PMDF.HL_ 8 01/09/1998 07:27 99751 BCE9E3DD PMDFMSG.DLL PMDFMSG.DL_ 9 07/28/1999 08:49 44436 3F51C356 PMDRAG.DLL PMDRAG.DL_ 11 07/24/2000 21:12 1731 80203C5E PMGPI.DLL PMGPI.DL_ 3 07/24/2000 20:31 240974 54C0BFCD PMGRE.DLL PMGRE.DL_ 11 08/17/2000 10:45 2231 840E2F7E PMMLE.DLL PMMLE.DL_ 11 07/24/2000 21:19 673 11270A60 PMPIC.DLL PMPIC.DL_ 9 07/24/2000 22:29 34870 42B0ACE8 PMPIC.TDF PMPIC.TD_ 11 07/24/2000 22:29 400 1E15A7BD PMPRINT.QPR PMPRINT.QP_ 11 10/14/1998 21:04 12657 9EA7F7BD PMSDMRI.DLL PMSDMRI.DL_ 11 06/17/1998 16:54 13312 FD9863DF PMSEEK.EXE PMSEEK.EX_ 10 07/24/2000 23:08 31285 7E449FE0 PMSHAPI.DLL PMSHAPI.DL_ 11 01/08/1998 16:40 4549 22E92C50 PMSPL.DLL PMSPL.DL_ 3 08/18/2000 15:36 286151 4C625204 PMSPL.TDF PMSPL.TD_ 11 08/18/2000 15:36 6930 8DC31673 PMVDMP.DLL PMVDMP.DL_ 9 07/24/2000 22:13 42979 4B52953A PMVDMP.TDF PMVDMP.TD_ 11 07/24/2000 22:13 1786 6619142B PMVIOP.DLL PMVIOP.DL_ 8 07/24/2000 22:12 57740 C58F2974 PMVIOP.TDF PMVIOP.TD_ 11 07/24/2000 22:12 2326 417547B6 PMWIN.DLL PMWIN.DL_ 11 07/24/2000 20:51 11264 94A98194 PMWP.DLL PMWP.DL_ 1 07/25/2000 00:21 961329 16E8396B PMWP.TDF PMWP.TD_ 11 07/25/2000 00:21 10855 7EDEFD46 PMWPMRI.DLL PMWPMRI.DL_ 9 07/25/2000 00:07 46054 A5CE3E76 PO.KBL PO.KB_ 11 12/02/1999 14:19 926 13EC7800 PRINTMAN.EXE PRINTMAN.EX_ 10 07/19/1999 16:54 43248 4B7A98E5 PROCDUMP.DOC PROCDUMP.DO_ 10 07/29/1998 18:07 63273 189C1459 PROCDUMP.EXE PROCDUMP.EX_ 9 07/25/2000 00:57 47647 6B49E39E PROGMAN.EXE PROGMAN.EX_ 8 07/19/1999 16:51 115328 03CE0799 PSSDMON.EXE PSSDMON.EX_ 10 07/24/2000 23:54 27117 F6D9EA78 PSTAT.EXE PSTAT.EX_ 11 07/24/2000 23:08 11044 4B853F4F PVDAPI.DLL PVDAPI.DL_ 10 07/24/2000 23:53 20398 7801728F QUECALLS.DLL QUECALLS.DL_ 11 08/26/1998 01:30 1024 DB25D550 RAS001.MSG RAS001.MS_ 11 01/09/1998 07:20 25739 5B41EDDD RASH.MSG RASH.MS_ 11 01/09/1998 07:20 11581 98CABDA3 README.DBG README.DB_ 11 05/20/1999 13:28 22934 D76AEEF6 RECOVER.COM RECOVER.CO_ 9 07/24/2000 23:09 48704 67FFD525 REGEDIT.EXE REGEDIT.EX_ 10 06/18/1999 09:31 32336 2B8B6362 REGEDIT.HLP REGEDIT.HL_ 10 07/19/1999 18:13 22682 E46C54AC RESTORE.EXE RESTORE.EX_ 10 07/24/2000 23:10 36080 5190E899 REXX.DLL REXX.DL_ 4 04/05/1999 09:56 266031 2CB50B8E REXXAPI.DLL REXXAPI.DL_ 10 07/07/1998 16:42 40995 22013324 REXXUTIL.DLL REXXUTIL.DL_ 7 08/23/2000 11:31 68119 4D4FB76B RO.KBL RO.KB_ 11 12/02/1999 14:19 944 AB98DE81 RSPDSPI.EXE RSPDSPI.EX_ 7 07/24/2000 23:47 93192 37DBCD59 RU.KBL RU.KB_ 11 12/02/1999 14:19 1144 48A696E0 RU441.KBL RU441.KB_ 11 12/02/1999 14:19 1260 196F635B S8514.DRV S8514.DR_ 9 07/19/1999 17:43 89776 E601AA2F SD.KBL SD.KB_ 11 12/02/1999 14:19 1036 702BC72E SEAMLESS.DLL SEAMLESS.DL_ 10 07/24/2000 22:49 49125 5D53D83D SECUTIL.DLL SECUTIL.DL_ 10 07/24/2000 23:53 21468 0C32C5EC FixPak Corrective Service levels and disk layouts 46 October 18, 2000 - Warp 3 FixPak XR_W043 SEMAINT.EXE SEMAINT.EX_ 9 07/24/2000 23:19 66064 55003FE8 SESAPI.DLL SESAPI.DL_ 10 07/24/2000 19:19 24155 8A8A57A9 SESDB.DLL SESDB.DL_ 10 07/24/2000 23:52 23411 9FD0DFD5 SESDMON.EXE SESDMON.EX_ 10 07/24/2000 23:54 26750 44D2EEC5 SESMGR.DLL SESMGR.DL_ 11 08/26/1998 00:51 1536 E6962283 SETBOOT.EXE SETBOOT.EX_ 10 07/24/2000 21:45 19760 DB57E92A SETUP.EXE SETUP.EX_ 6 07/19/1999 16:24 182448 38030DA4 SF.KBL SF.KB_ 11 12/02/1999 14:19 1036 30F78793 SHELL.DLL SHELL.DL_ 10 07/19/1999 16:50 32576 DA5FEBFA SIPANEL2.DLL SIPANEL2.DL_ 11 07/25/2000 00:31 53712 9B4BA2E8 SK.KBL SK.KB_ 11 12/02/1999 14:19 1008 42A1D014 SL.KBL SL.KB_ 11 12/02/1999 14:19 982 51F7B9B4 SLDAPI.DLL SLDAPI.DL_ 10 07/24/2000 23:52 22441 2FEBB040 SND.CPL SND.CP_ 11 07/19/1999 17:13 8192 E04657DB SNDBLST.DRV SNDBLST.DR_ 11 07/19/1999 17:08 13808 9F3A5354 SNDBLST2.DRV SNDBLST2.DR_ 11 07/19/1999 17:09 14464 853178BB SOFTDRAW.DLL SOFTDRAW.DL_ 3 07/24/2000 19:23 416439 CAC786BD SOM.DLL SOM.DL_ 7 04/28/1997 18:07 92009 2CA2A023 SOM.IR SOM.IR_ 5 03/12/1997 18:54 523185 402453DE SOMD.DLL SOMD.DL_ 3 03/12/1997 18:54 270638 CEA4A89C SOMD.MSG SOMD.MS_ 11 03/12/1997 18:54 15056 67D978FB SOMDD.EXE SOMDD.EX_ 10 03/12/1997 18:54 24928 3419526F SOMDSVR.EXE SOMDSVR.EX_ 10 03/12/1997 18:54 22800 6E2FC7B2 SOMEM.DLL SOMEM.DL_ 9 03/12/1997 18:54 40132 8B31F245 SOMIR.DLL SOMIR.DL_ 6 03/12/1997 18:54 110972 563D3A09 SOMK.MSG SOMK.MS_ 11 03/12/1997 18:54 3724 C7CDF169 SOMS.DLL SOMS.DL_ 10 03/12/1997 18:54 23074 719E33D8 SOMTC.DLL SOMTC.DL_ 9 03/12/1997 18:54 35768 1B67EDCC SOMU.DLL SOMU.DL_ 7 03/12/1997 18:54 81652 DFFA1C69 SOUND.DRV SOUND.DR_ 11 06/18/1999 09:31 3441 4F4AAE75 SOUNDREC.EXE SOUNDREC.EX_ 10 07/19/1999 17:13 51305 04E55DB1 SQ.KBL SQ.KB_ 11 12/02/1999 14:19 824 75B4805A SR.KBL SR.KB_ 11 12/02/1999 14:19 1222 8998A046 STRACE.INF STRACE.IN_ 7 01/09/1998 07:31 153828 8838C9D0 SV.KBL SV.KB_ 11 12/02/1999 14:19 946 80720FAB SYMB.PFM SYM1.PF_ 11 06/17/1998 14:49 679 46ACE0BD SYSDUMP.EXE SYSDUMP.EX_ 10 01/09/1998 07:29 16000 FE2B4A73 SYSEDIT.EXE SYSEDIT.EX_ 11 07/19/1999 16:28 18896 3611E2AA SYSINST1.EXE SYSINST1.EX_ 11 01/09/1998 06:54 4224 58970725 SYSINSTX.COM SYSINSTX.CO_ 10 09/23/2000 17:56 39472 E2FF1C21 SYSLEVEL.EXE SYSLEVEL.EX_ 9 07/24/2000 22:45 43024 807A7408 SYSLEVEL.FPK SYSLEVEL.FP_ 11 08/25/2000 15:27 165 311D3EF0 SYSLEVEL.MSG SYSLEVEL.MS_ 11 07/24/2000 22:45 1445 FA956E54 SYSLEVEL.SDS SYSLEVEL.SD_ 11 03/12/1997 18:54 265 735858E1 SYSLEVEL.SEM SYSLEVEL.SE_ 11 03/12/1997 18:54 191 D0B7D94A SYSLEVEL.SIR SYSLEVEL.SI_ 11 03/12/1997 18:54 188 A7693C50 SYSLEVEL.SRK SYSLEVEL.SR_ 11 03/12/1997 18:54 185 02859A09 SYSLEVEL.SUT SYSLEVEL.SUT 11 03/12/1997 18:54 177 A007547A SYSLOG.DLL SYSLOG.DL_ 11 07/24/2000 23:45 5681 2CE947FB SYSLOG.EXE SYSLOG.EX_ 11 07/24/2000 23:45 7204 8D3C8920 SYSLOGPM.EXE SYSLOGPM.EX_ 9 07/24/2000 23:46 35478 E708EE18 FixPak Corrective Service levels and disk layouts 47 October 18, 2000 - Warp 3 FixPak XR_W043 SYSMONO.FON SYSMONO.FO_ 10 06/17/1998 17:03 46255 88EACB2D SYSMONOI.FON SYSMONOI.FO_ 10 06/17/1998 17:03 46255 6803212B SYSSPLIT.CMD SYSSPLIT.CM_ 11 01/07/1998 17:08 3712 A32FABC8 SYSTEM.DRV SYSTEM.DR_ 11 07/19/1999 16:56 2304 275E5C72 TASKMAN.EXE TASKMAN.EX_ 11 07/19/1999 16:52 3744 E081632B TDFLST.CMD TDFLST.CM_ 11 04/05/1999 09:56 13564 61543592 TEDIT.EXE TEDIT.EX_ 11 01/09/1998 04:02 9390 C58DDFE7 TEXTCON1.EXE TEXTCON1.EX_ 10 11/23/1999 20:12 49011 5916B6E7 TFFLST.CMD TFFLST.CM_ 11 04/05/1999 09:56 4638 12A615D0 TH.KBL TH.KB_ 11 12/02/1999 14:19 1184 3D2E382C TH190.KBL TH190.KB_ 11 12/02/1999 14:19 1184 BBB3E598 TIMER.DRV TIMER.DR_ 11 07/19/1999 17:07 4464 C7D0FA88 TIMES.FON TIMES.FO_ 6 01/19/1998 13:36 257547 C00001C9 TNR.OFM TNR.OF_ 11 02/12/1998 09:24 4882 65F1B2C9 TNR.PFB TNR.PF_ 5 02/12/1998 09:24 119332 363246F5 TNR.PFM TN1.PF_ 11 02/12/1998 09:24 1103 0CCC4E38 TNRB.OFM TNRB.OF_ 11 02/12/1998 09:24 4898 551E8409 TNRB.PFB TNRB.PF_ 5 02/12/1998 09:24 123083 E9834D17 TNRB.PFM TNR1.PF_ 11 02/12/1998 09:24 1112 6035F3E3 TNRBI.OFM TNRBI.OF_ 11 02/12/1998 09:24 4912 3A912F8F TNRBI.PFB TNRBI.PF_ 5 02/12/1998 09:24 134003 3B146D03 TNRBI.PFM TNRB1.PF_ 11 02/12/1998 09:24 1118 8EDE75CB TNRI.OFM TNRI.OF_ 11 02/12/1998 09:24 4903 00B3E83C TNRI.PFB TNRI.PF_ 5 02/12/1998 09:24 131366 2C27E764 TNRI.PFM TNR2.PF_ 11 02/12/1998 09:24 1114 27AE6580 TOOLHELP.DLL TOOLHELP.DL_ 11 07/19/1999 16:14 14112 AB61F670 TOUCH.DRV TOUCH.DR_ 11 07/19/1999 18:10 15760 044C9CF6 TR.KBL TR.KB_ 11 12/02/1999 14:19 962 5DC99E17 TR440.KBL TR440.KB_ 11 12/02/1999 14:19 1042 6D22006E TRACE.DOC TRACE.DO_ 10 04/05/1999 09:56 64057 95DDD0A2 TRACE.EXE TRACE.EX_ 9 08/24/2000 09:42 35280 886E8B4D TRACEFMT.EXE TRACEFMT.EX_ 5 04/05/1999 20:44 155698 2B76B25F TRACEGET.EXE TRACEGET.EX_ 10 08/24/2000 09:42 22026 1126D207 TRAPDUMP.EXE TRAPDUMP.EX_ 10 07/25/2000 00:58 16352 B0AFAABD TRAPLOG.EXE TRAPLOG.EX_ 10 01/09/1998 07:30 15056 5EE4C314 TRC0007.TFF TRC0007.TF_ 11 07/24/2000 22:37 1041 11FA72A8 TRC00C4.TFF TRC00C4.TF_ 11 07/24/2000 22:29 289 DB9FA422 TRC00C6.TFF TRC00C6.TF_ 11 08/18/2000 15:36 11255 23E26239 TRC0118.TFF TRC0118.TF_ 11 08/24/2000 09:41 2746 4B813DA6 TRC0119.TFF TRC0119.TF_ 11 07/24/2000 21:43 3786 6E25B20C TRC012C.TFF TRC012C.TF_ 11 07/24/2000 22:13 3301 47BB5625 TRC012D.TFF TRC012D.TF_ 11 07/24/2000 22:12 4739 7FC7B3D3 TRC012E.TFF TRC012E.TF_ 11 07/25/2000 00:21 25717 5A554E19 TRCUST.EXE TRCUST.EX_ 8 07/24/2000 19:28 98773 BBF8F3FC TRSPOOL.DOC TRSPOOL.DO_ 1 04/05/1999 09:56 6638 FC5E989C TRSPOOL.EXE TRSPOOL.EX_ 10 08/18/2000 15:38 27986 E0EF0896 TW.KBL TW.KB_ 11 12/02/1999 14:19 780 23906445 UA.KBL UA.KB_ 11 12/02/1999 14:19 1476 FDE0FA51 UCDFS.DLL UCDFS.DL_ 8 01/08/1998 23:30 13264 8BD020DB UCONV.DLL UCONV.DL_ 10 12/02/1999 14:21 22819 AAC74ECC UCSTBL.LST UCSTBL.LS_ 11 11/22/1999 11:42 1789 78EC2A97 FixPak Corrective Service levels and disk layouts 48 October 18, 2000 - Warp 3 FixPak XR_W043 UHPFS.DLL UHPFS.DL_ 7 08/24/2000 09:39 106000 DB3D3386 UK.KBL UK.KB_ 11 12/02/1999 14:19 816 47EA3FBA UK168.KBL UK168.KB_ 11 12/02/1999 14:19 850 B43C6228 ULS.REP ULS.RE_ 11 11/23/1999 13:33 19504 7FA91C1F ULSACT01.MSG ULSACT01.MS_ 11 11/23/1999 13:33 907 CCFEF741 ULSCAU01.MSG ULSCAU01.MS_ 11 11/23/1999 13:33 899 5B2E152F ULSDET01.MSG ULSDET01.MS_ 7 11/23/1999 13:33 903 A0B1A1BE ULSERR01.MSG ULSERR01.MS_ 11 11/23/1999 13:33 1967 DB03FAC5 UNICODE.SYS UNICODE.SY_ 11 12/02/1999 14:13 20014 71350E75 UNIKBD.DLL UNIKBD.DL_ 10 12/02/1999 14:13 28515 58278529 UNINSTAL.EXE UNINSTAL.EX_ 7 07/25/2000 00:51 94313 224D0BB8 UNPACK2.EXE UNPACK2.EX_ 6 08/18/2000 15:39 79728 9265A7C7 US.KBL US.KB_ 11 12/02/1999 14:19 774 8316962C USDV.KBL USDV.KB_ 11 12/02/1999 14:19 942 9E519962 USDVL.KBL USDVL.KB_ 11 12/02/1999 14:19 924 040B0F6A USDVR.KBL USDVR.KB_ 11 12/02/1999 14:19 942 2624513F USER.EXE USER.EX_ 4 07/19/1999 17:02 281008 7AFB68FB USINTER.KBL USINTER.KB_ 11 12/02/1999 14:19 1032 5FE88FD9 VBIOS.SYS VBIOS.SY_ 11 07/24/2000 23:23 8816 DBA67F95 VCMOS.SYS VCMOS.SY_ 11 07/24/2000 23:23 2272 85C719BE VDMA.SYS VDMAPS2.SY_ 11 07/24/2000 23:25 14329 018914A3 VDMA.SYS VDMAAT.SY_ 11 07/24/2000 23:24 11465 7C819F8B VDPMI.SYS VDPMI.SY_ 11 07/24/2000 23:27 22385 7586B6FD VDPX.SYS VDPX.SY_ 10 07/24/2000 23:02 25857 FB2744C4 VER.DLL VER.DL_ 4 07/19/1999 16:13 9008 5353A52A VIOTBL.DCP VIOTBL.DC_ 10 12/02/1999 14:20 225355 406F489E VIOTBL.ISO VIOTBL.IS_ 9 12/02/1999 14:21 230105 2FE2121C VMAN.DLL VMAN.DL_ 9 08/06/2000 12:13 61017 EEF32ED5 VMANWIN.SYS VMANWIN.SY_ 11 07/10/2000 14:07 3040 C2F3E282 VW32S.SYS VW32S.SY_ 9 07/24/2000 21:47 18289 DA76264F VWIN.SYS VWIN.SY_ 10 07/24/2000 23:41 26912 1EF1992A WIN.COM WIN.CO_ 10 07/19/1999 17:03 44651 91A9CCC5 WINFILE.EXE WINFILE.EX_ 7 07/19/1999 16:52 146960 A5D456E1 WINOS2.COM WINOS2.CO_ 10 07/19/1999 17:03 16592 34A9D3F5 WINSCLIP.DLL WINSCLIP.DL_ 11 07/19/1999 16:49 14848 063E0199 WINSDDE.DLL WINSDDE.DL_ 11 07/19/1999 16:49 18432 A4D90F73 WINSHELD.EXE WINSHELD.EX_ 11 07/19/1999 16:49 22016 50F1265D WINSMSG.DLL WINSMSG.DL_ 11 07/19/1999 16:49 28441 331BB9D3 WINVER.EXE WINVER.EX_ 11 07/19/1999 16:27 3904 A3F20381 WPCMPNP.DLL WPCMPNP.DL_ 7 01/09/1998 06:23 73433 C85C4DFF WPCONFIG.DLL WPCONFIG.DL_ 1 07/26/1999 22:10 220139 9DB983B4 WPCONMRI.DLL WPCONMRI.DL_ 10 01/09/1998 06:42 16777 C0C8F0AC WPHELP.HLP WPHELP.HL_ 2 07/24/2000 23:36 713080 B8D0EBE2 WPPRINT.DLL WPPRINT.DL_ 3 07/25/2000 00:25 365740 2DDCFA1D WPPRINT.HLP WPPRINT.HL_ 8 01/09/1998 06:13 71408 27006DF2 WPPRTMRI.DLL WPPRTMRI.DL_ 9 01/09/1998 06:13 54486 EBE95633 WRITE.EXE WRITE.EX_ 5 07/19/1999 16:33 244976 C99E812D WSPDBF.DRV WSPDBF.DR_ 8 07/19/1999 17:38 108512 E4E01A2F WSPDSBF.DRV WSPDSBF.DR_ 8 07/19/1999 17:39 109568 2B67AE15 WSPDSF.DRV WSPDSF.DR_ 8 07/19/1999 17:38 106032 7F2A0817 WSPDSSF.DRV WSPDSSF.DR_ 8 07/19/1999 17:39 107088 205D36A3 FixPak Corrective Service levels and disk layouts 49 October 18, 2000 - Warp 3 FixPak XR_W043 XCOPY.EXE XCOPY.EX_ 9 07/24/2000 23:37 51616 D97DE90A XDFH.MSG XDFH.MS_ 9 07/24/2000 22:44 1045 4FE7C3D5 XPG00420.TBL XPG00420.TB_ 11 11/22/1999 12:17 27264 48667C1E XPG00864.TBL XPG00864.TB_ 11 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 3.01 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3005_ System Id: 1000 Component Id: 562274700 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- BVHVGA.DLL BVHVGA.DL_ 13 02/17/1998 15:37 31847 3C3497E0 DF_DEB.EXE DF_DEB.EX_ 13 07/24/2000 21:11 136061 1190A466 DF_RET.EXE DF_RET.EX_ 13 07/24/2000 21:11 136029 9A2915DE DOSCALL1.DLL DOSCALL1.DL_ 11 07/24/2000 19:24 125480 45DF7BAD DOSCALL1.TDF DOSCALL1.TD_ 13 07/24/2000 19:24 5426 EE8777BD DOSKRNL DOSKRNL.___ 13 07/24/2000 19:21 30509 0DF905BB GETMONID.CMD GETMONID.CM_ 13 03/15/1999 13:49 2426 47BB3FE5 INSTALL.EXE INSTALL.EX_ 12 07/24/2000 20:57 302747 9C58053F KBDBASE.SYS KBDBASE.SY_ 13 07/19/2000 12:30 25021 B4C8D21E KERNEL.SDF KERNEL.SD_ 13 07/24/2000 21:13 55657 D6B3FFE8 KERNELD.SDF KERNELD.SD_ 13 07/24/2000 21:14 55735 053970B5 KRNLBDEV.TDF KRNLBDEV.TD_ 13 09/25/2000 13:40 3314 850AEBB5 KRNLBFS.TDF KRNLBFS.TD_ 13 09/25/2000 13:40 4572 CB03AE0C KRNLBLDR.TDF KRNLBLDR.TD_ 13 09/25/2000 13:40 5497 F500F82E KRNLBPG.TDF KRNLBPG.TD_ 13 09/25/2000 13:40 3203 C0FC9F8E KRNLBSEL.TDF KRNLBSEL.TD_ 13 09/25/2000 13:40 2369 09BD37A2 KRNLBSEM.TDF KRNLBSEM.TD_ 13 09/25/2000 13:40 1353 67689620 KRNLBSM.TDF KRNLBSM.TD_ 13 09/25/2000 13:40 1321 93064B4B KRNLBTK.TDF KRNLBTK.TD_ 13 09/25/2000 13:40 14180 F9931D8F KRNLBTOM.TDF KRNLBTOM.TD_ 13 09/25/2000 13:40 925 0221FEC6 FixPak Corrective Service levels and disk layouts 50 October 18, 2000 - Warp 3 FixPak XR_W043 KRNLBVDM.TDF KRNLBVDM.TD_ 13 09/25/2000 13:40 17560 7F99BF47 KRNLBVM.TDF KRNLBVM.TD_ 13 09/25/2000 13:40 5293 5F083CD3 KRNLDDEV.TDF KRNLDDEV.TD_ 13 09/25/2000 13:39 3314 8FA379A9 KRNLDFS.TDF KRNLDFS.TD_ 13 09/25/2000 13:39 4538 1488A588 KRNLDLDR.TDF KRNLDLDR.TD_ 13 09/25/2000 13:39 5500 B05FC61C KRNLDPG.TDF KRNLDPG.TD_ 13 09/25/2000 13:39 3284 28174535 KRNLDSEL.TDF KRNLDSEL.TD_ 13 09/25/2000 13:39 2425 96282968 KRNLDSEM.TDF KRNLDSEM.TD_ 13 09/25/2000 13:39 1493 72E5546A KRNLDSM.TDF KRNLDSM.TD_ 13 09/25/2000 13:39 1321 0AF11429 KRNLDTK.TDF KRNLDTK.TD_ 13 09/25/2000 13:39 14286 F5479021 KRNLDTOM.TDF KRNLDTOM.TD_ 13 09/25/2000 13:39 953 5339EA8A KRNLDVDM.TDF KRNLDVDM.TD_ 13 09/25/2000 13:39 17635 72A5B58E KRNLDVM.TDF KRNLDVM.TD_ 13 09/25/2000 13:39 5405 429C0D13 KRNLRDEV.TDF KRNLRDEV.TD_ 13 09/25/2000 13:37 3314 65DBD521 KRNLRFS.TDF KRNLRFS.TD_ 13 09/25/2000 13:37 4597 4D3A8E1F KRNLRLDR.TDF KRNLRLDR.TD_ 13 09/25/2000 13:37 5472 26949C21 KRNLRPG.TDF KRNLRPG.TD_ 13 09/25/2000 13:38 3203 38A6A180 KRNLRSEL.TDF KRNLRSEL.TD_ 13 09/25/2000 13:38 2369 3BFFF7B3 KRNLRSEM.TDF KRNLRSEM.TD_ 13 09/25/2000 13:38 1353 92536947 KRNLRSM.TDF KRNLRSM.TD_ 13 09/25/2000 13:38 1321 FCF4EF39 KRNLRTK.TDF KRNLRTK.TD_ 13 09/25/2000 13:38 14096 47A303D2 KRNLRTOM.TDF KRNLRTOM.TD_ 13 09/25/2000 13:38 897 E628FE9F KRNLRVDM.TDF KRNLRVDM.TD_ 13 09/25/2000 13:37 17242 5C2B66A0 KRNLRVM.TDF KRNLRVM.TD_ 13 09/25/2000 13:38 5293 E5D867BB MONCALLS.TDF MONCALLS.TD_ 13 07/24/2000 19:22 1139 6AB63A8C OS2CHAR.TDF OS2CHAR.TD_ 13 07/24/2000 19:24 13889 148319BB OS2KRNL OS2KRNL.___ 11 09/25/2000 13:38 634314 1C5B6FAF OS2KRNL.TDF OS2KRNL.TD_ 13 09/25/2000 13:37 16609 6D399A29 OS2KRNLB.TDF OS2KRNLB.TD_ 13 09/25/2000 13:40 16609 7B7DE4C6 OS2KRNLD.TDF OS2KRNLD.TD_ 13 09/25/2000 13:39 16609 0DCE8081 OS2LDR OS2LDR.___ 13 09/23/2000 17:54 33280 9934916D PMDF.EXE PMDF.EX_ 13 07/24/2000 21:13 260024 C7C82016 PMDFINST.CMD PMDFINST.CM_ 13 01/07/1998 17:10 18501 61C6F001 PMGPI.TDF PMGPI.TD_ 13 07/24/2000 20:19 12338 74FB2856 PMGRE.TDF PMGRE.TD_ 13 07/24/2000 21:12 1062 512B0C38 PMMERGE.DLL PMMERGE.DL_ 12 07/24/2000 21:12 1335998 DA95F37A PMSHAPI.TDF PMSHAPI.TD_ 13 07/24/2000 21:12 6751 0D242ED0 PMWIN.TDF PMWIN.TD_ 13 07/24/2000 21:12 13570 CBB0C971 PMWIN32.SDF PMWIN32.SD_ 13 07/24/2000 21:14 33388 BEE59D2E QUECALLS.TDF QUECALLS.TD_ 13 07/24/2000 19:24 1319 B7B21859 RSPINST.EXE RSPINST.EX_ 13 07/24/2000 21:03 289706 23A17478 RUPINST2.EXE RUPINST2.EX_ 12 07/24/2000 21:00 173120 21E0BCB6 RXVIDCFG.DLL RXVIDCFG.DL_ 13 04/07/1999 16:04 14741 4698736B SESDD32.SYS SESDD32.SY_ 13 07/24/2000 20:47 118833 3F07B28D SESMGR.TDF SESMGR.TD_ 13 07/24/2000 19:24 1877 8A6DE498 SHELL.SDF SHELL.SD_ 13 07/24/2000 21:14 20418 CB4388DE SOMCT.DLL SOMCT.DL_ 13 04/28/1997 18:06 42841 A6FF6813 SOMSEC.DLL SOMSEC.DL_ 11 04/28/1997 18:06 33214 1A34710E SOMUC.DLL SOMUC.DL_ 13 04/28/1997 18:06 86276 BA4B46D0 STRACE.EXE STRACE.EX_ 13 07/24/2000 21:15 41010 6A6A85F6 SYSINST2.EXE SYSINST2.EX_ 13 07/24/2000 20:59 171808 5FC0B0A7 FixPak Corrective Service levels and disk layouts 51 October 18, 2000 - Warp 3 FixPak XR_W043 SYSLEVEL.SCT SYSLEVEL.SC_ 13 06/16/1998 17:42 187 9FD92CA3 SYSLEVEL.SUC SYSLEVEL.SUC 13 06/16/1998 17:42 191 665CE147 TRACE.HLP TRACE.HL_ 13 04/05/1999 18:12 29376 DF1AC854 TRACEFMT.ICO TRACEFMT.IC_ 13 03/12/1997 17:08 2692 510E56CA TRC0000.TFF TRC0000.TF_ 13 01/25/1999 10:24 189 78DB2563 TRC0003.TFF TRC0003.TF_ 13 01/25/1999 10:24 1503 0DDD868D TRC0004.TFF TRC0004.TF_ 13 09/25/2000 11:01 4754 EDA2826B TRC0005.TFF TRC0005.TF_ 13 09/25/2000 13:40 38800 6E9E4F39 TRC0006.TFF TRC0006.TF_ 13 01/25/1999 09:53 12356 8DD5674E TRC0010.TFF TRC0010.TF_ 13 07/24/2000 19:24 13359 60C2A17F TRC0016.TFF TRC0016.TF_ 13 07/24/2000 19:24 1719 29E34E3E TRC0017.TFF TRC0017.TF_ 13 07/24/2000 19:24 5561 E8B3BD71 TRC0018.TFF TRC0018.TF_ 13 07/24/2000 19:24 39488 29C61366 TRC00C0.TFF TRC00C0.TF_ 13 07/24/2000 21:12 16022 20415253 TRC00C2.TFF TRC00C2.TF_ 13 07/24/2000 21:12 34340 3A188B88 TRC00C3.TFF TRC00C3.TF_ 13 07/24/2000 21:12 3984 F96F4AC7 TRC00C5.TFF TRC00C5.TF_ 13 07/24/2000 20:19 32994 870F1018 TRC0100.TFF TRC0100.TF_ 13 09/25/2000 13:40 5475 04A7A7D9 TRC0101.TFF TRC0101.TF_ 13 09/25/2000 13:40 7557 1122EE24 TRC0102.TFF TRC0102.TF_ 13 09/25/2000 13:40 34804 B4DE818E TRC0103.TFF TRC0103.TF_ 13 09/25/2000 13:40 9891 254E2B21 TRC0104.TFF TRC0104.TF_ 13 09/25/2000 13:40 5135 C63FDFBD TRC0105.TFF TRC0105.TF_ 13 09/25/2000 13:40 27788 E221FE02 TRC0106.TFF TRC0106.TF_ 13 09/25/2000 13:40 1835 59FAB074 TRC0107.TFF TRC0107.TF_ 12 09/25/2000 13:40 3732 0307A335 TRC0108.TFF TRC0108.TF_ 11 09/25/2000 13:40 9082 33D53052 TRC0109.TFF TRC0109.TF_ 13 09/25/2000 13:40 1713 1C40CCB5 TRC010A.TFF TRC010A.TF_ 13 09/25/2000 13:40 1029 FDEB4F4F TRCFORMT.DLL TRCFORMT.DL_ 13 10/14/1998 20:27 26630 1C6837BB VCFGCID.CMD VCFGCID.CM_ 13 03/15/1999 13:49 13187 E79BE969 VMOUSE.SYS VMOUSE.SY_ 13 07/24/2000 19:57 17280 C234CFE8 VPIC.SYS VPIC.SY_ 13 07/24/2000 19:58 9942 91BA55C2 VPICPARM.SYS VPICPARM.SY_ 13 07/24/2000 19:58 736 A3AC54AA VTIMER.SYS VTIMER.SY_ 13 07/24/2000 19:59 9936 B627CF2E VXGA.SYS VXGA.SY_ 12 02/17/1998 15:37 24771 0727963F ************************************************************************ Product location on CSD: A:\FIX\OS2.3 Product name: "IBM OS/2 Base Operating System" Standard Edition 3.02 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3006_ System Id: 1000 Component Id: 5639A5500 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* FixPak Corrective Service levels and disk layouts 52 October 18, 2000 - Warp 3 FixPak XR_W043 ..\..\VT ..\..\VT\* ..\..\PSFONTS ..\..\PSFONTS\* ..\..\LANGUAGE ..\..\LANGUAGE\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- ALR.PSD ALR.PS_ 16 07/24/2000 19:16 18432 E5F17A7D CAVERUN.PSD CAVERUN.PS_ 16 07/24/2000 19:17 29184 8E5B1630 DF_DEB.EXE DF_DEB.EX_ 16 07/25/2000 00:54 144949 12423600 DF_RET.EXE DF_RET.EX_ 16 07/25/2000 00:53 144917 6CEE25DF DOSCALL1.DLL DOSCALL1.DL_ 15 07/24/2000 21:56 137960 10EF703F DOSCALL1.SYM DOSCALL1.SY_ 16 07/24/2000 21:56 42740 8C464683 DOSCALL1.TDF DOSCALL1.TD_ 16 07/24/2000 21:56 5534 A4588FDF DOSKRNL DOSKRNL.___ 16 07/24/2000 21:31 30525 C9052EFD INSTALL.EXE INSTALL.EX_ 14 07/25/2000 00:37 304595 D6A93019 KBDBASE.SYS KBDBASE.SY_ 16 07/19/2000 12:34 24989 DD68564A KERNEL.SDF KERNEL.SD_ 16 07/25/2000 00:57 57011 6C2C0512 KERNELD.SDF KERNELD.SD_ 16 07/25/2000 00:57 57136 056B67DC KRNLBDEV.TDF KRNLBDEV.TD_ 16 09/25/2000 13:40 4279 4A3DE8BD KRNLBFS.TDF KRNLBFS.TD_ 16 09/25/2000 13:40 4899 46304E8F KRNLBLDR.TDF KRNLBLDR.TD_ 16 09/25/2000 13:40 5609 865BDB7F KRNLBPG.TDF KRNLBPG.TD_ 16 09/25/2000 13:40 3427 6AD4B4BB KRNLBSEL.TDF KRNLBSEL.TD_ 16 09/25/2000 13:40 2755 B32DA9CC KRNLBSEM.TDF KRNLBSEM.TD_ 16 09/25/2000 13:40 1764 EB8C892C KRNLBSM.TDF KRNLBSM.TD_ 16 09/25/2000 13:40 1321 36FCF4D7 KRNLBTK.TDF KRNLBTK.TD_ 16 09/25/2000 13:40 15892 E4C075FD KRNLBTOM.TDF KRNLBTOM.TD_ 16 09/25/2000 13:40 1009 9BFC4126 KRNLBVDM.TDF KRNLBVDM.TD_ 16 09/25/2000 13:40 17831 4FD6D8B1 KRNLBVM.TDF KRNLBVM.TD_ 16 09/25/2000 13:40 5321 BA713337 KRNLDDEV.TDF KRNLDDEV.TD_ 16 09/25/2000 13:37 4279 0F9ABCB2 KRNLDFS.TDF KRNLDFS.TD_ 16 09/25/2000 13:37 4865 D0AC8946 KRNLDLDR.TDF KRNLDLDR.TD_ 16 09/25/2000 13:38 5637 A802D470 KRNLDPG.TDF KRNLDPG.TD_ 16 09/25/2000 13:38 3508 12CA5953 KRNLDSEL.TDF KRNLDSEL.TD_ 16 09/25/2000 13:38 2867 BD9877B6 KRNLDSEM.TDF KRNLDSEM.TD_ 16 09/25/2000 13:38 1932 BC04424E KRNLDSM.TDF KRNLDSM.TD_ 16 09/25/2000 13:38 1321 2BAED117 KRNLDTK.TDF KRNLDTK.TD_ 16 09/25/2000 13:38 16023 2F86D4B3 KRNLDTOM.TDF KRNLDTOM.TD_ 16 09/25/2000 13:38 1037 2F5B8648 KRNLDVDM.TDF KRNLDVDM.TD_ 16 09/25/2000 13:38 17881 2A62A101 KRNLDVM.TDF KRNLDVM.TD_ 16 09/25/2000 13:38 5433 5F8C7812 KRNLRDEV.TDF KRNLRDEV.TD_ 16 09/25/2000 13:39 4279 616E3EC6 KRNLRFS.TDF KRNLRFS.TD_ 16 09/25/2000 13:39 4899 4B693890 KRNLRLDR.TDF KRNLRLDR.TD_ 16 09/25/2000 13:39 5609 BA5CF59D KRNLRPG.TDF KRNLRPG.TD_ 16 09/25/2000 13:39 3427 239EBD53 KRNLRSEL.TDF KRNLRSEL.TD_ 16 09/25/2000 13:39 2755 B70AE9C1 KRNLRSEM.TDF KRNLRSEM.TD_ 16 09/25/2000 13:39 1764 315FD8D3 FixPak Corrective Service levels and disk layouts 53 October 18, 2000 - Warp 3 FixPak XR_W043 KRNLRSM.TDF KRNLRSM.TD_ 16 09/25/2000 13:39 1321 5158EBAC KRNLRTK.TDF KRNLRTK.TD_ 16 09/25/2000 13:39 15808 18D65227 KRNLRTOM.TDF KRNLRTOM.TD_ 16 09/25/2000 13:39 981 BCC6A059 KRNLRVDM.TDF KRNLRVDM.TD_ 16 09/25/2000 13:39 17513 1896CC3E KRNLRVM.TDF KRNLRVM.TD_ 16 09/25/2000 13:39 5321 1E05F612 MONCALLS.TDF MONCALLS.TD_ 16 07/24/2000 21:51 1139 6AB4753C OS2APIC.PSD OS2APIC.PS_ 16 07/24/2000 19:18 31232 06DFE794 OS2CHAR.TDF OS2CHAR.TD_ 16 07/24/2000 21:56 13889 89827E0A OS2KRNL OS2KRNL.___ 15 09/25/2000 13:39 729234 BDC9CDE4 OS2KRNL.TDF OS2KRNL.TD_ 16 09/25/2000 13:39 16837 05503D4D OS2KRNLB.SYM OS2KRNLB.SY_ 15 09/25/2000 13:40 192612 0BD959BA OS2KRNLB.TDF OS2KRNLB.TD_ 16 09/25/2000 13:40 16837 98918FF7 OS2KRNLD.SYM OS2KRNLD.SY_ 15 09/25/2000 13:37 195604 B1CC4FB8 OS2KRNLD.TDF OS2KRNLD.TD_ 16 09/25/2000 13:37 16867 ABA5ADB7 OS2KRNLR.SYM OS2KRNLR.SY_ 13 09/25/2000 13:39 173652 89FEE965 OS2LDR OS2LDR.___ 16 09/23/2000 17:54 35000 3A155991 PMCTLS.SYM PMCTLS.SY_ 15 07/24/2000 21:20 43508 05FFEC59 PMDD.SYM PMDD.SY_ 16 07/24/2000 23:06 2740 39C734BF PMDDE.SYM PMDDE.SY_ 16 07/24/2000 23:49 2500 D2133706 PMDF.EXE PMDF.EX_ 15 07/25/2000 00:56 260028 0DE435BE PMDRAG.SYM PMDRAG.SY_ 16 07/24/2000 21:12 36 FC6F4BE7 PMGPI.SYM PMGPI.SY_ 16 07/24/2000 20:32 46708 A60E75F4 PMGPI.TDF PMGPI.TD_ 16 07/24/2000 20:32 12338 4A7B283F PMGRE.TDF PMGRE.TD_ 16 08/18/2000 07:41 1062 3CAC6ADE PMMERGE.DLL PMMERGE.DL_ 14 08/18/2000 07:42 1336372 3CB34385 PMMERGE.SYM PMMERGE.SY_ 16 08/18/2000 07:41 92564 72FC458D PMMLE.SYM PMMLE.SY_ 16 07/24/2000 21:19 36 CC21FB55 PMPIC.SYM PMPIC.SY_ 16 07/24/2000 22:29 8436 C698A770 PMPRINT.SYM PMPRINT.SY_ 16 08/18/2000 15:35 1636 1A207904 PMSHAPI.TDF PMSHAPI.TD_ 14 08/18/2000 07:41 6751 6AB9DC9C PMSHELL.SYM PMSHELL.SY_ 16 07/25/2000 00:06 500 BDC92418 PMSPL.SYM PMSPL.SY_ 16 08/18/2000 15:36 32436 4C9B0A64 PMSPOOL.SYM PMSPOOL.SY_ 16 07/26/1999 19:33 404 BAFD842C PMVDMP.SYM PMVDMP.SY_ 16 07/24/2000 22:13 5268 743EDF3C PMVIOP.SYM PMVIOP.SY_ 16 07/24/2000 22:12 6404 28F623A5 PMWIN.TDF PMWIN.TD_ 16 08/18/2000 07:41 13570 202012E2 PMWIN32.SDF PMWIN32.SD_ 16 07/25/2000 00:57 33419 16C2F123 PMWP.SYM PMWP.SY_ 16 07/25/2000 00:21 95972 80AE9164 PROLIANT.PSD PROLIANT.PS_ 16 07/24/2000 19:18 18944 9B185EE4 QUECALLS.TDF QUECALLS.TD_ 16 07/24/2000 21:56 1319 48BC83B3 RSPDDI.EXE RSPDDI.EX_ 16 07/24/2000 22:57 22073 25D3A600 RSPINST.EXE RSPINST.EX_ 15 07/25/2000 00:46 290825 3A06E599 RUPINST2.EXE RUPINST2.EX_ 14 07/25/2000 00:41 172096 9E0129FD SESDD32.SYS SESDD32.SY_ 16 09/25/2000 10:48 118833 EC906600 SESMGR.TDF SESMGR.TD_ 16 07/24/2000 21:56 1877 5EE631E5 SHELL.SDF SHELL.SD_ 16 07/25/2000 00:57 20425 B0547CB6 STRACE.EXE STRACE.EX_ 16 07/25/2000 00:58 41010 783585F5 SYSINST2.EXE SYSINST2.EX_ 16 07/25/2000 00:41 170784 00D74AB5 SYSLOGPM.EXE SYSLOGPM.EX_ 16 07/24/2000 23:46 35478 E708EE18 TRACE.HLP TRACE.HL_ 16 04/05/1999 20:44 29376 DFB82054 TRC0000.TFF TRC0000.TF_ 16 08/11/1998 19:53 189 CEDB268C FixPak Corrective Service levels and disk layouts 54 October 18, 2000 - Warp 3 FixPak XR_W043 TRC0003.TFF TRC0003.TF_ 16 08/11/1998 19:53 1503 B3358691 TRC0004.TFF TRC0004.TF_ 16 09/25/2000 10:42 4754 FA4D826B TRC0005.TFF TRC0005.TF_ 16 09/25/2000 13:40 39307 E9EF5D99 TRC0006.TFF TRC0006.TF_ 16 08/11/1998 18:51 12356 AF80674E TRC0010.TFF TRC0010.TF_ 16 07/24/2000 21:56 13647 C63E083D TRC0016.TFF TRC0016.TF_ 16 07/24/2000 21:56 1719 7FE34E65 TRC0017.TFF TRC0017.TF_ 16 07/24/2000 21:56 5561 3EB3BD99 TRC0018.TFF TRC0018.TF_ 16 07/24/2000 21:56 39488 9F261368 TRC00C0.TFF TRC00C0.TF_ 16 08/18/2000 07:41 16022 20131D13 TRC00C2.TFF TRC00C2.TF_ 16 08/18/2000 07:41 34340 73708B82 TRC00C3.TFF TRC00C3.TF_ 16 08/18/2000 07:41 3984 8EEF4A6B TRC00C5.TFF TRC00C5.TF_ 16 07/24/2000 20:32 32994 87037AD8 TRC0100.TFF TRC0100.TF_ 13 09/25/2000 13:40 7355 BE5C1C68 TRC0101.TFF TRC0101.TF_ 16 09/25/2000 13:40 8178 79210C9E TRC0102.TFF TRC0102.TF_ 16 09/25/2000 13:40 35318 620B6A64 TRC0103.TFF TRC0103.TF_ 16 09/25/2000 13:40 10111 3D6CAA6A TRC0104.TFF TRC0104.TF_ 16 09/25/2000 13:40 5574 8FC9972B TRC0105.TFF TRC0105.TF_ 16 09/25/2000 13:40 31306 2AB9C9AE TRC0106.TFF TRC0106.TF_ 16 09/25/2000 13:40 1835 B1FAB071 TRC0107.TFF TRC0107.TF_ 16 09/25/2000 13:40 4462 152E7E07 TRC0108.TFF TRC0108.TF_ 16 09/25/2000 13:40 9131 F3DB24C9 TRC0109.TFF TRC0109.TF_ 16 09/25/2000 13:40 2483 7817B7CF TRC010A.TFF TRC010A.TF_ 16 09/25/2000 13:40 1175 86E593DF TRCFORMT.DLL TRCFORMT.DL_ 16 10/14/1998 22:11 26630 1C838DBB TRICRD.PSD TRICRD.PS_ 16 07/24/2000 19:18 4608 56023051 V1_EBI2.PSD V1_EBI2.PS_ 14 07/24/2000 19:17 19456 0D290E76 VIPERMP.PSD VIPERMP.PS_ 16 07/24/2000 19:19 6656 6FB5B2A8 VMOUSE.SYS VMOUSE.SY_ 16 07/24/2000 23:32 17280 230A9DB6 VPIC.SYS VPIC.SY_ 16 07/24/2000 23:33 9942 2997CF70 VPICPARM.SYS VPICPARM.SY_ 15 07/24/2000 23:33 736 A3AC54B7 VTIMER.SYS VTIMER.SY_ 16 07/24/2000 23:34 10576 D7DD634F WYSE.PSD WYSE.PS_ 16 07/24/2000 19:19 3072 AF5DC006 ************************************************************************ Product location on CSD: A:\FIX\MPM.4 Product name: "IBM Multimedia Presentation Manager/2" Standard Edition 3.01 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3005_ System Id: 1000 Component Id: 562274700 Archive is ON for this product. ________________________________________________________________________ Product name: "IBM Multimedia Presentation Manager/2" Standard Edition 1.01.2 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_6200_ System Id: B020 Component Id: 562137400 Archive is ON for this product. ________________________________________________________________________ FixPak Corrective Service levels and disk layouts 55 October 18, 2000 - Warp 3 FixPak XR_W043 Product name: "IBM Multimedia Presentation Manager/2" Standard Edition 3.02 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3006_ System Id: 1000 Component Id: 5639A5500 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- AMPMXMCD.DLL AMPMXMCD.DL_ 17 12/07/1998 09:43 544 B642596D AUDIOIF.DLL AUDIOIF.DL_ 17 12/07/1998 09:53 544 78F89813 AUDIOMCD.DLL AUDIOMCD.DL_ 17 12/07/1998 09:51 544 3C92541E AUDIOSH.DLL AUDIOSH.DL_ 17 12/07/1998 09:38 532 F7D87B94 AUTOPROC.DLL AUTOPROC.DL_ 17 12/07/1998 10:08 17936 DF47B61C AVIO.DLL AVIO.DL_ 17 12/07/1998 09:41 532 20C4245A CARDINFO.DLL CARDINFO.DL_ 17 12/07/1998 10:01 10768 C42FF25C CS4231.SYS CS4231.SY_ 17 10/08/1996 00:36 35319 ACF3AC36 DIVE.DLL DIVE.DL_ 16 12/07/1998 09:26 69840 933863D6 IOPRNLS.DLL IOPRNLS.DL_ 17 12/07/1998 09:25 3088 CEA8662B MDM.DLL MDM.DL_ 17 12/07/1998 09:28 26036 51D2A6A7 MEMSH.DLL MEMSH.DL_ 17 12/07/1998 09:32 14144 055A0ED3 MMPM.DLL MMPM.DL_ 17 12/07/1998 10:11 723448 CF6A2C1A MPGDC.DLL MPGDC.DL_ 17 12/07/1998 09:36 8912 62C9F5B5 MPGDCS.DLL MPGDCS.DL_ 17 12/07/1998 09:36 8768 7BCEC092 MPGIO.DLL MPGIO.DL_ 16 12/07/1998 09:37 59327 47A7FE5D MPGIOS.DLL MPGIOS.DL_ 16 12/07/1998 09:37 63067 508AAB7A MPGIOS.SCR MPGIOS.SC_ 17 10/08/1996 01:14 1053 A395762D R0STUB.SYS R0STUB.SY_ 17 12/07/1998 09:38 8398 C4F35C7F R565LUT8.LUT R565LUT8.LU_ 17 07/11/1996 18:10 263168 22446327 SMVSMRI.DLL SMVSMRI.DL_ 17 12/07/1998 10:07 5648 0C6F8457 SMVSPAGE.DLL SMVSPAGE.DL_ 16 12/07/1998 10:06 81440 7F50367E SSM.DLL SSM.DL_ 17 12/07/1998 09:25 1044 C69C1347 SSMDD.SYS SSMDD.SY_ 17 12/07/1998 09:25 33484 5BBD8079 SSMPEG.DLL SSMPEG.DL_ 17 12/07/1998 09:36 30160 793A067F SSMRES.DLL SSMRES.DL_ 17 12/07/1998 09:25 22364 F280FCD5 SVMC.DLL SVMC.DL_ 17 12/07/1998 09:40 532 130150BF SVSH.DLL SVSH.DL_ 17 12/07/1998 09:42 23044 9B2235A4 SWVR.EXE SWVR.EX_ 16 12/07/1998 10:09 152326 89AACD23 VIDVCI.DLL VIDVCI.DL_ 16 10/19/1998 10:46 34864 41C8C682 WAVEPROC.DLL WAVEPROC.DL_ 16 12/07/1998 10:06 532 3FA082C0 Y644LUT8.LUT Y644LUT8.LU_ 17 07/11/1996 18:10 66560 88251A02 YUV_LUT8.LUT YUV_LUT8.LU_ 17 07/11/1996 18:10 263168 8D29B8C1 FixPak Corrective Service levels and disk layouts 56 October 18, 2000 - Warp 3 FixPak XR_W043 ************************************************************************ Product location on CSD: A:\FIX\OS2.5 Product name: "IBM OS/2 Base Operating System" Standard Edition 3.01 Fixpak name: XR_W043_ (Country = Generic) Pre-requisite CSD Level: XR_3005_ System Id: 1000 Component Id: 562274700 Archive is ON for this product. ________________________________________________________________________ Default directories: ..\..\ ..\* ..\..\LANGUAGE\* Files contained in Fixpak for product: Filename Name on CSD Disk# Date Time Size Checksum ------------ ------------ ----- ---------- ----- ------- -------- FFST.DLL FFST.DL_ 18 09/05/1997 11:31 23583 8CDD7AE4 IBMDAPIN.EXE IBMDAPIN.EX_ 18 10/25/1996 12:49 66248 34C8A147 IBMDAPPM.EXE IBMDAPPM.EX_ 18 10/25/1996 12:49 51190 86BEC82A INST_DOS.EXE INST_DOS.EX_ 18 07/24/2000 21:35 36506 C87AD5F2 LIBAUX.DLL LIBAUX.DL_ 18 09/05/1997 11:30 113848 B55CBE3C LIBTK.DLL LIBTK.DL_ 18 09/05/1997 11:30 1101576 BDE3379B NAMEADD.EXE NAMEADD.EX_ 18 07/24/2000 19:11 20045 E3D22290 NAMECOPY.EXE NAMECOPY.EX_ 18 07/24/2000 19:11 20045 D93652E1 NAMECSSP.DLL NAMECSSP.DL_ 18 01/21/1998 16:36 61155 ED25B521 NAMEDEL.EXE NAMEDEL.EX_ 18 07/24/2000 19:11 20045 33567B12 NAMEDSP.DLL NAMEDSP.DL_ 17 07/24/2000 19:08 123411 AD39D529 NAMEDUMP.EXE NAMEDUMP.EX_ 18 07/24/2000 19:11 20045 C1652756 NAMEEXT.EXE NAMEEXT.EX_ 18 07/24/2000 19:11 20045 F1CE1668 NAMEFT.DLL NAMEFT.DL_ 18 01/21/1998 16:49 66306 05DC15F6 NAMEFW.DLL NAMEFW.DL_ 18 07/24/2000 19:08 72312 C6BE3ECE NAMEINFO.DLL NAMEINFO.DL_ 18 07/24/2000 19:11 47925 D5284CD2 NAMEINI.DLL NAMEINI.DL_ 18 07/24/2000 19:11 59011 B9CB85BE NAMEMOD.EXE NAMEMOD.EX_ 18 07/24/2000 19:11 20045 DF495A55 NAMEMOVE.EXE NAMEMOVE.EX_ 17 07/24/2000 19:11 20045 3F809E14 NAMEOSP.DLL NAMEOSP.DL_ 18 07/24/2000 19:10 52709 6737BF8B NAMEREXX.DLL NAMEREXX.DL_ 17 07/24/2000 19:11 156291 DD122EFA NAMEREXX.MSG NAMEREXX.MS_ 18 01/21/1998 16:47 4257 D09A395D OS2NS.EXE OS2NS.EX_ 18 07/24/2000 19:10 44964 167DBD57 PMDDEML.DLL PMDDEML.DL_ 18 07/24/2000 20:40 27210 2E45543A PMWINX.DLL PMWINX.DL_ 17 07/24/2000 21:35 520559 AE7B8ED7 RSRV.EXE RSRV.EX_ 18 07/24/2000 19:08 77955 6EF40617 FixPak Corrective Service levels and disk layouts 57 October 18, 2000 - Warp 3 FixPak XR_W043 12.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 32MB FixPak Archive/Backup for product with CSD level of XR_3005 Up to 33MB FixPak Archive/Backup for product with CSD level of XR_3006 Up to 3MB FixPak Archive/Backup for product with CSD level of XR_6200 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. Space Utilization 58 October 18, 2000 - Warp 3 FixPak XR_W043 13.0 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. Recovering FixPak ARCHIVE and BACKUP space 59 October 18, 2000 - Warp 3 FixPak XR_W043 14.0 RECOVERING FROM PROBLEMS See the file "README.TIP" for information on recovering from FixPak installation problems and resolving problems after the FixPak is installed. It is located on the first FixPak disk which is: FixPak XR_W043 Corrective Service Diskette 1 (CSF DISK 1). This file is setup to print at 60 lines per page. Recovering from problems 60