<        Installation instructions for Warp 4 FixPak XRAM011















        

        
        



        October 7, 1999

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

                      October 7, 1999 - Warp 4 FixPak XRAM011


        October 7, 1999 - Warp 4 FixPak XRAM011


















































   
                                                                    Page  ii


                    October 7, 1999 - Warp 4 FixPak XRAM011

   CONTENTS


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

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

     3.0 Installation Notes  . . . . . . . . . . . . . . . . . . . . . . . 3
       3.0.1 Device Drivers removed from Fixpak  . . . . . . . . . . . . . 3
       3.0.2 Can't install Warp 4  . . . . . . . . . . . . . . . . . . . . 3
       3.0.3 Please use Fixtool f.141 or later   . . . . . . . . . . . . . 3
       3.0.4 TRAP in ES16881$ after FP10 applied   . . . . . . . . . . . . 3
       3.0.5 System Sounds not working after FixPak applied  . . . . . . . 4
       3.0.6 Using Display Recovery Choices  . . . . . . . . . . . . . . . 4
       3.0.7 Installation of Java 1.1.4  . . . . . . . . . . . . . . . . . 5
       3.0.8 DSPRES.DLL included in this FixPak  . . . . . . . . . . . . . 5
       3.0.9 No products were found  . . . . . . . . . . . . . . . . . . . 5
       3.0.10 Previous installation interrupted  . . . . . . . . . . . . . 6
       3.0.11 Unable to open Archive directory   . . . . . . . . . . . . . 6
       3.0.12 RC 932 doing CID install of Warp 4   . . . . . . . . . . . . 7
       3.0.13 Multimedia no longer selectable  . . . . . . . . . . . . . . 8
       3.0.14 MMPARTS.DLL/USER.EXE popup during install  . . . . . . . . . 8
       3.0.15 CSF0208 No products were found on the target ...   . . . . . 8
       3.0.16 CSF0248 Archive path is shared between mismatched  . . . . . 8
       3.0.17 CSF0249 Error opening or creating archive file.    . . . . . 9
       3.0.18 Printer installation process change  . . . . . . . . . . . . 9
       3.0.19 Configuration Installation Distribution ( CID )  . . . . . . 9

     4.0 Post Installation Notes  . . . . . . . . . . . . . . . . . . . . 10
       4.0.1 RAS file changes   . . . . . . . . . . . . . . . . . . . . . 10
       4.0.2 Setting IRQ9 processing in config.sys for VPIC.SYS   . . . . 10
       4.0.3 Windows printer drivers leave a zombie thread running  . . . 11
       4.0.4 APAR JR09494 (trap exiting WINOS2 with MWAVE audio)  . . . . 11
       4.0.5 SYS3170 installing Lotus SmartSuite 96   . . . . . . . . . . 11
       4.0.6 Intermittent hangs   . . . . . . . . . . . . . . . . . . . . 12

     5.0 New Function   . . . . . . . . . . . . . . . . . . . . . . . . . 13
     5.1 Serviceability (RAS) Enhancements  . . . . . . . . . . . . . . . 13
     5.2 Querying file dates for files after Dec 31, 1999 in REXX   . . . 13
     5.3 Enhanced support for Workspace On-Demand   . . . . . . . . . . . 14
       5.3.1 PMLOGON user exits   . . . . . . . . . . . . . . . . . . . . 14
       5.3.2 Setup strings for public applications  . . . . . . . . . . . 17
       5.3.3 Command line options for TLOGOFF and TSHUTDWN  . . . . . . . 18
       5.3.4 PMLOGON No Progress Indicator option   . . . . . . . . . . . 18
       5.3.5 PMLOGON No System Modal Window option  . . . . . . . . . . . 19
     5.4 Euro Support   . . . . . . . . . . . . . . . . . . . . . . . . . 19
       5.4.1 Base OS/2 support  . . . . . . . . . . . . . . . . . . . . . 19
       5.4.2 Where Euro is not supported  . . . . . . . . . . . . . . . . 20
       5.4.3 Printing the Euro  . . . . . . . . . . . . . . . . . . . . . 21
     5.5 New Warp Registry Editor   . . . . . . . . . . . . . . . . . . . 21
     5.6 WorkSpace On Demand  . . . . . . . . . . . . . . . . . . . . . . 21

   
                                                               Contents  iii


                    October 7, 1999 - Warp 4 FixPak XRAM011

     5.7 IBM Open32   . . . . . . . . . . . . . . . . . . . . . . . . . . 21
     5.8 Graphics Adapter Device Drivers (GRADD)  . . . . . . . . . . . . 22
     5.9 Joliet-2 support in CDFS.IFS   . . . . . . . . . . . . . . . . . 22
     5.10 New (improved) CHKDSK   . . . . . . . . . . . . . . . . . . . . 22
       5.10.1 Using the new CHKDSK  . . . . . . . . . . . . . . . . . . . 22
       5.10.2 CHKDSK log formatter  . . . . . . . . . . . . . . . . . . . 24
     5.11 Automated Trap Screen Logging   . . . . . . . . . . . . . . . . 25
       5.11.1 SUPPRESSPOPUPS  . . . . . . . . . . . . . . . . . . . . . . 25
       5.11.2 TRAPLOG   . . . . . . . . . . . . . . . . . . . . . . . . . 25
       5.11.3 TRAPDUMP  . . . . . . . . . . . . . . . . . . . . . . . . . 26
       5.11.4 SYSDUMP   . . . . . . . . . . . . . . . . . . . . . . . . . 26
     5.12 Other README files  . . . . . . . . . . . . . . . . . . . . . . 27

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

     7.0 Installation Process   . . . . . . . . . . . . . . . . . . . . . 33
     7.1 Before installation  . . . . . . . . . . . . . . . . . . . . . . 33
     7.2 Method 1: Install from booted OS/2 partition.    . . . . . . . . 33
     7.3 Method 2: Install from alternate bootable media  . . . . . . . . 34
     7.4 Additional Corrective Service Facility information   . . . . . . 35
     7.5 FixPaks on CD-ROM  . . . . . . . . . . . . . . . . . . . . . . . 35

     8.0 CSD level of SYSLEVEL.OS2  . . . . . . . . . . . . . . . . . . . 36
       8.0.1 New SYSLEVEL.FPK   . . . . . . . . . . . . . . . . . . . . . 37

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

     10.0 Space Utilization   . . . . . . . . . . . . . . . . . . . . . . 51
       10.0.1 Recovering FixPak ARCHIVE and BACKUP space  . . . . . . . . 51
       10.0.2 TRADEMARKS  . . . . . . . . . . . . . . . . . . . . . . . . 52















   
                                                                Contents  iv


                    October 7, 1999 - Warp 4 FixPak XRAM011

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

   Downloading the Service Fixes included in FixPak XRAM011 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
      XRAM011 for maintenance purposes.
   4. All other terms and conditions of your OS/2 Warp 4 license agreements
      apply to the Service Fixes; however, this does not extend any warranty
      and/or services, including but not limited to the "Initial
      Installation" period, outlined in such agreements.



































   
                                                     Terms and Conditions  1


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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 7, 1999 - Warp 4 FixPak XRAM011

   3.0 INSTALLATION NOTES



   3.0.1 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 one will be XR_D001 which is scheduled for a later release.

   To avoid potential Device Driver problems with the installation of Warp 4
   FixPak XRAM011 and Warp 3 FixPak XR_W041, your system should be at FixPak
   level XR5M005 or higher for Warp 4 and XR5W032 or higher for Warp 3.


   3.0.2 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.3 PLEASE USE FIXTOOL F.141 OR LATER

   Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
   Corrective Service Facility f.141 or later.  It has fixes for problems
   found in 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.141 you will get a "CSF0208 No
   products were found on the target system to service" message.


   3.0.4 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.


   
                                                       Installation Notes  3


                    October 7, 1999 - Warp 4 FixPak XRAM011

   3.0.5 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


   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.6 USING DISPLAY RECOVERY CHOICES

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

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


   
                                                       Installation Notes  4


                    October 7, 1999 - Warp 4 FixPak XRAM011

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

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

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


   3.0.7 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.8 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.9 NO PRODUCTS WERE FOUND

   If you see a "No products were found" 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


   
                                                       Installation Notes  5


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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.


   3.0.10 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.11 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.







   
                                                       Installation Notes  6


                    October 7, 1999 - Warp 4 FixPak XRAM011

   3.0.12 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.

   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

   
                                                       Installation Notes  7


                    October 7, 1999 - Warp 4 FixPak XRAM011

         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




   3.0.13 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.14 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL

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


   3.0.15 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.16 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.

   
                                                       Installation Notes  8


                    October 7, 1999 - Warp 4 FixPak XRAM011

      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.17 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.

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

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


   3.0.18 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.19 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  9


                    October 7, 1999 - Warp 4 FixPak XRAM011

   4.0 POST INSTALLATION NOTES



   4.0.1 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:

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



   4.0.2 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.








   
                                                 Post Installation Notes  10


                    October 7, 1999 - Warp 4 FixPak XRAM011

   4.0.3 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING

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

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

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

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

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

   þ  backgroundtasks=run_enum.exe,hpfbkg02.exe

   then restart WINOS2.

   Note: There may be other drivers that have the same problem.  If you
   experiences a similar problem with other drivers, please report it so the
   correct SYSTEM.INI entry can be determined.



   4.0.4 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.5 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

   
                                                 Post Installation Notes  11


                    October 7, 1999 - Warp 4 FixPak XRAM011

   completed, restore the Matrox driver.


   4.0.6 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  12


                    October 7, 1999 - Warp 4 FixPak XRAM011

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


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

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

   Since the output format of the 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:











   
                                                            New Function  13


                    October 7, 1999 - Warp 4 FixPak XRAM011

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

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


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


   5.3 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND



   5.3.1 PMLOGON USER EXITS

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

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

      /URX                           \OS2\PMLOGURX.CMD

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

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




   
                                                            New Function  14


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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  15


                    October 7, 1999 - Warp 4 FixPak XRAM011

       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  16


                    October 7, 1999 - Warp 4 FixPak XRAM011

                          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.3.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  17


                    October 7, 1999 - Warp 4 FixPak XRAM011

       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.3.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.3.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  18


                    October 7, 1999 - Warp 4 FixPak XRAM011

   5.3.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.4 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.4.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  19


                    October 7, 1999 - Warp 4 FixPak XRAM011

       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    it142    altgr-5
       Latin America     la       altgr-e
       Netherlands       nl       altgr-e
       Norway            no       altgr-5
       Portugal          po       altgr-5
       Spain             sp (es)  altgr-5
       Sweden            sv       altgr-5
       Swiss French      sf       altgr-e
       Swiss German      sg (sd)  altgr-e
       Turkey            tr179    altgr-e
       Turkey 440        tr440    altgr-e
       UK                uk       altgr-4
       UK 168            uk168    altgr-e
       US International  ux       altgr-e





   5.4.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  20


                    October 7, 1999 - Warp 4 FixPak XRAM011

           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.4.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.5 NEW WARP REGISTRY EDITOR

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


   5.6 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.7 IBM OPEN32

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





   
                                                            New Function  21


                    October 7, 1999 - Warp 4 FixPak XRAM011

   5.8 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.9 JOLIET-2 SUPPORT IN CDFS.IFS

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

   Joilet-3 format is not supported.



   5.10 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.10.1 USING THE NEW CHKDSK

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

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

   Note: OS/2 Warp Install uses fast format.



   
                                                            New Function  22


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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  23


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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.10.2 CHKDSK LOG FORMATTER

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

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


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





   
                                                            New Function  24


                    October 7, 1999 - Warp 4 FixPak XRAM011

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


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

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


   5.11 AUTOMATED TRAP SCREEN LOGGING

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

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


   5.11.1 SUPPRESSPOPUPS

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

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

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


   5.11.2 TRAPLOG

   The TRAPLOG command allows dynamic control of trap information logging.

   The command syntax is:

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



   
                                                            New Function  25


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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.11.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.11.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  26


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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.12 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).
















   
                                                            New Function  27


                    October 7, 1999 - Warp 4 FixPak XRAM011

   6.0 CORRECTIVE SERVICE FACILITY



   6.0.1 REQUIRED CSF LEVEL

   You should use release level f.141 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  28


                    October 7, 1999 - Warp 4 FixPak XRAM011


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

   Label the diskette as

         FixPak XRAM011
   Corrective Service Diskette ?
          (CSF DISK ?)


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

        Examples:

        XRAM011.ADK = 10
        XRAM011.FDK = 15
        XRAM011.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  29


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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  30


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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  31


                    October 7, 1999 - Warp 4 FixPak XRAM011

       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  32


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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_141 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 XRAM011
   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  33


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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_141 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  34


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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.


   7.5 FIXPAKS ON CD-ROM

   Both the IBM Technical Connection and the IBM Developer Connection
   contain the latest OS/2 and LAN FixPaks that were available at publishing
   time.

   The IBM Technical Connection homepage on the World Wide Web is located
   at:

   þ  http://www.ibm.com/Support/techconn/index.htm

   The IBM Developer Connection homepage on the World Wide Web is located
   at:

   þ  http://www.developer.ibm.com/devcon/titlepg.htm

   Check these WWW sites for content and ordering information.


   
                                                    Installation Process  35


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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.00
   Revision 9.035


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

   Build Level: n.nnn



   
                                               CSD level of SYSLEVEL.OS2  36


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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  37


                    October 7, 1999 - Warp 4 FixPak XRAM011

   9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 9.035

   Product location on CSD:  A:\FIX\OS2.1
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRAM011_   (Country = Arabic)
   Pre-requisite CSD Level:  XRA4000_
   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:   XRAM011_   (Country = Arabic)
   Pre-requisite CSD Level:  XRA4010_
   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:   XRAM011_   (Country = Arabic)
   Pre-requisite CSD Level:  XRA4010_
   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  38


                    October 7, 1999 - Warp 4 FixPak XRAM011

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

      ..\..\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
   ------------  ------------  -----  ----------  -----  -------  --------
   ARACONV.EXE   ARACONV.EX_    15    04/12/1999  15:53    62183  13A30324
   ASIACOL.DLL   ASIACOL.DL_    11    04/29/1999  09:34   158758  A60EF581
   AVIO.DLL      AVIO.DL_       14    02/03/1999  11:26    53923  811D0F32
   BACKUP.EXE    BACKUP.EX_     16    07/19/1999  11:44    28196  594E45AE
   BDIME.DLL     BDIME.DL_      16    03/25/1999  13:18    11911  53FAD67F
   BDPRTM.IMP    BDPRTM.IM_     15    04/12/1999  15:53    93440  35660361
   BE.KBL        BE.KB_         17    04/30/1999  08:52      972  F5955524
   BIDI.DLL      BIDI.DL_       16    03/11/1999  17:40    47616  D7C0C63D
   BLDLEVEL.EXE  BLDLEVEL.EX_   15    09/15/1998  11:32    43974  F7F6C354
   BOOTDISK.EXE  BOOTDISK.EX_   15    07/19/1999  11:32    60947  B165128B
   BOOTDISK.HLP  BOOTDISK.HL_   16    07/19/1999  11:32    11095  ECF855CA
   BVSCALLS.DLL  BVSCALLS.DL_   17    07/19/1999  10:38      512  92582BBF
   BY.KBL        BY.KB_         17    04/30/1999  08:52     1292  7E3BA904
   CA.KBL        CA.KB_         17    04/30/1999  08:52     1214  D3255232
   CACHE.EXE     CACHE.EX_      16    07/19/1999  11:36    11820  164D2EAE
   CARDINFO.DAT  CARDINFO.DA_   16    02/02/1999  19:41    54979  C547DE0F
   CDFS.IFS      CDFS.IF_       16    07/19/1999  10:35    45173  60EE7F68
   CDFS.TDF      CDFS.TD_       17    07/19/1999  10:35     2113  7E23DB0C
   CDROM.TBL     CDROM.TB_      17    11/12/1996  13:38     4365  F398665E
   CF.KBL        CF.KB_         17    04/30/1999  08:52      956  23E91A7E
   CHKDSK.COM    CHKDSK.CO_     14    07/19/1999  11:37    70208  B22BF419
   CHKDSK.SYS    CHKDSK.SY_     17    04/01/1999  17:10      747  11D6D4C8
   CHKDSK32.DLL  CHKDSK32.DL_    5    07/19/1999  11:37   121895  E08B864E
   CHKDSK32.EXE  CHKDSK32.EX_   17    07/19/1999  11:36     6417  441BCC60
   CLOCK01.SYS   CLOCK01.SY_    17    04/01/1999  15:46     4400  CEAE38AA
   CLOCK02.SYS   CLOCK02.SY_    17    04/01/1999  15:46     4282  6107249B
   CMD.EXE       CMD.EX_        13    07/19/1999  11:40    74296  0511DC0C
   COMM.DRV      COMM.DR_       16    03/09/1999  12:59     9552  2A77F5F2
   COMMAND.COM   COMMAND.CO_    15    07/19/1999  11:39    53375  60C4EFA7
   CONTROL.PM    CONTROL.PM_    17    05/05/1998  01:48     8474  85121A82
   COUNTRY.SYS   COUNTRY.SY_    16    03/15/1999  18:23    50947  19A8000B
   COUR.OFM      COUR.OF_       17    03/15/1999  13:45     6163  E932E21E
   COUR.PFB      COUR.PF_       10    03/15/1999  13:46   137111  48049C47
   COUR.PFM      COU1.PF_       17    03/15/1999  13:45      674  EB210968
   COURB.OFM     COURB.OF_      17    03/15/1999  13:45     6173  31304A2B
   COURB.PFB     COURB.PF_       8    03/15/1999  13:46   140829  503DA614
   COURB.PFM     COURB1.PF_     17    03/15/1999  13:45      679  1EF9DD6B
   COURBI.OFM    COURBI.OF_     17    03/15/1999  13:45     6187  0F7825D1

   
                       FixPak Corrective Service levels and disk layouts  39


                    October 7, 1999 - Warp 4 FixPak XRAM011

   COURBI.PFB    COURBI.PF_     11    03/15/1999  13:46   136240  16421E63
   COURBI.PFM    COURBI1.PF_    17    03/15/1999  13:45      685  D0390DF6
   COURI.OFM     COURI.OF_      17    03/15/1999  13:45     6178  4FCF133A
   COURI.PFB     COURI.PF_      10    03/15/1999  13:46   137394  71C135E2
   COURI.PFM     COURI1.PF_     17    03/15/1999  13:45      681  A6EEB882
   COURIER.FON   COURIER.FO_    15    04/07/1999  14:14    77826  231B9F4F
   COURIERI.FON  COURIERI.FO_   14    04/07/1999  14:09    86641  F95899C8
   CPG01256.TBL  CPG01256.TB_   17    04/12/1999  15:51    27264  221D21BE
   CREX.MSG      CREX.MS_       17    09/19/1996  15:44     2865  84FD8E0E
   CREXUTIL.DLL  CREXUTIL.DL_   15    11/20/1998  15:58    47837  2280613F
   CREXX.DLL     CREXX2.DL_     10    04/01/1999  14:20   266031  D55B2A5F
   CZ.KBL        CZ.KB_         17    04/30/1999  08:52     1014  51EE971B
   DDINSTAL.EXE  DDINSTAL.EX_   15    07/22/1999  12:14    35367  01DE737B
   DE.KBL        DE.KB_         17    04/30/1999  08:52      958  65F64883
   DE453.KBL     DE453.KB_      17    04/30/1999  08:52     1354  7C6CDDF2
   DF_DEB.EXE    DF_DEB.EX_     13    07/19/1999  10:41   135921  37C54313
   DF_RET.EXE    DF_RET.EX_     13    07/19/1999  10:41   136177  43C3BB76
   DIBDRVR.DLL   DIBDRVR.DL_    17    10/22/1997  23:20     2267  1429B272
   DICTATE.EXE   DICTATE.EX_    14    05/06/1998  11:58    51391  45FF49B4
   DICTDLL.DLL   DICTDLL.DL_    14    12/21/1997  01:28    51187  CF92C5CA
   DISPLAY.DLL   DISPLAY.DL_    15    04/07/1999  15:46    46574  82EEAA74
   DIVE.DLL      DIVE.DL_       13    09/29/1998  16:01    69640  C06FD486
   DK.KBL        DK.KB_         17    04/30/1999  08:52      928  6ADF0F9C
   DMQSPROF.DLL  DMQSPROF.DL_   15    04/07/1999  16:01    39033  EC252D39
   DOSCALL1.DLL  DOSCALL1.DL_   12    07/19/1999  10:40   124684  09547865
   DOSCALL1.SYM  DOSCALL1.SY_   15    07/19/1999  10:40    41716  53AD99C8
   DOSCALL1.TDF  DOSCALL1.TD_   17    07/19/1999  10:40     5426  6264E976
   DOSKRNL       DOSKRNL.___    16    07/19/1999  10:33    30569  2E448D22
   DRVMAP.INF    DRVMAP.IN_     17    04/03/1997  13:54    12986  0AD62B34
   DSPINSTL.EXE  DSPINSTL.EX_   12    07/19/1999  11:29   117816  B680EA23
   DSPRES.DLL    DSPRES1.DL_     7    04/07/1999  14:09   376488  FF6B63F9
   DSPRES.DLL    DSPRES.DL_      4    04/07/1999  14:09   376488  FF8AA3F9
   DTRACE.DOC    DTRACE.DO_     16    04/21/1999  10:58    75371  D5765F89
   DTRACE.EXE    DTRACE1.EX_    14    02/16/1999  10:15    48906  D9D70598
   DTRACE.EXE    DTRACE.EX_     14    02/16/1999  10:15    48906  D9D70598
   E.EXE         E.EX_           1    04/13/1999  11:03    61719  6FDA865C
   EAUTIL.EXE    EAUTIL.EX_     16    07/19/1999  11:41    37984  B4A37A31
   EJECT.EXE     EJECT.EX_      16    07/19/1999  11:46    25648  0C9E11B6
   EL.KBL        EL.KB_         17    04/30/1999  08:52     1396  A25E71EB
   EL459.KBL     EL459.KB_      17    04/30/1999  08:52     1372  6E3E5A60
   ENGINE.EXE    ENGINE.EX_      6    07/23/1997  11:39   440424  C247CBAA
   EPM.EXE       EPM.EX_        16    07/16/1998  13:18    19684  E6ED87A9
   ERLOGGER.EXE  ERLOGGER.EX_   15    02/05/1999  16:23    34320  1AAB418B
   ERRLOG.DLL    ERRLOG.DL_     13    02/05/1999  16:23    72594  6B4602A5
   ES.KBL        ES.KB_         17    04/30/1999  08:52      920  66A6BF7A
   ETKC603.DLL   ETKC603.DL_    12    12/16/1997  15:06   135759  6AF203C2
   ETKE603.DLL   ETKE603.DL_     5    05/07/1998  09:10   754050  D31EE9AF
   FDISK.COM     FDISK.CO_      14    07/19/1999  11:46   114218  89162E0F
   FDISKPM.DLL   FDISKPM.DL_    17    07/19/1999  11:46     7731  ADA7E4E9
   FDISKPM.EXE   FDISKPM.EX_    14    07/19/1999  11:46    63042  05CDFEE0
   FFST.DLL      FFST.DL_       16    04/03/1997  19:03    11425  C6365786

   
                       FixPak Corrective Service levels and disk layouts  40


                    October 7, 1999 - Warp 4 FixPak XRAM011

   FFSTCONF.EXE  FFSTCONF.EX_   13    02/05/1999  16:25    68669  6DC63C77
   FFSTPCT.EXE   FFSTPCT.EX_    13    02/05/1999  16:25    69583  194DAAD9
   FI.KBL        FI.KB_         17    04/30/1999  08:52      940  752CFEC5
   FILT.DLL      FILT.DL_       16    09/29/1998  16:10    22888  C4544636
   FKA.DLL       FKA.DL_        16    10/10/1997  01:03    13997  768EF997
   FORMAT.COM    FORMAT.CO_     15    07/19/1999  11:42    70432  8ED4F00F
   FR.KBL        FR.KB_         17    04/30/1999  08:52      950  9DA40CBA
   FSFILTER.SYS  FSFILTER.SY_   16    07/19/1999  10:41    12988  487EED31
   GDI.EXE       GDI.EX_         7    03/11/1999  18:30   580200  7D0FF0C1
   GRADD.SYS     GRADD.SY_      17    04/07/1999  17:44     1195  AF3BC4DC
   GRE2VMAN.DLL  GRE2VMAN.DL_   16    04/07/1999  17:43    17901  95F8D672
   HDMON.EXE     HDMON.EX_      13    04/13/1999  09:50    75071  9D672805
   HELPMGR.DLL   HELPMGR.DL_     8    04/13/1999  16:04   249825  55AA43A1
   HELPMSG.EXE   HELPMSG.EX_    16    07/19/1999  11:42    36256  A2EDF682
   HELV.FON      HELV.FO_       11    04/07/1999  14:14   171252  A075B461
   HELV.OFM      HELV.OF_       17    03/15/1999  13:45     6793  FF46E30D
   HELV.PFB      HELV.PF_       11    03/15/1999  13:46   120578  0DA723CF
   HELV.PFM      HELV1.PF_      17    03/15/1999  13:45     1096  C722995E
   HELVB.OFM     HELVB.OF_      17    03/15/1999  13:45     6785  94469F2F
   HELVB.PFB     HELVB.PF_      11    03/15/1999  13:46   123085  0037FB2B
   HELVB.PFM     HELVB1.PF_     17    03/15/1999  13:45     1089  9A484EA2
   HELVBI.OFM    HELVBI.OF_     17    03/15/1999  13:45     6787  4196DDD9
   HELVBI.PFB    HELVBI.PF_     11    03/15/1999  13:46   124245  46A18ABC
   HELVBI.PFM    HELVBI1.PF_    17    03/15/1999  13:45     1087  06B58D9D
   HELVI.FON     HELVI.FO_      10    04/07/1999  14:09   199523  17786C48
   HELVI.OFM     HELVI.OF_      17    03/15/1999  13:45     6772  3B3191CD
   HELVI.PFB     HELVI.PF_      11    03/15/1999  13:47   123355  48E064F0
   HELVI.PFM     HELVI1.PF_     17    03/15/1999  13:45     1079  CD475F06
   HPFS.IFS      HPFS.IF_       13    07/19/1999  11:35   141378  2E6FD07D
   HPFS.TDF      HPFS.TD_       17    04/26/1999  13:42     1620  C6DBB5AE
   HR.KBL        HR.KB_         17    04/30/1999  08:52      982  BFF8C1F1
   HU.KBL        HU.KB_         17    04/30/1999  08:52     1006  BE7552DE
   IBM1004       IBM1004.___    17    04/29/1999  09:30     3584  9B6B2753
   IBM1125       IBM1125.___    17    04/29/1999  09:31     4320  82C0CC15
   IBM1131       IBM1131.___    17    04/29/1999  09:31     4320  111E2969
   IBM1140       IBM1140.___    17    07/26/1999  13:23     2816  511E46AE
   IBM1141       IBM1141.___    17    07/26/1999  13:23     2784  51C4B993
   IBM1142       IBM1142.___    17    07/26/1999  13:23     2816  17E42197
   IBM1143       IBM1143.___    17    07/26/1999  13:23     2816  3FE17606
   IBM1144       IBM1144.___    17    07/26/1999  13:23     2784  CE079525
   IBM1145       IBM1145.___    17    07/26/1999  13:23     2784  3E0EE64E
   IBM1146       IBM1146.___    17    07/26/1999  13:23     2816  E88C76A8
   IBM1147       IBM1147.___    17    07/26/1999  13:23     2784  2336B680
   IBM1148       IBM1148.___    17    07/26/1999  13:23     2816  6101E543
   IBM1250       IBM1250.___    17    04/29/1999  09:31     3552  C4CE9667
   IBM1251       IBM1251.___    17    04/29/1999  09:31     3328  633C1B41
   IBM1252       IBM1252.___    17    04/29/1999  09:31     3552  78EC03DB
   IBM1253       IBM1253.___    17    04/29/1999  09:31     3552  719FBD08
   IBM1254       IBM1254.___    17    04/29/1999  09:31     3552  7FC54E70
   IBM1255       IBM1255.___    17    04/29/1999  09:31     3808  E705867B
   IBM1256       IBM1256.___    17    04/29/1999  09:31     4320  E73BF85E

   
                       FixPak Corrective Service levels and disk layouts  41


                    October 7, 1999 - Warp 4 FixPak XRAM011

   IBM1257       IBM1257.___    17    04/29/1999  09:31     3296  D6E0732F
   IBM813        IBM813.___     17    07/26/1999  13:24     3072  DA4A683C
   IBM850        IBM850.___     17    04/29/1999  09:31     4320  49F10734
   IBM852        IBM852.___     17    07/26/1999  13:24     4608  44C19E65
   IBM857        IBM857.___     17    04/29/1999  09:31     4352  4A7BC489
   IBM859        IBM859.___     17    07/26/1999  13:24     4320  B68FB360
   IBM862        IBM862.___     17    07/26/1999  13:24     4576  ECCF6ADB
   IBM864        IBM864.___     17    07/26/1999  13:24     4576  E55C982C
   IBM869        IBM869.___     17    07/26/1999  13:24     4320  E2D98857
   IBM923        IBM923.___     17    07/26/1999  13:24     2784  ED42AC6D
   IBM924        IBM924.___     17    07/26/1999  13:24     2784  FD6977EE
   IBMOPTNS.DLL  IBMOPTNS.DL_   16    02/02/1999  19:41    18744  DAA60B97
   ICONEDIT.EXE  ICONEDIT.EX_   12    07/19/1999  08:37   109504  ECABF8E3
   IFGDI2VM.DRV  IFGDI2VM.DR_   15    04/07/1999  16:06    92520  E82D65AD
   INST_DOS.EXE  INST_DOS.EX_   15    04/13/1999  16:02    36466  B52FE8D0
   INSTALL.EXE   INSTALL.EX_     6    07/19/1999  11:15   392814  8D1EA8D1
   IOPROC.DLL    IOPROC.DL_     15    02/03/1999  11:27    37878  1CD20161
   IS.KBL        IS.KB_         17    04/30/1999  08:52      940  F90C5854
   IS458.KBL     IS458.KB_      17    04/30/1999  08:52      928  37C485CE
   ISGDI2VM.DRV  ISGDI2VM.DR_   15    04/07/1999  16:06    91328  1CCF9230
   IT.KBL        IT.KB_         17    04/30/1999  08:52      876  59A120A0
   IT142.KBL     IT142.KB_      17    04/30/1999  08:52      854  ADAD10FB
   KERNEL.SDF    KERNEL.SD_     15    11/07/1996  21:11   467330  06CC86A1
   KERNELD.SDF   KERNELD.SD_    15    11/07/1996  21:12   468657  3CC5754F
   KEYBOARD.DCP  KEYBOARD.DC_   16    03/25/1999  14:34   315109  14E81503
   KRNLBDEV.TDF  KRNLBDEV.TD_   17    07/19/1999  10:32     3703  DF4A5591
   KRNLBFS.TDF   KRNLBFS.TD_    17    07/19/1999  10:32     4464  53A6B960
   KRNLBLDR.TDF  KRNLBLDR.TD_   17    07/19/1999  10:33     5581  D602A875
   KRNLBPG.TDF   KRNLBPG.TD_    17    07/19/1999  10:33     3203  02DB0917
   KRNLBSEL.TDF  KRNLBSEL.TD_   17    07/19/1999  10:33     2727  A361A83B
   KRNLBSEM.TDF  KRNLBSEM.TD_   17    07/19/1999  10:33     1792  30CF5822
   KRNLBSM.TDF   KRNLBSM.TD_    17    07/19/1999  10:33     1321  51F2F03F
   KRNLBTK.TDF   KRNLBTK.TD_    17    07/19/1999  10:33    14363  388373CF
   KRNLBTOM.TDF  KRNLBTOM.TD_   17    07/19/1999  10:33      925  AF6E9864
   KRNLBVDM.TDF  KRNLBVDM.TD_   17    07/19/1999  10:33    13917  BBAC1C8F
   KRNLBVM.TDF   KRNLBVM.TD_    17    07/19/1999  10:33     5514  0ED68AC5
   KRNLDDEV.TDF  KRNLDDEV.TD_   17    07/19/1999  10:31     3678  B6225382
   KRNLDFS.TDF   KRNLDFS.TD_    17    07/19/1999  10:31     4355  69E29EB9
   KRNLDLDR.TDF  KRNLDLDR.TD_   17    07/19/1999  10:31     5609  6E34A150
   KRNLDPG.TDF   KRNLDPG.TD_    17    07/19/1999  10:31     3284  3D295190
   KRNLDSEL.TDF  KRNLDSEL.TD_   17    07/19/1999  10:32     2814  1D2C1922
   KRNLDSEM.TDF  KRNLDSEM.TD_   17    07/19/1999  10:32     1932  04AC9712
   KRNLDSM.TDF   KRNLDSM.TD_    17    07/19/1999  10:32     1321  ADB0D814
   KRNLDTK.TDF   KRNLDTK.TD_    17    07/19/1999  10:32    14394  E7EFFA9C
   KRNLDTOM.TDF  KRNLDTOM.TD_   17    07/19/1999  10:32      953  15AEAB78
   KRNLDVDM.TDF  KRNLDVDM.TD_   17    07/19/1999  10:31    13992  3CC19339
   KRNLDVM.TDF   KRNLDVM.TD_    17    07/19/1999  10:32     5601  6625FE56
   KRNLRDEV.TDF  KRNLRDEV.TD_   17    07/19/1999  10:30     3703  DC1FA0B7
   KRNLRFS.TDF   KRNLRFS.TD_    17    07/19/1999  10:30     4464  6DBD8831
   KRNLRLDR.TDF  KRNLRLDR.TD_   17    07/19/1999  10:30     5581  14B92781
   KRNLRPG.TDF   KRNLRPG.TD_    17    07/19/1999  10:30     3203  077AEA16

   
                       FixPak Corrective Service levels and disk layouts  42


                    October 7, 1999 - Warp 4 FixPak XRAM011

   KRNLRSEL.TDF  KRNLRSEL.TD_   17    07/19/1999  10:30     2727  48035960
   KRNLRSEM.TDF  KRNLRSEM.TD_   17    07/19/1999  10:30     1792  C89F90A7
   KRNLRSM.TDF   KRNLRSM.TD_    17    07/19/1999  10:30     1321  D9D73750
   KRNLRTK.TDF   KRNLRTK.TD_    17    07/19/1999  10:30    14279  2248F7C9
   KRNLRTOM.TDF  KRNLRTOM.TD_   17    07/19/1999  10:30      897  A506FC5D
   KRNLRVDM.TDF  KRNLRVDM.TD_   17    07/19/1999  10:30    13749  59465A34
   KRNLRVM.TDF   KRNLRVM.TD_    17    07/19/1999  10:30     5514  26A3BCFD
   LIBCM.DLL     LIBCM.DL_       9    04/08/1999  16:09   210916  98DAC306
   LIBCN.DLL     LIBCN.DL_      14    04/08/1999  16:08    57340  7BBE3105
   LIBCS.DLL     LIBCS.DL_      10    04/08/1999  16:08   192386  978D3E9F
   LIBUNI.DLL    LIBUNI.DL_     14    04/30/1999  11:00    81372  89A66834
   LOCALE.DLL    LOCALE.DL_     13    04/30/1999  08:52   107901  9ACCD12E
   MAIN.CPL      MAIN.CP_        9    03/11/1999  18:47   351738  4C7BC3E6
   MAKETSF.EXE   MAKETSF.EX_     6    04/01/1999  14:39    37516  94D71533
   MAPTSF.CMD    MAPTSF.CM_     17    04/01/1999  14:23    16803  0FFD489E
   MIDI.SYS      MIDI.SY_       16    03/16/1999  10:29    26328  FA7BB5A8
   MIDIMCD.DLL   MIDIMCD.DL_    17    09/29/1998  16:02      532  40B1F3FB
   MIGRATE.EXE   MIGRATE.EX_    12    07/19/1999  11:28   118313  999C3A59
   MINSTALL.EXE  MINSTALL.EX_   11    02/02/1999  19:41   152580  84E992F2
   MINXOBJ.DLL   MINXOBJ.DL_    15    04/13/1999  10:27    31778  80E6E488
   MIRRORS.DLL   MIRRORS.DL_     6    09/19/1996  15:53   444744  4D936F0C
   MMODPTS.DLL   MMODPTS.DL_     3    09/29/1998  14:42   184020  4C87AB95
   MMPARTS.DLL   MMPARTS.DL_     2    09/29/1998  16:13  1532250  AA3EBDC4
   MMPM.DLL      MMPM.DL_        6    02/02/1999  19:46   431781  5F4F04BD
   MMPTMRI.DLL   MMPTMRI.DL_    12    02/02/1999  18:35   227344  BDDD3E9B
   MMSOUND.DRV   MMSOUND.DR_    17    03/11/1999  19:03     3456  41B26138
   MONCALLS.DLL  MONCALLS.DL_   17    07/19/1999  10:37     2472  AA21596D
   MONCALLS.TDF  MONCALLS.TD_   17    07/19/1999  10:37     1139  6AB0C33C
   MPGIO.DLL     MPGIO.DL_      14    02/03/1999  11:27    59267  4C29334D
   NAMEADD.EXE   NAMEADD.EX_    16    05/10/1999  09:32    23040  FA0DD0A5
   NAMECOPY.EXE  NAMECOPY.EX_   16    05/10/1999  09:32    23040  DBBA8851
   NAMECSSP.DLL  NAMECSSP.DL_   14    01/06/1998  17:11    61123  E0DF6016
   NAMEDEL.EXE   NAMEDEL.EX_    16    05/10/1999  09:32    23040  220DD0A7
   NAMEDSP.DLL   NAMEDSP.DL_    12    01/06/1998  17:11   123427  2AA06CC6
   NAMEEXT.EXE   NAMEEXT.EX_    16    05/10/1999  09:32    23040  5A0DD0A9
   NAMEFT.DLL    NAMEFT.DL_     14    01/06/1998  17:11    66274  19FE0D65
   NAMEFW.DLL    NAMEFW.DL_     13    01/06/1998  17:11    72312  3F959646
   NAMEINFO.DLL  NAMEINFO.DL_   14    01/06/1998  17:11    47973  68541BA6
   NAMEINI.DLL   NAMEINI.DL_    14    01/06/1998  17:11    59027  FAF4B3FE
   NAMEMOD.EXE   NAMEMOD.EX_    16    05/10/1999  09:32    23040  0A0DD0A7
   NAMEMOVE.EXE  NAMEMOVE.EX_   16    05/10/1999  09:32    23040  E3BA884F
   NAMEOSP.DLL   NAMEOSP.DL_    14    01/06/1998  17:11    52725  EA34508A
   NL.KBL        NL.KB_         17    04/30/1999  08:52      954  758BA4B8
   NO.KBL        NO.KB_         17    04/30/1999  08:52      920  137D4FE6
   NWIAPI.DLL    NWIAPI.DL_     16    04/13/1999  10:36    14768  8407D55F
   OREXUTIL.DLL  ORXUTIL2.DL_   15    11/20/1998  15:58    32797  2A5A4EBD
   OREXX.DLL     OREXX2.DL_      7    11/20/1998  15:58   446245  1B2A536B
   OS2CHAR.TDF   OS2CHAR.TD_    17    07/19/1999  10:40    13889  38274652
   OS2DASD.DMD   OS2DASD.DM_    16    03/22/1999  16:59    40876  0451B0A5
   OS2DUMP       OS2DUMP.___    16    04/07/1999  10:27    17425  F01D2D20
   OS2K386.EXE   OS2K386.EX_    14    03/11/1999  18:33    80306  8BEED240

   
                       FixPak Corrective Service levels and disk layouts  43


                    October 7, 1999 - Warp 4 FixPak XRAM011

   OS2KRNL       OS2KRNL.___     3    07/19/1999  10:31   634333  E0BA46C8
   OS2KRNL.TDF   OS2KRNL.TD_    17    07/19/1999  10:30    16581  ECF2EEF9
   OS2KRNLD.SYM  OS2KRNLD.SY_   12    07/19/1999  10:31   186132  9D4ED370
   OS2KRNLR.SYM  OS2KRNLR.SY_   12    07/19/1999  10:30   163284  AE773204
   OS2LDR.MSG    OS2LDR.MS_     17    07/19/1999  10:23     8368  A55FC233
   OS2MM.DLL     OS2MM.DL_       9    02/02/1999  19:41   219650  AD7890CC
   OS2NS.EXE     OS2NS.EX_      15    01/06/1998  17:32    44964  61548A06
   OS2UGL        OS2UGL.___     17    04/29/1999  09:31    15616  4D835ECE
   OS2UGLG       OS2UGLG.___    17    12/12/1997  22:59     8928  AA89831E
   OSO001.MSG    OSO001.MS_     14    07/16/1999  17:28   179413  C4F7F21E
   OSO001H.MSG   OSO001H.MS_    13    07/16/1999  17:28   241617  C078073E
   PARALLEL.PDR  PARALLEL.PD_   16    04/13/1999  10:56    15848  FDDC9DA6
   PCMCIA.TBL    PCMCIA.TB_     17    07/24/1998  12:34     5114  E4E2485A
   PDUMPSYS.EXE  PDUMPSYS.EX_   15    04/13/1999  09:50    34877  C4D753E7
   PDUMPUSR.EXE  PDUMPUSR.EX_   15    04/13/1999  09:50    34875  6C37F546
   PICV.DLL      PICV.DL_       16    04/13/1999  16:02    26200  C8F7662B
   PICVIEW.DLL   PICVIEW.DL_    16    04/13/1999  16:02    10786  1ED9C9A1
   PICVIEW.EXE   PICVIEW.EX_    14    04/13/1999  16:02    69146  5E8A2516
   PL.KBL        PL.KB_         17    04/30/1999  08:53      980  F0765642
   PL457.KBL     PL457.KB_      17    04/30/1999  08:53      882  CF0B4E0A
   PMATM.DLL     PMATM.DL_       9    03/15/1999  18:36   224319  71C7F565
   PMBIDI.DLL    PMBIDI.DL_     16    04/12/1999  15:52    12352  10E87CC0
   PMCHKDSK.DLL  PMCHKDSK.DL_   17    07/19/1999  11:47     4127  4C9F8005
   PMCHKDSK.EXE  PMCHKDSK.EX_   16    07/19/1999  11:47    28183  FFCE1BD8
   PMCLIP.DLL    PMCLIP.DL_     16    10/22/1997  23:19    21295  2FE91E38
   PMCTLS.DLL    PMCTLS.DL_      4    08/04/1999  08:44   584870  9A9DB31D
   PMCTLS.SYM    PMCTLS.SY_     16    08/04/1999  08:44    44084  E997E6A6
   PMDDE.DLL     PMDDE.DL_      16    04/13/1999  16:05    28334  F294941A
   PMDDEML.DLL   PMDDEML.DL_    16    04/13/1999  15:40    27710  60965C59
   PMDF.EXE      PMDF.EX_        8    04/13/1999  09:49   263480  B682ACA8
   PMDFMSG.DLL   PMDFMSG.DL_    15    02/05/1999  16:26    44240  C0BFAB8D
   PMDRAG.DLL    PMDRAG.DL_     17    05/05/1999  14:00     1731  801F3520
   PMGPI.DLL     PMGPI.DL_       9    04/13/1999  15:37   229146  10D24DA4
   PMGPI.TDF     PMGPI.TD_      17    04/13/1999  15:37    12338  FD344EBE
   PMGRE.DLL     PMGRE.DL_      17    04/13/1999  15:36     2231  B20E2F7F
   PMGRE.TDF     PMGRE.TD_      17    09/17/1999  14:51     1062  392330F0
   PMMERGE.DLL   PMMERGE.DL_     1    09/17/1999  14:51  1255021  01F5BD31
   PMMERGE.SYM   PMMERGE.SY_    11    09/17/1999  14:50   115412  BF0E17DA
   PMMLE.DLL     PMMLE.DL_      17    05/05/1999  14:02      673  4C270A0D
   PMPIC.DLL     PMPIC.DL_      15    04/13/1999  16:02    47206  D0411841
   PMPIC.TDF     PMPIC.TD_      17    05/05/1999  14:13      400  AAA319FB
   PMPRINT.QPR   PMPRINT.QP_    16    04/13/1999  10:36    11833  87DF5DC4
   PMSDMRI.DLL   PMSDMRI.DL_    16    04/13/1999  15:44    13312  10BBAF4D
   PMSEEK.EXE    PMSEEK.EX_     16    07/19/1999  11:47    31285  4DDE1A86
   PMSHAPI.DLL   PMSHAPI.DL_    17    10/22/1997  22:53     4549  7AE93081
   PMSHAPI.TDF   PMSHAPI.TD_    17    09/17/1999  14:51     6726  53109D34
   PMSPL.DLL     PMSPL.DL_       8    04/13/1999  10:35   277033  B981E25E
   PMSPL.SYM     PMSPL.SY_      16    04/13/1999  10:35    32260  D04D12A0
   PMSPL.TDF     PMSPL.TD_      17    04/13/1999  10:35     4491  AC4E7DE4
   PMVDMP.DLL    PMVDMP.DL_     15    09/17/1999  14:59    42867  D9E471AE
   PMVDMP.TDF    PMVDMP.TD_     17    09/17/1999  14:59     2661  B120E353

   
                       FixPak Corrective Service levels and disk layouts  44


                    October 7, 1999 - Warp 4 FixPak XRAM011

   PMVIOP.DLL    PMVIOP.DL_     14    09/17/1999  14:58    58958  265BA7AC
   PMVIOP.SYM    PMVIOP.SY_     17    09/17/1999  14:58     6628  6434FD17
   PMVIOP.TDF    PMVIOP.TD_     17    09/17/1999  14:58     3551  24D85541
   PMWIN.DLL     PMWIN.DL_      17    04/13/1999  15:38    11264  93A2E194
   PMWIN.TDF     PMWIN.TD_      17    09/17/1999  14:51     9567  54B4BAFE
   PMWIN32.SDF   PMWIN32.SD_    15    10/28/1997  18:56   299617  47F639A5
   PMWINX.DLL    PMWINX.DL_      5    04/13/1999  16:02   530279  3A004321
   PMWP.DLL      PMWP.DL_        3    04/13/1999  10:22   926615  751DC152
   PMWP.SYM      PMWP.SY_       13    04/13/1999  10:22   100420  2711F96A
   PMWP.TDF      PMWP.TD_       17    04/13/1999  10:22    13825  32CE568D
   PMWPMRI.DLL   PMWPMRI.DL_    15    04/13/1999  10:23    54821  E3C815F0
   PO.KBL        PO.KB_         17    04/30/1999  08:53      926  8FD4CA89
   PROCDUMP.DOC  PROCDUMP.DO_   16    04/01/1999  14:23    62765  B74B1E35
   PROCDUMP.EXE  PROCDUMP.EX_   15    04/13/1999  09:50    47135  A1E0A208
   PROGMAN.EXE   PROGMAN.EX_    13    03/11/1999  18:43   159264  0D5DCB99
   PRTDRV.EXE    PRTDRV.EX_     15    07/28/1998  17:32    57951  98CDF971
   PSSDMON.EXE   PSSDMON.EX_    16    04/06/1999  17:06    27117  A48B4E88
   PSTAT.EXE     PSTAT.EX_       4    07/19/1999  11:43    11731  50D86261
   QUECALLS.DLL  QUECALLS.DL_   17    07/19/1999  10:37     1024  BE89EA51
   QUECALLS.TDF  QUECALLS.TD_   17    07/19/1999  10:40     1287  980F9D53
   RAS001.MSG    RAS001.MS_     16    07/23/1997  18:57    25739  52573E1C
   RASH.MSG      RASH.MS_       17    07/23/1997  18:47    11581  598AA877
   README.CID    README.CI_     16    07/16/1999  17:21    60401  F6778C8C
   README.DBG    README.DB_     17    02/15/1999  09:00    22967  127E9036
   REGCONV.EXE   REGCONV.EX_    15    05/10/1999  09:11    39446  26689A76
   REGEDIT.HLP   REGEDIT.HL_    16    03/11/1999  20:30    22682  BCFF2549
   REGEDIT2.EXE  REGEDIT2.EX_    4    05/10/1999  09:21   950272  20AFE229
   REGISTRY.DLL  REGISTRY.DL_   15    05/10/1999  09:11    81440  CA8317D9
   REGISTRY.MSG  REGISTRY.MS_   17    05/10/1999  09:21      629  E72A36D8
   REGISTRY.TDF  REGISTRY.TD_   17    05/10/1999  09:11     7591  E2A548D1
   REPLACE.EXE   REPLACE.EX_    16    07/19/1999  11:48    37995  93E4446C
   RESTORE.EXE   RESTORE.EX_    16    07/19/1999  11:48    36256  5C008CC2
   REX.MSG       REX.MS_        17    09/19/1996  15:44     2865  6725D657
   REXX.DLL      CREXX1.DL_     10    04/01/1999  14:20   266031  5E688B8E
   REXX.DLL      OREXX1.DL_      7    11/20/1998  15:58   446245  92847558
   REXX.IMG      REXX.IM_       13    11/20/1998  15:58   275420  034B1863
   REXXAPI.DLL   REXXAPI.DL_    16    07/23/1998  15:54    29603  057F1B73
   REXXC.EXE     REXXC.EX_      17    03/31/1997  17:35     1980  EB392AB2
   REXXCRT.DLL   REXXCRT.DL_    14    03/31/1997  17:35    61195  D865CF3E
   REXXUTIL.DLL  REXXUTIL.DL_   14    11/20/1998  15:58    47837  22A11D3F
   REXXUTIL.DLL  ORXUTIL1.DL_   15    11/20/1998  15:58    32797  2AC4C23D
   RINSTPRN.EXE  RINSTPRN.EX_   10    04/13/1999  11:09   194722  B8E9C8D0
   RO.KBL        RO.KB_         17    04/30/1999  08:53      944  0E4407AD
   RSPDDI.EXE    RSPDDI.EX_     16    07/19/1999  11:23    22073  7D60E6FA
   RSPDSPI.EXE   RSPDSPI.EX_    13    07/19/1999  11:29    95352  3ED8BB3D
   RSPINST.EXE   RSPINST.EX_     8    07/19/1999  11:12   428848  9EA50872
   RSRV.EXE      RSRV.EX_       13    01/06/1998  17:32    78051  642067F1
   RU.KBL        RU.KB_         17    04/30/1999  08:53     1144  09E78387
   SCENTER.DLL   SCENTER.DL_     8    04/13/1999  10:58   291373  7FC1F608
   SD.KBL        SD.KB_         17    04/30/1999  08:53     1036  23806109
   SEAMLESS.DLL  SEAMLESS.DL_   15    09/17/1999  14:59    49679  7EE6649A

   
                       FixPak Corrective Service levels and disk layouts  45


                    October 7, 1999 - Warp 4 FixPak XRAM011

   SECUTIL.DLL   SECUTIL.DL_    16    04/01/1999  14:34    21468  C9F6B616
   SEINST.EXE    SEINST.EX_     15    07/19/1999  10:43    37441  E7C4B546
   SEMAINT.EXE   SEMAINT.EX_    15    07/19/1999  10:43    67376  B74E8823
   SERIAL.PDR    SERIAL.PD_     16    04/13/1999  10:27    19060  597E0C63
   SESAPI.DLL    SESAPI.DL_     16    04/13/1999  09:40    24283  FD1EECE1
   SESDD32.SYS   SESDD32.SY_    14    04/13/1999  14:44   118832  167EDEE9
   SESMGR.DLL    SESMGR.DL_     17    07/19/1999  10:35     1536  46610705
   SESMGR.TDF    SESMGR.TD_     17    07/19/1999  10:40     1877  5E49ABC2
   SETBOOT.EXE   SETBOOT.EX_     2    07/19/1999  11:45    17196  5C98CE25
   SETDEFV.CMD   SETDEFV.CM_    17    06/23/1998  16:25     1652  AA7ED9EC
   SF.KBL        SF.KB_         17    04/30/1999  08:53     1036  66248BC1
   SK.KBL        SK.KB_         17    04/30/1999  08:53     1008  664CAD60
   SL.KBL        SL.KB_         17    04/30/1999  08:53      982  8C23B0F9
   SOFTDRAW.DLL  SOFTDRAW.DL_    8    04/13/1999  15:30   401003  FDB06A84
   SOM.DLL       SOM.DL_        13    08/13/1996  09:29    88763  78038014
   SPCHOBJ.DLL   SPCHOBJ.DL_    12    12/21/1997  01:27   132899  E38BF817
   SPL1B.DLL     SPL1B.DL_      17    04/13/1999  10:35     5077  0353DE3C
   SQ.KBL        SQ.KB_         17    04/30/1999  08:53      824  47E3192C
   SSM.DLL       SSM.DL_        17    09/29/1998  16:01     1556  382C75A8
   SSMDD.SYS     SSMDD.SY_      16    09/29/1998  16:09    36813  739AF02E
   STRACE.EXE    STRACE.EX_     15    07/19/1999  11:49    40318  713B3B16
   SV.KBL        SV.KB_         17    04/30/1999  08:53      946  A11A1019
   SVMC.DLL      SVMC.DL_       13    02/03/1999  11:25    98389  B3501172
   SVSH.DLL      SVSH.DL_       16    02/03/1999  11:26    23452  6C7078C9
   SW.DLL        SW.DL_         14    02/03/1999  11:25    66503  8FE319CA
   SWITCHRX.CMD  SWITCHRX.CM_   17    05/06/1998  16:31     7928  79CA9FC4
   SYMB.PFM      SYMB1.PF_      17    03/15/1999  13:45      679  F258E0BD
   SYSDUMP.EXE   SYSDUMP.EX_    16    04/13/1999  12:10    16000  8605F03F
   SYSINST2.EXE  SYSINST2.EX_   12    07/19/1999  11:17   184512  D2727603
   SYSINSTX.COM  SYSINSTX.CO_   16    07/19/1999  11:43    39472  1883AD33
   SYSLEVEL.EXE  SYSLEVEL.EX_   10    07/19/1999  10:42    42848  23823FCC
   SYSLEVEL.FPK  SYSLEVEL.FP_   17    05/13/1999  12:30      165  11379A28
   SYSLOGPM.EXE  SYSLOGPM.EX_   12    02/05/1999  16:23   138955  13A55A4E
   SYSMONO.FON   SYSMONO.FO_    16    04/07/1999  15:05    21294  3D0CCA31
   SYSMONOI.FON  SYSMONOI.FO_   16    04/07/1999  14:09    35841  F038FB2C
   SYSSPLIT.CMD  SYSSPLIT.CM_   17    12/02/1998  16:25     3712  A35A41C8
   SYSTEM.TDF    SYSTEM.TD_     17    09/25/1998  12:06    18358  35415CA8
   SYSTEM.TFF    SYSTEM.TF_     16    09/25/1998  12:06    45067  C09E1523
   SYSTEMD.TFF   SYSTEMD.TF_    16    09/25/1998  12:06    45067  FE173666
   TDFLST.CMD    TDFLST.CM_     17    12/02/1998  16:25    13564  A45F3592
   TEDIT.EXE     TEDIT.EX_      16    07/19/1999  11:48     9390  6F62F81F
   TEDIT.HLP     TEDIT.HL_      17    07/19/1999  11:48    14596  59E1376F
   TESTCFG.SYS   TESTCFG.SY_    16    03/22/1999  17:28     9808  6A65FD45
   TEXTCON1.EXE  TEXTCON1.EX_   15    03/25/1999  13:18    34067  EFB64F79
   TFFLST.CMD    TFFLST.CM_     17    12/02/1998  16:25     4638  2AFE15D2
   TIMES.FON     TIMES.FO_      11    04/07/1999  14:14   166150  532CB4D1
   TIMESI.FON    TIMESI.FO_     11    04/07/1999  14:09   181173  DFD253CC
   TNR.OFM       TNR.OF_        17    03/15/1999  13:45     6809  33F5154C
   TNR.PFB       TNR.PF_        10    03/15/1999  13:46   145785  BD752E3E
   TNR.PFM       TNR1.PF_       17    03/15/1999  13:45     1103  4811CE38
   TNRB.OFM      TNRB.OF_       17    03/15/1999  13:45     6825  36C2110D

   
                       FixPak Corrective Service levels and disk layouts  46


                    October 7, 1999 - Warp 4 FixPak XRAM011

   TNRB.PFB      TNRB.PF_       10    03/15/1999  13:47   148564  014EE100
   TNRB.PFM      TNRB1.PF_      17    03/15/1999  13:45     1112  6044C543
   TNRBI.OFM     TNRBI.OF_      17    03/15/1999  13:45     6839  8F51C7B5
   TNRBI.PFB     TNRBI.PF_      10    03/15/1999  13:47   159652  81973739
   TNRBI.PFM     TNRBI1.PF_     17    03/15/1999  13:45     1118  690A75CD
   TNRI.OFM      TNRI.OF_       17    03/15/1999  13:45     6830  23B86C92
   TNRI.PFB      TNRI.PF_        9    03/15/1999  13:47   157010  5E813D84
   TNRI.PFM      TNRI1.PF_      17    03/15/1999  13:45     1114  CA6E659D
   TR.KBL        TR.KB_         17    04/30/1999  08:53      962  39746498
   TR440.KBL     TR440.KB_      17    04/30/1999  08:53     1042  9478BFDA
   TRACE.DOC     TRACE.DO_      16    04/01/1999  16:21    64057  45DDD8C5
   TRACE.EXE     TRACE.EX_      15    07/19/1999  11:48    35136  427651C0
   TRACEDLL.DLL  TRACEDLL.DL_   15    12/02/1998  16:35    44551  B988DF4C
   TRACEFMT.EXE  TRACEFMT.EX_   11    07/19/1999  11:49   156569  0E770F2D
   TRACEGET.EXE  TRACGET1.EX_   16    04/13/1999  09:46    22026  F16A3EEB
   TRACEGET.EXE  TRACEGET.EX_   16    04/13/1999  09:46    22026  F16A3EEB
   TRAPDUMP.EXE  TRAPDUMP.EX_   16    04/13/1999  09:50    23068  4C281BDE
   TRAPLOG.EXE   TRAPLOG.EX_    16    04/13/1999  12:10    15056  DE99A8A2
   TRC0000.TFF   TRC0000.TF_    17    11/24/1998  09:09      189  0EDB257E
   TRC0001.TFF   TRC0001.TF_    17    05/10/1999  09:11    17168  E6522B9A
   TRC0003.TFF   TRC0003.TF_    17    12/12/1996  17:56     1503  3435868F
   TRC0004.TFF   TRC0004.TF_    17    11/24/1998  09:09     4754  E52D826B
   TRC0005.TFF   TRC0005.TF_    16    07/19/1999  10:32    38713  35BFABDC
   TRC0006.TFF   TRC0006.TF_    17    12/12/1996  17:19    12356  B2A0674E
   TRC0007.TFF   TRC0007.TF_    17    03/22/1999  16:59     1394  9B7822C9
   TRC0008.TFF   TRC0008.TF_    17    03/22/1999  16:57      544  451196D2
   TRC0010.TFF   TRC0010.TF_    17    07/19/1999  10:40    13359  3D08217F
   TRC0012.TFF   TRC0012.TF_    17    07/19/1999  10:37     1247  1801F7BD
   TRC0016.TFF   TRC0016.TF_    17    07/19/1999  10:40     1663  A66BC2BB
   TRC0017.TFF   TRC0017.TF_    17    07/19/1999  10:40     5561  FEB3BCE2
   TRC0018.TFF   TRC0018.TF_    17    07/19/1999  10:40    39488  3B26135D
   TRC006D.TFF   TRC006D.TF_    17    06/23/1998  19:40    24181  FB8B4954
   TRC00C0.TFF   TRC00C0.TF_    17    09/17/1999  14:51    15970  F3A2FC65
   TRC00C2.TFF   TRC00C2.TF_    16    09/17/1999  14:51    25991  CC93DB04
   TRC00C3.TFF   TRC00C3.TF_    17    09/17/1999  14:51     3984  BEEF4A99
   TRC00C4.TFF   TRC00C4.TF_    17    05/05/1999  14:13      288  625BDDA4
   TRC00C5.TFF   TRC00C5.TF_    16    04/13/1999  15:37    32994  870A02D8
   TRC00C6.TFF   TRC00C6.TF_    17    04/13/1999  10:35     7146  F49BE5AD
   TRC0100.TFF   TRC0100.TF_    17    07/19/1999  10:32     6190  B1E78360
   TRC0101.TFF   TRC0101.TF_    17    07/19/1999  10:32     7422  5FFD56C6
   TRC0102.TFF   TRC0102.TF_    16    07/19/1999  10:33    25895  65D413B6
   TRC0103.TFF   TRC0103.TF_    17    07/19/1999  10:33    10057  C08742AC
   TRC0104.TFF   TRC0104.TF_    17    07/19/1999  10:33     5135  C63FECE8
   TRC0105.TFF   TRC0105.TF_    16    07/19/1999  10:33    28049  AE82A9B2
   TRC0106.TFF   TRC0106.TF_    17    07/19/1999  10:33     1835  B1FAB0DD
   TRC0107.TFF   TRC0107.TF_    17    07/19/1999  10:33     4403  9731823A
   TRC0108.TFF   TRC0108.TF_    17    07/19/1999  10:33     9456  FD1C0640
   TRC0109.TFF   TRC0109.TF_    17    07/19/1999  10:33     2535  CF7C9D90
   TRC010A.TFF   TRC010A.TF_    11    07/19/1999  10:33     1029  FDEB5C7A
   TRC0118.TFF   TRC0118.TF_    17    04/26/1999  13:43     2526  46EFF705
   TRC0119.TFF   TRC0119.TF_    17    07/19/1999  10:35     3786  6E0F14CC

   
                       FixPak Corrective Service levels and disk layouts  47


                    October 7, 1999 - Warp 4 FixPak XRAM011

   TRC012C.TFF   TRC012C.TF_    17    09/17/1999  14:59     5361  796B9315
   TRC012D.TFF   TRC012D.TF_    17    09/17/1999  14:58     7870  F9F5F184
   TRC012E.TFF   TRC012E.TF_    17    04/13/1999  10:22    32972  8DB44A12
   TRCFORMT.DLL  TRCFORMT.DL_   16    07/19/1999  11:49    26645  34A62B09
   TRCUST.EXE    TRCUST.EX_     14    07/19/1999  11:49    99285  7AA60F76
   TRSPOOL.DOC   TRSPOOL.DO_    17    04/01/1999  14:23     6638  7C5EE1B2
   TRSPOOL.EXE   TRSPOOL1.EX_   16    02/05/1999  16:23    27982  7BD31091
   TRSPOOL.EXE   TRSPOOL.EX_    16    02/05/1999  16:23    27982  7BD31091
   TRSTOP.EXE    TRSTOP.EX_     16    02/16/1999  10:14    17190  A6320EAB
   TRUETYPE.DLL  TRUETYPE.DL_   12    03/15/1999  18:36   128695  E483A9B8
   UA.KBL        UA.KB_         17    04/30/1999  08:53     1476  1B0EFF78
   UCDFS.DLL     UCDFS.DL_      14    07/19/1999  10:34    13264  95290D3A
   UCONV.DLL     UCONV.DL_      16    04/30/1999  08:52    22819  E68668CF
   UHPFS.DLL     UHPFS.DL_      14    07/19/1999  11:37   104976  3ABCC189
   UK.KBL        UK.KB_         17    04/30/1999  08:53      816  2975CFB1
   UK168.KBL     UK168.KB_      17    04/30/1999  08:53      850  35C8F2AE
   ULSACT01.MSG  ULSACT01.MS_    7    04/29/1999  09:32      907  D76AF4D3
   ULSCAU01.MSG  ULSCAU01.MS_    6    04/29/1999  09:32      899  5E1112BC
   ULSDET01.MSG  ULSDET01.MS_    3    04/29/1999  09:32      903  748763DC
   ULSERR01.MSG  ULSERR01.MS_   17    04/29/1999  09:32     1967  81C19C9D
   UNINSTAL.EXE  UNINSTAL.EX_   13    07/19/1999  11:27    99593  6E716398
   UNPACK2.EXE   UNPACK2.EX_    14    07/19/1999  11:34    79936  FEE12059
   USER.EXE      USER.EX_        9    03/11/1999  18:57   314560  BAE1B99D
   USINTER.KBL   USINTER.KB_    17    04/30/1999  08:53     1032  5CC52AE9
   VBIOS.SYS     VBIOS.SY_      17    07/19/1999  11:50     8816  9409ED6A
   VCMOS.SYS     VCMOS.SY_      17    07/19/1999  11:50     2272  C7B68EC7
   VDMA.SYS      VDMAPS2.SY_    16    07/19/1999  11:50    14329  D644B6E0
   VDMA.SYS      VDMAAT.SY_     16    07/19/1999  11:50    11465  732C54B5
   VDPMI.SYS     VDPMI.SY_      16    07/19/1999  11:50    30624  C2E1CF9F
   VDPX.SYS      VDPX.SY_       16    07/19/1999  11:51    26112  E2F5202E
   VGA.DSP       VGA.DS_        17    07/22/1999  12:32     3094  4E02E174
   VIEW.EXE      VIEW.EX_       16    04/13/1999  16:04    26828  6911B747
   VIOCALLS.DLL  VIOCALLS.DL_   17    09/25/1998  11:16     2048  0BA643CA
   VIOTBL.DCP    VIOTBL.DC_     15    03/29/1999  17:14   225355  40A5689E
   VIOTBL.ISO    VIOTBL.IS_     15    04/29/1999  09:34   230105  25D0D21C
   VMAN.DLL      VMAN.DL_       16    04/07/1999  21:39    26637  EC69F3C3
   VMANWIN.SYS   VMANWIN.SY_    17    04/07/1999  17:40     3024  BCD10A9A
   VPICPARM.SYS  VPICPARM.SY_    9    07/19/1999  11:52      736  ACAD1DBC
   VTIMER.SYS    VTIMER.SY_     17    07/19/1999  11:52     9936  384D9648
   VW32S.SYS     VW32S.SY_      16    04/01/1999  17:26    18336  B5D35004
   VWIN.SYS      VWIN.SY_       16    07/19/1999  11:52    27088  59689817
   WCFGMRI.DLL   WCFGMRI.DL_    17    07/23/1998  19:04     2596  B73786AA
   WD24B.DSP     WD24B.DS_      16    11/12/1996  13:42    12051  02A75248
   WINCFG.DLL    WINCFG.DL_     16    04/13/1999  10:27    12839  E21E0F7A
   WINFILE.EXE   WINFILE.EX_    12    03/11/1999  18:45   225408  CA3A23D0
   WINSCLIP.DLL  WINSCLIP.DL_   16    03/09/1999  11:38    14848  A63E042A
   WINSDDE.DLL   WINSDDE.DL_    16    03/09/1999  11:38    18432  A77BAF73
   WINSHELD.EXE  WINSHELD.EX_   16    03/09/1999  11:38    22016  10F12B78
   WINSMSG.DLL   WINSMSG.DL_    16    03/09/1999  11:37    28441  091BB9DC
   WPCLS.IMP     WPCLS.IM_      17    03/31/1997  17:35     8661  DA24BBC2
   WPCONFIG.DLL  WPCONFIG.DL_    9    04/13/1999  10:27   246078  626F15F6

   
                       FixPak Corrective Service levels and disk layouts  48


                    October 7, 1999 - Warp 4 FixPak XRAM011

   WPCONMRI.DLL  WPCONMRI.DL_   16    07/23/1998  19:04    27694  4487233F
   WPHELP.HLP    WPHELP.HL_      5    10/07/1999  13:32   841366  87FE70F9
   WPINET.DLL    WPINET.DL_     13    04/13/1999  10:55   115384  D7CE9EBA
   WPMSG.HLP     WPMSG.HL_      15    10/07/1999  13:32    50198  9BBDBB75
   WPPRINT.DLL   WPPRINT.DL_     2    04/13/1999  10:33   364008  D74B85F0
   WPPRINT.HLP   WPPRINT.HL_    14    10/07/1999  13:32    71408  60006DEA
   WPPRTMRI.DLL  WPPRTMRI.DL_   14    04/13/1999  10:33    66681  9CAB6A26
   WPREXX.IMP    WPREXX.IM_     17    03/31/1997  17:35     6313  707B163F
   WPSINIT.WPS   WPSINIT.WP_    17    03/31/1997  17:35    15877  ACC13319
   WPSINST.CMD   WPSINST.CM_    17    05/06/1998  16:31     2813  494D1428
   WW.EXE        WW.EX_         17    07/16/1998  14:31     8305  FE171078
   WWDLL.DLL     WWDLL.DL_       7    12/21/1997  01:29   276981  751E3674
   WWHOOK.DLL    WWHOOK.DL_     16    12/21/1997  01:29    27230  893E20E8
   XCOPY.EXE     XCOPY.EX_      15    07/19/1999  11:43    51152  23CBFC79
   XPG00420.TBL  XPG00420.TB_   17    04/12/1999  15:51    27264  08668BA9
   XPG00864.TBL  XPG00864.TB_    8    04/12/1999  15:51    27264  2672604F

   ************************************************************************
   Product location on CSD:  A:\FIX\OS2.2
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRAM011_   (Country = Arabic)
   Pre-requisite CSD Level:  XRA4000_
   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
   ------------  ------------  -----  ----------  -----  -------  --------
   OS2LDR        OS2LDR.___     17    07/19/1999  10:23    33280  4DD22847

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

   
                       FixPak Corrective Service levels and disk layouts  49


                    October 7, 1999 - Warp 4 FixPak XRAM011

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

   Default directories:

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

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPDBUTL.DLL  APPDBUTL.DL_   17    09/24/1998  12:44    25013  B03740C5
   APPSTART.EXE  APPSTART.EX_   17    09/24/1998  12:45    33864  F3D9B794
   NCAPPUTL.EXE  NCAPPUTL.EX_   17    05/11/1998  10:54    12612  F048440D
   OS2LDR        OS2LDR.___     17    07/19/1999  10:23    33280  6DC64137
   PMLOGON.EXE   PMLOGON.EX_    17    09/24/1998  12:49    40107  6ECF0A76
   PRNCFG.DLL    PRNCFG.DL_     17    09/24/1998  12:51    58258  1083DD95
   TDESK.DLL     TDESK.DL_      17    09/24/1998  12:48     3769  CC72A5DC
   TLOGOFF.EXE   TLOGOFF.EX_    17    09/24/1998  12:48     9577  DB742894
   TOBJECT.DLL   TOBJECT.DL_    17    09/24/1998  12:48     4876  54B32CDC
   TSHUTDWN.EXE  TSHUTDWN.EX_   17    09/24/1998  12:48     8611  BB45D1FD


















   
                       FixPak Corrective Service levels and disk layouts  50


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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 36MB     FixPak Archive/Backup for product with CSD level of
                  XRA4000
   Up to 36MB     FixPak Archive/Backup for product with CSD level of
                  XRA4010

   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  51


                    October 7, 1999 - Warp 4 FixPak XRAM011

   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  52
