<        Installation instructions for Warp 4 FixPak XRJM014















        

        
        



        October 24, 2000

        This FixPak makes the products it services Year 2000 ready
        
        Build level 14.044
        
        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 24, 2000 - Warp 4 FixPak XRJM014


        October 24, 2000 - Warp 4 FixPak XRJM014


















































   
                                                                    Page  ii


                   October 24, 2000 - Warp 4 FixPak XRJM014

   CONTENTS


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

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

     3.0 Installation Notes  . . . . . . . . . . . . . . . . . . . . . . . 3
       3.0.1 Audio CD does not play  . . . . . . . . . . . . . . . . . . . 3
       3.0.2 Out of memory or System error SYS0008 - FP13+   . . . . . . . 3
       3.0.3 Warp 4 Revision number changed  . . . . . . . . . . . . . . . 3
       3.0.4 Changes you may see due to source convergence   . . . . . . . 4
       3.0.5 Security Applications Work Around   . . . . . . . . . . . . . 4
       3.0.6 Cannot install on WSoD Release 2  . . . . . . . . . . . . . . 4
       3.0.7 New PopUps During FixPak 12 Install   . . . . . . . . . . . . 4
       3.0.8 Device Drivers removed from Fixpak  . . . . . . . . . . . . . 5
       3.0.9 Can't install Warp 4  . . . . . . . . . . . . . . . . . . . . 5
       3.0.10 Please use Fixtool f.143 or later  . . . . . . . . . . . . . 5
       3.0.11 OS2DUMP split into two versions  . . . . . . . . . . . . . . 5
       3.0.12 TRAP in ES16881$ after FP10 applied  . . . . . . . . . . . . 6
       3.0.13 System Sounds not working after FixPak applied   . . . . . . 6
       3.0.14 Using Display Recovery Choices   . . . . . . . . . . . . . . 7
       3.0.15 Installation of Java 1.1.4   . . . . . . . . . . . . . . . . 8
       3.0.16 DSPRES.DLL included in this FixPak   . . . . . . . . . . . . 8
       3.0.17 No products found  . . . . . . . . . . . . . . . . . . . . . 8
       3.0.18 Previous installation interrupted  . . . . . . . . . . . . . 9
       3.0.19 Unable to open Archive directory   . . . . . . . . . . . . . 9
       3.0.20 RC 932 doing CID install of Warp 4   . . . . . . . . . . . . 9
       3.0.21 Multimedia no longer selectable   . . . . . . . . . . . . . 11
       3.0.22 MMPARTS.DLL/USER.EXE popup during install   . . . . . . . . 11
       3.0.23 CSF0208 No products were found on the target ...    . . . . 11
       3.0.24 CSF0248 Archive path is shared between mismatched   . . . . 11
       3.0.25 CSF0249 Error opening or creating archive file.   . . . . . 11
       3.0.26 Printer installation process change   . . . . . . . . . . . 12
       3.0.27 Configuration Installation Distribution ( CID )   . . . . . 12

     4.0 Post Installation Notes  . . . . . . . . . . . . . . . . . . . . 13
       4.0.1 Enabling client updates to the WSOD 2.0 GRADD.MOD file   . . 13
       4.0.2 Print Screen SET parameter for APAR JR11837  . . . . . . . . 13
       4.0.3 New Message Box in fix for APAR JR12954  . . . . . . . . . . 14
       4.0.4 RAS file changes   . . . . . . . . . . . . . . . . . . . . . 14
       4.0.5 Setting IRQ9 processing in config.sys for VPIC.SYS   . . . . 15
       4.0.6 Windows printer drivers leave a zombie thread running  . . . 15
       4.0.7 APAR JR09494 (trap exiting WINOS2 with MWAVE audio)  . . . . 16
       4.0.8 SYS3170 installing Lotus SmartSuite 96   . . . . . . . . . . 16
       4.0.9 Intermittent hangs   . . . . . . . . . . . . . . . . . . . . 16

     5.0 New Function   . . . . . . . . . . . . . . . . . . . . . . . . . 17
     5.1 Intel's new SpeedStep  . . . . . . . . . . . . . . . . . . . . . 17
     5.2 New RAS Utilities added  . . . . . . . . . . . . . . . . . . . . 17
     5.3 Serviceability (RAS) Enhancements  . . . . . . . . . . . . . . . 17

   
                                                               Contents  iii


                   October 24, 2000 - Warp 4 FixPak XRJM014

     5.4 Querying file dates for files after Dec 31, 1999 in REXX   . . . 18
     5.5 Enhanced support for Workspace On-Demand   . . . . . . . . . . . 18
       5.5.1 PMLOGON user exits   . . . . . . . . . . . . . . . . . . . . 18
       5.5.2 Setup strings for public applications  . . . . . . . . . . . 21
       5.5.3 Command line options for TLOGOFF and TSHUTDWN  . . . . . . . 22
       5.5.4 PMLOGON No Progress Indicator option   . . . . . . . . . . . 22
       5.5.5 PMLOGON No System Modal Window option  . . . . . . . . . . . 23
     5.6 Euro Support   . . . . . . . . . . . . . . . . . . . . . . . . . 23
       5.6.1 Base OS/2 support  . . . . . . . . . . . . . . . . . . . . . 23
       5.6.2 Where Euro is not supported  . . . . . . . . . . . . . . . . 24
       5.6.3 Printing the Euro  . . . . . . . . . . . . . . . . . . . . . 25
     5.7 New Warp Registry Editor   . . . . . . . . . . . . . . . . . . . 25
     5.8 WorkSpace On Demand  . . . . . . . . . . . . . . . . . . . . . . 25
     5.9 IBM Open32   . . . . . . . . . . . . . . . . . . . . . . . . . . 25
     5.10 Graphics Adapter Device Drivers (GRADD)   . . . . . . . . . . . 26
     5.11 Joliet-2 support in CDFS.IFS  . . . . . . . . . . . . . . . . . 26
     5.12 New (improved) CHKDSK   . . . . . . . . . . . . . . . . . . . . 26
       5.12.1 Using the new CHKDSK  . . . . . . . . . . . . . . . . . . . 26
       5.12.2 CHKDSK log formatter  . . . . . . . . . . . . . . . . . . . 28
     5.13 Automated Trap Screen Logging   . . . . . . . . . . . . . . . . 29
       5.13.1 SUPPRESSPOPUPS  . . . . . . . . . . . . . . . . . . . . . . 29
       5.13.2 TRAPLOG   . . . . . . . . . . . . . . . . . . . . . . . . . 29
       5.13.3 TRAPDUMP  . . . . . . . . . . . . . . . . . . . . . . . . . 30
       5.13.4 SYSDUMP   . . . . . . . . . . . . . . . . . . . . . . . . . 30
     5.14 REXX New Fuction  . . . . . . . . . . . . . . . . . . . . . . . 31
     5.15 Other README files  . . . . . . . . . . . . . . . . . . . . . . 31

     6.0 Corrective Service Facility  . . . . . . . . . . . . . . . . . . 32
       6.0.1 Required CSF level   . . . . . . . . . . . . . . . . . . . . 32
       6.0.2 Where you can find CSF code  . . . . . . . . . . . . . . . . 32
       6.0.3 Creating FixPak diskettes  . . . . . . . . . . . . . . . . . 33
     6.1 Residual FixPak files from OS/2 2.11 or Warp 3   . . . . . . . . 33
     6.2 Read-Only files  . . . . . . . . . . . . . . . . . . . . . . . . 34
     6.3 SYSLEVEL file locations  . . . . . . . . . . . . . . . . . . . . 34
     6.4 Relocated OS/2 file support  . . . . . . . . . . . . . . . . . . 35

     7.0 Installation Process   . . . . . . . . . . . . . . . . . . . . . 37
     7.1 Before installation  . . . . . . . . . . . . . . . . . . . . . . 37
     7.2 Method 1: Install from booted OS/2 partition.    . . . . . . . . 37
     7.3 Method 2: Install from alternate bootable media  . . . . . . . . 38
     7.4 Additional Corrective Service Facility information   . . . . . . 39

     8.0 CSD level of SYSLEVEL.OS2  . . . . . . . . . . . . . . . . . . . 40
       8.0.1 New SYSLEVEL.FPK   . . . . . . . . . . . . . . . . . . . . . 41

     9.0 FixPak Corrective Service levels and disk layouts  . . . . . . . 42

     10.0 Space Utilization   . . . . . . . . . . . . . . . . . . . . . . 65
       10.0.1 Recovering FixPak ARCHIVE and BACKUP space  . . . . . . . . 65
       10.0.2 TRADEMARKS  . . . . . . . . . . . . . . . . . . . . . . . . 66


   
                                                                Contents  iv


                   October 24, 2000 - Warp 4 FixPak XRJM014

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

   Downloading the Service Fixes included in FixPak XRJM014 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
      XRJM014 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 24, 2000 - Warp 4 FixPak XRJM014

   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 24, 2000 - Warp 4 FixPak XRJM014

   3.0 INSTALLATION NOTES



   3.0.1 AUDIO CD DOES NOT PLAY

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

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

    Your CD should now be able to play CDs.


   3.0.2 OUT OF MEMORY OR SYSTEM ERROR SYS0008 - FP13+

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

   þ  SET JAVA_HIGH_MEMORY=1

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


   3.0.3 WARP 4 REVISION NUMBER CHANGED

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

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

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

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

   1. Open an OS/2 window.

   
                                                       Installation Notes  3


                   October 24, 2000 - Warp 4 FixPak XRJM014

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



   3.0.4 CHANGES YOU MAY SEE DUE TO SOURCE CONVERGENCE

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


   3.0.5 SECURITY APPLICATIONS WORK AROUND

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

   þ  FAKEISS=YES

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


   3.0.6 CANNOT INSTALL ON WSOD RELEASE 2

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


   3.0.7 NEW POPUPS DURING FIXPAK 12 INSTALL

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







   
                                                       Installation Notes  4


                   October 24, 2000 - Warp 4 FixPak XRJM014

   3.0.8 DEVICE DRIVERS REMOVED FROM FIXPAK

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


   3.0.9 CAN'T INSTALL WARP 4

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

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


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


   3.0.10 PLEASE USE FIXTOOL F.143 OR LATER

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

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


   3.0.11 OS2DUMP SPLIT INTO TWO VERSIONS

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

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

   
                                                       Installation Notes  5


                   October 24, 2000 - Warp 4 FixPak XRJM014

   not it has a PCI bus. All BIOS problems have been worked out.

   To reiterate, the problem occurs only on older hardware. If you are
   running a 486 or early Pentium (P60 or less), you may wish to use the
   non-PCI version located on the last fixpak diskette. If you are running a
   9595, you must use the non-PCI version located on the last fixpak
   diskette.

    If, after installing this FixPak, you encounter problems taking a
   standalone dump and your system fits description above, perform the
   following steps to install the non-PCI version of OS2DUMP located on last
   disk of this FixPak:

   1. Open an OS/2 window.
   2. Change to drive letter where OS/2 is installed.
   3. Enter "cd\" to get to the root directory.
   4. Enter OS/2 command "attrib -s -h -r os2dump" to unhide OS2DUMP.
   5. Enter "ren os2dump os2dump.pci"; save PCI version of OS2DUMP.
   6. Insert last disk of FixPak in drive A.
   7. Copy a:\os2dump
   8. Enter OS/2 command "attrib +r +s +h os2dump" to hide OS2DUMP.
   9. Reboot system.



   3.0.12 TRAP IN ES16881$ AFTER FP10 APPLIED

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

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


   Do this before you install the FixPak.


   3.0.13 SYSTEM SOUNDS NOT WORKING AFTER FIXPAK APPLIED

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

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


   
                                                       Installation Notes  6


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

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

      UNPACK source target

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


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



   3.0.14 USING DISPLAY RECOVERY CHOICES

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

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

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

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

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


   
                                                       Installation Notes  7


                   October 24, 2000 - Warp 4 FixPak XRJM014

   3.0.15 INSTALLATION OF JAVA 1.1.4

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


   3.0.16 DSPRES.DLL INCLUDED IN THIS FIXPAK

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


   3.0.17 NO PRODUCTS FOUND

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

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

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

      LOGF0000.OS2
      LOGSTART.OS2
      LOGARCH.OS2


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

      LOGF0000.MPM
      LOGSTART.MPM
      LOGARCH.MPM


   Also check for the following file:

      C:\CSF_SEL.000


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

   
                                                       Installation Notes  8


                   October 24, 2000 - Warp 4 FixPak XRJM014

   3.0.18 PREVIOUS INSTALLATION INTERRUPTED

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

     Files:
        FIXSTART
        IBMCSFLK.LST
        IBMCSFLK.CSF
        CSF_*

     Directory:
        IBMCSFLK


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


   3.0.19 UNABLE TO OPEN ARCHIVE DIRECTORY

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

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


   3.0.20 RC 932 DOING CID INSTALL OF WARP 4

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

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

         assume it's c:\tempwork


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

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



   
                                                       Installation Notes  9


                   October 24, 2000 - Warp 4 FixPak XRJM014

   4. Place FixPak disk 12 in A: and enter

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


   5. Place FixPak disk  8 in A: and enter

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


   6. Place FixPak disk 12 in A: and enter

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


   7. Place FixPak disk  9 in A: and enter

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


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

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


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

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

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







   
                                                      Installation Notes  10


                   October 24, 2000 - Warp 4 FixPak XRJM014

   3.0.21 MULTIMEDIA NO LONGER SELECTABLE

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


   3.0.22 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL

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


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

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

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


   3.0.24 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED

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

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



   3.0.25 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.

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

   
                                                      Installation Notes  11


                   October 24, 2000 - Warp 4 FixPak XRJM014

   This can also occur for Multi Media Presentation Manager/2 (MMPM). You
   would then need to delete the LOGF0000.MPM and LOGSTART.MPM files from
   the \MMOS2\INSTALL directory and possibly LOGARCH.MPM if it exists.


   3.0.26 PRINTER INSTALLATION PROCESS CHANGE

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


   3.0.27 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )

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




































   
                                                      Installation Notes  12


                   October 24, 2000 - Warp 4 FixPak XRJM014

   4.0 POST INSTALLATION NOTES



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

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

   For existing clients, edit the client's FIT file
   \IBMLAN\RPL\FITS\<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.


   4.0.2 PRINT SCREEN SET PARAMETER FOR APAR JR11837

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



   
                                                 Post Installation Notes  13


                   October 24, 2000 - Warp 4 FixPak XRJM014

   SET PM_PRINTSCREEN_ACTIVE_WINDOW=ON

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

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

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

   "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=OFF"

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


   4.0.3 NEW MESSAGE BOX IN FIX FOR APAR JR12954

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

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

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

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


   4.0.4 RAS FILE CHANGES

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

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

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

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


   
                                                 Post Installation Notes  14


                   October 24, 2000 - Warp 4 FixPak XRJM014

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



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

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

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

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


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

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


   4.0.6 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING

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

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

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

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

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

   þ  backgroundtasks=run_enum.exe,hpfbkg02.exe

   then restart WINOS2.

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

   
                                                 Post Installation Notes  15


                   October 24, 2000 - Warp 4 FixPak XRJM014

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



   4.0.7 APAR JR09494 (TRAP EXITING WINOS2 WITH MWAVE AUDIO)

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


   4.0.8 SYS3170 INSTALLING LOTUS SMARTSUITE 96

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

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

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


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


   4.0.9 INTERMITTENT HANGS

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

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

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











   
                                                 Post Installation Notes  16


                   October 24, 2000 - Warp 4 FixPak XRJM014

   5.0 NEW FUNCTION

   It is our policy not to include new function in FixPaks. However, as with
   any policy there may be exceptions. If any exception occurs in the
   future, we will communicate them to you in this section of the
   README.1ST.


   5.1 INTEL'S NEW SPEEDSTEP

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


   5.2 NEW RAS UTILITIES ADDED

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

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

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

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


   5.3 SERVICEABILITY (RAS) ENHANCEMENTS

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

   Other associated documentation may be found in:

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

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


   
                                                            New Function  17


                   October 24, 2000 - Warp 4 FixPak XRJM014

   5.4 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


   5.5 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND



   5.5.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:


   
                                                            New Function  18


                   October 24, 2000 - Warp 4 FixPak XRJM014

      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  19


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

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

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

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

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

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

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

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

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

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

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

   
                                                            New Function  20


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

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




   5.5.2 SETUP STRINGS FOR PUBLIC APPLICATIONS

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

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

       NCC_SETUP_POST=ICONPOS=10,10;


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

   The following KEYNAME values are permitted for setup strings:


   
                                                            New Function  21


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

       ICONFILE       filename         Sets the object's icon.

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

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


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

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


   5.5.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN

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

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


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


   5.5.4 PMLOGON NO PROGRESS INDICATOR OPTION

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




   
                                                            New Function  22


                   October 24, 2000 - Warp 4 FixPak XRJM014

   5.5.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION

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


   5.6 EURO SUPPORT

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



   5.6.1 BASE OS/2 SUPPORT

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

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

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


   The Euro character is added to these fonts.








   
                                                            New Function  23


                   October 24, 2000 - Warp 4 FixPak XRJM014

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


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

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





   5.6.2 WHERE EURO IS NOT SUPPORTED

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

   
                                                            New Function  24


                   October 24, 2000 - Warp 4 FixPak XRJM014

           Arial             (Windows TrueType)
           Courier New       (Windows TrueType)


   The Euro is not in the 437 (US English) or 863 (Canadian French)
   codepages.  You must use codepage 850 to get the Euro.  The Euro is not
   on the US keyboard.  You can use the US International (ux) keyboard
   instead.



   5.6.3 PRINTING THE EURO

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

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

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



   5.7 NEW WARP REGISTRY EDITOR

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


   5.8 WORKSPACE ON DEMAND

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


   5.9 IBM OPEN32

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





   
                                                            New Function  25


                   October 24, 2000 - Warp 4 FixPak XRJM014

   5.10 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)

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

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



   5.11 JOLIET-2 SUPPORT IN CDFS.IFS

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

   Joilet-3 format is not supported.



   5.12 NEW (IMPROVED) CHKDSK

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

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


   5.12.1 USING THE NEW CHKDSK

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

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

   Note: OS/2 Warp Install uses fast format.



   
                                                            New Function  26


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

     BASEDEV=CHKDSK.SYS


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

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

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

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

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

   This technique involves the following steps:

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



   
                                                            New Function  27


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

     Original IFS statement:

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

     New IFS statement:

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

     The CALL statement to use is:

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


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

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

     CHKDSK.COM
     CHKDSK32.DLL
     UHPFS.DLL


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


   5.12.2 CHKDSK LOG FORMATTER

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

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


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





   
                                                            New Function  28


                   October 24, 2000 - Warp 4 FixPak XRJM014

     message.txt
     msghdr.txt
     pmchklog.exe
     range.txt
     readme


   They should all have a date of 05/14/97 or later (May 14, 1997).

   This is a tool used by OS/2 service to format and view the new CHKDSK log
   entries.  There is no support for this tool. You are welcome to use it
   but if you have problems with it or do not understand the output DO NOT
   contact IBM for assistance as none will be provided.


   5.13 AUTOMATED TRAP SCREEN LOGGING

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

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


   5.13.1 SUPPRESSPOPUPS

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

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

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


   5.13.2 TRAPLOG

   The TRAPLOG command allows dynamic control of trap information logging.

   The command syntax is:

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



   
                                                            New Function  29


                   October 24, 2000 - Warp 4 FixPak XRJM014

   where:

   þ  x: specifies that trap information is to be logged in
       x:\POPUPLOG.OS2, x: being any partition drive letter.
   þ  NOLOG disables logging of trap information.
   þ  POPUPS enables the trap information pop-up message (SYS3175).
   þ  NOPOPUPS disables the trap information pop-up message.



   5.13.3 TRAPDUMP

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

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

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

   The command syntax is:

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


   where:

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



   5.13.4 SYSDUMP

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

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

   
                                                            New Function  30


                   October 24, 2000 - Warp 4 FixPak XRJM014

   The system behaves as if a fatal crash has occurred thus under rare
   circumstances data can be lost.

   The command syntax is:

          SYSDUMP [/NOPROMPT]


   where:

   þ  NOPROMPT allows the Dump to proceed without the prompt and response to
      message:

          "Do you want to force a system dump? (Y/N)"




   5.14 REXX NEW FUCTION

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


   5.15 OTHER README FILES

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

   File           Use

   README2        Problems fixed in each FixPak (APAR list)

   README.CID     Installing FixPaks via CID

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

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

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







   
                                                            New Function  31


                   October 24, 2000 - Warp 4 FixPak XRJM014

   6.0 CORRECTIVE SERVICE FACILITY



   6.0.1 REQUIRED CSF LEVEL

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

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

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


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


   6.0.2 WHERE YOU CAN FIND CSF CODE

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

   Source         How to access

   
                                             Corrective Service Facility  32


                   October 24, 2000 - Warp 4 FixPak XRJM014


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

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

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



   6.0.3 CREATING FIXPAK DISKETTES

   Use LOADDSKF.EXE to create the diskettes. For each disk image, place a
   2MB HD (1.44MB formatted) diskette in A:.

   Warning: DO NOT use a 1MB (720KB formatted) diskette because you might
   have problems trying to install this FixPak.

   For each diskette image in the FixPak, do the following:

   Enter LOADDSKF XRJM014.?DK A: /F  (? can be 1 through 9, A through Z).

   Label the diskette as

         FixPak XRJM014
   Corrective Service Diskette ?
          (CSF DISK ?)


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

        Examples:

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




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

   If the following is true:

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


   
                                             Corrective Service Facility  33


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

   On your Warp 4 boot drive:

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

   On the drive where Multimedia Presentation Manager is installed:

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

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

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

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


   6.2 READ-ONLY FILES

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

   Press the "OK" button.


   6.3 SYSLEVEL FILE LOCATIONS

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

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


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


   
                                             Corrective Service Facility  34


                   October 24, 2000 - Warp 4 FixPak XRJM014

   For \OS2\INSTALL\SYSLEVEL.OS2

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

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

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

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

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

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




   6.4 RELOCATED OS/2 FILE SUPPORT

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

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

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



















   
                                             Corrective Service Facility  35


                   October 24, 2000 - Warp 4 FixPak XRJM014

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


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

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


   Then copy that data into the USERDIRS.OS2 file.

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

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



















   
                                             Corrective Service Facility  36


                   October 24, 2000 - Warp 4 FixPak XRJM014

   7.0 INSTALLATION PROCESS



   7.1 BEFORE INSTALLATION

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

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

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


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

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

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

   Here are some additional notes:

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

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

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

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

   
                                                    Installation Process  37


                   October 24, 2000 - Warp 4 FixPak XRJM014

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

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

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

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

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

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

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

      The locked file driver is loaded.

             Processing locked files

             Processing complete


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


   7.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA

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

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



   
                                                    Installation Process  38


                   October 24, 2000 - Warp 4 FixPak XRJM014

   Here are some additional notes:

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

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

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

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


   7.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION

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

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





















   
                                                    Installation Process  39


                   October 24, 2000 - Warp 4 FixPak XRJM014

   8.0 CSD LEVEL OF SYSLEVEL.OS2

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

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

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

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


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

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


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

      \OS2\INSTALL\SERVICE.LOG


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

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

   The Operating System/2 Version is 4.50
   Revision 14.044


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

   Build Level: nn.nnn



   
                                               CSD level of SYSLEVEL.OS2  40


                   October 24, 2000 - Warp 4 FixPak XRJM014

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


   8.0.1 NEW SYSLEVEL.FPK

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

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





































   
                                               CSD level of SYSLEVEL.OS2  41


                   October 24, 2000 - Warp 4 FixPak XRJM014

   9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 14.044

   Product location on CSD:  A:\FIX\OS2.1
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM014_   (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:   XRJM014_   (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:   XRJM014_   (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  42


                   October 24, 2000 - Warp 4 FixPak XRJM014

      ..\..\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  99BC5AB1
   $JPNZN16.FNT  $JPNZN16.F7_   15    12/30/2010  17:04   185856  0E27A6CD
   $JPNZN24.FNT  $JPNZN24.F9_   12    12/30/2010  11:33   342528  E7833AFD
   $JPNZN24.FNT  $JPNZN24.F7_   12    12/30/2010  17:04   343040  21D1A67C
   AA.KBL        AA.KB_         26    05/02/2000  13:58     1200  65074FED
   AA470.KBL     AA470.KB_      26    05/02/2000  13:58     1212  FBCCA743
   ALIASFNT.EXE  ALIASFNT.EX_   21    07/10/2000  18:43    88368  F178E4B9
   ANSICALL.DLL  ANSICALL.DL_   26    07/10/2000  16:55      512  4CA3CCD4
   APPEND.EXE    APPEND.EU_     26    07/14/2000  11:02     7602  0FFA948E
   APPEND.EXE    APPEND.EX_     26    07/14/2000  15:49     7650  F9A31521
   ARACONV.EXE   ARACONV.EX_    23    11/23/1999  20:12    62151  F784F7D0
   ASIACOL.DLL   ASIACOL.DL_    17    05/02/2000  13:52   158758  1EC935A1
   ASSIGN.COM    ASSIGN.CU_     26    07/14/2000  11:03     2684  0EBD2846
   ASSIGN.COM    ASSIGN.CO_     26    07/14/2000  15:49     2742  28EA3967
   ATTRIB.EXE    ATTRIB.EX_     24    07/14/2000  15:50    37789  BE86FFB9
   AVIO.DLL      AVIO.DL_       22    06/27/2000  12:46    53921  5B3DFFFA
   BA.KBL        BA.KB_         26    05/02/2000  13:58      980  77A3A61A
   BACKUP.EXE    BACKUP.EX_     24    07/14/2000  15:57    35472  42F3B247
   BDBVH.DLL     BDBVH.DL_      25    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_     23    07/08/2000  16:33    34888  FF4E1312
   BDWPCLS.DLL   BDWPCLS.DL_    25    07/08/2000  16:32    20144  A5A0AE8A
   BE.KBL        BE.KB_         26    05/02/2000  13:58      972  44AE7FF0
   BG.KBL        BG.KB_         26    05/02/2000  13:58     1152  341749B5
   BG241.KBL     BG241.KB_      26    05/02/2000  13:58     1372  DDB8BDFE
   BKSCALLS.DLL  BKSCALLS.DL_   26    07/10/2000  16:55      512  EF05FB14
   BLDLEVEL.EXE  BLDLEVEL.EX_   23    07/10/2000  08:45    57842  74068786
   BMSCALLS.DLL  BMSCALLS.DL_   26    07/10/2000  16:55      512  77F73B15
   BR.KBL        BR.KB_         26    05/02/2000  13:58      932  63D9BF55
   BR274.KBL     BR274.KB_      26    05/02/2000  13:58      852  68C6FBB2
   BVHINIT.DLL   BVHINIT.DL_    26    07/10/2000  14:23    11158  9D660E41
   BVHMPA.DLL    BVHMPA.DL_     25    07/10/2000  14:04    15293  61735A62

   
                       FixPak Corrective Service levels and disk layouts  43


                   October 24, 2000 - Warp 4 FixPak XRJM014

   BVHVGA.DLL    BVHVGA.DL_     23    07/10/2000  14:23    31875  FC904E22
   BVHVGA2.DLL   BVHVGA2.DL_    23    11/24/1999  15:43    35409  F58C7DB6
   BVHWNDW.DLL   BVHWNDW.DL_    25    07/10/2000  14:04    16797  DF671B0D
   BVSCALLS.DLL  BVSCALLS.DL_   26    07/10/2000  16:55      512  0EB362F3
   BXVSCALL.DLL  BXVSVGA2.DL_   24    11/24/1999  15:43    30628  6BF11F5D
   BY.KBL        BY.KB_         26    05/02/2000  13:58     1292  FCDE138D
   CA.KBL        CA.KB_         26    05/02/2000  13:58     1214  4A184542
   CACHE.EXE     CACHE.EX_      25    05/03/2000  14:13    13870  C3988726
   CARDINFO.DAT  CARDINFO.DA_   26    06/27/2000  18:23    55282  5F387F5E
   CARDSYM.FON   CARDSYM.FO_    24    11/23/1999  17:43    60453  2FA044C7
   CCHMAIN.EXE   CCHMAIN.EX_    16    07/07/2000  21:56   199408  0D0A6D7C
   CCHUSER.DLL   CCHUSER.DL_    21    07/07/2000  21:55    63763  E1ACACE6
   CDFS.IFS      CDFS.IF_       24    05/03/2000  14:27    45165  F8BCC488
   CDFS.TDF      CDFS.TD_       26    05/03/2000  14:27     2113  75682068
   CDROM.TBL     CDROM.TB_      26    03/15/2000  09:36     4371  CF56BE53
   CF.KBL        CF.KB_         26    05/02/2000  13:58      956  D1C7A808
   CHGMON.EXE    CHGMON.EX_     26    07/10/2000  18:05     4260  E8552109
   CHKDSK.COM    CHKDSK.CO_     22    07/14/2000  15:50    70720  EDCC3456
   CHKDSK.SYS    CHKDSK.SY_     26    05/03/2000  14:14      795  3BACD8C8
   CHKDSK32.DLL  CHKDSK32.DL_   19    05/03/2000  14:25   139227  47EAD08B
   CHKDSK32.EXE  CHKDSK32.EX_   26    05/03/2000  14:14     6417  46D91C60
   CIDLOG.DLL    CIDLOG.DL_     24    01/04/2000  15:56    27312  835140F1
   CLDAPI.DLL    CLDAPI.DL_     25    01/04/2000  09:09    22217  B0DA1490
   CLIPOS2.EXE   CLIPOS2.EX_    25    07/08/2000  15:18    16411  25817A30
   CLOCK01.SYS   CLOCK01.SY_    26    06/17/2000  12:03     4560  C6F9EF4F
   CLOCK02.SYS   CLOCK02.SY_    26    06/17/2000  12:03     4318  253DF515
   CMD.EXE       CMD.EX_        16    07/14/2000  15:53   100620  049ECFE1
   CMDREF.INF    CMDREF.IN_      5    05/04/2000  20:27  1347235  072F41D4
   COMMAND.COM   COMMAND.CO_    23    07/14/2000  15:52    50342  1099B2B8
   COMP.COM      COMP.CO_       24    07/14/2000  15:53    35881  6DE1A9F0
   CONTROL.PM    CONTROL.PM_    26    07/10/2000  23:40     8486  257DE3FB
   COUNTRY.SYS   COUNTRY.SY_    25    01/21/2000  23:40    50947  191DA4B3
   COUR.OFM      COUR.OF_       26    11/22/1999  11:22     6163  8932E1ED
   COUR.PFB      COUR.PF_       17    11/22/1999  11:23   137111  48043987
   COUR.PFM      COU1.PF_       26    11/22/1999  11:22      674  EB14B168
   COURB.OFM     COURB.OF_      26    11/22/1999  11:22     6173  30530A2B
   COURB.PFB     COURB.PF_      17    11/22/1999  11:23   140829  503DA489
   COURB.PFM     COUR1.PF_      26    11/22/1999  11:22      679  1EF9C4BB
   COURBI.OFM    COURBI.OF_     26    11/22/1999  11:22     6187  0F59E5D1
   COURBI.PFB    COURBI.PF_     17    11/22/1999  11:23   136240  56421E00
   COURBI.PFM    COURB1.PF_     26    11/22/1999  11:22      685  A4390DF0
   COURI.OFM     COURI.OF_      26    11/22/1999  11:22     6178  1CEF133A
   COURI.PFB     COURI.PF_      14    11/22/1999  11:23   137394  715E75E2
   COURI.PFM     COUR2.PF_      26    11/22/1999  11:22      681  A6EEB6F7
   COURIER.FON   COURIER.FO_    22    07/10/2000  09:15    77826  E0FB5ECD
   COURIERI.FON  COURIERI.FO_   22    07/10/2000  09:10    86641  199F40E8
   CPG01256.TBL  CPG01256.TB_   26    11/22/1999  12:17    27264  A5C721BD
   CREXUTIL.DLL  CREXUTIL.DL_   21    03/27/2000  14:23    68119  4D4C346B
   CREXX.DLL     CREXX2.DL_     17    03/27/2000  14:23   266031  E0EEAA5F
   CYRIME.DLL    CYRIME.DL_     25    07/10/2000  08:54    21529  7252DB22
   CZ.KBL        CZ.KB_         26    05/02/2000  13:58     1014  0F79F2EC

   
                       FixPak Corrective Service levels and disk layouts  44


                   October 24, 2000 - Warp 4 FixPak XRJM014

   DDINSTAL.EXE  DDINSTAL.EX_   24    07/10/2000  23:58    52263  2322A5FB
   DE.KBL        DE.KB_         26    05/02/2000  13:58      958  D5F22494
   DE453.KBL     DE453.KB_      26    05/02/2000  13:58     1354  8F9775F6
   DEBUG.EXE     DEBUG.EU_      25    07/14/2000  11:06    27233  38132531
   DEBUG.EXE     DEBUG.EX_      25    07/14/2000  15:53    27985  9F4554CB
   DF_DEB.EXE    DF_DEB.EX_     20    07/07/2000  20:55   135989  8C2A8472
   DF_RET.EXE    DF_RET.EX_     20    07/07/2000  19:17   135957  3AAD3B9A
   DIBDRVR.DLL   DIBDRVR.DL_    26    07/10/2000  11:30     5627  7AA4F51B
   DISKCOMP.COM  DISKCOMP.CO_   23    07/14/2000  15:58    41697  F3B1A6BF
   DISKCOPY.COM  DISKCOPY.CO_   23    07/14/2000  15:58    46196  44610E98
   DISPLAY.DLL   DISPLAY.DL_    22    11/24/1999  15:47    59478  F0190E9E
   DIVE.DLL      DIVE.DL_       21    06/27/2000  12:39    69662  E42CBACC
   DK.KBL        DK.KB_         26    05/02/2000  13:58      928  F157DFAD
   DMISL.EXE     DMISL.EX_      20    02/16/2000  04:50   144918  69D48902
   DMQSPROF.DLL  DMQSPROF.DL_   23    04/10/2000  17:32    39033  4FFBE863
   DOSCALL1.DLL  DOSCALL1.DL_    8    07/10/2000  16:53   138029  6BC4EA29
   DOSCALL1.SYM  DOSCALL1.SY_   23    07/10/2000  16:53    43652  B63F91D9
   DOSCALL1.TDF  DOSCALL1.TD_   26    07/07/2000  19:16     5534  FC52CD30
   DOSKEY.COM    DOSKEY.CU_     26    07/14/2000  11:06     6243  8A55A9F7
   DOSKEY.COM    DOSKEY.CO_     26    07/14/2000  15:54     7272  6F78ADA3
   DOSKRNL       DOSKRNL.___    24    07/10/2000  16:53    31553  16159365
   DOSRFICO.DLL  DOSRFICO.DL_   24    03/27/2000  14:25    32332  BB49B571
   DSPIMRI.DLL   DSPIMRI.DL_    25    04/28/2000  12:34    17958  60B85ADA
   DSPINSTL.EXE  DSPINSTL.EX_   19    07/10/2000  14:11   175128  1BE89386
   DSPRES.DLL    DSPRES1.DL_    13    07/10/2000  09:10   376488  75B71E6A
   DSPRES.DLL    DSPRES.DL_     13    07/10/2000  09:10   376488  75CC5E6A
   DSPSUP.FON    DSPSUP.FO_     13    07/10/2000  09:10   370008  03B1FB3D
   DTRACE.DOC    DTRACE.DO_     24    11/22/1999  11:25    75371  5B1E5F89
   DTRACE.EXE    DTRACE1.EX_    22    02/16/2000  04:57    74850  2505CF97
   DTRACE.EXE    DTRACE.EX_     22    02/16/2000  04:57    74850  2505FA17
   E.EXE         E.EX_          21    07/08/2000  15:19    63383  F78722A1
   EAUTIL.EXE    EAUTIL.EX_     24    07/14/2000  15:54    38512  74F1CEC0
   EDLIN.COM     EDLIN.CO_      26    07/14/2000  15:54     8236  2A64BC0E
   EE.KBL        EE.KB_         26    05/02/2000  13:58      932  8E08DE2A
   EHXDLD.DLL    EHXDLD.DL_     25    07/08/2000  15:21    13861  EE67B6B2
   EHXDLMRI.DLL  EHXDLMRI.DL_   25    07/08/2000  15:20    13861  13564694
   EJECT.EXE     EJECT.EX_      25    01/21/2000  23:49    29746  F4FB28A3
   EL.KBL        EL.KB_         26    05/02/2000  13:58     1396  251D982A
   EL220.KBL     EL220.KB_      26    05/02/2000  13:58     1428  A7431047
   EL459.KBL     EL459.KB_      26    05/02/2000  13:58     1372  717E7982
   EPM.EX        EPM.E__        20    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_   23    02/15/2000  11:46    48608  5EB8D715
   ERRLOG.DLL    ERRLOG.DL_     20    02/15/2000  11:46    72806  D084DF84
   ERRTXT.DLL    ERRTXT.DL_     24    05/03/2000  18:26    26714  9793E5F2
   ES.KBL        ES.KB_         26    05/02/2000  13:58      920  DA5569AB
   ETKC603.DLL   ETKC603.DL_    17    11/23/1999  16:02   136124  B18E8724
   ETKE603.DLL   ETKE603.DL_     8    11/23/1999  16:02   767421  C1741876
   ETKR603.DLL   ETKR603.DL_    23    11/23/1999  16:02    36713  3E7A36BC
   ETKUCMS.DLL   ETKUCMS.DL_    19    11/23/1999  15:53    88156  B176E2E9

   
                       FixPak Corrective Service levels and disk layouts  45


                   October 24, 2000 - Warp 4 FixPak XRJM014

   EZP2MRI.DLL   EZP2MRI.DL_    22    07/08/2000  15:23    95774  93B417BB
   FDISK.COM     FDISK.CO_      20    07/14/2000  16:00   126139  7BEB5114
   FDISKPM.DLL   FDISKPM.DL_    26    07/14/2000  16:00    10805  F3AF4A79
   FDISKPM.EXE   FDISKPM.EX_    22    07/14/2000  16:00    89156  5F0A5DC3
   FDISKPMH.HLP  FDISKPMH.HL_   25    07/14/2000  16:00    18314  397AF15B
   FFCONFIG.DLL  FFCONFIG.DL_   25    02/15/2000  11:49    20551  0DDCCA24
   FFDUMP.DLL    FFDUMP.DL_     23    02/15/2000  12:52    41217  D917C351
   FFGUI.DLL     FFGUI.DL_      25    02/15/2000  22:05    19067  AEE6868C
   FFIPC.DLL     FFIPC.DL_      24    02/15/2000  11:49    27201  F844A592
   FFPCT.DLL     FFPCT.DL_      25    02/15/2000  11:49    21588  96F21588
   FFPROBE.DLL   FFPROBE.DL_    24    02/15/2000  12:19    24680  77EE9A33
   FFST.DLL      FFST.DL_       26    01/21/2000  14:58    11425  B9B2970A
   FFST.EXE      FFST.EX_       25    02/15/2000  12:52    32448  2486BC53
   FFSTCONF.EXE  FFSTCONF.EX_   18    02/15/2000  12:52   104505  120F8833
   FFSTPCT.EXE   FFSTPCT.EX_    21    02/15/2000  12:52   105143  721E9336
   FI.KBL        FI.KB_         26    05/02/2000  13:58      940  6AE2A1C8
   FILT.DLL      FILT.DL_       25    06/27/2000  12:41    22890  BFF132C4
   FIND.EXE      FIND.EX_       24    07/14/2000  15:54    31053  92BF101D
   FKA.DLL       FKA.DL_        25    11/22/1999  11:46    13997  66CDC379
   FNTCALLS.DLL  FNTCALLS.DL_   25    11/24/1999  15:42    22962  AB513336
   FNTPROCV.EXE  FNTPROCV.EX_   26    11/24/1999  15:42     3519  E286FA90
   FONTMEM.SYS   FONTMEM.SY_    26    11/24/1999  15:44     1466  70E8F829
   FORMAT.COM    FORMAT.CO_     22    07/14/2000  15:54    72064  E6A22189
   FR.KBL        FR.KB_         26    05/02/2000  13:58      950  37A63B57
   FSFILTER.SYS  FSFILTER.SY_   26    07/10/2000  16:53    12730  58B10F1B
   GLOCALE.DAT   GLOCALE.DA_     1    11/22/1999  11:47   362841  A5DCA1CA
   GLOCALE.EXE   GLOCALE.EX_    20    05/02/2000  14:17   145336  B93D8A45
   GLOCALE.HLP   GLOCALE.HL_    25    05/02/2000  14:17    34326  D7034224
   GLOCMRI.DLL   GLOCMRI.DL_    26    05/02/2000  14:17    11334  C28E71F1
   GRADD.SYS     GRADD.SY_      26    05/15/2000  16:23     2754  05B49EB1
   GRAFTABL.COM  GRAFTABL.CO_   26    07/14/2000  15:54     9628  9E2E55BA
   GRE2VMAN.DLL  GRE2VMAN.DL_   25    07/10/2000  19:17    18221  FDEC2658
   GSVDAEMN.EXE  GSVDAEMN.EX_   26    04/24/2000  13:13     4832  22EF48A6
   GSVINST.EXE   GSVINST.EX_    23    07/07/2000  18:58    34351  3C80D4F6
   HARDERR.EXE   HARDERR.EX_    26    07/10/2000  16:53    14377  3B26460E
   HDMON.EXE     HDMON.EX_      21    02/15/2000  22:10   112063  2A0CC6AF
   HELP.CMD      HELP.CM_       26    01/21/2000  09:57      586  D610F9DD
   HELPMGR.DLL   HELPMGR.DL_    14    07/10/2000  09:12   250157  0A77B4A7
   HELPMSG.EXE   HELPMSG.EX_    24    07/14/2000  15:55    37280  010360D9
   HELV.FON      HELV.FO_       18    07/10/2000  09:15   171252  537CF554
   HELV.OFM      HELV.OF_       26    11/22/1999  11:22     6793  9CE6E30D
   HELV.PFB      HELV.PF_       18    11/22/1999  11:23   120578  014F23CF
   HELV.PFM      HEL1.PF_       26    11/22/1999  11:22     1096  6F229952
   HELVB.OFM     HELVB.OF_      26    11/22/1999  11:22     6785  94469E8E
   HELVB.PFB     HELVB.PF_      18    11/22/1999  11:23   123085  0037C9CB
   HELVB.PFM     HELV1.PF_      26    11/22/1999  11:22     1089  84484E9F
   HELVBI.OFM    HELVBI.OF_     26    11/22/1999  11:22     6787  409F5DD9
   HELVBI.PFB    HELVBI.PF_     18    11/22/1999  11:23   124245  46A1595C
   HELVBI.PFM    HELVB1.PF_     26    11/22/1999  11:22     1087  06B4029D
   HELVI.FON     HELVI.FO_      17    07/10/2000  09:10   199523  03035DDD
   HELVI.OFM     HELVI.OF_      26    11/22/1999  11:22     6772  3B1431CD

   
                       FixPak Corrective Service levels and disk layouts  46


                   October 24, 2000 - Warp 4 FixPak XRJM014

   HELVI.PFB     HELVI.PF_      18    11/22/1999  11:24   123355  48DC6098
   HELVI.PFM     HELV2.PF_      26    11/22/1999  11:22     1079  A1475F00
   HG.CMB        HG.CM_         26    11/24/1999  15:47     8028  8CC1402C
   HGP.CMB       HGP.CM_        26    11/24/1999  15:47     3380  547E5EBD
   HKG-H90P.CMB  HKG-H90P.CM_   26    11/24/1999  15:47     3380  3D4ABC25
   HKGW590T.CMB  HKGW590T.CM_   26    11/24/1999  15:47     8028  1DFC6196
   HKGW5H90.CMB  HKGW5H90.CM_   26    11/24/1999  15:47     8028  F9429AAA
   HM-H90P.CMB   HM-H90P.CM_    26    11/24/1999  15:47     4044  B75C1752
   HM-W390T.CMB  HM-W390T.CM_   26    11/24/1999  15:47     8028  D663F923
   HM-W3H90.CMB  HM-W3H90.CM_   26    11/24/1999  15:47     8028  5AB47034
   HM.CMB        HM.CM_         26    11/24/1999  15:47     8028  7F66F4DC
   HMP.CMB       HMP.CM_        26    11/24/1999  15:47     4044  386BE227
   HPFS.IFS      HPFS.IF_       20    05/03/2000  14:11   141890  D62CBAE8
   HPFS.TDF      HPFS.TD_       26    05/03/2000  14:11     1620  A7A46569
   HPMGRMRI.DLL  HPMGRMRI.DL_   25    07/10/2000  18:01    18733  F4EA9648
   HR.KBL        HR.KB_         26    05/02/2000  13:58      982  9EB5B0AB
   HU.KBL        HU.KB_         26    05/02/2000  13:58     1006  52F83717
   HWDVPD.DLL    HWDVPD.DL_     25    02/15/2000  11:42    19476  A7D136A5
   IBM1004       IBM1004.___    26    05/02/2000  13:57     3584  5E34565D
   IBM1125       IBM1125.___    26    05/02/2000  13:57     4320  3BA1E748
   IBM1131       IBM1131.___    26    05/02/2000  13:57     4320  DDF5BED9
   IBM1140       IBM1140.___    26    05/02/2000  13:57     2816  2C2B3088
   IBM1141       IBM1141.___    26    05/02/2000  13:57     2784  75975006
   IBM1142       IBM1142.___    26    05/02/2000  13:57     2816  3BBF0AA1
   IBM1143       IBM1143.___    26    05/02/2000  13:57     2816  A9A92C47
   IBM1144       IBM1144.___    26    05/02/2000  13:57     2784  25F22BD4
   IBM1145       IBM1145.___    26    05/02/2000  13:57     2784  D07B2CFB
   IBM1146       IBM1146.___    26    05/02/2000  13:57     2816  78C1C6CD
   IBM1147       IBM1147.___    26    05/02/2000  13:57     2784  E3AF8CEB
   IBM1148       IBM1148.___    26    05/02/2000  13:57     2816  4FFC1F17
   IBM1250       IBM1250.___    26    05/02/2000  13:57     3552  A81ADB39
   IBM1251       IBM1251.___    26    05/02/2000  13:57     3328  D903688F
   IBM1252       IBM1252.___    26    05/02/2000  13:57     3552  6F8E7237
   IBM1253       IBM1253.___    26    05/02/2000  13:57     3552  944AD650
   IBM1254       IBM1254.___    26    05/02/2000  13:57     3552  9A43BE2B
   IBM1255       IBM1255.___    26    05/02/2000  13:57     3808  F89057CC
   IBM1256       IBM1256.___    26    05/02/2000  13:57     4320  87597164
   IBM1257       IBM1257.___    26    05/02/2000  13:57     3296  1722D1C9
   IBM813        IBM813.___     26    05/02/2000  13:57     3072  3BBA249D
   IBM850        IBM850.___     26    05/02/2000  13:57     4320  E4988E99
   IBM852        IBM852.___     26    05/02/2000  13:57     4608  44750204
   IBM857        IBM857.___     26    05/02/2000  13:57     4352  0542F856
   IBM859        IBM859.___     26    05/02/2000  13:57     4320  63BC5173
   IBM862        IBM862.___     26    05/02/2000  13:57     4576  D2481E83
   IBM864        IBM864.___     26    05/02/2000  13:58     4576  48AB6766
   IBM869        IBM869.___     26    05/02/2000  13:58     4320  65EC40B8
   IBM923        IBM923.___     26    05/02/2000  13:58     2784  558DE506
   IBM924        IBM924.___     26    05/02/2000  13:58     2784  A43F1673
   IBMOPTNS.DLL  IBMOPTNS.DL_   25    06/27/2000  18:23    22550  5921416E
   ICONEDIT.EXE  ICONEDIT.EX_   20    11/23/1999  17:02   163408  0E371980
   IL.KBL        IL.KB_         26    05/02/2000  13:58     1232  B0D7B300

   
                       FixPak Corrective Service levels and disk layouts  47


                   October 24, 2000 - Warp 4 FixPak XRJM014

   IMBRGDLL.DLL  IMBRGDLL.DL_   26    07/10/2000  18:05    10081  09D6ECF4
   IMBRIDGE.EXE  IMBRIDGE.EX_   25    07/10/2000  18:05    20669  B5ABA9E5
   IMDAEMON.DLL  IMDAEMON.DL_   26    07/10/2000  18:05    11362  C45C2842
   IMMON.EXE     IMMON.EX_      25    07/10/2000  18:06    10832  259ECBEF
   IMP.DLL       IMP.DL_        26    11/24/1999  15:47     9653  1B402F49
   IMREGIST.EXE  IMREGIST.EX_   26    07/10/2000  18:06     3460  6FEFA8A1
   IMSTART.EXE   IMSTART.EX_    26    07/10/2000  18:48     3636  39EA1516
   INSCFG32.DLL  INSCFG32.DL_   23    07/10/2000  23:41    32082  EAC53F04
   INSPGM32.DLL  INSPGM32.DL_   23    07/10/2000  23:41    41424  44B50AE7
   INST_DOS.EXE  INST_DOS.EX_   23    07/10/2000  11:27    39114  80A392E8
   IOPROC.DLL    IOPROC.DL_     23    06/27/2000  12:54    37880  AC4A08F1
   IS.KBL        IS.KB_         26    05/02/2000  13:58      940  E8D85C76
   IS458.KBL     IS458.KB_      26    05/02/2000  13:58      928  3404EF9E
   IT.KBL        IT.KB_         26    05/02/2000  13:58      876  90A1DED3
   IT142.KBL     IT142.KB_      26    05/02/2000  13:58      854  253BF832
   JIS90FNT.EXE  JIS90FNT.EX_   21    03/15/1999  17:05    66714  BCBF7817
   JOIN.EXE      JOIN.EU_       26    07/14/2000  11:07     4520  04C3C6C9
   JOIN.EXE      JOIN.EX_       26    07/14/2000  15:55     4520  CBD0748B
   JP.KBL        JP.KB_         26    05/02/2000  13:58     6374  38ACEF3D
   JPEGIO.DLL    JPEGIO.DL_     22    06/27/2000  16:19    44357  1BA9BFB5
   JPN932.DLL    JPN932.DL_     26    11/24/1999  15:44     9263  354DF27F
   KANCALLS.DLL  KANCALLS.DL_   20    08/24/2000  11:33    78440  7131E05B
   KBDCALLS.DLL  KBDCALLS.DL_   26    07/10/2000  16:55     1024  72434292
   KERNEL.SDF    KERNEL.SD_     20    07/07/2000  19:17    58993  74FF80C7
   KERNELD.SDF   KERNELD.SD_    20    07/07/2000  19:17    59138  2C9281B6
   KEYB.COM      KEYB-AX.CO_    25    08/27/1998  15:27    16632  4EDBC028
   KEYB.COM      KEYB-106.CO_   25    08/27/1998  15:27    15728  906FC08F
   KEYB.COM      KEYB-101.CO_   25    08/27/1998  15:27    15728  906FC08F
   KEYBOARD.DCP  KEYB-AX.DC_    26    05/02/2000  14:17    39239  2688D502
   KEYBOARD.DCP  KEYB-106.DC_   26    05/02/2000  14:17    53861  D842F745
   KEYBOARD.DCP  KEYB-101.DC_   26    05/02/2000  14:17    39239  C0E6B780
   KKCBRDGE.EXE  KKCBRDGE.EX_   26    11/24/1999  15:42     8102  39DEA958
   KLONDIKE.EXE  KLONDIKE.EX_   15    11/23/1999  17:02   457912  12934294
   KR.KBL        KR.KB_         26    05/02/2000  13:58      724  E6EAA187
   KRNLBDEV.TDF  KRNLBDEV.TD_   26    07/10/2000  16:00     4232  7CDA9AD7
   KRNLBFS.TDF   KRNLBFS.TD_    26    07/10/2000  16:00     4793  5CD0103E
   KRNLBLDR.TDF  KRNLBLDR.TD_   26    07/10/2000  16:00     5384  8782244C
   KRNLBPG.TDF   KRNLBPG.TD_    26    07/10/2000  16:00     3209  8A9C19B2
   KRNLBSEL.TDF  KRNLBSEL.TD_   26    07/10/2000  16:00     2783  70110B37
   KRNLBSEM.TDF  KRNLBSEM.TD_   26    07/10/2000  16:00     1792  E06E7BC5
   KRNLBSM.TDF   KRNLBSM.TD_    26    07/10/2000  16:00     1196  D1A91BC4
   KRNLBTK.TDF   KRNLBTK.TD_    26    07/10/2000  16:00    13005  A45621D8
   KRNLBTOM.TDF  KRNLBTOM.TD_   26    07/10/2000  16:00     1012  A5863267
   KRNLBVDM.TDF  KRNLBVDM.TD_   26    07/10/2000  16:00    15517  39CFDC95
   KRNLBVM.TDF   KRNLBVM.TD_    26    07/10/2000  16:00     5542  9A2CB5DF
   KRNLDDEV.TDF  KRNLDDEV.TD_   26    07/10/2000  15:58     4232  663C8458
   KRNLDFS.TDF   KRNLDFS.TD_    26    07/10/2000  15:58     4734  891E96E3
   KRNLDLDR.TDF  KRNLDLDR.TD_   26    07/10/2000  15:58     5387  D382095A
   KRNLDPG.TDF   KRNLDPG.TD_    26    07/10/2000  15:58     3265  E2E46F8E
   KRNLDSEL.TDF  KRNLDSEL.TD_   26    07/10/2000  15:58     2895  35458E49
   KRNLDSEM.TDF  KRNLDSEM.TD_   26    07/10/2000  15:58     1932  650C47E5

   
                       FixPak Corrective Service levels and disk layouts  48


                   October 24, 2000 - Warp 4 FixPak XRJM014

   KRNLDSM.TDF   KRNLDSM.TD_    26    07/10/2000  15:58     1221  054D8A90
   KRNLDTK.TDF   KRNLDTK.TD_    26    07/10/2000  15:58    13008  E98B518E
   KRNLDTOM.TDF  KRNLDTOM.TD_   26    07/10/2000  15:59     1040  5E29D36A
   KRNLDVDM.TDF  KRNLDVDM.TD_   26    07/10/2000  15:59    15742  7898A1FD
   KRNLDVM.TDF   KRNLDVM.TD_    26    07/10/2000  15:59     5654  59CC7975
   KRNLRDEV.TDF  KRNLRDEV.TD_   26    07/10/2000  15:50     4232  E9F2D284
   KRNLRFS.TDF   KRNLRFS.TD_    26    07/10/2000  15:50     4793  3FDD971E
   KRNLRLDR.TDF  KRNLRLDR.TD_   26    07/10/2000  15:50     5384  81D06414
   KRNLRPG.TDF   KRNLRPG.TD_    26    07/10/2000  15:50     3209  A664EFDE
   KRNLRSEL.TDF  KRNLRSEL.TD_   26    07/10/2000  15:50     2783  E819A385
   KRNLRSEM.TDF  KRNLRSEM.TD_   26    07/10/2000  15:50     1792  72C1A8D5
   KRNLRSM.TDF   KRNLRSM.TD_    26    07/10/2000  15:50     1196  35E9317D
   KRNLRTK.TDF   KRNLRTK.TD_    26    07/10/2000  15:50    12921  30DD5EBF
   KRNLRTOM.TDF  KRNLRTOM.TD_   26    07/10/2000  15:50      984  809231AB
   KRNLRVDM.TDF  KRNLRVDM.TD_   26    07/10/2000  15:50    15352  790125AD
   KRNLRVM.TDF   KRNLRVM.TD_    26    07/10/2000  15:50     5542  13A8D43D
   LA.KBL        LA.KB_         26    05/02/2000  13:58      916  B225248B
   LABEL.COM     LABEL.CO_      24    07/14/2000  15:59    33805  0E604F91
   LFAPI.DLL     LFAPI.DL_      25    02/15/2000  11:46    21178  EEECF8F9
   LIBC.MSG      LIBC.MS_       26    05/02/2000  14:17     9590  B119F828
   LIBCM.DLL     LIBCM.DL_      16    11/22/1999  11:45   210916  5BC599EE
   LIBCN.DLL     LIBCN.DL_      22    11/22/1999  11:45    57340  676A0B04
   LIBCREG.MSG   LIBCREG.MS_    26    05/02/2000  14:17      760  CCCAA0E1
   LIBCS.DLL     LIBCS.DL_      16    11/22/1999  11:45   192386  7E2C4E24
   LIBUNI.DLL    LIBUNI.DL_     21    05/02/2000  14:01    81372  726093C5
   LINK386.EXE   LINK386.EX_    19    07/14/2000  15:59   154196  3E28D055
   LMDLL.DLL     LMDLL.DL_      22    06/17/2000  12:06    76973  D720A4B0
   LOCALE.DLL    LOCALE.DL_     19    05/02/2000  13:57   107901  73E773EC
   LOG.SYS       LOG.SY_        26    02/16/2000  04:55     7354  28E2C663
   LOGDAEM.EXE   LOGDAEM.EX_    25    02/15/2000  11:46    30256  A1C5C328
   LT.KBL        LT.KB_         26    05/02/2000  13:58     1972  BE5BD080
   LV.KBL        LV.KB_         26    05/02/2000  13:58     1404  F33DA48B
   MAHJONGG.EXE  MAHJONGG.EX_   15    11/23/1999  17:02   620095  8246E087
   MAKEINI.EXE   MAKEINI.EX_    23    07/10/2000  17:46    64460  3B393DF1
   MAKETAGS.EX   MAKETAGS.EX_   26    11/23/1999  17:03     4272  5E748F07
   MAKETSF.EXE   MAKETSF.EX_    23    02/16/2000  04:57    51928  A3B9ACD3
   MAPTSF.CMD    MAPTSF.CM_     26    11/22/1999  11:25    16803  1E81489D
   MEM.EXE       MEM.EU_        24    07/14/2000  11:12    39716  822E38D6
   MEM.EXE       MEM.EX_        23    07/14/2000  16:00    39828  38804079
   MIDI.SYS      MIDI.SY_       25    04/24/2000  14:44    26328  FA7C0E60
   MIDIMCD.DLL   MIDIMCD.DL_    26    06/27/2000  16:17     4118  B6D2BA3C
   MIGRATE.EXE   MIGRATE.EX_    19    07/11/2000  00:07   181307  573C2065
   MINSTALL.EXE  MINSTALL.EX_   18    06/27/2000  18:24   191774  84ECD0F7
   MINXMRI.DLL   MINXMRI.DL_    26    07/08/2000  14:56     6930  50F805E0
   MINXOBJ.DLL   MINXOBJ.DL_    23    07/07/2000  20:02    31886  E9BEE7C0
   MIRRORS.DLL   MIRRORS.DL_     3    03/27/2000  14:24   444744  ED936544
   MK.KBL        MK.KB_         26    05/02/2000  13:58     1302  CBA8E098
   MMODPTS.DLL   MMODPTS.DL_    16    06/27/2000  13:31   185858  1075437E
   MMPARTS.DLL   MMPARTS.DL_     2    06/27/2000  16:33  1534588  11B3F0FC
   MMPM.DLL      MMPM.DL_       11    06/27/2000  16:21   432003  A8490C6C
   MMPTMRI.DLL   MMPTMRI.DL_    19    06/27/2000  18:22   229394  DC864537

   
                       FixPak Corrective Service levels and disk layouts  49


                   October 24, 2000 - Warp 4 FixPak XRJM014

   MMSNIFF.DLL   MMSNIFF.DL_    24    04/24/2000  15:41    33298  72526D0B
   MMSOUND.DRV   MMSOUND.DR_    26    12/02/1999  16:48     3456  97C7C550
   MODE.COM      MODE.CO_       23    07/14/2000  15:55    64213  A3D50589
   MONCALLS.DLL  MONCALLS.DL_   26    07/10/2000  16:55     5536  D4DB68A0
   MONCALLS.TDF  MONCALLS.TD_   26    07/10/2000  16:55     1139  21670426
   MORE.COM      MORE.CO_       24    07/14/2000  15:55    34823  38090ACD
   MOUCALLS.DLL  MOUCALLS.DL_   26    07/10/2000  16:55     1024  DFB80687
   MPGIO.DLL     MPGIO.DL_      21    06/27/2000  12:59    59269  56378FD8
   MSG.DLL       MSG.DL_        26    07/10/2000  16:55      512  CCB23BF2
   MSGOTHIC.CMB  MSGOTHIC.CM_   26    11/24/1999  15:47     8028  6464AB85
   MSMINCHO.CMB  MSMINCHO.CM_   26    11/24/1999  15:47     8028  1CFD444F
   NAMEADD.EXE   NAMEADD.EX_    25    11/24/1999  13:10    23040  3DD309A2
   NAMECOPY.EXE  NAMECOPY.EX_   25    11/24/1999  13:10    23040  1C05214E
   NAMECSSP.DLL  NAMECSSP.DL_   21    07/09/1997  12:29    61123  E0DF612A
   NAMEDEL.EXE   NAMEDEL.EX_    25    11/24/1999  13:10    23040  65C869A3
   NAMEDSP.DLL   NAMEDSP.DL_    18    07/10/2000  09:02   123427  CBBC9063
   NAMEEXT.EXE   NAMEEXT.EX_    25    11/24/1999  13:10    23040  9DC869A5
   NAMEFT.DLL    NAMEFT.DL_     21    07/09/1997  12:29    66274  19FE9C65
   NAMEFW.DLL    NAMEFW.DL_     20    07/10/2000  09:02    72312  044B8DC9
   NAMEINFO.DLL  NAMEINFO.DL_   22    07/09/1997  12:29    47973  685657A6
   NAMEINI.DLL   NAMEINI.DL_    21    07/09/1997  12:29    59027  FAF92BFE
   NAMEMOD.EXE   NAMEMOD.EX_    25    11/24/1999  13:10    23040  4DC869A3
   NAMEMOVE.EXE  NAMEMOVE.EX_   25    11/24/1999  13:10    23040  2405214C
   NAMEOSP.DLL   NAMEOSP.DL_    22    07/09/1997  12:29    52725  0DF4508B
   NAMEREXX.DLL  NAMEREXX.DL_   11    07/10/2000  09:02   156291  353A64C9
   NAMEREXX.MSG  NAMEREXX.MS_   26    07/10/2000  09:02     4796  08E12C22
   NAMPIPES.DLL  NAMPIPES.DL_   26    07/10/2000  16:55     1024  5FCAEED0
   NL.KBL        NL.KB_         26    05/02/2000  13:58      954  007E6878
   NLS.DLL       NLS.DL_        26    07/10/2000  16:55      512  B2828263
   NO.KBL        NO.KB_         26    05/02/2000  13:58      920  DD758193
   NPXEMLTR.DLL  NPXEMLTR.DL_   25    07/07/2000  19:17    21812  5B9D3016
   NWIAPI.DLL    NWIAPI.DL_     25    07/08/2000  16:52    14770  07CA2A39
   OBJDATA.DLL   OBJDATA.DL_    25    01/04/2000  14:40    22465  7E05FDFA
   OREX.MSG      OREX2.MS_      26    03/27/2000  14:23    25123  6D057F44
   OREXUTIL.DLL  ORXUTIL2.DL_   23    03/27/2000  14:23    41175  5BC7270C
   OREXX.DLL     OREXX2.DL_     10    03/27/2000  14:23   490355  38ED06D5
   OREXXSC.DLL   OREXXSC2.DL_   25    03/27/2000  14:24    43858  62426AD9
   OREXXSOM.DLL  OREXSOM2.DL_   23    03/27/2000  14:24    76878  363386FE
   OREXXWPS.DLL  OREXWPS2.DL_   26    03/27/2000  14:24     4002  08494B0A
   OS2CHAR.DLL   OS2CHAR.DL_    26    07/10/2000  16:55      512  C96DE747
   OS2CHAR.TDF   OS2CHAR.TD_    26    07/07/2000  19:16    13889  EAE1119B
   OS2CHESS.EXE  OS2CHESS.EX_    8    11/23/1999  17:02   958145  A1C40F4D
   OS2DASD.DMD   OS2DASD.DM_    24    04/24/2000  13:17    40910  33C9A31A
   OS2DUMP       OS2DUMP.___    25    07/10/2000  16:57    15101  6F76D8EB
   OS2IM.DLL     OS2IM.DL_      19    07/10/2000  18:03    91637  315CE0D8
   OS2IMJP.DLL   OS2IMJP.DL_    25    07/10/2000  18:03    19890  E90064F7
   OS2KRNL       OS2KRNL.___     4    07/10/2000  15:50   822344  868D9490
   OS2KRNLD.SYM  OS2KRNLD.SY_   18    07/10/2000  15:58   187940  9B1F6E39
   OS2KRNLR.SYM  OS2KRNLR.SY_   19    07/10/2000  15:50   165732  5588BAAB
   OS2KRNLR.TDF  OS2KRNLR.TD_   26    07/10/2000  15:50    17554  6D6BBB98
   OS2LDR.MSG    OS2LDR.MS_     26    07/07/2000  21:29     8915  32CCE952

   
                       FixPak Corrective Service levels and disk layouts  50


                   October 24, 2000 - Warp 4 FixPak XRJM014

   OS2MM.DLL     OS2MM.DL_      15    06/27/2000  18:24   219884  C169E695
   OS2NS.EXE     OS2NS.EX_      22    07/09/1997  12:38    44964  61548F04
   OS2SM.DLL     OS2SM.DL_      26    07/10/2000  11:49     1598  86ED7005
   OS2UG.INF     OS2UG.IN_      11    05/04/2000  20:33   639827  2E2A4AC4
   OS2UGL        OS2UGL.___     26    05/02/2000  13:58    15616  BC78F6F2
   OS2UGLG       OS2UGLG.___    26    07/07/1998  21:21     8928  AAAF5B4A
   OSO001.437    OSO001.43_     21    07/07/2000  16:05   175350  6A0EC769
   OSO001.MSG    OSO001.MS_     20    07/07/2000  16:05   177820  A08A7DDD
   OSO001H.437   OSO001H.43_    20    07/07/2000  16:05   240252  CE6EFE27
   OSO001H.MSG   OSO001H.MS_     7    07/07/2000  16:05   243353  49D67AF9
   OVERVIEW.INF  OVERVIEW.IN_    6    05/04/2000  20:34   485069  97CE4A5B
   PARALLEL.PDR  PARALLEL.PD_   25    07/08/2000  15:15    15914  6870D17A
   PATCH.EXE     PATCH.EX_      23    07/14/2000  16:01    42653  E261B56E
   PCMCIA.TBL    PCMCIA.TB_     26    04/14/2000  13:27     5114  A4E24825
   PDFSLA.EXE    PDFSLA.EX_     25    01/04/2000  09:09    24946  F929F32B
   PDUMPSYS.EXE  PDUMPSYS.EX_   24    02/16/2000  05:03    47165  E5FDAEB0
   PDUMPUSR.EXE  PDUMPUSR.EX_   24    02/16/2000  05:03    47163  FEB06F9B
   PICV.DLL      PICV.DL_       25    07/10/2000  09:11    26200  595D1553
   PICVIEW.DLL   PICVIEW.DL_    25    07/10/2000  18:00    14370  5F2B195F
   PICVIEW.EXE   PICVIEW.EX_    21    07/10/2000  18:00    95770  2CCF7872
   PL.KBL        PL.KB_         26    05/02/2000  13:58      980  505A72CD
   PL457.KBL     PL457.KB_      26    05/02/2000  13:58      882  1EF50BBD
   PMATM.DLL     PMATM.DL_      15    04/12/2000  11:39   224343  15C73B97
   PMBIDI.DLL    PMBIDI.DL_     25    11/23/1999  20:11    13611  08D96136
   PMCHKDSK.DLL  PMCHKDSK.DL_   26    07/14/2000  16:01     7199  355630BF
   PMCHKDSK.EXE  PMCHKDSK.EX_   24    07/14/2000  16:01    33303  BF9A42BF
   PMCLIP.DLL    PMCLIP.DL_     25    07/10/2000  11:29    21167  BCB5C85A
   PMCTL.MSG     PMCTL.MS_      26    07/10/2000  17:52      784  B975F83E
   PMCTLS.DLL    PMCTLS.DL_      6    07/10/2000  18:35   587734  9438D20C
   PMCTLS.SYM    PMCTLS.SY_     24    07/10/2000  18:35    44660  9170F84E
   PMDDE.DLL     PMDDE.DL_      24    07/10/2000  18:44    28236  45F6C418
   PMDDEML.DLL   PMDDEML.DL_    24    07/10/2000  08:55    27814  E9A81B42
   PMDF.EXE      PMDF.EX_        5    02/16/2000  05:02   393388  D9272FBB
   PMDF.INF      PMDF.IN_       25    05/04/2000  20:34    29798  70DB361E
   PMDFMSG.DLL   PMDFMSG.DL_    22    02/15/2000  22:09    44512  302395D0
   PMDRAG.DLL    PMDRAG.DL_     26    07/10/2000  09:00     1731  8C66A791
   PMFORMAT.DLL  PMFORMAT.DL_   26    07/14/2000  16:01    10240  E8818027
   PMFORMAT.EXE  PMFORMAT.EX_   25    07/14/2000  16:01    17431  BF2B0BF6
   PMGPI.DLL     PMGPI.DL_      15    07/10/2000  08:49   248446  EC68C77E
   PMGPI.TDF     PMGPI.TD_      26    07/10/2000  08:50    12338  BDBC9674
   PMGRE.DLL     PMGRE.DL_      26    07/10/2000  11:13     2231  A8FA9F54
   PMGRE.TDF     PMGRE.TD_      26    07/10/2000  18:36     1062  80050269
   PMMERGE.DLL   PMMERGE.DL_     3    07/10/2000  18:36  1268513  B0C83CE5
   PMMERGE.SYM   PMMERGE.SY_    20    07/10/2000  18:36   117492  7AF396C4
   PMMLE.DLL     PMMLE.DL_      26    07/10/2000  11:19      673  6C8DB99C
   PMMRGRES.DLL  PMMRGRES.DL_   20    07/10/2000  17:53   136704  7F3068D9
   PMNLS.DLL     PMNLS.DL_      25    11/24/1999  15:38    21611  98F8C144
   PMNLSAX1.DLL  PMNLSAX1.DL_   26    07/10/2000  18:04     5618  C9243CFD
   PMNLSFD1.FDR  PMNLSFD1.FD_   21    11/24/1999  15:39    76608  7C616E1F
   PMNLSFD2.FDR  PMNLSFD2.FD_   25    11/24/1999  15:40    10892  46EE0D81
   PMNLSFD3.FDR  PMNLSFD3.FD_   22    11/24/1999  15:40    64026  73791917

   
                       FixPak Corrective Service levels and disk layouts  51


                   October 24, 2000 - Warp 4 FixPak XRJM014

   PMNLSFEP.DLL  PMNLSFEP.DL_    6    07/10/2000  17:21    15017  24428E45
   PMNLSFM.DLL   PMNLSFM.DL_    23    11/24/1999  15:38    37474  E5B71FF0
   PMNLSJP1.DLL  PMNLSJP1.DL_   26    07/10/2000  18:04    10592  2BC326D9
   PMNLSJP2.DLL  PMNLSJP2.DL_   26    07/10/2000  18:04    10608  26F0E588
   PMNLSJP3.DLL  PMNLSJP3.DL_   26    07/10/2000  18:04    10594  55BDE6C1
   PMNLSKIT.DLL  PMNLSKIT.DL_   26    07/10/2000  18:03    24946  36BE3183
   PMNLSML1.DLL  PMNLSML1.DL_   26    07/10/2000  18:04     5312  EE7C2B34
   PMNLSSSC.DLL  PMNLSSSC.DL_   26    07/10/2000  18:47     1536  522881EE
   PMNLSUN1.DLL  PMNLSUN1.DL_   26    07/10/2000  18:04     5506  CDB24235
   PMNLSVIO.DLL  PMNLSVIO.DL_   25    07/10/2000  18:05    14413  7B55F946
   PMPIC.DLL     PMPIC.DL_      23    07/10/2000  09:11    47206  3DC5F653
   PMPIC.TDF     PMPIC.TD_      26    07/10/2000  11:28      400  AAA235A3
   PMPRE.DLL     PMPRE.DL_      22    07/10/2000  13:48    46574  37AC57EA
   PMPREJ.DLL    PMPREJ.DL_     22    11/24/1999  15:47    59478  74244E37
   PMPRINT.QPR   PMPRINT.QP_    25    07/08/2000  15:02    11911  7BF2E542
   PMREXX.EXE    PMREXX.EX_     23    07/10/2000  09:02    78885  6E5561CB
   PMREXXIO.DLL  PMREXXIO.DL_   24    07/10/2000  09:02    49189  74AE4FED
   PMSDMRI.DLL   PMSDMRI.DL_    26    04/16/1999  15:37    15872  FA150359
   PMSDMRID.DLL  PMSDMRID.DL_   26    07/10/2000  17:49    13312  A8E7FCD2
   PMSEEK.DLL    PMSEEK.DL_     26    07/14/2000  16:01    10273  9B34839C
   PMSEEK.EXE    PMSEEK.EX_     24    07/14/2000  16:01    44597  F0165A31
   PMSHAPI.DLL   PMSHAPI.DL_    26    07/10/2000  08:57     4549  396A9933
   PMSHAPI.TDF   PMSHAPI.TD_    26    07/10/2000  18:36     6726  0028D089
   PMSHELL.EXE   PMSHELL.EX_    26    07/07/2000  19:56     6028  FB27C744
   PMSHLTKT.DLL  PMSHLTKT.DL_   23    03/27/2000  14:25    44232  A1AEDC0F
   PMSPL.DLL     PMSPL.DL_      13    07/08/2000  15:01   319185  6D5DAE9C
   PMSPL.SYM     PMSPL.SY_      25    07/08/2000  15:01    32340  E29F8433
   PMSPL.TDF     PMSPL.TD_      26    07/07/2000  18:31     4491  8596CB44
   PMSPOOL.EXE   PMSPOOL.EX_    26    07/07/2000  18:31     9590  59510FB9
   PMTKT.DLL     PMTKT.DL_      25    03/27/2000  14:25    32720  B94DFE81
   PMUNIF.DLL    PMUNIF.DL_     22    07/10/2000  09:11    43823  31464C47
   PMVDMH.DLL    PMVDMH.DL_     26    07/10/2000  18:45     6521  6D00A9AE
   PMVDMP.DLL    PMVDMP.DL_     22    07/10/2000  18:01    46269  1AB9EBDA
   PMVDMP.TDF    PMVDMP.TD_     26    07/10/2000  18:45     2661  081A6964
   PMVIOP.DLL    PMVIOP.DL_     21    07/10/2000  18:01    64306  022A99AB
   PMVIOP.SYM    PMVIOP.SY_     26    07/10/2000  18:01     7620  11B39944
   PMVIOP.TDF    PMVIOP.TD_     26    07/10/2000  18:45     3551  2638056D
   PMWIN.DLL     PMWIN.DL_      26    07/10/2000  08:52    11264  34ABC9B1
   PMWIN.TDF     PMWIN.TD_      26    07/10/2000  18:36     9567  AD3254EE
   PMWIN32.SDF   PMWIN32.SD_    24    07/10/2000  08:54   313392  B4B1932E
   PMWINX.DLL    PMWINX.DL_      8    07/10/2000  17:59   530843  A0D1AEEC
   PMWP.DLL      PMWP.DL_        1    07/08/2000  16:39  1064287  77E82A78
   PMWP.SYM      PMWP.SY_       21    07/08/2000  16:39   103796  7394B87E
   PMWP.TDF      PMWP.TD_       26    07/08/2000  16:39    13825  69CAEA18
   PMWPMRI.DLL   PMWPMRI.DL_    22    07/08/2000  14:51    54823  2ED2A2BF
   PNP.DLL       PNP.DL_        24    07/07/2000  20:12    28297  9CBEE035
   PNP.SYS       PNP.SY_        26    04/28/2000  14:52     2152  ACA5FF85
   PNPMRI.DLL    PNPMRI.DL_     25    07/08/2000  15:07    31781  1C1D7173
   PO.KBL        PO.KB_         26    05/02/2000  13:58      926  8C3BB320
   PORTPLUG.DLL  PORTPLUG.DL_   25    07/08/2000  16:54    26200  E1E204DD
   PPIBMJ.DLL    PPIBMJ.DL_     25    08/27/1998  15:27    17153  60FF40AD

   
                       FixPak Corrective Service levels and disk layouts  52


                   October 24, 2000 - Warp 4 FixPak XRJM014

   PRINT.COM     PRINT.CO_      24    07/14/2000  15:55    34177  546EC871
   PROCDUMP.DOC  PROCDUMP.DO_    4    11/22/1999  11:25    62998  5680E87C
   PROCDUMP.EXE  PROCDUMP.EX_   23    02/16/2000  05:03    66591  CBF90C08
   PROG.DLL      PROG.DL_       21    07/10/2000  20:46    57864  C7F0DE22
   PRPPESCP.DLL  PRPPESCP.DL_   24    08/27/1998  15:27    26329  F6359C62
   PRTRLIST.DLL  PRTRLIST.DL_   24    07/08/2000  16:54    31840  2BE085C7
   PRTRMRI.DLL   PRTRMRI.DL_    23    07/08/2000  15:05    48736  24E17173
   PS55DG20.JFD  PS55DG20.J9_   14    12/30/2010  11:33   232645  0498A266
   PS55DG20.JFD  PS55DG20.J7_   14    12/30/2010  17:04   232638  8D967BBA
   PS55DG24.JFD  PS55DG24.J9_   13    12/30/2010  11:33   290151  51EEBDD1
   PS55DG24.JFD  PS55DG24.J7_    9    12/30/2010  17:04   290144  37C69C87
   PS55DG28.FDR  PS55DG28.FD_   25    11/24/1999  15:41    22096  851C091E
   PS55DG28.JFD  PS55DG28.J9_   12    12/30/2010  11:33   338142  B7C5E739
   PS55DG28.JFD  PS55DG28.J7_   10    12/30/2010  17:04   338135  659262D4
   PS55DG32.FDR  PS55DG32.FD_   25    11/24/1999  15:41    24200  E6CB447F
   PS55DG32.JFD  PS55DG32.J9_    9    12/30/2010  11:33   417508  26554461
   PS55DG32.JFD  PS55DG32.J7_   10    12/30/2010  17:04   417501  BDD1E211
   PS55DG36.FDR  PS55DG36.FD_   21    11/24/1999  15:41    27406  5AE1CC56
   PS55DG36.JFD  PS55DG36.J9_    7    12/30/2010  11:33   476704  57F55BC9
   PS55DG36.JFD  PS55DG36.J7_    7    12/30/2010  17:04   476697  35C14FB1
   PS55DM20.JFD  PS55DM20.J9_   14    12/30/2010  11:33   246715  9A3282AC
   PS55DM20.JFD  PS55DM20.J7_   14    12/30/2010  13:10   246708  C69A9982
   PS55DM28.FDR  PS55DM28.FD_   25    11/24/1999  15:40    22594  8747ADA0
   PS55DM28.JFD  PS55DM28.J9_   11    12/30/2010  11:33   374011  B846B118
   PS55DM28.JFD  PS55DM28.J7_   11    12/30/2010  17:04   374004  0F317C69
   PS55DM32.FDR  PS55DM32.FD_   24    11/24/1999  15:41    24216  B7129B35
   PS55DM32.JFD  PS55DM32.J9_    9    12/30/2010  11:33   439775  F679EFF8
   PS55DM32.JFD  PS55DM32.J7_    9    12/30/2010  17:04   439768  8ACF153A
   PS55DM36.FDR  PS55DM36.FD_   24    11/24/1999  15:41    27694  9BB244D3
   PS55DM36.JFD  PS55DM36.J9_    7    12/30/2010  11:33   529686  A58DB43C
   PS55DM36.JFD  PS55DM36.J7_    6    12/30/2010  17:04   529679  B1166C77
   PS55DV12.JFD  PS55DV12.J9_   18    12/30/2010  14:57   118648  F24B8844
   PS55DV12.JFD  PS55DV12.J7_   18    12/30/2010  11:29   118641  D24D3568
   PS55DV14.JFD  PS55DV14.J9_   17    12/30/2010  14:57   151556  6FC5AE5A
   PS55DV14.JFD  PS55DV14.J7_   17    12/30/2010  11:29   151549  48944337
   PS55GUI.FDR   PS55GUI.FD_    22    11/24/1999  15:42    56618  56E00B21
   PSFILES.EXE   PSFILES.EX_    26    07/14/2000  15:56    10229  68D9A071
   PSSDMON.EXE   PSSDMON.EX_    24    01/04/2000  12:47    41533  C52DEBF9
   PSSEMS.EXE    PSSEMS.EX_     26    07/14/2000  15:56    11717  AF8742D6
   PSTAT.EXE     PSTAT.EX_      25    07/14/2000  15:56    14661  9BD8E195
   PULSE.EXE     PULSE.EX_      24    07/14/2000  16:01    39997  BAD46DBE
   PVDAPI.DLL    PVDAPI.DL_     25    01/04/2000  09:09    20398  59045AD3
   QUECALLS.DLL  QUECALLS.DL_   26    07/10/2000  16:55     1024  D0C33C8E
   QUECALLS.TDF  QUECALLS.TD_   26    07/07/2000  19:16     1299  077B6A31
   RAS001.MSG    RAS001.MS_     25    02/15/2000  22:01    36365  E3060039
   RASH.MSG      RASH.MS_       26    02/15/2000  22:01     5356  D03C566B
   RC.EXE        RC.EX_         22    06/30/1999  16:27    88045  9140B3F2
   RCPP.EXE      RCPP.EX_       23    06/30/1999  16:27    47331  9CD4C820
   README.DBG    README.DB_     26    03/27/2000  14:24     2463  042C4614
   RECOVER.COM   RECOVER.CO_    23    07/14/2000  16:02    46656  6AA53B54
   REFLOW.EX     REFLOW.EX_     26    11/23/1999  17:03     2867  B6379D3D

   
                       FixPak Corrective Service levels and disk layouts  53


                   October 24, 2000 - Warp 4 FixPak XRJM014

   REGCONV.EXE   REGCONV.EX_    23    11/24/1999  13:59    52758  FC28E778
   REGEDIT2.EXE  REGEDIT2.EX_    4    11/24/1999  14:00   970752  A6DF77C0
   REGISTRY.DLL  REGISTRY.DL_   22    11/24/1999  13:02    81440  E24B1433
   REGISTRY.MSG  REGISTRY.MS_   26    11/24/1999  14:00      614  734A3416
   REGISTRY.TDF  REGISTRY.TD_   26    11/24/1999  13:02      984  E7DBD05C
   REPLACE.EXE   REPLACE.EX_    24    07/14/2000  16:02    41584  55F7419D
   RESTORE.EXE   RESTORE.EX_    24    07/14/2000  16:02    39584  3C42219B
   REX.MSG       OREX1.MS_      25    03/27/2000  14:23    25123  068B4D67
   REXX.DLL      CREXX1.DL_     17    03/27/2000  14:23   266031  75D50B8E
   REXX.DLL      OREXX1.DL_     10    03/27/2000  14:23   490355  1A317A06
   REXX.IMG      REXX.IM_       20    03/27/2000  14:23   283636  D7EDE39D
   REXXAPI.DLL   REXXAPI.DL_    24    03/27/2000  14:23    40995  2E213324
   REXXC.EXE     REXXC.EX_      26    03/27/2000  14:23     2758  D085D34F
   REXXCRT.DLL   REXXCRT.DL_    20    04/18/2000  09:33    79348  411751D8
   REXXINIT.DLL  REXXINIT.DL_   26    03/27/2000  14:23     8360  98498EC0
   REXXSC.DLL    OREXXSC1.DL_   25    03/27/2000  14:24    43858  5DAC034E
   REXXSOM.DLL   OREXSOM1.DL_   23    03/27/2000  14:24    76878  E448D5E3
   REXXUTIL.DLL  REXXUTIL.DL_   19    03/27/2000  14:23    68119  4D50446B
   REXXUTIL.DLL  ORXUTIL1.DL_   23    03/27/2000  14:23    41175  9BC75C21
   REXXWPS.DLL   OREXWPS1.DL_   26    03/27/2000  14:24     4002  81E1A305
   RINSTPRN.EXE  RINSTPRN.EX_   16    07/08/2000  15:25   208804  2A6EFC2F
   RJAPPLET.EXE  RJAPPLET.EX_   25    07/08/2000  15:13    22702  7860EFD9
   RO.KBL        RO.KB_         26    05/02/2000  13:58      944  AE2308F5
   RSPDDI.EXE    RSPDDI.EX_     24    07/10/2000  23:58    29753  2C264E56
   RSPDSPI.EXE   RSPDSPI.EX_    20    07/10/2000  14:11   143398  B0C04EA6
   RSPIMRI.DLL   RSPIMRI.DL_    25    04/28/2000  12:34    17967  B8B4CDC9
   RSRV.EXE      RSRV.EX_       20    07/10/2000  09:02    78051  5BBEE708
   RU.KBL        RU.KB_         26    05/02/2000  13:58     1144  A00E93D0
   RU441.KBL     RU441.KB_      26    05/02/2000  13:58     1260  E53A3842
   RXVIDCFG.DLL  RXVIDCFG.DL_   25    04/11/2000  13:20    14741  A1C3EF07
   SBFILTER.DLL  SBFILTER.DL_   25    05/15/2000  16:24    14861  430E54D2
   SCENTER.DLL   SCENTER.DL_    13    07/08/2000  15:17   294845  EB0F13E0
   SD.KBL        SD.KB_         26    05/02/2000  13:58     1036  49602175
   SEAMLESS.DLL  SEAMLESS.DL_   24    07/10/2000  18:45    49167  EF39F519
   SECUTIL.DLL   SECUTIL.DL_    25    01/04/2000  12:47    21468  EE210C88
   SEINST.EXE    SEINST.EX_     23    07/10/2000  23:44    48707  D7FA140A
   SERIAL.PDR    SERIAL.PD_     25    07/08/2000  14:57    19170  C1C8DC8E
   SESAPI.DLL    SESAPI.DL_     24    01/04/2000  09:08    24203  6D54FAD7
   SESDB.DLL     SESDB.DL_      25    01/04/2000  09:08    23411  609FC082
   SESDD32.SYS   SESDD32.SY_    21    01/04/2000  12:47   118834  8B2CD1C2
   SESDMON.EXE   SESDMON.EX_    24    01/04/2000  12:47    41742  D0543D86
   SESMGR.DLL    SESMGR.DL_     26    07/10/2000  16:55     1536  E534B919
   SESMGR.TDF    SESMGR.TD_     26    07/07/2000  19:16     1877  800D0D16
   SESRES.DLL    SESRES.DL_     25    01/04/2000  09:09    38672  0A8EFDDE
   SESSHELL.EXE  SESSHELL.EX_    9    01/04/2000  12:47    29517  7D9371E3
   SESSTART.EXE  SESSTART.EX_   25    01/04/2000  12:47    23431  C2B3D398
   SETBOOT.EXE   SETBOOT.EX_    25    07/14/2000  16:00    20912  12B31CB8
   SETDEFV.CMD   SETDEFV.CM_    26    05/26/2000  11:24     1652  7E7ED903
   SF.KBL        SF.KB_         26    05/02/2000  13:58     1036  DEC119F6
   SGMLPARS.DLL  SGMLPARS.DL_   22    07/08/2000  16:53    60416  4D39B493
   SHELL.SDF     SHELL.SD_      24    07/07/2000  19:17    21279  280E0D8B

   
                       FixPak Corrective Service levels and disk layouts  54


                   October 24, 2000 - Warp 4 FixPak XRJM014

   SHOWTODO.EX   SHOWTODO.EX_   26    11/23/1999  17:03     1222  31C06C8E
   SHPIINST.DLL  SHPIINST.DL_   23    07/10/2000  18:29    37310  FCE8ADA1
   SK.KBL        SK.KB_         26    05/02/2000  13:58     1008  06950227
   SL.KBL        SL.KB_         26    05/02/2000  13:58      982  1C59CF1B
   SLDAPI.DLL    SLDAPI.DL_     25    01/04/2000  09:09    22441  30FEBB76
   SOFTDRAW.DLL  SOFTDRAW.DL_   12    07/10/2000  08:43   416439  5D8F45F2
   SOM.DLL       SOM.DL_        19    06/30/1999  16:33    92009  A7AC7A85
   SORT.EXE      SORT.EX_       24    07/14/2000  15:56    32015  433AC9DD
   SPL1B.DLL     SPL1B.DL_      26    07/07/2000  18:31     7125  E590CA23
   SPOOL.EXE     SPOOL.EX_      26    07/14/2000  16:08     6639  CFA7316E
   SPOOLCP.DLL   SPOOLCP.DL_    26    07/07/2000  18:43    10210  F38BBF98
   SQ.KBL        SQ.KB_         26    05/02/2000  13:58      824  304055C3
   SR.KBL        SR.KB_         26    05/02/2000  13:58     1222  CA578989
   SSM.DLL       SSM.DL_        26    06/27/2000  12:38     4118  06E1D369
   SSMDD.SYS     SSMDD.SY_      22    06/27/2000  12:38    36813  A487C18F
   STRACE.EXE    STRACE.EX_     23    07/14/2000  16:03    55943  05E00492
   STRACE.INF    STRACE.IN_     19    01/21/2000  23:52   153828  60F855FC
   SUBST.EXE     SUBST.EU_      26    07/14/2000  11:07     4520  854C6E32
   SUBST.EXE     SUBST.EX_      26    07/14/2000  15:55     4008  1B2A3531
   SV.KBL        SV.KB_         26    05/02/2000  13:58      946  45080742
   SVMC.DLL      SVMC.DL_       19    06/27/2000  12:44    98391  3B0AA8BD
   SVSH.DLL      SVSH.DL_       24    06/27/2000  12:46    23454  B706AC21
   SW.DLL        SW.DL_         21    06/27/2000  12:40    66505  514B957E
   SWITCHRX.CMD  SWITCHRX.CM_   26    03/27/2000  14:23     7928  D1729FC3
   SYMB.PFM      SYM1.PF_       26    11/22/1999  11:22      679  EC2CE0BD
   SYSC.EXE      SYSC.EX_       22    11/24/1999  15:44    57546  D537A3AE
   SYSCTBL.EXE   SYSCTBL.EX_    26    11/24/1999  15:44     7672  F8B161CA
   SYSDUMP.EXE   SYSDUMP.EX_    25    02/16/2000  05:03    28701  D6167DF8
   SYSINSTX.COM  SYSINSTX.CO_   24    07/14/2000  15:56    40128  D4C8C5DD
   SYSLEVEL.EXE  SYSLEVEL.EX_   23    07/10/2000  23:41    44656  1CE68441
   SYSLEVEL.FPK  SYSLEVEL.FP_   26    06/27/2000  08:16      165  35091230
   SYSLEVEL.MSG  SYSLEVEL.MS_   26    09/10/2000  15:26     1474  C44828E4
   SYSLOG.EXE    SYSLOG.EX_     24    02/15/2000  11:46    33288  A593713D
   SYSLOGPM.DLL  SYSLOGPM.DL_   23    02/15/2000  22:01    31644  DED5B1D5
   SYSLOGPM.EXE  SYSLOGPM.EX_   19    02/15/2000  11:46   215355  44F9D44B
   SYSMONO.FON   SYSMONO.FO_    25    07/10/2000  11:30    21294  8E8E0485
   SYSMONOI.FON  SYSMONOI.FO_   24    07/10/2000  09:10    35841  C613405A
   SYSSPLIT.CMD  SYSSPLIT.CM_   26    11/22/1999  11:25     3712  A308EBC8
   TDFLST.CMD    TDFLST.CM_     26    11/22/1999  11:25    13564  7BB43592
   TEDIT.EXE     TEDIT.EX_      25    07/14/2000  16:03     9390  CE8AECA5
   TEDIT.HLP     TEDIT.HL_      26    07/14/2000  15:49    14597  9784A716
   TESTCFG.SYS   TESTCFG.SY_    26    04/24/2000  14:35     9808  77E8686F
   TEXTCON1.EXE  TEXTCON1.EX_   13    11/23/1999  20:12    49011  9916B6FC
   TFFLST.CMD    TFFLST.CM_     26    11/22/1999  11:25     4638  E5A615D0
   TH.KBL        TH.KB_         26    05/02/2000  13:58     1184  72971B5B
   TH190.KBL     TH190.KB_      26    05/02/2000  13:58     1184  54C25399
   TILEHK.DLL    TILEHK.DL_     23    11/23/1999  17:43    51829  E4F46F74
   TIMES.FON     TIMES.FO_      18    07/10/2000  09:15   166150  F0A4D624
   TIMESI.FON    TIMESI.FO_     17    07/10/2000  09:10   181173  7CAE972B
   TNR.OFM       TNR.OF_        26    11/22/1999  11:22     6809  D815154B
   TNR.PFB       TNR.PF_        16    11/22/1999  11:24   145785  BD3CE8BE

   
                       FixPak Corrective Service levels and disk layouts  55


                   October 24, 2000 - Warp 4 FixPak XRJM014

   TNR.PFM       TN1.PF_        26    11/22/1999  11:22     1103  474C4E38
   TNRB.OFM      TNRB.OF_       26    11/22/1999  11:22     6825  BEC21108
   TNRB.PFB      TNRB.PF_       16    11/22/1999  11:24   148564  FD4A88FF
   TNRB.PFM      TNR1.PF_       26    11/22/1999  11:22     1112  604493E3
   TNRBI.OFM     TNRBI.OF_      26    11/22/1999  11:22     6839  6E19C7B5
   TNRBI.PFB     TNRBI.PF_      16    11/22/1999  11:24   159652  798E8739
   TNRBI.PFM     TNRB1.PF_      26    11/22/1999  11:22     1118  62DE75CD
   TNRI.OFM      TNRI.OF_       26    11/22/1999  11:22     6830  23B85EEE
   TNRI.PFB      TNRI.PF_       16    11/22/1999  11:24   157010  AE81357B
   TNRI.PFM      TNR2.PF_       26    11/22/1999  11:22     1114  67AE659D
   TR.KBL        TR.KB_         26    05/02/2000  13:58      962  E4CD2587
   TR440.KBL     TR440.KB_      26    05/02/2000  13:58     1042  5924013D
   TRACE.DOC     TRACE.DO_      25    01/21/2000  10:05    64057  95DDD51A
   TRACE.EXE     TRACE.EX_      23    07/14/2000  16:03    56064  C5FBA534
   TRACE.HLP     TRACE.HL_      24    07/14/2000  16:07    38870  7BC64A31
   TRACEDLL.DLL  TRACEDLL.DL_   22    02/16/2000  04:57    46987  ACD413F0
   TRACEFMT.EXE  TRACEFMT.EX_   18    07/14/2000  16:07   232067  5C04B595
   TRACEGET.EXE  TRACGET1.EX_   25    02/16/2000  04:57    29930  FC469660
   TRACEGET.EXE  TRACEGET.EX_   25    02/16/2000  04:57    29930  FC469660
   TRACEREF.INF  TRACEREF.IN_   12    05/04/2000  20:34  1391720  8CFE4351
   TRADEMBK.INF  TRADEMBK.IN_   26    05/04/2000  20:33     2364  7A12A28F
   TRAPDUMP.EXE  TRAPDUMP.EX_   25    02/16/2000  05:03    30236  B98D8AA7
   TRAPLOG.EXE   TRAPLOG.EX_    25    02/16/2000  05:03    28191  E269D501
   TRC0000.TFF   TRC0000.TF_    26    07/10/2000  15:50      189  B8DB2626
   TRC0001.TFF   TRC0001.TF_    26    11/24/1999  13:02     1370  17F81D51
   TRC0003.TFF   TRC0003.TF_    26    07/10/2000  15:50     1503  1ADD8690
   TRC0004.TFF   TRC0004.TF_    26    07/10/2000  15:50     4754  3982826C
   TRC0005.TFF   TRC0005.TF_    25    07/10/2000  15:50    40960  41101E42
   TRC0006.TFF   TRC0006.TF_    26    07/10/2000  15:50    12356  A475674E
   TRC0007.TFF   TRC0007.TF_    26    06/26/2000  17:05     3336  6032C047
   TRC0008.TFF   TRC0008.TF_    26    04/24/2000  13:07      544  473F96D2
   TRC0010.TFF   TRC0010.TF_    26    07/07/2000  19:16    13647  C63B2EDD
   TRC0012.TFF   TRC0012.TF_    26    07/10/2000  16:55     1247  4B139675
   TRC0016.TFF   TRC0016.TF_    26    07/07/2000  19:16     1673  8107012A
   TRC0017.TFF   TRC0017.TF_    26    07/07/2000  19:16     5561  A8B3BD6B
   TRC0018.TFF   TRC0018.TF_    26    07/07/2000  19:16    39488  C5C61365
   TRC006D.TFF   TRC006D.TF_    26    06/05/2000  11:01    24181  FB8A71A8
   TRC00C0.TFF   TRC00C0.TF_    26    07/10/2000  18:36    15970  167D7C66
   TRC00C2.TFF   TRC00C2.TF_    26    07/10/2000  18:36    25994  78380A03
   TRC00C3.TFF   TRC00C3.TF_    26    07/10/2000  18:36     3984  996F4ABC
   TRC00C4.TFF   TRC00C4.TF_    22    07/10/2000  11:28      288  623F52A4
   TRC00C5.TFF   TRC00C5.TF_    26    07/10/2000  08:50    32994  86F3A018
   TRC00C6.TFF   TRC00C6.TF_    26    07/07/2000  18:31     7146  F49E1201
   TRC0100.TFF   TRC0100.TF_    26    07/10/2000  15:50     7219  FB08088B
   TRC0101.TFF   TRC0101.TF_    15    07/10/2000  15:50     7968  B40AAFEE
   TRC0102.TFF   TRC0102.TF_    26    07/10/2000  15:50    29153  76955C86
   TRC0103.TFF   TRC0103.TF_    26    07/10/2000  15:50     9590  88EA9449
   TRC0104.TFF   TRC0104.TF_    26    07/10/2000  15:50     5134  610873D7
   TRC0105.TFF   TRC0105.TF_    26    07/10/2000  15:50    24421  9F711FDC
   TRC0106.TFF   TRC0106.TF_    26    07/10/2000  15:50     1549  9CDE5090
   TRC0108.TFF   TRC0108.TF_    26    07/10/2000  15:50     9505  42F6E01E

   
                       FixPak Corrective Service levels and disk layouts  56


                   October 24, 2000 - Warp 4 FixPak XRJM014

   TRC0109.TFF   TRC0109.TF_    26    07/10/2000  15:50     2535  CF7D8464
   TRC010A.TFF   TRC010A.TF_    20    07/10/2000  15:50     1130  75D8C180
   TRC0118.TFF   TRC0118.TF_    26    05/03/2000  14:13     2526  4787CB05
   TRC0119.TFF   TRC0119.TF_    26    05/03/2000  14:29     3786  6E1C8A0C
   TRC012C.TFF   TRC012C.TF_    26    07/10/2000  18:45     5361  4D6B946C
   TRC012D.TFF   TRC012D.TF_    26    07/10/2000  18:45     7870  CDF5F31B
   TRC012E.TFF   TRC012E.TF_    26    07/08/2000  16:39    32972  8DB92D62
   TRCFORMT.DLL  TRCFORMT.DL_   24    07/14/2000  16:07    27015  6527C774
   TRCUST.EXE    TRCUST.EX_     22    07/14/2000  16:04    98773  23AAD422
   TREE.COM      TREE.CO_       24    07/14/2000  15:56    34153  0D742D4E
   TRNSCALL.DLL  TRNSCALL.DL_   26    11/24/1999  15:44     8434  E7461CC3
   TRSPOOL.DOC   TRSPOOL.DO_    26    11/22/1999  11:25     6638  FC5EA5CC
   TRSPOOL.EXE   TRSPOOL1.EX_   24    02/16/2000  04:57    42054  46643F00
   TRSPOOL.EXE   TRSPOOL.EX_    24    02/16/2000  04:57    42054  46643F00
   TRSTOP.EXE    TRSTOP.EX_     25    02/16/2000  04:57    23486  F5EB78A5
   TRUECONV.DLL  TRUECONV.DL_   21    12/30/2010  22:16    89131  107352D7
   TRUETYPE.DLL  TRUETYPE.DL_   15    04/12/2000  11:40   128567  2661D3D5
   TW.KBL        TW.KB_         26    05/02/2000  13:58      780  A1663157
   UA.KBL        UA.KB_         26    05/02/2000  13:58     1476  93B0531A
   UCDFS.DLL     UCDFS.DL_      25    02/17/2000  00:13    13776  63BBEFAF
   UCDFS.MSG     UCDFS.MS_      26    02/17/2000  00:13     2269  CCDE1984
   UCONV.DLL     UCONV.DL_      25    05/02/2000  14:03    22819  74476AC2
   UHPFS.DLL     UHPFS.DL_      21    05/03/2000  14:25   106000  EF8329E9
   UK.KBL        UK.KB_         26    05/02/2000  13:58      816  45ED40AD
   UK168.KBL     UK168.KB_      26    05/02/2000  13:58      850  E82F54C5
   ULSACT01.MSG  ULSACT01.MS_    7    11/23/1999  13:33      907  CCFEF741
   ULSCAU01.MSG  ULSCAU01.MS_    5    11/23/1999  13:33      899  5B2E152F
   ULSDET01.MSG  ULSDET01.MS_    1    11/23/1999  13:33      903  A0B1A1BE
   ULSERR01.MSG  ULSERR01.MS_   26    11/23/1999  13:33     1967  DB03FAC5
   UNDELETE.COM  UNDELETE.CO_   24    07/14/2000  16:07    36953  F55A6E88
   UNICODE.SYS   UNICODE.SY_    25    05/02/2000  13:58    20014  B3F4439D
   UNIKBD.DLL    UNIKBD.DL_     24    05/02/2000  13:58    28291  EDE0E469
   UNPACK.EXE    UNPACK.EX_     20    07/10/2000  23:59    75168  78787923
   UNPACK2.EXE   UNPACK2.EX_    22    07/11/2000  00:11    80128  C04B1795
   US.KBL        US.KB_         26    05/02/2000  13:58      774  BFEA4A56
   USDV.KBL      USDV.KB_       26    05/02/2000  13:58      942  F79C60F7
   USDVL.KBL     USDVL.KB_      26    05/02/2000  13:58      924  96E2F19A
   USDVR.KBL     USDVR.KB_      26    05/02/2000  13:58      942  64EEF3C7
   USERFDD.DLL   USERFDD.DL_    26    11/24/1999  15:42     7083  D5C1F99F
   USINTER.KBL   USINTER.KB_    26    05/02/2000  13:58     1032  51BEB55E
   VBIOS.SYS     VBIOS.SY_      10    11/23/1999  12:44    10128  11CF310E
   VCMOS.SYS     VCMOS.SY_      26    11/23/1999  12:45     2272  43B68ECA
   VDMA.SYS      VDMAPS2.SY_    26    11/23/1999  12:45    14329  8FF31025
   VDMA.SYS      VDMAAT.SY_     26    11/23/1999  12:45    11465  A4ECE8B0
   VDMIMFEP.EXE  VDMIMFEP.EX_   26    07/10/2000  18:06     8192  B8A9D1C2
   VDPMI.SYS     VDPMI.SY_      25    11/23/1999  12:46    30626  DE6D0B18
   VDPX.SYS      VDPX.SY_       25    11/23/1999  12:47    26322  81E975E0
   VIDEOCFG.DLL  VIDEOCFG.DL_   23    07/10/2000  14:04    38126  0BD9EFBC
   VIEW.EXE      VIEW.EX_       24    07/10/2000  18:01    33792  06DD147D
   VIEWDOC.EXE   VIEWDOC.EX_    24    07/10/2000  18:01    31999  A6ADE6B1
   VIOCALLS.DLL  VIOCALLS.DL_   26    07/10/2000  09:14     2048  E62456F1

   
                       FixPak Corrective Service levels and disk layouts  57


                   October 24, 2000 - Warp 4 FixPak XRJM014

   VIOTBL.DCP    VIOTBL.DC_     23    05/02/2000  13:58   225355  4050889E
   VIOTBL.ISO    VIOTBL.IS_     23    05/02/2000  13:58   230105  29FF721C
   VKKC.SYS      VKKC.SY_        2    11/24/1999  15:42     7632  9691F2EC
   VMAN.DLL      VMAN.DL_       22    07/10/2000  19:17    46649  720AE672
   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
   VTIMER.SYS    VTIMER.SY_     26    11/23/1999  12:48    10560  68AF43F8
   VW32S.SYS     VW32S.SY_      25    11/23/1999  12:50    18338  52CBEA0A
   VWIN.SYS      VWIN.SY_       25    11/23/1999  12:49    27104  94A9C806
   WCFGMRI.DLL   WCFGMRI.DL_    26    07/08/2000  14:55     5670  F8410E08
   WD24B.DSP     WD24B.DS_      26    03/15/2000  11:19    32662  6883B5CF
   WELCMMRI.DLL  WELCMMRI.DL_   25    07/08/2000  15:32    13897  455413A8
   WINCFG.DLL    WINCFG.DL_     25    07/08/2000  16:44    13379  2ACDE769
   WINPRF.DLL    WINPRF.DL_     23    04/13/2000  10:34    36288  7D00D820
   WPCLS.IMP     WPCLS.IM_      26    03/27/2000  14:23     8661  DA299BC2
   WPCOMET.DLL   WPCOMET.DL_    26    07/10/2000  17:53     8720  AA3EC617
   WPCONFIG.DLL  WPCONFIG.DL_   14    07/08/2000  14:54   266404  2806C59E
   WPCONMRI.DLL  WPCONMRI.DL_   24    07/08/2000  14:54    34352  765C5944
   WPDSACTV.EXE  WPDSACTV.EX_   25    07/07/2000  18:44    13955  678153A4
   WPDSINIT.EXE  WPDSINIT.EX_   24    07/07/2000  18:44    21803  36243F65
   WPDSRVP.DLL   WPDSRVP.DL_    25    07/07/2000  18:44    14194  8F0C5332
   WPHELP.HLP    WPHELP.HL_      5    02/24/2000  20:21  1049548  796D2BDF
   WPINET.DLL    WPINET.DL_     19    07/08/2000  17:04   117180  7F46EA67
   WPINSTAL.DLL  WPINSTAL.DL_   24    01/04/2000  15:52    29281  20901EE7
   WPINTMRI.DLL  WPINTMRI.DL_   26    07/08/2000  15:13    11836  C912CE43
   WPMSG.HLP     WPMSG.HL_      22    05/04/2000  20:27    69958  2B429D2E
   WPNLS.DLL     WPNLS.DL_      22    07/08/2000  15:30    43676  97597A58
   WPNLSMRI.DLL  WPNLSMRI.DL_   12    07/08/2000  15:31    17335  DF677E37
   WPPRINT.DLL   WPPRINT.DL_     2    07/07/2000  20:04   364102  2D309408
   WPPRINT.HLP   WPPRINT.HL_    21    07/08/2000  15:00    96313  C0C19727
   WPPRTMRI.DLL  WPPRTMRI.DL_   22    07/08/2000  15:00    67513  884BA06F
   WPREXX.IMP    WPREXX.IM_     26    03/27/2000  14:23     6313  8425963F
   WPSH.IR       WPSH.IR_       21    07/07/2000  08:17   274823  4F04B7EB
   WPSINIT.WPS   WPSINIT.WP_    26    03/27/2000  14:23    15877  ACCB0859
   WPSINST.CMD   WPSINST.CM_    26    03/27/2000  14:23     2813  EDFD1426
   WSLCALLS.DLL  WSLCALLS.DL_   19    08/24/2000  11:33    95560  2056C08B
   XCOPY.EXE     XCOPY.EX_      23    07/14/2000  15:57    53008  CBB50347
   XDF.MSG       XDF.MS_        26    07/14/2000  15:57     2155  5BFB291A
   XDFCOPY.EXE   XDFCOPY.EX_    21    07/14/2000  15:57    89887  BCF9B880
   XDFH.MSG      XDFH.MS_       26    07/14/2000  15:57     1113  341A8DD2
   XIMACALL.DLL  XIMACALL.DL_   19    07/10/2000  18:06    92634  29455AC3
   XIPSCALL.DLL  XIPSCALL.DL_   25    07/10/2000  18:06     4998  0F2F1470
   XPG00420.TBL  XPG00420.TB_   14    11/22/1999  12:17    27264  88667C8B
   XPG00864.TBL  XPG00864.TB_    8    11/22/1999  12:17    27264  76725C6C
   XVIOCALL.DLL  XVIOCALL.DL_   26    11/24/1999  15:43     6829  ECF60D8C

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

   
                       FixPak Corrective Service levels and disk layouts  58


                   October 24, 2000 - Warp 4 FixPak XRJM014

   Fixpak name:   XRJM014_   (Country = Japan)
   Pre-requisite CSD Level:  XRJ4000_
   System Id:  1000
   Component Id:  5639A6100
   Archive is ON for this product.
   ________________________________________________________________________

   Default directories:

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

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   INSTALL.EXE   INSTALL2.EX_   26    05/11/1999  00:52   423209  4FCE2843
   INSTALL.EXE   INSTALL1.EX_   27    05/11/1999  01:47   416477  651DC9FC
   OS2LDR        OS2LDR.___     26    07/07/2000  20:56    45056  57D01542
   RSPINST.EXE   RSPINST2.EX_   26    05/11/1999  01:07   470016  D70EB68F
   RSPINST.EXE   RSPINST1.EX_   27    05/11/1999  02:03   457152  4E1940D3

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.3
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.01
   Fixpak name:   XRJM014_   (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\*

   
                       FixPak Corrective Service levels and disk layouts  59


                   October 24, 2000 - Warp 4 FixPak XRJM014

           ..\..\LANGUAGE
           ..\..\LANGUAGE\*

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPDBUTL.DLL  APPDBUTL.DL_   27    02/25/2000  12:15    25015  46879016
   APPSTART.EXE  APPSTART.EX_   27    02/25/2000  12:15    33858  D7711D28
   NCAPPUTL.EXE  NCAPPUTL.EX_   27    02/25/2000  12:15    14624  29FB65C8
   OS2LDR        OS2LDR.___     27    07/07/2000  20:58    45056  6E31E302
   PMLOGON.EXE   PMLOGON.EX_    27    01/24/2000  11:20    40109  5D5B81C3
   PRNCFG.DLL    PRNCFG.DL_     26    01/24/2000  11:21    58258  E0003042
   TDESK.DLL     TDESK.DL_      26    01/25/2000  01:53     6653  E9923660
   TLOGOFF.EXE   TLOGOFF.EX_    27    01/25/2000  01:53     9581  388C409D
   TOBJECT.DLL   TOBJECT.DL_    26    01/25/2000  01:53     7312  887F372F
   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:   XRJM014_   (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_   27    03/22/2000  10:08    35022  D8F2F43F
   NCAPPUTL.EXE  NCAPPUTL.EX_   27    03/22/2000  10:08    21270  DAA7210D
   OS2LDR        OS2LDR.___     27    07/07/2000  20:58    45056  6E31E302
   TSHUTDWN.EXE  TSHUTDWN.EX_   27    02/15/2000  12:41    10795  F1099ADA


   
                       FixPak Corrective Service levels and disk layouts  60


                   October 24, 2000 - Warp 4 FixPak XRJM014

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.5
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM014_   (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:   XRJM014_   (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:   XRJM014_   (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  2944F5F2
   DRVMAP.INF    DRVMAP.IN_     27    07/10/2000  23:40     7668  5E3D05B3
   GDI.EXE       GDI.EX_        27    12/02/1999  16:20   225776  8E4C99DC
   IFGDI2VM.DRV  IFGDI2VM.DR_   27    05/15/2000  16:23    93136  7268D00F
   ISGDI2VM.DRV  ISGDI2VM.DR_   27    05/15/2000  16:07    92048  414AB307
   MAIN.CPL      MAIN.CP_       27    12/02/1999  16:32   147680  FF983A7F
   MMSOUND.DRV   MMSOUND.DR_    27    12/02/1999  16:48     3456  97C7CFF0
   OS2K386.EXE   OS2K386.EX_    27    12/02/1999  16:22    80306  CAEDD240
   PROGMAN.EXE   PROGMAN.EX_    27    12/02/1999  16:29   115328  43CE07B7
   REGEDIT.HLP   REGEDIT.HL_    27    12/02/1999  17:59    22682  FEC4ACA5
   USER.EXE      USER.EX_       27    12/02/1999  16:42   281088  453F4D7A
   WINFILE.EXE   WINFILE.EX_    27    12/02/1999  16:31   146960  225456E2
   WINSCLIP.DLL  WINSCLIP.DL_   28    12/02/1999  16:27    14848  063E037D
   WINSDDE.DLL   WINSDDE.DL_    27    12/02/1999  16:27    18432  A6BD0F73
   WINSHELD.EXE  WINSHELD.EX_   27    12/02/1999  16:27    22528  F1802A0D

   
                       FixPak Corrective Service levels and disk layouts  61


                   October 24, 2000 - Warp 4 FixPak XRJM014

   WINSMSG.DLL   WINSMSG.DL_    27    12/02/1999  16:27    28441  ED6CB51E

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.6
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM014_   (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:   XRJM014_   (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:   XRJM014_   (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_       28    08/27/1998  15:32     9888  04488555
   DRVMAP.INF    DRVMAP.IN_     28    07/10/2000  23:40     2968  CCCE66EA
   GDI.EXE       GDI.EX_        28    02/08/1999  17:59   277568  97A89558
   IBMJ5577.DRV  IBMJ5577.DR_   28    02/08/1999  17:59    50784  0EE893FE
   IBMJ5587.DRV  IBMJ5587.DR_   28    02/08/1999  17:59    37008  9F475EF1
   IFGDI2VM.DRV  IFGDI2VM.DR_   28    05/15/2000  16:23    93136  7268D00F
   ISGDI2VM.DRV  ISGDI2VM.DR_   28    05/15/2000  16:07    92048  414AB307
   MAIN.CPL      MAIN.CP_       28    02/08/1999  17:59   181216  6FF18F23
   MMSOUND.DRV   MMSOUND.DR_    28    08/27/1998  15:30     3456  06834379
   OS2K386.EXE   OS2K386.EX_    28    02/08/1999  17:59    82338  F937D689
   PROGMAN.EXE   PROGMAN.EX_    28    02/08/1999  17:59   118336  C4CBDCD6
   PS55DM24.JFD  PS55DM24.JF_   28    03/15/1999  17:04   302316  5A344411
   PS55SGOT.JFD  PS55SGOT.JF_   28    02/02/1999  15:34    81024  E40626F0

   
                       FixPak Corrective Service levels and disk layouts  62


                   October 24, 2000 - Warp 4 FixPak XRJM014

   PS55SMIN.JFD  PS55SMIN.JF_   28    02/02/1999  15:34    81152  6F607B18
   REGEDIT.HLP   REGEDIT.HL_    28    08/27/1998  15:34    21951  3FB49281
   USER.EXE      USER.EX_       28    03/15/1999  17:04   281040  5E84305D
   WINFILE.EXE   WINFILE.EX_    28    08/27/1998  15:32   152560  19DD937D
   WINSCLIP.DLL  WINSCLIP.DL_   28    08/27/1998  15:32    14848  A346D953
   WINSDDE.DLL   WINSDDE.DL_    28    02/08/1999  17:59    18432  0903955B
   WINSHELD.EXE  WINSHELD.EX_   28    08/27/1998  15:32    22528  0F8D6ADC
   WINSMSG.DLL   WINSMSG.DL_    28    02/08/1999  17:59    28953  FF6A5390

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.7
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM014_   (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:   XRJM014_   (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:   XRJM014_   (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_      28    08/24/2000  11:33    28005  9295637B
   WSLOGIC.DLL   WSLOGIC.DL_    28    08/24/2000  11:33   146146  CA8F71D8

   ************************************************************************

   
                       FixPak Corrective Service levels and disk layouts  63


                   October 24, 2000 - Warp 4 FixPak XRJM014

   Product location on CSD:  A:\FIX\OS2.8
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRJM014_   (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:   XRJM014_   (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:   XRJM014_   (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_   28    11/24/1999  15:43    30628  6A372195
   KEYB106.COM   KEYB106.CO_    28    08/27/1998  15:27    15728  E77E3D9C
   KEYB106.DCP   KEYB106.DC_    28    05/02/2000  14:17    53861  7EEFEFC2
   KEYBAX.COM    KEYBAX.CO_     28    08/27/1998  15:27    16632  2546BF0F
   KEYBAX.DCP    KEYBAX.DC_     28    05/02/2000  14:17    39239  8B304F05
   KEYBUS.DCP    KEYBUS.DC_     28    05/02/2000  14:17    39239  41BFE173
   VDMAAT.SYS    VDMAAT1.SY_    28    11/23/1999  12:45    11465  5359C2B9
   VDMAPS2.SYS   VDMAPS21.SY_   28    11/23/1999  12:45    14329  C55F2401









   
                       FixPak Corrective Service levels and disk layouts  64


                   October 24, 2000 - Warp 4 FixPak XRJM014

   10.0 SPACE UTILIZATION

   The FixPak installation process requires free space on the following
   drives:

   Space needed   Drive
   Up to 2MB      C:
   Up to 2MB      Boot drive (4MB if boot is C:)
   Up to 22MB     Drive with most free space, holds deferred files if
                  A:SERVICE method used.
   Up to 61MB     FixPak Archive/Backup for product with CSD level of
                  XRJ4000
   Up to 59MB     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.


   10.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE

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

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

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

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




   
                                                       Space Utilization  65


                   October 24, 2000 - Warp 4 FixPak XRJM014

   10.0.2 TRADEMARKS

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

   þ  IBM
   þ  OS/2
   þ  WorkSpace On-Demand

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









































   
                                                       Space Utilization  66
