home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 28 Fixes4x
/
28-Fixes4x.zip
/
xr_m010.1dk
/
README.1ST
< prev
next >
Wrap
Text File
|
1999-02-26
|
125KB
|
3,190 lines
< Installation instructions for Warp 4 FixPak XR_M010
February 26, 1999
This FixPak makes the products it services Year 2000 ready
Build level 9.034
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
Component ID: 5639A6100
Version: 4.01
Type: 0C
Requires Corrective Service Facility release F.140 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
February 26, 1999 - Warp 4 FixPak XR_M010
February 26, 1999 - Warp 4 FixPak XR_M010
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3
3.0.1 Can't install Warp 4 . . . . . . . . . . . . . . . . . . . . 3
3.0.2 Please use Fixtool f.140 or later . . . . . . . . . . . . . 3
3.0.3 TRAP in ES16881$ after FP10 applied . . . . . . . . . . . . 3
3.0.4 System Sounds not working after FixPak applied . . . . . . . 3
3.0.5 Using Display Recovery Choices . . . . . . . . . . . . . . . 4
3.0.6 Installation of Java 1.1.4 . . . . . . . . . . . . . . . . . 5
3.0.7 DSPRES.DLL included in this FixPak . . . . . . . . . . . . . 5
3.0.8 No products were found . . . . . . . . . . . . . . . . . . . 5
3.0.9 Previous installation interrupted . . . . . . . . . . . . . 6
3.0.10 Unable to open Archive directory . . . . . . . . . . . . . 6
3.0.11 RC 932 doing CID install of Warp 4 . . . . . . . . . . . . 6
3.0.12 Multimedia no longer selectable . . . . . . . . . . . . . . 8
3.0.13 MMPARTS.DLL/USER.EXE popup during install . . . . . . . . . 8
3.0.14 CSF0208 No products were found on the target ... . . . . . 8
3.0.15 CSF0248 Archive path is shared between mismatched . . . . . 8
3.0.16 CSF0249 Error opening or creating archive file. . . . . . 9
3.0.17 Printer installation process change . . . . . . . . . . . . 9
3.0.18 Configuration Installation Distribution ( CID ) . . . . . . 9
4.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 10
4.0.1 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 10
4.0.2 Windows printer drivers leave a zombie thread running . . . 10
4.0.3 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . . . . 11
4.0.4 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . . . 11
4.0.5 Intermittent hangs . . . . . . . . . . . . . . . . . . . . 11
4.0.6 Intermittent pause with IBM Thinkpad 760E/ED/ELD/EL . . . . 11
4.0.7 APM users . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 13
5.2 Querying file dates for files after Dec 31, 1999 in REXX . . . 13
5.3 Enhanced support for Workspace On-Demand . . . . . . . . . . . 14
5.3.1 PMLOGON user exits . . . . . . . . . . . . . . . . . . . . 14
5.3.2 Setup strings for public applications . . . . . . . . . . . 17
5.3.3 Command line options for TLOGOFF and TSHUTDWN . . . . . . . 18
5.3.4 PMLOGON No Progress Indicator option . . . . . . . . . . . 18
5.3.5 PMLOGON No System Modal Window option . . . . . . . . . . . 19
5.4 Fixed IDE Hard Drive and Removable Media Support . . . . . . . 19
5.5 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.5.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 19
5.5.2 Where euro is not supported . . . . . . . . . . . . . . . . 21
5.5.3 Printing the euro . . . . . . . . . . . . . . . . . . . . . 21
5.6 New Warp Registry Editor . . . . . . . . . . . . . . . . . . . 21
Contents ii
February 26, 1999 - Warp 4 FixPak XR_M010
5.7 WorkSpace On Demand . . . . . . . . . . . . . . . . . . . . . . 21
5.8 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.9 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 22
5.10 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 22
5.10.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 22
5.10.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 24
5.11 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 25
5.11.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 25
5.11.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.11.3 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.11.4 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.12 Other README files . . . . . . . . . . . . . . . . . . . . . . 27
6.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 28
6.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 28
6.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 28
6.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 29
6.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . . . . 29
6.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 30
6.4 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 31
7.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 33
7.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 33
7.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 33
7.3 Method 2: Install from alternate bootable media . . . . . . . . 34
7.4 Additional Corrective Service Facility information . . . . . . 35
7.5 FixPaks on CD-ROM . . . . . . . . . . . . . . . . . . . . . . . 35
8.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 36
8.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 37
9.0 FixPak Corrective Service levels and disk layouts . . . . . . . 38
10.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 52
10.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 52
10.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 53
Contents iii
February 26, 1999 - Warp 4 FixPak XR_M010
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_M010 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_M010 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
February 26, 1999 - Warp 4 FixPak XR_M010
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
February 26, 1999 - Warp 4 FixPak XR_M010
3.0 INSTALLATION NOTES
3.0.1 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.2 PLEASE USE FIXTOOL F.140 OR LATER
Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
Corrective Service Facility F.140 or later. It has fixes for problems
found in the F.138B and F.139 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 40 and 10) and type 2 (FixPaks
40 and 10 and later) FixPaks.
If you try to use a CSF level prior to F.138B you will get a "CSF0208 No
products were found on the target system to service" message.
3.0.3 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 ESE device driver for your card from
the OS/2 Device Driver Pak online at
http://service.software.ibm.com/os2ddpak/html/multimed/esstechn
Do this before you install the FixPak.
3.0.4 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:
Installation Notes 3
February 26, 1999 - Warp 4 FixPak XR_M010
\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 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.5 USING DISPLAY RECOVERY CHOICES
If you have the "Display Recovery Choices at each system startup"
function active on your system, you need to disable it before you apply a
FixPak if
■ The system is running
■ The boot partition will be serviced.
The problem with using this function is that the Corrective Service
Facility (CSF) updates the current CONFIG.SYS with entries to run the
Locked File Device Driver (LFDD) the next time you boot the system. This
is done to replace files that are currently in use (locked) by the
system.
Installation Notes 4
February 26, 1999 - Warp 4 FixPak XR_M010
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.6 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.7 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.8 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
Check for the following files in your MMOS2\INSTALL directory.
Installation Notes 5
February 26, 1999 - Warp 4 FixPak XR_M010
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.9 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.10 UNABLE TO OPEN ARCHIVE DIRECTORY
If you get a message about problems with the Archive directory (for
example, cannot find or unable to open), then the most probable cause is
that you applied a previous FixPak and have since deleted the FixPak
ARCHIVE or BACKUP directory.
To recover from this, follow the "No files to service" and "Previous
installation interrupted" steps listed above.
3.0.11 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.
Installation Notes 6
February 26, 1999 - Warp 4 FixPak XR_M010
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
ftp://ps.software.ibm.com/ps/products/os2/fixes/v4warp
15.PACK2 CHKDSK32.EXE bundle /H:\OS2\CHKDSK32.EXE /A
Installation Notes 7
February 26, 1999 - Warp 4 FixPak XR_M010
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.12 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.13 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.14 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.15 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED
1. The Archive path you specified (or was previously specified) contains
files from a different release of OS/2. You need to specify a
different Archive path.
2. You have a bad SYSLEVEL.OS2 or SYSLEVEL.MPM file. Both must have the
same Current CSD Level, Version, Type and Component ID if you point
both Fixpak Archives to the same location.
Check \OS2\INSTALL\SYSLEVEL.OS2 and \MMOS2\INSTALL\SYSLEVEL.MPM. If
either is wrong, place the last FixPak disk in A: and run FIXSYSL.CMD
to correct SYSLEVEL.OS2 problems or SYSZMPM.CMD to fix SYSLEVEL.MPM
problems.
Installation Notes 8
February 26, 1999 - Warp 4 FixPak XR_M010
3.0.16 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.17 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.18 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )
Read the README.CID on Disk # 1 for an example of how to set up a
response file to do a CID install.
Installation Notes 9
February 26, 1999 - Warp 4 FixPak XR_M010
4.0 POST INSTALLATION NOTES
4.0.1 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.2 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 10
February 26, 1999 - Warp 4 FixPak XR_M010
4.0.3 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.4 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.5 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.
4.0.6 INTERMITTENT PAUSE WITH IBM THINKPAD 760E/ED/ELD/EL
If you have an IBM Thinkpad 760E/ED/ELD/EL that exhibits sluggish
harddisk behavior (pausing intermittently with hard drive light on) after
this FixPak has been applied, add the /!BM parameter to the
BASEDEV=IBM1S506.ADD statement (if present) in your CONFIG.SYS. This
will disable the Bus Mastering function whose default has been changed
from OFF to ON.
If your CONFIG.SYS has the statement
BASEDEV=PIIXIDE.ADD
Post Installation Notes 11
February 26, 1999 - Warp 4 FixPak XR_M010
you must remark out the statement by inserting REM as the first
characters on the line as shown below.
REM BASEDEV=PIIXIDE.ADD
BASEDEV=IBM1S506.ADD /A:0 /!BM /U:1 /ATAPI /FORCE
4.0.7 APM USERS
APM users will need to add the following statement after the
DEVICE=\OS2\BOOT\APM.SYS statement in their CONFIG.SYS:
RUN=\OS2\BOOT\APMDAEMN.EXE
This will complete the fix for APAR JR09869.
Post Installation Notes 12
February 26, 1999 - Warp 4 FixPak XR_M010
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. Under 5.0 New Function. Add a new section (5.15)
Serviceability (RAS) Enhancements. with the following words:
5.1 SERVICEABILITY (RAS) ENHANCEMENTS
With FixPak 35 for Warp 3.0 and FixPak 10 for Warp 4.0 major enhancements
were provided to the system diagnostic tools (RAS Enhancements). They
provide major functional enhancements to the System Trace and Process
Dump facilities. Full details of these enhancements can be found in the
README.DBG file that will be found in the \OS2\INSTALL directory after
this FixPak is installed.
Other associated documentation may be found in:
■ OS2\SYSTEM\RAS\TRACE.DOC
■ OS2\SYSTEM\RAS\DTRACE.DOC
■ OS2\SYSTEM\RAS\PROCDUMP.DOC
■ OS2\SYSTEM\RAS\TRSPOOL.DOC
Always refer to README.DBG for details of any RAS enhancements delivered
with a FixPak.
5.2 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX
Existing REXX functions return file dates with a two digit year only.
While these functions are Year 2000 tolerant (i.e. the results will be
correct for files dated after Dec 31, 1999) they require some additional
logic in existing programs to handle the returned date correctly when
they are compared with other file dates.
Since the output format of the existing functions could not be changed
for compatibility reasons, new options have been added to the REXX
interpreter to return file dates with the year formatted with 4 digits.
Two functions have been extended to support the new format. The syntax to
retrieve the file date in 4 digit format is as follows:
New Function 13
February 26, 1999 - Warp 4 FixPak XR_M010
/********************************************/
/* Use STREAM QUERY TIMESTAMP to query file */
/* date in 4 digit format */
/********************************************/
Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP")
/***********************************************/
/* Use option "L" with SysFileTree to return a */
/* list of files with long date format */
/***********************************************/
Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
Call SysLoadFuncs
Call SysFileTree "C:\*.*", "Files", "L"
Do i = 1 To Files.0
Say Files.i
End
These extensions are available in both classic REXX and Object REXX on
OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these
extensions in your program you have to make sure that you are running the
right level of REXX
5.3 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND
5.3.1 PMLOGON USER EXITS
This function, provided by PMLOGON, allows system integrators to have
REXX code executed at specific points during the startup and logon
sequence. By default, user exits are disabled in PMLOGON.EXE. To enable
user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the
CONFIG.SYS file must be added. The /URX parameter specifies the location
and name of the user exit command file:
Execution Parameter User Exit command file that will be
executed
------------------- -----------------------------------
/URX \OS2\PMLOGURX.CMD
/URX:<filename>.CMD <filename>.CMD located in one of the
locations specified by the PATH
environment variable
/URX:d:\<path>\<filename>.CMD d:\<path>\<filename>.CMD
New Function 14
February 26, 1999 - Warp 4 FixPak XR_M010
The same command file is called for ALL user exits. The FIRST parameter
supplied to the command file indicates the exit that it is being called
for. The REXX command file is called for all these exits, even if it does
not need to process all of the exits. The REXX command file must be able
to return error free if it receives an exit number that it does not need
to handle. The following user exits are available:
New Function 15
February 26, 1999 - Warp 4 FixPak XR_M010
First Parameter Exit Description
--------------- ----------------
0 Executes ONCE per boot, before the requester
is started. There is no user logged on at this
time. This exit may return a string that is
processed exactly as the following execution
parameters set in RUNWORKPLACE of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately after the execution
parameters. See Note 2 below on /AUTO processing.
1 Executes ONCE per logon, after the requester
is started, but before logon occurs. There is no
user logged on at this time. This exit may return
a string that is processed exactly as the
following execution parameters set in RUNWORKPLACE
of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately before logon. See
Note 2 below on /AUTO processing.
2 Executes ONCE per logon, after the requester is
started and after logon occurs. There is a user
logged on at this time, but the Desktop has not
been started and the objects are not displayed.
No returns are processed.
3 Executes ONCE per logon, after the Desktop has
been started and the objects are created but not
currently displayed, but immediately before
control is passed to the Desktop. The icons are
fixed at this point. There is a user logged on
at this time. No returns are processed.
4 Executes immediately after a failed logon. The
second parameter passed to the exit contains the
return code from the logon API. This exit may
return a string that is processed exactly as the
execution parameters set in RUNWORKPLACE of
CONFIG.SYS for the following parameters only:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
This exit is processed immediately and logon is
retried with the new parameters regardless of
the /AUTO switch. See Note 2 below on /AUTO
New Function 16
February 26, 1999 - Warp 4 FixPak XR_M010
processing. If no string is returned, then the
normal logon failure or password expired message
box is displayed.
Note 1: The session environment for the REXX command file is that
of PMLOGON.EXE and, therefore, does not contain any input or
output facility. For example, "PULL" from the keyboard and
"SAY" to the console do not work.
Note 2: The /AUTO parameter is validated at every step (for example,
after command line processing, after exit 0 returns, and
after exit 1 returns). It is turned off if insufficient
information (such as no user ID) is provided at that stage
for an automatic logon. If the user ID is supplied by the
exit, that exit must also provide the /AUTO parameter in
order for an auto logon to work.
5.3.2 SETUP STRINGS FOR PUBLIC APPLICATIONS
The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific
Workplace Shell WPProgram setup strings that are provided when creating
public applications on the WorkSpace On-Demand Desktop. In particular,
the ICONPOS setup string can be defined for a public application so that
the Administrator can identify where application icons are placed on the
WorkSpace On-Demand Desktop.
When a WorkSpace On-Demand Administrator creates a public application, a
new environment variable must be added to the application to provide a
setup string. The parameter name is NCC_SETUP_POST and the parameter
value can consist of any of the setup strings specified below. Each
setup string consists of a KEYNAME, followed immediately by an equal
('=') sign and a VALUE. Multiple setup strings can be passed in the
NCC_SETUP_POST environment variable by separating each setup string with
a semicolon (';'). The creation of this parameter can be performed
either using the WorkSpace On-Demand Public Applications Notebook (on the
Parameters page) or using a Command Line Interface (CLI). The following
is an example of one parameter:
NCC_SETUP_POST=ICONPOS=10,10;
The NCC_SETUP_POST environment variable will be searched for when each
WorkSpace On-Demand public application is created. If it is found, its
value will be used when creating the public application on the WorkSpace
On-Demand Desktop.
The following KEYNAME values are permitted for setup strings:
New Function 17
February 26, 1999 - Warp 4 FixPak XR_M010
Keyname Value Description
------- ----- -----------
CCVIEW DEFAULT Specifies the default value for
concurrent views
YES Creates new views
NO Displays the open view
ICONFILE filename Sets the object's icon.
ICONPOS x,y Sets the initial icon position in
a folder. The "x" and "y" values
represent the position in the object's
folder in percentage coordinates.
ICONRESOURCE id,module Sets the object's icon. The "id"
is the icon resource ID in the dynamic
link library (DLL) "module."
Refer to the Workplace Shell Programming Reference for a description and
definition of the above setup strings.
Note: The NCC_SETUP_POST environment variable exists in the current
environment when the public application with which it is associated is
running.
5.3.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN
Three command line options have been added to both TLOGOFF.EXE and
TSHUTDWN.EXE:
1. /Q -- causes these programs not to display the UPM/LAN
copyright window.
2. /N -- causes no confirmation message boxes to be displayed.
Note: If these parameters are not capitalized, they are ignored.
5.3.4 PMLOGON NO PROGRESS INDICATOR OPTION
An execution parameter has been added to PMLOGON that causes the progress
indicator window not to be displayed during all of logon processing. That
parameter is /NOPI and can be specified only from the RUNWORKPLACE line
in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit,
it is ignored.
New Function 18
February 26, 1999 - Warp 4 FixPak XR_M010
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 FIXED IDE HARD DRIVE AND REMOVABLE MEDIA SUPPORT
FixPak 35 (FP35) for Warp 3 and FixPak 6 (FP6) for Warp 4 extended
support for fixed Enhanced IDE drives to sizes up to 8.4GB and added new
caching HPFS and FAT file system support for removable media drives such
as SCSI Syquest Syjet 1.5GB portable hard drive and the Iomega jaz 1GB
and 2GB personal hard drives.
5.5 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.5.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
New Function 19
February 26, 1999 - Warp 4 FixPak XR_M010
The euro character is added to these fonts.
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
New Function 20
February 26, 1999 - Warp 4 FixPak XR_M010
5.5.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:
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.5.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.6 NEW WARP REGISTRY EDITOR
See the README.REG file on the first FixPak disk for details.
5.7 WORKSPACE ON DEMAND
WorkSpace on Demand is supported starting with FixPak 5 (XR_M005).
New Function 21
February 26, 1999 - Warp 4 FixPak XR_M010
5.8 IBM OPEN32
This FixPak includes updates to the IBM Open32 Application Programming
Interfaces (APIs).
5.9 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.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.
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:
New Function 22
February 26, 1999 - Warp 4 FixPak XR_M010
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.
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.
New Function 23
February 26, 1999 - Warp 4 FixPak XR_M010
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:
message.txt
msghdr.txt
pmchklog.exe
range.txt
readme
They should all have a date of 05/14/97 or later (May 14, 1997).
New Function 24
February 26, 1999 - Warp 4 FixPak XR_M010
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]
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.
New Function 25
February 26, 1999 - Warp 4 FixPak XR_M010
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.
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:
New Function 26
February 26, 1999 - Warp 4 FixPak XR_M010
■ 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.RMS Using the new Removable Media Support
README.DBG Tips on debugging OS/2 Warp and details on the latest
Serviceability (RAS) Enhancements (3.0 and 4.0).
New Function 27
February 26, 1999 - Warp 4 FixPak XR_M010
6.0 CORRECTIVE SERVICE FACILITY
6.0.1 REQUIRED CSF LEVEL
You should use release level F.140 or later of the OS/2 Corrective
Service Facility to install this FixPak.
Bootable diskettes are no longer provided starting with the F.138B CSF
build. Instead, you now get a self-extracting ZIP file which contains the
following:
archctl.cmd
build.lvl
csfpans.dll
filefix.dll
fpinst.cmd
fservice.exe
fservice.msg
ibmcsflk.dll
ibmcsflk.exe
ibmcsflk.msg
ibmcsflk.sys
msg.dll
nls.dll
pack.exe
read.me
readme.inf
response.lan
response.wp3
response.wp4
service.exe
service.hlp
shpiinst.dll
unpack.exe
unpack2.exe
viocalls.dll
Follow the directions in the READ.ME file to use the new CSF code. It
covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
from one of several alternative boot methods.
6.0.2 WHERE YOU CAN FIND CSF CODE
The Corrective Service Facility code is available from many places,
including, but not limited to, the following:
Source How to access
Corrective Service Facility 28
February 26, 1999 - Warp 4 FixPak XR_M010
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_M010.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_M010
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through 35.
Examples:
XR_M010.ADK = 10
XR_M010.FDK = 15
XR_M010.LDK = 21
etc.
6.1 RESIDUAL FIXPAK FILES FROM OS/2 2.11 OR WARP 3
If the following is true:
1. You upgraded your system from OS/2 2.11 or Warp 3
2. You applied one or more FixPaks to the previous system
3. You HAVE NOT applied a Warp 4 FixPak
Corrective Service Facility 29
February 26, 1999 - Warp 4 FixPak XR_M010
You will have files and directories left on your harddisk that will cause
problems when installing a Warp 4 FixPak.
To prevent these problems from occurring, do the following before
applying your first Warp 4 FixPak.
On your Warp 4 boot drive:
■ Delete \OS2\INSTALL\LOGF0000.OS2
■ ATTRIB -R \OS2\INSTALL\LOGSTART.OS2
■ Delete \OS2\INSTALL\LOGSTART.OS2
On the drive where Multimedia Presentation Manager is installed:
Note: This can be your Warp 4 boot drive or any other drive on your
system. Check the "SET MMBASE=" statement in CONFIG.SYS to determine
which drive this is.
■ Delete \MMOS2\INSTALL\LOGF0000.MPM
■ ATTRIB -R \MMOS2\INSTALL\LOGSTART.MPM
■ Delete \MMOS2\INSTALL\LOGSTART.MPM
Remove the old Archive and Backup directories and SERVICE.LOG file to
recover the space they are using.
You should also remove the FixPak Archive and Backup directories left
over from your updated OS/2 2.11 or Warp 3 system at this time as well as
the \OS2\INSTALL\SERVICE.LOG file.
6.2 READ-ONLY FILES
Some files being updated by this FixPak may have the Read-Only attribute
set. If you are using the A:SERVICE method to install this FixPak you
will be asked if you want the files replaced.
Press the "OK" button.
6.3 SYSLEVEL FILE LOCATIONS
This FixPak will service directories based on the location of a supported
SYSLEVEL.OS2 file. Please check your system to make sure extra copies of
this file are not located in directories other than:
\OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)
If additional copies of these files are found in other locations on your
hard disk then CSF will try to service files as follows:
Corrective Service Facility 30
February 26, 1999 - Warp 4 FixPak XR_M010
For \OS2\INSTALL\SYSLEVEL.OS2
..\..\ all files in a directory two levels above (toward the
root). This should be the root directory of your boot
drive.
..\* all files in a directory one level above (toward the root)
and all subdirectories below. This should be the OS2
directory and subdirectories.
..\..\VT\* all files in the VT directory and subdirectories.
..\..\PSFONTS\* all files in the PSFONTS directory and subdirectories.
..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories.
..\..\OPENDOC\* all files in the OPENDOC directory and subdirectories.
6.4 RELOCATED OS/2 FILE SUPPORT
If you have moved OS/2 files or directories to a drive other than the one
the SYSLEVEL.OS2 file is on, do the following in order to have them
serviced:
■ Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
OS\2 Warp 4 partition to be serviced.
In this file, place the full path to the directories you want to be
serviced. Assuming your boot drive is C: and you installed Multimedia
on the D: drive and manually moved WINOS2 support to the E: drive:
Corrective Service Facility 31
February 26, 1999 - Warp 4 FixPak XR_M010
D:\MMOS2
D:\MMOS2\DLL
D:\MMOS2\DSP
D:\MMOS2\HELP
D:\MMOS2\IMAGES
D:\MMOS2\INETTEMP
D:\MMOS2\INSTALL
D:\MMOS2\MACROS
D:\MMOS2\MOVIES
D:\MMOS2\SOUNDS
D:\MMOS2\SOUNDS\DESKTOP
D:\MMOS2\SOUNDS\GARDEN
D:\MMOS2\SOUNDS\OCEAN
D:\MMOS2\SOUNDS\SPACE
E:\OS2\MDOS\WINOS2
E:\OS2\MDOS\WINOS2\SYSTEM
E:\OS2\MDOS\WINOS2\TEMP
Note: Leave this file for any future OS/2 Warp 4 FixPaks you might apply.
The easy way to create this file is to use the DIR command with the /A:D
/S /B parameters and pipe the output to a file.
dir d:\mmos2 /a:d /s /b > anyfile
Then copy that data into the USERDIRS.OS2 file.
With CSF release level F.137B or later, you can use wildcards, so your
USERDIRS.OS2 file would be much simpler and would look like:
D:\MMOS2\*
E:\OS2\MDOS\WINOS2\*
Corrective Service Facility 32
February 26, 1999 - Warp 4 FixPak XR_M010
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.
Follow the instructions in the READ.ME file that comes in the CS_139.EXE
self-extracting zip file. This explains how to use the CS_139.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_M010
Corrective Service Diskette 1 in drive A. Repeat for the rest of the
FixPak disks when requested to do so.
It can take a considerable length of time for the Corrective Service
Facility to scan your hard disk for serviceable files. In some cases, it
has taken as long as 40 minutes. Please be patient and allow this
process to complete.
If this is the first OS/2 Warp FixPak you have applied to this system,
then enter the path to the directory where a copy of replaced files will
be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)
Note: This ARCHIVE directory is not related to the ARCHIVES directory
built into OS/2 Warp 3 and Warp 4. Please specify a different path. You
must specify a different ARCHIVE directory for each product to be
serviced.
Installation Process 33
February 26, 1999 - Warp 4 FixPak XR_M010
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
Follow the instructions in the READ.ME file that comes in the CS_139.EXE
self-extracting zip file. This explains how to use the CS_139.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Here are some additional notes:
Installation Process 34
February 26, 1999 - Warp 4 FixPak XR_M010
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_139.EXE.
7.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility, like how to
backout a FixPak, is available from the README.INF file on the first
Corrective Service Facility disk. To view this file, place CSF disk 1 in
drive A and enter VIEW A:\README.INF.
There is also some additional information in the READ.ME file.
7.5 FIXPAKS ON CD-ROM
Both the IBM Technical Connection and the IBM Developer Connection
contain the latest OS/2 and LAN FixPaks that were available at publishing
time.
The IBM Technical Connection homepage on the World Wide Web is located
at:
■ http://www.ibm.com/Support/techconn/index.htm
The IBM Developer Connection homepage on the World Wide Web is located
at:
■ http://www.developer.ibm.com/devcon/titlepg.htm
Check these WWW sites for content and ordering information.
Installation Process 35
February 26, 1999 - Warp 4 FixPak XR_M010
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.034
The first page of this document has a line that looks like:
Build Level: n.nnn
CSD level of SYSLEVEL.OS2 36
February 26, 1999 - Warp 4 FixPak XR_M010
That is the number you should see for this FixPak when you issue the VER
/R command.
8.0.1 NEW SYSLEVEL.FPK
A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning with
XR_M004. It is titled "OS/2 Warp 4 Service Level". It contains the name
of the currently installed FixPak in both the Current and Previous CSD
level fields and is located in the same directory the SYSLEVEL.OS2 file
is located in which should be \OS2\INSTALL.
The easiest way to look at SYSLEVEL information is to use the SYSLEVEL
command and redirect the output to a file then edit the file and search
for SYSLEVEL.FPK.
CSD level of SYSLEVEL.OS2 37
February 26, 1999 - Warp 4 FixPak XR_M010
9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 9.034
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M010_ (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_M010_ (Country = Generic)
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\*
Will create the following directories
..\..\OS2 Stub File: @OS2DIR
..\..\OS2\DLL Stub File: @DLLDIR
..\..\OS2\BOOT Stub File: @BOOTDIR
..\..\OS2\SYSTEM Stub File: @SYSTDIR
..\..\OS2\INSTALL Stub File: @INSTDIR
..\..\OS2\SYSTEM\RAS Stub File: @RASDIR
..\..\OS2\SYSTEM\TRACE Stub File: @TRACDIR
Files contained in Fixpak for product:
FixPak Corrective Service levels and disk layouts 38
February 26, 1999 - Warp 4 FixPak XR_M010
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
AHA152X.ADD AHA152X.AD_ 15 02/09/1998 11:38 44208 E689E8A8
AHA164X.ADD AHA164X.AD_ 16 02/09/1998 11:38 20022 F1D90301
AHA6360.SNP AHA6360.SN_ 15 02/09/1998 12:20 27395 920536ED
AIC7770.ADD AIC7770.AD_ 15 02/09/1998 11:39 42558 FA9ADDF2
AIC7870.ADD AIC7870.AD_ 12 10/27/1998 14:59 134280 80A45603
AIC7870.SNP AIC7870.SN_ 16 02/09/1998 12:21 9104 0607EAB1
APM.SYS APM.SY_ 16 02/06/1998 11:55 11412 ABDDF37B
APMDAEMN.EXE APMDAEMN.EX_ 17 02/09/1998 12:52 2733 E39B04BD
ART.DLL ART.DL_ 9 06/17/1997 10:15 202952 117CE534
ART.HLP ART.HL_ 16 04/18/1997 16:16 11980 173C6284
ARTADMIN.EXE ARTADMIN.EX_ 13 06/17/1997 10:15 78693 F298CC78
ARTCHRON.EXE ARTCHRON.EX_ 14 07/25/1997 10:01 58994 B82B9F52
ARTFI.EXE ARTFI.EX_ 14 06/17/1997 10:15 61482 973E97DC
ARTFIR.DLL ARTFIR.DL_ 16 01/16/1998 16:06 30614 41654982
ARTINET.DLL ARTINET.DL_ 13 06/17/1997 10:15 66252 2D5C4592
ARTR.DLL ARTR.DL_ 14 01/16/1998 16:06 80629 BD96A723
ARTREG.EXE ARTREG.EX_ 14 06/17/1997 10:15 66193 A0DDFAF6
ARTREGR.DLL ARTREGR.DL_ 15 01/16/1998 16:06 38138 F3FDF3E4
ARTSTART.DLL ARTSTART.DL_ 16 11/12/1996 13:43 17419 00C5D48F
ASIACOL.DLL ASIACOL.DL_ 10 11/20/1998 08:51 158732 FF2F61DF
AVIO.DLL AVIO.DL_ 14 02/03/1999 11:26 53923 811D0F32
BDIME.DLL BDIME.DL_ 16 05/11/1998 10:32 11879 0F2776DF
BE.KBL BE.KB_ 17 11/20/1998 08:49 972 1F09D05C
BLDLEVEL.EXE BLDLEVEL.EX_ 14 09/15/1998 11:32 43974 F7F6BF98
BOOTDISK.EXE BOOTDISK.EX_ 14 09/25/1998 11:44 60941 49697218
BOOTDISK.HLP BOOTDISK.HL_ 16 09/25/1998 11:44 10892 C5042F09
BSAUDIO.SNP BSAUDIO.SN_ 16 02/09/1998 12:22 5756 5EEF7C9C
BTSCSI.ADD BTSCSI.AD_ 16 02/09/1998 11:41 26569 F7C7B49D
BVSCALLS.DLL BVSCALLS.DL_ 17 09/25/1998 11:52 512 40ADC2D3
BY.KBL BY.KB_ 17 11/20/1998 08:49 1292 8B2B47A4
CA.KBL CA.KB_ 17 11/20/1998 08:49 1214 94F4C78C
CACHE.EXE CACHE.EX_ 16 02/05/1999 16:40 11820 41A72C12
CARDINFO.DAT CARDINFO.DA_ 16 02/02/1999 19:41 54979 4547DDFE
CDFS.IFS CDFS.IF_ 15 02/16/1999 11:39 45173 A5526592
CDFS.TDF CDFS.TD_ 17 02/16/1999 11:39 2113 7EF25B0C
CDROM.TBL CDROM.TB_ 17 11/12/1996 13:38 4365 F3986660
CF.KBL CF.KB_ 17 11/20/1998 08:49 956 0F6A5C3E
CHKDSK.COM CHKDSK.CO_ 14 02/10/1999 13:15 70208 F62FDC55
CHKDSK.SYS CHKDSK.SY_ 17 11/23/1998 17:28 747 11F5A9C8
CHKDSK32.DLL CHKDSK32.DL_ 5 11/23/1998 17:37 121895 6374152A
CHKDSK32.EXE CHKDSK32.EX_ 16 02/05/1999 16:41 6417 426A7C60
CLOCK01.SYS CLOCK01.SY_ 16 04/27/1998 17:07 4400 479AB13E
CLOCK02.SYS CLOCK02.SY_ 16 06/12/1998 20:10 4282 55DA0EE4
CMD.EXE CMD.EX_ 13 01/22/1999 16:10 74300 891E18AF
CMPXCHG8.SYS CMPXCHG8.SY_ 17 01/23/1998 17:03 2634 F00F9D02
COM.SYS COM.SY_ 16 02/09/1998 11:48 18799 E9C4799B
COMM.DRV COMM.DR_ 16 01/28/1999 10:27 9552 23F635F2
COMMAND.COM COMMAND.CO_ 15 02/05/1999 16:30 53375 8B564A37
FixPak Corrective Service levels and disk layouts 39
February 26, 1999 - Warp 4 FixPak XR_M010
CONTROL.PM CONTROL.PM_ 17 05/05/1998 01:48 8474 87121A82
COUNTRY.SYS COUNTRY.SY_ 16 01/08/1998 11:31 38803 F14B8597
COUR.OFM COUR.OF_ 17 01/07/1998 23:34 4236 62B4251D
COUR.PFB COUR.PF_ 11 01/07/1998 23:34 112702 F47DEC19
COUR.PFM COU1.PF_ 17 01/07/1998 23:34 674 EBCD0968
COURB.OFM COURB.OF_ 17 01/07/1998 23:34 4246 78B1D3EA
COURB.PFB COURB.PF_ 10 01/07/1998 23:34 116938 3F227222
COURB.PFM COUR1.PF_ 17 01/07/1998 23:34 679 1EFB356B
COURBI.OFM COURBI.OF_ 17 01/07/1998 23:34 4260 BC9E6AF3
COURBI.PFB COURBI.PF_ 10 01/07/1998 23:34 112484 88CD4829
COURBI.PFM COURB1.PF_ 17 01/07/1998 23:34 685 D0390E4C
COURI.OFM COURI.OF_ 17 01/07/1998 23:34 4251 4E97A3B8
COURI.PFB COURI.PF_ 10 01/07/1998 23:34 113244 4A250D0F
COURI.PFM COUR2.PF_ 17 01/07/1998 23:34 681 A6EECE02
COURIER.FON COURIER.FO_ 15 01/16/1998 17:56 104183 CDD08B00
CREX.MSG CREX.MS_ 17 09/19/1996 15:44 2865 84FD8E0E
CREXUTIL.DLL CREXUTIL.DL_ 14 11/20/1998 15:58 49229 1FDA62DB
CREXX.DLL CREXX2.DL_ 10 12/16/1997 13:09 266047 3474118E
CZ.KBL CZ.KB_ 17 11/20/1998 08:49 1014 92C25A83
DDINSTAL.EXE DDINSTAL.EX_ 15 11/23/1998 17:05 34855 F287DA96
DE.KBL DE.KB_ 17 11/20/1998 08:49 958 D7677506
DE453.KBL DE453.KB_ 17 11/20/1998 08:49 1354 A23A055E
DETNE2.SYS DETNE2.SY_ 16 02/09/1998 11:33 5658 8519BFB1
DF_DEB.EXE DF_DEB.EX_ 12 02/10/1999 13:14 135921 41D4478D
DF_RET.EXE DF_RET.EX_ 12 02/10/1999 13:14 136177 283A50AB
DIBDRVR.DLL DIBDRVR.DL_ 17 10/22/1997 23:20 2267 1429B4B2
DICTATE.EXE DICTATE.EX_ 14 05/06/1998 11:58 51391 45FFC0F4
DICTDLL.DLL DICTDLL.DL_ 14 12/21/1997 01:28 51187 CF8D71CA
DISPLAY.DLL DISPLAY.DL_ 14 10/27/1998 11:37 46574 A8555B05
DIVE.DLL DIVE.DL_ 13 09/29/1998 16:01 69640 C06FD486
DK.KBL DK.KB_ 17 11/20/1998 08:49 928 4CBC25D4
DMQSPROF.DLL DMQSPROF.DL_ 14 08/05/1998 16:46 43533 624785C7
DOSCALL1.DLL DOSCALL1.DL_ 11 02/16/1999 11:41 124438 67CC2EBF
DOSCALL1.SYM DOSCALL1.SY_ 15 02/16/1999 11:41 41716 833006F2
DOSCALL1.TDF DOSCALL1.TD_ 17 02/16/1999 11:41 5426 6264F7F6
DOSKRNL DOSKRNL.___ 15 02/16/1999 11:39 30569 09362CCC
DRVMAP.INF DRVMAP.IN_ 17 04/03/1997 13:54 12986 0AD62B34
DSPINSTL.EXE DSPINSTL.EX_ 12 11/23/1998 17:13 117816 6C4B4277
DSPRES.DLL DSPRES1.DL_ 9 01/16/1998 17:54 411990 4A5373A5
DSPRES.DLL DSPRES.DL_ 9 01/16/1998 17:54 411990 4A5373A5
DTRACE.DOC DTRACE.DO_ 15 12/02/1998 16:29 75371 A0765F8C
DTRACE.EXE DTRACE.EX_ 14 02/16/1999 10:15 48906 D9D70598
E.EXE E.EX_ 13 02/05/1999 17:14 61719 776A77E6
EAUTIL.EXE EAUTIL.EX_ 15 02/10/1999 13:15 37984 EF8EBB0B
EJECT.EXE EJECT.EX_ 15 01/09/1998 16:20 25648 CC9E0C0E
EL.KBL EL.KB_ 17 11/20/1998 08:49 1396 58F9CB76
EL459.KBL EL459.KB_ 17 11/20/1998 08:49 1372 29C6E702
ENGINE.EXE ENGINE.EX_ 6 07/23/1997 11:39 440424 C247CBAA
EPM.EXE EPM.EX_ 16 07/16/1998 13:18 19684 E6ED87A9
ERLOGGER.EXE ERLOGGER.EX_ 15 02/05/1999 16:23 34320 1AAB428F
ERRLOG.DLL ERRLOG.DL_ 13 02/05/1999 16:23 72594 6B4602A5
FixPak Corrective Service levels and disk layouts 40
February 26, 1999 - Warp 4 FixPak XR_M010
ES.KBL ES.KB_ 17 11/20/1998 08:49 920 D85665CF
ETKC603.DLL ETKC603.DL_ 11 12/16/1997 15:06 135759 6AF203C2
ETKE603.DLL ETKE603.DL_ 5 05/07/1998 09:10 754050 D31F92AF
FD16-700.ADD FD16-700.AD_ 15 02/26/1998 13:57 34152 BF036884
FD7000EX.ADD FD7000EX.AD_ 16 02/09/1998 11:40 20758 EA0548BD
FD8XX.ADD FD8XX.AD_ 16 02/09/1998 11:40 29954 9C40E49E
FDISK.COM FDISK.CO_ 13 02/10/1999 13:19 114218 6D1C2E0F
FDISKPM.DLL FDISKPM.DL_ 16 01/26/1999 14:22 7731 6B64272C
FDISKPM.EXE FDISKPM.EX_ 13 02/10/1999 13:20 63042 DF89D81C
FFST.DLL FFST.DL_ 16 04/03/1997 19:03 11425 C6365786
FFSTCONF.EXE FFSTCONF.EX_ 13 02/05/1999 16:25 68669 6DC63C77
FFSTPCT.EXE FFSTPCT.EX_ 13 02/05/1999 16:25 69583 194DAAD9
FI.KBL FI.KB_ 17 11/20/1998 08:49 940 15C2FCE6
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 02/10/1999 13:16 69920 F12D91CE
FR.KBL FR.KB_ 17 11/20/1998 08:49 950 63AB1939
FSFILTER.SYS FSFILTER.SY_ 16 02/16/1999 11:42 12988 087EEDA3
GDI.EXE GDI.EX_ 9 01/28/1999 08:45 225744 D54CFFD9
GRADD.SYS GRADD.SY_ 17 10/16/1997 18:49 1195 127C007B
GRE2VMAN.DLL GRE2VMAN.DL_ 16 10/27/1998 11:47 17899 7541571C
HDMON.EXE HDMON.EX_ 13 01/22/1999 11:50 75043 7A10FC57
HELPMGR.DLL HELPMGR.DL_ 8 01/22/1999 12:18 249825 EF3821E8
HELPMSG.EXE HELPMSG.EX_ 15 02/10/1999 13:16 36256 F2B8CA00
HELV.FON HELV.FO_ 12 01/16/1998 17:56 264425 4A47AFF3
HELV.OFM HELV.OF_ 16 05/06/1998 16:34 4865 81A5D22A
HELV.PFB HELV.PF_ 11 05/06/1998 16:34 101942 3F1961BC
HELV.PFM HEL1.PF_ 17 05/06/1998 16:34 1096 C72298C9
HELVB.OFM HELVB.OF_ 16 05/06/1998 16:34 4857 0F9226BE
HELVB.PFB HELVB.PF_ 11 05/06/1998 16:34 104404 D2D90EE1
HELVB.PFM HELV1.PF_ 17 05/06/1998 16:34 1089 5A484E7D
HELVBI.OFM HELVBI.OF_ 16 05/06/1998 16:34 4859 F812E3EB
HELVBI.PFB HELVBI.PF_ 11 05/06/1998 16:34 105074 CF169E28
HELVBI.PFM HELVB1.PF_ 17 05/06/1998 16:34 1087 06A2ED9D
HELVI.OFM HELVI.OF_ 16 05/06/1998 16:34 4844 A99A0D2F
HELVI.PFB HELVI.PF_ 11 05/06/1998 16:34 103996 D3AF0069
HELVI.PFM HELV2.PF_ 17 05/06/1998 16:34 1079 4D475EBC
HPFS.IFS HPFS.IF_ 12 02/05/1999 16:39 141378 63D8606E
HPFS.TDF HPFS.TD_ 17 02/05/1999 16:39 1620 C6DBB891
HR.KBL HR.KB_ 17 11/20/1998 08:49 982 098EA38D
HU.KBL HU.KB_ 17 11/20/1998 08:49 1006 70245E54
IBM1004 IBM1004.___ 17 11/20/1998 08:47 3552 6026EE1E
IBM1125 IBM1125.___ 17 11/20/1998 08:47 4320 C4D5BAAA
IBM1131 IBM1131.___ 17 11/20/1998 08:47 4320 37809FFA
IBM1250 IBM1250.___ 17 11/20/1998 08:47 3552 9678BAA0
IBM1251 IBM1251.___ 17 11/20/1998 08:47 3296 88C0CF17
IBM1252 IBM1252.___ 17 11/20/1998 08:47 3552 F6DA0EE3
IBM1253 IBM1253.___ 17 11/20/1998 08:47 3552 5A9A97EA
IBM1254 IBM1254.___ 17 11/20/1998 08:47 3552 26986E3C
IBM1255 IBM1255.___ 17 11/20/1998 08:47 3808 95EA9EF3
IBM1256 IBM1256.___ 17 11/20/1998 08:47 3808 192A19BE
FixPak Corrective Service levels and disk layouts 41
February 26, 1999 - Warp 4 FixPak XR_M010
IBM1257 IBM1257.___ 17 11/20/1998 08:47 3296 6F4C235A
IBM16AFS.EXE IBM16AFS.EX_ 17 02/26/1998 13:59 3177 CA09DDE5
IBM1FLPY.ADD IBM1FLPY.AD_ 15 06/12/1998 18:21 35450 468D7BE6
IBM1S506.ADD IBM1S506.AD_ 14 11/18/1998 18:56 54158 E0EA5086
IBM2AMB1.SYS IBM2AMB1.SY_ 16 02/26/1998 14:20 12453 82179E90
IBM2AST1.SYS IBM2AST1.SY_ 16 02/26/1998 14:19 10047 E1649391
IBM2CAD1.SYS IBM2CAD1.SY_ 16 02/26/1998 14:22 12495 D2A09CCB
IBM2CMQ1.SYS IBM2CMQ1.SY_ 16 02/26/1998 14:20 10101 4FFCC5CA
IBM2FLPY.ADD IBM2FLPY.AD_ 16 02/09/1998 11:36 14420 9E1E4F1E
IBM2MAT1.SYS IBM2MAT1.SY_ 16 02/26/1998 14:21 10083 B17AB7AA
IBM2NCR1.SYS IBM2NCR1.SY_ 16 02/26/1998 14:21 10063 CFA9832E
IBM2NEC1.SYS IBM2NEC1.SY_ 16 02/26/1998 14:20 10063 F1CBCAF0
IBM2SCSI.ADD IBM2SCSI.AD_ 16 09/19/1998 13:02 33145 2CCFE16B
IBM2SS01.SYS IBM2SS01.SY_ 16 02/26/1998 15:05 27102 A306DE47
IBM2SS02.SYS IBM2SS02.SY_ 16 02/26/1998 15:05 22835 37DA88EE
IBM2TOS1.SYS IBM2TOS1.SY_ 16 02/26/1998 14:19 10054 C4A26E3D
IBM2ZEN1.SYS IBM2ZEN1.SY_ 16 02/26/1998 14:19 10047 E5F235D0
IBM2ZOS1.SYS IBM2ZOS1.SY_ 16 02/26/1998 14:21 10079 2442A8C9
IBM4612.SYS IBM4612.SY_ 16 02/26/1998 14:22 10180 EC2E20A4
IBM850 IBM850.___ 17 11/20/1998 08:47 4320 9AFAAE55
IBM857 IBM857.___ 17 11/20/1998 08:47 4320 3A7C727E
IBMATAPI.FLT IBMATAPI.FL_ 16 06/12/1998 20:37 30436 CF36B890
IBMIDECD.FLT IBMIDECD.FL_ 16 09/30/1998 21:14 24136 DA6F6C51
IBMKBD.SYS IBMKBD.SY_ 16 08/07/1998 14:22 7834 A8D4A166
IBMOPTNS.DLL IBMOPTNS.DL_ 16 02/02/1999 19:41 18744 DAD5DB97
ICMEMCDD.SYS ICMEMCDD.SY_ 16 02/26/1998 14:24 13932 9ACEB1BD
ICMEMFMT.EXE ICMEMFMT.EX_ 15 02/26/1998 14:26 44276 785B0ADE
ICMEMMTD.SYS ICMEMMTD.SY_ 16 02/26/1998 14:25 7788 F0695871
ICONEDIT.EXE ICONEDIT.EX_ 12 07/23/1998 16:08 109504 5761E8A9
IFGDI2VM.DRV IFGDI2VM.DR_ 14 10/27/1998 11:46 91464 7AA45953
INST_DOS.EXE INST_DOS.EX_ 14 12/04/1998 17:34 36466 EDCF1A16
INSTALL.EXE INSTALL.EX_ 6 01/22/1999 16:35 384536 F08E4A48
IOPROC.DLL IOPROC.DL_ 15 02/03/1999 11:27 37878 1CD1DBA1
IPSRAID.ADD IPSRAID.AD_ 16 10/20/1998 09:53 19990 81E1EA12
IS.KBL IS.KB_ 17 11/20/1998 08:49 940 33135410
IS458.KBL IS458.KB_ 17 11/20/1998 08:49 928 50090566
ISGDI2VM.DRV ISGDI2VM.DR_ 7 10/27/1998 11:45 90144 83F46A5E
IT.KBL IT.KB_ 17 11/20/1998 08:49 876 EA80500B
IT142.KBL IT142.KB_ 17 11/20/1998 08:49 854 1289EE05
KBDBASE.SYS KBDBASE.SY_ 16 08/07/1998 14:26 31061 00AC4300
KERNEL.SDF KERNEL.SD_ 15 11/07/1996 21:11 467330 E94C86A0
KERNELD.SDF KERNELD.SD_ 15 11/07/1996 21:12 468657 3CC5754F
KEYBOARD.DCP KEYBOARD.DC_ 15 01/28/1999 17:28 307393 A2F8222F
KRNLBDEV.TDF KRNLBDEV.TD_ 17 02/10/1999 13:06 3703 DFA93591
KRNLBFS.TDF KRNLBFS.TD_ 17 02/10/1999 13:06 4464 A14B7834
KRNLBLDR.TDF KRNLBLDR.TD_ 17 02/10/1999 13:07 5581 5835C7D4
KRNLBPG.TDF KRNLBPG.TD_ 17 02/10/1999 13:07 3203 BE1E32A4
KRNLBSEL.TDF KRNLBSEL.TD_ 17 02/10/1999 13:07 2727 F38470A2
KRNLBSEM.TDF KRNLBSEM.TD_ 17 02/10/1999 13:07 1792 30DB3422
KRNLBSM.TDF KRNLBSM.TD_ 17 02/10/1999 13:07 1321 02863E74
KRNLBTK.TDF KRNLBTK.TD_ 16 02/10/1999 13:07 14388 71D3B7F0
FixPak Corrective Service levels and disk layouts 42
February 26, 1999 - Warp 4 FixPak XR_M010
KRNLBTOM.TDF KRNLBTOM.TD_ 17 02/10/1999 13:07 925 7AAF6EC2
KRNLBVDM.TDF KRNLBVDM.TD_ 16 02/10/1999 13:06 13917 4BAC54BB
KRNLBVM.TDF KRNLBVM.TD_ 17 02/10/1999 13:07 5514 5D4D7584
KRNLDDEV.TDF KRNLDDEV.TD_ 17 02/10/1999 13:10 3678 B6211702
KRNLDFS.TDF KRNLDFS.TD_ 17 02/10/1999 13:10 4355 0BB40DF7
KRNLDLDR.TDF KRNLDLDR.TD_ 17 02/10/1999 13:10 5609 71CA2F4C
KRNLDPG.TDF KRNLDPG.TD_ 17 02/10/1999 13:10 3284 C44BA732
KRNLDSEL.TDF KRNLDSEL.TD_ 17 02/10/1999 13:10 2814 C74617DF
KRNLDSEM.TDF KRNLDSEM.TD_ 17 02/10/1999 13:10 1932 02AC9714
KRNLDSM.TDF KRNLDSM.TD_ 17 02/10/1999 13:10 1321 1D778C2C
KRNLDTK.TDF KRNLDTK.TD_ 16 02/10/1999 13:10 14419 6AA2017B
KRNLDTOM.TDF KRNLDTOM.TD_ 17 02/10/1999 13:11 953 AAC496BF
KRNLDVDM.TDF KRNLDVDM.TD_ 16 02/10/1999 13:10 13992 0D59E08D
KRNLDVM.TDF KRNLDVM.TD_ 17 02/10/1999 13:10 5601 91DBFD53
KRNLRDEV.TDF KRNLRDEV.TD_ 17 02/10/1999 13:05 3703 DBFF60B7
KRNLRFS.TDF KRNLRFS.TD_ 17 02/10/1999 13:05 4464 34F32659
KRNLRLDR.TDF KRNLRLDR.TD_ 17 02/10/1999 13:05 5581 EE58EFAA
KRNLRPG.TDF KRNLRPG.TD_ 17 02/10/1999 13:05 3203 DD2C7921
KRNLRSEL.TDF KRNLRSEL.TD_ 17 02/10/1999 13:05 2727 BD6280F0
KRNLRSEM.TDF KRNLRSEM.TD_ 17 02/10/1999 13:05 1792 C89B88A7
KRNLRSM.TDF KRNLRSM.TD_ 17 02/10/1999 13:05 1321 9274A9AD
KRNLRTK.TDF KRNLRTK.TD_ 16 02/10/1999 13:05 14304 152389B5
KRNLRTOM.TDF KRNLRTOM.TD_ 17 02/10/1999 13:05 897 891C8EEE
KRNLRVDM.TDF KRNLRVDM.TD_ 16 02/10/1999 13:05 13749 899FC9A9
KRNLRVM.TDF KRNLRVM.TD_ 17 02/10/1999 13:05 5514 0E59290E
LIBCM.DLL LIBCM.DL_ 9 05/05/1998 18:21 210916 B8DAC35A
LIBCN.DLL LIBCN.DL_ 14 05/05/1998 18:21 57340 0C3E3107
LIBCS.DLL LIBCS.DL_ 9 05/05/1998 18:21 192386 978ECF1F
LIBUNI.DLL LIBUNI.DL_ 13 01/28/1999 16:11 81144 459C5C42
LMS206.ADD LMS206.AD_ 15 02/09/1998 11:46 38706 6FE51860
LOCALE.DLL LOCALE.DL_ 12 01/28/1999 14:37 100941 BE095926
MAIN.CPL MAIN.CP_ 12 01/28/1999 08:57 147616 1F0EADF8
MAPTSF.CMD MAPTSF.CM_ 16 12/02/1998 16:25 16633 6A805CF2
MIDI.SYS MIDI.SY_ 16 02/06/1998 12:48 21834 F826CD08
MIDIMCD.DLL MIDIMCD.DL_ 17 09/29/1998 16:02 532 40B1F3FB
MIGRATE.EXE MIGRATE.EX_ 11 01/22/1999 16:49 118313 CAC0050D
MINSTALL.EXE MINSTALL.EX_ 9 02/02/1999 19:41 152580 84E992F2
MINXOBJ.DLL MINXOBJ.DL_ 15 02/05/1999 16:54 31778 80E6E4FC
MIRRORS.DLL MIRRORS.DL_ 7 09/19/1996 15:53 444744 4D936F0C
MITFX001.ADD MITFX001.AD_ 16 02/09/1998 11:44 20492 4A654D4D
MMODPTS.DLL MMODPTS.DL_ 3 09/29/1998 14:42 184020 4C87AB95
MMPARTS.DLL MMPARTS.DL_ 2 09/29/1998 16:13 1532250 AA3EBDC4
MMPM.DLL MMPM.DL_ 7 02/02/1999 19:46 431781 5F4F04BD
MMSOUND.DRV MMSOUND.DR_ 16 01/28/1999 09:13 3456 97C92E30
MONCALLS.DLL MONCALLS.DL_ 17 11/23/1998 16:44 2472 45E0839F
MONCALLS.TDF MONCALLS.TD_ 17 11/23/1998 16:44 1139 6AB1D73C
MOUSE.SYS MOUSE.SY_ 16 07/24/1998 15:09 19587 E12C806A
MPGIO.DLL MPGIO.DL_ 13 02/03/1999 11:27 59267 4C29334D
NAMEADD.EXE NAMEADD.EX_ 16 11/20/1998 08:41 23040 377F09A2
NAMECOPY.EXE NAMECOPY.EX_ 16 11/20/1998 08:41 23040 18B5214E
NAMECSSP.DLL NAMECSSP.DL_ 13 10/28/1997 13:00 61155 A8FF5283
FixPak Corrective Service levels and disk layouts 43
February 26, 1999 - Warp 4 FixPak XR_M010
NAMEDEL.EXE NAMEDEL.EX_ 16 11/20/1998 08:41 23040 5F2869A3
NAMEDSP.DLL NAMEDSP.DL_ 11 10/28/1997 13:00 123411 2EF315D9
NAMEEXT.EXE NAMEEXT.EX_ 16 11/20/1998 08:41 23040 972869A5
NAMEFT.DLL NAMEFT.DL_ 13 10/28/1997 13:00 66306 76F89339
NAMEFW.DLL NAMEFW.DL_ 13 10/28/1997 13:00 72312 9A504B37
NAMEINFO.DLL NAMEINFO.DL_ 14 10/28/1997 13:00 47941 A05DAC90
NAMEINI.DLL NAMEINI.DL_ 13 10/28/1997 13:00 59011 34E2CDED
NAMEMOD.EXE NAMEMOD.EX_ 16 11/20/1998 08:41 23040 472869A3
NAMEMOVE.EXE NAMEMOVE.EX_ 16 11/20/1998 08:41 23040 20B5214C
NAMEOSP.DLL NAMEOSP.DL_ 14 10/28/1997 13:00 52725 F9AB278A
NL.KBL NL.KB_ 17 11/20/1998 08:49 954 BF23F2CD
NO.KBL NO.KB_ 17 11/20/1998 08:49 920 DEEB9347
NWIAPI.DLL NWIAPI.DL_ 16 01/26/1999 09:46 14768 659C9960
OREXUTIL.DLL ORXUTIL2.DL_ 15 11/20/1998 15:58 33725 52F2EC68
OREXX.DLL OREXX2.DL_ 6 11/20/1998 15:58 489013 4BB269FA
OS2ASPI.DMD OS2ASPI.DM_ 16 02/06/1998 12:13 11096 25ADBADF
OS2CDROM.DMD OS2CDROM.DM_ 16 02/09/1998 11:43 27356 97942D46
OS2CHAR.TDF OS2CHAR.TD_ 16 02/16/1999 11:41 13889 3835C652
OS2DASD.DMD OS2DASD.DM_ 15 08/07/1998 12:19 40894 61CB3260
OS2DUMP OS2DUMP.___ 16 01/26/1999 14:11 17369 CE90FE1C
OS2K386.EXE OS2K386.EX_ 13 01/28/1999 08:46 80306 8600D240
OS2KRNL OS2KRNL.___ 3 02/10/1999 13:05 634639 CD8019A2
OS2KRNL.TDF OS2KRNL.TD_ 16 02/10/1999 13:05 16581 13CC42B7
OS2KRNLD.SYM OS2KRNLD.SY_ 11 02/10/1999 13:10 186132 8684DE5A
OS2KRNLR.SYM OS2KRNLR.SY_ 12 02/10/1999 13:05 163284 DFC7E45E
OS2LDR.MSG OS2LDR.MS_ 16 12/04/1998 17:56 8368 DF472A34
OS2MM.DLL OS2MM.DL_ 8 02/02/1999 19:41 219650 AD788CD4
OS2NS.EXE OS2NS.EX_ 14 10/28/1997 14:18 44964 C6014916
OS2SCSI.DMD OS2SCSI.DM_ 16 08/07/1998 12:20 11606 966E22D3
OS2UGL OS2UGL.___ 16 01/28/1999 14:37 15616 70598C8E
OS2UGLG OS2UGLG.___ 17 12/12/1997 22:59 8928 AA89831E
OSO001.MSG OSO001.MS_ 13 01/21/1999 15:08 179413 699961EA
OSO001H.MSG OSO001H.MS_ 12 01/21/1999 15:08 241617 3EFA6913
PARALLEL.PDR PARALLEL.PD_ 12 12/03/1998 18:03 15848 04549DA7
PCIBUS.SNP PCIBUS.SN_ 16 02/09/1998 12:17 2496 5BE2AE0B
PCM2ATA.ADD PCM2ATA.AD_ 16 02/26/1998 15:00 27938 DB6FFBDD
PCMCIA.SYS PCMCIA.SY_ 15 02/26/1998 14:58 48646 7537995C
PCMCIA.TBL PCMCIA.TB_ 17 07/24/1998 12:34 5114 8DE2485F
PDUMPSYS.EXE PDUMPSYS.EX_ 15 12/18/1998 09:27 34877 C38B3587
PDUMPUSR.EXE PDUMPUSR.EX_ 15 12/02/1998 16:41 34875 AD697C70
PICV.DLL PICV.DL_ 16 02/08/1999 11:37 26200 CACD75BD
PICVIEW.DLL PICVIEW.DL_ 16 12/16/1997 17:02 10786 B47452C4
PL.KBL PL.KB_ 17 11/20/1998 08:49 980 2D8F5B99
PL457.KBL PL457.KB_ 17 11/20/1998 08:49 882 E5516C13
PMATM.DLL PMATM.DL_ 8 01/22/1999 10:17 223987 8FFB51C9
PMCHKDSK.DLL PMCHKDSK.DL_ 16 11/04/1996 16:44 4127 CE30C1EE
PMCHKDSK.EXE PMCHKDSK.EX_ 15 12/02/1998 17:02 28183 23BC5713
PMCLIP.DLL PMCLIP.DL_ 16 10/22/1997 23:19 21295 2FE91E38
PMCTLS.DLL PMCTLS.DL_ 4 02/04/1999 16:12 584766 3CF8AB5E
PMCTLS.SYM PMCTLS.SY_ 15 02/04/1999 16:12 44084 E5AB57DE
PMDDE.DLL PMDDE.DL_ 15 11/25/1998 14:15 28346 4ABC0A3F
FixPak Corrective Service levels and disk layouts 44
February 26, 1999 - Warp 4 FixPak XR_M010
PMDDEML.DLL PMDDEML.DL_ 15 11/25/1998 13:51 27710 18D45019
PMDF.EXE PMDF.EX_ 7 02/05/1999 16:26 266268 2EB20F1B
PMDFMSG.DLL PMDFMSG.DL_ 14 02/05/1999 16:26 44240 C0BFAB8D
PMDRAG.DLL PMDRAG.DL_ 17 11/25/1998 13:55 1731 686406C9
PMGPI.DLL PMGPI.DL_ 8 01/22/1999 11:57 229162 C75C3EED
PMGPI.TDF PMGPI.TD_ 16 01/22/1999 11:58 12338 09C8F730
PMGRE.DLL PMGRE.DL_ 17 11/25/1998 13:47 2231 AFBE3883
PMGRE.TDF PMGRE.TD_ 17 02/05/1999 18:14 1062 914D0706
PMMERGE.DLL PMMERGE.DL_ 1 02/05/1999 18:15 1237727 88DE3722
PMMERGE.SYM PMMERGE.SY_ 12 02/05/1999 18:14 115348 7BEB0D71
PMMLE.DLL PMMLE.DL_ 17 01/22/1999 12:05 673 E6270A8D
PMPIC.DLL PMPIC.DL_ 14 02/08/1999 11:37 47206 AB409467
PMPIC.TDF PMPIC.TD_ 17 02/08/1999 11:37 400 AAA214FB
PMPRINT.QPR PMPRINT.QP_ 16 11/20/1998 16:50 11833 87E305C4
PMSDMRI.DLL PMSDMRI.DL_ 16 11/25/1998 13:55 13312 214084A4
PMSEEK.EXE PMSEEK.EX_ 15 02/10/1999 13:20 31285 D65F98D9
PMSHAPI.DLL PMSHAPI.DL_ 17 10/22/1997 22:53 4549 7AE93081
PMSHAPI.TDF PMSHAPI.TD_ 17 02/05/1999 18:14 6726 4BB9F713
PMSPL.DLL PMSPL.DL_ 8 01/26/1999 09:45 276521 DA388A43
PMSPL.SYM PMSPL.SY_ 16 01/26/1999 09:45 32244 E88552A9
PMSPL.TDF PMSPL.TD_ 17 01/26/1999 09:45 4491 83259CA3
PMVDMP.DLL PMVDMP.DL_ 14 02/08/1999 12:32 42867 692B60FF
PMVDMP.TDF PMVDMP.TD_ 17 02/08/1999 12:32 2661 AE20E351
PMVIOP.DLL PMVIOP.DL_ 13 02/08/1999 12:32 58958 E97D3478
PMVIOP.SYM PMVIOP.SY_ 16 02/08/1999 12:32 6628 E434FC55
PMVIOP.TDF PMVIOP.TD_ 17 02/08/1999 12:32 3551 C4D85510
PMWIN.DLL PMWIN.DL_ 16 11/25/1998 13:51 11264 AEAD9DA5
PMWIN.TDF PMWIN.TD_ 16 02/05/1999 18:14 9567 AA57A713
PMWIN32.SDF PMWIN32.SD_ 15 10/28/1997 18:56 299617 47F639A5
PMWINX.DLL PMWINX.DL_ 5 11/25/1998 14:13 530279 A67E8650
PMWP.DLL PMWP.DL_ 3 02/05/1999 16:47 926615 D8B4E526
PMWP.SYM PMWP.SY_ 13 02/05/1999 16:47 100420 9D51F96A
PMWP.TDF PMWP.TD_ 16 02/05/1999 16:47 13825 D2CE5690
PMWPMRI.DLL PMWPMRI.DL_ 14 11/20/1998 16:35 54821 AA713643
PNP.DLL PNP.DL_ 15 02/05/1999 17:04 28297 16A4D33F
PNP.SYS PNP.SY_ 17 02/09/1998 12:18 2152 ACA5DFD5
PO.KBL PO.KB_ 17 11/20/1998 08:49 926 7A143859
POINTDD.SYS POINTDD.SY_ 17 02/09/1998 12:14 2823 EAA05B40
PRINT01.SYS PRINT01.SY_ 16 01/06/1998 13:44 12590 60821C55
PRINT02.SYS PRINT02.SY_ 16 12/05/1997 11:31 11766 140600A2
PROCDUMP.DOC PROCDUMP.DO_ 16 02/19/1999 10:29 62765 94EB1E35
PROCDUMP.EXE PROCDUMP.EX_ 14 12/02/1998 16:41 47135 0DE0F2C3
PROGMAN.EXE PROGMAN.EX_ 14 01/28/1999 08:54 115328 93CE0750
PSSDMON.EXE PSSDMON.EX_ 15 01/28/1999 17:59 27565 58DD44F1
PSTAT.EXE PSTAT.EX_ 16 02/10/1999 13:17 11699 A02D0695
QUECALLS.DLL QUECALLS.DL_ 17 09/25/1998 11:51 1024 E01AB550
QUECALLS.TDF QUECALLS.TD_ 17 02/16/1999 11:41 1287 980FA493
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 4938EC49
README.DBG README.DB_ 16 02/15/1999 09:00 22967 CAFE9035
FixPak Corrective Service levels and disk layouts 45
February 26, 1999 - Warp 4 FixPak XR_M010
REGCONV.EXE REGCONV.EX_ 15 01/28/1999 14:32 39446 ED3E9368
REGEDIT.HLP REGEDIT.HL_ 16 01/28/1999 10:31 22682 17F065CD
REGEDIT2.EXE REGEDIT2.EX_ 4 01/28/1999 14:33 950784 99031789
REGISTRY.DLL REGISTRY.DL_ 14 11/20/1998 08:24 81438 9F494BB5
REGISTRY.MSG REGISTRY.MS_ 17 01/28/1999 14:33 629 E72A35BA
REGISTRY.TDF REGISTRY.TD_ 17 11/20/1998 08:24 7591 E2A454D1
REPLACE.EXE REPLACE.EX_ 15 12/02/1998 17:04 37483 8F447F1C
RESERVE.SYS RESERVE.SY_ 16 02/09/1998 11:33 5704 2CA621DA
RESOURCE.SYS RESOURCE.SY_ 15 08/07/1998 12:02 55372 484383D4
RESTORE.EXE RESTORE.EX_ 15 02/10/1999 13:21 36256 BC40F4B3
REX.MSG REX.MS_ 17 09/19/1996 15:44 2865 6725D657
REXX.DLL CREXX1.DL_ 9 12/16/1997 13:09 266047 71D20229
REXX.DLL OREXX1.DL_ 6 11/20/1998 15:58 489013 E0D40871
REXX.IMG REXX.IM_ 13 11/20/1998 15:58 275420 034B1863
REXXAPI.DLL REXXAPI.DL_ 15 07/23/1998 15:54 29603 057F1B73
REXXC.EXE REXXC.EX_ 17 03/31/1997 17:35 1980 EB392AB2
REXXCRT.DLL REXXCRT.DL_ 13 03/31/1997 17:35 61195 D865CF3E
REXXUTIL.DLL REXXUTIL.DL_ 8 11/20/1998 15:58 49229 DFDA8338
REXXUTIL.DLL ORXUTIL1.DL_ 15 11/20/1998 15:58 33725 532823E8
RINSTPRN.EXE RINSTPRN.EX_ 9 01/22/1999 13:23 194586 A9644AFF
RO.KBL RO.KB_ 17 11/20/1998 08:49 944 3AC9AC9C
RSPDDI.EXE RSPDDI.EX_ 16 11/23/1998 17:05 22073 D31F5149
RSPDSPI.EXE RSPDSPI.EX_ 11 11/23/1998 17:14 95352 A96E3543
RSPINST.EXE RSPINST.EX_ 8 01/22/1999 16:42 429040 301FF25B
RSRV.EXE RSRV.EX_ 12 10/28/1997 14:19 77955 45C9B6CB
RU.KBL RU.KB_ 17 11/20/1998 08:49 1144 39BB415F
SBCD2.ADD SBCD2.AD_ 16 02/09/1998 11:44 18820 1A3D5F00
SCENTER.DLL SCENTER.DL_ 7 02/05/1999 17:12 291373 7FC31C90
SD.KBL SD.KB_ 17 11/20/1998 08:49 1036 4D899A4C
SEAMLESS.DLL SEAMLESS.DL_ 15 02/08/1999 11:39 49679 8E6E9262
SECUTIL.DLL SECUTIL.DL_ 16 05/07/1998 12:15 21468 0C32C3AE
SEINST.EXE SEINST.EX_ 15 11/23/1998 16:51 37441 3389FACF
SEMAINT.EXE SEMAINT.EX_ 14 11/23/1998 16:51 67376 5D70C5C7
SERIAL.PDR SERIAL.PD_ 16 11/20/1998 16:41 19060 A97E0C6A
SESAPI.DLL SESAPI.DL_ 15 11/20/1998 16:10 24283 B8A7AE5B
SESDD32.SYS SESDD32.SY_ 13 11/20/1998 16:11 118832 05AA1172
SESMGR.DLL SESMGR.DL_ 17 09/25/1998 11:49 1536 E6969999
SESMGR.TDF SESMGR.TD_ 17 02/16/1999 11:41 1877 5E49AD92
SETBOOT.EXE SETBOOT.EX_ 2 02/10/1999 13:19 17196 498A7ED8
SETDEFV.CMD SETDEFV.CM_ 17 06/23/1998 16:25 1652 AA7ED9EC
SF.KBL SF.KB_ 17 11/20/1998 08:49 1036 1A766EAB
SK.KBL SK.KB_ 17 11/20/1998 08:49 1008 4EFCD632
SL.KBL SL.KB_ 17 11/20/1998 08:49 982 34CD374E
SOFTDRAW.DLL SOFTDRAW.DL_ 7 09/16/1998 18:23 400939 D030BFF6
SOM.DLL SOM.DL_ 12 08/13/1996 09:29 88763 78098814
SONY31A.ADD SONY31A.AD_ 16 02/09/1998 11:45 32738 FFD08BC8
SPCHOBJ.DLL SPCHOBJ.DL_ 11 12/21/1997 01:27 132899 E38BF817
SPL1B.DLL SPL1B.DL_ 16 01/26/1999 09:45 5077 E9132409
SQ.KBL SQ.KB_ 17 11/20/1998 08:49 824 309B01B5
SS2PCIC1.SYS SS2PCIC1.SY_ 16 02/26/1998 15:04 19087 6BC161B4
SS2TCIC1.SYS SS2TCIC1.SY_ 16 02/26/1998 15:04 22824 0EBF2054
FixPak Corrective Service levels and disk layouts 46
February 26, 1999 - Warp 4 FixPak XR_M010
SSM.DLL SSM.DL_ 17 09/29/1998 16:01 1556 382C768D
SSMDD.SYS SSMDD.SY_ 16 09/29/1998 16:09 36813 339AF036
STRACE.EXE STRACE.EX_ 14 12/07/1998 09:01 40318 D1C64ABC
SV.KBL SV.KB_ 17 11/20/1998 08:49 946 FD7C9C3C
SVMC.DLL SVMC.DL_ 10 02/03/1999 11:25 98389 B3501172
SVSH.DLL SVSH.DL_ 15 02/03/1999 11:26 23452 6C7078C9
SW.DLL SW.DL_ 13 02/03/1999 11:25 66503 8FE319CA
SWITCHRX.CMD SWITCHRX.CM_ 16 05/06/1998 16:31 7928 79CA9FC4
SYMB.PFM SYM1.PF_ 17 10/10/1997 01:03 679 C8D8E0BA
SYSDUMP.EXE SYSDUMP.EX_ 16 11/23/1998 16:47 16000 7E2B4A82
SYSINST2.EXE SYSINST2.EX_ 11 01/22/1999 16:38 184560 3971D8E9
SYSINSTX.COM SYSINSTX.CO_ 15 02/10/1999 13:17 39472 65B8B7CE
SYSLEVEL.EXE SYSLEVEL.EX_ 15 11/23/1998 16:50 42848 02D18192
SYSLEVEL.FPK SYSLEVEL.FP_ 17 12/08/1998 16:22 165 3595DAF0
SYSLOGPM.EXE SYSLOGPM.EX_ 10 02/05/1999 16:23 138955 13A5672E
SYSMONO.FON SYSMONO.FO_ 16 05/07/1998 11:29 46255 88EA273D
SYSMONOI.FON SYSMONOI.FO_ 13 01/16/1998 17:54 42146 4E79763E
SYSSPLIT.CMD SYSSPLIT.CM_ 17 12/02/1998 16:25 3712 A35A41C8
SYSTEM.TDF SYSTEM.TD_ 16 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 02/09/1998 12:15 9808 E96F4A07
TFFLST.CMD TFFLST.CM_ 17 12/02/1998 16:25 4638 2AFE15D2
TIMES.FON TIMES.FO_ 12 01/16/1998 17:57 257547 525801C9
TNR.OFM TNR.OF_ 16 02/12/1998 10:05 4882 D671B2F3
TNR.PFB TNR.PF_ 10 02/12/1998 10:05 119332 4B5D06F5
TNR.PFM TN1.PF_ 17 02/12/1998 10:05 1103 3721CE38
TNRB.OFM TNRB.OF_ 16 02/12/1998 10:05 4898 800C0409
TNRB.PFB TNRB.PF_ 10 02/12/1998 10:05 123083 3F834DC1
TNRB.PFM TNR1.PF_ 17 02/12/1998 10:05 1112 60408943
TNRBI.OFM TNRBI.OF_ 16 02/12/1998 10:05 4912 DA9134F6
TNRBI.PFB TNRBI.PF_ 10 02/12/1998 10:05 134003 3B151659
TNRBI.PFM TNRB1.PF_ 17 02/12/1998 10:05 1118 E18A75CC
TNRI.OFM TNRI.OF_ 16 02/12/1998 10:05 4903 00B41362
TNRI.PFB TNRI.PF_ 10 02/12/1998 10:05 131366 4152A764
TNRI.PFM TNR2.PF_ 17 02/12/1998 10:05 1114 526E6595
TR.KBL TR.KB_ 17 11/20/1998 08:49 962 5C4237BB
TR440.KBL TR440.KB_ 17 11/20/1998 08:49 1042 780DCC83
TRACE.DOC TRACE.DO_ 16 02/19/1999 10:29 63897 09F1DAE2
TRACE.EXE TRACE.EX_ 15 02/10/1999 13:21 35488 14BC01B8
TRACEDLL.DLL TRACEDLL.DL_ 14 12/02/1998 16:35 44551 8188DF56
TRACEFMT.EXE TRACEFMT.EX_ 10 01/26/1999 14:24 156565 E84BCE5C
TRACEGET.EXE TRACEGET.EX_ 15 12/02/1998 16:36 22058 6FE02302
TRAPDUMP.EXE TRAPDUMP.EX_ 15 12/02/1998 16:41 23068 C82D84D7
TRAPLOG.EXE TRAPLOG.EX_ 4 11/23/1998 16:47 15056 5F48C314
TRC0000.TFF TRC0000.TF_ 17 11/24/1998 09:09 189 0EDB257E
TRC0001.TFF TRC0001.TF_ 16 11/20/1998 08:24 17360 69F0A08C
TRC0003.TFF TRC0003.TF_ 17 12/12/1996 17:56 1503 3435868F
FixPak Corrective Service levels and disk layouts 47
February 26, 1999 - Warp 4 FixPak XR_M010
TRC0004.TFF TRC0004.TF_ 17 11/24/1998 09:09 4754 E52D826B
TRC0005.TFF TRC0005.TF_ 16 02/10/1999 13:10 38711 BCABCF25
TRC0006.TFF TRC0006.TF_ 16 12/12/1996 17:19 12356 B2A0674E
TRC0007.TFF TRC0007.TF_ 17 02/09/1998 11:35 1394 9B780A39
TRC0008.TFF TRC0008.TF_ 17 02/06/1998 11:51 544 449A16D2
TRC0010.TFF TRC0010.TF_ 16 02/16/1999 11:41 13359 3ED8217F
TRC0012.TFF TRC0012.TF_ 17 11/23/1998 16:44 1247 1801FC0D
TRC0016.TFF TRC0016.TF_ 17 02/16/1999 11:41 1663 A66BC9FB
TRC0017.TFF TRC0017.TF_ 17 02/16/1999 11:41 5561 3EB3BCEA
TRC0018.TFF TRC0018.TF_ 16 02/16/1999 11:41 39488 AF26135D
TRC006D.TFF TRC006D.TF_ 16 06/23/1998 19:40 24181 FB8B4954
TRC00C0.TFF TRC00C0.TF_ 16 02/05/1999 18:14 15970 1A42FC66
TRC00C2.TFF TRC00C2.TF_ 16 02/05/1999 18:14 25991 CC93DD6E
TRC00C3.TFF TRC00C3.TF_ 17 02/05/1999 18:14 3984 5EEF4AC0
TRC00C4.TFF TRC00C4.TF_ 17 02/08/1999 11:37 288 623B3DA4
TRC00C5.TFF TRC00C5.TF_ 16 01/22/1999 11:58 32994 86F40AD8
TRC00C6.TFF TRC00C6.TF_ 17 01/26/1999 09:45 7146 F49C202D
TRC0100.TFF TRC0100.TF_ 17 02/10/1999 13:10 6140 39F2ED25
TRC0101.TFF TRC0101.TF_ 17 02/10/1999 13:10 7234 A86A15D5
TRC0102.TFF TRC0102.TF_ 16 02/10/1999 13:10 26074 F6120C3D
TRC0103.TFF TRC0103.TF_ 16 02/10/1999 13:10 10103 E1896C8E
TRC0104.TFF TRC0104.TF_ 17 02/10/1999 13:10 5285 11538BB0
TRC0105.TFF TRC0105.TF_ 16 02/10/1999 13:10 28174 3310ED32
TRC0106.TFF TRC0106.TF_ 17 02/10/1999 13:10 1835 B1FAB15C
TRC0107.TFF TRC0107.TF_ 17 02/10/1999 13:10 4563 C662279D
TRC0108.TFF TRC0108.TF_ 16 02/10/1999 13:10 9607 DD254C6D
TRC0109.TFF TRC0109.TF_ 17 02/10/1999 13:10 2774 29A1DBBE
TRC010A.TFF TRC010A.TF_ 17 02/10/1999 13:11 1080 C19AA066
TRC0118.TFF TRC0118.TF_ 17 02/05/1999 16:40 2526 46657705
TRC0119.TFF TRC0119.TF_ 17 02/16/1999 11:40 3786 6E003CCC
TRC012C.TFF TRC012C.TF_ 17 02/08/1999 12:32 5361 F96B9213
TRC012D.TFF TRC012D.TF_ 17 02/08/1999 12:32 7870 79F5F0C3
TRC012E.TFF TRC012E.TF_ 16 02/05/1999 16:47 32972 8DB7EA12
TRCFORMT.DLL TRCFORMT.DL_ 15 01/26/1999 14:24 26645 6F6FFC4F
TRCUST.EXE TRCUST.EX_ 14 02/10/1999 13:22 99285 3C6A09BC
TRSPOOL.DOC TRSPOOL.DO_ 16 12/02/1998 16:29 6648 28B150A2
TRSPOOL.EXE TRSPOOL.EX_ 15 02/05/1999 16:23 27982 7BD31091
TRSTOP.EXE TRSTOP.EX_ 16 02/16/1999 10:14 17190 A6320EAB
TRUETYPE.DLL TRUETYPE.DL_ 11 01/22/1999 10:17 128677 C8508C1D
UA.KBL UA.KB_ 17 11/20/1998 08:49 1476 B4827643
UCDFS.DLL UCDFS.DL_ 16 10/21/1996 09:24 13264 A114CE30
UCONV.DLL UCONV.DL_ 15 01/28/1999 14:35 23841 2029D07A
UHPFS.DLL UHPFS.DL_ 13 02/05/1999 16:41 105488 4B7972A0
UK.KBL UK.KB_ 17 11/20/1998 08:49 816 9F26676B
UK168.KBL UK168.KB_ 17 11/20/1998 08:49 850 8BD12A9A
ULSACT01.MSG ULSACT01.MS_ 17 10/07/1997 15:24 907 D78FD5D3
ULSCAU01.MSG ULSCAU01.MS_ 9 10/07/1997 15:24 899 5E5812BC
ULSDET01.MSG ULSDET01.MS_ 6 10/07/1997 15:24 903 74AAE3DC
ULSERR01.MSG ULSERR01.MS_ 17 10/07/1997 15:24 1967 F1C19CA1
UNICODE.SYS UNICODE.SY_ 16 01/28/1999 16:11 20010 6C745842
UNINSTAL.EXE UNINSTAL.EX_ 12 09/25/1998 11:39 99641 619B51C2
FixPak Corrective Service levels and disk layouts 48
February 26, 1999 - Warp 4 FixPak XR_M010
UNPACK2.EXE UNPACK2.EX_ 14 01/22/1999 16:53 79792 6A84FC14
USER.EXE USER.EX_ 9 02/19/1999 17:05 280976 36568678
USINTER.KBL USINTER.KB_ 17 11/20/1998 08:49 1032 269B53D3
VBIOS.SYS VBIOS.SY_ 16 11/23/1998 17:38 8816 2EC0059F
VCDROM.SYS VCDROM.SY_ 16 02/09/1998 12:22 6880 A05DBDFB
VCMOS.SYS VCMOS.SY_ 17 09/24/1998 09:50 2272 6B071989
VCOM.SYS VCOM.SY_ 16 02/06/1998 13:02 12384 EF0274D0
VDMA.SYS VDMAPS2.SY_ 16 11/23/1998 17:38 14329 D3017935
VDMA.SYS VDMAAT.SY_ 10 11/23/1998 17:38 11465 50D5C1FB
VDPMI.SYS VDPMI.SY_ 16 09/24/1998 09:51 30624 F1E337B1
VDPX.SYS VDPX.SY_ 16 11/23/1998 17:38 26112 C0D79FB9
VDSK.SYS VDSK.SY_ 16 02/06/1998 13:02 10384 8A7004F4
VGA.DSP VGA.DS_ 17 05/05/1998 01:48 3094 4C886174
VIEW.EXE VIEW.EX_ 15 01/22/1999 12:18 26828 A0AF8E35
VIOCALLS.DLL VIOCALLS.DL_ 17 09/25/1998 11:16 2048 2EC643CA
VIOTBL.DCP VIOTBL.DC_ 15 11/20/1998 11:25 225355 915CF392
VIOTBL.ISO VIOTBL.IS_ 15 11/20/1998 11:25 230105 693C5449
VKBD.SYS VKBD.SY_ 16 11/05/1998 15:09 25659 15E609AA
VLPT.SYS VLPT.SY_ 16 02/06/1998 13:03 10113 91754BAE
VMAN.DLL VMAN.DL_ 14 10/27/1998 11:46 26125 B1A2CDFE
VMANWIN.SYS VMANWIN.SY_ 17 01/13/1998 18:27 2880 26B2F7DA
VMOUSE.SYS VMOUSE.SY_ 16 02/06/1998 13:03 18704 1AE91550
VPIC.SYS VPIC.SY_ 16 11/23/1998 17:39 9942 E9672666
VPICPARM.SYS VPICPARM.SY_ 3 09/24/1998 09:51 736 E3AC5450
VTIMER.SYS VTIMER.SY_ 16 09/24/1998 09:51 9936 DF6F879B
VW32S.SYS VW32S.SY_ 16 09/24/1998 09:52 18320 2BFE570F
VWIN.SYS VWIN.SY_ 15 09/24/1998 09:51 26896 4C5D479C
WCFGMRI.DLL WCFGMRI.DL_ 16 07/23/1998 19:04 2596 B73786AA
WD24B.DSP WD24B.DS_ 17 04/03/1997 13:55 12050 329F1B70
WINCFG.DLL WINCFG.DL_ 16 02/05/1999 16:53 12839 43E31BE1
WINFILE.EXE WINFILE.EX_ 12 01/28/1999 08:56 146960 4D6C56DF
WINSCLIP.DLL WINSCLIP.DL_ 16 01/28/1999 08:52 14848 063DFCD4
WINSDDE.DLL WINSDDE.DL_ 16 01/28/1999 08:52 18432 9FF5AF73
WINSHELD.EXE WINSHELD.EX_ 16 01/28/1999 08:51 22016 10F11890
WINSMSG.DLL WINSMSG.DL_ 16 01/28/1999 08:51 28441 A0626045
WPCLS.IMP WPCLS.IM_ 16 03/31/1997 17:35 8661 DA24BBC2
WPCONFIG.DLL WPCONFIG.DL_ 8 02/05/1999 16:53 246078 4362A810
WPCONMRI.DLL WPCONMRI.DL_ 15 07/23/1998 19:04 27694 94872329
WPHELP.HLP WPHELP.HL_ 5 10/29/1997 16:28 841366 47FE7152
WPINET.DLL WPINET.DL_ 12 02/05/1999 17:11 115384 9E4E9EB5
WPMSG.HLP WPMSG.HL_ 6 12/16/1997 15:18 50198 9F06EB75
WPPRINT.DLL WPPRINT.DL_ 2 02/05/1999 16:56 363970 208FEE07
WPPRINT.HLP WPPRINT.HL_ 14 10/10/1997 05:48 71408 10006DCB
WPPRTMRI.DLL WPPRTMRI.DL_ 14 02/05/1999 16:56 66681 9CAB6D73
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_ 11 05/06/1998 16:31 2813 4BAD1428
WW.EXE WW.EX_ 16 04/01/1997 15:37 8305 EB671078
WWDLL.DLL WWDLL.DL_ 4 12/21/1997 01:29 276981 751E3674
WWHOOK.DLL WWHOOK.DL_ 16 12/21/1997 01:29 27230 893E20E8
XCOPY.EXE XCOPY.EX_ 1 02/10/1999 13:17 51152 9F9E73A3
FixPak Corrective Service levels and disk layouts 49
February 26, 1999 - Warp 4 FixPak XR_M010
************************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M010_ (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 01/26/1999 14:11 33280 4DD06747
************************************************************************
Product location on CSD: A:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
Fixpak name: XR_M010_ (Country = Generic)
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
FixPak Corrective Service levels and disk layouts 50
February 26, 1999 - Warp 4 FixPak XR_M010
..\..\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 F3D9AF24
NCAPPUTL.EXE NCAPPUTL.EX_ 17 05/11/1998 10:54 12612 F048440D
OS2LDR OS2LDR.___ 17 01/26/1999 14:11 33280 6DB83937
PMLOGON.EXE PMLOGON.EX_ 17 09/24/1998 12:49 40107 6ECF0A76
PRNCFG.DLL PRNCFG.DL_ 17 09/24/1998 12:51 58258 13B7DD95
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
February 26, 1999 - Warp 4 FixPak XR_M010
10.0 SPACE UTILIZATION
The FixPak installation process requires free space on the following
drives:
Space needed Drive
Up to 2MB C:
Up to 2MB Boot drive (4MB if boot is C:)
Up to 22MB Drive with most free space, holds deferred files if
A:SERVICE method used.
Up to 36MB FixPak Archive/Backup for product with CSD level of
XR_4000
Up to 36MB 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.
Space Utilization 52
February 26, 1999 - Warp 4 FixPak XR_M010
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.
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