<        Installation instructions for Warp 4 FixPak XRJM015















        

        
        



        October 4, 2001

        This FixPak makes the products it services Year 2000 ready
        
        Build level 14.062
        
        This FixPak applies to:
        
        CSD Level:    XRJ4000    Warp 4
        Component ID: 5639A6100
        Version:      4.00
        Type:         0C
        
        CSD Level:    XRJ4010    WorkSpace On Demand Release 1
        Component ID: 5639A6100
        Version:      4.01
        Type:         0C
        
        CSD Level:    XRJ4010    WorkSpace On Demand Release 2
        Component ID: 5639A6120
        Version:      4.01
        Type:         0C
        
        Requires Corrective Service Facility release f.143 or later
        
        OS/2 Fix Distribution
        Personal System Products
        Austin, Tx
        
        
        (c) Copyright International Business Machines Corporation, 1981, 1998.
        All rights Reserved.


                      October 4, 2001 - Warp 4 FixPak XRJM015


        October 4, 2001 - Warp 4 FixPak XRJM015


















































   
                                                                    Page  ii


                    October 4, 2001 - Warp 4 FixPak XRJM015

   CONTENTS


     1.0 Terms and Conditions  . . . . . . . . . . . . . . . . . . . . . . 1

     2.0 Do not use your system  . . . . . . . . . . . . . . . . . . . . . 2

     3.0 Prerequisite service level for this FixPak  . . . . . . . . . . . 3

     4.0 Installation Notes  . . . . . . . . . . . . . . . . . . . . . . . 4
       4.0.1 Audio CD does not play  . . . . . . . . . . . . . . . . . . . 4
       4.0.2 Out of memory or System error SYS0008 - FP13+   . . . . . . . 4
       4.0.3 Warp 4 Revision number changed  . . . . . . . . . . . . . . . 4
       4.0.4 Changes you may see due to source convergence   . . . . . . . 5
       4.0.5 Security Applications Work Around   . . . . . . . . . . . . . 5
       4.0.6 Cannot install on WSoD Release 2  . . . . . . . . . . . . . . 5
       4.0.7 New PopUps During FixPak 12 Install   . . . . . . . . . . . . 5
       4.0.8 Device Drivers removed from Fixpak  . . . . . . . . . . . . . 6
       4.0.9 Can't install Warp 4  . . . . . . . . . . . . . . . . . . . . 6
       4.0.10 Please use Fixtool f.143 or later  . . . . . . . . . . . . . 6
       4.0.11 OS2DUMP split into two versions  . . . . . . . . . . . . . . 6
       4.0.12 TRAP in ES16881$ after FP10 applied  . . . . . . . . . . . . 7
       4.0.13 System Sounds not working after FixPak applied   . . . . . . 7
       4.0.14 Using Display Recovery Choices   . . . . . . . . . . . . . . 8
       4.0.15 Installation of Java 1.1.4   . . . . . . . . . . . . . . . . 9
       4.0.16 DSPRES.DLL included in this FixPak   . . . . . . . . . . . . 9
       4.0.17 No products found  . . . . . . . . . . . . . . . . . . . . . 9
       4.0.18 Previous installation interrupted   . . . . . . . . . . . . 10
       4.0.19 Unable to open Archive directory  . . . . . . . . . . . . . 10
       4.0.20 RC 932 doing CID install of Warp 4  . . . . . . . . . . . . 10
       4.0.21 Multimedia no longer selectable   . . . . . . . . . . . . . 12
       4.0.22 MMPARTS.DLL/USER.EXE popup during install   . . . . . . . . 12
       4.0.23 CSF0208 No products were found on the target ...    . . . . 12
       4.0.24 CSF0248 Archive path is shared between mismatched   . . . . 12
       4.0.25 CSF0249 Error opening or creating archive file.   . . . . . 12
       4.0.26 Printer installation process change   . . . . . . . . . . . 13
       4.0.27 Configuration Installation Distribution ( CID )   . . . . . 13

     5.0 Post Installation Notes  . . . . . . . . . . . . . . . . . . . . 14
       5.0.1 Enabling client updates to the WSOD 2.0 GRADD.MOD file   . . 14
       5.0.2 Print Screen SET parameter for APAR JR11837  . . . . . . . . 14
       5.0.3 New Message Box in fix for APAR JR12954  . . . . . . . . . . 15
       5.0.4 RAS file changes   . . . . . . . . . . . . . . . . . . . . . 15
       5.0.5 Setting IRQ9 processing in config.sys for VPIC.SYS   . . . . 16
       5.0.6 Windows printer drivers leave a zombie thread running  . . . 16
       5.0.7 APAR JR09494 (trap exiting WINOS2 with MWAVE audio)  . . . . 17
       5.0.8 SYS3170 installing Lotus SmartSuite 96   . . . . . . . . . . 17
       5.0.9 Intermittent hangs   . . . . . . . . . . . . . . . . . . . . 17

     6.0 New Function   . . . . . . . . . . . . . . . . . . . . . . . . . 18
     6.1 System Boot Message enhancements   . . . . . . . . . . . . . . . 18

   
                                                               Contents  iii


                    October 4, 2001 - Warp 4 FixPak XRJM015

     6.2 Intel's new SpeedStep  . . . . . . . . . . . . . . . . . . . . . 18
     6.3 New RAS Utilities added  . . . . . . . . . . . . . . . . . . . . 18
     6.4 Serviceability (RAS) Enhancements  . . . . . . . . . . . . . . . 18
     6.5 Querying file dates for files after Dec 31, 1999 in REXX   . . . 19
     6.6 Enhanced support for Workspace On-Demand   . . . . . . . . . . . 20
       6.6.1 PMLOGON user exits   . . . . . . . . . . . . . . . . . . . . 20
       6.6.2 Setup strings for public applications  . . . . . . . . . . . 22
       6.6.3 Command line options for TLOGOFF and TSHUTDWN  . . . . . . . 23
       6.6.4 PMLOGON No Progress Indicator option   . . . . . . . . . . . 23
       6.6.5 PMLOGON No System Modal Window option  . . . . . . . . . . . 24
     6.7 Euro Support   . . . . . . . . . . . . . . . . . . . . . . . . . 24
       6.7.1 Base OS/2 support  . . . . . . . . . . . . . . . . . . . . . 24
       6.7.2 Where Euro is not supported  . . . . . . . . . . . . . . . . 25
       6.7.3 Printing the Euro  . . . . . . . . . . . . . . . . . . . . . 26
     6.8 New Warp Registry Editor   . . . . . . . . . . . . . . . . . . . 26
     6.9 WorkSpace On Demand  . . . . . . . . . . . . . . . . . . . . . . 26
     6.10 IBM Open32  . . . . . . . . . . . . . . . . . . . . . . . . . . 26
     6.11 Graphics Adapter Device Drivers (GRADD)   . . . . . . . . . . . 27
     6.12 Joliet-2 support in CDFS.IFS  . . . . . . . . . . . . . . . . . 27
     6.13 New (improved) CHKDSK   . . . . . . . . . . . . . . . . . . . . 27
       6.13.1 Using the new CHKDSK  . . . . . . . . . . . . . . . . . . . 27
       6.13.2 CHKDSK log formatter  . . . . . . . . . . . . . . . . . . . 29
     6.14 Automated Trap Screen Logging   . . . . . . . . . . . . . . . . 30
       6.14.1 SUPPRESSPOPUPS  . . . . . . . . . . . . . . . . . . . . . . 30
       6.14.2 TRAPLOG   . . . . . . . . . . . . . . . . . . . . . . . . . 30
       6.14.3 TRAPDUMP  . . . . . . . . . . . . . . . . . . . . . . . . . 31
       6.14.4 SYSDUMP   . . . . . . . . . . . . . . . . . . . . . . . . . 31
     6.15 REXX New Fuction  . . . . . . . . . . . . . . . . . . . . . . . 32
     6.16 Other README files  . . . . . . . . . . . . . . . . . . . . . . 32

     7.0 Corrective Service Facility  . . . . . . . . . . . . . . . . . . 33
       7.0.1 Required CSF level   . . . . . . . . . . . . . . . . . . . . 33
       7.0.2 Where you can find CSF code  . . . . . . . . . . . . . . . . 33
       7.0.3 Creating FixPak diskettes  . . . . . . . . . . . . . . . . . 34
     7.1 Residual FixPak files from OS/2 2.11 or Warp 3   . . . . . . . . 34
     7.2 Read-Only files  . . . . . . . . . . . . . . . . . . . . . . . . 35
     7.3 SYSLEVEL file locations  . . . . . . . . . . . . . . . . . . . . 35
     7.4 Relocated OS/2 file support  . . . . . . . . . . . . . . . . . . 36

     8.0 Installation Process   . . . . . . . . . . . . . . . . . . . . . 38
     8.1 Before installation  . . . . . . . . . . . . . . . . . . . . . . 38
     8.2 Method 1: Install from booted OS/2 partition.    . . . . . . . . 38
     8.3 Method 2: Install from alternate bootable media  . . . . . . . . 39
     8.4 Additional Corrective Service Facility information   . . . . . . 40

     9.0 CSD level of SYSLEVEL.OS2  . . . . . . . . . . . . . . . . . . . 41
       9.0.1 New SYSLEVEL.FPK   . . . . . . . . . . . . . . . . . . . . . 42

     10.0 FixPak Corrective Service levels and disk layouts   . . . . . . 43

     11.0 Space Utilization   . . . . . . . . . . . . . . . . . . . . . . 66

   
                                                                Contents  iv


                    October 4, 2001 - Warp 4 FixPak XRJM015

       11.0.1 Recovering FixPak ARCHIVE and BACKUP space  . . . . . . . . 66
       11.0.2 TRADEMARKS  . . . . . . . . . . . . . . . . . . . . . . . . 67


















































   
                                                                 Contents  v


                    October 4, 2001 - Warp 4 FixPak XRJM015

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

   Downloading the Service Fixes included in FixPak XRJM015 for OS/2 Warp 4
   indicates your acceptance of the following terms and conditions:

   1. You must be, and agree that you are, a current licensee of OS/2 Warp
      4.
   2. You may make copies of the OS/2 Service Fixes equal to the number of
      licensed copies of OS/2 Warp 4 you possess.
   3. You may only use the OS/2 Warp 4 Service Fixes included with FixPak
      XRJM015 for maintenance purposes.
   4. All other terms and conditions of your OS/2 Warp 4 license agreements
      apply to the Service Fixes; however, this does not extend any warranty
      and/or services, including but not limited to the "Initial
      Installation" period, outlined in such agreements.



































   
                                                     Terms and Conditions  1


                    October 4, 2001 - Warp 4 FixPak XRJM015

   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 4, 2001 - Warp 4 FixPak XRJM015

   3.0 PREREQUISITE SERVICE LEVEL FOR THIS FIXPAK

   You must be at the correct prerequisite service level in order to apply
   this FixPak. If you are not at the prerequisite level you will receive a
   "No products to service" error message when you attempt to apply this
   FixPak.

   The prerequisite levels needed are:

   Warp 4 and Work Space on Demand release 1    FX00505
   Work Space on Demand release 2               FX00506









































   
                               Prerequisite service level for this FixPak  3


                    October 4, 2001 - Warp 4 FixPak XRJM015

   4.0 INSTALLATION NOTES



   4.0.1 AUDIO CD DOES NOT PLAY

   On some systems, after installing Warp 4 FixPak XR_M014, your audio CD
   may no longer play. The Multimedia CD applet will display a message with
   a RC of 5060. To correct this problem, perform the following steps :

   1. Right mouse click on your desktop.
   2. Left mouse click on System setup.
   3. Double left mouse click on the Multimedia Setup icon.
   4. Left mouse click on the Compact Disc tab.
   5. Left mouse click on "+" sign in the right corner.
   6. Change the Drive Letter to the Drive Letter where your CD is located.
   7. Save change.

    Your CD should now be able to play CDs.


   4.0.2 OUT OF MEMORY OR SYSTEM ERROR SYS0008 - FP13+

   Customers who have had an "Out of memory" or SYS0008 problems on systems
   using Java should add the following line to the CONFIG.SYS file:

   þ  SET JAVA_HIGH_MEMORY=1

   This will allow Java to move it't buffers to a lesser-used region of
   memory and may alleviate some memory constraints. There are no known
   unwanted side-effects to doing this.


   4.0.3 WARP 4 REVISION NUMBER CHANGED

   As of FixPak XR_M013 we've converged the souce lines with Warp Server for
   e-business. This is what causes the initial boot screen to display as
   14.040_W4 and the internal version to be reported as 4.50 as well. Some
   program might interpret this as you not running the correct version of
   OS/2.

   If this occurs, please use OS2VER to set the proper version number to be
   reported to the program.

   To do so, you must edit a SYSTEM HIDDEN READONLY file, OS2VER, in the
   root of the boot drive. Then add a line in the format of 40=executable
   file name and save the file and reset the attributes.

   Note: To unhide the file OS2VER, perform the following steps:

   1. Open an OS/2 window.

   
                                                       Installation Notes  4


                    October 4, 2001 - Warp 4 FixPak XRJM015

   2. Change to drive letter where OS/2 is installed.
   3. Enter "cd\" to get to the root directory.
   4. Enter OS/2 command "attrib -s -h -r os2ver" to unhide OS2VER.
   5. Edit OS2VER to add line above ; save
   6. Enter OS/2 command "attrib +r +s +h os2ver" to hide OS2VER.
   7. Reboot system.



   4.0.4 CHANGES YOU MAY SEE DUE TO SOURCE CONVERGENCE

   Due to the Source Line convergence for OS/2 Warp 4 with the Warp Server
   for e-Business source code, you might see references to Warp Server for
   e-business being reported by some device drivers or executables. This is
   not a problem and may be ignored.


   4.0.5 SECURITY APPLICATIONS WORK AROUND

   Users of some security-related ISS (security) packages such as Utimaco's
   SafeGuard Professional, will have to add a new line to config.sys:

   þ  FAKEISS=YES

   This works around a limitiation of some legacy ISS drivers. This is not a
   problem for the Tivoli ISS driver.


   4.0.6 CANNOT INSTALL ON WSOD RELEASE 2

   If you get a message stating "No products found to service" when trying
   to install on WorkSpace on-Demand Release 2, you may have a corrupted
   syslevel.os2 file.  Copy the syslevel.os2 file from the installation CD
   or from a working WSoD R2 system and retry the installation.  Be sure to
   use Fixtool 1.42 to service your WSoD R2 system.  This will prevent the
   syslevel.os2 file corruption.  Previous versions of the Fixtool fail to
   correct a problem with the previous CSD level field in the syslevel.os2
   file.


   4.0.7 NEW POPUPS DURING FIXPAK 12 INSTALL

   If you get a popup for module VIOTBL.ISO, VIOTBL.DCP, BDIME.DLL, or
   COUNTRY.SYS during installation of this FixPak, reply "OK" to replace
   these modules with the ones in this FixPak.







   
                                                       Installation Notes  5


                    October 4, 2001 - Warp 4 FixPak XRJM015

   4.0.8 DEVICE DRIVERS REMOVED FROM FIXPAK

    Beginning with Warp 4 FixPak XR_M011 and Warp 3 FixPak 41, most OS/2
    Device Drivers have been moved to a separate Device Driver FixPak. The
   first
    Device Driver FixPak, XR_D001, is now available where this FixPak is
    available.


   4.0.9 CAN'T INSTALL WARP 4

   If you can't get Warp 4 installed, check the OS/2 Device Driver Pak
   Online at:

   http://service.software.ibm.com/os2ddpak/readme.htm#disk1


   for the latest available device drivers to update your Installation disks
   with.


   4.0.10 PLEASE USE FIXTOOL F.143 OR LATER

   Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
   Corrective Service Facility f.143 or later.  It has fixes for problems
   found in previous CSF builds as well as a fix to support RIPL servers
   where there may be in excess of 250 SYSLEVEL files. It also handles the
   type 1 (All FixPaks prior to 10 and 40) and type 2 (FixPaks 10 and 40 and
   later) FixPaks.

   If you try to use a CSF level prior to f.143 you will get a "CSF0208 No
   products were found on the target system to service" message.


   4.0.11 OS2DUMP SPLIT INTO TWO VERSIONS

   OS2Dump has been split into two versions. If you are installing this
   fixpak on PS/2 model 9595 machines, use the version located on the last
   fixpak diskette.  Also, if you are running older hardware (486s or early
   Pentiums), you may wish to use the OS2Dump located on the last fixpak
   diskette.

   We have encountered some problems with early implementations of the PCI
   Bus BIOS extensions (INT 1A) on certain processors and BIOS levels. We
   are not sure how many different machines and BIOSes are affected. We do
   know many of the PS/2 model 9595s have the problem. The end result of
   this is that the version of OS2Dump which supports PCI Bus machines does
   not work on some older hardware.  In order to continue to support the
   full range of hardware that OS/2 runs on, we have divided OS2Dump into a
   PCI version and an non-PCI version. If you are running fairly recent
   hardware, the PCI version of OS2Dump will work on your machine whether or

   
                                                       Installation Notes  6


                    October 4, 2001 - Warp 4 FixPak XRJM015

   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.



   4.0.12 TRAP IN ES16881$ AFTER FP10 APPLIED

   We do not ship any of the ESS sound card drivers in this Fixpak.  To
   corrrect the problem, get the latest ESS device driver for your card from
   the OS/2 Device Driver Pak online at

   http://service.software.ibm.com/os2ddpak/html/multimed/esstechn


   Do this before you install the FixPak.


   4.0.13 SYSTEM SOUNDS NOT WORKING AFTER FIXPAK APPLIED

   If, after applying a FixPak, your System Sounds no longer work or you get
   an error message stating "Error in closing CD device:  Invalid device ID
   given" when you close the CD Player, it may be caused by the FixPak
   replacing the following files in your MMOS2 directory tree:

      \MMOS2\DLL\DIVE.DLL
      \MMOS2\DLL\MMPM.DLL
      \MMOS2\DLL\MPGIO.DLL
      \MMOS2\SSMDD.SYS
      \MMOS2\DLL\SVMC.DLL
      \MMOS2\DLL\SVSH.DLL


   
                                                       Installation Notes  7


                    October 4, 2001 - Warp 4 FixPak XRJM015

   To recover, restore these files from your FixPak Backup or Archive
   directory.

   1. Boot from another partition, your Installation or Utility disks.
   2. Rename the existing files in the MMOS2 directory tree so they will not
      be overlayed when you restore the older files.
   3. Change to the FixPak Backup directory if there is one. If not then
      change to the FixPak Archive directory.

      Note: The names may not be Backup or Archive. They will be whatever
      you called them when you applied a FixPak.
   4. For each of the above files, enter

      UNPACK source target

      Where "source" is the filename.ext of the file in the Backup or Archive
                     directory, like DIVE.DL_ or SSMDD.SY_
            "target" is the fully qualified path of where to place the file,
                     like C:\MMOS2\DLL or C:\MMOS2


   5. Repeat for each of the above files
   6. Reboot your system. This resolved the problem on a TP760 and may also
      resolve the problem on other hardware.



   4.0.14 USING DISPLAY RECOVERY CHOICES

   If you have the "Display Recovery Choices at each system startup"
   function active on your system, you need to disable it before you apply a
   FixPak if

   þ  The system is running
   þ  The boot partition will be serviced.

   The problem with using this function is that the Corrective Service
   Facility (CSF) updates the current CONFIG.SYS with entries to run the
   Locked File Device Driver (LFDD) the next time you boot the system. This
   is done to replace files that are currently in use (locked) by the
   system.

   The Recovery choices function replaces the current CONFIG.SYS with the
   one that is associated with the recovery choice you select, wiping out
   the LFDD entries. This means the LFDD does not run at boot time and the
   deferred files will not get updated, therefore the FixPak does not get
   completely applied.

   Note: It is not necessary to disable this function if you install a
   FixPak by booting from the CSF disks or from another OS/2 partition.


   
                                                       Installation Notes  8


                    October 4, 2001 - Warp 4 FixPak XRJM015

   4.0.15 INSTALLATION OF JAVA 1.1.4

   Installation of Java 1.1.4 on top of this FixPak will down-level portions
   of the ULS support. If this occurs, Euro currency support will not work
   correctly.  To recover, re-install this FixPak. This will allow both Java
   1.1.4 and Euro support to work correctly.


   4.0.16 DSPRES.DLL INCLUDED IN THIS FIXPAK

   DSPRES.DLL has been added to this FixPak for support for Euro character
   display. This file can sometimes be overwritten by video device driver
   installation. If this occurs, an updated version is located in
   \OS2\INSTALL\VGA. This updated file can be copied into the \OS2\DLL
   directory.


   4.0.17 NO PRODUCTS FOUND

   If you see a "No products were found on the target system to service"
   message while applying this FixPak, there is probably a mismatch between
   the data in \OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this
   FixPak.

   Compare the data for the OS/2 Base Operating System from the SYSLEVEL
   command output with the same values listed at the end of this document in
   the "FixPak Corrective Service levels and disk layouts" section. They
   must be identical.

   If these values are correct, check for the following files on any OS/2
   boot drive in the \OS2\INSTALL directory.

      LOGF0000.OS2
      LOGSTART.OS2
      LOGARCH.OS2


   Check for the following files in your MMOS2\INSTALL directory.

      LOGF0000.MPM
      LOGSTART.MPM
      LOGARCH.MPM


   Also check for the following file:

      C:\CSF_SEL.000


   If these files exist, rename them and try the FixPak installation again.
   Delete the renamed files after the FixPak has been applied.

   
                                                       Installation Notes  9


                    October 4, 2001 - Warp 4 FixPak XRJM015

   4.0.18 PREVIOUS INSTALLATION INTERRUPTED

   If you get a message that the previous installation of a FixPak was
   interrupted (whether true or not), check for the following files and
   directory on all drives:

     Files:
        FIXSTART
        IBMCSFLK.LST
        IBMCSFLK.CSF
        CSF_*

     Directory:
        IBMCSFLK


   If any exist, rename them and try the FixPak installation again.  Delete
   the renamed files after the FixPak has been applied.


   4.0.19 UNABLE TO OPEN ARCHIVE DIRECTORY

   If you get a message about problems with the Archive directory (for
   example, cannot find or unable to open), then the most probable cause is
   that you applied a previous FixPak and have since deleted the FixPak
   ARCHIVE or BACKUP directory.

   To recover from this, follow the "No files to service" and "Previous
   installation interrupted" steps listed above.


   4.0.20 RC 932 DOING CID INSTALL OF WARP 4

   If you get a RC (Return Code) 932 while doing a CID install of Warp 4 and
   you are using RSPINST.EXE from FixPak 3 or later, you will need to do the
   following.

   1. Create a temporary work directory somewhere on your harddrive.

         assume it's c:\tempwork


   2. Locate the section called "FixPak Corrective Service levels and disk
      layouts".
   3. Locate CHKDSK.SYS, CHKDSK32.DLL, CHKDSK32.EXE  and UHPFS.DLL and
      record what disks they are found on.

      Note: For FixPak 3, they are on disks 12, 8, 12 and 9 respectively.
      This will change for later FixPaks.



   
                                                      Installation Notes  10


                    October 4, 2001 - Warp 4 FixPak XRJM015

   4. Place FixPak disk 12 in A: and enter

         unpack a:\fix\os2.1\chkdsk.sy_ c:\tempwork


   5. Place FixPak disk  8 in A: and enter

         unpack a:\fix\os2.1\chkdsk32.dl_ c:\tempwork


   6. Place FixPak disk 12 in A: and enter

         unpack a:\fix\os2.1\chkdsk32.ex_ c:\tempwork


   7. Place FixPak disk  9 in A: and enter

         unpack a:\fix\os2.1\uhpfs.dl_ c:\tempwork


   8. Make backup copies of CHKDSK.SYS, CHKDSK32.DLL and UHPFS.DLL from the
      DISK_3 directory of your CID tree.
   9. Copy CHKDSK.SYS from c:\tempwork to the DISK_3 directory of your CID
      tree
   10.Copy CHKDSK32.DLL from c:\tempwork to the DISK_3 directory of your CID
      tree
   11.Copy UHPFS.DLL from c:\tempwork to the DISK_3 directory of your CID
      tree
   12.Make a backup copy of the BUNDLE file on DISK_0
   13.Copy DISK_0\BUNDLE c:\tempwork
   14.Copy PACK2.EXE to c:\tempwork. If you don't have this file you can get
      it using your Web browser from

         ftp://ps.software.ibm.com/ps/products/os2/fixes/v4warp


   15.PACK2 CHKDSK32.EXE bundle /H:\OS2\CHKDSK32.EXE /A

      Note: This adds CHKDSK32.EXE to the bundle file.  Enter "unpack bundle
      /show" to verify it's really there.

   16.Copy the updated BUNDLE back to the DISK_0 directory
   17.Delete the c:\tempwork directory and files.
   18.Copy the files SCSIADDS and PRESCHEK from DISK_4 to DISK_5.
   19.Do the CID install







   
                                                      Installation Notes  11


                    October 4, 2001 - Warp 4 FixPak XRJM015

   4.0.21 MULTIMEDIA NO LONGER SELECTABLE

   IBM Multimedia Presentation Manager/2 (MPM) is now fully integrated into
   the base OS/2. As part of this change, the \MMOS2\INSTALL\SYSLEVEL.MPM
   file has been deleted. This means you will no longer see it as a
   selectable entry in the Serviceable Products window when using the
   A:SERVICE method of installation.


   4.0.22 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL

   If you get a popup about MMPARTS.DLL or USER.EXE during install, reply
   "OK" to replace it.


   4.0.23 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET ...

   This means no SYSLEVEL files was found that had a CSD Level, COMPID,
   Version and Type that matched any of the SYSLEVEL files supported by this
   FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2
   in the OS2/INSTALL directory on your boot drive. Compare this data with
   the data contained in the README.1ST file on FixPak disk 1.

   To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2
   and copy SYSLEVEL.OS2 from your Warp 4 installation DISK 1.


   4.0.24 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED

   1. The Archive path you specified (or was previously specified) contains
      files from a different release of OS/2. You need to specify a
      different Archive path.
   2. You have a bad SYSLEVEL.OS2 or SYSLEVEL.MPM file. Both must have the
      same Current CSD Level, Version, Type and Component ID if you point
      both Fixpak Archives to the same location.

      Check \OS2\INSTALL\SYSLEVEL.OS2 and \MMOS2\INSTALL\SYSLEVEL.MPM. If
      either is wrong, place the last FixPak disk in A: and run FIXSYSL.CMD
      to correct SYSLEVEL.OS2 problems or SYSZMPM.CMD to fix SYSLEVEL.MPM
      problems.



   4.0.25 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.

   Typically this means the FixPak Archive directory has been deleted but
   the files that point to it still exist. You need to delete the
   LOGF000.OS2 and LOGSTART.OS2 files from your OS2/INSTALL directory.
   LOGSTART.OS2 has the R/O attribute set and it needs to be reset before
   the file can be deleted.  There may also be a LOGARCH.OS2 file that needs
   to be deleted.

   
                                                      Installation Notes  12


                    October 4, 2001 - Warp 4 FixPak XRJM015

   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.


   4.0.26 PRINTER INSTALLATION PROCESS CHANGE

   If you install a new printer by clicking MB2 on the Printer icon in the
   templates folder then clicking on Install, the printer object will now be
   created in the Printer folder, not on the Desktop.


   4.0.27 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )

   Read the README.CID on Disk # 1 for an example of how to set up a
   response file to do a CID install.




































   
                                                      Installation Notes  13


                    October 4, 2001 - Warp 4 FixPak XRJM015

   5.0 POST INSTALLATION NOTES



   5.0.1 ENABLING CLIENT UPDATES TO THE WSOD 2.0 GRADD.MOD FILE

   IBM WorkSpace On-Demand 2.0 now supports all resolutions and color depths
   for GRADD model video drivers (this includes the GENGRADD and IBM300G2
   machine classes).  To enable this support, modify the client's FIT file
   to enable the client to rewrite the GR ADD.MOD file in the client's OS2
   directory.

   For existing clients, edit the client's FIT file
   \IBMLAN\RPL\FITS\<client_name>.  FIT, where <client_name> represents the
   NetBIOS name of the client machine.

   Change the following entry:

   þ  Z:\OS2\GRADD.MOD   \\<RPLSERVR>\WRKFILES\<client_name>\OS2

   þ  to

   þ  Z:\OS2\GRADD.MOD   \\<RPLSERVR>\WRKFILES\<client_name>\OS2\GRADD.MOD

   where <RPLSERVR> represents the NetBIOS name of the RPL server, and
   <client_name> represents the NetBIOS name of the client machine.

   To enable this capability for all subsequently created clients, perform a
   similiar modification on the machine class template FIT file, as follows:
   \IBMLAN\RPL\MACHINES\BB20.<cc>\<machine_class>.MC\<machine_class>.FIT,
   where <cc> represents the country code, and <machine_class> represents
   the name of the machine class.  Update both the GENGRADD and IBM300G2
   machine class FIT files as follows:

   Change the following entry:

   þ  Z:\OS2\GRADD.MOD   \\<RPLSERVR>\WRKFILES\DEFAULT\OS2

   þ  to

   þ  Z:\OS2\GRADD.MOD   \\<RPLSERVR>\WRKFILES\DEFAULT\OS2\GRADD.MOD

   where <RPLSERVR> represents the NetBIOS name of the RPL server.


   5.0.2 PRINT SCREEN SET PARAMETER FOR APAR JR11837

   Add the following environment varible line to CONFIG.SYS to print active
   window during Print Screen operation:



   
                                                 Post Installation Notes  14


                    October 4, 2001 - Warp 4 FixPak XRJM015

   SET PM_PRINTSCREEN_ACTIVE_WINDOW=ON

   The WINDOW with focus will print when a Print Screen operation is
   initiated.

   For the default Print Screen operatin, perform either of these steps:

   Remove line "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=ON" from CONFIG.SYS or
   change the line to read:

   "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=OFF"

   Note:  System must be re-booted after any CONFIG.SYS changes.


   5.0.3 NEW MESSAGE BOX IN FIX FOR APAR JR12954

   With FixPak 10 installed, if you tried to create Utility Disks and
   selected "Use files from hard disk if they exist" you would get a SYS3175
   trap. This was caused by a much larger AIC7870.ADD file causing the
   diskette to fill up before all files were copied to it.

   With FixPak 11 you will now get a "Diskette Full" message box that says
   "Remove unwanted files and press OK.".

   This means you should delete from the diskette in your A: drive, files
   that are not needed on your system.  Good candidates for deletion are the
   CD-ROM drivers and harddisk drivers you do not need. You can check
   CONFIG.SYS in the root of your boot drive to see if a file is used. If
   not it can be deleted.

   When you delete a file, also delete or REM out that line in CONFIG.SYS on
   the diskette in A:.


   5.0.4 RAS FILE CHANGES

   Beginning with FixPak 11, the following files are being added to the
   \OS2\SYSTEM directory. If they also exist in the \OS2 directory you can
   delete them as they are no longer needed there.

   þ  DTRACE.EXE
   þ  TRACEFMT.EXE
   þ  TRSPOOL.EXE

   If you do not delete them from the \OS2 directory, they will be serviced
   the same as the ones in the \OS2\SYSTEM directory to keep them current.

   Also, the following files in the \OS2\SYSTEM\RAS directory can be deleted
   as they have been superseded as shown:


   
                                                 Post Installation Notes  15


                    October 4, 2001 - Warp 4 FixPak XRJM015

   File           Superseded by
   MDTRACE.doc    DTRACE.DOC
   MTRSPOOL.DOC   TRSPOOL.DOC



   5.0.5 SETTING IRQ9 PROCESSING IN CONFIG.SYS FOR VPIC.SYS

   Some applications like PCAS (and some terminal emulators) have problems
   sharing IRQ9 in a VDM.  Since the DOS Virtual Device drivers are not
   loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added
   starting with Warp 3 FixPak 38 and Warp 4 FixPak 8.

   To prevent sharing of IRQ9 in a VDM, add the following statement in
   config.sys:

      device=x:\os2\mdos\vpicparm.sys irq9_off
      (x: is your OS/2 boot drive)


   Next, in the settings for the program that requires exclusive access to
   IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON.

   When you next boot your system, VDMs will not share IRQ9.


   5.0.6 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING

   A problem occurs with some Windows printer drivers where a zombie thread
   is left running after the program that loaded it is exited.

   This does not occur when the program is run from a Seamless instance of
   PROGMAN or from a Full Screen session because when these are exited the
   whole WINOS2 Subsystem is exited.

   This problem has been reported for the Adobe and Hewlett Packard Windows
   printer drivers. To correct this problem for people running with these
   drivers ONLY who have experienced symptoms such as:

   þ  exiting a program running seamlessly after printing or
   þ  setting up a printer and seeing the icon not being unhatched and/or
   þ  not being able to start another copy of the program

   Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot*
   section:

   þ  backgroundtasks=run_enum.exe,hpfbkg02.exe

   then restart WINOS2.

   Note: There may be other drivers that have the same problem.  If you

   
                                                 Post Installation Notes  16


                    October 4, 2001 - Warp 4 FixPak XRJM015

   experiences a similar problem with other drivers, please report it so the
   correct SYSTEM.INI entry can be determined.



   5.0.7 APAR JR09494 (TRAP EXITING WINOS2 WITH MWAVE AUDIO)

   The fix for APAR JR09434 (trap exiting winos2 with MWAVE audio) requires
   a new MWAVEVDD.SYS dated 11/96 or later.  This file is available from the
   IBM PC Company web site at http://www.pc.ibm.com.


   5.0.8 SYS3170 INSTALLING LOTUS SMARTSUITE 96

   A problem was discovered when attempting to install Lotus SmartSuite 96
   with a early version of the Matrox video driver.  A SYS3170 occurs after
   pressing the button to start copying the files to the hard disk.

   The problem does not occur with the current Matrox driver available on
   the Web at

      http://www.matrox.com/mgaweb/drivers/ftp_os2.htm


   A work around that does not involve downloading files from the web, is to
   switch your display driver to VGA during the install and after it has
   completed, restore the Matrox driver.


   5.0.9 INTERMITTENT HANGS

   If you experience intermittent hangs of your system, check your LIBPATH
   statement in CONFIG.SYS to see if SOM.DLL is in a directory other than,
   and ahead of, OS2\DLL.

   If yes, either change the LIBPATH statement to move the directory after
   OS2\DLL or try renaming SOM.DLL to SOM.DLO.

   One known cause of this is VisualAge C++. It has a version of SOM.DLL in
   its DLL library and the installation puts this library ahead of OS2\DLL
   in the LIBPATH statement.











   
                                                 Post Installation Notes  17


                    October 4, 2001 - Warp 4 FixPak XRJM015

   6.0 NEW FUNCTION



   6.1 SYSTEM BOOT MESSAGE ENHANCEMENTS

   An enhancement has been made to the functions available at system boot
   time when the "white blob OS/2" appears in the upper left corner of the
   screen.

   þ  Alt+F3 - is the equivalent of Alt+F1 plus Alt+F2

   This will always display the device driver load information irregardless
   of what action you specify on the menu.

   Alt+F2 is automatically enabled if you create a file named ALTF2ON.$$$ in
   the root or OS2\BOOT directory of the boot drive. The content of this
   file does not matter.


   6.2 INTEL'S NEW SPEEDSTEP

   The support for Intel's new SpeedStep (a.k.a. Geyserville) included in
   this FixPak.


   6.3 NEW RAS UTILITIES ADDED

   Two new RAS utilities are included for Pak 13: PSFILES.EXE and
   PSSEMS.EXE.

   PSFILES.EXE can dump out information about open files on the system.  By
   default, it dumps out the information for all processes. Alternately,
   "PSFILES xxx" will dump out information for PID xxx (xxx is a hex number,
   e.g. from PSTAT).

   PSSEMS.EXE can dump out information about open 32 bit semaphores on the
   system.  By default it prints out all the shared (i.e. system-wide)
   semaphores.  Usage is:  pssems [/n] [hex_pid | /a] ; where /n suppresses
   shared semaphores and /a prints pruivate sems for all system processes.

   Note: These RAS Utilities are added to the OS2 directory on your system.


   6.4 SERVICEABILITY (RAS) ENHANCEMENTS

   With FixPak 35 for Warp 3.0 and FixPak 10 for Warp 4.0 major enhancements
   were provided to the system diagnostic tools (RAS Enhancements).  They
   provide major functional enhancements to the System Trace and Process
   Dump facilities.  Full details of these enhancements can be found in the
   README.DBG file that will be found in the \OS2\INSTALL directory after

   
                                                            New Function  18


                    October 4, 2001 - Warp 4 FixPak XRJM015

   this FixPak is installed.

   Other associated documentation may be found in:

   þ  OS2\SYSTEM\RAS\TRACE.DOC
   þ  OS2\SYSTEM\RAS\DTRACE.DOC
   þ  OS2\SYSTEM\RAS\PROCDUMP.DOC
   þ  OS2\SYSTEM\RAS\TRSPOOL.DOC

   Always refer to README.DBG for details of any RAS enhancements delivered
   with a FixPak.


   6.5 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX

   Existing REXX functions return file dates with a two digit year only.
   While these functions are Year 2000 tolerant (i.e. the results will be
   correct for files dated after Dec 31, 1999) they require some additional
   logic in existing programs to handle the returned date correctly when
   they are compared with other file dates.

   Since the output format of the existing functions could not be changed
   for compatibility reasons, new options have been added to the REXX
   interpreter to return file dates with the year formatted with 4 digits.
   Two functions have been extended to support the new format. The syntax to
   retrieve the file date in 4 digit format is as follows:

      /********************************************/
      /* Use STREAM QUERY TIMESTAMP to query file */
      /* date in 4 digit format                   */
      /********************************************/
      Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP")

      /***********************************************/
      /* Use option "L" with SysFileTree to return a */
      /* list of files with long date format         */
      /***********************************************/
      Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
      Call SysLoadFuncs
      Call SysFileTree "C:\*.*", "Files", "L"
      Do i = 1 To Files.0
         Say Files.i
      End


   These extensions are available in both classic REXX and Object REXX on
   OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these
   extensions in your program you have to make sure that you are running the
   right level of REXX



   
                                                            New Function  19


                    October 4, 2001 - Warp 4 FixPak XRJM015

   6.6 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND



   6.6.1 PMLOGON USER EXITS

   This function, provided by PMLOGON, allows system integrators to have
   REXX code executed at specific points during the startup and logon
   sequence.  By default, user exits are disabled in PMLOGON.EXE.  To enable
   user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the
   CONFIG.SYS file must be added.  The /URX parameter specifies the location
   and name of the user exit command file:

      Execution Parameter            User Exit command file that will be
                                                  executed
      -------------------            -----------------------------------

      /URX                           \OS2\PMLOGURX.CMD

      /URX:<filename>.CMD            <filename>.CMD located in one of the
                                     locations specified by the PATH
                                     environment variable

      /URX:d:\<path>\<filename>.CMD  d:\<path>\<filename>.CMD


   The same command file is called for ALL user exits.  The FIRST parameter
   supplied to the command file indicates the exit that it is being called
   for. The REXX command file is called for all these exits, even if it does
   not need to process all of the exits.  The REXX command file must be able
   to return error free if it receives an exit number that it does not need
   to handle.  The following user exits are available:




















   
                                                            New Function  20


                    October 4, 2001 - Warp 4 FixPak XRJM015

       First Parameter    Exit Description
       ---------------    ----------------

       0                  Executes ONCE per boot, before the requester
                          is started.  There is no user logged on at this
                          time.  This exit may return a string that is
                          processed exactly as the following execution
                          parameters set in RUNWORKPLACE of CONFIG.SYS:

                          /U: /UF: /P: /PF: /D: /DF: /PW  /AUTO  /NONFLE

                          It is processed immediately after the execution
                          parameters.  See Note 2 below on /AUTO processing.

       1                  Executes ONCE per logon, after the requester
                          is started, but before logon occurs.  There is no
                          user logged on at this time.  This exit may return
                          a string that is processed exactly as the
                          following execution parameters set in RUNWORKPLACE
                          of CONFIG.SYS:

                          /U: /UF: /P: /PF: /D: /DF: /PW  /AUTO  /NONFLE

                          It is processed immediately before logon.  See
                          Note 2 below on /AUTO processing.

       2                  Executes ONCE per logon, after the requester is
                          started and after logon occurs.  There is a user
                          logged on at this time, but the Desktop has not
                          been started and the objects are not displayed.
                          No returns are processed.

       3                  Executes ONCE per logon, after the Desktop has
                          been started and the objects are created but not
                          currently displayed, but immediately before
                          control is passed to the Desktop.  The icons are
                          fixed at this point.  There is a user logged on
                          at this time.  No returns are processed.

        4                 Executes immediately after a failed logon.  The
                          second parameter passed to the exit contains the
                          return code from the logon API.  This exit may
                          return a string that is processed exactly as the
                          execution parameters set in RUNWORKPLACE of
                          CONFIG.SYS for the following parameters only:

                          /U: /UF: /P: /PF: /D: /DF:  /PW  /AUTO  /NONFLE

                          This exit is processed immediately and logon is
                          retried with the new parameters regardless of
                          the /AUTO switch.  See Note 2 below on /AUTO

   
                                                            New Function  21


                    October 4, 2001 - Warp 4 FixPak XRJM015

                          processing.  If no string is returned, then the
                          normal logon failure or password expired message
                          box is displayed.

      Note 1:  The session environment for the REXX command file is that
               of PMLOGON.EXE and, therefore, does not contain any input or
               output facility. For example, "PULL" from the keyboard and
               "SAY" to the console do not work.

      Note 2:  The /AUTO parameter is validated at every step (for example,
               after command line processing, after exit 0 returns, and
               after exit 1 returns).  It is turned off if insufficient
               information (such as no user ID) is provided at that stage
               for an automatic logon.  If the user ID is supplied by the
               exit, that exit must also provide the /AUTO parameter in
               order for an auto logon to work.




   6.6.2 SETUP STRINGS FOR PUBLIC APPLICATIONS

   The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific
   Workplace Shell WPProgram setup strings that are provided when creating
   public applications on the WorkSpace On-Demand Desktop.  In particular,
   the ICONPOS setup string can be defined for a public application so that
   the Administrator can identify where application icons are placed on the
   WorkSpace On-Demand Desktop.

   When a WorkSpace On-Demand Administrator creates a public application, a
   new environment variable must be added to the application to provide a
   setup string.  The parameter name is NCC_SETUP_POST and the parameter
   value can consist of any of the setup strings specified below.  Each
   setup string consists of a KEYNAME, followed immediately by an equal
   ('=') sign and a VALUE.  Multiple setup strings can be passed in the
   NCC_SETUP_POST environment variable by separating each setup string with
   a semicolon (';').  The creation of this parameter can be performed
   either using the WorkSpace On-Demand Public Applications Notebook (on the
   Parameters page) or using a Command Line Interface (CLI).  The following
   is an example of one parameter:

       NCC_SETUP_POST=ICONPOS=10,10;


   The NCC_SETUP_POST environment variable will be searched for when each
   WorkSpace On-Demand public application is created.  If it is found, its
   value will be used when creating the public application on the WorkSpace
   On-Demand Desktop.

   The following KEYNAME values are permitted for setup strings:


   
                                                            New Function  22


                    October 4, 2001 - Warp 4 FixPak XRJM015

       Keyname        Value            Description
       -------        -----            -----------

       CCVIEW         DEFAULT          Specifies the default value for
                                       concurrent views
                      YES              Creates new views
                      NO               Displays the open view

       ICONFILE       filename         Sets the object's icon.

       ICONPOS        x,y              Sets the initial icon position in
                                       a folder.  The "x" and "y" values
                                       represent the position in the object's
                                       folder in percentage coordinates.

       ICONRESOURCE   id,module        Sets the object's icon.  The "id"
                                       is the icon resource ID in the dynamic
                                       link library (DLL) "module."


   Refer to the Workplace Shell Programming Reference for a description and
   definition of the above setup strings.

   Note: The NCC_SETUP_POST environment variable exists in the current
   environment when the public application with which it is associated is
   running.


   6.6.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN

   Three command line options have been added to both TLOGOFF.EXE and
   TSHUTDWN.EXE:

    1.  /Q -- causes these programs not to display the UPM/LAN
              copyright window.
    2.  /N -- causes no confirmation message boxes to be displayed.


   Note: If these parameters are not capitalized, they are ignored.


   6.6.4 PMLOGON NO PROGRESS INDICATOR OPTION

   An execution parameter has been added to PMLOGON that causes the progress
   indicator window not to be displayed during all of logon processing. That
   parameter is /NOPI and can be specified only from the RUNWORKPLACE line
   in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit,
   it is ignored.




   
                                                            New Function  23


                    October 4, 2001 - Warp 4 FixPak XRJM015

   6.6.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION

   An execution parameter has been added to PMLOGON which prevents PMLOGON
   from setting any of its windows to be system modal after user exit 1 is
   executed on the first boot or anytime after a logoff.  The parameter is
   /NOSM1 and can only be specified from the RUNWORKPLACE line in
   CONFIG.SYS.  If /NOSM1 is returned as a parameter from a user REXX exit,
   it is ignored.


   6.7 EURO SUPPORT

   The European Monetary Union is creating the Euro as a new common currency
   for Europe.  As part of this effort the European Commission has
   introduced a new character which represents the Euro.  This character
   looks like an uppercase C with two horizontal lines through it.  The Euro
   will come into existence on January 1, 1999 for use in banking.  Euro
   notes and coins will be issued starting January 2002.



   6.7.1 BASE OS/2 SUPPORT

   The OS/2 basic support for Euro consists of adding the Euro character to
   fonts, codepages, and keyboards.  The Euro is added to all display and
   ATM fonts and to the Times New Roman MT 30 TrueType font which is
   available with Java 1.1.  The Euro is added to all western European
   keyboards and the US International keyboard.  The Euro can be used in
   base OS/2, Presentation Manager, and in DOS.  The Euro is not supported
   in WinOS2.

   The Euro character is added to these OS/2 base and PM codepages:

       850    0xD5   PC Latin 1          base + PM
       857    0xD5   PC Turkish          base + PM
       1004   0x80   Windows Extended    base + PM
       1250   0x80   Windows Latin 2     PM
       1251   0x88   Windows Cyrillic    PM
       1252   0x80   Windows Latin 1     PM
       1254   0x80   Windows Turkish     PM
       1257   0x80   Windows Baltic      PM


   The Euro character is added to these fonts.








   
                                                            New Function  24


                    October 4, 2001 - Warp 4 FixPak XRJM015

       Courier                      (bitmap)
       Courier                      (ATM)
       Helv                         (bitmap)
       Helvetica                    (ATM)
       System Monospace             (bitmap)
       System Proportional          (bitmap)
       System VIO                   (bitmap)
       Times New Roman              (ATM)
       Times New Roman MT 30        (TrueType - Java 1.1)
       Tms Rmn                      (bitmap)
       WarpSans                     (bitmap)


   The Euro character is added to these OS/2 keyboards:

       Belgium           be       altgr-e
       Canada            ca       altgr-e
       Canadian French   cf       altgr-e
       Denmark           dk       altgr-5
       Finland           su (fi)  altgr-5
       France            fr       altgr-e
       Germany           gr (de)  altgr-e
       Germany(453)      de453    altgr-e
       Iceland           ic (is)  altgr-5
       Iceland 101       is458    altgr-5
       Italy             it       altgr-5
       Italy extended    itn142    altgr-5
       Latin America     la       altgr-e
       Netherlands       nl       altgr-e
       Norway            no       altgr-5
       Portugal          po       altgr-5
       Spain             sp (es)  altgr-5
       Sweden            sv       altgr-5
       Swiss French      sf       altgr-e
       Swiss German      sg (sd)  altgr-e
       Turkey            tr179    altgr-e
       Turkey 440        tr440    altgr-e
       UK                uk       altgr-4
       UK 168            uk168    altgr-e
       US International  ux       altgr-e





   6.7.2 WHERE EURO IS NOT SUPPORTED

   The Euro is not supported in WinOS2.  This character is not supported in
   the Windows-1252 codepage used in WinOS2.  This character is not
   available on the WinOS2 keyboards.  This character is not available in
   the WinOS2 supplied TrueType fonts:

   
                                                            New Function  25


                    October 4, 2001 - Warp 4 FixPak XRJM015

           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.



   6.7.3 PRINTING THE EURO

   Existing printers do not support the Euro in device fonts.  You need to
   select a font which is not mapped to a device font in order to print the
   Euro.  The Euro will print correctly on printers where the system fonts
   are used.  When there are problems, a dotless-i is normally printed
   instead of the Euro.

   For PostScript printers, it is necessary to disable device fonts to print
   the Euro in one of the base PostScript fonts (Helvetica, Times Roman,
   Courier).  To do this:

   1. Open the properties of the Printer object
   2. Select the Print Driver tab
   3. Select Job Properties
   4. Select the Output tab
   5. Deselect "Use printer device fonts"



   6.8 NEW WARP REGISTRY EDITOR

   See the README.REG file on the first FixPak disk for details.


   6.9 WORKSPACE ON DEMAND

   WorkSpace on Demand Release 1 is supported starting with FixPak 5
   (XR_M005).  WorkSpace on Demand Release 2 is supported starting with
   FixPak 11 (XR_M011).


   6.10 IBM OPEN32

   This FixPak includes updates to the IBM Open32 Application Programming
   Interfaces (APIs).





   
                                                            New Function  26


                    October 4, 2001 - Warp 4 FixPak XRJM015

   6.11 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)

   Future updates for GRADD and other video drivers (when they are released)
   will be found via the internet at:

   þ  http://service.software.ibm.com/pslaunch.html



   6.12 JOLIET-2 SUPPORT IN CDFS.IFS

   Joliet is a Microsoft extension to the ISO 9660 CD-ROM file system which
   adds Unicode and longname support.  Presently both Windows 95 and Windows
   NT 4.0 support the Joliet-2 and Joilet-3 formats.  Beginning with Warp 3
   Fixpak 32 and Warp 4 Fixpak 4, you can enable the Joliet-2 support by
   adding the '/w' option to the CDFS.IFS statement in CONFIG.SYS.

   Joilet-3 format is not supported.



   6.13 NEW (IMPROVED) CHKDSK

   This version of CHKDSK offers significant improvements for High
   Performance File System (HPFS) drives.  CHKDSK now fixes all errors found
   on HPFS drives in a single pass, operating faster, and with less memory
   than previous versions.  It contains better error detection and
   correction algorithms, and creates a log file so service personnel can
   determine what errors it found and how it corrected them.  Finally, only
   the amount of physical memory in your system limits the size of the
   largest drive CHKDSK can check at boot time (autocheck).

   Improvements in this version of CHKDSK are for HPFS drives only.  No
   changes occurred to checking File Allocation Table (FAT) drives.  This
   enhanced CHKDSK operates on IBM OS/2 Warp 3.0 and higher, including IBM
   Warp 4, IBM Warp Server 4 and IBM Warp Server 4 SMP.  This new CHKDSK
   version will not run on version of OS/2 before OS/2 Warp 3.0.


   6.13.1 USING THE NEW CHKDSK

   The interface to CHKDSK remains CHKDSK.COM and PMCHKDSK.  No changes
   occurred to the CHKDSK command line parameters or messages.

   The first time this version of CHKDSK runs on a fast formatted drive, it
   will report harmless errors.  These errors go away once CHKDSK is run
   with the /F option.

   Note: OS/2 Warp Install uses fast format.



   
                                                            New Function  27


                    October 4, 2001 - Warp 4 FixPak XRJM015

   Unlike prior versions of CHKDSK, large drives ( > 8GB) may be autochecked
   if sufficient memory is available.  The amount of memory required can
   vary between 16MB and 48MB depending on the size of the drive.  To enable
   the autochecking of large drives, the following line must be added to
   your config.sys:

     BASEDEV=CHKDSK.SYS


   This device driver allows CHKDSK to access memory normally reserved for
   the system during the boot process.  Due to this, if CHKDSK has to use
   this memory:

   þ  The memory will not be available for the system to use in completing
      the boot process
   þ  Errors may occur later in the boot process.

   Hence, the chkdsk.sys device driver is smart enough to recognize when
   CHKDSK has used this reserved memory and will reboot the system
   automatically after all HPFS drives have been checked.  Since the drives
   were checked before the reboot, CHKDSK will not have to check them after
   the reboot and the system will boot normally.

   Note: For those wishing to run unattended:  In order to prevent the
   system from pausing between autocheck and the reboot, we recommend that
   the statement PAUSEONERROR=NO be in the CONFIG.SYS.

   When you don't have enough physical (real) memory to autocheck large
   drives, you must use virtual memory from SWAPPER.DAT.  The technique is
   to check the large drives between the time OS/2 starts and PM begins.  To
   start OS/2, the swap file and device drivers must reside on an unaffected
   drive.  The drives to be checked must not appear in the autocheck list in
   the IFS statement for HPFS (or HPFS386).

   This technique involves the following steps:

   1. Remove the drive letter of the affected drive(s) from the autocheck
      list in the IFS statement for HPFS (or HPFS386).
   2. If you are using HPFS, add /QUIET to the IFS statement for HPFS.
   3. If you are using HPFS386.IFS, add POPUPERRORS=NO below the
      [filesystem] section of the HPFS386.INI file. Support for the
      POPUPERRORS parameter requires OS/2 LAN Server FixPak IP08265 or
      higher for LS 5.0 or FixPak IP08503 or higher for LS 5.1. In addition,
      the POPUPERRORS parameter ONLY suppresses HFS0102 messages.
   4. Add a CALL statement to your config.sys.  This CALL statement will
      call CHKDSK.COM, and will tell it what drive to check. This CALL
      statement must appear after the LIBPATH=, SET PATH=, and SET DPATH=
      statements, but before any other CALL statements in your CONFIG.SYS
      file.



   
                                                            New Function  28


                    October 4, 2001 - Warp 4 FixPak XRJM015

   Calls to CHKDSK in STARTUP.CMD are not necessary, when using this method
   or the base device driver (chkdsk.sys) method.

   Example: The computer boots from drive C (moderate HPFS or FAT sized
   drive).  Drive D (large HPFS) requires more RAM to check than installed
   in the machine.

     Original IFS statement:

          IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:CD

     New IFS statement:

          IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:C /QUIET

     The CALL statement to use is:

          CALL=C:\OS2\CHKDSK.COM D: /C


   The /C option tells CHKDSK to check the drive only if it is "dirty" and
   it needs checking.

   If you need to boot from diskettes to check an HPFS drive, you must have
   the following files on the diskette you wish to run CHKDSK from:

     CHKDSK.COM
     CHKDSK32.DLL
     UHPFS.DLL


   The BOOTDISK.EXE program has been updated to create new utility diskettes
   with the proper files.


   6.13.2 CHKDSK LOG FORMATTER

   CHKDSK creates a binary service log file (chkdsk.log) on the root of the
   drive being checked during autocheck or whenever the /F option is
   invoked.  The previous log file is saved as chkdsk.old. A formatter for
   this log file can be found at:

   ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe


   This is a self extracting ZIP file. Place it in a directory in your path
   and enter CHKLOGPK. This will create the following files:





   
                                                            New Function  29


                    October 4, 2001 - Warp 4 FixPak XRJM015

     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.


   6.14 AUTOMATED TRAP SCREEN LOGGING

   Whenever an application program traps, the trap information is (now)
   automatically logged in the POPUPLOG.OS2 file. This is a cumulative file
   that is by default located in the root directory of the bootable
   partition.  Should this file become too large then it may be erased or
   pruned (reduced in size). The system will automatically re-create it if
   it does not exist.

   The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used
   to control trap screen behavior (see below).


   6.14.1 SUPPRESSPOPUPS

   SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior.  That
   is, to disable logging and to have trap screens displayed unless
   specifically overridden by an application's use of the DosError API.

   SUPPRESSPOPUPS=x: will disable trap screen display for all processes and
   will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or
   partition.

   If SUPPRESSPOPUPS is omitted then the behavior is as described above
   under "Automated Trap Screen Logging".


   6.14.2 TRAPLOG

   The TRAPLOG command allows dynamic control of trap information logging.

   The command syntax is:

          TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]



   
                                                            New Function  30


                    October 4, 2001 - Warp 4 FixPak XRJM015

   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.



   6.14.3 TRAPDUMP

   The TRAPDUMP command allows the conditions under which a trap will
   initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak
   29, the System Dump setting could only be manipulated from CONFIG.SYS by
   use of the TRAPDUMP statement.

   Use of this command should be made under the direction of service
   personnel.

   Warning: The initiation of a System Dump causes an immediate termination
   of the system without any shutdown. No file system shutdown is performed.
   The system behaves as if a fatal crash has occurred, thus under rare
   circumstances data can be lost.

   The command syntax is:

          TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]


   where:

   þ  ON enables all application and system traps to initiate a System Dump.
   þ  OFF disables automatic dump initiation.
   þ  R0 enables only Ring 0 traps to initiate a System Dump.
   þ  x: specifies the Dump Partition.
   þ  NOCHECK overrides the system level check for WARP 4.0, since use of
      this command on a system level prior to FixPak 29 is equivalent to the
      SYSDUMP command.



   6.14.4 SYSDUMP

   The SYSDUMP command forces a System Dump to be initiated, regardless of
   the TRAPDUMP settings. This command is provided for the use of service
   personnel to allow Dump Initiation to be automated through use of a
   command file.

   Warning: The initiation of a System Dump causes an immediate termination
   of the system without any shutdown. No file system shutdown is performed.

   
                                                            New Function  31


                    October 4, 2001 - Warp 4 FixPak XRJM015

   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)"




   6.15 REXX NEW FUCTION

   New Function has been added in REXX. Please see the "Other README Files"
   for documentation pointers. This new function was added to FP 13 and
   later.


   6.16 OTHER README FILES

   There are other README files containing information you may want to
   review.  All except README.DBG are found on the first FixPak disk and are
   not copied to your system when the Fixpak is installed. README.DBG will
   be copied to the \OS2\INSTALL directory during installation beginning
   with Fixpak 10 and Fixpak 41.

   File           Use

   README2        Problems fixed in each FixPak (APAR list)

   README.CID     Installing FixPaks via CID

   README.REG     Use of the Warp Registry Editor REGEDIT2.EXE

   README.DBG     Tips on debugging OS/2 Warp and details on the latest
                  Serviceability (RAS) Enhancements (3.0 and 4.0).

   READREXX.TXT   New RexxUtil Function documentation added in this FixPak.







   
                                                            New Function  32


                    October 4, 2001 - Warp 4 FixPak XRJM015

   7.0 CORRECTIVE SERVICE FACILITY



   7.0.1 REQUIRED CSF LEVEL

   You should use release level f.143 or later of the OS/2 Corrective
   Service Facility to install this FixPak.

   Bootable diskettes are no longer provided starting with the F.138B CSF
   build. Instead, you now get a self-extracting ZIP file which contains the
   following:

      archctl.cmd
      build.lvl
      csfpans.dll
      filefix.dll
      fpinst.cmd
      fservice.exe
      fservice.msg
      ibmcsflk.dll
      ibmcsflk.exe
      ibmcsflk.msg
      ibmcsflk.sys
      msg.dll
      nls.dll
      pack.exe
      read.me
      readme.inf
      response.lan
      response.wp3
      response.wp4
      service.exe
      service.hlp
      shpiinst.dll
      unpack.exe
      unpack2.exe
      viocalls.dll


   Follow the directions in the READ.ME file to use the new CSF code. It
   covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
   from one of several alternative boot methods.


   7.0.2 WHERE YOU CAN FIND CSF CODE

   The Corrective Service Facility code is available from many places,
   including, but not limited to, the following:

   Source         How to access

   
                                             Corrective Service Facility  33


                    October 4, 2001 - Warp 4 FixPak XRJM015


   Internet(FTP)  Anonymous FTP to ftp.software.ibm.com in the
                  "/ps/products/os2/fixtool" directory.

   Internet(WWW)  Point your Web Browser at
                  ftp://service.boulder.ibm.com/ps/products/os2/fixtool

   Intranet(FTP)  Anonymous FTP to os2service.austin.ibm.com in the
                  "f:\fixpacks\fixtool" directory.



   7.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 XRJM015.?DK A: /F  (? can be 1 through 9, A through Z).

   Label the diskette as

         FixPak XRJM015
   Corrective Service Diskette ?
          (CSF DISK ?)


   Note: For diskette images ADK through ZDK, use the numbers 10 through 35.

        Examples:

        XRJM015.ADK = 10
        XRJM015.FDK = 15
        XRJM015.LDK = 21
      etc.




   7.1 RESIDUAL FIXPAK FILES FROM OS/2 2.11 OR WARP 3

   If the following is true:

   1. You upgraded your system from OS/2 2.11 or Warp 3
   2. You applied one or more FixPaks to the previous system
   3. You HAVE NOT applied a Warp 4 FixPak


   
                                             Corrective Service Facility  34


                    October 4, 2001 - Warp 4 FixPak XRJM015

   You will have files and directories left on your harddisk that will cause
   problems when installing a Warp 4 FixPak.

   To prevent these problems from occurring, do the following before
   applying your first Warp 4 FixPak.

   On your Warp 4 boot drive:

   þ  Delete \OS2\INSTALL\LOGF0000.OS2
   þ  ATTRIB -R \OS2\INSTALL\LOGSTART.OS2
   þ  Delete \OS2\INSTALL\LOGSTART.OS2

   On the drive where Multimedia Presentation Manager is installed:

   Note: This can be your Warp 4 boot drive or any other drive on your
   system.  Check the "SET MMBASE=" statement in CONFIG.SYS to determine
   which drive this is.

   þ  Delete \MMOS2\INSTALL\LOGF0000.MPM
   þ  ATTRIB -R \MMOS2\INSTALL\LOGSTART.MPM
   þ  Delete \MMOS2\INSTALL\LOGSTART.MPM

   Remove the old Archive and Backup directories and SERVICE.LOG file to
   recover the space they are using.

   You should also remove the FixPak Archive and Backup directories left
   over from your updated OS/2 2.11 or Warp 3 system at this time as well as
   the \OS2\INSTALL\SERVICE.LOG file.


   7.2 READ-ONLY FILES

   Some files being updated by this FixPak may have the Read-Only attribute
   set. If you are using the A:SERVICE method to install this FixPak you
   will be asked if you want the files replaced.

   Press the "OK" button.


   7.3 SYSLEVEL FILE LOCATIONS

   This FixPak will service directories based on the location of a supported
   SYSLEVEL.OS2 file.  Please check your system to make sure extra copies of
   this file are not located in directories other than:

     \OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)


   If additional copies of these files are found in other locations on your
   hard disk then CSF will try to service files as follows:


   
                                             Corrective Service Facility  35


                    October 4, 2001 - Warp 4 FixPak XRJM015

   For \OS2\INSTALL\SYSLEVEL.OS2

     ..\..\           all files in a directory two levels above (toward the
                      root). This should be the root directory of your boot
                      drive.

     ..\*             all files in a directory one level above (toward the root)
                      and all subdirectories below. This should be the OS2
                      directory and subdirectories.

     ..\..\VT\*       all files in the VT directory and subdirectories.

     ..\..\PSFONTS\*  all files in the PSFONTS directory and subdirectories.

     ..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories.

     ..\..\OPENDOC\*  all files in the OPENDOC directory and subdirectories.




   7.4 RELOCATED OS/2 FILE SUPPORT

   If you have moved OS/2 files or directories to a drive other than the one
   the SYSLEVEL.OS2 file is on, do the following in order to have them
   serviced:

   þ  Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
      OS\2 Warp 4 partition to be serviced.

      In this file, place the full path to the directories you want to be
      serviced. Assuming your boot drive is C: and you installed Multimedia
      on the D: drive and manually moved WINOS2 support to the E: drive:



















   
                                             Corrective Service Facility  36


                    October 4, 2001 - Warp 4 FixPak XRJM015

       D:\MMOS2
       D:\MMOS2\DLL
       D:\MMOS2\DSP
       D:\MMOS2\HELP
       D:\MMOS2\IMAGES
       D:\MMOS2\INETTEMP
       D:\MMOS2\INSTALL
       D:\MMOS2\MACROS
       D:\MMOS2\MOVIES
       D:\MMOS2\SOUNDS
       D:\MMOS2\SOUNDS\DESKTOP
       D:\MMOS2\SOUNDS\GARDEN
       D:\MMOS2\SOUNDS\OCEAN
       D:\MMOS2\SOUNDS\SPACE
       E:\OS2\MDOS\WINOS2
       E:\OS2\MDOS\WINOS2\SYSTEM
       E:\OS2\MDOS\WINOS2\TEMP


   Note: Leave this file for any future OS/2 Warp 4 FixPaks you might apply.
   The easy way to create this file is to use the DIR command with the /A:D
   /S /B parameters and pipe the output to a file.

      dir d:\mmos2 /a:d /s /b > anyfile


   Then copy that data into the USERDIRS.OS2 file.

   With CSF release level F.137B or later, you can use wildcards, so your
   USERDIRS.OS2 file would be much simpler and would look like:

       D:\MMOS2\*
       E:\OS2\MDOS\WINOS2\*



















   
                                             Corrective Service Facility  37


                    October 4, 2001 - Warp 4 FixPak XRJM015

   8.0 INSTALLATION PROCESS



   8.1 BEFORE INSTALLATION

   Before installing any FixPak, run CHKDSK /F against all drives on your
   system to correct any file system errors that might be present. You
   cannot do this while OS/2 is active. You must shut down and run CHKDSK by
   one of the following methods:

   þ  Boot from your Installation, DISK 1 and DISK 2 diskettes.  If your
      file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL
      on it in your A: drive before issuing the CHKDSK command.
   þ  Boot from the Utilities disk you created via the "Create Utility
      Diskettes" icon in the System Setup folder.
   þ  Boot from a different OS/2 partition.

   Once CHKDSK has completed, reboot your system then shutdown all running
   applications before starting the FixPak installation.


   8.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.

   Note: CS_???.EXE below means CS_143 or later.

   Follow the instructions in the READ.ME file that comes in the CS_???.EXE
   self-extracting zip file.  This explains how to use the CS_???.EXE file
   and the various ways you can install a FixPak with this level of CSF
   code.

   Here are some additional notes:

   Follow the displayed instructions.  When prompted to insert Corrective
   Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XRJM015
   Corrective Service Diskette 1 in drive A. Repeat for the rest of the
   FixPak disks when requested to do so.

   It can take a considerable length of time for the Corrective Service
   Facility to scan your hard disk for serviceable files.  In some cases, it
   has taken as long as 40 minutes.  Please be patient and allow this
   process to complete.

   If this is the first OS/2 Warp FixPak you have applied to this system,
   then enter the path to the directory where a copy of replaced files will
   be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)

   Note: This ARCHIVE directory is not related to the ARCHIVES directory
   built into OS/2 Warp 3 and Warp 4. Please specify a different path.  You
   must specify a different ARCHIVE directory for each product to be
   serviced.

   
                                                    Installation Process  38


                    October 4, 2001 - Warp 4 FixPak XRJM015

   If this is not the first OS/2 Warp FixPak, then enter the path to the
   BACKUP directory where a copy of replaced files will be stored (for
   example, D:\BACKUP).

   Note: You must specify a different BACKUP directory for each product to
   be serviced.

   Make sure there is sufficient space available on the drive you specify
   for archive or backup.  Even though these files are kept in compressed
   (PACK2) format, they can take up a lot of space on the drive.

   During the installation process you may see messages about Archiving,
   Updating and Deferring service.

   þ  Archiving saves a compressed copy of the original file in the ARCHIVE
      or BACKUP path you specified.
   þ  Updating means the original files are replaced with the new ones from
      this FixPak.
   þ  Deferring service means the file to be updated is currently in use by
      the system and cannot be updated.  The new files from the FixPak are
      placed in unpacked format in the \IBMCSFLK\FIX directory on the drive
      with the most free space.  They are processed by the locked file
      device driver during reboot after you shut down the system.

   See the section "FixPak Corrective Service levels and disk layouts" for
   the CSD levels this FixPak applies to.

   You will see the following during reboot of the system if you applied
   service to the OS/2 partition you were booted from.

      The locked file driver is loaded.

             Processing locked files

             Processing complete


   The system will do one automatic reboot after the Locked File Device
   Driver has completed.


   8.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA

   Note: CS_???.EXE below means CS_143 or later.

   Follow the instructions in the READ.ME file that comes in the CS_???.EXE
   self-extracting zip file.  This explains how to use the CS_???.EXE file
   and the various ways you can install a FixPak with this level of CSF
   code.



   
                                                    Installation Process  39


                    October 4, 2001 - Warp 4 FixPak XRJM015

   Here are some additional notes:

   This method does not prompt the user for any information.  No interaction
   with the user takes place other than requests to put the next diskette in
   drive A. All serviceable partitions on your system will be updated
   automatically unless you have modified the default response file.  Be
   especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
   this method because they can cause CSF to apply service to directories
   you do not want serviced.

   See the section "FixPak Corrective Service levels and disk layouts" for
   the CSD levels this FixPak applies to.

   Note: It can take a considerable length of time for the Corrective
   Service Facility to scan your hard disk for serviceable files.  Please be
   patient and allow this process to complete.

   Note: You can edit the response file to control some of the actions taken
   by FSERVICE.EXE while applying a FixPak.  See the READ.ME file or use the
   VIEW command to look at the file README.INF.  They are part of
   CS_???.EXE.


   8.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION

   Additional information on the Corrective Service Facility, like how to
   backout a FixPak, is available from the README.INF file on the first
   Corrective Service Facility disk.  To view this file, place CSF disk 1 in
   drive A and enter VIEW A:\README.INF.

   There is also some additional information in the READ.ME file.





















   
                                                    Installation Process  40


                    October 4, 2001 - Warp 4 FixPak XRJM015

   9.0 CSD LEVEL OF SYSLEVEL.OS2

   The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
   partition will be updated with the name of the FixPak when it is applied.

   This is a major change from previous CSF releases. The Prior CSD level
   field will be left asis. This means when you use the SYSLEVEL command to
   look at the release levels of products on your system, you will see the
   following for SYSLEVEL.OS2.

   Before a FixPak is applied using the F.138B CSF build (or later)

      E:\OS2\INSTALL\SYSLEVEL.OS2
      IBM OS/2 Base Operating System
      Version 4.00     Component ID 5639A6100
      Type 0C
      Current CSD level: XR04000
      Prior   CSD level: XR04000


   After a FixPak is applied using the F.138B CSF build (or later)

      E:\OS2\INSTALL\SYSLEVEL.OS2
      IBM OS/2 Base Operating System
      Version 4.00     Component ID 5639A6100
      Type 0C
      Current CSD level: XR0M008
      Prior   CSD level: XR04000


   All fix information is recorded in SERVICE.LOG. Look at the file

      \OS2\INSTALL\SERVICE.LOG


   on your boot drive for information relating to the installation of
   FixPaks on your system.

   Additionally, you can use the VER /R command to see the current revision
   of OS/2 installed.  The response will look like the following for this
   FixPak:

   The Operating System/2 Version is 4.50
   Revision 14.044


   The first page of this document has a line that looks like:

   Build Level: nn.nnn



   
                                               CSD level of SYSLEVEL.OS2  41


                    October 4, 2001 - Warp 4 FixPak XRJM015

   That is the number you should see for this FixPak when you issue the VER
   /R command.


   9.0.1 NEW SYSLEVEL.FPK

   A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning with
   XR_M004.  It is titled "OS/2 Warp 4 Service Level".  It contains the name
   of the currently installed FixPak in both the Current and Previous CSD
   level fields and is located in the same directory the SYSLEVEL.OS2 file
   is located in which should be \OS2\INSTALL.

   The easiest way to look at SYSLEVEL information is to use the SYSLEVEL
   command and redirect the output to a file then edit the file and search
   for SYSLEVEL.FPK.





































   
                                               CSD level of SYSLEVEL.OS2  42


                    October 4, 2001 - Warp 4 FixPak XRJM015

   10.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 14.062

   Product location on CSD:  A:\FIX\OS2.1
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6120
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\
           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*
   Will create the following directories
      ..\..\OS2   Stub File:  @OS2DIR

      ..\..\OS2\DLL   Stub File:  @DLLDIR

      ..\..\OS2\BOOT   Stub File:  @BOOTDIR

      ..\..\OS2\SYSTEM   Stub File:  @SYSTDIR


   
                       FixPak Corrective Service levels and disk layouts  43


                    October 4, 2001 - Warp 4 FixPak XRJM015

      ..\..\OS2\INSTALL   Stub File:  @INSTDIR

      ..\..\OS2\INSTALL\BOOTDISK   Stub File:  @INBTDIR

      ..\..\OS2\APPS   Stub File:  @APPSDIR

      ..\..\OS2\SYSTEM\RAS   Stub File:  @RASDIR

      ..\..\OS2\SYSTEM\TRACE   Stub File:  @TRACDIR

      ..\..\LANGUAGE\CODEPAGE   Stub File:  @CDPGDIR


   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   $JPNZN16.FNT  $JPNZN16.F9_   15    12/30/2010  11:33   185856  9991DAB1
   $JPNZN16.FNT  $JPNZN16.F7_   13    12/30/2010  10:40   185856  0E273378
   $JPNZN24.FNT  $JPNZN24.F9_   12    12/30/2010  11:33   342528  93833AFC
   $JPNZN24.FNT  $JPNZN24.F7_   12    12/30/2010  10:40   343040  E827267B
   AA.KBL        AA.KB_         26    10/12/2000  16:00     1200  05C2A948
   AA470.KBL     AA470.KB_      26    10/12/2000  16:00     1212  6729A283
   ALIASFNT.EXE  ALIASFNT.EX_   22    10/19/2000  21:11    88368  F17994B9
   ANSICALL.DLL  ANSICALL.DL_   27    11/15/2000  18:31      512  4B93CCD4
   APPEND.EXE    APPEND.EU_     26    11/15/2000  19:32     7602  0FFAE4BA
   APPEND.EXE    APPEND.EX_     26    11/15/2000  20:44     7650  F9EA2021
   ARACONV.EXE   ARACONV.EX_    23    11/23/1999  20:12    62151  F784F7D0
   ASIACOL.DLL   ASIACOL.DL_    18    10/12/2000  15:54   158758  1ECA61A1
   ASSIGN.COM    ASSIGN.CU_     26    11/15/2000  19:33     2684  1413A846
   ASSIGN.COM    ASSIGN.CO_     26    11/15/2000  20:44     2742  6FF53967
   ATTRIB.EXE    ATTRIB.EX_     24    11/15/2000  20:44    37789  C5685FB9
   AVIO.DLL      AVIO.DL_       22    10/13/2000  10:12    53921  F4FA279B
   BA.KBL        BA.KB_         26    10/12/2000  16:00      980  294DB95E
   BACKUP.EXE    BACKUP.EX_     25    11/15/2000  20:52    35472  42F3B6BD
   BDBVH.DLL     BDBVH.DL_      26    11/23/1999  20:12    13874  A63C3B38
   BDCALL32.DLL  BDCALL32.DL_   24    11/23/1999  20:11    33519  761AA009
   BDCALLS.DLL   BDCALLS.DL_    24    11/23/1999  20:12    38149  A8F06EF1
   BDIME.DLL     BDIME.DL_      26    11/23/1999  20:12    11911  1CA663B5
   BDVIEW.DLL    BDVIEW.DL_     24    11/15/2000  02:59    34888  FF485512
   BDWPCLS.DLL   BDWPCLS.DL_    25    11/15/2000  02:58    20144  A5A0A30E
   BE.KBL        BE.KB_         26    10/12/2000  16:00      972  9473C4B2
   BG.KBL        BG.KB_         26    10/12/2000  16:00     1152  734A5EF9
   BG241.KBL     BG241.KB_      26    10/12/2000  16:00     1372  C8D04059
   BKSCALLS.DLL  BKSCALLS.DL_   27    11/15/2000  18:31      512  EDF5FB14
   BLDLEVEL.EXE  BLDLEVEL.EX_   23    10/06/2000  14:52    57842  DA887122
   BMSCALLS.DLL  BMSCALLS.DL_   27    11/15/2000  18:31      512  76063B15
   BOOTDISK.EXE  BOOTDISK.EX_   23    02/14/2001  10:57    61662  3DFC0D33
   BOOTDISK.HLP  BOOTDISK.HL_   26    02/09/2001  14:59    15053  40A94EA9
   BR.KBL        BR.KB_         26    10/12/2000  16:00      932  7F3B7C6C
   BR274.KBL     BR274.KB_      26    10/12/2000  16:00      852  240B6DCB

   
                       FixPak Corrective Service levels and disk layouts  44


                    October 4, 2001 - Warp 4 FixPak XRJM015

   BVHINIT.DLL   BVHINIT.DL_    26    09/15/2000  17:09    11158  EE660E10
   BVHMPA.DLL    BVHMPA.DL_     26    09/15/2000  16:10    15293  6169D262
   BVHVGA.DLL    BVHVGA.DL_     24    09/15/2000  16:09    31875  3C904D4F
   BVHVGA2.DLL   BVHVGA2.DL_    24    10/20/2000  15:43    35409  F58C7D5A
   BVHWNDW.DLL   BVHWNDW.DL_    26    09/15/2000  17:09    16797  DDF61B0D
   BVSCALLS.DLL  BVSCALLS.DL_   27    11/15/2000  18:31      512  EEB36284
   BY.KBL        BY.KB_         26    10/12/2000  16:00     1292  11BE6C9F
   CA.KBL        CA.KB_         26    10/12/2000  16:00     1214  8C1C9E65
   CACHE.EXE     CACHE.EX_      26    10/06/2000  15:17    13870  F36258D0
   CARDINFO.DAT  CARDINFO.DA_   26    10/13/2000  10:51    55282  DF383873
   CARDSYM.FON   CARDSYM.FO_    24    11/23/1999  17:43    60453  2FA044C7
   CCHMAIN.EXE   CCHMAIN.EX_    16    11/14/2000  19:38   199408  8D0A6E74
   CCHUSER.DLL   CCHUSER.DL_    22    11/14/2000  19:37    63763  24B23C1B
   CDFS.IFS      CDFS.IF_       24    10/06/2000  15:31    45145  75DC7945
   CDFS.TDF      CDFS.TD_       27    10/06/2000  15:31     2113  7D1B6068
   CDROM.TBL     CDROM.TB_      26    09/05/2000  11:54     4371  E4B6BE58
   CF.KBL        CF.KB_         26    10/12/2000  16:00      956  C70BE074
   CHGMON.EXE    CHGMON.EX_     26    10/19/2000  14:39     4260  AC812109
   CHKDSK.COM    CHKDSK.CO_     22    11/15/2000  20:44    70720  EE039456
   CHKDSK.SYS    CHKDSK.SY_     26    10/06/2000  15:18      795  3BABD09C
   CHKDSK32.DLL  CHKDSK32.DL_   19    10/06/2000  15:29   139227  56C2508B
   CHKDSK32.EXE  CHKDSK32.EX_   26    10/06/2000  15:18     6417  42B31C60
   CIDLOG.DLL    CIDLOG.DL_     25    01/04/2000  15:56    27312  835140F1
   CLDAPI.DLL    CLDAPI.DL_     25    10/30/2000  11:25    22217  F0DA163E
   CLIPOS2.EXE   CLIPOS2.EX_    26    11/14/2000  20:22    16411  15CDAE85
   CLOCK01.SYS   CLOCK01.SY_    26    09/22/2000  09:07     4560  E5023FAB
   CLOCK02.SYS   CLOCK02.SY_    26    09/22/2000  09:07     4318  352B5662
   CMD.EXE       CMD.EX_        20    11/15/2000  20:47   100108  EAD7EBC7
   CMDREF.INF    CMDREF.IN_      5    11/13/2000  08:01  1347235  072F393A
   COMMAND.COM   COMMAND.CO_    24    11/15/2000  20:46    50365  8D4F3917
   COMP.COM      COMP.CO_       24    11/15/2000  20:47    35881  A4ECA9F0
   CONTROL.PM    CONTROL.PM_    26    11/15/2000  20:51     8486  2F5DE3FB
   COUNTRY.SYS   COUNTRY.SY_    26    09/05/2000  18:01    50947  1934AC0B
   COUR.OFM      COUR.OF_       26    11/22/1999  11:22     6163  A932E20A
   COUR.PFB      COUR.PF_       17    11/22/1999  11:23   137111  48042447
   COUR.PFM      COU1.PF_       27    11/22/1999  11:22      674  EB120968
   COURB.OFM     COURB.OF_      26    11/22/1999  11:22     6173  303DCA2B
   COURB.PFB     COURB.PF_      17    11/22/1999  11:23   140829  503DA434
   COURB.PFM     COUR1.PF_      27    11/22/1999  11:22      679  1EF9BF6B
   COURBI.OFM    COURBI.OF_     26    11/22/1999  11:22     6187  0F573DD1
   COURBI.PFB    COURBI.PF_     17    11/22/1999  11:23   136240  16421DEB
   COURBI.PFM    COURB1.PF_     27    11/22/1999  11:22      685  50390DEF
   COURI.OFM     COURI.OF_      26    11/22/1999  11:22     6178  179F133A
   COURI.PFB     COURI.PF_      17    11/22/1999  11:23   137394  714935E2
   COURI.PFM     COUR2.PF_      27    11/22/1999  11:22      681  A6EEB6A2
   COURIER.FON   COURIER.FO_    23    10/19/2000  13:03    77826  6ED0073A
   COURIERI.FON  COURIERI.FO_   22    10/19/2000  12:59    86641  C6745985
   CPG01256.TBL  CPG01256.TB_   26    11/22/1999  12:17    27264  A5C721BD
   CREX.MSG      CREX.MS_       26    09/06/2000  12:42     2865  81838E0E
   CREXUTIL.DLL  CREXUTIL.DL_   21    09/06/2000  12:42    68119  4D4A9597
   CREXX.DLL     CREXX2.DL_     17    09/06/2000  12:42   266031  C7016A5F

   
                       FixPak Corrective Service levels and disk layouts  45


                    October 4, 2001 - Warp 4 FixPak XRJM015

   CYRIME.DLL    CYRIME.DL_     25    10/19/2000  12:43    21529  4ED04128
   CZ.KBL        CZ.KB_         26    10/12/2000  16:00     1014  E4EC6917
   DDINSTAL.EXE  DDINSTAL.EX_   24    11/15/2000  21:09    52263  A881AE03
   DE.KBL        DE.KB_         26    10/12/2000  16:00      958  28E3A029
   DE453.KBL     DE453.KB_      26    10/12/2000  16:00     1354  1CF79BBC
   DEBUG.EXE     DEBUG.EU_      25    11/15/2000  19:34    27233  3218A531
   DEBUG.EXE     DEBUG.EX_      25    11/15/2000  20:48    27985  DF9D54C9
   DF_DEB.EXE    DF_DEB.EX_     20    11/15/2000  18:05   135989  52462C3C
   DF_RET.EXE    DF_RET.EX_     20    11/15/2000  16:51   135957  94CE7FB8
   DIBDRVR.DLL   DIBDRVR.DL_    26    10/19/2000  14:02     5627  7A64BF1B
   DICTATE.EXE   DICTATE.EX_    22    05/06/1998  11:58    59315  50477D97
   DICTDLL.DLL   DICTDLL.DL_    22    12/21/1997  01:28    51187  2DAC90F6
   DISKCOMP.COM  DISKCOMP.CO_   24    11/15/2000  20:52    41697  017466C0
   DISKCOPY.COM  DISKCOPY.CO_   24    11/15/2000  20:52    46196  25C10E9F
   DIVE.DLL      DIVE.DL_       21    10/06/2000  08:13    69662  B5D13AA0
   DK.KBL        DK.KB_         26    10/12/2000  16:00      928  CAEC9535
   DMISL.EXE     DMISL.EX_      20    10/06/2000  21:03   144918  AC808904
   DMQSPROF.DLL  DMQSPROF.DL_   22    09/15/2000  16:07    39033  62BBE86E
   DOSCALL1.DLL  DOSCALL1.DL_    8    11/15/2000  18:28   137819  E76B4FA1
   DOSCALL1.SYM  DOSCALL1.SY_   24    11/15/2000  18:28    43492  572025A5
   DOSCALL1.TDF  DOSCALL1.TD_   26    11/15/2000  16:50     5534  09AE23CB
   DOSKEY.COM    DOSKEY.CU_     26    11/15/2000  19:34     6243  B655A9C7
   DOSKEY.COM    DOSKEY.CO_     26    11/15/2000  20:48     7272  667A0DA3
   DOSKRNL       DOSKRNL.___    25    11/15/2000  18:28    31553  58F0142E
   DOSRFICO.DLL  DOSRFICO.DL_   24    09/06/2000  12:45    32332  BFFCD571
   DSPIMRI.DLL   DSPIMRI.DL_    26    09/15/2000  20:08    17958  A12F35A0
   DSPINSTL.EXE  DSPINSTL.EX_   20    10/02/2000  15:46   175640  C6659EB6
   DSPRES.DLL    DSPRES1.DL_    13    10/19/2000  12:59   376488  C8B8B2CB
   DSPRES.DLL    DSPRES.DL_     13    10/19/2000  12:59   376488  C8B8B2CB
   DSPSUP.FON    DSPSUP.FO_     14    10/19/2000  12:59   370008  B7E80682
   DTRACE.DOC    DTRACE.DO_     25    11/22/1999  11:25    75371  58765F89
   DTRACE.EXE    DTRACE1.EX_    23    10/06/2000  21:10    74850  254E4F97
   DTRACE.EXE    DTRACE.EX_     23    10/06/2000  21:10    74850  254EBC97
   E.EXE         E.EX_          22    11/14/2000  20:24    63383  89148D73
   EAUTIL.EXE    EAUTIL.EX_     24    11/15/2000  20:48    38512  74F187BE
   EDLIN.COM     EDLIN.CO_      26    07/01/1999  10:40    15080  B60E9E20
   EE.KBL        EE.KB_         26    10/12/2000  16:00      932  DB23D283
   EHXDLD.DLL    EHXDLD.DL_     26    11/14/2000  20:24    13861  EF211C19
   EHXDLMRI.DLL  EHXDLMRI.DL_   26    11/14/2000  20:24    13861  7874C389
   EJECT.EXE     EJECT.EX_      25    09/05/2000  18:11    29746  96E3362C
   EL.KBL        EL.KB_         26    10/12/2000  16:00     1396  610DE7D0
   EL220.KBL     EL220.KB_      26    10/12/2000  16:00     1428  F8265A42
   EL459.KBL     EL459.KB_      26    10/12/2000  16:00     1372  797B7C72
   ENGINE.EXE    ENGINE.EX_     11    07/23/1997  11:39   440424  CA47CBAA
   EPM.EX        EPM.E__        21    11/23/1999  17:03   145225  33E42936
   EPM.EXE       EPM.EX_        25    11/23/1999  17:44    24032  16DDF472
   EPMMRI.DLL    EPMMRI.DL_     21    11/23/1999  17:02    74986  25BFB447
   ERLOGGER.EXE  ERLOGGER.EX_   24    10/06/2000  14:10    48608  5EB8C0A5
   ERRLOG.DLL    ERRLOG.DL_     21    10/06/2000  14:09    72806  CF915F84
   ERRTXT.DLL    ERRTXT.DL_     25    11/15/2000  13:40    26714  741E43EA
   ES.KBL        ES.KB_         26    10/12/2000  16:00      920  3744F42A

   
                       FixPak Corrective Service levels and disk layouts  46


                    October 4, 2001 - Warp 4 FixPak XRJM015

   ETKC603.DLL   ETKC603.DL_    19    11/23/1999  16:02   136124  B18E8724
   ETKE603.DLL   ETKE603.DL_     8    11/23/1999  16:02   767421  C1804876
   ETKR603.DLL   ETKR603.DL_    24    11/23/1999  16:02    36713  3E7A36BC
   ETKUCMS.DLL   ETKUCMS.DL_    20    11/23/1999  15:53    88156  B176E2E9
   EZP2MRI.DLL   EZP2MRI.DL_    22    11/14/2000  20:25    95774  BFD3EA20
   FDISK.COM     FDISK.CO_      21    11/15/2000  20:54   126139  EEC3ACE6
   FDISKPM.DLL   FDISKPM.DL_    26    11/15/2000  20:54    10805  0C02C709
   FDISKPM.EXE   FDISKPM.EX_    22    11/15/2000  20:54    89156  87383E0F
   FDISKPMH.HLP  FDISKPMH.HL_   26    11/15/2000  20:54    18314  D17AF178
   FFCONFIG.DLL  FFCONFIG.DL_   25    10/06/2000  14:13    20551  1DDCCA4D
   FFDUMP.DLL    FFDUMP.DL_     23    10/06/2000  15:21    41217  D9206251
   FFGUI.DLL     FFGUI.DL_      26    10/06/2000  18:54    19067  AE8F868C
   FFIPC.DLL     FFIPC.DL_      25    10/06/2000  14:13    27201  F86D8B12
   FFPCT.DLL     FFPCT.DL_      25    10/06/2000  14:13    21588  96F267A8
   FFPROBE.DLL   FFPROBE.DL_    25    10/06/2000  14:50    24680  77EEB333
   FFST.DLL      FFST.DL_       26    10/06/2000  14:13    11425  B9B55D0A
   FFST.EXE      FFST.EX_       25    10/06/2000  15:21    32448  248748D3
   FFSTCONF.EXE  FFSTCONF.EX_   22    10/06/2000  15:21   104505  9E8F8833
   FFSTPCT.EXE   FFSTPCT.EX_    22    10/06/2000  15:21   105143  76829336
   FI.KBL        FI.KB_         26    10/12/2000  16:00      940  F49DDB21
   FILT.DLL      FILT.DL_       25    10/13/2000  10:07    22890  F997AA11
   FIND.EXE      FIND.EX_       25    11/15/2000  20:48    31053  92BE80DD
   FKA.DLL       FKA.DL_        26    11/22/1999  11:46    13997  66D06B79
   FNTCALLS.DLL  FNTCALLS.DL_   25    10/20/2000  15:43    22962  03513394
   FNTPROCV.EXE  FNTPROCV.EX_   26    10/20/2000  15:43     3519  E286FA9C
   FONTMEM.SYS   FONTMEM.SY_    26    10/20/2000  15:44     1466  70E8F809
   FORMAT.COM    FORMAT.CO_     22    11/15/2000  20:49    72064  B4FEA634
   FR.KBL        FR.KB_         26    10/12/2000  16:00      950  BC615CC6
   FSFILTER.SYS  FSFILTER.SY_   26    11/15/2000  18:28    12730  58AC71DB
   GLOCALE.DAT   GLOCALE.DA_    16    11/22/1999  11:47   362841  A5DCA1CA
   GLOCALE.EXE   GLOCALE.EX_    21    10/12/2000  16:13   145338  D84E80CE
   GLOCALE.HLP   GLOCALE.HL_    25    10/12/2000  16:13    34326  E7AF4225
   GLOCMRI.DLL   GLOCMRI.DL_    26    10/12/2000  16:13    11334  C644B42A
   GRADD.SYS     GRADD.SY_      26    09/15/2000  17:12     2754  03EBF6B1
   GRAFTABL.COM  GRAFTABL.CO_   26    11/15/2000  20:49     9628  CE2E559E
   GRE2VMAN.DLL  GRE2VMAN.DL_   26    09/15/2000  22:04    18189  1874FBCE
   GSVDAEMN.EXE  GSVDAEMN.EX_   26    07/20/2000  08:31     4832  286F48A6
   GSVINST.EXE   GSVINST.EX_    23    11/14/2000  19:01    34351  F6E06023
   HARDERR.EXE   HARDERR.EX_    26    11/15/2000  18:28    14377  51023C62
   HDMON.EXE     HDMON.EX_      21    10/06/2000  18:59   112063  29F706AF
   HELP.CMD      HELP.CM_       27    09/05/2000  12:01      586  4B90F9E5
   HELPMGR.DLL   HELPMGR.DL_    15    10/19/2000  13:01   250157  0A772627
   HELPMSG.EXE   HELPMSG.EX_    24    11/15/2000  20:49    37280  0C036091
   HELV.FON      HELV.FO_       18    10/19/2000  13:03   171252  BE4CF130
   HELV.OFM      HELV.OF_       26    11/22/1999  11:22     6793  9246E30D
   HELV.PFB      HELV.PF_       18    11/22/1999  11:23   120578  FEA723CE
   HELV.PFM      HEL1.PF_       26    11/22/1999  11:22     1096  C722994F
   HELVB.OFM     HELVB.OF_      26    11/22/1999  11:22     6785  54469E79
   HELVB.PFB     HELVB.PF_      18    11/22/1999  11:23   123085  0037BF2B
   HELVB.PFM     HELV1.PF_      26    11/22/1999  11:22     1089  DA484E9E
   HELVBI.OFM    HELVBI.OF_     26    11/22/1999  11:22     6787  40005DD9

   
                       FixPak Corrective Service levels and disk layouts  47


                    October 4, 2001 - Warp 4 FixPak XRJM015

   HELVBI.PFB    HELVBI.PF_     18    11/22/1999  11:23   124245  46A14EBC
   HELVBI.PFM    HELVB1.PF_     26    11/22/1999  11:22     1087  06B3AD9D
   HELVI.FON     HELVI.FO_      17    10/19/2000  12:59   199523  A15187FF
   HELVI.OFM     HELVI.OF_      26    11/22/1999  11:22     6772  3B0EE1CD
   HELVI.PFB     HELVI.PF_      18    11/22/1999  11:24   123355  48DC5DF0
   HELVI.PFM     HELV2.PF_      26    11/22/1999  11:22     1079  4D475EFF
   HG.CMB        HG.CM_         27    10/20/2000  15:47     8028  8CBF15AC
   HGP.CMB       HGP.CM_        27    10/20/2000  15:47     3380  547DD41D
   HKG-H90P.CMB  HKG-H90P.CM_   27    10/20/2000  15:47     3380  1AA2BC25
   HKGW590T.CMB  HKGW590T.CM_   27    10/20/2000  15:47     8028  19A76196
   HKGW5H90.CMB  HKGW5H90.CM_   27    10/20/2000  15:47     8028  F0989AAA
   HM-H90P.CMB   HM-H90P.CM_    27    10/20/2000  15:47     4044  AEB21752
   HM-W390T.CMB  HM-W390T.CM_   27    10/20/2000  15:47     8028  9113F923
   HM-W3H90.CMB  HM-W3H90.CM_   27    10/20/2000  15:47     8028  D0147033
   HM.CMB        HM.CM_         27    10/20/2000  15:47     8028  7F64CA5C
   HMP.CMB       HMP.CM_        27    10/20/2000  15:47     4044  F86BE111
   HPFS.IFS      HPFS.IF_       20    10/06/2000  15:15   141890  B15CB6D6
   HPFS.TDF      HPFS.TD_       27    10/06/2000  15:15     1620  5E70D1E9
   HPMGRMRI.DLL  HPMGRMRI.DL_   26    10/19/2000  14:35    18733  4CEA95D1
   HR.KBL        HR.KB_         26    10/12/2000  16:00      982  4371550F
   HU.KBL        HU.KB_         26    10/12/2000  16:00     1006  5894479F
   HWDVPD.DLL    HWDVPD.DL_     26    10/06/2000  14:04    19476  3DD13709
   IBM1004       IBM1004.___    26    10/12/2000  15:51     3584  9FB42D9E
   IBM1125       IBM1125.___    26    10/12/2000  15:51     4320  DB8513DC
   IBM1131       IBM1131.___    26    10/12/2000  15:51     4320  866C40E6
   IBM1140       IBM1140.___    26    10/12/2000  15:51     2816  776F51FA
   IBM1141       IBM1141.___    26    10/12/2000  15:51     2784  9B08CF2D
   IBM1142       IBM1142.___    26    10/12/2000  15:51     2816  7C6BA473
   IBM1143       IBM1143.___    26    10/12/2000  15:51     2816  FB88C823
   IBM1144       IBM1144.___    26    10/12/2000  15:51     2784  4087FB0E
   IBM1145       IBM1145.___    26    10/12/2000  15:51     2784  81D24DF7
   IBM1146       IBM1146.___    26    10/12/2000  15:51     2816  85F1F6E5
   IBM1147       IBM1147.___    26    10/12/2000  15:51     2784  7A2A00FC
   IBM1148       IBM1148.___    26    10/12/2000  15:51     2816  6114895E
   IBM1250       IBM1250.___    26    10/12/2000  15:51     3552  E91C78A4
   IBM1251       IBM1251.___    26    10/12/2000  15:51     3328  3AC2A11F
   IBM1252       IBM1252.___    26    10/12/2000  15:51     3552  BAEEE0FD
   IBM1253       IBM1253.___    26    10/12/2000  15:51     3552  9FCC3C7E
   IBM1254       IBM1254.___    26    10/12/2000  15:51     3552  65D18A68
   IBM1255       IBM1255.___    26    10/12/2000  15:51     3808  EEB4CAF7
   IBM1256       IBM1256.___    26    10/12/2000  15:51     4320  3DBDA3E8
   IBM1257       IBM1257.___    26    10/12/2000  15:51     3296  9D4AD72D
   IBM813        IBM813.___     26    10/12/2000  15:51     3072  08A2984D
   IBM850        IBM850.___     26    10/12/2000  15:51     4320  C9955D45
   IBM852        IBM852.___     26    10/12/2000  15:51     4608  FB8DC70F
   IBM857        IBM857.___     26    10/12/2000  15:51     4352  2B09830F
   IBM859        IBM859.___     26    10/12/2000  15:51     4320  0EF4A493
   IBM862        IBM862.___     26    10/12/2000  15:51     4576  96A84D36
   IBM864        IBM864.___     26    10/12/2000  15:51     4576  F9F0D5CC
   IBM869        IBM869.___     26    10/12/2000  15:51     4320  12FBFC5A
   IBM923        IBM923.___     26    10/12/2000  15:51     2784  6DCE74D1

   
                       FixPak Corrective Service levels and disk layouts  48


                    October 4, 2001 - Warp 4 FixPak XRJM015

   IBM924        IBM924.___     26    10/12/2000  15:51     2784  036319A7
   IBMOPTNS.DLL  IBMOPTNS.DL_   15    10/13/2000  10:51    22550  73E7BD47
   ICONEDIT.EXE  ICONEDIT.EX_   20    11/23/1999  17:02   163408  0E371980
   IL.KBL        IL.KB_         26    10/12/2000  16:00     1232  3CBAB0AB
   IMBRGDLL.DLL  IMBRGDLL.DL_   26    10/19/2000  14:39    10081  09BAE8F4
   IMBRIDGE.EXE  IMBRIDGE.EX_   26    10/19/2000  14:39    20669  B5ABA63D
   IMDAEMON.DLL  IMDAEMON.DL_   26    10/19/2000  15:20    11362  1E146177
   IMMON.EXE     IMMON.EX_      26    10/19/2000  14:40    10832  257B63EF
   IMP.DLL       IMP.DL_        26    10/20/2000  15:47     9653  1B3C2F49
   IMREGIST.EXE  IMREGIST.EX_   26    10/19/2000  15:59     3460  6FDAC0A1
   IMSTART.EXE   IMSTART.EX_    26    10/19/2000  15:20     3636  39EE57D6
   INSCFG32.DLL  INSCFG32.DL_   24    11/15/2000  21:14    32098  48E35EAB
   INSPGM32.DLL  INSPGM32.DL_   23    11/15/2000  20:52    41504  4CA38422
   INST_DOS.EXE  INST_DOS.EX_   23    10/19/2000  14:00    39114  40A3876B
   IOPROC.DLL    IOPROC.DL_     23    10/13/2000  10:16    37880  91C2CA33
   IS.KBL        IS.KB_         26    10/12/2000  16:00      940  86D694EE
   IS458.KBL     IS458.KB_      26    10/12/2000  16:00      928  1A3415EB
   IT.KBL        IT.KB_         26    10/12/2000  16:00      876  B83B7729
   IT142.KBL     IT142.KB_      26    10/12/2000  16:00      854  901F665B
   JIS90FNT.EXE  JIS90FNT.EX_   21    07/01/1999  10:40    66714  BCBF3DB7
   JOIN.EXE      JOIN.EU_       26    11/15/2000  19:35     4520  729938E4
   JOIN.EXE      JOIN.EX_       26    11/15/2000  20:49     4520  26AECBD6
   JP.KBL        JP.KB_         26    10/12/2000  16:00     6374  D871F0CA
   JPEGIO.DLL    JPEGIO.DL_     23    10/13/2000  10:19    44357  B48913B3
   JPN932.DLL    JPN932.DL_     26    11/24/1999  15:44     9263  354DF27F
   KANCALLS.DLL  KANCALLS.DL_   14    08/24/2000  11:33    78440  7131E05B
   KBDCALLS.DLL  KBDCALLS.DL_   27    11/15/2000  18:31     1024  FD43428F
   KERNEL.SDF    KERNEL.SD_     21    11/15/2000  16:51    59155  CA18682D
   KERNELD.SDF   KERNELD.SD_    21    11/15/2000  16:51    59147  E97AE9C8
   KKCBRDGE.EXE  KKCBRDGE.EX_   26    10/20/2000  15:43     8102  F48EA958
   KLONDIKE.EXE  KLONDIKE.EX_   15    11/23/1999  17:02   457912  136EC294
   KR.KBL        KR.KB_         26    10/12/2000  16:00      724  2CF66834
   KRNLBDEV.TDF  KRNLBDEV.TD_   26    11/15/2000  18:02     4232  16B37047
   KRNLBFS.TDF   KRNLBFS.TD_    26    11/15/2000  18:02     4793  53063297
   KRNLBLDR.TDF  KRNLBLDR.TD_   26    11/15/2000  18:02     5384  6520E2B6
   KRNLBPG.TDF   KRNLBPG.TD_    26    11/15/2000  18:02     3209  0C916192
   KRNLBSEL.TDF  KRNLBSEL.TD_   26    11/15/2000  18:02     2783  09883895
   KRNLBSEM.TDF  KRNLBSEM.TD_   26    11/15/2000  18:02     1792  96E89963
   KRNLBSM.TDF   KRNLBSM.TD_    27    11/15/2000  18:02     1196  4D39F15C
   KRNLBTK.TDF   KRNLBTK.TD_    26    11/15/2000  18:02    13005  AB5AB621
   KRNLBTOM.TDF  KRNLBTOM.TD_   27    11/15/2000  18:02     1012  E6448FFD
   KRNLBVDM.TDF  KRNLBVDM.TD_   26    11/15/2000  18:02    15570  DBD16ADF
   KRNLBVM.TDF   KRNLBVM.TD_    26    11/15/2000  18:02     5542  A673EA19
   KRNLDDEV.TDF  KRNLDDEV.TD_   26    11/15/2000  17:54     4232  F5FA3583
   KRNLDFS.TDF   KRNLDFS.TD_    26    11/15/2000  17:54     4734  8C333542
   KRNLDLDR.TDF  KRNLDLDR.TD_   26    11/15/2000  17:54     5387  37503BB2
   KRNLDPG.TDF   KRNLDPG.TD_    26    11/15/2000  17:54     3265  964C9AEB
   KRNLDSEL.TDF  KRNLDSEL.TD_   26    11/15/2000  17:54     2895  8253AD1E
   KRNLDSEM.TDF  KRNLDSEM.TD_   26    11/15/2000  17:54     1932  A308B5DC
   KRNLDSM.TDF   KRNLDSM.TD_    27    11/15/2000  17:54     1221  B449C6F0
   KRNLDTK.TDF   KRNLDTK.TD_    26    11/15/2000  17:54    13033  0D3F617B

   
                       FixPak Corrective Service levels and disk layouts  49


                    October 4, 2001 - Warp 4 FixPak XRJM015

   KRNLDTOM.TDF  KRNLDTOM.TD_   27    11/15/2000  17:54     1040  F60460A8
   KRNLDVDM.TDF  KRNLDVDM.TD_   26    11/15/2000  17:54    15795  E9D6E94B
   KRNLDVM.TDF   KRNLDVM.TD_    26    11/15/2000  17:54     5654  2825EB0E
   KRNLRDEV.TDF  KRNLRDEV.TD_   26    11/15/2000  17:11     4232  C5B483F5
   KRNLRFS.TDF   KRNLRFS.TD_    26    11/15/2000  17:11     4793  A729B211
   KRNLRLDR.TDF  KRNLRLDR.TD_   26    11/15/2000  17:11     5384  0E5C5AAA
   KRNLRPG.TDF   KRNLRPG.TD_    26    11/15/2000  17:11     3209  2CAD0A4E
   KRNLRSEL.TDF  KRNLRSEL.TD_   26    11/15/2000  17:11     2783  79FE2812
   KRNLRSEM.TDF  KRNLRSEM.TD_   26    11/15/2000  17:11     1792  E4675F66
   KRNLRSM.TDF   KRNLRSM.TD_    27    11/15/2000  17:11     1196  2CD94AC0
   KRNLRTK.TDF   KRNLRTK.TD_    26    11/15/2000  17:11    12921  4862FE17
   KRNLRTOM.TDF  KRNLRTOM.TD_   27    11/15/2000  17:11      984  7D8D4AD6
   KRNLRVDM.TDF  KRNLRVDM.TD_   26    11/15/2000  17:11    15405  13A549D9
   KRNLRVM.TDF   KRNLRVM.TD_    26    11/15/2000  17:11     5542  53DA5C5F
   LA.KBL        LA.KB_         26    10/12/2000  16:00      916  2E4A02A8
   LABEL.COM     LABEL.CO_      25    11/15/2000  20:53    33805  1C384F91
   LFAPI.DLL     LFAPI.DL_      25    10/06/2000  14:09    21178  EEE925A9
   LIBC.MSG      LIBC.MS_       26    10/12/2000  16:13     9590  B1A24E28
   LIBCM.DLL     LIBCM.DL_      16    11/22/1999  11:45   210916  5BC599EE
   LIBCN.DLL     LIBCN.DL_      20    11/22/1999  11:45    57340  66C00B04
   LIBCREG.MSG   LIBCREG.MS_    27    10/12/2000  16:13      760  522AA0EA
   LIBCS.DLL     LIBCS.DL_      17    11/22/1999  11:45   192386  7E2C4DCF
   LIBUNI.DLL    LIBUNI.DL_     21    10/12/2000  16:00    81372  C1127F47
   LINK386.EXE   LINK386.EX_    20    11/15/2000  20:53   154196  159B5661
   LMDLL.DLL     LMDLL.DL_      23    08/15/2000  08:34    76973  CFDB54B0
   LOCALE.DLL    LOCALE.DL_     20    10/12/2000  16:00   107901  6DE56502
   LOG.SYS       LOG.SY_        26    10/06/2000  21:09     7354  28E2E80E
   LOGDAEM.EXE   LOGDAEM.EX_    25    10/06/2000  14:47    30256  A2FC1B28
   LT.KBL        LT.KB_         26    10/12/2000  16:00     1972  8BEA4F3C
   LV.KBL        LV.KB_         26    10/12/2000  16:00     1404  E6AD152C
   MAHJONGG.EXE  MAHJONGG.EX_   15    11/23/1999  17:02   620095  8246E087
   MAKEINI.EXE   MAKEINI.EX_    23    10/19/2000  14:20    64460  D0C36B2D
   MAKETAGS.EX   MAKETAGS.EX_   26    11/23/1999  17:03     4272  5E748F07
   MAKETSF.EXE   MAKETSF.EX_    24    10/06/2000  21:10    51928  E3B9D125
   MAPTSF.CMD    MAPTSF.CM_     26    11/22/1999  11:25    16803  1E81489D
   MEM.EXE       MEM.EU_        24    11/15/2000  19:38    39716  875EE8D6
   MEM.EXE       MEM.EX_        24    11/15/2000  20:55    39828  64804291
   MIDI.SYS      MIDI.SY_       26    08/15/2000  08:11    26328  FA7AB750
   MIDIMCD.DLL   MIDIMCD.DL_    27    10/13/2000  10:14     4118  1D334B7A
   MIGRATE.EXE   MIGRATE.EX_    20    11/15/2000  21:18   181307  CFD609BB
   MINSTALL.EXE  MINSTALL.EX_   18    10/13/2000  10:52   191774  3CE73628
   MINXMRI.DLL   MINXMRI.DL_    26    11/14/2000  20:14     6930  93BAB864
   MINXOBJ.DLL   MINXOBJ.DL_    24    11/14/2000  19:31    31886  BD6028F9
   MIRRORS.DLL   MIRRORS.DL_    11    09/06/2000  12:44   444744  4D9369F8
   MK.KBL        MK.KB_         26    10/12/2000  16:00     1302  B00C6DC9
   MMODPTS.DLL   MMODPTS.DL_    16    10/13/2000  10:46   184022  12635668
   MMPARTS.DLL   MMPARTS.DL_     2    10/13/2000  10:45  1532232  EEF994D0
   MMPM.DLL      MMPM.DL_        3    10/13/2000  10:50   432003  CD8DD638
   MMPTMRI.DLL   MMPTMRI.DL_    19    10/13/2000  10:45   229394  8A550DA6
   MMSNIFF.DLL   MMSNIFF.DL_    24    07/20/2000  10:33    33298  3D8FA011
   MODE.COM      MODE.CO_       23    11/15/2000  20:49    64213  66D50587

   
                       FixPak Corrective Service levels and disk layouts  50


                    October 4, 2001 - Warp 4 FixPak XRJM015

   MONCALLS.DLL  MONCALLS.DL_   26    11/15/2000  18:31     5536  94DB689C
   MONCALLS.TDF  MONCALLS.TD_   27    11/15/2000  18:31     1139  4D67041C
   MORE.COM      MORE.CO_       25    11/15/2000  20:49    34823  9009088D
   MOUCALLS.DLL  MOUCALLS.DL_   26    11/15/2000  18:31     1024  DFB7DF37
   MPGIO.DLL     MPGIO.DL_      22    10/13/2000  10:20    59269  C5A5BB04
   MSG.DLL       MSG.DL_        27    11/15/2000  18:31      512  CCB1ED52
   MSGOTHIC.CMB  MSGOTHIC.CM_   27    10/20/2000  15:47     8028  0F64AB81
   MSMINCHO.CMB  MSMINCHO.CM_   27    10/20/2000  15:47     8028  72FD4446
   NAMEADD.EXE   NAMEADD.EX_    25    11/24/1999  13:10    23040  3DC869A2
   NAMECOPY.EXE  NAMECOPY.EX_   25    11/24/1999  13:10    23040  1C05214E
   NAMEDEL.EXE   NAMEDEL.EX_    25    11/24/1999  13:10    23040  65C869A3
   NAMEDSP.DLL   NAMEDSP.DL_    19    10/06/2000  15:20   123427  A1BC90DE
   NAMEEXT.EXE   NAMEEXT.EX_    25    11/24/1999  13:10    23040  9DC869A5
   NAMEFW.DLL    NAMEFW.DL_     21    10/06/2000  15:20    72312  C44B9D23
   NAMEMOD.EXE   NAMEMOD.EX_    25    11/24/1999  13:10    23040  4DC869A3
   NAMEMOVE.EXE  NAMEMOVE.EX_   25    11/24/1999  13:10    23040  2405214C
   NAMEREXX.DLL  NAMEREXX.DL_    7    10/06/2000  15:20   156291  8D3A66B4
   NAMEREXX.MSG  NAMEREXX.MS_   26    10/06/2000  15:20     4796  98E13002
   NAMPIPES.DLL  NAMPIPES.DL_   27    11/15/2000  18:31     1024  5FCAC780
   NL.KBL        NL.KB_         26    10/12/2000  16:00      954  431DC1DE
   NLS.DLL       NLS.DL_        27    11/15/2000  18:31      512  B00D8263
   NO.KBL        NO.KB_         26    10/12/2000  16:00      920  2555DC36
   NPXEMLTR.DLL  NPXEMLTR.DL_   25    11/15/2000  16:51    21812  BB9D2FB3
   NWIAPI.DLL    NWIAPI.DL_     26    11/15/2000  03:05    14770  3FA6E7D6
   OBJDATA.DLL   OBJDATA.DL_    25    01/04/2000  14:40    22465  7E05FDFA
   OREX.MSG      OREX2.MS_      26    09/06/2000  12:43    25123  B8057EEC
   OREXUTIL.DLL  ORXUTIL2.DL_   23    09/06/2000  12:43    41175  5BC71134
   OREXX.DLL     OREXX2.DL_     10    09/06/2000  12:43   490355  38E21035
   OREXXSC.DLL   OREXXSC2.DL_   25    09/06/2000  12:43    43858  63B71AD9
   OREXXSOM.DLL  OREXSOM2.DL_   24    09/06/2000  12:43    76878  6233875B
   OREXXWPS.DLL  OREXWPS2.DL_   26    09/06/2000  12:43     4002  7CF94B0B
   OS2CHAR.DLL   OS2CHAR.DL_    27    11/15/2000  18:31      512  DF6DE742
   OS2CHAR.TDF   OS2CHAR.TD_    26    11/15/2000  16:50    13889  D239119B
   OS2CHESS.EXE  OS2CHESS.EX_    8    11/23/1999  17:02   958145  A1C404AD
   OS2DASD.DMD   OS2DASD.DM_    24    08/15/2000  07:33    40910  CD699CB1
   OS2DUMP       OS2DUMP.___    26    11/15/2000  18:32    15101  EF76D04F
   OS2IM.DLL     OS2IM.DL_      20    10/19/2000  15:19    91829  6D754E6A
   OS2IMJP.DLL   OS2IMJP.DL_    25    10/19/2000  14:37    19890  740064F7
   OS2KRNL       OS2KRNL.___     4    11/15/2000  17:11   845682  4E21F1C2
   OS2KRNLD.SYM  OS2KRNLD.SY_   19    11/15/2000  17:53   189380  06EE45A7
   OS2KRNLR.SYM  OS2KRNLR.SY_   19    11/15/2000  17:11   167188  2C207A6F
   OS2KRNLR.TDF  OS2KRNLR.TD_   26    11/15/2000  17:11    21026  5EE5E808
   OS2LDR.MSG    OS2LDR.MS_     26    11/15/2000  18:28     8917  4CE65E84
   OS2MM.DLL     OS2MM.DL_      16    10/13/2000  10:52   219884  C79CFD28
   OS2SM.DLL     OS2SM.DL_      26    10/19/2000  14:20     1598  874F8605
   OS2UG.INF     OS2UG.IN_      11    11/13/2000  08:08   639827  2E2A2C5C
   OS2UGL        OS2UGL.___     26    10/12/2000  15:52    15616  42667255
   OSO001.437    OSO001.43_     21    11/14/2000  16:22   175350  6A0ECA34
   OSO001.MSG    OSO001.MS_     21    11/14/2000  16:22   177819  2DB2711D
   OSO001H.437   OSO001H.43_    21    11/14/2000  16:22   240252  4E6EFEAA
   OSO001H.MSG   OSO001H.MS_    21    11/14/2000  16:22   243340  554B5295

   
                       FixPak Corrective Service levels and disk layouts  51


                    October 4, 2001 - Warp 4 FixPak XRJM015

   OVERVIEW.INF  OVERVIEW.IN_    6    11/13/2000  08:09   485069  889A4A5B
   PARALLEL.PDR  PARALLEL.PD_   26    11/14/2000  20:21    15914  B0DA2C70
   PATCH.EXE     PATCH.EX_      24    11/15/2000  20:55    42653  6261F074
   PCMCIA.TBL    PCMCIA.TB_     26    04/14/2000  13:27     5114  F9E24825
   PDFSLA.EXE    PDFSLA.EX_     26    10/30/2000  11:26    24946  4DC7F32C
   PDUMPSYS.EXE  PDUMPSYS.EX_   24    10/06/2000  21:17    47165  E603B960
   PDUMPUSR.EXE  PDUMPUSR.EX_   24    10/06/2000  21:17    47163  FEE0EF9B
   PICV.DLL      PICV.DL_       25    10/19/2000  12:59    26200  59732B53
   PICVIEW.DLL   PICVIEW.DL_    26    10/19/2000  14:34    14370  5F2AA45F
   PICVIEW.EXE   PICVIEW.EX_    22    10/19/2000  14:34    95770  9E45E841
   PL.KBL        PL.KB_         26    10/12/2000  16:00      980  5B4C9089
   PL457.KBL     PL457.KB_      26    10/12/2000  16:00      882  F102688A
   PMATM.DLL     PMATM.DL_      16    04/12/2000  11:39   224343  15C73B97
   PMBIDI.DLL    PMBIDI.DL_     26    11/23/1999  20:11    13611  08D96136
   PMCHKDSK.DLL  PMCHKDSK.DL_   26    11/15/2000  20:55     7199  3CB6E0BF
   PMCHKDSK.EXE  PMCHKDSK.EX_   25    11/15/2000  20:55    33303  579A42DD
   PMCLIP.DLL    PMCLIP.DL_     26    10/19/2000  14:01    21253  99E1CE18
   PMCTL.MSG     PMCTL.MS_      27    10/19/2000  14:26      784  BEF5F817
   PMCTLS.DLL    PMCTLS.DL_      6    10/19/2000  21:02   587798  89320509
   PMCTLS.SYM    PMCTLS.SY_     24    10/19/2000  21:02    44660  85EA57A0
   PMDDE.DLL     PMDDE.DL_      25    10/19/2000  21:12    28314  9DD5314F
   PMDDEML.DLL   PMDDEML.DL_    24    10/19/2000  12:43    27814  81BE1B42
   PMDF.EXE      PMDF.EX_       16    10/06/2000  21:16   393388  A090947D
   PMDF.INF      PMDF.IN_       25    11/13/2000  08:09    29798  5273361E
   PMDFMSG.DLL   PMDFMSG.DL_    23    10/06/2000  18:58    44512  23174C27
   PMDRAG.DLL    PMDRAG.DL_     26    10/19/2000  13:50     1731  8C66B469
   PMFORMAT.DLL  PMFORMAT.DL_   26    11/15/2000  20:55    10240  48818EE9
   PMFORMAT.EXE  PMFORMAT.EX_   26    11/15/2000  20:55    17431  C30DD4D8
   PMGPI.DLL     PMGPI.DL_      15    10/19/2000  12:38   248446  EDA8C795
   PMGPI.TDF     PMGPI.TD_      26    10/19/2000  12:38    12338  16149677
   PMGRE.DLL     PMGRE.DL_      26    10/19/2000  12:35     2231  815A9F54
   PMGRE.TDF     PMGRE.TD_      27    10/19/2000  21:04     1062  0B13F07E
   PMMERGE.DLL   PMMERGE.DL_     3    10/19/2000  21:04  1268731  E52C528F
   PMMERGE.SYM   PMMERGE.SY_    20    10/19/2000  21:04   117508  573ED03C
   PMMLE.DLL     PMMLE.DL_      27    10/19/2000  14:25      673  2DEDB999
   PMMRGRES.DLL  PMMRGRES.DL_   20    10/19/2000  14:27   136704  7E947ED9
   PMNLS.DLL     PMNLS.DL_      25    10/20/2000  15:43    21611  98F88DEF
   PMNLSAX1.DLL  PMNLSAX1.DL_   26    10/19/2000  14:38     5618  C8E868FD
   PMNLSFD1.FDR  PMNLSFD1.FD_   22    10/10/2000  15:14    76608  7C5E5B7F
   PMNLSFD2.FDR  PMNLSFD2.FD_   26    10/10/2000  15:14    10892  F6EE12E7
   PMNLSFD3.FDR  PMNLSFD3.FD_   22    10/16/2000  09:45    64026  33791FE2
   PMNLSFEP.DLL  PMNLSFEP.DL_    6    10/19/2000  14:39    15017  243E13C5
   PMNLSFM.DLL   PMNLSFM.DL_    23    10/10/2000  15:14    37474  E5B71EE8
   PMNLSJP1.DLL  PMNLSJP1.DL_   26    10/19/2000  14:38    10592  2BC23CD9
   PMNLSJP2.DLL  PMNLSJP2.DL_   26    10/19/2000  14:38    10608  86F0E3A9
   PMNLSJP3.DLL  PMNLSJP3.DL_   26    10/19/2000  14:38    10594  55BDD7CC
   PMNLSKIT.DLL  PMNLSKIT.DL_   26    10/19/2000  14:37    24946  41BE3174
   PMNLSML1.DLL  PMNLSML1.DL_   26    10/19/2000  14:38     5312  E7A92B34
   PMNLSSSC.DLL  PMNLSSSC.DL_   26    10/19/2000  15:59     1536  515697EE
   PMNLSUN1.DLL  PMNLSUN1.DL_   26    10/19/2000  14:38     5506  CDA34D35
   PMNLSVIO.DLL  PMNLSVIO.DL_   26    10/19/2000  14:39    14413  7B4E7EC6

   
                       FixPak Corrective Service levels and disk layouts  52


                    October 4, 2001 - Warp 4 FixPak XRJM015

   PMPIC.DLL     PMPIC.DL_      23    10/19/2000  14:00    47206  CDF1F652
   PMPIC.TDF     PMPIC.TD_      27    10/19/2000  14:34      400  AAA165FB
   PMPRE.DLL     PMPRE.DL_      23    09/15/2000  15:58    46574  37B947EA
   PMPREJ.DLL    PMPREJ.DL_     22    10/20/2000  15:47    59478  7423C397
   PMPRINT.QPR   PMPRINT.QP_    26    11/14/2000  20:16    11911  C2F7A560
   PMREXX.EXE    PMREXX.EX_     23    10/06/2000  15:20    78885  B07D5380
   PMREXXIO.DLL  PMREXXIO.DL_   24    10/06/2000  15:20    49189  8D01B81D
   PMSDMRI.DLL   PMSDMRI.DL_    26    04/16/1999  15:37    15872  FA150359
   PMSDMRID.DLL  PMSDMRID.DL_   24    10/19/2000  14:23    13312  A91907D2
   PMSEEK.DLL    PMSEEK.DL_     26    11/15/2000  20:55    10273  4B8C83A0
   PMSEEK.EXE    PMSEEK.EX_     25    11/15/2000  20:55    44597  F01746F1
   PMSHAPI.DLL   PMSHAPI.DL_    26    10/19/2000  12:45     4549  84759933
   PMSHAPI.TDF   PMSHAPI.TD_    26    10/19/2000  21:04     6726  D941F764
   PMSHELL.EXE   PMSHELL.EX_    26    11/14/2000  18:48     6028  084C898C
   PMSHLTKT.DLL  PMSHLTKT.DL_   23    09/06/2000  12:45    44232  A1FD720F
   PMSPL.DLL     PMSPL.DL_      14    11/14/2000  20:16   319185  2079E699
   PMSPL.SYM     PMSPL.SY_      25    11/14/2000  20:16    32340  F1E4BB2B
   PMSPL.TDF     PMSPL.TD_      26    11/14/2000  17:58     4491  5E47698E
   PMSPOOL.EXE   PMSPOOL.EX_    26    11/14/2000  18:51     9590  5950C3D9
   PMTKT.DLL     PMTKT.DL_      26    09/06/2000  12:45    32720  B94E25CC
   PMUNIF.DLL    PMUNIF.DL_     23    10/19/2000  14:00    43823  519E4C46
   PMVDMH.DLL    PMVDMH.DL_     26    10/19/2000  21:13     6521  6D00A9C4
   PMVDMP.DLL    PMVDMP.DL_     23    10/19/2000  14:35    46269  18DB4BDA
   PMVDMP.TDF    PMVDMP.TD_     26    10/19/2000  21:13     2661  081AAC24
   PMVIOP.DLL    PMVIOP.DL_     22    10/19/2000  14:35    64306  B50671FD
   PMVIOP.SYM    PMVIOP.SY_     26    10/19/2000  14:35     7620  3DB39942
   PMVIOP.TDF    PMVIOP.TD_     26    10/19/2000  21:12     3551  263626CD
   PMWIN.DLL     PMWIN.DL_      26    10/19/2000  12:41    11264  341BF5B1
   PMWIN.TDF     PMWIN.TD_      26    10/19/2000  21:04     9567  0EC55C25
   PMWIN32.SDF   PMWIN32.SD_    24    10/19/2000  12:43   313392  B4B1035A
   PMWINX.DLL    PMWINX.DL_      8    10/19/2000  14:33   530843  A083BBEC
   PMWP.DLL      PMWP.DL_        1    11/15/2000  03:02  1063363  DB99A67A
   PMWP.SYM      PMWP.SY_       22    11/15/2000  03:02   103796  236720E9
   PMWP.TDF      PMWP.TD_       26    11/15/2000  03:02    13825  3CBA64E4
   PMWPMRI.DLL   PMWPMRI.DL_    23    11/14/2000  20:13    54823  988D9355
   PNP.DLL       PNP.DL_        24    11/14/2000  19:35    28297  9CB5FD75
   PNP.SYS       PNP.SY_        26    08/15/2000  08:13     2152  2CA5E480
   PNPMRI.DLL    PNPMRI.DL_     25    11/14/2000  20:18    31781  4BD5967E
   PO.KBL        PO.KB_         26    10/12/2000  16:00      926  623C72BA
   PORTPLUG.DLL  PORTPLUG.DL_   25    11/15/2000  03:06    26200  6C6ED257
   PPIBMJ.DLL    PPIBMJ.DL_     26    07/01/1999  10:39    17153  60FF4D2D
   PRINT.COM     PRINT.CO_      25    11/15/2000  20:49    34177  53DF8871
   PROCDUMP.DOC  PROCDUMP.DO_   26    11/22/1999  11:25    62998  5680E87C
   PROCDUMP.EXE  PROCDUMP.EX_   23    10/06/2000  21:17    66591  E1590C14
   PROG.DLL      PROG.DL_       22    10/16/2000  11:53    57865  D6B006D9
   PRPPESCP.DLL  PRPPESCP.DL_   25    07/01/1999  10:39    26329  F635CE0D
   PRTRLIST.DLL  PRTRLIST.DL_   25    11/15/2000  03:06    31840  03F61F1D
   PRTRMRI.DLL   PRTRMRI.DL_    24    11/14/2000  20:17    48736  A9276657
   PS55DG20.JFD  PS55DG20.J9_   12    12/30/2010  11:33   232645  8498A23B
   PS55DG20.JFD  PS55DG20.J7_   15    12/30/2010  10:46   232638  8D8CD13A
   PS55DG24.JFD  PS55DG24.J9_   13    12/30/2010  11:33   290151  51EE9351

   
                       FixPak Corrective Service levels and disk layouts  53


                    October 4, 2001 - Warp 4 FixPak XRJM015

   PS55DG24.JFD  PS55DG24.J7_    9    12/30/2010  10:46   290144  CD269C84
   PS55DG28.FDR  PS55DG28.FD_   25    10/16/2000  09:45    22096  85325F1E
   PS55DG28.JFD  PS55DG28.J9_   12    12/30/2010  11:33   338142  B7C59239
   PS55DG28.JFD  PS55DG28.J7_   10    12/30/2010  10:46   338135  658D8D94
   PS55DG32.FDR  PS55DG32.FD_   25    10/16/2000  09:45    24200  46CB45E5
   PS55DG32.JFD  PS55DG32.J9_    9    12/30/2010  11:33   417508  7C554460
   PS55DG32.JFD  PS55DG32.J7_   10    12/30/2010  10:46   417501  3DD1D867
   PS55DG36.FDR  PS55DG36.FD_   25    10/16/2000  09:45    27406  F061CC5B
   PS55DG36.JFD  PS55DG36.J9_    7    12/30/2010  11:33   476704  57A05BC9
   PS55DG36.JFD  PS55DG36.J7_    7    12/30/2010  10:46   476697  35C0BBA1
   PS55DM20.JFD  PS55DM20.J9_   14    12/30/2010  11:33   246715  3A3282F0
   PS55DM20.JFD  PS55DM20.J7_   14    12/30/2010  10:46   246708  D1855982
   PS55DM28.FDR  PS55DM28.FD_   25    10/16/2000  09:45    22594  3747AF53
   PS55DM28.JFD  PS55DM28.J9_   12    12/30/2010  11:33   374011  6346B118
   PS55DM28.JFD  PS55DM28.J7_   11    12/30/2010  10:46   374004  BF317B33
   PS55DM32.FDR  PS55DM32.FD_   25    10/16/2000  09:45    24216  0D129B4C
   PS55DM32.JFD  PS55DM32.J9_    9    12/30/2010  11:33   439775  4C79EFF8
   PS55DM32.JFD  PS55DM32.J7_    9    12/30/2010  10:46   439768  8124953A
   PS55DM36.FDR  PS55DM36.FD_   25    10/16/2000  09:45    27694  A6DD44D3
   PS55DM36.JFD  PS55DM36.J9_    7    12/30/2010  11:33   529686  508DA43C
   PS55DM36.JFD  PS55DM36.J7_    6    12/30/2010  10:46   529679  9DC16C77
   PS55DV12.JFD  PS55DV12.J9_   19    12/30/2010  14:57   118648  F2742844
   PS55DV12.JFD  PS55DV12.J7_   19    12/30/2010  11:29   118641  D222B568
   PS55DV14.JFD  PS55DV14.J9_   18    12/30/2010  14:57   151556  6A75AE5A
   PS55DV14.JFD  PS55DV14.J7_   18    12/30/2010  11:29   151549  4893EE37
   PS55GUI.FDR   PS55GUI.FD_    23    10/10/2000  15:14    56618  16E018BC
   PSFILES.EXE   PSFILES.EX_    26    11/15/2000  20:50    10229  540FEF64
   PSSDMON.EXE   PSSDMON.EX_    25    10/30/2000  11:25    41533  712DEA6E
   PSSEMS.EXE    PSSEMS.EX_     26    11/15/2000  20:50    11717  6273B150
   PSTAT.EXE     PSTAT.EX_      26    11/15/2000  20:50    14661  1DED2319
   PULSE.EXE     PULSE.EX_      25    11/15/2000  20:56    39997  30D46DBF
   PVDAPI.DLL    PVDAPI.DL_     26    10/30/2000  11:25    20398  5905FFC3
   QUECALLS.DLL  QUECALLS.DL_   27    11/15/2000  18:31     1024  D0C33A19
   QUECALLS.TDF  QUECALLS.TD_   26    11/15/2000  16:50     1299  C1001679
   RAS001.MSG    RAS001.MS_     26    10/06/2000  18:50    36365  23060024
   RASH.MSG      RASH.MS_       26    10/06/2000  18:50     5356  D036BBEB
   RC.EXE        RC.EX_         22    06/30/1999  16:27    88045  9140B3F2
   RCPP.EXE      RCPP.EX_       24    06/30/1999  16:27    47331  FCD4C815
   README.DBG    README.DB_     26    09/06/2000  12:44     2463  F82C4618
   RECOVER.COM   RECOVER.CO_    24    11/15/2000  20:56    46656  6A935154
   REFLOW.EX     REFLOW.EX_     26    11/23/1999  17:03     2867  B6379D3D
   REGCONV.EXE   REGCONV.EX_    24    11/24/1999  13:59    52758  F980E778
   REGEDIT2.EXE  REGEDIT2.EX_    5    11/24/1999  14:00   970752  A6DF77C0
   REGISTRY.DLL  REGISTRY.DL_   23    11/24/1999  13:02    81440  A24B145B
   REGISTRY.MSG  REGISTRY.MS_   27    11/24/1999  14:00      614  7349DF16
   REGISTRY.TDF  REGISTRY.TD_   27    11/24/1999  13:02      984  E7DBD05C
   REPLACE.EXE   REPLACE.EX_    24    11/15/2000  20:56    41584  6BF7418B
   RESTORE.EXE   RESTORE.EX_    11    11/15/2000  20:56    39584  E397821E
   REX.MSG       OREX1.MS_      26    09/06/2000  12:43    25123  9C8B4CB7
   REX.MSG       REX.MS_        26    09/06/2000  12:42     2865  6031D657
   REXX.DLL      CREXX1.DL_     17    09/06/2000  12:42   266031  41FA8B8E

   
                       FixPak Corrective Service levels and disk layouts  54


                    October 4, 2001 - Warp 4 FixPak XRJM015

   REXX.DLL      OREXX1.DL_     10    09/06/2000  12:43   490355  1A1B8CC6
   REXX.IMG      REXX.IM_       21    09/06/2000  12:42   283636  D71E799D
   REXXAPI.DLL   REXXAPI.DL_    25    09/06/2000  12:42    40995  1433F324
   REXXC.EXE     REXXC.EX_      26    09/06/2000  12:42     2758  D07F57FF
   REXXCRT.DLL   REXXCRT.DL_    21    09/06/2000  12:42    79348  C14ED1D8
   REXXINIT.DLL  REXXINIT.DL_   26    09/06/2000  12:42     8360  646F0EC0
   REXXSC.DLL    OREXXSC1.DL_   25    09/06/2000  12:43    43858  6095634E
   REXXSOM.DLL   OREXSOM1.DL_   24    09/06/2000  12:43    76878  F448D696
   REXXUTIL.DLL  REXXUTIL.DL_   21    09/06/2000  12:42    68119  4D4EA597
   REXXUTIL.DLL  ORXUTIL1.DL_   23    09/06/2000  12:43    41175  5BC74634
   REXXWPS.DLL   OREXWPS1.DL_   26    09/06/2000  12:43     4002  6B41A308
   RINSTPRN.EXE  RINSTPRN.EX_   17    11/14/2000  20:25   208804  4E3BE494
   RJAPPLET.EXE  RJAPPLET.EX_   26    11/14/2000  20:21    22702  1643BC1D
   RO.KBL        RO.KB_         26    10/12/2000  16:00      944  E33356F6
   RSPDDI.EXE    RSPDDI.EX_     25    11/15/2000  21:09    29753  B7264E20
   RSPDSPI.EXE   RSPDSPI.EX_    21    10/02/2000  15:46   143398  921C6111
   RSPIMRI.DLL   RSPIMRI.DL_    26    08/31/2000  13:16    17967  8981AFCF
   RSRV.EXE      RSRV.EX_       21    10/06/2000  15:20    78051  9929E708
   RU.KBL        RU.KB_         26    10/12/2000  16:00     1144  0E8C7DDF
   RU441.KBL     RU441.KB_      26    10/12/2000  16:00     1260  FB23F724
   RXVIDCFG.DLL  RXVIDCFG.DL_   26    09/15/2000  17:10    14741  A1B7AF07
   SBFILTER.DLL  SBFILTER.DL_   26    09/15/2000  17:13    14861  430E5704
   SCENTER.DLL   SCENTER.DL_    14    11/14/2000  20:22   294845  7B0F0FE7
   SD.KBL        SD.KB_         26    10/12/2000  16:00     1036  415E88FE
   SEAMLESS.DLL  SEAMLESS.DL_   24    10/19/2000  21:13    49167  F14FF519
   SECUTIL.DLL   SECUTIL.DL_    25    10/30/2000  11:25    21468  AE20F41C
   SEINST.EXE    SEINST.EX_     24    11/15/2000  20:54    48707  3C1FD1D0
   SEMAINT.EXE   SEMAINT.EX_    23    02/09/2001  14:46    69264  65B868AE
   SERIAL.PDR    SERIAL.PD_     26    11/14/2000  20:14    19170  B2A1EA14
   SESAPI.DLL    SESAPI.DL_     25    10/30/2000  11:24    24203  BC54FAF1
   SESDB.DLL     SESDB.DL_      25    10/30/2000  11:25    23411  60A112FA
   SESDD32.SYS   SESDD32.SY_    22    10/30/2000  11:26   118834  299C986B
   SESDMON.EXE   SESDMON.EX_    25    10/30/2000  11:25    41742  D047ED86
   SESMGR.DLL    SESMGR.DL_     26    11/15/2000  18:31     1536  6534B911
   SESMGR.TDF    SESMGR.TD_     26    11/15/2000  16:50     1877  4D4EBBF3
   SESRES.DLL    SESRES.DL_     26    10/30/2000  11:25    38672  0DD8DDDE
   SESSHELL.EXE  SESSHELL.EX_    9    10/30/2000  11:25    29805  86BACFB0
   SESSTART.EXE  SESSTART.EX_   26    10/30/2000  11:25    23431  C2B3BAF8
   SETBOOT.EXE   SETBOOT.EX_    26    11/15/2000  20:54    20912  DEB31CC6
   SETDEFV.CMD   SETDEFV.CM_    26    10/05/2000  13:50     1652  127ED995
   SF.KBL        SF.KB_         26    10/12/2000  16:00     1036  5CC5BB81
   SGMLPARS.DLL  SGMLPARS.DL_   23    11/15/2000  03:05    60416  E339B398
   SHELL.SDF     SHELL.SD_      25    11/15/2000  16:51    21279  130E0D65
   SHOWTODO.EX   SHOWTODO.EX_   26    11/23/1999  17:03     1222  E1C06C88
   SHPIINST.DLL  SHPIINST.DL_   23    10/19/2000  20:57    37304  5D86AF59
   SK.KBL        SK.KB_         26    10/12/2000  16:00     1008  CAB66A86
   SL.KBL        SL.KB_         26    10/12/2000  16:00      982  D1DE1E66
   SLDAPI.DLL    SLDAPI.DL_     25    10/30/2000  11:25    22441  90FEBB7C
   SOFTDRAW.DLL  SOFTDRAW.DL_   13    10/19/2000  12:32   416439  5D865DF2
   SOM.DLL       SOM.DL_        20    06/30/1999  16:33    92009  A7AC7A85
   SORT.EXE      SORT.EX_       25    11/15/2000  20:50    32015  43A989DD

   
                       FixPak Corrective Service levels and disk layouts  55


                    October 4, 2001 - Warp 4 FixPak XRJM015

   SPCHOBJ.DLL   SPCHOBJ.DL_     1    12/21/1997  01:27   132899  9000C8F7
   SPL1B.DLL     SPL1B.DL_      26    11/14/2000  17:58     7125  3D90C70A
   SPOOL.EXE     SPOOL.EX_      26    11/15/2000  21:02     6639  9FA734EC
   SPOOLCP.DLL   SPOOLCP.DL_    26    11/14/2000  18:05    10210  FF56BF98
   SQ.KBL        SQ.KB_         26    10/12/2000  16:00      824  77F9CFE8
   SR.KBL        SR.KB_         26    10/12/2000  16:00     1222  A12BB6D9
   SSM.DLL       SSM.DL_        26    10/06/2000  08:13     4118  C2CE804D
   SSMDD.SYS     SSMDD.SY_      13    10/06/2000  08:12    36813  2CB233BD
   STRACE.EXE    STRACE.EX_     23    11/15/2000  20:57    56023  5CC3A923
   STRACE.INF    STRACE.IN_     18    09/05/2000  18:14   153828  60F4A5FC
   SUBST.EXE     SUBST.EU_      26    11/15/2000  19:35     4520  7C232C41
   SUBST.EXE     SUBST.EX_      26    11/15/2000  20:49     4008  F831000F
   SV.KBL        SV.KB_         26    10/12/2000  16:00      946  9B897832
   SVMC.DLL      SVMC.DL_       20    10/13/2000  10:10    98391  E30AAAF8
   SVSH.DLL      SVSH.DL_       25    10/13/2000  10:11    23082  66D71003
   SW.DLL        SW.DL_         17    10/06/2000  08:15    66505  25805B3F
   SWITCHRX.CMD  SWITCHRX.CM_   26    09/06/2000  12:43     7928  13CA9FC1
   SYMB.PFM      SYM1.PF_       27    11/22/1999  11:22      679  EAD8E0BD
   SYSC.EXE      SYSC.EX_       22    10/10/2000  15:15    57546  0B37A3B0
   SYSCTBL.EXE   SYSCTBL.EX_    26    10/10/2000  15:15     7672  F8B166A2
   SYSDUMP.EXE   SYSDUMP.EX_    25    10/06/2000  21:17    28701  06967DF9
   SYSINST2.EXE  SYSINST2.EX_   19    02/09/2001  14:49   189360  0B0B3CF8
   SYSINSTX.COM  SYSINSTX.CO_   24    11/15/2000  20:50    40128  E2A0C5DD
   SYSLEVEL.EXE  SYSLEVEL.EX_   24    11/15/2000  20:52    44720  15F273D7
   SYSLEVEL.FPK  SYSLEVEL.FP_   27    01/19/2001  09:10      165  350DACF0
   SYSLEVEL.MSG  SYSLEVEL.MS_   26    03/09/2000  15:08     1474  B2771404
   SYSLOG.EXE    SYSLOG.EX_     25    10/06/2000  14:47    33288  C5937164
   SYSLOGPM.DLL  SYSLOGPM.DL_   24    10/06/2000  18:50    31644  B355B1D5
   SYSLOGPM.EXE  SYSLOGPM.EX_   19    10/06/2000  14:09   215355  D088C92D
   SYSMONO.FON   SYSMONO.FO_    26    10/19/2000  13:03    21294  C2FF1A9F
   SYSMONOI.FON  SYSMONOI.FO_   24    10/19/2000  14:00    35841  3D5546D6
   SYSSPLIT.CMD  SYSSPLIT.CM_   26    11/22/1999  11:25     3712  A30841C8
   TDFLST.CMD    TDFLST.CM_     26    11/22/1999  11:25    13564  7B5F3592
   TEDIT.EXE     TEDIT.EX_      25    11/15/2000  20:57     9390  CE8AEA7D
   TEDIT.HLP     TEDIT.HL_      26    11/15/2000  20:44    14597  9812BD16
   TESTCFG.SYS   TESTCFG.SY_    26    07/20/2000  09:53     9808  C02483BE
   TEXTCON1.EXE  TEXTCON1.EX_   24    11/23/1999  20:12    49011  5916B6E7
   TFFLST.CMD    TFFLST.CM_     26    11/22/1999  11:25     4638  E2FE15D0
   TH.KBL        TH.KB_         26    10/12/2000  16:00     1184  22232806
   TH190.KBL     TH190.KB_      26    10/12/2000  16:00     1184  3DAAA1D5
   TILEHK.DLL    TILEHK.DL_     24    11/23/1999  17:43    51829  E4F3C574
   TIMES.FON     TIMES.FO_      18    10/19/2000  13:03   166150  8B4CCD42
   TIMESI.FON    TIMESI.FO_     18    10/19/2000  12:59   181173  027007EB
   TNR.OFM       TNR.OF_        26    11/22/1999  11:22     6809  CD75154B
   TNR.PFB       TNR.PF_        17    11/22/1999  11:24   145785  BD3CBE3E
   TNR.PFM       TN1.PF_        26    11/22/1999  11:22     1103  4721CE38
   TNRB.OFM      TNRB.OF_       26    11/22/1999  11:22     6825  14C21108
   TNRB.PFB      TNRB.PF_       16    11/22/1999  11:24   148564  FD47E0FF
   TNRB.PFM      TNR1.PF_       26    11/22/1999  11:22     1112  60448943
   TNRBI.OFM     TNRBI.OF_      26    11/22/1999  11:22     6839  6B71C7B5
   TNRBI.PFB     TNRBI.PF_      16    11/22/1999  11:24   159652  79893739

   
                       FixPak Corrective Service levels and disk layouts  56


                    October 4, 2001 - Warp 4 FixPak XRJM015

   TNRBI.PFM     TNRB1.PF_      26    11/22/1999  11:22     1118  618A75CD
   TNRI.OFM      TNRI.OF_       26    11/22/1999  11:22     6830  23B85D9A
   TNRI.PFB      TNRI.PF_        4    11/22/1999  11:24   157010  5E813576
   TNRI.PFM      TNR2.PF_       26    11/22/1999  11:22     1114  526E659D
   TR.KBL        TR.KB_         26    10/12/2000  16:00      962  4F79408D
   TR440.KBL     TR440.KB_      26    10/12/2000  16:00     1042  DE3CC0BA
   TRACE.DOC     TRACE.DO_      26    09/05/2000  12:11    64057  95DDD40E
   TRACE.EXE     TRACE.EX_      24    11/15/2000  20:57    56064  D4BD1780
   TRACE.HLP     TRACE.HL_      25    11/15/2000  21:01    38870  81464A0D
   TRACEDLL.DLL  TRACEDLL.DL_   23    10/06/2000  21:11    46987  C2341404
   TRACEFMT.EXE  TRACEFMT.EX_   19    11/15/2000  21:01   232067  8F183FFD
   TRACEGET.EXE  TRACGET1.EX_   25    10/06/2000  21:10    29930  05569661
   TRACEGET.EXE  TRACEGET.EX_   25    10/06/2000  21:10    29930  05569661
   TRACEREF.INF  TRACEREF.IN_   13    11/13/2000  08:09  1391720  8CFE341D
   TRADEMBK.INF  TRADEMBK.IN_   26    11/13/2000  08:08     2364  9392A28D
   TRAPDUMP.EXE  TRAPDUMP.EX_   25    10/06/2000  21:17    30236  B9939AA7
   TRAPLOG.EXE   TRAPLOG.EX_    26    10/06/2000  21:17    28191  F269D507
   TRC0000.TFF   TRC0000.TF_    27    11/15/2000  17:11      189  78DB263E
   TRC0001.TFF   TRC0001.TF_    26    11/24/1999  13:02     1370  17F81D51
   TRC0003.TFF   TRC0003.TF_    27    11/15/2000  17:11     1503  79DD8690
   TRC0004.TFF   TRC0004.TF_    26    11/15/2000  17:11     4754  4562826C
   TRC0005.TFF   TRC0005.TF_    26    11/15/2000  17:11    49321  E063153B
   TRC0006.TFF   TRC0006.TF_    26    11/15/2000  17:11    12356  B055674E
   TRC0007.TFF   TRC0007.TF_    26    11/15/2000  19:58     3336  601FB047
   TRC0008.TFF   TRC0008.TF_    27    08/15/2000  07:29      544  44533ED2
   TRC0010.TFF   TRC0010.TF_    26    11/15/2000  16:50    13647  C63AD6DD
   TRC0012.TFF   TRC0012.TF_    27    11/15/2000  18:31     1247  4B138575
   TRC0016.TFF   TRC0016.TF_    26    11/15/2000  16:50     1673  8106FBAA
   TRC0017.TFF   TRC0017.TF_    26    11/15/2000  16:50     5561  28B3BD66
   TRC0018.TFF   TRC0018.TF_    26    11/15/2000  16:50    39488  6DC61365
   TRC006D.TFF   TRC006D.TF_    26    10/06/2000  09:16    24181  FB89BB28
   TRC00C0.TFF   TRC00C0.TF_    26    10/19/2000  21:04    15970  172D7C66
   TRC00C2.TFF   TRC00C2.TF_    26    10/19/2000  21:04    25994  38380A06
   TRC00C3.TFF   TRC00C3.TF_    26    10/19/2000  21:04     3984  496F4ABD
   TRC00C4.TFF   TRC00C4.TF_    26    10/19/2000  14:34      288  6225B2A4
   TRC00C5.TFF   TRC00C5.TF_     2    10/19/2000  12:38    32994  87067818
   TRC00C6.TFF   TRC00C6.TF_    26    11/14/2000  17:58     7146  F49C8681
   TRC0100.TFF   TRC0100.TF_    26    11/15/2000  17:11     7219  FB080949
   TRC0101.TFF   TRC0101.TF_     1    11/15/2000  17:11     7968  B4168FEE
   TRC0102.TFF   TRC0102.TF_    26    11/15/2000  17:11    29256  51C17755
   TRC0103.TFF   TRC0103.TF_    26    11/15/2000  17:11     9590  88F67449
   TRC0104.TFF   TRC0104.TF_    26    11/15/2000  17:11     5134  61087FB7
   TRC0105.TFF   TRC0105.TF_    26    11/15/2000  17:11    24421  FE711FDC
   TRC0106.TFF   TRC0106.TF_    26    11/15/2000  17:11     1549  F9365090
   TRC0107.TFF   TRC0107.TF_    26    11/15/2000  17:11     4516  9B2B5C4B
   TRC0108.TFF   TRC0108.TF_    26    11/15/2000  17:11     9505  42F6E19A
   TRC0109.TFF   TRC0109.TF_    26    11/15/2000  17:11     2535  CF7DB3E4
   TRC010A.TFF   TRC010A.TF_    21    11/15/2000  17:11     1130  33D8C181
   TRC0118.TFF   TRC0118.TF_    26    10/06/2000  15:17     2526  467E4B05
   TRC0119.TFF   TRC0119.TF_    26    10/06/2000  15:33     3786  6E0BF20C
   TRC012C.TFF   TRC012C.TF_    26    10/19/2000  21:13     5361  CD6B9471

   
                       FixPak Corrective Service levels and disk layouts  57


                    October 4, 2001 - Warp 4 FixPak XRJM015

   TRC012D.TFF   TRC012D.TF_    26    10/19/2000  21:12     7870  4DF5F2E1
   TRC012E.TFF   TRC012E.TF_    26    11/15/2000  03:02    32972  8DAC7F62
   TRCFORMT.DLL  TRCFORMT.DL_   25    11/15/2000  21:01    27015  35498A41
   TRCUST.EXE    TRCUST.EX_     22    11/15/2000  20:58    98773  23AAAF2A
   TREE.COM      TREE.CO_       25    11/15/2000  20:50    34153  10EA2D4E
   TRNSCALL.DLL  TRNSCALL.DL_   26    11/24/1999  15:44     8434  E7461CC3
   TRSPOOL.DOC   TRSPOOL.DO_    26    11/22/1999  11:25     6638  7C5EA5A2
   TRSPOOL.EXE   TRSPOOL1.EX_   25    10/06/2000  21:10    42054  66643F12
   TRSPOOL.EXE   TRSPOOL.EX_     5    10/06/2000  21:10    42054  66643F12
   TRSTOP.EXE    TRSTOP.EX_     26    10/06/2000  21:10    23486  4BEB79C7
   TRUETYPE.DLL  TRUETYPE.DL_   19    04/12/2000  11:40   128567  2661D3D5
   TW.KBL        TW.KB_         26    10/12/2000  16:00      780  416E74AD
   UA.KBL        UA.KB_         26    10/12/2000  16:00     1476  755F2EED
   UCDFS.DLL     UCDFS.DL_      26    09/05/2000  17:41    13776  6402AFAF
   UCDFS.MSG     UCDFS.MS_      26    09/05/2000  17:41     2269  CCDF3330
   UCONV.DLL     UCONV.DL_      25    10/12/2000  16:00    22819  5B2AEC7E
   UHPFS.DLL     UHPFS.DL_      21    10/06/2000  15:29   106000  53D5EAF6
   UK.KBL        UK.KB_         26    10/12/2000  16:00      816  0BA7B2C7
   UK168.KBL     UK168.KB_      26    10/12/2000  16:00      850  56B6D36E
   ULSACT01.MSG  ULSACT01.MS_   16    10/12/2000  15:52      907  CD788D41
   ULSCAU01.MSG  ULSCAU01.MS_   14    10/12/2000  15:52      899  5C21412F
   ULSDET01.MSG  ULSDET01.MS_    7    10/12/2000  15:52      903  A12B37BE
   ULSERR01.MSG  ULSERR01.MS_   26    10/12/2000  15:52     1967  A7B3FAC9
   UNDELETE.COM  UNDELETE.CO_   24    11/15/2000  21:01    36953  F81A6E76
   UNICODE.SYS   UNICODE.SY_    26    10/12/2000  16:00    20014  4983A6FF
   UNIKBD.DLL    UNIKBD.DL_     24    10/12/2000  16:00    28291  EDE015C1
   UNINSTAL.EXE  UNINSTAL.EX_   19    02/14/2001  10:57   102633  52833D08
   UNPACK.EXE    UNPACK.EX_     21    11/15/2000  21:10    75168  78784403
   UNPACK2.EXE   UNPACK2.EX_    22    11/15/2000  21:23    80080  C42D4D8C
   US.KBL        US.KB_         26    10/12/2000  16:00      774  F658131E
   USDV.KBL      USDV.KB_       26    10/12/2000  16:00      942  36966906
   USDVL.KBL     USDVL.KB_      26    10/12/2000  16:00      924  BBA45BD0
   USDVR.KBL     USDVR.KB_      26    10/12/2000  16:00      942  75AC2E83
   USERFDD.DLL   USERFDD.DL_    26    10/10/2000  15:14     7083  0F59B1EF
   USINTER.KBL   USINTER.KB_    26    10/12/2000  16:00     1032  BCA4C15F
   VBIOS.SYS     VBIOS.SY_      10    11/23/1999  12:44    10128  11CF068E
   VCMOS.SYS     VCMOS.SY_      26    11/23/1999  12:45     2272  43B68ECA
   VDMIMFEP.EXE  VDMIMFEP.EX_   26    10/19/2000  15:20     8192  B8A8AF42
   VDPMI.SYS     VDPMI.SY_      25    11/23/1999  12:46    30626  DE6D0B18
   VDPX.SYS      VDPX.SY_       26    11/23/1999  12:47    26322  81E975E0
   VIDEOCFG.DLL  VIDEOCFG.DL_   23    09/15/2000  16:08    38126  030B4FBC
   VIEW.EXE      VIEW.EX_       24    10/19/2000  14:35    33792  06DC2A7D
   VIEWDOC.EXE   VIEWDOC.EX_    24    10/19/2000  14:35    31999  A6A696B1
   VIOCALLS.DLL  VIOCALLS.DL_   26    10/19/2000  14:01     2048  E444AEF1
   VIOTBL.DCP    VIOTBL.DC_     24    10/12/2000  16:00   225355  4037089E
   VIOTBL.ISO    VIOTBL.IS_     23    10/12/2000  16:00   230105  26CF721C
   VKKC.SYS      VKKC.SY_       26    10/20/2000  15:43     7632  9691FEEC
   VMAN.DLL      VMAN.DL_       23    09/15/2000  22:04    46745  AD73BA5A
   VMANWIN.SYS   VMANWIN.SY_    26    07/10/2000  14:07     3040  C2F3E282
   VPIC.SYS      VPIC.SY_       26    11/23/1999  12:48     9942  C81F2E64
   VPICPARM.SYS  VPICPARM.SY_   26    11/23/1999  12:48      736  6F551DBA

   
                       FixPak Corrective Service levels and disk layouts  58


                    October 4, 2001 - Warp 4 FixPak XRJM015

   VTIMER.SYS    VTIMER.SY_     26    11/23/1999  12:48    10560  C0AF43F5
   VW32S.SYS     VW32S.SY_      26    11/23/1999  12:50    18338  52CBEA0A
   VWIN.SYS      VWIN.SY_       26    11/23/1999  12:49    27104  94A9C806
   WCFGMRI.DLL   WCFGMRI.DL_    26    11/14/2000  20:14     5670  EB4A7809
   WD24B.DSP     WD24B.DS_      26    09/05/2000  11:59    32662  6683B5CF
   WELCMMRI.DLL  WELCMMRI.DL_   26    11/14/2000  20:26    13897  CB2F66E7
   WINCFG.DLL    WINCFG.DL_     26    11/15/2000  03:03    13379  5D959672
   WINPRF.DLL    WINPRF.DL_     23    09/15/2000  16:25    36288  887CFDC5
   WPCLS.IMP     WPCLS.IM_       3    09/06/2000  12:42     8661  DA1CAFC2
   WPCOMET.DLL   WPCOMET.DL_    12    10/19/2000  14:28     8720  A9C60217
   WPCONFIG.DLL  WPCONFIG.DL_   15    11/14/2000  20:14   266404  CDFB8DBB
   WPCONMRI.DLL  WPCONMRI.DL_   24    11/14/2000  20:14    34352  C7465716
   WPDSACTV.EXE  WPDSACTV.EX_   26    11/14/2000  18:05    13955  AB0DF940
   WPDSINIT.EXE  WPDSINIT.EX_   25    11/14/2000  18:05    21803  3CE8517E
   WPDSRVP.DLL   WPDSRVP.DL_    26    11/14/2000  18:05    14194  8F0C425E
   WPHELP.HLP    WPHELP.HL_      4    02/24/2000  20:21  1049548  236D2BE0
   WPINET.DLL    WPINET.DL_     19    11/15/2000  03:10   117180  42DCEA66
   WPINSTAL.DLL  WPINSTAL.DL_   24    01/04/2000  15:52    29281  20901E92
   WPINTMRI.DLL  WPINTMRI.DL_   26    11/14/2000  20:21    11836  57AB15ED
   WPMSG.HLP     WPMSG.HL_      23    11/13/2000  08:01    69958  17589D2D
   WPNLS.DLL     WPNLS.DL_      23    11/14/2000  20:26    43676  01785CA2
   WPNLSMRI.DLL  WPNLSMRI.DL_   26    11/14/2000  20:26    17335  7F656C1F
   WPPRINT.DLL   WPPRINT.DL_     2    11/14/2000  19:32   364102  31DB91C4
   WPPRINT.HLP   WPPRINT.HL_    22    11/14/2000  20:15    96313  E76D9729
   WPPRTMRI.DLL  WPPRTMRI.DL_   22    11/14/2000  20:15    67513  CAB18491
   WPREXX.IMP    WPREXX.IM_     26    09/06/2000  12:42     6313  504B163F
   WPSH.IR       WPSH.IR_       22    11/14/2000  17:53   274823  FF04BFB7
   WPSINIT.WPS   WPSINIT.WP_    26    09/06/2000  12:42    15877  ACB11B19
   WPSINST.CMD   WPSINST.CM_    26    09/06/2000  12:42     2813  77FD1420
   WSLCALLS.DLL  WSLCALLS.DL_   20    08/24/2000  11:33    95560  1F02C08B
   WW.EXE        WW.EX_         26    07/16/1998  14:31    11377  F8082A19
   WWDLL.DLL     WWDLL.DL_      14    12/21/1997  01:29   276981  9F80E623
   WWHOOK.DLL    WWHOOK.DL_     23    12/21/1997  01:29    27230  5071DBC4
   XCOPY.EXE     XCOPY.EX_      23    11/15/2000  20:51    53008  1707C6A2
   XDF.MSG       XDF.MS_        26    11/15/2000  20:51     2155  62DC891A
   XDFCOPY.EXE   XDFCOPY.EX_    22    11/15/2000  20:51    89887  77F9B882
   XDFH.MSG      XDFH.MS_        4    11/15/2000  20:51     1113  4FA00DD2
   XIMACALL.DLL  XIMACALL.DL_   20    10/19/2000  14:40    92634  2944CE0C
   XIPSCALL.DLL  XIPSCALL.DL_   26    10/19/2000  16:00     4998  CF2EF3B2
   XPG00420.TBL  XPG00420.TB_   26    11/22/1999  12:17    27264  C8667C5C
   XPG00864.TBL  XPG00864.TB_    8    11/22/1999  12:17    27264  76725C6C
   XVIOCALL.DLL  XVIOCALL.DL_   26    10/20/2000  15:43     6829  ECF3E30C

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.2
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100

   
                       FixPak Corrective Service levels and disk layouts  59


                    October 4, 2001 - Warp 4 FixPak XRJM015

   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\
           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   INSTALL.EXE   INSTALL2.EX_   27    02/14/2001  10:57   423113  26ECADE0
   INSTALL.EXE   INSTALL1.EX_   27    05/11/1999  01:47   416477  651C75FC
   OS2LDR        OS2LDR.___     27    11/15/2000  18:06    45056  BEEF34A4
   RSPINST.EXE   RSPINST2.EX_   27    02/09/2001  14:50   470000  E0D7874A
   RSPINST.EXE   RSPINST1.EX_   27    05/11/1999  02:03   457152  48C940D3

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.3
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\
           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   
                       FixPak Corrective Service levels and disk layouts  60


                    October 4, 2001 - Warp 4 FixPak XRJM015


   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPDBUTL.DLL  APPDBUTL.DL_   27    02/25/2000  12:15    23529  4EAC16E2
   APPSTART.EXE  APPSTART.EX_   27    02/25/2000  12:15    33858  82711D28
   NCAPPUTL.EXE  NCAPPUTL.EX_   27    02/25/2000  12:15    14624  29FB65C8
   OS2LDR        OS2LDR.___     27    11/15/2000  18:06    45056  8EE0F6F1
   PMLOGON.EXE   PMLOGON.EX_    27    01/24/2000  11:20    40109  5D5B81C3
   PRNCFG.DLL    PRNCFG.DL_     27    01/24/2000  11:21    81090  2DBD657B
   TDESK.DLL     TDESK.DL_      27    01/25/2000  01:53     3909  E02D18EA
   TLOGOFF.EXE   TLOGOFF.EX_    27    01/25/2000  01:53     9581  388C409D
   TOBJECT.DLL   TOBJECT.DL_    27    01/25/2000  01:53     4970  44345678
   TSHUTDWN.EXE  TSHUTDWN.EX_   27    01/25/2000  01:53     8695  FEBAC1E2

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.4
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6120
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\
           ..\*
           ..\..\MMOS2
           ..\..\MMOS2\*
           ..\..\VT
           ..\..\VT\*
           ..\..\PSFONTS
           ..\..\PSFONTS\*
           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPSTART.EXE  APPSTART.EX_   28    03/22/2000  10:08    35022  D8F2F43F
   NCAPPUTL.EXE  NCAPPUTL.EX_   28    03/22/2000  10:08    21270  DAA7210D
   NCMONIT.DLL   NCMONIT.DL_    27    07/17/2000  14:14    55035  D88CEDED
   OS2LDR        OS2LDR.___     28    11/15/2000  18:06    45056  8EE0F6F1
   PMLOGON.EXE   PMLOGON.EX_    27    07/17/2000  15:34    57813  F02101DE
   TSHUTDWN.EXE  TSHUTDWN.EX_   27    02/15/2000  12:41    10795  F1099ADA

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.5

   
                       FixPak Corrective Service levels and disk layouts  61


                    October 4, 2001 - Warp 4 FixPak XRJM015

   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6120
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\MDOS\WINOS2
           ..\MDOS\WINOS2\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   COMM.DRV      COMM.DR_       28    12/02/1999  17:56     9552  292FB5F2
   DRVMAP.INF    DRVMAP.IN_     27    11/15/2000  20:51     7668  5E3D18C9
   GDI.EXE       GDI.EX_        28    12/02/1999  16:20   225776  8E4C9987
   IFGDI2VM.DRV  IFGDI2VM.DR_   28    09/15/2000  17:12    93136  726896FA
   ISGDI2VM.DRV  ISGDI2VM.DR_   28    09/15/2000  16:14    92048  174AB2C9
   MAIN.CPL      MAIN.CP_       28    12/02/1999  16:32   147680  00D43A80
   MMSOUND.DRV   MMSOUND.DR_    27    12/02/1999  16:48     3456  97C7C550
   OS2K386.EXE   OS2K386.EX_    28    12/02/1999  16:22    80306  CA98D240
   PROGMAN.EXE   PROGMAN.EX_    28    12/02/1999  16:29   115328  99CE07B6
   REGEDIT.HLP   REGEDIT.HL_    28    12/02/1999  17:59    22682  FE9A2CA5
   USER.EXE      USER.EX_       28    12/02/1999  16:42   281088  453EF87A
   WINFILE.EXE   WINFILE.EX_    28    12/02/1999  16:31   146960  210056E2
   WINSCLIP.DLL  WINSCLIP.DL_   28    12/02/1999  16:27    14848  663E0372
   WINSDDE.DLL   WINSDDE.DL_    28    12/02/1999  16:27    18432  A6B26F73
   WINSHELD.EXE  WINSHELD.EX_   28    12/02/1999  16:27    22528  F1801F6D
   WINSMSG.DLL   WINSMSG.DL_    28    12/02/1999  16:27    28441  ED6C8A9E


   
                       FixPak Corrective Service levels and disk layouts  62


                    October 4, 2001 - Warp 4 FixPak XRJM015

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.6
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6120
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\MDOS\WINJOS2
           ..\MDOS\WINJOS2\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   COMM.DRV      COMM.DR_       29    07/01/1999  10:44     9888  5A4885B8
   DRVMAP.INF    DRVMAP.IN_     28    11/15/2000  20:51     2968  51CE66F5
   GDI.EXE       GDI.EX_        28    07/01/1999  10:44   277568  8C0E1558
   IBMJ5577.DRV  IBMJ5577.DR_   29    07/01/1999  10:42    50784  0801F3FE
   IBMJ5587.DRV  IBMJ5587.DR_   29    07/01/1999  10:42    37008  FF47580A
   IFGDI2VM.DRV  IFGDI2VM.DR_   29    09/15/2000  17:12    93136  726896FA
   ISGDI2VM.DRV  ISGDI2VM.DR_   29    09/15/2000  16:14    92048  174AB2C9
   MAIN.CPL      MAIN.CP_       29    07/01/1999  10:44   181216  B6498F22
   MMSOUND.DRV   MMSOUND.DR_    28    07/01/1999  10:42     3456  054DEF79
   OS2K386.EXE   OS2K386.EX_    28    07/01/1999  10:44    82338  F93779B5
   PROGMAN.EXE   PROGMAN.EX_    29    07/01/1999  10:44   118336  4CCBDC15
   PS55DM24.JFD  PS55DM24.JF_   28    07/01/1999  10:46   302316  5A2A1A11
   PS55SGOT.JFD  PS55SGOT.JF_   29    07/01/1999  10:46    81024  64063D36
   PS55SMIN.JFD  PS55SMIN.JF_   29    07/01/1999  10:45    81152  6F6243C8
   REGEDIT.HLP   REGEDIT.HL_    29    07/01/1999  10:45    21951  9FB496B6

   
                       FixPak Corrective Service levels and disk layouts  63


                    October 4, 2001 - Warp 4 FixPak XRJM015

   USER.EXE      USER.EX_       28    07/01/1999  10:44   281040  D404304A
   WINFILE.EXE   WINFILE.EX_    29    07/01/1999  10:44   152560  71DD950A
   WINSCLIP.DLL  WINSCLIP.DL_   29    07/01/1999  10:44    14848  69F2D954
   WINSDDE.DLL   WINSDDE.DL_    29    07/01/1999  10:44    18432  09033887
   WINSHELD.EXE  WINSHELD.EX_   29    07/01/1999  10:44    22528  BB8D6BA2
   WINSMSG.DLL   WINSMSG.DL_    29    07/01/1999  10:44    28953  322A538B

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.7
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6120
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\DLL
           ..\DLL\*
           ..\..\WHEADS
           ..\..\WHEADS\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   WSGTO.DLL     WSGTO.DL_      29    08/24/2000  11:33    19221  7850465B
   WSLOGIC.DLL   WSLOGIC.DL_    29    08/24/2000  11:33   146146  CA8F6738

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.8
   Product name:  "IBM OS/2 Base Operating System"

   
                       FixPak Corrective Service levels and disk layouts  64


                    October 4, 2001 - Warp 4 FixPak XRJM015

   Standard Edition  4.00
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM015_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4010_
   System Id:  1000
   Component Id:  5639A6120
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

           ..\..\..\..\..\IBMLAN\RPL\BB10.JP\OS2
           ..\..\..\..\..\IBMLAN\RPL\BB20.JP\OS2

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   BXVSVGA2.DLL  BXVSVGA2.DL_   29    10/20/2000  15:43    30628  6A36FEED
   KEYB106.COM   KEYB106.CO_    29    07/01/1999  10:40    15728  E77E0047
   KEYB106.DCP   KEYB106.DC_    29    10/12/2000  16:13    53861  877FEFC2
   KEYBAX.COM    KEYBAX.CO_     29    07/01/1999  10:40    16632  25464465
   KEYBAX.DCP    KEYBAX.DC_     29    10/12/2000  16:13    39239  AB3057B2
   KEYBUS.DCP    KEYBUS.DC_     29    10/12/2000  16:13    39239  6317E175
   VDMAAT.SYS    VDMAAT1.SY_    29    11/23/1999  12:45    11465  5359C2B9
   VDMAPS2.SYS   VDMAPS21.SY_   29    11/23/1999  12:45    14329  C55F2401











   
                       FixPak Corrective Service levels and disk layouts  65


                    October 4, 2001 - Warp 4 FixPak XRJM015

   11.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 61MB     FixPak Archive/Backup for product with CSD level of
                  XRJ4000
   Up to 60MB     FixPak Archive/Backup for product with CSD level of
                  XRJ4010

   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.


   11.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE

   Warning: Make sure you read and understand the following before removing
   the Archive and Backup files and directories.

   You can recover the space used for FixPak Archive and Backup files as
   long as you understand that doing this prevents you from being able to
   backout to the previous Backup or Archive level. If it becomes necessary
   at a later time to backout a FixPak, the only way you can do this is to
   reinstall Warp.

   Do the following to delete the FixPak Backup and Archive files and remove
   the files used by CSF to keep track of what service has been applied to
   your system.

   1.  Delete every instance of the following files on your system
       (search every drive and every directory they contain).
       þ   LOGF0000.*   (can be OS2 or MPM)
       þ   LOGSTART.*   (can be OS2 or MPM)
       þ   LOGARCH.*    (can be OS2 or MPM)
       þ   CSF_*.*
       þ   FIXSTART
   2.  Delete the files in the FixPak Archive and Backup directories on
       your harddisk.
   3.  Remove the FixPak Archive and Backup directories with the RMDIR
       command.




   
                                                       Space Utilization  66


                    October 4, 2001 - Warp 4 FixPak XRJM015

   11.0.2 TRADEMARKS

   The following terms are trademarks of the International Business Machines
   Corporation in the United States or other countries or both:

   þ  IBM
   þ  OS/2
   þ  WorkSpace On-Demand

   Other company, product, and service names may be trademarks or service
   marks of others.









































   
                                                       Space Utilization  67
