home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 28 Fixes4x
/
28-Fixes4x.zip
/
xr_m012.1dk
/
README.1ST
< prev
next >
Wrap
Text File
|
1999-09-29
|
126KB
|
3,248 lines
< Installation instructions for Warp 4 FixPak XR_M012
September 29, 1999
This FixPak makes the products it services Year 2000 ready
Build level 9.036
This FixPak applies to:
CSD Level: XR_4000 Warp 4
Component ID: 5639A6100
Version: 4.00
Type: 0C
CSD Level: XR_4010 WorkSpace On Demand Release 1
Component ID: 5639A6100
Version: 4.01
Type: 0C
CSD Level: XR_4010 WorkSpace On Demand Release 2
Component ID: 5639A6120
Version: 4.01
Type: 0C
Requires Corrective Service Facility release f.141 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
September 29, 1999 - Warp 4 FixPak XR_M012
September 29, 1999 - Warp 4 FixPak XR_M012
Page ii
September 29, 1999 - Warp 4 FixPak XR_M012
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3
3.0.1 OS2DASD.DMD popup during install . . . . . . . . . . . . . . 3
3.0.2 Device Drivers removed from Fixpak . . . . . . . . . . . . . 3
3.0.3 Can't install Warp 4 . . . . . . . . . . . . . . . . . . . . 3
3.0.4 Please use Fixtool f.141 or later . . . . . . . . . . . . . 3
3.0.5 OS2DUMP split into two versions . . . . . . . . . . . . . . 3
3.0.6 TRAP in ES16881$ after FP10 applied . . . . . . . . . . . . 4
3.0.7 System Sounds not working after FixPak applied . . . . . . . 5
3.0.8 Using Display Recovery Choices . . . . . . . . . . . . . . . 5
3.0.9 Installation of Java 1.1.4 . . . . . . . . . . . . . . . . . 6
3.0.10 DSPRES.DLL included in this FixPak . . . . . . . . . . . . 6
3.0.11 No products were found . . . . . . . . . . . . . . . . . . 6
3.0.12 Previous installation interrupted . . . . . . . . . . . . . 7
3.0.13 Unable to open Archive directory . . . . . . . . . . . . . 7
3.0.14 RC 932 doing CID install of Warp 4 . . . . . . . . . . . . 8
3.0.15 Multimedia no longer selectable . . . . . . . . . . . . . . 9
3.0.16 MMPARTS.DLL/USER.EXE popup during install . . . . . . . . . 9
3.0.17 CSF0208 No products were found on the target ... . . . . . 9
3.0.18 CSF0248 Archive path is shared between mismatched . . . . . 9
3.0.19 CSF0249 Error opening or creating archive file. . . . . . 10
3.0.20 Printer installation process change . . . . . . . . . . . 10
3.0.21 Configuration Installation Distribution ( CID ) . . . . . 10
4.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 11
4.0.1 New Message Box in fix for APAR JR12954 . . . . . . . . . . 11
4.0.2 RAS file changes . . . . . . . . . . . . . . . . . . . . . 11
4.0.3 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 12
4.0.4 Windows printer drivers leave a zombie thread running . . . 12
4.0.5 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . . . . 13
4.0.6 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . . . 13
4.0.7 Intermittent hangs . . . . . . . . . . . . . . . . . . . . 13
5.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 14
5.2 Querying file dates for files after Dec 31, 1999 in REXX . . . 14
5.3 Enhanced support for Workspace On-Demand . . . . . . . . . . . 15
5.3.1 PMLOGON user exits . . . . . . . . . . . . . . . . . . . . 15
5.3.2 Setup strings for public applications . . . . . . . . . . . 18
5.3.3 Command line options for TLOGOFF and TSHUTDWN . . . . . . . 19
5.3.4 PMLOGON No Progress Indicator option . . . . . . . . . . . 19
5.3.5 PMLOGON No System Modal Window option . . . . . . . . . . . 20
5.4 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.4.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 20
5.4.2 Where Euro is not supported . . . . . . . . . . . . . . . . 21
Contents iii
September 29, 1999 - Warp 4 FixPak XR_M012
5.4.3 Printing the Euro . . . . . . . . . . . . . . . . . . . . . 22
5.5 New Warp Registry Editor . . . . . . . . . . . . . . . . . . . 22
5.6 WorkSpace On Demand . . . . . . . . . . . . . . . . . . . . . . 22
5.7 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.8 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 23
5.9 Joliet-2 support in CDFS.IFS . . . . . . . . . . . . . . . . . 23
5.10 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 23
5.10.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 23
5.10.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 25
5.11 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 26
5.11.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 26
5.11.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.11.3 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.11.4 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.12 Other README files . . . . . . . . . . . . . . . . . . . . . . 28
6.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 29
6.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 29
6.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 29
6.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 30
6.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . . . . 30
6.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 31
6.4 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 32
7.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 34
7.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 34
7.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 34
7.3 Method 2: Install from alternate bootable media . . . . . . . . 35
7.4 Additional Corrective Service Facility information . . . . . . 36
7.5 FixPaks on CD-ROM . . . . . . . . . . . . . . . . . . . . . . . 36
8.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 37
8.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 38
9.0 FixPak Corrective Service levels and disk layouts . . . . . . . 39
10.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 52
10.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 52
10.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 53
Contents iv
September 29, 1999 - Warp 4 FixPak XR_M012
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_M012 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
XR_M012 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
September 29, 1999 - Warp 4 FixPak XR_M012
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
September 29, 1999 - Warp 4 FixPak XR_M012
3.0 INSTALLATION NOTES
3.0.1 OS2DASD.DMD POPUP DURING INSTALL
If you get a popup for module OS2DASD.DMD saying file on system is later
than the one in this FixPak, reply "No" to replace it.
3.0.2 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.3 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.4 PLEASE USE FIXTOOL F.141 OR LATER
Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
Corrective Service Facility f.141 or later. It has fixes for problems
found in previous CSF builds as well as a fix to support RIPL servers
where there may be in excess of 250 SYSLEVEL files. It also handles the
type 1 (All FixPaks prior to 10 and 40) and type 2 (FixPaks 10 and 40 and
later) FixPaks.
If you try to use a CSF level prior to f.141 you will get a "CSF0208 No
products were found on the target system to service" message.
3.0.5 OS2DUMP SPLIT INTO TWO VERSIONS
OS2Dump has been split into two versions. If you are installing this
fixpak on PS/2 model 9595 machines, use the version located on the last
fixpak diskette. Also, if you are running older hardware (486s or early
Pentiums), you may wish to use the OS2Dump located on the last fixpak
diskette.
Installation Notes 3
September 29, 1999 - Warp 4 FixPak XR_M012
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.6 TRAP IN ES16881$ AFTER FP10 APPLIED
We do not ship any of the ESS sound card drivers in this Fixpak. To
corrrect the problem, get the latest ESS device driver for your card from
the OS/2 Device Driver Pak online at
http://service.software.ibm.com/os2ddpak/html/multimed/esstechn
Do this before you install the FixPak.
Installation Notes 4
September 29, 1999 - Warp 4 FixPak XR_M012
3.0.7 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.8 USING DISPLAY RECOVERY CHOICES
If you have the "Display Recovery Choices at each system startup"
function active on your system, you need to disable it before you apply a
FixPak if
■ The system is running
■ The boot partition will be serviced.
Installation Notes 5
September 29, 1999 - Warp 4 FixPak XR_M012
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.9 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.10 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.11 NO PRODUCTS WERE FOUND
If you see a "No products were found" message while applying this FixPak,
there is probably a mismatch between the data in
\OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this FixPak.
Compare the data for the OS/2 Base Operating System from the SYSLEVEL
command output with the same values listed at the end of this document in
the "FixPak Corrective Service levels and disk layouts" section. They
must be identical.
If these values are correct, check for the following files on any OS/2
boot drive in the \OS2\INSTALL directory.
LOGF0000.OS2
LOGSTART.OS2
LOGARCH.OS2
Installation Notes 6
September 29, 1999 - Warp 4 FixPak XR_M012
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.12 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.13 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 7
September 29, 1999 - Warp 4 FixPak XR_M012
3.0.14 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 8
September 29, 1999 - Warp 4 FixPak XR_M012
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.15 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.16 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL
If you get a popup about MMPARTS.DLL or USER.EXE during install, reply
"Yes" to replace it.
3.0.17 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.18 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 9
September 29, 1999 - Warp 4 FixPak XR_M012
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.19 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.20 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.21 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 10
September 29, 1999 - Warp 4 FixPak XR_M012
4.0 POST INSTALLATION NOTES
4.0.1 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.2 RAS FILE CHANGES
Beginning with FixPak 11, the following files are being added to the
\OS2\SYSTEM directory. If they also exist in the \OS2 directory you can
delete them as they are no longer needed there.
■ DTRACE.EXE
■ TRACEFMT.EXE
■ TRSPOOL.EXE
If you do not delete them from the \OS2 directory, they will be serviced
the same as the ones in the \OS2\SYSTEM directory to keep them current.
Also, the following files in the \OS2\SYSTEM\RAS directory can be deleted
as they have been superseded as shown:
File Superseded by
MDTRACE.doc DTRACE.DOC
MTRSPOOL.DOC TRSPOOL.DOC
Post Installation Notes 11
September 29, 1999 - Warp 4 FixPak XR_M012
4.0.3 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.4 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING
A problem occurs with some Windows printer drivers where a zombie thread
is left running after the program that loaded it is exited.
This does not occur when the program is run from a Seamless instance of
PROGMAN or from a Full Screen session because when these are exited the
whole WINOS2 Subsystem is exited.
This problem has been reported for the Adobe and Hewlett Packard Windows
printer drivers. To correct this problem for people running with these
drivers ONLY who have experienced symptoms such as:
■ exiting a program running seamlessly after printing or
■ setting up a printer and seeing the icon not being unhatched and/or
■ not being able to start another copy of the program
Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot*
section:
■ backgroundtasks=run_enum.exe,hpfbkg02.exe
then restart WINOS2.
Note: There may be other drivers that have the same problem. If you
experiences a similar problem with other drivers, please report it so the
correct SYSTEM.INI entry can be determined.
Post Installation Notes 12
September 29, 1999 - Warp 4 FixPak XR_M012
4.0.5 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.6 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.7 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 13
September 29, 1999 - Warp 4 FixPak XR_M012
5.0 NEW FUNCTION
It is our policy not to include new function in FixPaks. However, as with
any policy there may be exceptions. If any exception occurs in the
future, we will communicate them to you in this section of the
README.1ST.
5.1 SERVICEABILITY (RAS) ENHANCEMENTS
With FixPak 35 for Warp 3.0 and FixPak 10 for Warp 4.0 major enhancements
were provided to the system diagnostic tools (RAS Enhancements). They
provide major functional enhancements to the System Trace and Process
Dump facilities. Full details of these enhancements can be found in the
README.DBG file that will be found in the \OS2\INSTALL directory after
this FixPak is installed.
Other associated documentation may be found in:
■ OS2\SYSTEM\RAS\TRACE.DOC
■ OS2\SYSTEM\RAS\DTRACE.DOC
■ OS2\SYSTEM\RAS\PROCDUMP.DOC
■ OS2\SYSTEM\RAS\TRSPOOL.DOC
Always refer to README.DBG for details of any RAS enhancements delivered
with a FixPak.
5.2 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX
Existing REXX functions return file dates with a two digit year only.
While these functions are Year 2000 tolerant (i.e. the results will be
correct for files dated after Dec 31, 1999) they require some additional
logic in existing programs to handle the returned date correctly when
they are compared with other file dates.
Since the output format of the existing functions could not be changed
for compatibility reasons, new options have been added to the REXX
interpreter to return file dates with the year formatted with 4 digits.
Two functions have been extended to support the new format. The syntax to
retrieve the file date in 4 digit format is as follows:
New Function 14
September 29, 1999 - Warp 4 FixPak XR_M012
/********************************************/
/* Use STREAM QUERY TIMESTAMP to query file */
/* date in 4 digit format */
/********************************************/
Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP")
/***********************************************/
/* Use option "L" with SysFileTree to return a */
/* list of files with long date format */
/***********************************************/
Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
Call SysLoadFuncs
Call SysFileTree "C:\*.*", "Files", "L"
Do i = 1 To Files.0
Say Files.i
End
These extensions are available in both classic REXX and Object REXX on
OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these
extensions in your program you have to make sure that you are running the
right level of REXX
5.3 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND
5.3.1 PMLOGON USER EXITS
This function, provided by PMLOGON, allows system integrators to have
REXX code executed at specific points during the startup and logon
sequence. By default, user exits are disabled in PMLOGON.EXE. To enable
user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the
CONFIG.SYS file must be added. The /URX parameter specifies the location
and name of the user exit command file:
Execution Parameter User Exit command file that will be
executed
------------------- -----------------------------------
/URX \OS2\PMLOGURX.CMD
/URX:<filename>.CMD <filename>.CMD located in one of the
locations specified by the PATH
environment variable
/URX:d:\<path>\<filename>.CMD d:\<path>\<filename>.CMD
New Function 15
September 29, 1999 - Warp 4 FixPak XR_M012
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 16
September 29, 1999 - Warp 4 FixPak XR_M012
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 17
September 29, 1999 - Warp 4 FixPak XR_M012
processing. If no string is returned, then the
normal logon failure or password expired message
box is displayed.
Note 1: The session environment for the REXX command file is that
of PMLOGON.EXE and, therefore, does not contain any input or
output facility. For example, "PULL" from the keyboard and
"SAY" to the console do not work.
Note 2: The /AUTO parameter is validated at every step (for example,
after command line processing, after exit 0 returns, and
after exit 1 returns). It is turned off if insufficient
information (such as no user ID) is provided at that stage
for an automatic logon. If the user ID is supplied by the
exit, that exit must also provide the /AUTO parameter in
order for an auto logon to work.
5.3.2 SETUP STRINGS FOR PUBLIC APPLICATIONS
The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific
Workplace Shell WPProgram setup strings that are provided when creating
public applications on the WorkSpace On-Demand Desktop. In particular,
the ICONPOS setup string can be defined for a public application so that
the Administrator can identify where application icons are placed on the
WorkSpace On-Demand Desktop.
When a WorkSpace On-Demand Administrator creates a public application, a
new environment variable must be added to the application to provide a
setup string. The parameter name is NCC_SETUP_POST and the parameter
value can consist of any of the setup strings specified below. Each
setup string consists of a KEYNAME, followed immediately by an equal
('=') sign and a VALUE. Multiple setup strings can be passed in the
NCC_SETUP_POST environment variable by separating each setup string with
a semicolon (';'). The creation of this parameter can be performed
either using the WorkSpace On-Demand Public Applications Notebook (on the
Parameters page) or using a Command Line Interface (CLI). The following
is an example of one parameter:
NCC_SETUP_POST=ICONPOS=10,10;
The NCC_SETUP_POST environment variable will be searched for when each
WorkSpace On-Demand public application is created. If it is found, its
value will be used when creating the public application on the WorkSpace
On-Demand Desktop.
The following KEYNAME values are permitted for setup strings:
New Function 18
September 29, 1999 - Warp 4 FixPak XR_M012
Keyname Value Description
------- ----- -----------
CCVIEW DEFAULT Specifies the default value for
concurrent views
YES Creates new views
NO Displays the open view
ICONFILE filename Sets the object's icon.
ICONPOS x,y Sets the initial icon position in
a folder. The "x" and "y" values
represent the position in the object's
folder in percentage coordinates.
ICONRESOURCE id,module Sets the object's icon. The "id"
is the icon resource ID in the dynamic
link library (DLL) "module."
Refer to the Workplace Shell Programming Reference for a description and
definition of the above setup strings.
Note: The NCC_SETUP_POST environment variable exists in the current
environment when the public application with which it is associated is
running.
5.3.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN
Three command line options have been added to both TLOGOFF.EXE and
TSHUTDWN.EXE:
1. /Q -- causes these programs not to display the UPM/LAN
copyright window.
2. /N -- causes no confirmation message boxes to be displayed.
Note: If these parameters are not capitalized, they are ignored.
5.3.4 PMLOGON NO PROGRESS INDICATOR OPTION
An execution parameter has been added to PMLOGON that causes the progress
indicator window not to be displayed during all of logon processing. That
parameter is /NOPI and can be specified only from the RUNWORKPLACE line
in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit,
it is ignored.
New Function 19
September 29, 1999 - Warp 4 FixPak XR_M012
5.3.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION
An execution parameter has been added to PMLOGON which prevents PMLOGON
from setting any of its windows to be system modal after user exit 1 is
executed on the first boot or anytime after a logoff. The parameter is
/NOSM1 and can only be specified from the RUNWORKPLACE line in
CONFIG.SYS. If /NOSM1 is returned as a parameter from a user REXX exit,
it is ignored.
5.4 EURO SUPPORT
The European Monetary Union is creating the Euro as a new common currency
for Europe. As part of this effort the European Commission has
introduced a new character which represents the Euro. This character
looks like an uppercase C with two horizontal lines through it. The Euro
will come into existence on January 1, 1999 for use in banking. Euro
notes and coins will be issued starting January 2002.
5.4.1 BASE OS/2 SUPPORT
The OS/2 basic support for Euro consists of adding the Euro character to
fonts, codepages, and keyboards. The Euro is added to all display and
ATM fonts and to the Times New Roman MT 30 TrueType font which is
available with Java 1.1. The Euro is added to all western European
keyboards and the US International keyboard. The Euro can be used in
base OS/2, Presentation Manager, and in DOS. The Euro is not supported
in WinOS2.
The Euro character is added to these OS/2 base and PM codepages:
850 0xD5 PC Latin 1 base + PM
857 0xD5 PC Turkish base + PM
1004 0x80 Windows Extended base + PM
1250 0x80 Windows Latin 2 PM
1251 0x88 Windows Cyrillic PM
1252 0x80 Windows Latin 1 PM
1254 0x80 Windows Turkish PM
1257 0x80 Windows Baltic PM
The Euro character is added to these fonts.
New Function 20
September 29, 1999 - Warp 4 FixPak XR_M012
Courier (bitmap)
Courier (ATM)
Helv (bitmap)
Helvetica (ATM)
System Monospace (bitmap)
System Proportional (bitmap)
System VIO (bitmap)
Times New Roman (ATM)
Times New Roman MT 30 (TrueType - Java 1.1)
Tms Rmn (bitmap)
WarpSans (bitmap)
The Euro character is added to these OS/2 keyboards:
Belgium be altgr-e
Canada ca altgr-e
Canadian French cf altgr-e
Denmark dk altgr-5
Finland su (fi) altgr-5
France fr altgr-e
Germany gr (de) altgr-e
Germany(453) de453 altgr-e
Iceland ic (is) altgr-5
Iceland 101 is458 altgr-5
Italy it altgr-5
Italy extended it142 altgr-5
Latin America la altgr-e
Netherlands nl altgr-e
Norway no altgr-5
Portugal po altgr-5
Spain sp (es) altgr-5
Sweden sv altgr-5
Swiss French sf altgr-e
Swiss German sg (sd) altgr-e
Turkey tr179 altgr-e
Turkey 440 tr440 altgr-e
UK uk altgr-4
UK 168 uk168 altgr-e
US International ux altgr-e
5.4.2 WHERE EURO IS NOT SUPPORTED
The Euro is not supported in WinOS2. This character is not supported in
the Windows-1252 codepage used in WinOS2. This character is not
available on the WinOS2 keyboards. This character is not available in
the WinOS2 supplied TrueType fonts:
New Function 21
September 29, 1999 - Warp 4 FixPak XR_M012
Arial (Windows TrueType)
Courier New (Windows TrueType)
The Euro is not in the 437 (US English) or 863 (Canadian French)
codepages. You must use codepage 850 to get the Euro. The Euro is not
on the US keyboard. You can use the US International (ux) keyboard
instead.
5.4.3 PRINTING THE EURO
Existing printers do not support the Euro in device fonts. You need to
select a font which is not mapped to a device font in order to print the
Euro. The Euro will print correctly on printers where the system fonts
are used. When there are problems, a dotless-i is normally printed
instead of the Euro.
For PostScript printers, it is necessary to disable device fonts to print
the Euro in one of the base PostScript fonts (Helvetica, Times Roman,
Courier). To do this:
1. Open the properties of the Printer object
2. Select the Print Driver tab
3. Select Job Properties
4. Select the Output tab
5. Deselect "Use printer device fonts"
5.5 NEW WARP REGISTRY EDITOR
See the README.REG file on the first FixPak disk for details.
5.6 WORKSPACE ON DEMAND
WorkSpace on Demand Release 1 is supported starting with FixPak 5
(XR_M005). WorkSpace on Demand Release 2 is supported starting with
FixPak 11 (XR_M011).
5.7 IBM OPEN32
This FixPak includes updates to the IBM Open32 Application Programming
Interfaces (APIs).
New Function 22
September 29, 1999 - Warp 4 FixPak XR_M012
5.8 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
Future updates for GRADD and other video drivers (when they are released)
will be found via the internet at:
■ http://service.software.ibm.com/pslaunch.html
5.9 JOLIET-2 SUPPORT IN CDFS.IFS
Joliet is a Microsoft extension to the ISO 9660 CD-ROM file system which
adds Unicode and longname support. Presently both Windows 95 and Windows
NT 4.0 support the Joliet-2 and Joilet-3 formats. Beginning with Warp 3
Fixpak 32 and Warp 4 Fixpak 4, you can enable the Joliet-2 support by
adding the '/w' option to the CDFS.IFS statement in CONFIG.SYS.
Joilet-3 format is not supported.
5.10 NEW (IMPROVED) CHKDSK
This version of CHKDSK offers significant improvements for High
Performance File System (HPFS) drives. CHKDSK now fixes all errors found
on HPFS drives in a single pass, operating faster, and with less memory
than previous versions. It contains better error detection and
correction algorithms, and creates a log file so service personnel can
determine what errors it found and how it corrected them. Finally, only
the amount of physical memory in your system limits the size of the
largest drive CHKDSK can check at boot time (autocheck).
Improvements in this version of CHKDSK are for HPFS drives only. No
changes occurred to checking File Allocation Table (FAT) drives. This
enhanced CHKDSK operates on IBM OS/2 Warp 3.0 and higher, including IBM
Warp 4, IBM Warp Server 4 and IBM Warp Server 4 SMP. This new CHKDSK
version will not run on version of OS/2 before OS/2 Warp 3.0.
5.10.1 USING THE NEW CHKDSK
The interface to CHKDSK remains CHKDSK.COM and PMCHKDSK. No changes
occurred to the CHKDSK command line parameters or messages.
The first time this version of CHKDSK runs on a fast formatted drive, it
will report harmless errors. These errors go away once CHKDSK is run
with the /F option.
Note: OS/2 Warp Install uses fast format.
New Function 23
September 29, 1999 - Warp 4 FixPak XR_M012
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 24
September 29, 1999 - Warp 4 FixPak XR_M012
Calls to CHKDSK in STARTUP.CMD are not necessary, when using this method
or the base device driver (chkdsk.sys) method.
Example: The computer boots from drive C (moderate HPFS or FAT sized
drive). Drive D (large HPFS) requires more RAM to check than installed
in the machine.
Original IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:CD
New IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:C /QUIET
The CALL statement to use is:
CALL=C:\OS2\CHKDSK.COM D: /C
The /C option tells CHKDSK to check the drive only if it is "dirty" and
it needs checking.
If you need to boot from diskettes to check an HPFS drive, you must have
the following files on the diskette you wish to run CHKDSK from:
CHKDSK.COM
CHKDSK32.DLL
UHPFS.DLL
The BOOTDISK.EXE program has been updated to create new utility diskettes
with the proper files.
5.10.2 CHKDSK LOG FORMATTER
CHKDSK creates a binary service log file (chkdsk.log) on the root of the
drive being checked during autocheck or whenever the /F option is
invoked. The previous log file is saved as chkdsk.old. A formatter for
this log file can be found at:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe
This is a self extracting ZIP file. Place it in a directory in your path
and enter CHKLOGPK. This will create the following files:
New Function 25
September 29, 1999 - Warp 4 FixPak XR_M012
message.txt
msghdr.txt
pmchklog.exe
range.txt
readme
They should all have a date of 05/14/97 or later (May 14, 1997).
This is a tool used by OS/2 service to format and view the new CHKDSK log
entries. There is no support for this tool. You are welcome to use it
but if you have problems with it or do not understand the output DO NOT
contact IBM for assistance as none will be provided.
5.11 AUTOMATED TRAP SCREEN LOGGING
Whenever an application program traps, the trap information is (now)
automatically logged in the POPUPLOG.OS2 file. This is a cumulative file
that is by default located in the root directory of the bootable
partition. Should this file become too large then it may be erased or
pruned (reduced in size). The system will automatically re-create it if
it does not exist.
The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used
to control trap screen behavior (see below).
5.11.1 SUPPRESSPOPUPS
SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior. That
is, to disable logging and to have trap screens displayed unless
specifically overridden by an application's use of the DosError API.
SUPPRESSPOPUPS=x: will disable trap screen display for all processes and
will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or
partition.
If SUPPRESSPOPUPS is omitted then the behavior is as described above
under "Automated Trap Screen Logging".
5.11.2 TRAPLOG
The TRAPLOG command allows dynamic control of trap information logging.
The command syntax is:
TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]
New Function 26
September 29, 1999 - Warp 4 FixPak XR_M012
where:
■ x: specifies that trap information is to be logged in
x:\POPUPLOG.OS2, x: being any partition drive letter.
■ NOLOG disables logging of trap information.
■ POPUPS enables the trap information pop-up message (SYS3175).
■ NOPOPUPS disables the trap information pop-up message.
5.11.3 TRAPDUMP
The TRAPDUMP command allows the conditions under which a trap will
initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak
29, the System Dump setting could only be manipulated from CONFIG.SYS by
use of the TRAPDUMP statement.
Use of this command should be made under the direction of service
personnel.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred, thus under rare
circumstances data can be lost.
The command syntax is:
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]
where:
■ ON enables all application and system traps to initiate a System Dump.
■ OFF disables automatic dump initiation.
■ R0 enables only Ring 0 traps to initiate a System Dump.
■ x: specifies the Dump Partition.
■ NOCHECK overrides the system level check for WARP 4.0, since use of
this command on a system level prior to FixPak 29 is equivalent to the
SYSDUMP command.
5.11.4 SYSDUMP
The SYSDUMP command forces a System Dump to be initiated, regardless of
the TRAPDUMP settings. This command is provided for the use of service
personnel to allow Dump Initiation to be automated through use of a
command file.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
New Function 27
September 29, 1999 - Warp 4 FixPak XR_M012
The system behaves as if a fatal crash has occurred thus under rare
circumstances data can be lost.
The command syntax is:
SYSDUMP [/NOPROMPT]
where:
■ NOPROMPT allows the Dump to proceed without the prompt and response to
message:
"Do you want to force a system dump? (Y/N)"
5.12 OTHER README FILES
There are other README files containing information you may want to
review. All except README.DBG are found on the first FixPak disk and are
not copied to your system when the Fixpak is installed. README.DBG will
be copied to the \OS2\INSTALL directory during installation beginning
with Fixpak 10 and Fixpak 41.
File Use
README2 Problems fixed in each FixPak (APAR list)
README.CID Installing FixPaks via CID
README.REG Use of the Warp Registry Editor REGEDIT2.EXE
README.DBG Tips on debugging OS/2 Warp and details on the latest
Serviceability (RAS) Enhancements (3.0 and 4.0).
New Function 28
September 29, 1999 - Warp 4 FixPak XR_M012
6.0 CORRECTIVE SERVICE FACILITY
6.0.1 REQUIRED CSF LEVEL
You should use release level f.141 or later of the OS/2 Corrective
Service Facility to install this FixPak.
Bootable diskettes are no longer provided starting with the F.138B CSF
build. Instead, you now get a self-extracting ZIP file which contains the
following:
archctl.cmd
build.lvl
csfpans.dll
filefix.dll
fpinst.cmd
fservice.exe
fservice.msg
ibmcsflk.dll
ibmcsflk.exe
ibmcsflk.msg
ibmcsflk.sys
msg.dll
nls.dll
pack.exe
read.me
readme.inf
response.lan
response.wp3
response.wp4
service.exe
service.hlp
shpiinst.dll
unpack.exe
unpack2.exe
viocalls.dll
Follow the directions in the READ.ME file to use the new CSF code. It
covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
from one of several alternative boot methods.
6.0.2 WHERE YOU CAN FIND CSF CODE
The Corrective Service Facility code is available from many places,
including, but not limited to, the following:
Source How to access
Corrective Service Facility 29
September 29, 1999 - Warp 4 FixPak XR_M012
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 XR_M012.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_M012
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through 35.
Examples:
XR_M012.ADK = 10
XR_M012.FDK = 15
XR_M012.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 30
September 29, 1999 - Warp 4 FixPak XR_M012
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 31
September 29, 1999 - Warp 4 FixPak XR_M012
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 32
September 29, 1999 - Warp 4 FixPak XR_M012
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 33
September 29, 1999 - Warp 4 FixPak XR_M012
7.0 INSTALLATION PROCESS
7.1 BEFORE INSTALLATION
Before installing any FixPak, run CHKDSK /F against all drives on your
system to correct any file system errors that might be present. You
cannot do this while OS/2 is active. You must shut down and run CHKDSK by
one of the following methods:
■ Boot from your Installation, DISK 1 and DISK 2 diskettes. If your
file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL
on it in your A: drive before issuing the CHKDSK command.
■ Boot from the Utilities disk you created via the "Create Utility
Diskettes" icon in the System Setup folder.
■ Boot from a different OS/2 partition.
Once CHKDSK has completed, reboot your system then shutdown all running
applications before starting the FixPak installation.
7.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
Note: CS_???.EXE below means CS_141 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Here are some additional notes:
Follow the displayed instructions. When prompted to insert Corrective
Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_M012
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 34
September 29, 1999 - Warp 4 FixPak XR_M012
If this is not the first OS/2 Warp FixPak, then enter the path to the
BACKUP directory where a copy of replaced files will be stored (for
example, D:\BACKUP).
Note: You must specify a different BACKUP directory for each product to
be serviced.
Make sure there is sufficient space available on the drive you specify
for archive or backup. Even though these files are kept in compressed
(PACK2) format, they can take up a lot of space on the drive.
During the installation process you may see messages about Archiving,
Updating and Deferring service.
■ Archiving saves a compressed copy of the original file in the ARCHIVE
or BACKUP path you specified.
■ Updating means the original files are replaced with the new ones from
this FixPak.
■ Deferring service means the file to be updated is currently in use by
the system and cannot be updated. The new files from the FixPak are
placed in unpacked format in the \IBMCSFLK\FIX directory on the drive
with the most free space. They are processed by the locked file
device driver during reboot after you shut down the system.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
You will see the following during reboot of the system if you applied
service to the OS/2 partition you were booted from.
The locked file driver is loaded.
Processing locked files
Processing complete
The system will do one automatic reboot after the Locked File Device
Driver has completed.
7.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA
Note: CS_???.EXE below means CS_141 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Installation Process 35
September 29, 1999 - Warp 4 FixPak XR_M012
Here are some additional notes:
This method does not prompt the user for any information. No interaction
with the user takes place other than requests to put the next diskette in
drive A. All serviceable partitions on your system will be updated
automatically unless you have modified the default response file. Be
especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
this method because they can cause CSF to apply service to directories
you do not want serviced.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. Please be
patient and allow this process to complete.
Note: You can edit the response file to control some of the actions taken
by FSERVICE.EXE while applying a FixPak. See the READ.ME file or use the
VIEW command to look at the file README.INF. They are part of
CS_???.EXE.
7.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility, like how to
backout a FixPak, is available from the README.INF file on the first
Corrective Service Facility disk. To view this file, place CSF disk 1 in
drive A and enter VIEW A:\README.INF.
There is also some additional information in the READ.ME file.
7.5 FIXPAKS ON CD-ROM
Both the IBM Technical Connection and the IBM Developer Connection
contain the latest OS/2 and LAN FixPaks that were available at publishing
time.
The IBM Technical Connection homepage on the World Wide Web is located
at:
■ http://www.ibm.com/Support/techconn/index.htm
The IBM Developer Connection homepage on the World Wide Web is located
at:
■ http://www.developer.ibm.com/devcon/titlepg.htm
Check these WWW sites for content and ordering information.
Installation Process 36
September 29, 1999 - Warp 4 FixPak XR_M012
8.0 CSD LEVEL OF SYSLEVEL.OS2
The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
partition will be updated with the name of the FixPak when it is applied.
This is a major change from previous CSF releases. The Prior CSD level
field will be left asis. This means when you use the SYSLEVEL command to
look at the release levels of products on your system, you will see the
following for SYSLEVEL.OS2.
Before a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR04000
Prior CSD level: XR04000
After a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0M008
Prior CSD level: XR04000
All fix information is recorded in SERVICE.LOG. Look at the file
\OS2\INSTALL\SERVICE.LOG
on your boot drive for information relating to the installation of
FixPaks on your system.
Additionally, you can use the VER /R command to see the current revision
of OS/2 installed. The response will look like the following for this
FixPak:
The Operating System/2 Version is 4.00
Revision 9.036
The first page of this document has a line that looks like:
Build Level: n.nnn
CSD level of SYSLEVEL.OS2 37
September 29, 1999 - Warp 4 FixPak XR_M012
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 38
September 29, 1999 - Warp 4 FixPak XR_M012
9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 9.036
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M012_ (Country = Generic)
Pre-requisite CSD Level: XR_4000_
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: XR_M012_ (Country = Generic)
Pre-requisite CSD Level: XR_4010_
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: XR_M012_ (Country = Generic)
Pre-requisite CSD Level: XR_4010_
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 39
September 29, 1999 - Warp 4 FixPak XR_M012
..\..\OS2\INSTALL Stub File: @INSTDIR
..\..\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
------------ ------------ ----- ---------- ----- ------- --------
ARACONV.EXE ARACONV.EX_ 15 07/20/1999 19:52 62183 CB4810AB
ASIACOL.DLL ASIACOL.DL_ 11 07/26/1999 13:26 158732 DDBF4510
AVIO.DLL AVIO.DL_ 1 02/03/1999 11:26 53923 811D0F32
BACKUP.EXE BACKUP.EX_ 16 07/27/1999 11:56 28196 354D593E
BDIME.DLL BDIME.DL_ 16 03/25/1999 13:18 11911 54EED67F
BE.KBL BE.KB_ 17 07/26/1999 13:31 972 4D2B8790
BLDLEVEL.EXE BLDLEVEL.EX_ 15 09/15/1998 11:32 43974 F7F6C3CC
BOOTDISK.EXE BOOTDISK.EX_ 14 07/21/1999 10:59 61057 7E0F45DF
BOOTDISK.HLP BOOTDISK.HL_ 16 07/21/1999 11:00 11575 AD0E2D74
BVSCALLS.DLL BVSCALLS.DL_ 17 07/21/1999 12:13 512 925828FF
BY.KBL BY.KB_ 17 07/26/1999 13:31 1292 098F3808
CA.KBL CA.KB_ 17 07/26/1999 13:31 1214 C900CD8F
CACHE.EXE CACHE.EX_ 16 08/10/1999 15:17 11820 B5B0DB75
CARDINFO.DAT CARDINFO.DA_ 16 02/02/1999 19:41 54979 4547DDFE
CDFS.IFS CDFS.IF_ 16 08/10/1999 15:28 45173 0D4D486C
CDFS.TDF CDFS.TD_ 17 08/10/1999 15:28 2113 7E8C5B0C
CDROM.TBL CDROM.TB_ 16 11/12/1996 13:38 4365 F3986660
CF.KBL CF.KB_ 17 07/26/1999 13:31 956 548C7599
CHKDSK.COM CHKDSK.CO_ 14 07/27/1999 11:51 70208 7D849250
CHKDSK.SYS CHKDSK.SY_ 17 04/01/1999 17:10 747 11D667C8
CHKDSK32.DLL CHKDSK32.DL_ 5 08/10/1999 15:18 121895 C5EE0C60
CHKDSK32.EXE CHKDSK32.EX_ 16 08/10/1999 15:18 6417 422DCC60
CLOCK01.SYS CLOCK01.SY_ 16 07/12/1999 16:40 4460 3E67C95B
CLOCK02.SYS CLOCK02.SY_ 16 07/12/1999 16:40 4302 E05DF2F7
CMD.EXE CMD.EX_ 13 07/27/1999 11:53 74300 B733447B
COMM.DRV COMM.DR_ 16 07/19/1999 18:10 9552 353A35F2
COMMAND.COM COMMAND.CO_ 15 07/27/1999 11:52 53375 9B81BD1F
CONTROL.PM CONTROL.PM_ 16 05/05/1998 01:48 8474 87121A82
COUNTRY.SYS COUNTRY.SY_ 16 03/15/1999 18:23 50947 19A8000B
COUR.OFM COUR.OF_ 16 03/15/1999 13:45 6163 E932E21E
COUR.PFB COUR.PF_ 10 03/15/1999 13:46 137111 48049C47
COUR.PFM COU1.PF_ 17 03/15/1999 13:45 674 EB24F168
COURB.OFM COURB.OF_ 16 03/15/1999 13:45 6173 31304A2B
COURB.PFB COURB.PF_ 10 03/15/1999 13:46 140829 503DA614
COURB.PFM COUR1.PF_ 17 03/15/1999 13:45 679 1EF9DD6B
COURBI.OFM COURBI.OF_ 16 03/15/1999 13:45 6187 0F7825D1
FixPak Corrective Service levels and disk layouts 40
September 29, 1999 - Warp 4 FixPak XR_M012
COURBI.PFB COURBI.PF_ 10 03/15/1999 13:46 136240 16421E63
COURBI.PFM COURB1.PF_ 17 03/15/1999 13:45 685 D0390DF6
COURI.OFM COURI.OF_ 16 03/15/1999 13:45 6178 4FCF133A
COURI.PFB COURI.PF_ 10 03/15/1999 13:46 137394 71C135E2
COURI.PFM COUR2.PF_ 17 03/15/1999 13:45 681 A6EEB882
COURIER.FON COURIER.FO_ 15 04/07/1999 14:14 77826 231B9F4F
COURIERI.FON COURIERI.FO_ 14 04/07/1999 14:09 86641 F95899C8
CPG01256.TBL CPG01256.TB_ 16 04/12/1999 15:51 27264 221D21BE
CREX.MSG CREX.MS_ 16 09/19/1996 15:44 2865 84FD8E0E
CREXUTIL.DLL CREXUTIL.DL_ 14 11/20/1998 15:58 49229 1FDA6291
CREXX.DLL CREXX2.DL_ 10 04/01/1999 14:20 266031 D55B2A5F
CZ.KBL CZ.KB_ 17 07/26/1999 13:31 1014 001CBC0E
DDINSTAL.EXE DDINSTAL.EX_ 15 07/21/1999 10:48 34855 6F31DBA8
DE.KBL DE.KB_ 17 07/26/1999 13:31 958 263C6312
DE453.KBL DE453.KB_ 17 07/26/1999 13:31 1354 241C7442
DF_DEB.EXE DF_DEB.EX_ 13 08/10/1999 15:31 135999 932AE7C6
DF_RET.EXE DF_RET.EX_ 13 07/27/1999 11:50 136255 0F67E0FB
DIBDRVR.DLL DIBDRVR.DL_ 16 10/22/1997 23:20 2267 1429B272
DICTATE.EXE DICTATE.EX_ 14 05/06/1998 11:58 51391 460F4CF4
DICTDLL.DLL DICTDLL.DL_ 14 12/21/1997 01:28 51187 D092C5CA
DISPLAY.DLL DISPLAY.DL_ 14 04/07/1999 15:46 46574 82EEAA74
DIVE.DLL DIVE.DL_ 13 08/03/1999 12:54 69660 71D0598D
DK.KBL DK.KB_ 17 07/26/1999 13:31 928 B2992DE9
DMQSPROF.DLL DMQSPROF.DL_ 15 04/07/1999 16:01 39033 EC272D39
DOSCALL1.DLL DOSCALL1.DL_ 12 07/27/1999 11:50 125384 EF802EDE
DOSCALL1.SYM DOSCALL1.SY_ 15 07/27/1999 11:49 42052 D7EAAF27
DOSCALL1.TDF DOSCALL1.TD_ 16 07/27/1999 11:49 5426 628CC911
DOSKRNL DOSKRNL.___ 16 08/10/1999 15:28 30569 3CE4D1E6
DRVMAP.INF DRVMAP.IN_ 16 04/03/1997 13:54 12986 0AD62B34
DSPINSTL.EXE DSPINSTL.EX_ 12 07/21/1999 10:56 117816 62C0EA23
DSPRES.DLL DSPRES1.DL_ 7 04/07/1999 14:09 376488 FF6B63F9
DSPRES.DLL DSPRES.DL_ 4 04/07/1999 14:09 376488 FFB9A3F9
DTRACE.DOC DTRACE.DO_ 16 04/21/1999 10:58 75371 D5765F89
DTRACE.EXE DTRACE1.EX_ 14 07/26/1999 15:40 48906 8CCC0389
DTRACE.EXE DTRACE.EX_ 14 07/26/1999 15:40 48906 8CCC0389
E.EXE E.EX_ 14 09/01/1999 11:15 61795 15F55800
EAUTIL.EXE EAUTIL.EX_ 16 07/27/1999 11:53 37984 43F0577E
EJECT.EXE EJECT.EX_ 16 01/09/1998 16:20 25648 0C9E0C86
EL.KBL EL.KB_ 17 07/26/1999 13:31 1396 5C248F65
EL459.KBL EL459.KB_ 17 07/26/1999 13:31 1372 06998499
ENGINE.EXE ENGINE.EX_ 6 07/23/1997 11:39 440424 CA606BAA
EPM.EXE EPM.EX_ 16 07/16/1998 13:18 19684 E6ED87A9
ERLOGGER.EXE ERLOGGER.EX_ 15 07/26/1999 15:37 34320 EFA4EBCA
ERRLOG.DLL ERRLOG.DL_ 13 07/26/1999 15:37 72594 37D929E8
ES.KBL ES.KB_ 17 07/26/1999 13:31 920 6F969662
ETKC603.DLL ETKC603.DL_ 12 12/16/1997 15:06 135759 6B0AA3C2
ETKE603.DLL ETKE603.DL_ 5 07/20/1999 19:50 753974 DCBB41A5
FDISK.COM FDISK.CO_ 13 07/27/1999 11:57 114218 62962E0F
FDISKPM.DLL FDISKPM.DL_ 16 01/26/1999 14:22 7731 6B64272C
FDISKPM.EXE FDISKPM.EX_ 14 07/27/1999 11:58 63042 C6B18D9A
FFST.DLL FFST.DL_ 16 04/03/1997 19:03 11425 C6365786
FixPak Corrective Service levels and disk layouts 41
September 29, 1999 - Warp 4 FixPak XR_M012
FFSTCONF.EXE FFSTCONF.EX_ 13 07/26/1999 15:41 68669 E5A6E581
FFSTPCT.EXE FFSTPCT.EX_ 10 07/26/1999 15:42 69583 7B7162BF
FI.KBL FI.KB_ 17 07/26/1999 13:31 940 8B5F64D8
FILT.DLL FILT.DL_ 16 09/29/1998 16:10 22888 C4544636
FKA.DLL FKA.DL_ 16 10/10/1997 01:03 13997 5C4513FC
FORMAT.COM FORMAT.CO_ 14 07/27/1999 11:54 69920 940591D0
FR.KBL FR.KB_ 17 07/26/1999 13:31 950 EC3E7D3A
FSFILTER.SYS FSFILTER.SY_ 16 08/10/1999 15:30 12988 087EF853
GDI.EXE GDI.EX_ 10 09/02/1999 12:03 225744 CD31FFD9
GRADD.SYS GRADD.SY_ 17 04/07/1999 17:44 1195 98CBC4DC
GRE2VMAN.DLL GRE2VMAN.DL_ 16 04/07/1999 17:43 17901 95F8D672
HDMON.EXE HDMON.EX_ 13 04/13/1999 09:50 75071 9D672805
HELPMGR.DLL HELPMGR.DL_ 8 07/24/1999 15:26 249825 EF1D9757
HELPMSG.EXE HELPMSG.EX_ 16 07/27/1999 11:54 36256 43B8CA04
HELV.FON HELV.FO_ 11 04/07/1999 14:14 171252 A073FA61
HELV.OFM HELV.OF_ 16 03/15/1999 13:45 6793 FF46E30D
HELV.PFB HELV.PF_ 11 03/15/1999 13:46 120578 0DA723CF
HELV.PFM HEL1.PF_ 17 03/15/1999 13:45 1096 C722995E
HELVB.OFM HELVB.OF_ 16 03/15/1999 13:45 6785 94469F2F
HELVB.PFB HELVB.PF_ 11 03/15/1999 13:46 123085 0037FB2B
HELVB.PFM HELV1.PF_ 17 03/15/1999 13:45 1089 9A484EA2
HELVBI.OFM HELVBI.OF_ 16 03/15/1999 13:45 6787 4196DDD9
HELVBI.PFB HELVBI.PF_ 11 03/15/1999 13:46 124245 46A18ABC
HELVBI.PFM HELVB1.PF_ 17 03/15/1999 13:45 1087 06B5E29D
HELVI.FON HELVI.FO_ 10 04/07/1999 14:09 199523 17786C48
HELVI.OFM HELVI.OF_ 16 03/15/1999 13:45 6772 3B3191CD
HELVI.PFB HELVI.PF_ 11 03/15/1999 13:47 123355 48E064F0
HELVI.PFM HELV2.PF_ 17 03/15/1999 13:45 1079 CD475F06
HPFS.IFS HPFS.IF_ 13 08/10/1999 15:16 140866 F7897E62
HPFS.TDF HPFS.TD_ 17 08/10/1999 15:16 1620 0ABC15D1
HR.KBL HR.KB_ 17 07/26/1999 13:31 982 C69C0318
HU.KBL HU.KB_ 17 07/26/1999 13:31 1006 8F146132
IBM1004 IBM1004.___ 17 07/26/1999 13:23 3584 C687A8BA
IBM1125 IBM1125.___ 16 07/26/1999 13:23 4320 DFBF4607
IBM1131 IBM1131.___ 16 07/26/1999 13:23 4320 87212A19
IBM1140 IBM1140.___ 16 07/26/1999 13:23 2816 511E46AE
IBM1141 IBM1141.___ 16 07/26/1999 13:23 2784 51C4B993
IBM1142 IBM1142.___ 16 07/26/1999 13:23 2816 17E42197
IBM1143 IBM1143.___ 16 07/26/1999 13:23 2816 3FE17606
IBM1144 IBM1144.___ 16 07/26/1999 13:23 2784 CE079525
IBM1145 IBM1145.___ 16 07/26/1999 13:23 2784 3E0EE64E
IBM1146 IBM1146.___ 16 07/26/1999 13:23 2816 E88C76A8
IBM1147 IBM1147.___ 16 07/26/1999 13:23 2784 2336B680
IBM1148 IBM1148.___ 16 07/26/1999 13:23 2816 6101E543
IBM1250 IBM1250.___ 16 07/26/1999 13:24 3552 1972EF6E
IBM1251 IBM1251.___ 17 07/26/1999 13:24 3328 1D8186C1
IBM1252 IBM1252.___ 17 07/26/1999 13:24 3552 ADB9AFE6
IBM1253 IBM1253.___ 17 07/26/1999 13:24 3552 B42CF613
IBM1254 IBM1254.___ 17 07/26/1999 13:24 3552 99377BE5
IBM1255 IBM1255.___ 17 07/26/1999 13:24 3808 77F8C1B7
IBM1256 IBM1256.___ 16 07/26/1999 13:24 4320 68394093
FixPak Corrective Service levels and disk layouts 42
September 29, 1999 - Warp 4 FixPak XR_M012
IBM1257 IBM1257.___ 17 07/26/1999 13:24 3296 7FABC453
IBM813 IBM813.___ 17 07/26/1999 13:24 3072 DA4A683C
IBM850 IBM850.___ 16 07/26/1999 13:24 4320 42BF69F4
IBM852 IBM852.___ 16 07/26/1999 13:24 4608 44C19E65
IBM857 IBM857.___ 16 07/26/1999 13:24 4352 226E6FF6
IBM859 IBM859.___ 16 07/26/1999 13:24 4320 B68FB360
IBM862 IBM862.___ 16 07/26/1999 13:24 4576 ECCF6ADB
IBM864 IBM864.___ 16 07/26/1999 13:24 4576 E55C982C
IBM869 IBM869.___ 16 07/26/1999 13:24 4320 E2D98857
IBM923 IBM923.___ 17 07/26/1999 13:24 2784 ED42AC6D
IBM924 IBM924.___ 17 07/26/1999 13:24 2784 FD6977EE
IBMOPTNS.DLL IBMOPTNS.DL_ 16 02/02/1999 19:41 18744 DAA60B97
ICONEDIT.EXE ICONEDIT.EX_ 12 07/23/1998 16:08 109504 2A41E8A9
IFGDI2VM.DRV IFGDI2VM.DR_ 15 04/07/1999 16:06 92520 E81825AD
INST_DOS.EXE INST_DOS.EX_ 15 07/24/1999 15:24 36466 F82FE8CF
INSTALL.EXE INSTALL.EX_ 6 07/21/1999 10:37 384280 C1110205
IOPROC.DLL IOPROC.DL_ 15 02/03/1999 11:27 37878 1CD1ED61
IS.KBL IS.KB_ 17 07/26/1999 13:31 940 275478F8
IS458.KBL IS458.KB_ 17 07/26/1999 13:31 928 83CFF66C
ISGDI2VM.DRV ISGDI2VM.DR_ 15 04/07/1999 16:06 91328 1C3F9230
IT.KBL IT.KB_ 17 07/26/1999 13:31 876 AC171867
IT142.KBL IT142.KB_ 17 07/26/1999 13:31 854 E528CF20
KERNEL.SDF KERNEL.SD_ 15 07/21/1999 12:17 470436 78076147
KERNELD.SDF KERNELD.SD_ 15 07/27/1999 11:51 471763 0D8DF501
KEYBOARD.DCP KEYBOARD.DC_ 16 03/25/1999 14:34 315109 14E81503
KRNLBDEV.TDF KRNLBDEV.TD_ 17 08/10/1999 15:27 3703 39EB9063
KRNLBFS.TDF KRNLBFS.TD_ 16 08/10/1999 15:27 4464 95AE06CE
KRNLBLDR.TDF KRNLBLDR.TD_ 16 08/10/1999 15:27 5581 817EA665
KRNLBPG.TDF KRNLBPG.TD_ 17 08/10/1999 15:27 3203 34EE3A38
KRNLBSEL.TDF KRNLBSEL.TD_ 17 08/10/1999 15:28 2727 5FA0F7E7
KRNLBSEM.TDF KRNLBSEM.TD_ 17 08/10/1999 15:28 1792 A4DD24F0
KRNLBSM.TDF KRNLBSM.TD_ 17 08/10/1999 15:27 1321 6B9CE039
KRNLBTK.TDF KRNLBTK.TD_ 16 08/10/1999 15:27 14363 26DD7556
KRNLBTOM.TDF KRNLBTOM.TD_ 17 08/10/1999 15:28 925 407268DE
KRNLBVDM.TDF KRNLBVDM.TD_ 16 08/10/1999 15:27 13917 25D47C02
KRNLBVM.TDF KRNLBVM.TD_ 16 08/10/1999 15:28 5514 13141223
KRNLDDEV.TDF KRNLDDEV.TD_ 17 08/10/1999 15:24 3678 5269C7E6
KRNLDFS.TDF KRNLDFS.TD_ 16 08/10/1999 15:24 4355 EF661534
KRNLDLDR.TDF KRNLDLDR.TD_ 16 08/10/1999 15:24 5609 FDF032AF
KRNLDPG.TDF KRNLDPG.TD_ 17 08/10/1999 15:24 3284 05AD6269
KRNLDSEL.TDF KRNLDSEL.TD_ 17 08/10/1999 15:24 2814 AF9508CE
KRNLDSEM.TDF KRNLDSEM.TD_ 17 08/10/1999 15:24 1932 6C1076BD
KRNLDSM.TDF KRNLDSM.TD_ 17 08/10/1999 15:24 1321 965F1D0A
KRNLDTK.TDF KRNLDTK.TD_ 16 08/10/1999 15:24 14394 9635BA4B
KRNLDTOM.TDF KRNLDTOM.TD_ 17 08/10/1999 15:24 953 7925FFB6
KRNLDVDM.TDF KRNLDVDM.TD_ 16 08/10/1999 15:24 13992 2D70B6B6
KRNLDVM.TDF KRNLDVM.TD_ 16 08/10/1999 15:24 5601 5C2BE067
KRNLRDEV.TDF KRNLRDEV.TD_ 17 08/10/1999 15:25 3703 FEB3A3E9
KRNLRFS.TDF KRNLRFS.TD_ 16 08/10/1999 15:25 4464 69A6B3E9
KRNLRLDR.TDF KRNLRLDR.TD_ 16 08/10/1999 15:26 5581 ED0B8811
KRNLRPG.TDF KRNLRPG.TD_ 17 08/10/1999 15:26 3203 9266B460
FixPak Corrective Service levels and disk layouts 43
September 29, 1999 - Warp 4 FixPak XR_M012
KRNLRSEL.TDF KRNLRSEL.TD_ 17 08/10/1999 15:26 2727 D0D00FFA
KRNLRSEM.TDF KRNLRSEM.TD_ 17 08/10/1999 15:26 1792 63D1E41C
KRNLRSM.TDF KRNLRSM.TD_ 17 08/10/1999 15:26 1321 4D3A18EB
KRNLRTK.TDF KRNLRTK.TD_ 16 08/10/1999 15:26 14279 5AF03526
KRNLRTOM.TDF KRNLRTOM.TD_ 17 08/10/1999 15:26 897 E5C8E523
KRNLRVDM.TDF KRNLRVDM.TD_ 16 08/10/1999 15:25 13749 7E717035
KRNLRVM.TDF KRNLRVM.TD_ 16 08/10/1999 15:26 5514 2F4E511A
LIBCM.DLL LIBCM.DL_ 8 04/08/1999 16:09 210916 98DAC306
LIBCN.DLL LIBCN.DL_ 14 04/08/1999 16:08 57340 7BBE3105
LIBCS.DLL LIBCS.DL_ 3 04/08/1999 16:08 192386 978D3E9F
LIBUNI.DLL LIBUNI.DL_ 13 07/26/1999 13:34 81242 3A2ACDA5
LOCALE.DLL LOCALE.DL_ 11 07/26/1999 13:23 107887 2BD6ACC6
MAIN.CPL MAIN.CP_ 13 09/02/1999 12:07 147680 82123A80
MAKETSF.EXE MAKETSF.EX_ 15 07/23/1999 12:01 37516 94D71209
MAPTSF.CMD MAPTSF.CM_ 16 04/01/1999 14:23 16803 0EC9489E
MIDI.SYS MIDI.SY_ 16 05/03/1999 18:10 26328 FA7C0728
MIDIMCD.DLL MIDIMCD.DL_ 17 09/29/1998 16:02 532 40B1F3FB
MIGRATE.EXE MIGRATE.EX_ 12 07/21/1999 10:56 118313 F795EB89
MINSTALL.EXE MINSTALL.EX_ 11 02/02/1999 19:41 152580 84E992F2
MINXOBJ.DLL MINXOBJ.DL_ 15 09/01/1999 10:54 31778 00E6E4D4
MIRRORS.DLL MIRRORS.DL_ 6 09/19/1996 15:53 444744 4D936F0C
MMODPTS.DLL MMODPTS.DL_ 9 07/27/1999 08:49 184020 2FE7AB91
MMPARTS.DLL MMPARTS.DL_ 2 07/27/1999 08:53 1532066 BE68CC0A
MMPM.DLL MMPM.DL_ 6 02/02/1999 19:46 431781 5F4F04BD
MMPTMRI.DLL MMPTMRI.DL_ 12 07/27/1999 08:49 227344 0BA39AC8
MMSOUND.DRV MMSOUND.DR_ 16 07/19/1999 17:07 3456 97D7C150
MONCALLS.DLL MONCALLS.DL_ 16 07/21/1999 12:11 2472 AA17F96D
MONCALLS.TDF MONCALLS.TD_ 17 07/21/1999 12:11 1139 6AAF973C
MPGIO.DLL MPGIO.DL_ 14 02/03/1999 11:27 59267 4C29334D
NAMEADD.EXE NAMEADD.EX_ 16 07/24/1999 13:03 23040 04FC90A6
NAMECOPY.EXE NAMECOPY.EX_ 16 07/24/1999 13:03 23040 E1168851
NAMECSSP.DLL NAMECSSP.DL_ 14 10/28/1997 13:00 61155 A8FF5683
NAMEDEL.EXE NAMEDEL.EX_ 16 07/24/1999 13:03 23040 2CC5D0A7
NAMEDSP.DLL NAMEDSP.DL_ 12 10/28/1997 13:00 123411 2EF315DB
NAMEEXT.EXE NAMEEXT.EX_ 16 07/24/1999 13:03 23040 64C5D0A9
NAMEFT.DLL NAMEFT.DL_ 14 10/28/1997 13:00 66306 77789339
NAMEFW.DLL NAMEFW.DL_ 13 10/28/1997 13:00 72312 9A504B3F
NAMEINFO.DLL NAMEINFO.DL_ 6 10/28/1997 13:00 47941 A05DAC94
NAMEINI.DLL NAMEINI.DL_ 14 10/28/1997 13:00 59011 3562CDED
NAMEMOD.EXE NAMEMOD.EX_ 16 07/24/1999 13:03 23040 14FC90A7
NAMEMOVE.EXE NAMEMOVE.EX_ 16 07/24/1999 13:03 23040 E916884F
NAMEOSP.DLL NAMEOSP.DL_ 14 10/28/1997 13:00 52725 FBAB278A
NL.KBL NL.KB_ 17 07/26/1999 13:31 954 145D3794
NO.KBL NO.KB_ 17 07/26/1999 13:31 920 8D019B17
NWIAPI.DLL NWIAPI.DL_ 16 09/01/1999 10:58 14768 4A2A7259
OREXUTIL.DLL ORXUTIL2.DL_ 15 11/20/1998 15:58 33725 52F2EC68
OREXX.DLL OREXX2.DL_ 7 07/20/1999 19:44 447475 E9D7E0CF
OS2CHAR.TDF OS2CHAR.TD_ 16 07/27/1999 11:49 13889 3B93ACB0
OS2DASD.DMD OS2DASD.DM_ 15 08/07/1998 12:19 40894 21CB3220
OS2DUMP OS2DUMP.___ 16 08/10/1999 15:19 14301 6E2526C0
OS2K386.EXE OS2K386.EX_ 12 09/02/1999 12:04 80306 7F0ED240
FixPak Corrective Service levels and disk layouts 44
September 29, 1999 - Warp 4 FixPak XR_M012
OS2KRNL OS2KRNL.___ 3 08/10/1999 15:26 639959 60A74AFA
OS2KRNL.TDF OS2KRNL.TD_ 16 08/10/1999 15:25 16581 B5899C27
OS2KRNLD.SYM OS2KRNLD.SY_ 12 08/10/1999 15:24 187140 BBBCE495
OS2KRNLR.SYM OS2KRNLR.SY_ 12 08/10/1999 15:25 164212 ED051E03
OS2LDR.MSG OS2LDR.MS_ 16 07/21/1999 11:22 8368 DF4796FA
OS2MM.DLL OS2MM.DL_ 9 02/02/1999 19:41 219650 AD7890CC
OS2NS.EXE OS2NS.EX_ 14 10/28/1997 14:18 44964 C80E8116
OS2UGL OS2UGL.___ 16 07/26/1999 13:24 15616 783F2B92
OS2UGLG OS2UGLG.___ 16 12/12/1997 22:59 8928 AA898322
OSO001.MSG OSO001.MS_ 13 07/20/1999 18:37 179413 6DB361EA
OSO001H.MSG OSO001H.MS_ 13 07/20/1999 18:37 241617 3EFA7141
PARALLEL.PDR PARALLEL.PD_ 16 07/27/1999 12:17 15848 00689DA7
PDUMPSYS.EXE PDUMPSYS.EX_ 15 04/13/1999 09:50 34877 C4D753E7
PDUMPUSR.EXE PDUMPUSR.EX_ 15 04/13/1999 09:50 34875 6C37F546
PICV.DLL PICV.DL_ 16 07/24/1999 15:24 26200 C8F6A92B
PICVIEW.DLL PICVIEW.DL_ 16 04/13/1999 16:02 10786 1EE319A1
PICVIEW.EXE PICVIEW.EX_ 13 07/24/1999 15:24 69146 7108F146
PL.KBL PL.KB_ 17 07/26/1999 13:31 980 518C037C
PL457.KBL PL457.KB_ 17 07/26/1999 13:31 882 899F5221
PMATM.DLL PMATM.DL_ 9 03/15/1999 18:36 224319 71C7F565
PMBIDI.DLL PMBIDI.DL_ 16 07/20/1999 19:52 12352 E0E87CC2
PMCHKDSK.DLL PMCHKDSK.DL_ 16 11/04/1996 16:44 4127 CE30C1EE
PMCHKDSK.EXE PMCHKDSK.EX_ 15 07/27/1999 11:58 28183 5DED21D1
PMCLIP.DLL PMCLIP.DL_ 16 10/22/1997 23:19 21295 2FE91E38
PMCTLS.DLL PMCTLS.DL_ 4 09/01/1999 10:06 584866 E7E78284
PMCTLS.SYM PMCTLS.SY_ 15 09/01/1999 10:06 44084 2EA0CDD1
PMDDE.DLL PMDDE.DL_ 16 07/24/1999 15:26 28334 F1F6141A
PMDDEML.DLL PMDDEML.DL_ 15 09/01/1999 10:00 27706 A4F05C05
PMDF.EXE PMDF.EX_ 8 07/27/1999 11:32 262900 81F0565E
PMDFMSG.DLL PMDFMSG.DL_ 15 07/26/1999 15:43 44240 3DB61353
PMDRAG.DLL PMDRAG.DL_ 17 07/24/1999 15:06 1731 802018B4
PMGPI.DLL PMGPI.DL_ 9 04/13/1999 15:37 229146 10D24DA4
PMGPI.TDF PMGPI.TD_ 16 04/13/1999 15:37 12338 FD344EBE
PMGRE.DLL PMGRE.DL_ 16 04/13/1999 15:36 2231 B20E2F7F
PMGRE.TDF PMGRE.TD_ 17 07/24/1999 15:10 1062 B27472DF
PMMERGE.DLL PMMERGE.DL_ 1 07/24/1999 15:10 1254673 7C93D18C
PMMERGE.SYM PMMERGE.SY_ 13 07/24/1999 15:10 115444 F6F73594
PMMLE.DLL PMMLE.DL_ 17 09/01/1999 10:06 673 C1270A1B
PMPIC.DLL PMPIC.DL_ 15 07/24/1999 15:24 47206 D0354841
PMPIC.TDF PMPIC.TD_ 17 07/24/1999 15:24 400 AAA13CFB
PMPRINT.QPR PMPRINT.QP_ 15 07/27/1999 12:03 11833 87E1CDC4
PMSDMRI.DLL PMSDMRI.DL_ 16 04/13/1999 15:44 13312 10BBAF4D
PMSEEK.EXE PMSEEK.EX_ 15 07/27/1999 11:58 31285 4DDE1A39
PMSHAPI.DLL PMSHAPI.DL_ 16 10/22/1997 22:53 4549 7AE93081
PMSHAPI.TDF PMSHAPI.TD_ 16 07/24/1999 15:10 6726 FA07456D
PMSPL.DLL PMSPL.DL_ 8 09/01/1999 10:57 277033 4648C7AD
PMSPL.SYM PMSPL.SY_ 16 09/01/1999 10:57 32340 94A997CC
PMSPL.TDF PMSPL.TD_ 16 09/01/1999 10:57 4491 F30A8434
PMVDMP.DLL PMVDMP.DL_ 15 09/01/1999 10:17 42867 A5F471AC
PMVDMP.TDF PMVDMP.TD_ 17 09/01/1999 10:17 2661 7920E351
PMVIOP.DLL PMVIOP.DL_ 14 09/01/1999 10:17 58958 A0175F3C
FixPak Corrective Service levels and disk layouts 45
September 29, 1999 - Warp 4 FixPak XR_M012
PMVIOP.SYM PMVIOP.SY_ 16 09/01/1999 10:17 6628 6434FC3B
PMVIOP.TDF PMVIOP.TD_ 17 09/01/1999 10:17 3551 24D8550A
PMWIN.DLL PMWIN.DL_ 16 04/13/1999 15:38 11264 93A2E194
PMWIN.TDF PMWIN.TD_ 16 07/24/1999 15:10 9567 1D9E3978
PMWIN32.SDF PMWIN32.SD_ 15 10/28/1997 18:56 299617 47F639A5
PMWINX.DLL PMWINX.DL_ 5 09/01/1999 10:15 530279 98ADC6F1
PMWP.DLL PMWP.DL_ 3 09/01/1999 10:52 926345 02BAEBEA
PMWP.SYM PMWP.SY_ 14 09/01/1999 10:51 100420 7326307F
PMWP.TDF PMWP.TD_ 16 09/01/1999 10:52 13825 C53428F5
PMWPMRI.DLL PMWPMRI.DL_ 15 07/20/1999 20:44 54821 2EAC433F
PO.KBL PO.KB_ 17 07/26/1999 13:31 926 BBED4216
PROCDUMP.DOC PROCDUMP.DO_ 16 04/01/1999 14:23 62765 B74B1E35
PROCDUMP.EXE PROCDUMP.EX_ 7 04/13/1999 09:50 47135 A1E0A208
PROGMAN.EXE PROGMAN.EX_ 14 07/19/1999 16:51 115328 59CE0798
PSSDMON.EXE PSSDMON.EX_ 15 04/06/1999 17:06 27117 A48B4E88
PSTAT.EXE PSTAT.EX_ 16 07/27/1999 11:55 10963 CF7AE814
QUECALLS.DLL QUECALLS.DL_ 17 07/21/1999 12:12 1024 BE89DF51
QUECALLS.TDF QUECALLS.TD_ 17 07/27/1999 11:49 1287 A8A1CE39
RAS001.MSG RAS001.MS_ 16 07/23/1997 18:57 25739 52573E1C
RASH.MSG RASH.MS_ 16 07/23/1997 18:47 11581 598AA877
README.CID README.CI_ 16 06/17/1997 10:14 60916 4938BF49
README.DBG README.DB_ 16 07/21/1999 10:20 22934 D48AEEF4
REGCONV.EXE REGCONV.EX_ 15 07/26/1999 11:19 39446 266F3F76
REGEDIT.HLP REGEDIT.HL_ 13 09/02/1999 12:41 22682 C20CA98C
REGEDIT2.EXE REGEDIT2.EX_ 4 07/26/1999 11:20 949760 1648AE23
REGISTRY.DLL REGISTRY.DL_ 15 07/24/1999 12:53 81440 4DB049C9
REGISTRY.MSG REGISTRY.MS_ 17 07/24/1999 12:59 629 E72A370E
REGISTRY.TDF REGISTRY.TD_ 16 07/24/1999 12:53 7591 E2A663D1
REPLACE.EXE REPLACE.EX_ 15 07/21/1999 12:30 37483 25447F35
RESTORE.EXE RESTORE.EX_ 16 07/27/1999 11:59 36256 BC40F40C
REX.MSG REX.MS_ 16 09/19/1996 15:44 2865 6725D657
REXX.DLL CREXX1.DL_ 10 04/01/1999 14:20 266031 5DDF8B8E
REXX.DLL OREXX1.DL_ 7 07/20/1999 19:44 447475 7FFAA0A8
REXX.IMG REXX.IM_ 13 07/20/1999 19:44 283636 D800799D
REXXAPI.DLL REXXAPI.DL_ 15 07/23/1998 15:54 29603 057F1B73
REXXC.EXE REXXC.EX_ 16 07/20/1999 19:44 2758 D08667FF
REXXCRT.DLL REXXCRT.DL_ 14 03/31/1997 17:35 61195 D865CF3E
REXXUTIL.DLL REXXUTIL.DL_ 14 11/20/1998 15:58 49229 DFDA8338
REXXUTIL.DLL ORXUTIL1.DL_ 15 11/20/1998 15:58 33725 532823E8
RINSTPRN.EXE RINSTPRN.EX_ 10 07/20/1999 21:27 194722 94E9C8E0
RO.KBL RO.KB_ 17 07/26/1999 13:31 944 287BC033
RSPDDI.EXE RSPDDI.EX_ 16 07/21/1999 10:48 22073 79CBAEFA
RSPDSPI.EXE RSPDSPI.EX_ 13 07/21/1999 10:57 95352 1DF13B3D
RSPINST.EXE RSPINST.EX_ 8 07/21/1999 10:44 428896 123BA1B7
RSRV.EXE RSRV.EX_ 13 10/28/1997 14:19 77955 45C9BACB
RU.KBL RU.KB_ 17 07/26/1999 13:31 1144 2D54C7A3
SCENTER.DLL SCENTER.DL_ 7 09/01/1999 11:12 291673 05C2707B
SD.KBL SD.KB_ 17 07/26/1999 13:31 1036 833E7757
SEAMLESS.DLL SEAMLESS.DL_ 15 09/01/1999 10:17 48655 81098A1B
SECUTIL.DLL SECUTIL.DL_ 16 04/01/1999 14:34 21468 55F6B618
SEINST.EXE SEINST.EX_ 15 07/21/1999 10:34 37441 85BC9A83
FixPak Corrective Service levels and disk layouts 46
September 29, 1999 - Warp 4 FixPak XR_M012
SEMAINT.EXE SEMAINT.EX_ 14 07/21/1999 10:34 67376 A4A49312
SERIAL.PDR SERIAL.PD_ 16 07/27/1999 11:59 19060 397E0C70
SESAPI.DLL SESAPI.DL_ 16 07/20/1999 19:59 24219 7BDCCB5E
SESDD32.SYS SESDD32.SY_ 14 07/20/1999 19:59 118832 B78FEE23
SESMGR.DLL SESMGR.DL_ 17 07/21/1999 12:10 1536 466106AD
SESMGR.TDF SESMGR.TD_ 16 07/27/1999 11:49 1877 9A0C998F
SETBOOT.EXE SETBOOT.EX_ 2 07/27/1999 11:57 17196 498930D8
SETDEFV.CMD SETDEFV.CM_ 16 06/23/1998 16:25 1652 BE7ED9EF
SF.KBL SF.KB_ 16 07/26/1999 13:31 1036 7E45199D
SK.KBL SK.KB_ 16 07/26/1999 13:31 1008 EC2D5647
SL.KBL SL.KB_ 16 07/26/1999 13:31 982 FD150232
SOFTDRAW.DLL SOFTDRAW.DL_ 8 04/13/1999 15:30 401003 FDB06A84
SOM.DLL SOM.DL_ 13 08/13/1996 09:29 88763 7804D814
SPCHOBJ.DLL SPCHOBJ.DL_ 12 12/21/1997 01:27 132899 E393F817
SPL1B.DLL SPL1B.DL_ 16 07/27/1999 12:02 5077 0353F1BC
SQ.KBL SQ.KB_ 16 07/26/1999 13:31 824 D5F858D7
SSM.DLL SSM.DL_ 16 09/29/1998 16:01 1556 382C768D
SSMDD.SYS SSMDD.SY_ 16 09/29/1998 16:09 36813 B39AF043
STRACE.EXE STRACE.EX_ 15 07/21/1999 12:32 40318 7138CB16
SV.KBL SV.KB_ 16 07/26/1999 13:31 946 FF0DB860
SVMC.DLL SVMC.DL_ 12 02/03/1999 11:25 98389 B3501172
SVSH.DLL SVSH.DL_ 16 02/03/1999 11:26 23452 6C7078C9
SW.DLL SW.DL_ 14 02/03/1999 11:25 66503 8FE319CA
SWITCHRX.CMD SWITCHRX.CM_ 16 05/06/1998 16:31 7928 79CA9FC4
SYMB.PFM SYM1.PF_ 17 03/15/1999 13:45 679 F258E0BD
SYSDUMP.EXE SYSDUMP.EX_ 16 07/21/1999 12:16 16000 6605F03E
SYSINST2.EXE SYSINST2.EX_ 9 07/21/1999 10:40 184512 17D9B6B5
SYSINSTX.COM SYSINSTX.CO_ 15 07/27/1999 11:55 39472 39F8B7CF
SYSLEVEL.EXE SYSLEVEL.EX_ 15 07/21/1999 10:33 42864 86E5EB80
SYSLEVEL.FPK SYSLEVEL.FP_ 17 08/03/1999 13:31 165 353832F0
SYSLOGPM.EXE SYSLOGPM.EX_ 11 07/26/1999 15:37 138955 97EF97B3
SYSMONO.FON SYSMONO.FO_ 16 04/07/1999 15:05 21294 DD0CCA1D
SYSMONOI.FON SYSMONOI.FO_ 15 04/07/1999 14:09 35841 F038FB2C
SYSSPLIT.CMD SYSSPLIT.CM_ 16 12/02/1998 16:25 3712 A35A41C8
SYSTEM.TDF SYSTEM.TD_ 14 09/25/1998 12:06 18358 35415CA8
SYSTEM.TFF SYSTEM.TF_ 16 09/25/1998 12:06 45067 429E1521
SYSTEMD.TFF SYSTEMD.TF_ 16 09/25/1998 12:06 45067 FE173666
TDFLST.CMD TDFLST.CM_ 16 12/02/1998 16:25 13564 A45F3592
TEDIT.EXE TEDIT.EX_ 16 11/04/1996 16:50 9390 113FA989
TEDIT.HLP TEDIT.HL_ 16 11/04/1996 14:56 14596 88E1376F
TESTCFG.SYS TESTCFG.SY_ 16 07/12/1999 16:11 9808 58CE2D16
TEXTCON1.EXE TEXTCON1.EX_ 15 04/12/1999 15:53 49011 25471D05
TFFLST.CMD TFFLST.CM_ 16 12/02/1998 16:25 4638 2AFE15D2
TIMES.FON TIMES.FO_ 11 04/07/1999 14:14 166150 532CB4D1
TIMESI.FON TIMESI.FO_ 11 04/07/1999 14:09 181173 DFD253CC
TNR.OFM TNR.OF_ 16 03/15/1999 13:45 6809 33F5154C
TNR.PFB TNR.PF_ 10 03/15/1999 13:46 145785 BD752E3E
TNR.PFM TN1.PF_ 16 03/15/1999 13:45 1103 4811CE38
TNRB.OFM TNRB.OF_ 16 03/15/1999 13:45 6825 36C2110D
TNRB.PFB TNRB.PF_ 9 03/15/1999 13:47 148564 014EE100
TNRB.PFM TNR1.PF_ 16 03/15/1999 13:45 1112 6044C543
FixPak Corrective Service levels and disk layouts 47
September 29, 1999 - Warp 4 FixPak XR_M012
TNRBI.OFM TNRBI.OF_ 16 03/15/1999 13:45 6839 8F51C7B5
TNRBI.PFB TNRBI.PF_ 9 03/15/1999 13:47 159652 81973739
TNRBI.PFM TNRB1.PF_ 16 03/15/1999 13:45 1118 690A75CD
TNRI.OFM TNRI.OF_ 16 03/15/1999 13:45 6830 23B86562
TNRI.PFB TNRI.PF_ 9 03/15/1999 13:47 157010 5E813D84
TNRI.PFM TNR2.PF_ 16 03/15/1999 13:45 1114 CA6E659D
TR.KBL TR.KB_ 16 07/26/1999 13:31 962 29C87B20
TR440.KBL TR440.KB_ 16 07/26/1999 13:31 1042 622614BA
TRACE.DOC TRACE.DO_ 16 04/01/1999 16:21 64057 45DDD8C5
TRACE.EXE TRACE.EX_ 15 07/27/1999 11:59 35136 427719C0
TRACEDLL.DLL TRACEDLL.DL_ 14 07/26/1999 15:40 46675 4AD8FB06
TRACEFMT.EXE TRACEFMT.EX_ 11 07/21/1999 12:35 156569 07116517
TRACEGET.EXE TRACGET1.EX_ 16 07/20/1999 20:07 22026 F16B1EAB
TRACEGET.EXE TRACEGET.EX_ 16 07/20/1999 20:07 22026 F16B1EAB
TRAPDUMP.EXE TRAPDUMP.EX_ 16 07/20/1999 20:10 23068 4C2821DC
TRAPLOG.EXE TRAPLOG.EX_ 16 07/21/1999 12:16 15056 DE9918A2
TRC0000.TFF TRC0000.TF_ 17 11/24/1998 09:09 189 0EDB257E
TRC0001.TFF TRC0001.TF_ 16 07/24/1999 12:53 17168 73D22B9B
TRC0003.TFF TRC0003.TF_ 17 12/12/1996 17:56 1503 3435868F
TRC0004.TFF TRC0004.TF_ 16 11/24/1998 09:09 4754 E52D826B
TRC0005.TFF TRC0005.TF_ 16 08/10/1999 15:27 38713 BDBFABEA
TRC0006.TFF TRC0006.TF_ 16 12/12/1996 17:19 12356 B2A0674E
TRC0007.TFF TRC0007.TF_ 16 07/12/1999 15:22 1394 9B783BA9
TRC0008.TFF TRC0008.TF_ 17 07/12/1999 15:17 544 451F96D2
TRC0010.TFF TRC0010.TF_ 16 07/27/1999 11:49 13359 4A08217F
TRC0012.TFF TRC0012.TF_ 17 07/21/1999 12:11 1247 1801F30D
TRC0016.TFF TRC0016.TF_ 16 07/27/1999 11:49 1663 A66BF6BB
TRC0017.TFF TRC0017.TF_ 16 07/27/1999 11:49 5561 FEB3BD16
TRC0018.TFF TRC0018.TF_ 16 07/27/1999 11:49 39488 7B261360
TRC006D.TFF TRC006D.TF_ 16 06/23/1998 19:40 24181 FB8B4954
TRC00C0.TFF TRC00C0.TF_ 16 07/24/1999 15:10 15970 F972FC65
TRC00C2.TFF TRC00C2.TF_ 16 07/24/1999 15:10 25991 CC93DB61
TRC00C3.TFF TRC00C3.TF_ 16 07/24/1999 15:10 3984 8EEF4A9F
TRC00C4.TFF TRC00C4.TF_ 16 07/24/1999 15:24 288 62203DA4
TRC00C5.TFF TRC00C5.TF_ 16 04/13/1999 15:37 32994 870A02D8
TRC00C6.TFF TRC00C6.TF_ 16 09/01/1999 10:57 7146 F49B3CAD
TRC0100.TFF TRC0100.TF_ 16 08/10/1999 15:27 6190 B1E78AA4
TRC0101.TFF TRC0101.TF_ 16 08/10/1999 15:27 7422 674156C6
TRC0102.TFF TRC0102.TF_ 16 08/10/1999 15:27 25895 75D413CB
TRC0103.TFF TRC0103.TF_ 16 08/10/1999 15:27 10057 C08743FD
TRC0104.TFF TRC0104.TF_ 16 08/10/1999 15:27 5135 C6401708
TRC0105.TFF TRC0105.TF_ 16 08/10/1999 15:27 28049 AE82BEC2
TRC0106.TFF TRC0106.TF_ 16 08/10/1999 15:27 1835 B1FAB22E
TRC0107.TFF TRC0107.TF_ 16 08/10/1999 15:28 4403 9731897E
TRC0108.TFF TRC0108.TF_ 16 08/10/1999 15:28 9456 FD1C0D84
TRC0109.TFF TRC0109.TF_ 16 08/10/1999 15:28 2535 CF7D8610
TRC010A.TFF TRC010A.TF_ 7 08/10/1999 15:28 1029 FDEB969A
TRC0118.TFF TRC0118.TF_ 16 08/10/1999 15:17 2526 465CF705
TRC0119.TFF TRC0119.TF_ 16 08/10/1999 15:29 3786 6E199CCC
TRC012C.TFF TRC012C.TF_ 16 09/01/1999 10:17 5361 796B91F9
TRC012D.TFF TRC012D.TF_ 16 09/01/1999 10:17 7870 F9F5F0A8
FixPak Corrective Service levels and disk layouts 48
September 29, 1999 - Warp 4 FixPak XR_M012
TRC012E.TFF TRC012E.TF_ 16 09/01/1999 10:52 32972 8DB1B612
TRCFORMT.DLL TRCFORMT.DL_ 16 04/01/1999 17:24 26645 34A6A109
TRCUST.EXE TRCUST.EX_ 14 07/21/1999 12:32 98773 3BA6F1BE
TRSPOOL.DOC TRSPOOL.DO_ 16 04/01/1999 14:23 6638 7C5EE1B2
TRSPOOL.EXE TRSPOOL1.EX_ 15 07/23/1999 12:01 27982 E701548C
TRSPOOL.EXE TRSPOOL.EX_ 15 07/23/1999 12:01 27982 E701548C
TRSTOP.EXE TRSTOP.EX_ 16 07/26/1999 15:40 17190 517F2AE4
TRUETYPE.DLL TRUETYPE.DL_ 12 03/15/1999 18:36 128695 E483A9B8
UA.KBL UA.KB_ 16 07/26/1999 13:31 1476 4033A2EE
UCDFS.DLL UCDFS.DL_ 8 10/21/1996 09:24 13264 C114CE18
UCONV.DLL UCONV.DL_ 16 07/26/1999 13:34 22819 668668E1
UHPFS.DLL UHPFS.DL_ 13 08/10/1999 15:18 104976 A40756B7
UK.KBL UK.KB_ 16 07/26/1999 13:31 816 BE2140D7
UK168.KBL UK168.KB_ 16 07/26/1999 13:31 850 A02B2351
ULSACT01.MSG ULSACT01.MS_ 4 07/24/1999 14:03 907 CD660D41
ULSCAU01.MSG ULSCAU01.MS_ 3 07/24/1999 14:03 899 5BFC412F
ULSDET01.MSG ULSDET01.MS_ 1 07/24/1999 14:03 903 A118B7BE
ULSERR01.MSG ULSERR01.MS_ 16 07/24/1999 14:03 1967 13B3FAC9
UNINSTAL.EXE UNINSTAL.EX_ 12 07/21/1999 10:52 99593 C8716398
UNPACK2.EXE UNPACK2.EX_ 14 07/21/1999 11:02 79792 4A84FBCE
USER.EXE USER.EX_ 9 09/02/1999 12:14 281088 44791624
USINTER.KBL USINTER.KB_ 16 07/26/1999 13:31 1032 45B0C287
VBIOS.SYS VBIOS.SY_ 16 04/01/1999 17:25 8816 9446356A
VCMOS.SYS VCMOS.SY_ 16 09/24/1998 09:50 2272 55C71989
VDMA.SYS VDMAPS2.SY_ 16 04/01/1999 17:25 14329 D644BA90
VDMA.SYS VDMAAT.SY_ 16 11/23/1998 17:38 11465 50D5B07B
VDPMI.SYS VDPMI.SY_ 16 09/24/1998 09:51 30624 F1E303B1
VDPX.SYS VDPX.SY_ 16 04/01/1999 17:25 26112 E39A202E
VGA.DSP VGA.DS_ 16 07/27/1999 09:40 3094 4DB5F174
VIEW.EXE VIEW.EX_ 15 09/01/1999 10:17 26828 69044F47
VIOCALLS.DLL VIOCALLS.DL_ 15 07/24/1999 15:26 2048 03BFEB9A
VIOTBL.DCP VIOTBL.DC_ 15 03/29/1999 17:14 225355 40A5689E
VIOTBL.ISO VIOTBL.IS_ 15 03/29/1999 17:14 230105 349B721C
VMAN.DLL VMAN.DL_ 16 04/07/1999 21:39 26637 EC69F3C3
VMANWIN.SYS VMANWIN.SY_ 16 04/07/1999 17:40 3024 BCD10FFA
VPIC.SYS VPIC.SY_ 16 04/01/1999 17:25 9942 A98D25CB
VPICPARM.SYS VPICPARM.SY_ 10 09/24/1998 09:51 736 A2AC5451
VTIMER.SYS VTIMER.SY_ 16 09/24/1998 09:51 9936 DF6F879B
VW32S.SYS VW32S.SY_ 4 04/01/1999 17:26 18336 B5D35004
VWIN.SYS VWIN.SY_ 16 04/01/1999 17:26 27088 59687017
WCFGMRI.DLL WCFGMRI.DL_ 16 07/23/1998 19:04 2596 B73786AA
WD24B.DSP WD24B.DS_ 12 04/03/1997 13:55 12050 329F1B70
WINCFG.DLL WINCFG.DL_ 16 09/01/1999 10:54 12839 65C18565
WINFILE.EXE WINFILE.EX_ 13 07/19/1999 16:52 146960 A48056E1
WINSCLIP.DLL WINSCLIP.DL_ 16 09/02/1999 12:05 14848 463E01BC
WINSDDE.DLL WINSDDE.DL_ 16 09/02/1999 12:05 18432 A4E7AF73
WINSHELD.EXE WINSHELD.EX_ 16 09/02/1999 12:05 22016 10F12650
WINSMSG.DLL WINSMSG.DL_ 16 09/02/1999 12:05 28441 04BD0009
WPCLS.IMP WPCLS.IM_ 16 03/31/1997 17:35 8661 DA24BBC2
WPCONFIG.DLL WPCONFIG.DL_ 8 09/01/1999 10:54 246078 C9F25DCD
WPCONMRI.DLL WPCONMRI.DL_ 16 07/23/1998 19:04 27694 4487233F
FixPak Corrective Service levels and disk layouts 49
September 29, 1999 - Warp 4 FixPak XR_M012
WPHELP.HLP WPHELP.HL_ 5 07/27/1999 08:45 841366 C7FE7138
WPINET.DLL WPINET.DL_ 12 09/01/1999 11:11 115384 47CE9EA8
WPMSG.HLP WPMSG.HL_ 15 07/27/1999 08:45 50198 9FB1BB75
WPPRINT.DLL WPPRINT.DL_ 2 09/01/1999 10:56 364008 6E4B85F0
WPPRINT.HLP WPPRINT.HL_ 14 07/27/1999 08:45 71408 00006E0A
WPPRTMRI.DLL WPPRTMRI.DL_ 14 09/01/1999 10:56 66681 9CAB66DE
WPREXX.IMP WPREXX.IM_ 16 03/31/1997 17:35 6313 707B163F
WPSINIT.WPS WPSINIT.WP_ 16 03/31/1997 17:35 15877 ACC13319
WPSINST.CMD WPSINST.CM_ 16 05/06/1998 16:31 2813 4BAD1428
WW.EXE WW.EX_ 11 04/01/1997 15:37 8305 0BC99079
WWDLL.DLL WWDLL.DL_ 7 12/21/1997 01:29 276981 751EB674
WWHOOK.DLL WWHOOK.DL_ 16 12/21/1997 01:29 27230 893E24E8
XCOPY.EXE XCOPY.EX_ 15 07/27/1999 11:55 51152 9F9E80E7
XPG00420.TBL XPG00420.TB_ 16 04/12/1999 15:51 27264 88668BE7
XPG00864.TBL XPG00864.TB_ 16 04/12/1999 15:51 27264 2672604F
************************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M012_ (Country = Generic)
Pre-requisite CSD Level: XR_4000_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
OS2LDR OS2LDR.___ 17 07/27/1999 11:39 33280 4DD2851F
************************************************************************
Product location on CSD: A:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
Fixpak name: XR_M012_ (Country = Generic)
FixPak Corrective Service levels and disk layouts 50
September 29, 1999 - Warp 4 FixPak XR_M012
Pre-requisite CSD Level: XR_4010_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
APPDBUTL.DLL APPDBUTL.DL_ 17 09/24/1998 12:44 25013 B03740C5
APPSTART.EXE APPSTART.EX_ 17 09/24/1998 12:45 33864 F3D9B794
NCAPPUTL.EXE NCAPPUTL.EX_ 17 05/11/1998 10:54 12612 F048440D
OS2LDR OS2LDR.___ 17 07/27/1999 11:39 33280 6DC90137
PMLOGON.EXE PMLOGON.EX_ 17 09/24/1998 12:49 40107 6ECF0A76
PRNCFG.DLL PRNCFG.DL_ 17 09/24/1998 12:51 58258 1083DD95
TDESK.DLL TDESK.DL_ 17 09/24/1998 12:48 3769 CC72A5DC
TLOGOFF.EXE TLOGOFF.EX_ 17 09/24/1998 12:48 9577 DB742894
TOBJECT.DLL TOBJECT.DL_ 17 09/24/1998 12:48 4876 54B32CDC
TSHUTDWN.EXE TSHUTDWN.EX_ 17 09/24/1998 12:48 8611 BB45D1FD
FixPak Corrective Service levels and disk layouts 51
September 29, 1999 - Warp 4 FixPak XR_M012
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 35MB FixPak Archive/Backup for product with CSD level of
XR_4000
Up to 35MB FixPak Archive/Backup for product with CSD level of
XR_4010
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 52
September 29, 1999 - Warp 4 FixPak XR_M012
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 53