<        Installation instructions for Warp 4 FixPak XRSM014















        

        
        



        December 1, 2000

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

                      December 1, 2000 - Warp 4 FixPak XRSM014


        December 1, 2000 - Warp 4 FixPak XRSM014


















































   
                                                                    Page  ii


                   December 1, 2000 - Warp 4 FixPak XRSM014

   CONTENTS


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

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

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

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

     5.0 New Function   . . . . . . . . . . . . . . . . . . . . . . . . . 16
     5.1 Intel's new SpeedStep  . . . . . . . . . . . . . . . . . . . . . 16
     5.2 New RAS Utilities added  . . . . . . . . . . . . . . . . . . . . 16

   
                                                               Contents  iii


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

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

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

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

     10.0 Space Utilization   . . . . . . . . . . . . . . . . . . . . . . 56
       10.0.1 Recovering FixPak ARCHIVE and BACKUP space  . . . . . . . . 56
       10.0.2 TRADEMARKS  . . . . . . . . . . . . . . . . . . . . . . . . 57

   
                                                                Contents  iv


                   December 1, 2000 - Warp 4 FixPak XRSM014

   1.0 TERMS AND CONDITIONS

   Important - please read the following terms and conditions.

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



































   
                                                     Terms and Conditions  1


                   December 1, 2000 - Warp 4 FixPak XRSM014

   2.0 DO NOT USE YOUR SYSTEM

   Once you begin a FixPak installation, do not try to use your system for
   any other purpose. Doing so may yield unexpected problems which can cause
   the FixPak installation to fail.















































   
                                                   Do not use your system  2


                   December 1, 2000 - Warp 4 FixPak XRSM014

   3.0 INSTALLATION NOTES



   3.0.1 AUDIO CD DOES NOT PLAY

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

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

    Your CD should now be able to play CDs.


   3.0.2 OUT OF MEMORY OR SYSTEM ERROR SYS0008 - FP13+

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

   þ  SET JAVA_HIGH_MEMORY=1

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


   3.0.3 CREAT UTILITY BOOT DISK DOES NOT WORK

   Due to the converged of souce lines with Warp Server for e-business, the
   Create Utility Boot Disks function does not work with the Refresh release
   of FixPak XR_M013.  A seperate Fix/Procedure will be made available on
   the Web Site where you downloaded this FixPak from when the Create
   Utility Disks problem is resolved.


   3.0.4 SUSPEND/RESUME HANG

   There is a known problem with suspend/resume on Thinkpads (or anything
   else that uses APM). The problem appears to be an interaction between the
   OS/2 kernel and the APM.SYS device driver. The workaround is to rem out
   APM.SYS and VAPM.SYS from CONFIG.SYS.  We plan to release an interim fix
   for this problem as soon as a solution is found.



   
                                                       Installation Notes  3


                   December 1, 2000 - Warp 4 FixPak XRSM014

   3.0.5 WARP 4 REVISION NUMBER CHANGED

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

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

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

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

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



   3.0.6 CHANGES YOU MAY SEE DUE TO SOURCE CONVERGENCE

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


   3.0.7 SECURITY APPLICATIONS WORK AROUND

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

   þ  FAKEISS=YES

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








   
                                                       Installation Notes  4


                   December 1, 2000 - Warp 4 FixPak XRSM014

   3.0.8 CANNOT INSTALL ON WSOD RELEASE 2

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


   3.0.9 NEW POPUPS DURING FIXPAK 12 INSTALL

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


   3.0.10 DEVICE DRIVERS REMOVED FROM FIXPAK

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


   3.0.11 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.12 PLEASE USE FIXTOOL F.143 OR LATER

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

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

   
                                                       Installation Notes  5


                   December 1, 2000 - Warp 4 FixPak XRSM014

   3.0.13 OS2DUMP SPLIT INTO TWO VERSIONS

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

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

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

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

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



   3.0.14 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



   
                                                       Installation Notes  6


                   December 1, 2000 - Warp 4 FixPak XRSM014

   Do this before you install the FixPak.


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


   
                                                       Installation Notes  7


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

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

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


   3.0.17 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.18 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.19 NO PRODUCTS FOUND

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

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

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


   
                                                       Installation Notes  8


                   December 1, 2000 - Warp 4 FixPak XRSM014

      LOGF0000.OS2
      LOGSTART.OS2
      LOGARCH.OS2


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

      LOGF0000.MPM
      LOGSTART.MPM
      LOGARCH.MPM


   Also check for the following file:

      C:\CSF_SEL.000


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


   3.0.20 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.21 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  9


                   December 1, 2000 - Warp 4 FixPak XRSM014

   3.0.22 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  10


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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


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

                   December 1, 2000 - Warp 4 FixPak XRSM014

      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.27 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.28 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.29 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )

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




















   
                                                      Installation Notes  12


                   December 1, 2000 - Warp 4 FixPak XRSM014

   4.0 POST INSTALLATION NOTES



   4.0.1 PRINT SCREEN SET PARAMETER FOR APAR JR11837

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

   SET PM_PRINTSCREEN_ACTIVE_WINDOW=ON

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

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

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

   "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=OFF"

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


   4.0.2 NEW MESSAGE BOX IN FIX FOR APAR JR12954

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

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

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

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


   4.0.3 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

   
                                                 Post Installation Notes  13


                   December 1, 2000 - Warp 4 FixPak XRSM014

   þ  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.4 SETTING IRQ9 PROCESSING IN CONFIG.SYS FOR VPIC.SYS

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

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

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


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

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


   4.0.5 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

   
                                                 Post Installation Notes  14


                   December 1, 2000 - Warp 4 FixPak XRSM014

   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.6 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.7 SYS3170 INSTALLING LOTUS SMARTSUITE 96

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

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

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


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


   4.0.8 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  15


                   December 1, 2000 - Warp 4 FixPak XRSM014

   5.0 NEW FUNCTION

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


   5.1 INTEL'S NEW SPEEDSTEP

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


   5.2 NEW RAS UTILITIES ADDED

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

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

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

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


   5.3 SERVICEABILITY (RAS) ENHANCEMENTS

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

   Other associated documentation may be found in:

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

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


   
                                                            New Function  16


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

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

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

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


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


   5.5 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND



   5.5.1 PMLOGON USER EXITS

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


   
                                                            New Function  17


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

      /URX                           \OS2\PMLOGURX.CMD

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

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


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

































   
                                                            New Function  18


                   December 1, 2000 - Warp 4 FixPak XRSM014

       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  19


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

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




   5.5.2 SETUP STRINGS FOR PUBLIC APPLICATIONS

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

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

       NCC_SETUP_POST=ICONPOS=10,10;


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

   The following KEYNAME values are permitted for setup strings:


   
                                                            New Function  20


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

       ICONFILE       filename         Sets the object's icon.

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

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


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

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


   5.5.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN

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

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


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


   5.5.4 PMLOGON NO PROGRESS INDICATOR OPTION

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




   
                                                            New Function  21


                   December 1, 2000 - Warp 4 FixPak XRSM014

   5.5.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION

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


   5.6 EURO SUPPORT

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



   5.6.1 BASE OS/2 SUPPORT

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

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

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


   The Euro character is added to these fonts.








   
                                                            New Function  22


                   December 1, 2000 - Warp 4 FixPak XRSM014

       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.6.2 WHERE EURO IS NOT SUPPORTED

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

   
                                                            New Function  23


                   December 1, 2000 - Warp 4 FixPak XRSM014

           Arial             (Windows TrueType)
           Courier New       (Windows TrueType)


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



   5.6.3 PRINTING THE EURO

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

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

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



   5.7 NEW WARP REGISTRY EDITOR

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


   5.8 WORKSPACE ON DEMAND

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


   5.9 IBM OPEN32

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





   
                                                            New Function  24


                   December 1, 2000 - Warp 4 FixPak XRSM014

   5.10 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)

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

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



   5.11 JOLIET-2 SUPPORT IN CDFS.IFS

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

   Joilet-3 format is not supported.



   5.12 NEW (IMPROVED) CHKDSK

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

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


   5.12.1 USING THE NEW CHKDSK

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

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

   Note: OS/2 Warp Install uses fast format.



   
                                                            New Function  25


                   December 1, 2000 - Warp 4 FixPak XRSM014

   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  26


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

     Original IFS statement:

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

     New IFS statement:

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

     The CALL statement to use is:

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


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

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

     CHKDSK.COM
     CHKDSK32.DLL
     UHPFS.DLL


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


   5.12.2 CHKDSK LOG FORMATTER

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

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


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





   
                                                            New Function  27


                   December 1, 2000 - Warp 4 FixPak XRSM014

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


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

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


   5.13 AUTOMATED TRAP SCREEN LOGGING

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

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


   5.13.1 SUPPRESSPOPUPS

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

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

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


   5.13.2 TRAPLOG

   The TRAPLOG command allows dynamic control of trap information logging.

   The command syntax is:

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



   
                                                            New Function  28


                   December 1, 2000 - Warp 4 FixPak XRSM014

   where:

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



   5.13.3 TRAPDUMP

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

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

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

   The command syntax is:

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


   where:

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



   5.13.4 SYSDUMP

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

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

   
                                                            New Function  29


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

   The command syntax is:

          SYSDUMP [/NOPROMPT]


   where:

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

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




   5.14 REXX NEW FUCTION

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


   5.15 OTHER README FILES

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

   File           Use

   README2        Problems fixed in each FixPak (APAR list)

   README.CID     Installing FixPaks via CID

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

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

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







   
                                                            New Function  30


                   December 1, 2000 - Warp 4 FixPak XRSM014

   6.0 CORRECTIVE SERVICE FACILITY



   6.0.1 REQUIRED CSF LEVEL

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

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

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


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


   6.0.2 WHERE YOU CAN FIND CSF CODE

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

   Source         How to access

   
                                             Corrective Service Facility  31


                   December 1, 2000 - Warp 4 FixPak XRSM014


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

   Label the diskette as

         FixPak XRSM014
   Corrective Service Diskette ?
          (CSF DISK ?)


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

        Examples:

        XRSM014.ADK = 10
        XRSM014.FDK = 15
        XRSM014.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  32


                   December 1, 2000 - Warp 4 FixPak XRSM014

   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  33


                   December 1, 2000 - Warp 4 FixPak XRSM014

   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  34


                   December 1, 2000 - Warp 4 FixPak XRSM014

       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  35


                   December 1, 2000 - Warp 4 FixPak XRSM014

   7.0 INSTALLATION PROCESS



   7.1 BEFORE INSTALLATION

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

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

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


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

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

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

   Here are some additional notes:

   Follow the displayed instructions.  When prompted to insert Corrective
   Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XRSM014
   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  36


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

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

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

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

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

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

      The locked file driver is loaded.

             Processing locked files

             Processing complete


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


   7.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA

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

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



   
                                                    Installation Process  37


                   December 1, 2000 - Warp 4 FixPak XRSM014

   Here are some additional notes:

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

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

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

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


   7.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION

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

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





















   
                                                    Installation Process  38


                   December 1, 2000 - Warp 4 FixPak XRSM014

   8.0 CSD LEVEL OF SYSLEVEL.OS2

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

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

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

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


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

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


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

      \OS2\INSTALL\SERVICE.LOG


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

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

   The Operating System/2 Version is 4.50
   Revision 14.044


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

   Build Level: nn.nnn



   
                                               CSD level of SYSLEVEL.OS2  39


                   December 1, 2000 - Warp 4 FixPak XRSM014

   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  40


                   December 1, 2000 - Warp 4 FixPak XRSM014

   9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS

   Build Level: 14.044

   Product location on CSD:  A:\FIX\OS2.1
   Product name:  "IBM OS/2 Base Operating System"
   Standard Edition  4.00
   Fixpak name:   XRSM014_   (Country = Spain)
   Pre-requisite CSD Level:  XRS4000_
   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:   XRSM014_   (Country = Spain)
   Pre-requisite CSD Level:  XRS4010_
   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:   XRSM014_   (Country = Spain)
   Pre-requisite CSD Level:  XRS4010_
   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  41


                   December 1, 2000 - Warp 4 FixPak XRSM014

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

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

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

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

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

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


   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPEND.EXE    APPEND.EX_     18    07/14/2000  12:37     7842  7DEAE8AD
   ARACONV.EXE   ARACONV.EX_    16    11/23/1999  20:12    62151  F801F7D0
   ASIACOL.DLL   ASIACOL.DL_    11    05/02/2000  13:52   158758  1EC93C21
   ASSIGN.COM    ASSIGN.CO_     18    07/14/2000  12:37     2843  48570D5C
   ATTRIB.EXE    ATTRIB.EX_     16    07/14/2000  12:37    37789  C1663FB9
   AVIO.DLL      AVIO.DL_       15    06/27/2000  12:46    53921  5B3E07CA
   BACKUP.EXE    BACKUP.EX_     17    07/14/2000  12:43    36064  FB5D597D
   BDCALL32.DLL  BDCALL32.DL_   16    11/23/1999  20:11    33519  7810A009
   BDIME.DLL     BDIME.DL_      17    11/23/1999  20:12    11911  6C2663B5
   BDVIEW.DLL    BDVIEW.DL_     16    07/08/2000  16:33    34888  FF4E26F2
   BDWPCLS.DLL   BDWPCLS.DL_    17    07/08/2000  16:32    20144  A5A0AE90
   BE.KBL        BE.KB_         18    05/02/2000  13:58      972  C4AE8064
   BLDLEVEL.EXE  BLDLEVEL.EX_   16    07/10/2000  08:45    57842  7406C1C6
   BOOTDISK.EXE  BOOTDISK.EX_   15    07/18/2000  15:26    61057  3DE21A06
   BOOTDISK.HLP  BOOTDISK.HL_   17    02/29/2000  14:13    13082  B750B80F
   BVHINIT.DLL   BVHINIT.DL_    17    07/10/2000  14:23    11158  9D660E41
   BVHMPA.DLL    BVHMPA.DL_      6    07/10/2000  14:04    15293  61739922
   BVHVGA.DLL    BVHVGA.DL_     16    07/10/2000  14:23    31875  1C904E21
   BVHWNDW.DLL   BVHWNDW.DL_    17    07/10/2000  14:04    16797  DF6D9B0D
   BVSCALLS.DLL  BVSCALLS.DL_   18    07/10/2000  16:55      512  EEB362C8
   BY.KBL        BY.KB_         18    05/02/2000  13:58     1292  FEB0138D
   CA.KBL        CA.KB_         18    05/02/2000  13:58     1214  4DBC4542
   CACHE.EXE     CACHE.EX_      17    05/03/2000  18:34    14382  BF8915D6
   CARDINFO.DAT  CARDINFO.DA_   18    06/27/2000  16:56    55689  9921F5F2
   CCHMAIN.EXE   CCHMAIN.EX_     9    07/07/2000  21:56   199408  B10A6D7F
   CCHUSER.DLL   CCHUSER.DL_    14    07/07/2000  21:55    63763  DC5CACE6
   CDFS.IFS      CDFS.IF_       16    05/03/2000  18:48    45747  101BBF01
   CDFS.TDF      CDFS.TD_       18    05/03/2000  18:48     2113  73E54068
   CDROM.TBL     CDROM.TB_      18    03/15/2000  09:36     4371  EE96BE53
   CF.KBL        CF.KB_         18    05/02/2000  13:58      956  D1C7AF50
   CHKDSK.COM    CHKDSK.CO_     15    07/14/2000  12:37    72256  BCF92FC2
   CHKDSK.SYS    CHKDSK.SY_     18    05/03/2000  18:34      795  3BAC6A04
   CHKDSK32.DLL  CHKDSK32.DL_   12    05/03/2000  18:46   139739  45D0DFF8
   CHKDSK32.EXE  CHKDSK32.EX_   18    05/03/2000  18:34     6417  4518BC60

   
                       FixPak Corrective Service levels and disk layouts  42


                   December 1, 2000 - Warp 4 FixPak XRSM014

   CLOCK01.SYS   CLOCK01.SY_    18    06/16/2000  23:18     4560  C6FB18DF
   CLOCK02.SYS   CLOCK02.SY_    18    06/16/2000  23:18     4318  A53E07CB
   CMD.EXE       CMD.EX_        13    07/14/2000  12:39   101644  0CAA8696
   COMM.DRV      COMM.DR_       18    01/08/2000  00:28     9552  F8095FEE
   COMMAND.COM   COMMAND.CO_    16    07/14/2000  12:38    43938  950B054C
   COMP.COM      COMP.CO_       16    07/14/2000  12:40    35881  05CAA9F0
   CONTROL.PM    CONTROL.PM_    18    07/10/2000  18:43     8478  AD2558B8
   COUNTRY.SYS   COUNTRY.SY_    17    01/21/2000  18:33    50947  191CE153
   COUR.OFM      COUR.OF_       18    11/22/1999  11:22     6163  A932E20A
   COUR.PFB      COUR.PF_       11    11/22/1999  11:23   137111  480473C7
   COUR.PFM      COU1.PF_       18    11/22/1999  11:22      674  EB1BF968
   COURB.OFM     COURB.OF_      18    11/22/1999  11:22     6173  308D4A2B
   COURB.PFB     COURB.PF_      10    11/22/1999  11:23   140829  503DA572
   COURB.PFM     COUR1.PF_      18    11/22/1999  11:22      679  1EF9D34B
   COURBI.OFM    COURBI.OF_     18    11/22/1999  11:22     6187  0F612DD1
   COURBI.PFB    COURBI.PF_     11    11/22/1999  11:23   136240  96421E3A
   COURBI.PFM    COURB1.PF_     18    11/22/1999  11:22      685  48390DF4
   COURI.OFM     COURI.OF_      18    11/22/1999  11:22     6178  2B7F133A
   COURI.PFB     COURI.PF_      10    11/22/1999  11:23   137394  7198B5E2
   COURI.PFM     COUR2.PF_      18    11/22/1999  11:22      681  A6EEB7E0
   COURIER.FON   COURIER.FO_    15    07/10/2000  09:15    77826  E0FC9CCD
   COURIERI.FON  COURIERI.FO_   15    07/10/2000  09:10    86641  199F448C
   CPG01256.TBL  CPG01256.TB_   18    11/22/1999  12:17    27264  A7BB21BD
   CREX.MSG      CREX.MS_       18    03/27/2000  14:23     2865  880D6E0E
   CREXUTIL.DLL  CREXUTIL.DL_   14    03/27/2000  14:23    68119  4D4C3853
   CREXX.DLL     CREXX2.DL_     10    03/27/2000  14:23   266031  E12D2A5F
   CYRIME.DLL    CYRIME.DL_     17    07/10/2000  08:54    21529  F252DB4B
   CZ.KBL        CZ.KB_         18    05/02/2000  13:58     1014  0F79F53C
   DDINSTAL.EXE  DDINSTAL.EX_   16    07/10/2000  19:00    52775  F2503D83
   DE.KBL        DE.KB_         18    05/02/2000  13:58      958  D5F96C94
   DE453.KBL     DE453.KB_      18    05/02/2000  13:58     1354  8F97C176
   DEBUG.EXE     DEBUG.EX_      17    07/14/2000  12:40    28449  60D0859F
   DF_DEB.EXE    DF_DEB.EX_     13    07/07/2000  20:55   135989  8C2B6D72
   DF_RET.EXE    DF_RET.EX_     13    07/07/2000  19:17   135957  3AADD39A
   DIBDRVR.DLL   DIBDRVR.DL_    18    07/10/2000  11:30     5627  7AA39D1B
   DICTATE.EXE   DICTATE.EX_    15    05/06/1998  11:58    51391  460F5574
   DICTDLL.DLL   DICTDLL.DL_    15    12/21/1997  01:28    51187  D092ADCA
   DISKCOMP.COM  DISKCOMP.CO_   16    07/14/2000  12:44    41697  F56BE6BF
   DISKCOPY.COM  DISKCOPY.CO_   16    07/14/2000  12:44    46196  21810E99
   DISPLAY.DLL   DISPLAY.DL_    15    07/10/2000  13:48    46574  F71B9416
   DIVE.DLL      DIVE.DL_       14    06/27/2000  12:39    69662  E42F32CC
   DK.KBL        DK.KB_         18    05/02/2000  13:58      928  8157DFBC
   DMISL.EXE     DMISL.EX_      13    02/16/2000  04:50   144918  6D788902
   DMQSPROF.DLL  DMQSPROF.DL_   16    04/10/2000  17:32    39033  709BE863
   DOSCALL1.DLL  DOSCALL1.DL_   12    07/10/2000  16:30   137609  019E1CC4
   DOSCALL1.SYM  DOSCALL1.SY_   16    07/10/2000  16:30    43636  936030DE
   DOSCALL1.TDF  DOSCALL1.TD_   18    07/07/2000  19:16     5534  FC52CF02
   DOSKEY.COM    DOSKEY.CO_     18    07/14/2000  12:40     6500  1834D2CD
   DOSKRNL       DOSKRNL.___    17    07/10/2000  16:30    31553  2DB8ACBD
   DRVMAP.INF    DRVMAP.IN_     18    07/10/2000  18:43    13008  09CA7852
   DSPIMRI.DLL   DSPIMRI.DL_    17    05/15/2000  17:41    18982  B171F077

   
                       FixPak Corrective Service levels and disk layouts  43


                   December 1, 2000 - Warp 4 FixPak XRSM014

   DSPINSTL.EXE  DSPINSTL.EX_   13    07/10/2000  14:11   175128  3B289386
   DSPRES.DLL    DSPRES1.DL_     8    07/10/2000  09:10   376488  75EB1E6A
   DSPRES.DLL    DSPRES.DL_      7    07/10/2000  09:10   376488  76069E6A
   DTRACE.DOC    DTRACE.DO_     17    11/22/1999  11:25    75371  62EE5F89
   DTRACE.EXE    DTRACE1.EX_    15    02/16/2000  04:57    74850  25061E97
   DTRACE.EXE    DTRACE.EX_     15    02/16/2000  04:57    74850  25067717
   E.EXE         E.EX_          14    07/08/2000  01:25    63383  D1CAA044
   EAUTIL.EXE    EAUTIL.EX_     16    07/14/2000  12:40    38512  9364B239
   EDLIN.COM     EDLIN.CO_      18    07/14/2000  12:40     8572  68213C60
   EHXDLMRI.DLL  EHXDLMRI.DL_   17    07/08/2000  01:26    14373  2BADD951
   EJECT.EXE     EJECT.EX_      17    01/21/2000  18:41    29746  B699826B
   EL.KBL        EL.KB_         18    05/02/2000  13:58     1396  423D982A
   EL459.KBL     EL459.KB_      18    05/02/2000  13:58     1372  717EB3C2
   ENGINE.EXE    ENGINE.EX_      3    07/23/1997  11:39   440424  CA5B8BAA
   EPM.EXE       EPM.EX_        17    11/23/1999  17:44    24032  197BF472
   ERLOGGER.EXE  ERLOGGER.EX_   16    02/15/2000  11:46    48608  5EB8D7B4
   ERRLOG.DLL    ERRLOG.DL_     14    02/15/2000  11:46    72806  D08A1B84
   ERRTXT.DLL    ERRTXT.DL_     17    05/03/2000  18:26    26714  979565F2
   ES.KBL        ES.KB_         18    05/02/2000  13:58      920  DA55783B
   ETKC603.DLL   ETKC603.DL_    12    11/23/1999  16:02   136124  298E8727
   ETKE603.DLL   ETKE603.DL_     6    11/23/1999  16:02   767421  C1790876
   EZP2MRI.DLL   EZP2MRI.DL_    15    07/08/2000  01:28    96286  6DB5D3D2
   FDISK.COM     FDISK.CO_      14    07/14/2000  12:46   117347  3D9CD944
   FDISKPM.DLL   FDISKPM.DL_    18    07/14/2000  12:46    10805  EAC824D7
   FDISKPM.EXE   FDISKPM.EX_    15    07/14/2000  12:46    78916  6B8E16CC
   FDISKPMH.HLP  FDISKPMH.HL_   17    07/14/2000  12:46    15773  D2AD204E
   FFCONFIG.DLL  FFCONFIG.DL_   17    02/15/2000  11:49    20551  ACDCCA24
   FFDUMP.DLL    FFDUMP.DL_     15    02/15/2000  12:52    41217  D917E9D1
   FFGUI.DLL     FFGUI.DL_      17    02/15/2000  17:47    19575  5B797DC5
   FFIPC.DLL     FFIPC.DL_      17    02/15/2000  11:49    27201  F844F112
   FFPCT.DLL     FFPCT.DL_      17    02/15/2000  11:49    21588  96F216C6
   FFPROBE.DLL   FFPROBE.DL_    17    02/15/2000  12:19    24680  77EEA0EB
   FFST.DLL      FFST.DL_       17    01/21/2000  14:58    11425  B9B2A0EA
   FFSTCONF.EXE  FFSTCONF.EX_   14    02/15/2000  12:52   104505  15B38833
   FFSTPCT.EXE   FFSTPCT.EX_    14    02/15/2000  12:52   105143  723BB336
   FI.KBL        FI.KB_         18    05/02/2000  13:58      940  6CB4A1C8
   FILT.DLL      FILT.DL_       17    06/27/2000  12:41    22890  BFF139BC
   FIND.EXE      FIND.EX_       17    07/14/2000  12:40    31165  90767FA9
   FKA.DLL       FKA.DL_        17    11/22/1999  11:46    13997  66D83B79
   FORMAT.COM    FORMAT.CO_     15    07/14/2000  12:41    73088  99235566
   FR.KBL        FR.KB_         18    05/02/2000  13:58      950  37A63C40
   FSFILTER.SYS  FSFILTER.SY_   17    07/10/2000  16:30    12730  ED18B058
   GDI.EXE       GDI.EX_        10    01/07/2000  22:33   226272  93FD63F8
   GRADD.SYS     GRADD.SY_      18    05/15/2000  16:23     2754  05B876B1
   GRAFTABL.COM  GRAFTABL.CO_   18    07/14/2000  12:41    10058  CD8CADF0
   GRE2VMAN.DLL  GRE2VMAN.DL_   17    07/10/2000  19:17    18221  FDEC26A7
   GSVDAEMN.EXE  GSVDAEMN.EX_   18    04/22/2000  09:37     4864  C6F07B3B
   GSVINST.EXE   GSVINST.EX_    16    07/07/2000  18:58    34351  BC80D4DE
   HARDERR.EXE   HARDERR.EX_    17    07/10/2000  16:30    15913  A596B590
   HDMON.EXE     HDMON.EX_      14    02/15/2000  17:52   112087  056A7B3E
   HELPMGR.DLL   HELPMGR.DL_     9    07/10/2000  09:12   250157  0A77B71F

   
                       FixPak Corrective Service levels and disk layouts  44


                   December 1, 2000 - Warp 4 FixPak XRSM014

   HELPMSG.EXE   HELPMSG.EX_    16    07/14/2000  12:41    37280  C7B14ADA
   HELV.FON      HELV.FO_       11    07/10/2000  09:15   171252  537EC754
   HELV.OFM      HELV.OF_       18    11/22/1999  11:22     6793  BA06E30D
   HELV.PFB      HELV.PF_       11    11/22/1999  11:23   120578  089723CF
   HELV.PFM      HEL1.PF_       18    11/22/1999  11:22     1096  C722994F
   HELVB.OFM     HELVB.OF_      18    11/22/1999  11:22     6785  D4469EC8
   HELVB.PFB     HELVB.PF_      11    11/22/1999  11:23   123085  0037E6EB
   HELVB.PFM     HELV1.PF_      18    11/22/1999  11:22     1089  56484EA1
   HELVBI.OFM    HELVBI.OF_     18    11/22/1999  11:22     6787  409F5DD9
   HELVBI.PFB    HELVBI.PF_     11    11/22/1999  11:23   124245  46A1767C
   HELVBI.PFM    HELVB1.PF_     18    11/22/1999  11:22     1087  06B4EB9D
   HELVI.FON     HELVI.FO_      11    07/10/2000  09:10   199523  0303981D
   HELVI.OFM     HELVI.OF_      18    11/22/1999  11:22     6772  3B22C1CD
   HELVI.PFB     HELVI.PF_      11    11/22/1999  11:24   123355  48DC67E0
   HELVI.PFM     HELV2.PF_      18    11/22/1999  11:22     1079  45475F04
   HPFS.IFS      HPFS.IF_       13    05/03/2000  18:31   141890  D8CFC37F
   HPFS.TDF      HPFS.TD_       18    05/03/2000  18:31     1620  37A46B98
   HPMGRMRI.DLL  HPMGRMRI.DL_   17    07/10/2000  13:13    22155  AC21DB8E
   HR.KBL        HR.KB_         18    05/02/2000  13:58      982  9EB6252B
   HU.KBL        HU.KB_         18    05/02/2000  13:58     1006  70183717
   IBM1004       IBM1004.___    18    05/02/2000  13:57     3584  5EA8D65D
   IBM1125       IBM1125.___    18    05/02/2000  13:57     4320  3BA58B48
   IBM1131       IBM1131.___    18    05/02/2000  13:57     4320  DDF790D9
   IBM1140       IBM1140.___    18    05/02/2000  13:57     2816  6C2B30C2
   IBM1141       IBM1141.___    18    05/02/2000  13:57     2784  75D19006
   IBM1142       IBM1142.___    18    05/02/2000  13:57     2816  3BF94AA1
   IBM1143       IBM1143.___    18    05/02/2000  13:57     2816  AD4D2C47
   IBM1144       IBM1144.___    18    05/02/2000  13:57     2784  F7F22BD5
   IBM1145       IBM1145.___    18    05/02/2000  13:57     2784  D07B2ECD
   IBM1146       IBM1146.___    18    05/02/2000  13:57     2816  78C1C7B6
   IBM1147       IBM1147.___    18    05/02/2000  13:57     2784  E3AFBEEB
   IBM1148       IBM1148.___    18    05/02/2000  13:57     2816  97FC1F1E
   IBM1250       IBM1250.___    18    05/02/2000  13:57     3552  A81CAD39
   IBM1251       IBM1251.___    18    05/02/2000  13:57     3328  D9036978
   IBM1252       IBM1252.___    18    05/02/2000  13:57     3552  AF8E7271
   IBM1253       IBM1253.___    18    05/02/2000  13:57     3552  DC4AD657
   IBM1254       IBM1254.___    18    05/02/2000  13:57     3552  9A43DB4B
   IBM1255       IBM1255.___    18    05/02/2000  13:57     3808  F8905849
   IBM1256       IBM1256.___    18    05/02/2000  13:57     4320  87597FF4
   IBM1257       IBM1257.___    18    05/02/2000  13:57     3296  172675C9
   IBM813        IBM813.___     18    05/02/2000  13:57     3072  3BBA332D
   IBM850        IBM850.___     18    05/02/2000  13:57     4320  E49FD699
   IBM852        IBM852.___     18    05/02/2000  13:57     4608  16750206
   IBM857        IBM857.___     18    05/02/2000  13:57     4352  05443656
   IBM859        IBM859.___     18    05/02/2000  13:57     4320  6B045173
   IBM862        IBM862.___     18    05/02/2000  13:57     4576  EF681E83
   IBM864        IBM864.___     18    05/02/2000  13:58     4576  ECAB6769
   IBM869        IBM869.___     18    05/02/2000  13:58     4320  65EFE4B8
   IBM923        IBM923.___     18    05/02/2000  13:58     2784  5CD5E506
   IBM924        IBM924.___     18    05/02/2000  13:58     2784  DE7F1673
   IBMOPTNS.DLL  IBMOPTNS.DL_   17    06/27/2000  16:56    22978  17A63E84

   
                       FixPak Corrective Service levels and disk layouts  45


                   December 1, 2000 - Warp 4 FixPak XRSM014

   ICONEDIT.EXE  ICONEDIT.EX_   13    11/23/1999  16:35   163984  7F46F54E
   IFGDI2VM.DRV  IFGDI2VM.DR_   15    05/15/2000  16:23    93136  7268D109
   INSCFG32.DLL  INSCFG32.DL_   16    07/10/2000  18:44    32082  CAC53F98
   INST_DOS.EXE  INST_DOS.EX_   16    07/10/2000  11:27    39114  00A39327
   INSTALL.EXE   INSTALL.EX_     7    07/18/2000  15:26   386312  24BABFA9
   IOPROC.DLL    IOPROC.DL_     16    06/27/2000  12:54    37880  AC4A85F1
   IS.KBL        IS.KB_         18    05/02/2000  13:58      940  E8D831F6
   IS458.KBL     IS458.KB_      18    05/02/2000  13:58      928  E404EF98
   ISGDI2VM.DRV  ISGDI2VM.DR_   15    05/15/2000  16:07    92048  354AB309
   IT.KBL        IT.KB_         18    05/02/2000  13:58      876  B0A1DEF0
   IT142.KBL     IT142.KB_      18    05/02/2000  13:58      854  253C0AB2
   JOIN.EXE      JOIN.EX_       18    07/14/2000  12:41     4520  9475C4BA
   JPEGIO.DLL    JPEGIO.DL_     15    06/27/2000  16:19    44357  BAA9BFB5
   KERNEL.SDF    KERNEL.SD_     14    07/07/2000  19:17    58993  74FFBB07
   KERNELD.SDF   KERNELD.SD_    14    07/07/2000  19:17    59138  2CAFA1B6
   KEYBOARD.DCP  KEYBOARD.DC_   17    05/02/2000  13:58   315109  088E80C8
   KRNLBDEV.TDF  KRNLBDEV.TD_   18    07/10/2000  16:00     4232  7D191AD7
   KRNLBFS.TDF   KRNLBFS.TD_    18    07/10/2000  16:00     4793  5CD010BB
   KRNLBLDR.TDF  KRNLBLDR.TD_   18    07/10/2000  16:00     5384  87FF244C
   KRNLBPG.TDF   KRNLBPG.TD_    18    07/10/2000  16:00     3209  8A9C1BD2
   KRNLBSEL.TDF  KRNLBSEL.TD_   18    07/10/2000  16:00     2783  70120537
   KRNLBSEM.TDF  KRNLBSEM.TD_   18    07/10/2000  16:00     1792  D46E7BC7
   KRNLBSM.TDF   KRNLBSM.TD_    18    07/10/2000  16:00     1196  D1A91C41
   KRNLBTK.TDF   KRNLBTK.TD_    18    07/10/2000  16:00    13005  C39621D8
   KRNLBTOM.TDF  KRNLBTOM.TD_   18    07/10/2000  16:00     1012  A586345B
   KRNLBVDM.TDF  KRNLBVDM.TD_   18    07/10/2000  16:00    15517  39D01B15
   KRNLBVM.TDF   KRNLBVM.TD_    18    07/10/2000  16:00     5542  D8ACB5DF
   KRNLDDEV.TDF  KRNLDDEV.TD_   18    07/10/2000  15:58     4232  6E0C8458
   KRNLDFS.TDF   KRNLDFS.TD_    18    07/10/2000  15:58     4734  892E36E3
   KRNLDLDR.TDF  KRNLDLDR.TD_   18    07/10/2000  15:58     5387  1382097A
   KRNLDPG.TDF   KRNLDPG.TD_    18    07/10/2000  15:58     3265  EAB46F8E
   KRNLDSEL.TDF  KRNLDSEL.TD_   18    07/10/2000  15:58     2895  B5458E87
   KRNLDSEM.TDF  KRNLDSEM.TD_   18    07/10/2000  15:58     1932  650C4BCD
   KRNLDSM.TDF   KRNLDSM.TD_    18    07/10/2000  15:58     1221  054E0790
   KRNLDTK.TDF   KRNLDTK.TD_    18    07/10/2000  15:58    13008  E98B612E
   KRNLDTOM.TDF  KRNLDTOM.TD_   18    07/10/2000  15:59     1040  5229D36C
   KRNLDVDM.TDF  KRNLDVDM.TD_   18    07/10/2000  15:59    15742  4898A205
   KRNLDVM.TDF   KRNLDVM.TD_    18    07/10/2000  15:59     5654  59D44975
   KRNLRDEV.TDF  KRNLRDEV.TD_   18    07/10/2000  15:50     4232  F992D284
   KRNLRFS.TDF   KRNLRFS.TD_    18    07/10/2000  15:50     4793  3FDD979B
   KRNLRLDR.TDF  KRNLRLDR.TD_   18    07/10/2000  15:50     5384  81D073B4
   KRNLRPG.TDF   KRNLRPG.TD_    18    07/10/2000  15:50     3209  A664F7AE
   KRNLRSEL.TDF  KRNLRSEL.TD_   18    07/10/2000  15:50     2783  E819C2C5
   KRNLRSEM.TDF  KRNLRSEM.TD_   18    07/10/2000  15:50     1792  72C1A952
   KRNLRSM.TDF   KRNLRSM.TD_    18    07/10/2000  15:50     1196  B2E9317D
   KRNLRTK.TDF   KRNLRTK.TD_    18    07/10/2000  15:50    12921  32D15EBF
   KRNLRTOM.TDF  KRNLRTOM.TD_   18    07/10/2000  15:50      984  810F31AB
   KRNLRVDM.TDF  KRNLRVDM.TD_   18    07/10/2000  15:50    15352  39012601
   KRNLRVM.TDF   KRNLRVM.TD_    18    07/10/2000  15:50     5542  1790D43D
   LABEL.COM     LABEL.CO_      17    07/14/2000  12:45    33805  B6313004
   LFAPI.DLL     LFAPI.DL_      17    02/15/2000  11:46    21178  EEED0119

   
                       FixPak Corrective Service levels and disk layouts  46


                   December 1, 2000 - Warp 4 FixPak XRSM014

   LIBCM.DLL     LIBCM.DL_       9    11/22/1999  11:45   210916  5BC59AE9
   LIBCN.DLL     LIBCN.DL_      15    11/22/1999  11:45    57340  693C0B04
   LIBCS.DLL     LIBCS.DL_      10    11/22/1999  11:45   192386  7E2C4F0D
   LIBUNI.DLL    LIBUNI.DL_     14    05/02/2000  14:01    81372  739C93C5
   LMDLL.DLL     LMDLL.DL_      15    06/16/2000  23:24    76973  D6D6C4B0
   LOCALE.DLL    LOCALE.DL_      8    05/02/2000  13:57   107901  53E77400
   MAIN.CPL      MAIN.CP_       13    01/07/2000  22:46   150528  C20A876E
   MAKETSF.EXE   MAKETSF.EX_    16    02/16/2000  04:57    51928  E3B9ACE5
   MAPTSF.CMD    MAPTSF.CM_     18    11/22/1999  11:25    16803  20FD489D
   MEM.EXE       MEM.EX_        16    07/14/2000  12:46    40040  50A5AB57
   MIDI.SYS      MIDI.SY_       17    04/22/2000  11:08    26328  FA7A9F0C
   MIDIMCD.DLL   MIDIMCD.DL_    18    06/27/2000  16:17     4118  B6D361BC
   MIGRATE.EXE   MIGRATE.EX_    13    07/10/2000  19:09   175771  4B1A47AD
   MINSTALL.EXE  MINSTALL.EX_   11    06/27/2000  16:57   191774  84ECDAEB
   MINXOBJ.DLL   MINXOBJ.DL_    16    07/07/2000  20:02    31886  E9BEEA08
   MIRRORS.DLL   MIRRORS.DL_     7    03/27/2000  14:24   444744  0D936518
   MMODPTS.DLL   MMODPTS.DL_    10    06/27/2000  13:31   185858  88754380
   MMPARTS.DLL   MMPARTS.DL_     2    06/27/2000  16:33  1534588  16A3F0FC
   MMPM.DLL      MMPM.DL_        7    06/27/2000  16:21   432003  A849164C
   MMPTMRI.DLL   MMPTMRI.DL_    12    06/27/2000  16:55   231954  A4F10C98
   MMSNIFF.DLL   MMSNIFF.DL_    16    04/22/2000  11:44    33298  505E06C4
   MMSOUND.DRV   MMSOUND.DR_    18    01/07/2000  23:06     3456  97D8A150
   MODE.COM      MODE.CO_       15    07/14/2000  12:42    64325  0401BC2D
   MONCALLS.DLL  MONCALLS.DL_   18    07/10/2000  16:55     5536  50DB68A3
   MONCALLS.TDF  MONCALLS.TD_   18    07/10/2000  16:55     1139  C5670429
   MORE.COM      MORE.CO_       17    07/14/2000  12:42    34935  E85ACCE9
   MPGIO.DLL     MPGIO.DL_      13    06/27/2000  12:59    59269  65D78FD8
   MSG.DLL       MSG.DL_        18    07/10/2000  16:55      512  CCB24C32
   NAMEADD.EXE   NAMEADD.EX_    17    11/24/1999  13:10    23040  3DDC29A2
   NAMECOPY.EXE  NAMECOPY.EX_   17    11/24/1999  13:10    23040  1C0F014E
   NAMEDEL.EXE   NAMEDEL.EX_    17    11/24/1999  13:10    23040  65DC29A3
   NAMEDSP.DLL   NAMEDSP.DL_    12    07/10/2000  08:51   123427  5BAD39EB
   NAMEEXT.EXE   NAMEEXT.EX_    17    11/24/1999  13:10    23040  9DDC29A5
   NAMEFW.DLL    NAMEFW.DL_     14    07/10/2000  08:51    72328  3C701BFF
   NAMEMOD.EXE   NAMEMOD.EX_    17    11/24/1999  13:10    23040  4DDC29A3
   NAMEMOVE.EXE  NAMEMOVE.EX_   17    11/24/1999  13:10    23040  240F014C
   NAMEREXX.DLL  NAMEREXX.DL_   13    07/10/2000  08:51    97779  B77CD86B
   NAMPIPES.DLL  NAMPIPES.DL_   18    07/10/2000  16:55     1024  5FCAFD60
   NL.KBL        NL.KB_         18    05/02/2000  13:58      954  007E6A4A
   NLS.DLL       NLS.DL_        18    07/10/2000  16:55      512  B36B8263
   NO.KBL        NO.KB_         18    05/02/2000  13:58      920  DD758537
   NWIAPI.DLL    NWIAPI.DL_     17    07/08/2000  16:52    14770  09062A39
   OREXUTIL.DLL  ORXUTIL2.DL_   15    03/27/2000  14:23    41175  1BC72760
   OREXX.DLL     OREXX2.DL_      6    03/27/2000  14:23   490355  38ECFC35
   OS2CHAR.DLL   OS2CHAR.DL_    18    07/10/2000  16:55      512  9B6DE749
   OS2CHAR.TDF   OS2CHAR.TD_    18    07/07/2000  19:16    13889  F229119B
   OS2DASD.DMD   OS2DASD.DM_    16    04/22/2000  09:41    40910  3391171A
   OS2DUMP       OS2DUMP.___    17    07/10/2000  16:57    15101  EF76D95F
   OS2K386.EXE   OS2K386.EX_    14    01/07/2000  22:35    80690  2908E27E
   OS2KRNL       OS2KRNL.___     4    07/10/2000  15:50   822344  968D965E
   OS2KRNLD.SYM  OS2KRNLD.SY_   12    07/10/2000  15:58   187940  9B14CE39

   
                       FixPak Corrective Service levels and disk layouts  47


                   December 1, 2000 - Warp 4 FixPak XRSM014

   OS2KRNLR.SYM  OS2KRNLR.SY_   12    07/10/2000  15:50   165732  1188BAAE
   OS2KRNLR.TDF  OS2KRNLR.TD_   18    07/10/2000  15:50    17554  6DAA3B98
   OS2LDR.MSG    OS2LDR.MS_     18    07/07/2000  21:02    10097  B7C7A4B5
   OS2MM.DLL     OS2MM.DL_       1    06/27/2000  16:57   219972  8A0985A9
   OS2SM.DLL     OS2SM.DL_      18    07/10/2000  11:49     1598  86EF4205
   OS2UGL        OS2UGL.___     18    05/02/2000  13:58    15616  8E78F6F4
   OSO001.MSG    OSO001.MS_     14    07/07/2000  15:53   205506  2CCBB996
   OSO001H.MSG   OSO001H.MS_    13    07/07/2000  15:53   278020  EAFE7EC0
   PARALLEL.PDR  PARALLEL.PD_   17    07/08/2000  01:21    15930  DA0D256E
   PCMCIA.TBL    PCMCIA.TB_     18    04/14/2000  13:27     5114  E2E24826
   PDUMPSYS.EXE  PDUMPSYS.EX_   16    02/16/2000  05:03    47165  E5FDB7E0
   PDUMPUSR.EXE  PDUMPUSR.EX_   16    02/16/2000  05:03    47163  FEB0BE9B
   PICV.DLL      PICV.DL_       17    07/10/2000  09:11    26200  595E0B53
   PICVIEW.DLL   PICVIEW.DL_    17    07/10/2000  13:12    14370  82E9F0ED
   PICVIEW.EXE   PICVIEW.EX_    14    07/10/2000  13:12    95770  E42E23C7
   PL.KBL        PL.KB_         18    05/02/2000  13:58      980  505C44CD
   PL457.KBL     PL457.KB_      18    05/02/2000  13:58      882  1EF50F61
   PMATM.DLL     PMATM.DL_       9    04/12/2000  11:39   224343  17033B97
   PMBIDI.DLL    PMBIDI.DL_     17    11/23/1999  20:11    13611  08D961D4
   PMCHKDSK.DLL  PMCHKDSK.DL_   18    07/14/2000  12:47     8223  B529503F
   PMCHKDSK.EXE  PMCHKDSK.EX_   17    07/14/2000  12:47    33303  96077FBB
   PMCLIP.DLL    PMCLIP.DL_     17    07/10/2000  11:29    21167  CC55C85A
   PMCTLS.DLL    PMCTLS.DL_      5    07/10/2000  18:35   587734  9438D348
   PMCTLS.SYM    PMCTLS.SY_     16    07/10/2000  18:35    44660  9170FAC6
   PMDDE.DLL     PMDDE.DL_      16    07/10/2000  18:44    28236  45F7BE18
   PMDDEML.DLL   PMDDEML.DL_    16    07/10/2000  08:55    27814  EB9C1B42
   PMDF.EXE      PMDF.EX_        9    02/16/2000  05:02   393388  78272FBC
   PMDFMSG.DLL   PMDFMSG.DL_    15    02/15/2000  17:51    47736  5C2C7BFE
   PMDRAG.DLL    PMDRAG.DL_     18    07/10/2000  09:00     1731  0C66A7B9
   PMGPI.DLL     PMGPI.DL_       9    07/10/2000  08:49   248446  2AE8C77F
   PMGPI.TDF     PMGPI.TD_      18    07/10/2000  08:50    12338  C5049674
   PMGRE.DLL     PMGRE.DL_      18    07/10/2000  11:13     2231  A9989F54
   PMGRE.TDF     PMGRE.TD_      18    07/10/2000  18:36     1062  83A90269
   PMMERGE.DLL   PMMERGE.DL_     3    07/10/2000  18:36  1268513  98C83CE9
   PMMERGE.SYM   PMMERGE.SY_    13    07/10/2000  18:36   117492  7AF3BE44
   PMMLE.DLL     PMMLE.DL_      18    07/10/2000  11:19      673  8BCDB99C
   PMMRGRES.DLL  PMMRGRES.DL_   13    07/10/2000  13:05   135680  422BFABA
   PMPIC.DLL     PMPIC.DL_      15    07/10/2000  09:11    47206  41E9F653
   PMPIC.TDF     PMPIC.TD_      18    07/10/2000  11:28      400  AAA23CEB
   PMPRE.DLL     PMPRE.DL_      15    07/10/2000  13:48    46574  37ACF6EA
   PMPRINT.QPR   PMPRINT.QP_    17    07/08/2000  01:09    12175  2E251703
   PMREXX.EXE    PMREXX.EX_     16    07/10/2000  08:51    78885  227E3F2D
   PMSDMRI.DLL   PMSDMRI.DL_    17    07/10/2000  13:02    15360  AB192728
   PMSEEK.EXE    PMSEEK.EX_     17    07/14/2000  12:47    44597  26D202EC
   PMSHAPI.DLL   PMSHAPI.DL_    18    07/10/2000  08:57     4549  3A019933
   PMSHAPI.TDF   PMSHAPI.TD_    18    07/10/2000  18:36     6726  00294509
   PMSHELL.EXE   PMSHELL.EX_    18    07/07/2000  19:56     6028  FB27DB04
   PMSHLTKT.DLL  PMSHLTKT.DL_   16    03/27/2000  14:25    44232  A1AF6E0F
   PMSPL.DLL     PMSPL.DL_       8    07/08/2000  01:08   319185  E2ECB72C
   PMSPL.SYM     PMSPL.SY_      17    07/08/2000  01:08    32340  B29F8043
   PMSPL.TDF     PMSPL.TD_      18    07/07/2000  18:31     4491  2496CB45

   
                       FixPak Corrective Service levels and disk layouts  48


                   December 1, 2000 - Warp 4 FixPak XRSM014

   PMSPOOL.EXE   PMSPOOL.EX_    18    07/07/2000  18:31     9590  59511057
   PMUNIF.DLL    PMUNIF.DL_     15    07/10/2000  09:11    43823  388E4C47
   PMVDMP.DLL    PMVDMP.DL_     15    07/10/2000  13:14    46763  8C7707A9
   PMVDMP.TDF    PMVDMP.TD_     18    07/10/2000  18:45     2661  081AA3A4
   PMVIOP.DLL    PMVIOP.DL_     14    07/10/2000  13:14    64334  007B9C79
   PMVIOP.SYM    PMVIOP.SY_     18    07/10/2000  13:14     7620  45739949
   PMVIOP.TDF    PMVIOP.TD_     18    07/10/2000  18:45     3551  2638228D
   PMWIN.DLL     PMWIN.DL_      18    07/10/2000  08:52    11264  34AFB1B1
   PMWIN.TDF     PMWIN.TD_      18    07/10/2000  18:36     9567  AD32720E
   PMWIN32.SDF   PMWIN32.SD_    16    07/10/2000  08:54   313392  B4B196D2
   PMWINX.DLL    PMWINX.DL_      5    07/10/2000  13:12   530847  F0717B5E
   PMWP.DLL      PMWP.DL_        1    07/08/2000  16:39  1064287  17E82A88
   PMWP.SYM      PMWP.SY_       14    07/08/2000  16:39   103796  3594B87E
   PMWP.TDF      PMWP.TD_       18    07/08/2000  16:39    13825  69CBD318
   PMWPMRI.DLL   PMWPMRI.DL_    15    07/08/2000  00:58    59431  8ADFFA27
   PNP.DLL       PNP.DL_        14    07/07/2000  20:12    28297  9CBF2FB5
   PNP.SYS       PNP.SY_        18    05/01/2000  10:24     2152  ACA5CEF4
   PNPMRI.DLL    PNPMRI.DL_     17    07/08/2000  01:14    32293  6020D635
   PO.KBL        PO.KB_         18    05/02/2000  13:58      926  753BB321
   PRINT.COM     PRINT.CO_      17    07/14/2000  12:42    34177  539F4471
   PROCDUMP.DOC  PROCDUMP.DO_   17    11/22/1999  11:25    62998  5A68E87C
   PROCDUMP.EXE  PROCDUMP.EX_   16    02/16/2000  05:03    66591  D5190C08
   PROGMAN.EXE   PROGMAN.EX_    15    01/07/2000  22:44   116224  FC7FC67B
   PSFILES.EXE   PSFILES.EX_    18    07/14/2000  12:42    10229  BD5D4817
   PSSDMON.EXE   PSSDMON.EX_    17    01/04/2000  12:47    41533  692DEBFD
   PSSEMS.EXE    PSSEMS.EX_     17    07/14/2000  12:42    11717  947607E3
   PSTAT.EXE     PSTAT.EX_      17    07/14/2000  12:42    14661  9335A20F
   QUECALLS.DLL  QUECALLS.DL_   18    07/10/2000  16:55     1024  D0C33D88
   QUECALLS.TDF  QUECALLS.TD_   18    07/07/2000  19:16     1299  077B7179
   RAS001.MSG    RAS001.MS_     17    02/15/2000  17:43    33665  CFB7EA3F
   RASH.MSG      RASH.MS_       18    02/15/2000  17:43    13182  640D8F94
   README.DBG    README.DB_     18    03/27/2000  14:24     2463  236C4614
   RECOVER.COM   RECOVER.CO_    16    07/14/2000  12:48    46656  6A330D54
   REGCONV.EXE   REGCONV.EX_    16    11/24/1999  13:39    52758  22A69C95
   REGEDIT.HLP   REGEDIT.HL_    17    01/08/2000  00:32    22681  D82BDB13
   REGEDIT2.EXE  REGEDIT2.EX_    4    11/24/1999  13:40   970752  CFAD7880
   REGISTRY.DLL  REGISTRY.DL_   15    11/24/1999  13:02    81440  C24B145D
   REGISTRY.MSG  REGISTRY.MS_   18    11/24/1999  13:40      653  8C194676
   REGISTRY.TDF  REGISTRY.TD_   18    11/24/1999  13:02      984  E7DBD198
   REPLACE.EXE   REPLACE.EX_    16    07/14/2000  12:48    41584  C46F9642
   RESTORE.EXE   RESTORE.EX_    16    07/14/2000  12:48    39904  AFD11CE8
   REX.MSG       REX.MS_        18    03/27/2000  14:23     2865  6D459657
   REXX.DLL      CREXX1.DL_     10    03/27/2000  14:23   266031  75AA8B8E
   REXX.DLL      OREXX1.DL_      6    03/27/2000  14:23   490355  1A319A86
   REXX.IMG      REXX.IM_       12    03/27/2000  14:23   283636  D7EFB59D
   REXXAPI.DLL   REXXAPI.DL_    17    03/27/2000  14:23    40995  2E5FB324
   REXXC.EXE     REXXC.EX_      18    03/27/2000  14:23     2758  D085E1DF
   REXXCRT.DLL   REXXCRT.DL_    14    04/18/2000  09:33    79348  C11923D8
   REXXUTIL.DLL  REXXUTIL.DL_   14    03/27/2000  14:23    68119  4D504853
   REXXUTIL.DLL  ORXUTIL1.DL_   15    03/27/2000  14:23    41175  1BC75C60
   RINSTPRN.EXE  RINSTPRN.EX_   10    07/08/2000  01:30   212532  E5506AA3

   
                       FixPak Corrective Service levels and disk layouts  49


                   December 1, 2000 - Warp 4 FixPak XRSM014

   RO.KBL        RO.KB_         18    05/02/2000  13:58      944  AE24DAF5
   RSPDDI.EXE    RSPDDI.EX_     17    07/10/2000  19:00    29753  26264E10
   RSPDSPI.EXE   RSPDSPI.EX_    14    07/10/2000  14:11   143398  B1A9CEA6
   RSPIMRI.DLL   RSPIMRI.DL_    17    04/28/2000  13:36    18991  85E8A76B
   RSPINST.EXE   RSPINST.EX_     8    02/29/2000  14:11   430992  C62D5A9D
   RSRV.EXE      RSRV.EX_       14    07/10/2000  08:51    77987  1821AEDE
   RU.KBL        RU.KB_         18    05/02/2000  13:58     1144  A01D23D0
   RXVIDCFG.DLL  RXVIDCFG.DL_   17    04/11/2000  13:20    14741  A1C4BF07
   SBFILTER.DLL  SBFILTER.DL_   17    05/15/2000  16:24    14861  430E54D2
   SCENTER.DLL   SCENTER.DL_     8    07/08/2000  01:23   295171  96B82895
   SD.KBL        SD.KB_         18    05/02/2000  13:58     1036  57F02175
   SEAMLESS.DLL  SEAMLESS.DL_   16    07/10/2000  18:45    49167  F12DF519
   SECUTIL.DLL   SECUTIL.DL_    17    01/04/2000  12:47    21468  EE210CBF
   SEINST.EXE    SEINST.EX_     16    07/10/2000  18:47    48707  49B54850
   SEMAINT.EXE   SEMAINT.EX_    15    02/29/2000  14:01    68032  A147D4D8
   SERIAL.PDR    SERIAL.PD_     17    07/08/2000  01:04    19166  5D30A113
   SESAPI.DLL    SESAPI.DL_     17    01/04/2000  09:08    24203  4954FAD8
   SESDD32.SYS   SESDD32.SY_    11    01/04/2000  12:47   118834  8B2CEEE2
   SESMGR.DLL    SESMGR.DL_     18    07/10/2000  16:55     1536  5D34B91C
   SESMGR.TDF    SESMGR.TD_     18    07/07/2000  19:16     1877  C00D0D50
   SETBOOT.EXE   SETBOOT.EX_    17    07/14/2000  12:46    20912  3510EF53
   SETDEFV.CMD   SETDEFV.CM_    18    05/26/2000  11:24     1652  A27ED904
   SF.KBL        SF.KB_         18    05/02/2000  13:58     1036  E60919F6
   SHPIINST.DLL  SHPIINST.DL_   16    07/10/2000  18:29    37310  BCE8ADA2
   SK.KBL        SK.KB_         18    05/02/2000  13:58     1008  0DDD0227
   SL.KBL        SL.KB_         18    05/02/2000  13:58      982  1C59EC3B
   SOFTDRAW.DLL  SOFTDRAW.DL_    6    07/10/2000  08:43   416439  5D8F99B2
   SOM.DLL       SOM.DL_        13    06/30/1999  16:33    92009  A7ACA245
   SORT.EXE      SORT.EX_       17    07/14/2000  12:42    32127  0B096EB8
   SPCHOBJ.DLL   SPCHOBJ.DL_    12    12/21/1997  01:27   132899  E393FAB7
   SPL1B.DLL     SPL1B.DL_      18    07/07/2000  18:31     7125  B590CA2B
   SPOOLCP.DLL   SPOOLCP.DL_    18    07/07/2000  18:43    10210  F366BF98
   SQ.KBL        SQ.KB_         18    05/02/2000  13:58      824  194055C4
   SSM.DLL       SSM.DL_        18    06/27/2000  12:38     4118  07DBD369
   SSMDD.SYS     SSMDD.SY_      17    06/27/2000  12:38    36813  5C87C194
   STRACE.EXE    STRACE.EX_     16    07/14/2000  12:49    55943  D5E002C9
   SUBST.EXE     SUBST.EX_      18    07/14/2000  12:41     4520  4CB1D009
   SV.KBL        SV.KB_         18    05/02/2000  13:58      946  45F10742
   SVMC.DLL      SVMC.DL_       13    06/27/2000  12:44    98391  44EAA8BD
   SVSH.DLL      SVSH.DL_        4    06/27/2000  12:46    23454  C6A6AC21
   SW.DLL        SW.DL_         14    06/27/2000  12:40    66505  5156D57E
   SWITCHRX.CMD  SWITCHRX.CM_   18    03/27/2000  14:23     7928  D9429FC3
   SYMB.PFM      SYM1.PF_       18    11/22/1999  11:22      679  EFD0E0BD
   SYSDUMP.EXE   SYSDUMP.EX_    17    02/16/2000  05:03    28701  D6657DF8
   SYSINST2.EXE  SYSINST2.EX_   12    02/29/2000  14:07   185104  A649C29C
   SYSINSTX.COM  SYSINSTX.CO_   16    07/14/2000  12:42    40128  EE2F3B0B
   SYSLEVEL.EXE  SYSLEVEL.EX_   16    02/29/2000  14:12    45088  29985D96
   SYSLEVEL.FPK  SYSLEVEL.FP_   18    05/03/2000  11:16      165  110D9568
   SYSLEVEL.MSG  SYSLEVEL.MS_   18    02/29/2000  14:12     1597  7F38746B
   SYSLOGPM.EXE  SYSLOGPM.EX_   12    02/15/2000  11:46   215355  44F9D47F
   SYSMONO.FON   SYSMONO.FO_    17    07/10/2000  11:30    21294  AE8E04A2

   
                       FixPak Corrective Service levels and disk layouts  50


                   December 1, 2000 - Warp 4 FixPak XRSM014

   SYSMONOI.FON  SYSMONOI.FO_   16    07/10/2000  09:10    35841  C9B7405A
   SYSSPLIT.CMD  SYSSPLIT.CM_   18    11/22/1999  11:25     3712  A30ABDC8
   TDFLST.CMD    TDFLST.CM_     18    11/22/1999  11:25    13564  7C9D3592
   TEDIT.EXE     TEDIT.EX_       2    07/14/2000  12:48     9516  8B3452B2
   TEDIT.HLP     TEDIT.HL_      18    07/14/2000  12:36    14597  1A37B7B6
   TESTCFG.SYS   TESTCFG.SY_    18    04/22/2000  10:58     9808  77E8524C
   TEXTCON1.EXE  TEXTCON1.EX_    9    11/23/1999  20:12    49011  D916B736
   TFFLST.CMD    TFFLST.CM_     18    11/22/1999  11:25     4638  ECEE15D0
   TIMES.FON     TIMES.FO_      12    07/10/2000  09:15   166150  F0A54AA4
   TIMESI.FON    TIMESI.FO_     11    07/10/2000  09:10   181173  0CAE973A
   TNR.OFM       TNR.OF_        18    11/22/1999  11:22     6809  F535154B
   TNR.PFB       TNR.PF_        10    11/22/1999  11:24   145785  BD3D5D3E
   TNR.PFM       TN1.PF_        18    11/22/1999  11:22     1103  47C0CE38
   TNRB.OFM      TNRB.OF_       18    11/22/1999  11:22     6825  90C2110A
   TNRB.PFB      TNRB.PF_       10    11/22/1999  11:24   148564  FD51D0FF
   TNRB.PFM      TNR1.PF_       18    11/22/1999  11:22     1112  6044B103
   TNRBI.OFM     TNRBI.OF_      18    11/22/1999  11:22     6839  75E9C7B5
   TNRBI.PFB     TNRBI.PF_       9    11/22/1999  11:24   159652  799D1739
   TNRBI.PFM     TNRB1.PF_      18    11/22/1999  11:22     1118  668275CD
   TNRI.OFM      TNRI.OF_       18    11/22/1999  11:22     6830  23B86292
   TNRI.PFB      TNRI.PF_        9    11/22/1999  11:24   157010  3E81358A
   TNRI.PFM      TNR2.PF_       18    11/22/1999  11:22     1114  A1EE659D
   TR.KBL        TR.KB_         18    05/02/2000  13:58      962  E4CD3417
   TR440.KBL     TR440.KB_      18    05/02/2000  13:58     1042  D92401B1
   TRACE.DOC     TRACE.DO_      17    01/21/2000  10:05    64057  35DDD52A
   TRACE.EXE     TRACE.EX_      10    07/14/2000  12:49    56064  C5DF4434
   TRACEDLL.DLL  TRACEDLL.DL_   15    02/16/2000  04:57    46987  B5F413F0
   TRACEFMT.EXE  TRACEFMT.EX_   12    07/14/2000  12:53   232067  C8306334
   TRACEGET.EXE  TRACGET1.EX_   17    02/16/2000  04:57    29930  FC507660
   TRACEGET.EXE  TRACEGET.EX_   17    02/16/2000  04:57    29930  FC507660
   TRAPDUMP.EXE  TRAPDUMP.EX_   17    02/16/2000  05:03    30236  B98D9F97
   TRAPLOG.EXE   TRAPLOG.EX_    17    02/16/2000  05:03    28191  E269D501
   TRC0000.TFF   TRC0000.TF_    18    07/10/2000  15:50      189  ACDB2628
   TRC0001.TFF   TRC0001.TF_    18    11/24/1999  13:02     1370  17FD0D51
   TRC0003.TFF   TRC0003.TF_    18    07/10/2000  15:50     1503  22AD8690
   TRC0004.TFF   TRC0004.TF_    18    07/10/2000  15:50     4754  3A7C826C
   TRC0005.TFF   TRC0005.TF_    17    07/10/2000  15:50    40960  3B101E43
   TRC0006.TFF   TRC0006.TF_    18    07/10/2000  15:50    12356  A56F674E
   TRC0007.TFF   TRC0007.TF_    18    06/26/2000  17:05     3336  60333D47
   TRC0008.TFF   TRC0008.TF_    18    05/01/2000  09:45      544  457B0ED2
   TRC0010.TFF   TRC0010.TF_    18    07/07/2000  19:16    13647  C63B4E1D
   TRC0012.TFF   TRC0012.TF_    18    07/10/2000  16:55     1247  4B139E45
   TRC0016.TFF   TRC0016.TF_    18    07/07/2000  19:16     1673  8107031E
   TRC0017.TFF   TRC0017.TF_    18    07/07/2000  19:16     5561  9CB3BD6D
   TRC0018.TFF   TRC0018.TF_    18    07/07/2000  19:16    39488  E5061365
   TRC006D.TFF   TRC006D.TF_    18    06/05/2000  11:01    24181  FB8A7590
   TRC00C0.TFF   TRC00C0.TF_    18    07/10/2000  18:36    15970  16FA7C66
   TRC00C2.TFF   TRC00C2.TF_    18    07/10/2000  18:36    25994  6C380A05
   TRC00C3.TFF   TRC00C3.TF_    18    07/10/2000  18:36     3984  166F4ABD
   TRC00C4.TFF   TRC00C4.TF_    18    07/10/2000  11:28      288  62404CA4
   TRC00C5.TFF   TRC00C5.TF_    18    07/10/2000  08:50    32994  86F3DE98

   
                       FixPak Corrective Service levels and disk layouts  51


                   December 1, 2000 - Warp 4 FixPak XRSM014

   TRC00C6.TFF   TRC00C6.TF_    18    07/07/2000  18:31     7146  F49E15E9
   TRC0100.TFF   TRC0100.TF_    18    07/10/2000  15:50     7219  9B08089B
   TRC0101.TFF   TRC0101.TF_    18    07/10/2000  15:50     7968  B40BA9EE
   TRC0102.TFF   TRC0102.TF_    18    07/10/2000  15:50    29153  76D3DC86
   TRC0103.TFF   TRC0103.TF_    18    07/10/2000  15:50     9590  88EB8E49
   TRC0104.TFF   TRC0104.TF_    18    07/10/2000  15:50     5134  610874D1
   TRC0105.TFF   TRC0105.TF_    18    07/10/2000  15:50    24421  A4291FDC
   TRC0106.TFF   TRC0106.TF_    18    07/10/2000  15:50     1549  A4AE5090
   TRC0108.TFF   TRC0108.TF_    18    07/10/2000  15:50     9505  82F6E03D
   TRC0109.TFF   TRC0109.TF_    18    07/10/2000  15:50     2535  CF7D884C
   TRC010A.TFF   TRC010A.TF_    18    07/10/2000  15:50     1130  8578C180
   TRC0118.TFF   TRC0118.TF_    18    05/03/2000  18:33     2526  4717B305
   TRC0119.TFF   TRC0119.TF_    18    05/03/2000  18:49     3786  6E15888C
   TRC012C.TFF   TRC012C.TF_    18    07/10/2000  18:45     5361  356B9470
   TRC012D.TFF   TRC012D.TF_    18    07/10/2000  18:45     7870  B5F5F31F
   TRC012E.TFF   TRC012E.TF_    18    07/08/2000  16:39    32972  8DB93D02
   TRCFORMT.DLL  TRCFORMT.DL_   17    07/14/2000  12:53    27427  6AE0ED23
   TRCUST.EXE    TRCUST.EX_     15    07/14/2000  12:49    98773  300DF44D
   TREE.COM      TREE.CO_       17    07/14/2000  12:42    34265  6C9CE445
   TRSPOOL.DOC   TRSPOOL.DO_    18    11/22/1999  11:25     6638  7C5EA5F1
   TRSPOOL.EXE   TRSPOOL1.EX_   17    02/16/2000  04:57    42054  5A243F00
   TRSPOOL.EXE   TRSPOOL.EX_    15    02/16/2000  04:57    42054  5A243F00
   TRSTOP.EXE    TRSTOP.EX_     16    02/16/2000  04:57    23486  87EB78A6
   TRUETYPE.DLL  TRUETYPE.DL_   12    04/12/2000  11:40   128567  2666C3D5
   UA.KBL        UA.KB_         18    05/02/2000  13:58     1476  93B79B1A
   UCDFS.DLL     UCDFS.DL_      17    02/16/2000  20:08    13264  67A4FAF2
   UCONV.DLL     UCONV.DL_      17    05/02/2000  14:03    22819  68476AC4
   UHPFS.DLL     UHPFS.DL_      14    05/03/2000  18:46   107024  9FF24556
   UK.KBL        UK.KB_         18    05/02/2000  13:58      816  17ED40AF
   UK168.KBL     UK168.KB_      18    05/02/2000  13:58      850  E83DE4C5
   ULSACT01.MSG  ULSACT01.MS_   18    11/23/1999  13:33      907  CD00C941
   ULSCAU01.MSG  ULSCAU01.MS_   18    11/23/1999  13:33      899  5B31B92F
   ULSDET01.MSG  ULSDET01.MS_   11    11/23/1999  13:33      903  A0B373BE
   ULSERR01.MSG  ULSERR01.MS_   18    11/23/1999  13:33     1967  E993FAC5
   UNDELETE.COM  UNDELETE.CO_   16    07/14/2000  12:53    36953  AF9A6E7A
   UNICODE.SYS   UNICODE.SY_    17    05/02/2000  13:58    20014  B3F4B81D
   UNIKBD.DLL    UNIKBD.DL_     16    05/02/2000  13:58    28291  EDE0E341
   UNINSTAL.EXE  UNINSTAL.EX_   13    07/18/2000  15:26    97817  2885DCED
   UNPACK2.EXE   UNPACK2.EX_    15    07/10/2000  19:14    80256  61C3E083
   USER.EXE      USER.EX_        7    01/07/2000  23:00   281328  C284D86D
   USINTER.KBL   USINTER.KB_    18    05/02/2000  13:58     1032  520E355E
   VBIOS.SYS     VBIOS.SY_      18    11/23/1999  11:25     8816  627FD9BA
   VCMOS.SYS     VCMOS.SY_      18    11/23/1999  11:26     2272  AD968EC6
   VDMA.SYS      VDMAPS2.SY_    17    11/23/1999  11:26    14329  8D462838
   VDMA.SYS      VDMAAT.SY_     18    11/23/1999  11:26    11465  C8ECE7C9
   VDPMI.SYS     VDPMI.SY_      17    11/23/1999  11:27    30626  DD8A4718
   VDPX.SYS      VDPX.SY_       17    11/23/1999  11:27    26322  7092BE9B
   VGA.DSP       VGA.DS_        18    03/15/2000  11:19     8731  13A18436
   VIDEOCFG.DLL  VIDEOCFG.DL_   16    07/10/2000  14:04    38126  0BF70FBC
   VIEW.EXE      VIEW.EX_       16    07/10/2000  13:13    33436  C0A3FD03
   VIOCALLS.DLL  VIOCALLS.DL_   18    07/10/2000  09:14     2048  E62C26F1

   
                       FixPak Corrective Service levels and disk layouts  52


                   December 1, 2000 - Warp 4 FixPak XRSM014

   VIOTBL.DCP    VIOTBL.DC_     16    05/02/2000  13:58   225355  4051C69E
   VIOTBL.ISO    VIOTBL.IS_     16    05/02/2000  13:58   230105  2A27321C
   VMAN.DLL      VMAN.DL_       15    07/10/2000  19:17    46649  75F2E672
   VMANWIN.SYS   VMANWIN.SY_    18    07/10/2000  14:07     3040  A2F3E28C
   VPIC.SYS      VPIC.SY_       18    11/23/1999  11:29     9942  A81F3717
   VPICPARM.SYS  VPICPARM.SY_   18    11/23/1999  11:29      736  9C451DBC
   VTIMER.SYS    VTIMER.SY_     18    11/23/1999  11:29    10560  38AF4628
   VW32S.SYS     VW32S.SY_      17    11/23/1999  11:31    18338  CACBEB20
   VWIN.SYS      VWIN.SY_        1    11/23/1999  11:30    27104  94B27BC6
   WCFGMRI.DLL   WCFGMRI.DL_    18    07/08/2000  01:02     6694  5FFE2327
   WD24B.DSP     WD24B.DS_      18    03/15/2000  11:19    32662  692B35CF
   WELCMMRI.DLL  WELCMMRI.DL_   17    07/08/2000  01:36    14409  B52000C1
   WINCFG.DLL    WINCFG.DL_     17    07/08/2000  16:44    13379  2ACDDE29
   WINFILE.EXE   WINFILE.EX_    13    01/07/2000  22:45   150016  987619F8
   WINSCLIP.DLL  WINSCLIP.DL_    7    01/07/2000  22:41    14848  463E0478
   WINSDDE.DLL   WINSDDE.DL_    17    01/07/2000  22:41    18432  A7B84F73
   WINSHELD.EXE  WINSHELD.EX_   17    01/07/2000  22:41    22528  C5601565
   WINSMSG.DLL   WINSMSG.DL_    17    01/07/2000  22:41    28441  ED70A21E
   WPCLS.IMP     WPCLS.IM_      18    03/27/2000  14:23     8661  DA29AF82
   WPCOMET.DLL   WPCOMET.DL_    18    07/10/2000  13:06     8752  3E4C1153
   WPCONFIG.DLL  WPCONFIG.DL_    8    07/08/2000  01:00   266408  F668A180
   WPCONMRI.DLL  WPCONMRI.DL_   17    07/08/2000  01:02    33328  29426149
   WPDSRVP.DLL   WPDSRVP.DL_    17    07/07/2000  18:44    14194  8F0C529E
   WPHELP.HLP    WPHELP.HL_      5    02/24/2000  18:22   889907  BDDFD1EB
   WPINET.DLL    WPINET.DL_     13    07/08/2000  17:04   117180  7FD8EA67
   WPINTMRI.DLL  WPINTMRI.DL_   17    07/08/2000  01:19    11836  81D3A2EF
   WPMSG.HLP     WPMSG.HL_      16    05/04/2000  18:34    56112  A3D852A6
   WPPRINT.DLL   WPPRINT.DL_     2    07/07/2000  20:04   364102  2D3097F0
   WPPRINT.HLP   WPPRINT.HL_    14    07/08/2000  01:07    78589  E442F773
   WPPRTMRI.DLL  WPPRTMRI.DL_   15    07/08/2000  01:07    69551  8A49B698
   WPREXX.IMP    WPREXX.IM_      8    03/27/2000  14:23     6313  84A2963F
   WPSINIT.WPS   WPSINIT.WP_    18    03/27/2000  14:23    15877  ACCB46D9
   WPSINST.CMD   WPSINST.CM_    18    03/27/2000  14:23     2813  02ED1427
   WW.EXE        WW.EX_          5    07/16/1998  14:31     8305  1F6A9079
   WWDLL.DLL     WWDLL.DL_       8    12/21/1997  01:29   276981  751EB912
   WWHOOK.DLL    WWHOOK.DL_     17    12/21/1997  01:29    27230  693E24F2
   XCOPY.EXE     XCOPY.EX_      16    07/14/2000  12:43    53376  FFF2E255
   XPG00420.TBL  XPG00420.TB_   18    11/22/1999  12:17    27264  C8667C5C
   XPG00864.TBL  XPG00864.TB_   13    11/22/1999  12:17    27264  16725C7C

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


   
                       FixPak Corrective Service levels and disk layouts  53


                   December 1, 2000 - Warp 4 FixPak XRSM014

   Default directories:

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

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   OS2LDR        OS2LDR.___     18    07/07/2000  20:56    45056  57DEA542

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

   Default directories:

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

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPDBUTL.DLL  APPDBUTL.DL_   18    02/25/2000  12:15    23529  C6AC16E4
   APPSTART.EXE  APPSTART.EX_   18    02/25/2000  12:15    33858  D1711D29
   NCAPPUTL.EXE  NCAPPUTL.EX_   18    02/25/2000  12:15    14624  2B3765C8
   OS2LDR        OS2LDR.___     18    07/07/2000  20:58    45056  6E274302

   
                       FixPak Corrective Service levels and disk layouts  54


                   December 1, 2000 - Warp 4 FixPak XRSM014

   PMLOGON.EXE   PMLOGON.EX_    18    01/24/2000  11:20    40109  3D5B81CD
   PRNCFG.DLL    PRNCFG.DL_     18    01/24/2000  11:21    81090  2DB0E57B
   TDESK.DLL     TDESK.DL_      18    01/25/2000  01:53     3909  7E2D18EB
   TLOGOFF.EXE   TLOGOFF.EX_    18    01/25/2000  01:53     9581  388C40EC
   TOBJECT.DLL   TOBJECT.DL_    18    01/25/2000  01:53     4970  44345678
   TSHUTDWN.EXE  TSHUTDWN.EX_   18    01/25/2000  01:53     8695  9CBAC1E3

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

   Default directories:

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

   Files contained in Fixpak for product:

   Filename      Name on CSD   Disk#  Date        Time   Size     Checksum
   ------------  ------------  -----  ----------  -----  -------  --------
   APPSTART.EXE  APPSTART.EX_   18    03/22/2000  10:08    35022  C8F2F444
   GENGRADD.FIT  GENGRADD.FI_   18    07/18/2000  18:36      472  A180D14F
   IBM300G2.FIT  IBM300G2.FI_   18    07/18/2000  18:36      416  3B2EDDD6
   NCAPPUTL.EXE  NCAPPUTL.EX_   18    03/22/2000  10:08    21270  DAA72249
   NCMONIT.DLL   NCMONIT.DL_    18    07/17/2000  14:14    55035  278CEDEE
   OS2LDR        OS2LDR.___     18    07/07/2000  20:58    45056  6E512302
   PMLOGON.EXE   PMLOGON.EX_    18    07/17/2000  15:34    57813  3F2101E0
   TSHUTDWN.EXE  TSHUTDWN.EX_   18    02/15/2000  12:41    10795  F1311ADA









   
                       FixPak Corrective Service levels and disk layouts  55


                   December 1, 2000 - Warp 4 FixPak XRSM014

   10.0 SPACE UTILIZATION

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

   Space needed   Drive
   Up to 2MB      C:
   Up to 2MB      Boot drive (4MB if boot is C:)
   Up to 22MB     Drive with most free space, holds deferred files if
                  A:SERVICE method used.
   Up to 38MB     FixPak Archive/Backup for product with CSD level of
                  XRS4000
   Up to 38MB     FixPak Archive/Backup for product with CSD level of
                  XRS4010

   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  56


                   December 1, 2000 - Warp 4 FixPak XRSM014

   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  57
