home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 28 Fixes4x
/
28-Fixes4x.zip
/
xr_m011.rm1
< prev
next >
Wrap
Text File
|
1999-07-06
|
122KB
|
3,248 lines
< Installation instructions for Warp 4 FixPak XR_M011 - 2nd release.
July 1, 1999
This FixPak makes the products it services Year 2000 ready
Build level 9.035 - 2nd release
This FixPak applies to:
CSD Level: XR_4000 Warp 4
Component ID: 5639A6100
Version: 4.00
Type: 0C
CSD Level: XR_4010 WorkSpace On Demand Release 1
Component ID: 5639A6100
Version: 4.01
Type: 0C
CSD Level: XR_4010 WorkSpace On Demand Release 2
Component ID: 5639A6120
Version: 4.01
Type: 0C
Requires Corrective Service Facility release f.141 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
July 1, 1999 - Warp 4 FixPak XR_M011
July 1, 1999 - Warp 4 FixPak XR_M011
Page ii
July 1, 1999 - Warp 4 FixPak XR_M011
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Second release of XR_M011 . . . . . . . . . . . . . . . . . . . 3
4.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 4
4.0.1 Device Drivers removed from Fixpak . . . . . . . . . . . . . 4
4.0.2 Can't install Warp 4 . . . . . . . . . . . . . . . . . . . . 4
4.0.3 Please use Fixtool f.141 or later . . . . . . . . . . . . . 4
4.0.4 TRAP in ES16881$ after FP10 applied . . . . . . . . . . . . 4
4.0.5 System Sounds not working after FixPak applied . . . . . . . 5
4.0.6 Using Display Recovery Choices . . . . . . . . . . . . . . . 5
4.0.7 Installation of Java 1.1.4 . . . . . . . . . . . . . . . . . 6
4.0.8 DSPRES.DLL included in this FixPak . . . . . . . . . . . . . 6
4.0.9 No products were found . . . . . . . . . . . . . . . . . . . 6
4.0.10 Previous installation interrupted . . . . . . . . . . . . . 7
4.0.11 Unable to open Archive directory . . . . . . . . . . . . . 7
4.0.12 RC 932 doing CID install of Warp 4 . . . . . . . . . . . . 8
4.0.13 Multimedia no longer selectable . . . . . . . . . . . . . . 9
4.0.14 MMPARTS.DLL/USER.EXE popup during install . . . . . . . . . 9
4.0.15 CSF0208 No products were found on the target ... . . . . . 9
4.0.16 CSF0248 Archive path is shared between mismatched . . . . . 9
4.0.17 CSF0249 Error opening or creating archive file. . . . . . 10
4.0.18 Printer installation process change . . . . . . . . . . . 10
4.0.19 Configuration Installation Distribution ( CID ) . . . . . 10
5.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 11
5.0.1 RAS file changes . . . . . . . . . . . . . . . . . . . . . 11
5.0.2 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 11
5.0.3 Windows printer drivers leave a zombie thread running . . . 12
5.0.4 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . . . . 12
5.0.5 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . . . 12
5.0.6 Intermittent hangs . . . . . . . . . . . . . . . . . . . . 13
6.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.1 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 14
6.2 Querying file dates for files after Dec 31, 1999 in REXX . . . 14
6.3 Enhanced support for Workspace On-Demand . . . . . . . . . . . 15
6.3.1 PMLOGON user exits . . . . . . . . . . . . . . . . . . . . 15
6.3.2 Setup strings for public applications . . . . . . . . . . . 18
6.3.3 Command line options for TLOGOFF and TSHUTDWN . . . . . . . 19
6.3.4 PMLOGON No Progress Indicator option . . . . . . . . . . . 19
6.3.5 PMLOGON No System Modal Window option . . . . . . . . . . . 20
6.4 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.4.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 20
6.4.2 Where Euro is not supported . . . . . . . . . . . . . . . . 21
6.4.3 Printing the Euro . . . . . . . . . . . . . . . . . . . . . 22
Contents iii
July 1, 1999 - Warp 4 FixPak XR_M011
6.5 New Warp Registry Editor . . . . . . . . . . . . . . . . . . . 22
6.6 WorkSpace On Demand . . . . . . . . . . . . . . . . . . . . . . 22
6.7 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.8 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 23
6.9 Joliet-2 support in CDFS.IFS . . . . . . . . . . . . . . . . . 23
6.10 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 23
6.10.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 23
6.10.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 25
6.11 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 26
6.11.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 26
6.11.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.11.3 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.11.4 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.12 Other README files . . . . . . . . . . . . . . . . . . . . . . 28
7.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 29
7.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 29
7.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 29
7.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 30
7.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . . . . 30
7.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 31
7.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 31
7.4 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 32
8.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 34
8.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 34
8.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 34
8.3 Method 2: Install from alternate bootable media . . . . . . . . 35
8.4 Additional Corrective Service Facility information . . . . . . 36
8.5 FixPaks on CD-ROM . . . . . . . . . . . . . . . . . . . . . . . 36
9.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 37
9.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 38
10.0 FixPak Corrective Service levels and disk layouts . . . . . . 39
11.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 52
11.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 52
11.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 53
Contents iv
July 1, 1999 - Warp 4 FixPak XR_M011
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_M011 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_M011 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
July 1, 1999 - Warp 4 FixPak XR_M011
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
July 1, 1999 - Warp 4 FixPak XR_M011
3.0 SECOND RELEASE OF XR_M011
This is the second release of Warp 4 FixPak XR_M011. The only difference
between this release and the first release is the addition of CHKDSK.COM
and CHKDSK.SYS and removal of PNP.DLL. CHKDSK.COM and CHKDSK.SYS are
identical to what was included in FixPak 6 through FixPak 10 and were
left out of FixPak 11 by mistake. PNP.DLL will be in the future release
of OS/2 Device Driver Fixpaks.
If you have previously installed FixPak 6 through FixPak 10 then you do
not need to install this 2nd release of FixPak 11 if you have previously
installed the 1st release of FixPak 11.
You can restore the previous version of PNP.DLL from your FixPak BACKUP
or ARCHIVE directory if you have installed the 1st release of FixPak 11.
Second release of XR_M011 3
July 1, 1999 - Warp 4 FixPak XR_M011
4.0 INSTALLATION NOTES
4.0.1 DEVICE DRIVERS REMOVED FROM FIXPAK
Beginning with Warp 4 FixPak XR_M011 and Warp 3 FixPak 41, most OS/2
Device Drivers have been moved to a separate Device Driver FixPak. The
first one will be XR_D001 which is scheduled for a later release.
4.0.2 CAN'T INSTALL WARP 4
If you can't get Warp 4 installed, check the OS/2 Device Driver Pak
Online at:
http://service.software.ibm.com/os2ddpak/readme.htm#disk1
for the latest available device drivers to update your Installation disks
with.
4.0.3 PLEASE USE FIXTOOL F.141 OR LATER
Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
Corrective Service Facility f.141 or later. It has fixes for problems
found in previous CSF builds as well as a fix to support RIPL servers
where there may be in excess of 250 SYSLEVEL files. It also handles the
type 1 (All FixPaks prior to 10 and 40) and type 2 (FixPaks 10 and 40 and
later) FixPaks.
If you try to use a CSF level prior to f.141 you will get a "CSF0208 No
products were found on the target system to service" message.
4.0.4 TRAP IN ES16881$ AFTER FP10 APPLIED
We do not ship any of the ESS sound card drivers in this Fixpak. To
corrrect the problem, get the latest ESS device driver for your card from
the OS/2 Device Driver Pak online at
http://service.software.ibm.com/os2ddpak/html/multimed/esstechn
Do this before you install the FixPak.
Installation Notes 4
July 1, 1999 - Warp 4 FixPak XR_M011
4.0.5 SYSTEM SOUNDS NOT WORKING AFTER FIXPAK APPLIED
If, after applying a FixPak, your System Sounds no longer work or you get
an error message stating "Error in closing CD device: Invalid device ID
given" when you close the CD Player, it may be caused by the FixPak
replacing the following files in your MMOS2 directory tree:
\MMOS2\DLL\DIVE.DLL
\MMOS2\DLL\MMPM.DLL
\MMOS2\DLL\MPGIO.DLL
\MMOS2\SSMDD.SYS
\MMOS2\DLL\SVMC.DLL
\MMOS2\DLL\SVSH.DLL
To recover, restore these files from your FixPak Backup or Archive
directory.
1. Boot from another partition, your Installation or Utility disks.
2. Rename the existing files in the MMOS2 directory tree so they will not
be overlayed when you restore the older files.
3. Change to the FixPak Backup directory if there is one. If not then
change to the FixPak Archive directory.
Note: The names may not be Backup or Archive. They will be whatever
you called them when you applied a FixPak.
4. For each of the above files, enter
UNPACK source target
Where "source" is the filename.ext of the file in the Backup or Archive
directory, like DIVE.DL_ or SSMDD.SY_
"target" is the fully qualified path of where to place the file,
like C:\MMOS2\DLL or C:\MMOS2
5. Repeat for each of the above files
6. Reboot your system. This resolved the problem on a TP760 and may also
resolve the problem on other hardware.
4.0.6 USING DISPLAY RECOVERY CHOICES
If you have the "Display Recovery Choices at each system startup"
function active on your system, you need to disable it before you apply a
FixPak if
■ The system is running
■ The boot partition will be serviced.
Installation Notes 5
July 1, 1999 - Warp 4 FixPak XR_M011
The problem with using this function is that the Corrective Service
Facility (CSF) updates the current CONFIG.SYS with entries to run the
Locked File Device Driver (LFDD) the next time you boot the system. This
is done to replace files that are currently in use (locked) by the
system.
The Recovery choices function replaces the current CONFIG.SYS with the
one that is associated with the recovery choice you select, wiping out
the LFDD entries. This means the LFDD does not run at boot time and the
deferred files will not get updated, therefore the FixPak does not get
completely applied.
Note: It is not necessary to disable this function if you install a
FixPak by booting from the CSF disks or from another OS/2 partition.
4.0.7 INSTALLATION OF JAVA 1.1.4
Installation of Java 1.1.4 on top of this FixPak will down-level portions
of the ULS support. If this occurs, Euro currency support will not work
correctly. To recover, re-install this FixPak. This will allow both Java
1.1.4 and Euro support to work correctly.
4.0.8 DSPRES.DLL INCLUDED IN THIS FIXPAK
DSPRES.DLL has been added to this FixPak for support for Euro character
display. This file can sometimes be overwritten by video device driver
installation. If this occurs, an updated version is located in
\OS2\INSTALL\VGA. This updated file can be copied into the \OS2\DLL
directory.
4.0.9 NO PRODUCTS WERE FOUND
If you see a "No products were found" message while applying this FixPak,
there is probably a mismatch between the data in
\OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this FixPak.
Compare the data for the OS/2 Base Operating System from the SYSLEVEL
command output with the same values listed at the end of this document in
the "FixPak Corrective Service levels and disk layouts" section. They
must be identical.
If these values are correct, check for the following files on any OS/2
boot drive in the \OS2\INSTALL directory.
LOGF0000.OS2
LOGSTART.OS2
LOGARCH.OS2
Installation Notes 6
July 1, 1999 - Warp 4 FixPak XR_M011
Check for the following files in your MMOS2\INSTALL directory.
LOGF0000.MPM
LOGSTART.MPM
LOGARCH.MPM
Also check for the following file:
C:\CSF_SEL.000
If these files exist, rename them and try the FixPak installation again.
Delete the renamed files after the FixPak has been applied.
4.0.10 PREVIOUS INSTALLATION INTERRUPTED
If you get a message that the previous installation of a FixPak was
interrupted (whether true or not), check for the following files and
directory on all drives:
Files:
FIXSTART
IBMCSFLK.LST
IBMCSFLK.CSF
CSF_*
Directory:
IBMCSFLK
If any exist, rename them and try the FixPak installation again. Delete
the renamed files after the FixPak has been applied.
4.0.11 UNABLE TO OPEN ARCHIVE DIRECTORY
If you get a message about problems with the Archive directory (for
example, cannot find or unable to open), then the most probable cause is
that you applied a previous FixPak and have since deleted the FixPak
ARCHIVE or BACKUP directory.
To recover from this, follow the "No files to service" and "Previous
installation interrupted" steps listed above.
Installation Notes 7
July 1, 1999 - Warp 4 FixPak XR_M011
4.0.12 RC 932 DOING CID INSTALL OF WARP 4
If you get a RC (Return Code) 932 while doing a CID install of Warp 4 and
you are using RSPINST.EXE from FixPak 3 or later, you will need to do the
following.
1. Create a temporary work directory somewhere on your harddrive.
assume it's c:\tempwork
2. Locate the section called "FixPak Corrective Service levels and disk
layouts".
3. Locate CHKDSK.SYS, CHKDSK32.DLL, CHKDSK32.EXE and UHPFS.DLL and
record what disks they are found on.
Note: For FixPak 3, they are on disks 12, 8, 12 and 9 respectively.
This will change for later FixPaks.
4. Place FixPak disk 12 in A: and enter
unpack a:\fix\os2.1\chkdsk.sy_ c:\tempwork
5. Place FixPak disk 8 in A: and enter
unpack a:\fix\os2.1\chkdsk32.dl_ c:\tempwork
6. Place FixPak disk 12 in A: and enter
unpack a:\fix\os2.1\chkdsk32.ex_ c:\tempwork
7. Place FixPak disk 9 in A: and enter
unpack a:\fix\os2.1\uhpfs.dl_ c:\tempwork
8. Make backup copies of CHKDSK.SYS, CHKDSK32.DLL and UHPFS.DLL from the
DISK_3 directory of your CID tree.
9. Copy CHKDSK.SYS from c:\tempwork to the DISK_3 directory of your CID
tree
10.Copy CHKDSK32.DLL from c:\tempwork to the DISK_3 directory of your CID
tree
11.Copy UHPFS.DLL from c:\tempwork to the DISK_3 directory of your CID
tree
12.Make a backup copy of the BUNDLE file on DISK_0
13.Copy DISK_0\BUNDLE c:\tempwork
14.Copy PACK2.EXE to c:\tempwork. If you don't have this file you can get
it using your Web browser from
Installation Notes 8
July 1, 1999 - Warp 4 FixPak XR_M011
ftp://ps.software.ibm.com/ps/products/os2/fixes/v4warp
15.PACK2 CHKDSK32.EXE bundle /H:\OS2\CHKDSK32.EXE /A
Note: This adds CHKDSK32.EXE to the bundle file. Enter "unpack bundle
/show" to verify it's really there.
16.Copy the updated BUNDLE back to the DISK_0 directory
17.Delete the c:\tempwork directory and files.
18.Copy the files SCSIADDS and PRESCHEK from DISK_4 to DISK_5.
19.Do the CID install
4.0.13 MULTIMEDIA NO LONGER SELECTABLE
IBM Multimedia Presentation Manager/2 (MPM) is now fully integrated into
the base OS/2. As part of this change, the \MMOS2\INSTALL\SYSLEVEL.MPM
file has been deleted. This means you will no longer see it as a
selectable entry in the Serviceable Products window when using the
A:SERVICE method of installation.
4.0.14 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL
If you get a popup about MMPARTS.DLL or USER.EXE during install, reply
"Yes" to replace it.
4.0.15 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET ...
This means no SYSLEVEL files was found that had a CSD Level, COMPID,
Version and Type that matched any of the SYSLEVEL files supported by this
FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2
in the OS2/INSTALL directory on your boot drive. Compare this data with
the data contained in the README.1ST file on FixPak disk 1.
To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2
and copy SYSLEVEL.OS2 from your Warp 4 installation DISK 1.
4.0.16 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED
1. The Archive path you specified (or was previously specified) contains
files from a different release of OS/2. You need to specify a
different Archive path.
2. You have a bad SYSLEVEL.OS2 or SYSLEVEL.MPM file. Both must have the
same Current CSD Level, Version, Type and Component ID if you point
both Fixpak Archives to the same location.
Installation Notes 9
July 1, 1999 - Warp 4 FixPak XR_M011
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.
4.0.17 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.
Typically this means the FixPak Archive directory has been deleted but
the files that point to it still exist. You need to delete the
LOGF000.OS2 and LOGSTART.OS2 files from your OS2/INSTALL directory.
LOGSTART.OS2 has the R/O attribute set and it needs to be reset before
the file can be deleted. There may also be a LOGARCH.OS2 file that needs
to be deleted.
This can also occur for Multi Media Presentation Manager/2 (MMPM). You
would then need to delete the LOGF0000.MPM and LOGSTART.MPM files from
the \MMOS2\INSTALL directory and possibly LOGARCH.MPM if it exists.
4.0.18 PRINTER INSTALLATION PROCESS CHANGE
If you install a new printer by clicking MB2 on the Printer icon in the
templates folder then clicking on Install, the printer object will now be
created in the Printer folder, not on the Desktop.
4.0.19 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )
Read the README.CID on Disk # 1 for an example of how to set up a
response file to do a CID install.
Installation Notes 10
July 1, 1999 - Warp 4 FixPak XR_M011
5.0 POST INSTALLATION NOTES
5.0.1 RAS FILE CHANGES
Beginning with FixPak 11, the following files are being added to the
\OS2\SYSTEM directory. If they also exist in the \OS2 directory you can
delete them as they are no longer needed there.
■ DTRACE.EXE
■ TRACEFMT.EXE
■ TRSPOOL.EXE
If you do not delete them from the \OS2 directory, they will be serviced
the same as the ones in the \OS2\SYSTEM directory to keep them current.
Also, the following files in the \OS2\SYSTEM\RAS directory can be deleted
as they have been superseded as shown:
File Superseded by
MDTRACE.doc DTRACE.DOC
MTRSPOOL.DOC TRSPOOL.DOC
5.0.2 SETTING IRQ9 PROCESSING IN CONFIG.SYS FOR VPIC.SYS
Some applications like PCAS (and some terminal emulators) have problems
sharing IRQ9 in a VDM. Since the DOS Virtual Device drivers are not
loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added
starting with Warp 3 FixPak 38 and Warp 4 FixPak 8.
To prevent sharing of IRQ9 in a VDM, add the following statement in
config.sys:
device=x:\os2\mdos\vpicparm.sys irq9_off
(x: is your OS/2 boot drive)
Next, in the settings for the program that requires exclusive access to
IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON.
When you next boot your system, VDMs will not share IRQ9.
Post Installation Notes 11
July 1, 1999 - Warp 4 FixPak XR_M011
5.0.3 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING
A problem occurs with some Windows printer drivers where a zombie thread
is left running after the program that loaded it is exited.
This does not occur when the program is run from a Seamless instance of
PROGMAN or from a Full Screen session because when these are exited the
whole WINOS2 Subsystem is exited.
This problem has been reported for the Adobe and Hewlett Packard Windows
printer drivers. To correct this problem for people running with these
drivers ONLY who have experienced symptoms such as:
■ exiting a program running seamlessly after printing or
■ setting up a printer and seeing the icon not being unhatched and/or
■ not being able to start another copy of the program
Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot*
section:
■ backgroundtasks=run_enum.exe,hpfbkg02.exe
then restart WINOS2.
Note: There may be other drivers that have the same problem. If you
experiences a similar problem with other drivers, please report it so the
correct SYSTEM.INI entry can be determined.
5.0.4 APAR JR09494 (TRAP EXITING WINOS2 WITH MWAVE AUDIO)
The fix for APAR JR09434 (trap exiting winos2 with MWAVE audio) requires
a new MWAVEVDD.SYS dated 11/96 or later. This file is available from the
IBM PC Company web site at http://www.pc.ibm.com.
5.0.5 SYS3170 INSTALLING LOTUS SMARTSUITE 96
A problem was discovered when attempting to install Lotus SmartSuite 96
with a early version of the Matrox video driver. A SYS3170 occurs after
pressing the button to start copying the files to the hard disk.
The problem does not occur with the current Matrox driver available on
the Web at
http://www.matrox.com/mgaweb/drivers/ftp_os2.htm
A work around that does not involve downloading files from the web, is to
switch your display driver to VGA during the install and after it has
Post Installation Notes 12
July 1, 1999 - Warp 4 FixPak XR_M011
completed, restore the Matrox driver.
5.0.6 INTERMITTENT HANGS
If you experience intermittent hangs of your system, check your LIBPATH
statement in CONFIG.SYS to see if SOM.DLL is in a directory other than,
and ahead of, OS2\DLL.
If yes, either change the LIBPATH statement to move the directory after
OS2\DLL or try renaming SOM.DLL to SOM.DLO.
One known cause of this is VisualAge C++. It has a version of SOM.DLL in
its DLL library and the installation puts this library ahead of OS2\DLL
in the LIBPATH statement.
Post Installation Notes 13
July 1, 1999 - Warp 4 FixPak XR_M011
6.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.
6.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.
6.2 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX
Existing REXX functions return file dates with a two digit year only.
While these functions are Year 2000 tolerant (i.e. the results will be
correct for files dated after Dec 31, 1999) they require some additional
logic in existing programs to handle the returned date correctly when
they are compared with other file dates.
Since the output format of the existing functions could not be changed
for compatibility reasons, new options have been added to the REXX
interpreter to return file dates with the year formatted with 4 digits.
Two functions have been extended to support the new format. The syntax to
retrieve the file date in 4 digit format is as follows:
New Function 14
July 1, 1999 - Warp 4 FixPak XR_M011
/********************************************/
/* 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
6.3 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND
6.3.1 PMLOGON USER EXITS
This function, provided by PMLOGON, allows system integrators to have
REXX code executed at specific points during the startup and logon
sequence. By default, user exits are disabled in PMLOGON.EXE. To enable
user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the
CONFIG.SYS file must be added. The /URX parameter specifies the location
and name of the user exit command file:
Execution Parameter User Exit command file that will be
executed
------------------- -----------------------------------
/URX \OS2\PMLOGURX.CMD
/URX:<filename>.CMD <filename>.CMD located in one of the
locations specified by the PATH
environment variable
/URX:d:\<path>\<filename>.CMD d:\<path>\<filename>.CMD
New Function 15
July 1, 1999 - Warp 4 FixPak XR_M011
The same command file is called for ALL user exits. The FIRST parameter
supplied to the command file indicates the exit that it is being called
for. The REXX command file is called for all these exits, even if it does
not need to process all of the exits. The REXX command file must be able
to return error free if it receives an exit number that it does not need
to handle. The following user exits are available:
New Function 16
July 1, 1999 - Warp 4 FixPak XR_M011
First Parameter Exit Description
--------------- ----------------
0 Executes ONCE per boot, before the requester
is started. There is no user logged on at this
time. This exit may return a string that is
processed exactly as the following execution
parameters set in RUNWORKPLACE of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately after the execution
parameters. See Note 2 below on /AUTO processing.
1 Executes ONCE per logon, after the requester
is started, but before logon occurs. There is no
user logged on at this time. This exit may return
a string that is processed exactly as the
following execution parameters set in RUNWORKPLACE
of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately before logon. See
Note 2 below on /AUTO processing.
2 Executes ONCE per logon, after the requester is
started and after logon occurs. There is a user
logged on at this time, but the Desktop has not
been started and the objects are not displayed.
No returns are processed.
3 Executes ONCE per logon, after the Desktop has
been started and the objects are created but not
currently displayed, but immediately before
control is passed to the Desktop. The icons are
fixed at this point. There is a user logged on
at this time. No returns are processed.
4 Executes immediately after a failed logon. The
second parameter passed to the exit contains the
return code from the logon API. This exit may
return a string that is processed exactly as the
execution parameters set in RUNWORKPLACE of
CONFIG.SYS for the following parameters only:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
This exit is processed immediately and logon is
retried with the new parameters regardless of
the /AUTO switch. See Note 2 below on /AUTO
New Function 17
July 1, 1999 - Warp 4 FixPak XR_M011
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.
6.3.2 SETUP STRINGS FOR PUBLIC APPLICATIONS
The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific
Workplace Shell WPProgram setup strings that are provided when creating
public applications on the WorkSpace On-Demand Desktop. In particular,
the ICONPOS setup string can be defined for a public application so that
the Administrator can identify where application icons are placed on the
WorkSpace On-Demand Desktop.
When a WorkSpace On-Demand Administrator creates a public application, a
new environment variable must be added to the application to provide a
setup string. The parameter name is NCC_SETUP_POST and the parameter
value can consist of any of the setup strings specified below. Each
setup string consists of a KEYNAME, followed immediately by an equal
('=') sign and a VALUE. Multiple setup strings can be passed in the
NCC_SETUP_POST environment variable by separating each setup string with
a semicolon (';'). The creation of this parameter can be performed
either using the WorkSpace On-Demand Public Applications Notebook (on the
Parameters page) or using a Command Line Interface (CLI). The following
is an example of one parameter:
NCC_SETUP_POST=ICONPOS=10,10;
The NCC_SETUP_POST environment variable will be searched for when each
WorkSpace On-Demand public application is created. If it is found, its
value will be used when creating the public application on the WorkSpace
On-Demand Desktop.
The following KEYNAME values are permitted for setup strings:
New Function 18
July 1, 1999 - Warp 4 FixPak XR_M011
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.
6.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.
6.3.4 PMLOGON NO PROGRESS INDICATOR OPTION
An execution parameter has been added to PMLOGON that causes the progress
indicator window not to be displayed during all of logon processing. That
parameter is /NOPI and can be specified only from the RUNWORKPLACE line
in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit,
it is ignored.
New Function 19
July 1, 1999 - Warp 4 FixPak XR_M011
6.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.
6.4 EURO SUPPORT
The European Monetary Union is creating the Euro as a new common currency
for Europe. As part of this effort the European Commission has
introduced a new character which represents the Euro. This character
looks like an uppercase C with two horizontal lines through it. The Euro
will come into existence on January 1, 1999 for use in banking. Euro
notes and coins will be issued starting January 2002.
6.4.1 BASE OS/2 SUPPORT
The OS/2 basic support for Euro consists of adding the Euro character to
fonts, codepages, and keyboards. The Euro is added to all display and
ATM fonts and to the Times New Roman MT 30 TrueType font which is
available with Java 1.1. The Euro is added to all western European
keyboards and the US International keyboard. The Euro can be used in
base OS/2, Presentation Manager, and in DOS. The Euro is not supported
in WinOS2.
The Euro character is added to these OS/2 base and PM codepages:
850 0xD5 PC Latin 1 base + PM
857 0xD5 PC Turkish base + PM
1004 0x80 Windows Extended base + PM
1250 0x80 Windows Latin 2 PM
1251 0x88 Windows Cyrillic PM
1252 0x80 Windows Latin 1 PM
1254 0x80 Windows Turkish PM
1257 0x80 Windows Baltic PM
The Euro character is added to these fonts.
New Function 20
July 1, 1999 - Warp 4 FixPak XR_M011
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
6.4.2 WHERE EURO IS NOT SUPPORTED
The Euro is not supported in WinOS2. This character is not supported in
the Windows-1252 codepage used in WinOS2. This character is not
available on the WinOS2 keyboards. This character is not available in
the WinOS2 supplied TrueType fonts:
New Function 21
July 1, 1999 - Warp 4 FixPak XR_M011
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.
6.4.3 PRINTING THE EURO
Existing printers do not support the Euro in device fonts. You need to
select a font which is not mapped to a device font in order to print the
Euro. The Euro will print correctly on printers where the system fonts
are used. When there are problems, a dotless-i is normally printed
instead of the Euro.
For PostScript printers, it is necessary to disable device fonts to print
the Euro in one of the base PostScript fonts (Helvetica, Times Roman,
Courier). To do this:
1. Open the properties of the Printer object
2. Select the Print Driver tab
3. Select Job Properties
4. Select the Output tab
5. Deselect "Use printer device fonts"
6.5 NEW WARP REGISTRY EDITOR
See the README.REG file on the first FixPak disk for details.
6.6 WORKSPACE ON DEMAND
WorkSpace on Demand Release 1 is supported starting with FixPak 5
(XR_M005). WorkSpace on Demand Release 2 is supported starting with
FixPak 11 (XR_M011).
6.7 IBM OPEN32
This FixPak includes updates to the IBM Open32 Application Programming
Interfaces (APIs).
New Function 22
July 1, 1999 - Warp 4 FixPak XR_M011
6.8 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
Future updates for GRADD and other video drivers (when they are released)
will be found via the internet at:
■ http://service.software.ibm.com/pslaunch.html
6.9 JOLIET-2 SUPPORT IN CDFS.IFS
Joliet is a Microsoft extension to the ISO 9660 CD-ROM file system which
adds Unicode and longname support. Presently both Windows 95 and Windows
NT 4.0 support the Joliet-2 and Joilet-3 formats. Beginning with Warp 3
Fixpak 32 and Warp 4 Fixpak 4, you can enable the Joliet-2 support by
adding the '/w' option to the CDFS.IFS statement in CONFIG.SYS.
Joilet-3 format is not supported.
6.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.
6.10.1 USING THE NEW CHKDSK
The interface to CHKDSK remains CHKDSK.COM and PMCHKDSK. No changes
occurred to the CHKDSK command line parameters or messages.
The first time this version of CHKDSK runs on a fast formatted drive, it
will report harmless errors. These errors go away once CHKDSK is run
with the /F option.
Note: OS/2 Warp Install uses fast format.
New Function 23
July 1, 1999 - Warp 4 FixPak XR_M011
Unlike prior versions of CHKDSK, large drives ( > 8GB) may be autochecked
if sufficient memory is available. The amount of memory required can
vary between 16MB and 48MB depending on the size of the drive. To enable
the autochecking of large drives, the following line must be added to
your config.sys:
BASEDEV=CHKDSK.SYS
This device driver allows CHKDSK to access memory normally reserved for
the system during the boot process. Due to this, if CHKDSK has to use
this memory:
■ The memory will not be available for the system to use in completing
the boot process
■ Errors may occur later in the boot process.
Hence, the chkdsk.sys device driver is smart enough to recognize when
CHKDSK has used this reserved memory and will reboot the system
automatically after all HPFS drives have been checked. Since the drives
were checked before the reboot, CHKDSK will not have to check them after
the reboot and the system will boot normally.
Note: For those wishing to run unattended: In order to prevent the
system from pausing between autocheck and the reboot, we recommend that
the statement PAUSEONERROR=NO be in the CONFIG.SYS.
When you don't have enough physical (real) memory to autocheck large
drives, you must use virtual memory from SWAPPER.DAT. The technique is
to check the large drives between the time OS/2 starts and PM begins. To
start OS/2, the swap file and device drivers must reside on an unaffected
drive. The drives to be checked must not appear in the autocheck list in
the IFS statement for HPFS (or HPFS386).
This technique involves the following steps:
1. Remove the drive letter of the affected drive(s) from the autocheck
list in the IFS statement for HPFS (or HPFS386).
2. If you are using HPFS, add /QUIET to the IFS statement for HPFS.
3. If you are using HPFS386.IFS, add POPUPERRORS=NO below the
[filesystem] section of the HPFS386.INI file. Support for the
POPUPERRORS parameter requires OS/2 LAN Server FixPak IP08265 or
higher for LS 5.0 or FixPak IP08503 or higher for LS 5.1. In addition,
the POPUPERRORS parameter ONLY suppresses HFS0102 messages.
4. Add a CALL statement to your config.sys. This CALL statement will
call CHKDSK.COM, and will tell it what drive to check. This CALL
statement must appear after the LIBPATH=, SET PATH=, and SET DPATH=
statements, but before any other CALL statements in your CONFIG.SYS
file.
New Function 24
July 1, 1999 - Warp 4 FixPak XR_M011
Calls to CHKDSK in STARTUP.CMD are not necessary, when using this method
or the base device driver (chkdsk.sys) method.
Example: The computer boots from drive C (moderate HPFS or FAT sized
drive). Drive D (large HPFS) requires more RAM to check than installed
in the machine.
Original IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:CD
New IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:C /QUIET
The CALL statement to use is:
CALL=C:\OS2\CHKDSK.COM D: /C
The /C option tells CHKDSK to check the drive only if it is "dirty" and
it needs checking.
If you need to boot from diskettes to check an HPFS drive, you must have
the following files on the diskette you wish to run CHKDSK from:
CHKDSK.COM
CHKDSK32.DLL
UHPFS.DLL
The BOOTDISK.EXE program has been updated to create new utility diskettes
with the proper files.
6.10.2 CHKDSK LOG FORMATTER
CHKDSK creates a binary service log file (chkdsk.log) on the root of the
drive being checked during autocheck or whenever the /F option is
invoked. The previous log file is saved as chkdsk.old. A formatter for
this log file can be found at:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe
This is a self extracting ZIP file. Place it in a directory in your path
and enter CHKLOGPK. This will create the following files:
New Function 25
July 1, 1999 - Warp 4 FixPak XR_M011
message.txt
msghdr.txt
pmchklog.exe
range.txt
readme
They should all have a date of 05/14/97 or later (May 14, 1997).
This is a tool used by OS/2 service to format and view the new CHKDSK log
entries. There is no support for this tool. You are welcome to use it
but if you have problems with it or do not understand the output DO NOT
contact IBM for assistance as none will be provided.
6.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).
6.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".
6.11.2 TRAPLOG
The TRAPLOG command allows dynamic control of trap information logging.
The command syntax is:
TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]
New Function 26
July 1, 1999 - Warp 4 FixPak XR_M011
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.
6.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.
6.11.4 SYSDUMP
The SYSDUMP command forces a System Dump to be initiated, regardless of
the TRAPDUMP settings. This command is provided for the use of service
personnel to allow Dump Initiation to be automated through use of a
command file.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
New Function 27
July 1, 1999 - Warp 4 FixPak XR_M011
The system behaves as if a fatal crash has occurred thus under rare
circumstances data can be lost.
The command syntax is:
SYSDUMP [/NOPROMPT]
where:
■ NOPROMPT allows the Dump to proceed without the prompt and response to
message:
"Do you want to force a system dump? (Y/N)"
6.12 OTHER README FILES
There are other README files containing information you may want to
review. All except README.DBG are found on the first FixPak disk and are
not copied to your system when the Fixpak is installed. README.DBG will
be copied to the \OS2\INSTALL directory during installation beginning
with Fixpak 10 and Fixpak 41.
File Use
README2 Problems fixed in each FixPak (APAR list)
README.CID Installing FixPaks via CID
README.REG Use of the Warp Registry Editor REGEDIT2.EXE
README.DBG Tips on debugging OS/2 Warp and details on the latest
Serviceability (RAS) Enhancements (3.0 and 4.0).
New Function 28
July 1, 1999 - Warp 4 FixPak XR_M011
7.0 CORRECTIVE SERVICE FACILITY
7.0.1 REQUIRED CSF LEVEL
You should use release level f.141 or later of the OS/2 Corrective
Service Facility to install this FixPak.
Bootable diskettes are no longer provided starting with the F.138B CSF
build. Instead, you now get a self-extracting ZIP file which contains the
following:
archctl.cmd
build.lvl
csfpans.dll
filefix.dll
fpinst.cmd
fservice.exe
fservice.msg
ibmcsflk.dll
ibmcsflk.exe
ibmcsflk.msg
ibmcsflk.sys
msg.dll
nls.dll
pack.exe
read.me
readme.inf
response.lan
response.wp3
response.wp4
service.exe
service.hlp
shpiinst.dll
unpack.exe
unpack2.exe
viocalls.dll
Follow the directions in the READ.ME file to use the new CSF code. It
covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
from one of several alternative boot methods.
7.0.2 WHERE YOU CAN FIND CSF CODE
The Corrective Service Facility code is available from many places,
including, but not limited to, the following:
Source How to access
Corrective Service Facility 29
July 1, 1999 - Warp 4 FixPak XR_M011
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.
7.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_M011.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_M011
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through 35.
Examples:
XR_M011.ADK = 10
XR_M011.FDK = 15
XR_M011.LDK = 21
etc.
7.1 RESIDUAL FIXPAK FILES FROM OS/2 2.11 OR WARP 3
If the following is true:
1. You upgraded your system from OS/2 2.11 or Warp 3
2. You applied one or more FixPaks to the previous system
3. You HAVE NOT applied a Warp 4 FixPak
Corrective Service Facility 30
July 1, 1999 - Warp 4 FixPak XR_M011
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.
7.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.
7.3 SYSLEVEL FILE LOCATIONS
This FixPak will service directories based on the location of a supported
SYSLEVEL.OS2 file. Please check your system to make sure extra copies of
this file are not located in directories other than:
\OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)
If additional copies of these files are found in other locations on your
hard disk then CSF will try to service files as follows:
Corrective Service Facility 31
July 1, 1999 - Warp 4 FixPak XR_M011
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.
7.4 RELOCATED OS/2 FILE SUPPORT
If you have moved OS/2 files or directories to a drive other than the one
the SYSLEVEL.OS2 file is on, do the following in order to have them
serviced:
■ Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
OS\2 Warp 4 partition to be serviced.
In this file, place the full path to the directories you want to be
serviced. Assuming your boot drive is C: and you installed Multimedia
on the D: drive and manually moved WINOS2 support to the E: drive:
Corrective Service Facility 32
July 1, 1999 - Warp 4 FixPak XR_M011
D:\MMOS2
D:\MMOS2\DLL
D:\MMOS2\DSP
D:\MMOS2\HELP
D:\MMOS2\IMAGES
D:\MMOS2\INETTEMP
D:\MMOS2\INSTALL
D:\MMOS2\MACROS
D:\MMOS2\MOVIES
D:\MMOS2\SOUNDS
D:\MMOS2\SOUNDS\DESKTOP
D:\MMOS2\SOUNDS\GARDEN
D:\MMOS2\SOUNDS\OCEAN
D:\MMOS2\SOUNDS\SPACE
E:\OS2\MDOS\WINOS2
E:\OS2\MDOS\WINOS2\SYSTEM
E:\OS2\MDOS\WINOS2\TEMP
Note: Leave this file for any future OS/2 Warp 4 FixPaks you might apply.
The easy way to create this file is to use the DIR command with the /A:D
/S /B parameters and pipe the output to a file.
dir d:\mmos2 /a:d /s /b > anyfile
Then copy that data into the USERDIRS.OS2 file.
With CSF release level F.137B or later, you can use wildcards, so your
USERDIRS.OS2 file would be much simpler and would look like:
D:\MMOS2\*
E:\OS2\MDOS\WINOS2\*
Corrective Service Facility 33
July 1, 1999 - Warp 4 FixPak XR_M011
8.0 INSTALLATION PROCESS
8.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.
8.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
Note: CS_???.EXE below means CS_141 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Here are some additional notes:
Follow the displayed instructions. When prompted to insert Corrective
Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_M011
Corrective Service Diskette 1 in drive A. Repeat for the rest of the
FixPak disks when requested to do so.
It can take a considerable length of time for the Corrective Service
Facility to scan your hard disk for serviceable files. In some cases, it
has taken as long as 40 minutes. Please be patient and allow this
process to complete.
If this is the first OS/2 Warp FixPak you have applied to this system,
then enter the path to the directory where a copy of replaced files will
be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)
Note: This ARCHIVE directory is not related to the ARCHIVES directory
built into OS/2 Warp 3 and Warp 4. Please specify a different path. You
must specify a different ARCHIVE directory for each product to be
serviced.
Installation Process 34
July 1, 1999 - Warp 4 FixPak XR_M011
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.
8.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA
Note: CS_???.EXE below means CS_141 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Installation Process 35
July 1, 1999 - Warp 4 FixPak XR_M011
Here are some additional notes:
This method does not prompt the user for any information. No interaction
with the user takes place other than requests to put the next diskette in
drive A. All serviceable partitions on your system will be updated
automatically unless you have modified the default response file. Be
especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
this method because they can cause CSF to apply service to directories
you do not want serviced.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. Please be
patient and allow this process to complete.
Note: You can edit the response file to control some of the actions taken
by FSERVICE.EXE while applying a FixPak. See the READ.ME file or use the
VIEW command to look at the file README.INF. They are part of
CS_???.EXE.
8.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.
8.5 FIXPAKS ON CD-ROM
Both the IBM Technical Connection and the IBM Developer Connection
contain the latest OS/2 and LAN FixPaks that were available at publishing
time.
The IBM Technical Connection homepage on the World Wide Web is located
at:
■ http://www.ibm.com/Support/techconn/index.htm
The IBM Developer Connection homepage on the World Wide Web is located
at:
■ http://www.developer.ibm.com/devcon/titlepg.htm
Check these WWW sites for content and ordering information.
Installation Process 36
July 1, 1999 - Warp 4 FixPak XR_M011
9.0 CSD LEVEL OF SYSLEVEL.OS2
The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
partition will be updated with the name of the FixPak when it is applied.
This is a major change from previous CSF releases. The Prior CSD level
field will be left asis. This means when you use the SYSLEVEL command to
look at the release levels of products on your system, you will see the
following for SYSLEVEL.OS2.
Before a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR04000
Prior CSD level: XR04000
After a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0M008
Prior CSD level: XR04000
All fix information is recorded in SERVICE.LOG. Look at the file
\OS2\INSTALL\SERVICE.LOG
on your boot drive for information relating to the installation of
FixPaks on your system.
Additionally, you can use the VER /R command to see the current revision
of OS/2 installed. The response will look like the following for this
FixPak:
The Operating System/2 Version is 4.00
Revision 9.035
The first page of this document has a line that looks like:
Build Level: n.nnn
CSD level of SYSLEVEL.OS2 37
July 1, 1999 - Warp 4 FixPak XR_M011
That is the number you should see for this FixPak when you issue the VER
/R command.
9.0.1 NEW SYSLEVEL.FPK
A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning with
XR_M004. It is titled "OS/2 Warp 4 Service Level". It contains the name
of the currently installed FixPak in both the Current and Previous CSD
level fields and is located in the same directory the SYSLEVEL.OS2 file
is located in which should be \OS2\INSTALL.
The easiest way to look at SYSLEVEL information is to use the SYSLEVEL
command and redirect the output to a file then edit the file and search
for SYSLEVEL.FPK.
CSD level of SYSLEVEL.OS2 38
July 1, 1999 - Warp 4 FixPak XR_M011
10.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 9.035
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M011_ (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_M011_ (Country = Generic)
Pre-requisite CSD Level: XR_4010_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
________________________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
Fixpak name: XR_M011_ (Country = Generic)
Pre-requisite CSD Level: XR_4010_
System Id: 1000
Component Id: 5639A6120
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Will create the following directories
..\..\OS2 Stub File: @OS2DIR
..\..\OS2\DLL Stub File: @DLLDIR
..\..\OS2\BOOT Stub File: @BOOTDIR
..\..\OS2\SYSTEM Stub File: @SYSTDIR
FixPak Corrective Service levels and disk layouts 39
July 1, 1999 - Warp 4 FixPak XR_M011
..\..\OS2\INSTALL Stub File: @INSTDIR
..\..\OS2\SYSTEM\RAS Stub File: @RASDIR
..\..\OS2\SYSTEM\TRACE Stub File: @TRACDIR
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
ART.DLL ART.DL_ 9 06/17/1997 10:15 202952 11623534
ART.HLP ART.HL_ 16 04/18/1997 16:16 11980 173C6284
ARTADMIN.EXE ARTADMIN.EX_ 13 06/17/1997 10:15 78693 F198CC78
ARTCHRON.EXE ARTCHRON.EX_ 14 07/25/1997 10:01 58994 B82B9752
ARTFI.EXE ARTFI.EX_ 14 06/17/1997 10:15 61482 873E97DC
ARTFIR.DLL ARTFIR.DL_ 15 01/16/1998 16:06 30614 416548E5
ARTINET.DLL ARTINET.DL_ 14 06/17/1997 10:15 66252 2D5C4572
ARTR.DLL ARTR.DL_ 13 01/16/1998 16:06 80629 BD96A723
ARTREG.EXE ARTREG.EX_ 14 06/17/1997 10:15 66193 20DDFAF6
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 04/09/1999 15:37 158758 A60EF63C
AVIO.DLL AVIO.DL_ 14 02/03/1999 11:26 53923 811D0F32
BACKUP.EXE BACKUP.EX_ 16 04/13/1999 13:01 28196 354D726E
BDIME.DLL BDIME.DL_ 16 04/12/1999 15:52 11911 89E4D67F
BE.KBL BE.KB_ 16 04/09/1999 15:34 972 47EAAF60
BLDLEVEL.EXE BLDLEVEL.EX_ 14 09/15/1998 11:32 43974 F7F6C0D4
BOOTDISK.EXE BOOTDISK.EX_ 14 04/13/1999 12:38 60435 750DEE33
BOOTDISK.HLP BOOTDISK.HL_ 16 04/13/1999 12:38 10892 C51CF389
BVSCALLS.DLL BVSCALLS.DL_ 16 09/25/1998 11:52 512 40ADC2D3
BY.KBL BY.KB_ 16 04/09/1999 15:34 1292 5060D151
CA.KBL CA.KB_ 16 04/09/1999 15:34 1214 B7CA68BE
CACHE.EXE CACHE.EX_ 16 04/26/1999 13:43 11820 8A223FC6
CARDINFO.DAT CARDINFO.DA_ 16 02/02/1999 19:41 54979 C547DE0F
CDFS.IFS CDFS.IF_ 15 06/08/1999 08:44 45173 60EE7D38
CDFS.TDF CDFS.TD_ 16 06/08/1999 08:44 2113 7E127B0C
CDROM.TBL CDROM.TB_ 16 11/12/1996 13:38 4365 F398665E
CF.KBL CF.KB_ 16 04/09/1999 15:34 956 96C22906
CHKDSK.COM CHKDSK.CO_ 14 04/13/1999 12:54 70208 F62F0BA5
CHKDSK.SYS CHKDSK.SY_ 16 04/01/1999 17:10 747 11D6D4C8
CHKDSK32.DLL CHKDSK32.DL_ 5 04/13/1999 12:53 121895 5AB4152A
CHKDSK32.EXE CHKDSK32.EX_ 16 04/13/1999 12:44 6417 43DFCC60
CMD.EXE CMD.EX_ 13 04/13/1999 12:56 74300 DE057E0F
COMM.DRV COMM.DR_ 16 03/09/1999 12:59 9552 2A6A35F2
COMMAND.COM COMMAND.CO_ 15 04/13/1999 12:55 53375 60C497A7
CONTROL.PM CONTROL.PM_ 16 05/05/1998 01:48 8474 85121A82
COUNTRY.SYS COUNTRY.SY_ 16 04/13/1999 12:59 50932 EC726673
COUR.OFM COUR.OF_ 16 01/07/1998 23:34 4236 62BDB51D
COUR.PFB COUR.PF_ 11 01/07/1998 23:34 112702 F47DEC19
COUR.PFM COU1.PF_ 16 01/07/1998 23:34 674 EBCD0968
FixPak Corrective Service levels and disk layouts 40
July 1, 1999 - Warp 4 FixPak XR_M011
COURB.OFM COURB.OF_ 16 01/07/1998 23:34 4246 6BB1D3EA
COURB.PFB COURB.PF_ 10 01/07/1998 23:34 116938 3F227222
COURB.PFM COUR1.PF_ 16 01/07/1998 23:34 679 1EFB356B
COURBI.OFM COURBI.OF_ 16 01/07/1998 23:34 4260 BD106AF3
COURBI.PFB COURBI.PF_ 10 01/07/1998 23:34 112484 88CD4829
COURBI.PFM COURB1.PF_ 16 01/07/1998 23:34 685 D0390E4C
COURI.OFM COURI.OF_ 16 01/07/1998 23:34 4251 4DC923B8
COURI.PFB COURI.PF_ 10 01/07/1998 23:34 113244 4A250D0F
COURI.PFM COUR2.PF_ 16 01/07/1998 23:34 681 A6EECE02
COURIER.FON COURIER.FO_ 15 01/16/1998 17:56 104183 CDD08B00
CREX.MSG CREX.MS_ 16 09/19/1996 15:44 2865 84FD8E0E
CREXUTIL.DLL CREXUTIL.DL_ 14 11/20/1998 15:58 49229 1FDA6291
CREXX.DLL CREXX2.DL_ 10 04/01/1999 14:20 266031 D55B2A5F
CZ.KBL CZ.KB_ 16 04/09/1999 15:34 1014 4C4E438C
DDINSTAL.EXE DDINSTAL.EX_ 15 04/13/1999 12:27 34855 E135AFAC
DE.KBL DE.KB_ 16 04/09/1999 15:34 958 E417FFD5
DE453.KBL DE453.KB_ 16 04/09/1999 15:34 1354 0C1FC811
DF_DEB.EXE DF_DEB.EX_ 12 04/07/1999 09:37 135921 37C545AB
DF_RET.EXE DF_RET.EX_ 12 04/13/1999 12:10 136177 45ABBB76
DIBDRVR.DLL DIBDRVR.DL_ 16 10/22/1997 23:20 2267 1429BD22
DICTATE.EXE DICTATE.EX_ 12 05/06/1998 11:58 51391 460F71F4
DICTDLL.DLL DICTDLL.DL_ 14 12/21/1997 01:28 51187 D092C5CA
DISPLAY.DLL DISPLAY.DL_ 14 04/07/1999 15:46 46574 82EEAA74
DIVE.DLL DIVE.DL_ 13 09/29/1998 16:01 69640 C06FD486
DK.KBL DK.KB_ 16 04/09/1999 15:34 928 3D2D683D
DMQSPROF.DLL DMQSPROF.DL_ 14 04/07/1999 16:01 39033 EC252D39
DOSCALL1.DLL DOSCALL1.DL_ 11 05/04/1999 09:07 124438 9A002B1D
DOSCALL1.SYM DOSCALL1.SY_ 15 05/04/1999 09:07 41716 2F3006F5
DOSCALL1.TDF DOSCALL1.TD_ 16 05/04/1999 09:07 5426 62664DF6
DOSKRNL DOSKRNL.___ 15 06/08/1999 08:43 30569 2E44EA22
DRVMAP.INF DRVMAP.IN_ 16 04/03/1997 13:54 12986 0AD62B34
DSPINSTL.EXE DSPINSTL.EX_ 12 04/13/1999 12:35 117816 92C0EA23
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 04/21/1999 10:58 75371 D5765F89
DTRACE.EXE DTRACE1.EX_ 14 02/16/1999 10:15 48906 D9D70598
DTRACE.EXE DTRACE.EX_ 14 02/16/1999 10:15 48906 D9D70598
E.EXE E.EX_ 13 04/13/1999 11:03 61719 6FDA865C
EAUTIL.EXE EAUTIL.EX_ 15 04/13/1999 12:57 37984 43F0351E
EJECT.EXE EJECT.EX_ 15 01/09/1998 16:20 25648 0C9E0C86
EL.KBL EL.KB_ 16 04/09/1999 15:34 1396 B76E4B7E
EL459.KBL EL459.KB_ 16 04/09/1999 15:34 1372 8C941E52
ENGINE.EXE ENGINE.EX_ 6 07/23/1997 11:39 440424 CA47CBAA
EPM.EXE EPM.EX_ 16 07/16/1998 13:18 19684 E6ED87A9
ERLOGGER.EXE ERLOGGER.EX_ 15 02/05/1999 16:23 34320 1AAB418B
ERRLOG.DLL ERRLOG.DL_ 13 02/05/1999 16:23 72594 6B4602A5
ES.KBL ES.KB_ 16 04/09/1999 15:34 920 FF749BFC
ETKC603.DLL ETKC603.DL_ 11 12/16/1997 15:06 135759 6AF203C2
ETKE603.DLL ETKE603.DL_ 5 05/07/1998 09:10 754050 D31FD1AF
FDISK.COM FDISK.CO_ 13 04/13/1999 13:03 114218 70362E0F
FDISKPM.DLL FDISKPM.DL_ 16 01/26/1999 14:22 7731 6B64272C
FixPak Corrective Service levels and disk layouts 41
July 1, 1999 - Warp 4 FixPak XR_M011
FDISKPM.EXE FDISKPM.EX_ 13 04/13/1999 13:03 63042 C6B18DC7
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_ 16 04/09/1999 15:34 940 6FE4DEC8
FILT.DLL FILT.DL_ 15 09/29/1998 16:10 22888 C4544636
FKA.DLL FKA.DL_ 16 10/10/1997 01:03 13997 5C4513FC
FORMAT.COM FORMAT.CO_ 14 04/13/1999 12:58 69920 810591CF
FR.KBL FR.KB_ 16 04/09/1999 15:34 950 562DD4F5
FSFILTER.SYS FSFILTER.SY_ 16 06/08/1999 08:46 12988 087EF483
GDI.EXE GDI.EX_ 9 03/09/1999 11:31 225744 10D1FFDA
GRADD.SYS GRADD.SY_ 16 04/07/1999 17:44 1195 98CBC4DC
GRE2VMAN.DLL GRE2VMAN.DL_ 16 04/07/1999 17:43 17901 95F8D672
HDMON.EXE HDMON.EX_ 13 04/13/1999 09:50 75071 9D672805
HELPMGR.DLL HELPMGR.DL_ 8 04/13/1999 16:04 249825 55AA43A1
HELPMSG.EXE HELPMSG.EX_ 15 04/13/1999 12:58 36256 1DB8CA02
HELV.FON HELV.FO_ 12 01/16/1998 17:56 264425 4A514FF3
HELV.OFM HELV.OF_ 16 05/06/1998 16:34 4865 8049D22A
HELV.PFB HELV.PF_ 11 05/06/1998 16:34 101942 3F1961BC
HELV.PFM HEL1.PF_ 16 05/06/1998 16:34 1096 C72298C9
HELVB.OFM HELVB.OF_ 16 05/06/1998 16:34 4857 10D426BE
HELVB.PFB HELVB.PF_ 11 05/06/1998 16:34 104404 D2D90EE1
HELVB.PFM HELV1.PF_ 16 05/06/1998 16:34 1089 5A484E7D
HELVBI.OFM HELVBI.OF_ 16 05/06/1998 16:34 4859 F812E346
HELVBI.PFB HELVBI.PF_ 11 05/06/1998 16:34 105074 CF169E28
HELVBI.PFM HELVB1.PF_ 16 05/06/1998 16:34 1087 06A2ED9D
HELVI.OFM HELVI.OF_ 16 05/06/1998 16:34 4844 299A0D5F
HELVI.PFB HELVI.PF_ 11 05/06/1998 16:34 103996 D3AF0069
HELVI.PFM HELV2.PF_ 16 05/06/1998 16:34 1079 4D475EBC
HPFS.IFS HPFS.IF_ 12 04/26/1999 13:42 141378 2C13507D
HPFS.TDF HPFS.TD_ 16 04/26/1999 13:42 1620 C6DBB5AE
HR.KBL HR.KB_ 16 04/09/1999 15:34 982 04524FA3
HU.KBL HU.KB_ 16 04/09/1999 15:34 1006 A5381FC1
IBM1004 IBM1004.___ 16 04/09/1999 15:33 3584 8C57D2DA
IBM1125 IBM1125.___ 16 04/09/1999 15:33 4320 02358C47
IBM1131 IBM1131.___ 16 04/09/1999 15:33 4320 B3BAD682
IBM1250 IBM1250.___ 16 04/09/1999 15:33 3552 3B327CBF
IBM1251 IBM1251.___ 16 04/09/1999 15:33 3328 EC5ECAEC
IBM1252 IBM1252.___ 16 04/09/1999 15:33 3552 AEEDDBC1
IBM1253 IBM1253.___ 16 04/09/1999 15:33 3552 B265BFF8
IBM1254 IBM1254.___ 16 04/09/1999 15:33 3552 A8DFEE3A
IBM1255 IBM1255.___ 16 04/09/1999 15:33 3808 152518CD
IBM1256 IBM1256.___ 16 04/09/1999 15:33 4320 8CFB62EA
IBM1257 IBM1257.___ 16 04/09/1999 15:33 3296 2080348D
IBM850 IBM850.___ 16 04/09/1999 15:33 4320 D7F0034B
IBM857 IBM857.___ 16 04/09/1999 15:33 4352 5EFE84D4
IBMOPTNS.DLL IBMOPTNS.DL_ 16 02/02/1999 19:41 18744 DAA60B97
ICONEDIT.EXE ICONEDIT.EX_ 12 07/23/1998 16:08 109504 2A41E8A9
IFGDI2VM.DRV IFGDI2VM.DR_ 14 04/07/1999 16:06 92520 E81825AD
INST_DOS.EXE INST_DOS.EX_ 14 04/13/1999 16:02 36466 B52FE8D0
INSTALL.EXE INSTALL.EX_ 6 04/13/1999 12:16 384280 C712EE44
FixPak Corrective Service levels and disk layouts 42
July 1, 1999 - Warp 4 FixPak XR_M011
IOPROC.DLL IOPROC.DL_ 15 02/03/1999 11:27 37878 1CD1ED61
IS.KBL IS.KB_ 16 04/09/1999 15:34 940 040B4152
IS458.KBL IS458.KB_ 16 04/09/1999 15:34 928 3D6742AF
ISGDI2VM.DRV ISGDI2VM.DR_ 14 04/07/1999 16:06 91328 1C3F9230
IT.KBL IT.KB_ 16 04/09/1999 15:34 876 130F54A8
IT142.KBL IT142.KB_ 16 04/09/1999 15:34 854 D12D2A22
KERNEL.SDF KERNEL.SD_ 15 11/07/1996 21:11 467330 06CC86A1
KERNELD.SDF KERNELD.SD_ 15 11/07/1996 21:12 468657 3CC5754F
KRNLBDEV.TDF KRNLBDEV.TD_ 16 06/08/1999 08:40 3703 DF35F591
KRNLBFS.TDF KRNLBFS.TD_ 16 06/08/1999 08:40 4464 0FA6B910
KRNLBLDR.TDF KRNLBLDR.TD_ 16 06/08/1999 08:40 5581 D5F07875
KRNLBPG.TDF KRNLBPG.TD_ 16 06/08/1999 08:40 3203 D2DB0904
KRNLBSEL.TDF KRNLBSEL.TD_ 16 06/08/1999 08:40 2727 9A0A283B
KRNLBSEM.TDF KRNLBSEM.TD_ 16 06/08/1999 08:40 1792 30CACC22
KRNLBSM.TDF KRNLBSM.TD_ 16 06/08/1999 08:40 1321 48DAF03F
KRNLBTK.TDF KRNLBTK.TD_ 16 06/08/1999 08:40 14363 3883619F
KRNLBTOM.TDF KRNLBTOM.TD_ 16 06/08/1999 08:40 925 AF6A0C64
KRNLBVDM.TDF KRNLBVDM.TD_ 16 06/08/1999 08:40 13917 BB635C8F
KRNLBVM.TDF KRNLBVM.TD_ 16 06/08/1999 08:40 5514 0ED444C5
KRNLDDEV.TDF KRNLDDEV.TD_ 16 06/08/1999 08:42 3678 B620C602
KRNLDFS.TDF KRNLDFS.TD_ 16 06/08/1999 08:42 4355 69D632B9
KRNLDLDR.TDF KRNLDLDR.TD_ 16 06/08/1999 08:42 5609 BE34A11E
KRNLDPG.TDF KRNLDPG.TD_ 16 06/08/1999 08:42 3284 3D28EE30
KRNLDSEL.TDF KRNLDSEL.TD_ 16 06/08/1999 08:42 2814 1D2C19DC
KRNLDSEM.TDF KRNLDSEM.TD_ 16 06/08/1999 08:42 1932 BEAC9712
KRNLDSM.TDF KRNLDSM.TD_ 16 06/08/1999 08:42 1321 ADB13514
KRNLDTK.TDF KRNLDTK.TD_ 16 06/08/1999 08:42 14394 44EFFA9D
KRNLDTOM.TDF KRNLDTOM.TD_ 16 06/08/1999 08:42 953 55AEAB8F
KRNLDVDM.TDF KRNLDVDM.TD_ 16 06/08/1999 08:42 13992 3CC005B9
KRNLDVM.TDF KRNLDVM.TD_ 16 06/08/1999 08:42 5601 C325FE56
KRNLRDEV.TDF KRNLRDEV.TD_ 16 06/08/1999 08:38 3703 DBF6E0B7
KRNLRFS.TDF KRNLRFS.TD_ 16 06/08/1999 08:38 4464 EDBD87DF
KRNLRLDR.TDF KRNLRLDR.TD_ 16 06/08/1999 08:39 5581 14B92551
KRNLRPG.TDF KRNLRPG.TD_ 16 06/08/1999 08:39 3203 877AEA04
KRNLRSEL.TDF KRNLRSEL.TD_ 16 06/08/1999 08:39 2727 E803595B
KRNLRSEM.TDF KRNLRSEM.TD_ 16 06/08/1999 08:39 1792 C89E78A7
KRNLRSM.TDF KRNLRSM.TD_ 16 06/08/1999 08:39 1321 D9B43750
KRNLRTK.TDF KRNLRTK.TD_ 16 06/08/1999 08:39 14279 2248EF09
KRNLRTOM.TDF KRNLRTOM.TD_ 16 06/08/1999 08:39 897 A4C0FC5D
KRNLRVDM.TDF KRNLRVDM.TD_ 16 06/08/1999 08:38 13749 594645D4
KRNLRVM.TDF KRNLRVM.TD_ 16 06/08/1999 08:39 5514 26A3AB7D
LIBCM.DLL LIBCM.DL_ 9 04/08/1999 16:09 210916 98DAC306
LIBCN.DLL LIBCN.DL_ 14 04/08/1999 16:08 57340 7BBE3105
LIBCS.DLL LIBCS.DL_ 9 04/08/1999 16:08 192386 978D3E9F
LIBUNI.DLL LIBUNI.DL_ 13 04/09/1999 15:32 81372 89A678E4
LOCALE.DLL LOCALE.DL_ 10 04/09/1999 15:33 107901 9ACCD164
MAIN.CPL MAIN.CP_ 12 03/09/1999 11:42 147680 ED523A7F
MAKETSF.EXE MAKETSF.EX_ 14 04/01/1999 14:39 37516 94D71533
MAPTSF.CMD MAPTSF.CM_ 16 04/01/1999 14:23 16803 0FFD489E
MIDI.SYS MIDI.SY_ 16 03/16/1999 10:29 26328 FA7BB5A8
MIDIMCD.DLL MIDIMCD.DL_ 16 09/29/1998 16:02 532 40B1F3FB
FixPak Corrective Service levels and disk layouts 43
July 1, 1999 - Warp 4 FixPak XR_M011
MIGRATE.EXE MIGRATE.EX_ 11 04/13/1999 12:35 118313 E8D14458
MINSTALL.EXE MINSTALL.EX_ 9 02/02/1999 19:41 152580 84E992F2
MINXOBJ.DLL MINXOBJ.DL_ 15 04/13/1999 10:27 31778 80E6E488
MIRRORS.DLL MIRRORS.DL_ 7 09/19/1996 15:53 444744 4D936F0C
MMODPTS.DLL MMODPTS.DL_ 3 09/29/1998 14:42 184020 4C87AB95
MMPARTS.DLL MMPARTS.DL_ 2 09/29/1998 16:13 1532250 AA3EBDC4
MMPM.DLL MMPM.DL_ 7 02/02/1999 19:46 431781 5F4F04BD
MMPTMRI.DLL MMPTMRI.DL_ 11 02/02/1999 18:35 227344 BDDD3E9B
MMSOUND.DRV MMSOUND.DR_ 16 03/09/1999 11:56 3456 97C27950
MONCALLS.DLL MONCALLS.DL_ 16 04/13/1999 12:08 2472 A9F9796D
MONCALLS.TDF MONCALLS.TD_ 16 04/13/1999 12:08 1139 6AABC73C
MPGIO.DLL MPGIO.DL_ 13 02/03/1999 11:27 59267 4C29334D
NAMEADD.EXE NAMEADD.EX_ 16 04/09/1999 16:01 23040 0209D0A6
NAMECOPY.EXE NAMECOPY.EX_ 16 04/09/1999 16:01 23040 DFB88851
NAMECSSP.DLL NAMECSSP.DL_ 13 10/28/1997 13:00 61155 A8FF5683
NAMEDEL.EXE NAMEDEL.EX_ 16 04/09/1999 16:01 23040 2A09D0A7
NAMEDSP.DLL NAMEDSP.DL_ 11 10/28/1997 13:00 123411 2EF315DB
NAMEEXT.EXE NAMEEXT.EX_ 16 04/09/1999 16:01 23040 6209D0A9
NAMEFT.DLL NAMEFT.DL_ 13 10/28/1997 13:00 66306 77789339
NAMEFW.DLL NAMEFW.DL_ 13 10/28/1997 13:00 72312 9A504B3F
NAMEINFO.DLL NAMEINFO.DL_ 14 10/28/1997 13:00 47941 A05DAC94
NAMEINI.DLL NAMEINI.DL_ 13 10/28/1997 13:00 59011 3562CDED
NAMEMOD.EXE NAMEMOD.EX_ 15 04/09/1999 16:01 23040 1209D0A7
NAMEMOVE.EXE NAMEMOVE.EX_ 15 04/09/1999 16:01 23040 E7B8884F
NAMEOSP.DLL NAMEOSP.DL_ 14 10/28/1997 13:00 52725 FBAB278A
NL.KBL NL.KB_ 16 04/09/1999 15:34 954 A4EF6074
NO.KBL NO.KB_ 16 04/09/1999 15:34 920 6F219407
NWIAPI.DLL NWIAPI.DL_ 16 04/13/1999 10:36 14768 8407D55F
OREXUTIL.DLL ORXUTIL2.DL_ 15 11/20/1998 15:58 33725 52F2EC68
OREXX.DLL OREXX2.DL_ 6 11/20/1998 15:58 489013 4BB269FA
OS2CHAR.TDF OS2CHAR.TD_ 16 05/04/1999 09:07 13889 398BC652
OS2DASD.DMD OS2DASD.DM_ 15 08/07/1998 12:19 40894 21CB3220
OS2DUMP OS2DUMP.___ 16 04/07/1999 10:27 17425 F01D2D20
OS2K386.EXE OS2K386.EX_ 13 03/09/1999 11:33 80306 53AED240
OS2KRNL OS2KRNL.___ 3 06/08/1999 08:39 634333 E0BA4625
OS2KRNL.TDF OS2KRNL.TD_ 16 06/08/1999 08:38 16581 ECA16EF9
OS2KRNLD.SYM OS2KRNLD.SY_ 11 06/08/1999 08:41 186132 C54ECFDA
OS2KRNLR.SYM OS2KRNLR.SY_ 12 06/08/1999 08:38 163284 AE7727D4
OS2LDR.MSG OS2LDR.MS_ 16 04/13/1999 11:51 8368 DF4724FA
OS2MM.DLL OS2MM.DL_ 8 02/02/1999 19:41 219650 AD7890CC
OS2NS.EXE OS2NS.EX_ 14 10/28/1997 14:18 44964 C8014916
OS2UGL OS2UGL.___ 16 04/09/1999 15:33 15616 AC7FB976
OS2UGLG OS2UGLG.___ 16 12/12/1997 22:59 8928 AA898322
OSO001.MSG OSO001.MS_ 1 04/12/1999 15:24 179413 69FD69EA
OSO001H.MSG OSO001H.MS_ 13 04/12/1999 15:24 241617 3EFA69E1
PARALLEL.PDR PARALLEL.PD_ 16 04/13/1999 10:56 15848 FDDC9DA6
PCMCIA.TBL PCMCIA.TB_ 16 07/24/1998 12:34 5114 E4E2485A
PDUMPSYS.EXE PDUMPSYS.EX_ 15 04/13/1999 09:50 34877 C4D753E7
PDUMPUSR.EXE PDUMPUSR.EX_ 15 04/13/1999 09:50 34875 6C37F546
PICV.DLL PICV.DL_ 15 04/13/1999 16:02 26200 C8F7662B
PICVIEW.DLL PICVIEW.DL_ 16 04/13/1999 16:02 10786 1EE319A1
FixPak Corrective Service levels and disk layouts 44
July 1, 1999 - Warp 4 FixPak XR_M011
PICVIEW.EXE PICVIEW.EX_ 13 04/13/1999 16:02 69146 61CA2516
PL.KBL PL.KB_ 16 04/09/1999 15:34 980 A865EE5D
PL457.KBL PL457.KB_ 16 04/09/1999 15:34 882 3F4F66C8
PMATM.DLL PMATM.DL_ 8 03/15/1999 18:36 224319 71C7F565
PMBIDI.DLL PMBIDI.DL_ 16 04/12/1999 15:52 12352 10E87CC0
PMCHKDSK.DLL PMCHKDSK.DL_ 16 11/04/1996 16:44 4127 CE30C1EE
PMCHKDSK.EXE PMCHKDSK.EX_ 15 04/13/1999 13:04 28183 FF9C60D8
PMCLIP.DLL PMCLIP.DL_ 16 10/22/1997 23:19 21295 2FE91E38
PMCTLS.DLL PMCTLS.DL_ 4 05/05/1999 14:03 585248 347D1C15
PMCTLS.SYM PMCTLS.SY_ 15 05/05/1999 14:03 44084 84C486EE
PMDDE.DLL PMDDE.DL_ 15 04/13/1999 16:05 28334 F2949C1A
PMDDEML.DLL PMDDEML.DL_ 15 04/13/1999 15:40 27710 60965C59
PMDF.EXE PMDF.EX_ 7 04/13/1999 09:49 263480 B682ACA8
PMDFMSG.DLL PMDFMSG.DL_ 14 02/05/1999 16:26 44240 C0BFAB8D
PMDRAG.DLL PMDRAG.DL_ 16 05/05/1999 14:00 1731 801F33F4
PMGPI.DLL PMGPI.DL_ 8 04/13/1999 15:37 229146 10D24DA4
PMGPI.TDF PMGPI.TD_ 16 04/13/1999 15:37 12338 FD344EBE
PMGRE.DLL PMGRE.DL_ 16 04/13/1999 15:36 2231 B20E2F7F
PMGRE.TDF PMGRE.TD_ 16 05/05/1999 14:04 1062 BD2330F1
PMMERGE.DLL PMMERGE.DL_ 1 05/05/1999 14:04 1255025 3809ACDA
PMMERGE.SYM PMMERGE.SY_ 12 05/05/1999 14:04 115412 BF1827DA
PMMLE.DLL PMMLE.DL_ 16 05/05/1999 14:02 673 4C270A0D
PMPIC.DLL PMPIC.DL_ 14 04/13/1999 16:02 47206 D0411841
PMPIC.TDF PMPIC.TD_ 16 05/05/1999 14:13 400 AAA319FB
PMPRINT.QPR PMPRINT.QP_ 16 04/13/1999 10:36 11833 87DF5DC4
PMSDMRI.DLL PMSDMRI.DL_ 16 04/13/1999 15:44 13312 10BBAF4D
PMSEEK.EXE PMSEEK.EX_ 15 04/13/1999 13:04 31285 8DDE1A54
PMSHAPI.DLL PMSHAPI.DL_ 16 10/22/1997 22:53 4549 7AE93081
PMSHAPI.TDF PMSHAPI.TD_ 16 05/05/1999 14:04 6726 15109D35
PMSPL.DLL PMSPL.DL_ 8 04/13/1999 10:35 277033 B981E25E
PMSPL.SYM PMSPL.SY_ 15 04/13/1999 10:35 32260 D04D12A0
PMSPL.TDF PMSPL.TD_ 16 04/13/1999 10:35 4491 AC4E7DE4
PMVDMP.DLL PMVDMP.DL_ 14 05/05/1999 14:15 42867 1BE471B1
PMVDMP.TDF PMVDMP.TD_ 16 05/05/1999 14:15 2661 F320E355
PMVIOP.DLL PMVIOP.DL_ 13 05/05/1999 14:15 58958 9D5A4C9C
PMVIOP.SYM PMVIOP.SY_ 16 05/05/1999 14:15 6628 6434FE78
PMVIOP.TDF PMVIOP.TD_ 16 05/05/1999 14:15 3551 64D85599
PMWIN.DLL PMWIN.DL_ 10 04/13/1999 15:38 11264 93A2E194
PMWIN.TDF PMWIN.TD_ 16 05/05/1999 14:04 9567 54B7C2FE
PMWIN32.SDF PMWIN32.SD_ 15 10/28/1997 18:56 299617 47F639A5
PMWINX.DLL PMWINX.DL_ 5 04/13/1999 16:02 530279 3A004321
PMWP.DLL PMWP.DL_ 3 04/13/1999 10:22 926615 751DC152
PMWP.SYM PMWP.SY_ 13 04/13/1999 10:22 100420 2711F96A
PMWP.TDF PMWP.TD_ 16 04/13/1999 10:22 13825 32CE568D
PMWPMRI.DLL PMWPMRI.DL_ 14 04/13/1999 10:23 54821 E3C815F0
PO.KBL PO.KB_ 16 04/09/1999 15:34 926 880ECFFE
PROCDUMP.DOC PROCDUMP.DO_ 16 04/01/1999 14:23 62765 B74B1E35
PROCDUMP.EXE PROCDUMP.EX_ 7 04/13/1999 09:50 47135 A1E0A208
PROGMAN.EXE PROGMAN.EX_ 14 03/09/1999 11:40 115328 D9CE06C3
PSSDMON.EXE PSSDMON.EX_ 15 04/06/1999 17:06 27117 A48B4E88
PSTAT.EXE PSTAT.EX_ 16 04/13/1999 13:00 11731 37F86261
FixPak Corrective Service levels and disk layouts 45
July 1, 1999 - Warp 4 FixPak XR_M011
QUECALLS.DLL QUECALLS.DL_ 16 09/25/1998 11:51 1024 E029B550
QUECALLS.TDF QUECALLS.TD_ 16 05/04/1999 09:07 1287 98104F93
RAS001.MSG RAS001.MS_ 15 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 49383F49
README.DBG README.DB_ 16 02/15/1999 09:00 22967 CB7E9035
REGCONV.EXE REGCONV.EX_ 15 04/09/1999 15:51 39446 2674D276
REGEDIT.HLP REGEDIT.HL_ 16 03/09/1999 13:02 22682 FD0A8523
REGEDIT2.EXE REGEDIT2.EX_ 4 04/09/1999 16:01 950272 2072DA29
REGISTRY.DLL REGISTRY.DL_ 14 04/09/1999 15:50 81440 4A83185D
REGISTRY.MSG REGISTRY.MS_ 16 04/09/1999 16:01 629 E72A3667
REGISTRY.TDF REGISTRY.TD_ 16 04/09/1999 15:50 7591 E2A5CC51
REPLACE.EXE REPLACE.EX_ 15 12/02/1998 17:04 37483 8F447F1C
RESTORE.EXE RESTORE.EX_ 15 04/13/1999 13:05 36256 BC40F4E6
REX.MSG REX.MS_ 16 09/19/1996 15:44 2865 6725D657
REXX.DLL CREXX1.DL_ 9 04/01/1999 14:20 266031 5DF28B8E
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_ 16 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 04/13/1999 11:09 194722 B8E9C8D0
RO.KBL RO.KB_ 16 04/09/1999 15:34 944 B000280C
RSPDDI.EXE RSPDDI.EX_ 15 04/13/1999 12:27 22073 7B4BAEFA
RSPDSPI.EXE RSPDSPI.EX_ 11 04/13/1999 12:36 95352 34F8BB3D
RSPINST.EXE RSPINST.EX_ 8 04/13/1999 12:23 428848 BE50E607
RSRV.EXE RSRV.EX_ 12 10/28/1997 14:19 77955 45C9BACB
RU.KBL RU.KB_ 16 04/09/1999 15:34 1144 6F2AF864
SCENTER.DLL SCENTER.DL_ 7 04/13/1999 10:58 291373 7FC1F890
SD.KBL SD.KB_ 16 04/09/1999 15:34 1036 18589C14
SEAMLESS.DLL SEAMLESS.DL_ 15 05/05/1999 14:15 49679 8EE664AC
SECUTIL.DLL SECUTIL.DL_ 16 04/01/1999 14:34 21468 C9F6B616
SEINST.EXE SEINST.EX_ 15 04/13/1999 12:13 37441 E7C4D486
SEMAINT.EXE SEMAINT.EX_ 14 04/13/1999 12:13 67376 B74E8A17
SERIAL.PDR SERIAL.PD_ 16 04/13/1999 10:27 19060 597E0C63
SESAPI.DLL SESAPI.DL_ 15 04/13/1999 09:40 24283 FD1EECE1
SESDD32.SYS SESDD32.SY_ 14 04/13/1999 14:44 118832 16809EE9
SESMGR.DLL SESMGR.DL_ 16 09/25/1998 11:49 1536 E6969999
SESMGR.TDF SESMGR.TD_ 16 05/04/1999 09:07 1877 5E49D852
SETBOOT.EXE SETBOOT.EX_ 2 04/13/1999 13:03 17196 498AE4D8
SETDEFV.CMD SETDEFV.CM_ 16 06/23/1998 16:25 1652 AA7ED9EC
SF.KBL SF.KB_ 16 04/09/1999 15:34 1036 EA004BF0
SK.KBL SK.KB_ 16 04/09/1999 15:34 1008 7B5D6967
SL.KBL SL.KB_ 16 04/09/1999 15:34 982 BDBAC7E9
SOFTDRAW.DLL SOFTDRAW.DL_ 7 04/13/1999 15:30 401003 FDB06A84
SOM.DLL SOM.DL_ 12 08/13/1996 09:29 88763 78038014
SPCHOBJ.DLL SPCHOBJ.DL_ 11 12/21/1997 01:27 132899 E393F817
SPL1B.DLL SPL1B.DL_ 16 04/13/1999 10:35 5077 0353DE3C
SQ.KBL SQ.KB_ 16 04/09/1999 15:34 824 4C421344
FixPak Corrective Service levels and disk layouts 46
July 1, 1999 - Warp 4 FixPak XR_M011
SSM.DLL SSM.DL_ 16 09/29/1998 16:01 1556 382C768D
SSMDD.SYS SSMDD.SY_ 16 09/29/1998 16:09 36813 739AF02E
STRACE.EXE STRACE.EX_ 15 04/13/1999 13:06 40318 714E8B16
SV.KBL SV.KB_ 16 04/09/1999 15:34 946 0677DA8D
SVMC.DLL SVMC.DL_ 12 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_ 16 10/10/1997 01:03 679 C8D8E0BA
SYSDUMP.EXE SYSDUMP.EX_ 16 04/13/1999 12:10 16000 8605F03F
SYSINST2.EXE SYSINST2.EX_ 12 04/13/1999 12:19 184512 17F1B6B5
SYSINSTX.COM SYSINSTX.CO_ 15 04/13/1999 13:00 39472 5278B7CE
SYSLEVEL.EXE SYSLEVEL.EX_ 15 04/13/1999 12:12 42848 2B6EFFCC
SYSLEVEL.FPK SYSLEVEL.FP_ 16 05/13/1999 12:30 165 113762E8
SYSLOGPM.EXE SYSLOGPM.EX_ 10 02/05/1999 16:23 138955 13A55A4E
SYSMONO.FON SYSMONO.FO_ 16 05/07/1998 11:29 46255 88EA273D
SYSMONOI.FON SYSMONOI.FO_ 16 01/16/1998 17:54 42146 CE79759A
SYSSPLIT.CMD SYSSPLIT.CM_ 16 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 03/22/1999 17:28 9808 6A65FD45
TFFLST.CMD TFFLST.CM_ 16 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 6171B2F4
TNR.PFB TNR.PF_ 10 02/12/1998 10:05 119332 4B7246F5
TNR.PFM TN1.PF_ 16 02/12/1998 10:05 1103 3721CE38
TNRB.OFM TNRB.OF_ 16 02/12/1998 10:05 4898 7FC80409
TNRB.PFB TNRB.PF_ 10 02/12/1998 10:05 123083 3F834DC1
TNRB.PFM TNR1.PF_ 16 02/12/1998 10:05 1112 60408943
TNRBI.OFM TNRBI.OF_ 16 02/12/1998 10:05 4912 EA913505
TNRBI.PFB TNRBI.PF_ 10 02/12/1998 10:05 134003 3B151659
TNRBI.PFM TNRB1.PF_ 16 02/12/1998 10:05 1118 E18A75CC
TNRI.OFM TNRI.OF_ 16 02/12/1998 10:05 4903 00B412A1
TNRI.PFB TNRI.PF_ 10 02/12/1998 10:05 131366 4152A764
TNRI.PFM TNR2.PF_ 16 02/12/1998 10:05 1114 526E6595
TR.KBL TR.KB_ 16 04/09/1999 15:34 962 E11D8DB2
TR440.KBL TR440.KB_ 16 04/09/1999 15:34 1042 81B006FF
TRACE.DOC TRACE.DO_ 16 04/01/1999 16:21 64057 45DDD8C5
TRACE.EXE TRACE.EX_ 15 04/13/1999 13:06 35136 4277C6C0
TRACEDLL.DLL TRACEDLL.DL_ 14 12/02/1998 16:35 44551 B988DF4C
TRACEFMT.EXE TRACEFMT.EX_ 10 04/13/1999 13:10 156569 65CB5F63
TRACEGET.EXE TRACGET1.EX_ 15 04/13/1999 09:46 22026 F16A3EEB
TRACEGET.EXE TRACEGET.EX_ 15 04/13/1999 09:46 22026 F16A3EEB
TRAPDUMP.EXE TRAPDUMP.EX_ 15 04/13/1999 09:50 23068 4C281BDE
TRAPLOG.EXE TRAPLOG.EX_ 4 04/13/1999 12:10 15056 DE99A8A2
TRC0000.TFF TRC0000.TF_ 16 11/24/1998 09:09 189 0EDB257E
TRC0001.TFF TRC0001.TF_ 16 04/09/1999 15:50 17168 28122B9B
FixPak Corrective Service levels and disk layouts 47
July 1, 1999 - Warp 4 FixPak XR_M011
TRC0003.TFF TRC0003.TF_ 16 12/12/1996 17:56 1503 3435868F
TRC0004.TFF TRC0004.TF_ 16 11/24/1998 09:09 4754 E52D826B
TRC0005.TFF TRC0005.TF_ 16 06/08/1999 08:41 38713 1DBFABDB
TRC0006.TFF TRC0006.TF_ 16 12/12/1996 17:19 12356 B2A0674E
TRC0007.TFF TRC0007.TF_ 16 03/22/1999 16:59 1394 9B7822C9
TRC0008.TFF TRC0008.TF_ 16 03/22/1999 16:57 544 451196D2
TRC0010.TFF TRC0010.TF_ 16 05/04/1999 09:07 13359 6998217F
TRC0012.TFF TRC0012.TF_ 16 04/13/1999 12:08 1247 1801E3CD
TRC0016.TFF TRC0016.TF_ 16 05/04/1999 09:07 1663 A66C74FB
TRC0017.TFF TRC0017.TF_ 16 05/04/1999 09:07 5561 3EB3BD95
TRC0018.TFF TRC0018.TF_ 16 05/04/1999 09:07 39488 5F261368
TRC006D.TFF TRC006D.TF_ 16 06/23/1998 19:40 24181 FB8B4954
TRC00C0.TFF TRC00C0.TF_ 16 05/05/1999 14:04 15970 FFC2FC65
TRC00C2.TFF TRC00C2.TF_ 16 05/05/1999 14:04 25991 CC93DBC6
TRC00C3.TFF TRC00C3.TF_ 16 05/05/1999 14:04 3984 DEEF4AA5
TRC00C4.TFF TRC00C4.TF_ 12 05/05/1999 14:13 288 625BDDA4
TRC00C5.TFF TRC00C5.TF_ 16 04/13/1999 15:37 32994 870A02D8
TRC00C6.TFF TRC00C6.TF_ 16 04/13/1999 10:35 7146 F49BE5AD
TRC0100.TFF TRC0100.TF_ 16 06/08/1999 08:42 6140 39F29C25
TRC0101.TFF TRC0101.TF_ 16 06/08/1999 08:42 7234 7FEA15D5
TRC0102.TFF TRC0102.TF_ 16 06/08/1999 08:42 26074 F6120B9B
TRC0103.TFF TRC0103.TF_ 16 06/08/1999 08:42 10103 B9096C8E
TRC0104.TFF TRC0104.TF_ 16 06/08/1999 08:42 5285 11538190
TRC0105.TFF TRC0105.TF_ 16 06/08/1999 08:42 28115 D71762B0
TRC0106.TFF TRC0106.TF_ 16 06/08/1999 08:42 1835 B1FAB0BA
TRC0107.TFF TRC0107.TF_ 16 06/08/1999 08:42 4563 B222279D
TRC0108.TFF TRC0108.TF_ 16 06/08/1999 08:42 9607 DD254B29
TRC0109.TFF TRC0109.TF_ 16 06/08/1999 08:42 2774 1561DBBE
TRC010A.TFF TRC010A.TF_ 7 06/08/1999 08:42 1080 C1985C66
TRC0118.TFF TRC0118.TF_ 16 04/26/1999 13:43 2526 46EFF705
TRC0119.TFF TRC0119.TF_ 16 06/08/1999 08:44 3786 6E0DFCCC
TRC012C.TFF TRC012C.TF_ 16 05/05/1999 14:15 5361 796B9436
TRC012D.TFF TRC012D.TF_ 16 05/05/1999 14:15 7870 F9F5F2E5
TRC012E.TFF TRC012E.TF_ 16 04/13/1999 10:22 32972 8DB44A12
TRCFORMT.DLL TRCFORMT.DL_ 15 04/01/1999 17:24 26645 34A6A109
TRCUST.EXE TRCUST.EX_ 14 04/13/1999 13:07 99285 086A09BF
TRSPOOL.DOC TRSPOOL.DO_ 16 04/01/1999 14:23 6638 7C5EE1B2
TRSPOOL.EXE TRSPOOL1.EX_ 15 02/05/1999 16:23 27982 7BD31091
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 03/15/1999 18:36 128695 E483A9B8
UA.KBL UA.KB_ 16 04/09/1999 15:34 1476 159E0855
UCDFS.DLL UCDFS.DL_ 16 10/21/1996 09:24 13264 C114CE18
UCONV.DLL UCONV.DL_ 15 04/09/1999 15:32 22819 468668C3
UHPFS.DLL UHPFS.DL_ 13 04/26/1999 13:44 104976 EF31C2F0
UK.KBL UK.KB_ 16 04/09/1999 15:34 816 F547878F
UK168.KBL UK168.KB_ 16 04/09/1999 15:34 850 9E48A829
ULSACT01.MSG ULSACT01.MS_ 6 04/09/1999 15:34 907 D7B874D3
ULSCAU01.MSG ULSCAU01.MS_ 3 04/09/1999 15:34 899 5EAC12BC
ULSDET01.MSG ULSDET01.MS_ 1 04/09/1999 15:34 903 74D4E3DC
ULSERR01.MSG ULSERR01.MS_ 16 04/09/1999 15:34 1967 31C19CA7
FixPak Corrective Service levels and disk layouts 48
July 1, 1999 - Warp 4 FixPak XR_M011
UNINSTAL.EXE UNINSTAL.EX_ 12 04/13/1999 12:31 99593 4871639A
UNPACK2.EXE UNPACK2.EX_ 14 04/13/1999 12:41 79792 4A84FBBE
USER.EXE USER.EX_ 9 03/09/1999 11:51 280976 36556E18
USINTER.KBL USINTER.KB_ 16 04/09/1999 15:34 1032 487BEDB9
VBIOS.SYS VBIOS.SY_ 16 04/01/1999 17:25 8816 9444ED6A
VCMOS.SYS VCMOS.SY_ 16 09/24/1998 09:50 2272 55C71989
VDMA.SYS VDMAPS2.SY_ 16 04/01/1999 17:25 14329 D644BA90
VDMA.SYS VDMAAT.SY_ 16 11/23/1998 17:38 11465 50D5B07B
VDPMI.SYS VDPMI.SY_ 16 09/24/1998 09:51 30624 F1E303B1
VDPX.SYS VDPX.SY_ 16 04/01/1999 17:25 26112 E1B5202E
VGA.DSP VGA.DS_ 16 05/05/1998 01:48 3094 4C806174
VIEW.EXE VIEW.EX_ 15 04/13/1999 16:04 26828 6911B747
VIOCALLS.DLL VIOCALLS.DL_ 13 09/25/1998 11:16 2048 336643CA
VIOTBL.DCP VIOTBL.DC_ 15 04/09/1999 15:36 225355 4079E89E
VIOTBL.ISO VIOTBL.IS_ 15 04/09/1999 15:36 230105 2F80D21C
VMAN.DLL VMAN.DL_ 15 04/07/1999 21:39 26637 EC69F3C3
VMANWIN.SYS VMANWIN.SY_ 16 04/07/1999 17:40 3024 BCD10A9A
VPICPARM.SYS VPICPARM.SY_ 11 09/24/1998 09:51 736 4EAC5451
VTIMER.SYS VTIMER.SY_ 16 09/24/1998 09:51 9936 DF6F879B
VW32S.SYS VW32S.SY_ 16 04/01/1999 17:26 18336 B5D35004
VWIN.SYS VWIN.SY_ 16 04/01/1999 17:26 27088 59687017
WCFGMRI.DLL WCFGMRI.DL_ 16 07/23/1998 19:04 2596 B73786AA
WD24B.DSP WD24B.DS_ 16 04/03/1997 13:55 12050 329F1B70
WINCFG.DLL WINCFG.DL_ 16 04/13/1999 10:27 12839 E21E0F7A
WINFILE.EXE WINFILE.EX_ 12 03/09/1999 11:41 146960 00D456E0
WINSCLIP.DLL WINSCLIP.DL_ 16 03/09/1999 11:38 14848 063E0448
WINSDDE.DLL WINSDDE.DL_ 16 03/09/1999 11:38 18432 A77BAF73
WINSHELD.EXE WINSHELD.EX_ 16 03/09/1999 11:38 22016 D0F12BEF
WINSMSG.DLL WINSMSG.DL_ 16 03/09/1999 11:37 28441 091BB9DC
WPCLS.IMP WPCLS.IM_ 16 03/31/1997 17:35 8661 DA24BBC2
WPCONFIG.DLL WPCONFIG.DL_ 8 04/13/1999 10:27 246078 626F15F6
WPCONMRI.DLL WPCONMRI.DL_ 15 07/23/1998 19:04 27694 4487233F
WPHELP.HLP WPHELP.HL_ 5 10/29/1997 16:28 841366 47FE7152
WPINET.DLL WPINET.DL_ 12 04/13/1999 10:55 115384 D7CE9EBA
WPMSG.HLP WPMSG.HL_ 6 12/16/1997 15:18 50198 9F1FBB75
WPPRINT.DLL WPPRINT.DL_ 2 04/13/1999 10:33 364008 D74B85F0
WPPRINT.HLP WPPRINT.HL_ 14 10/10/1997 05:48 71408 10006DCB
WPPRTMRI.DLL WPPRTMRI.DL_ 14 04/13/1999 10:33 66681 9CAB6A26
WPREXX.IMP WPREXX.IM_ 16 03/31/1997 17:35 6313 707B163F
WPSINIT.WPS WPSINIT.WP_ 14 03/31/1997 17:35 15877 ACC13319
WPSINST.CMD WPSINST.CM_ 16 05/06/1998 16:31 2813 4BAD1428
WW.EXE WW.EX_ 16 04/01/1997 15:37 8305 0B671079
WWDLL.DLL WWDLL.DL_ 4 12/21/1997 01:29 276981 751EB674
WWHOOK.DLL WWHOOK.DL_ 15 12/21/1997 01:29 27230 893E24E8
XCOPY.EXE XCOPY.EX_ 15 04/13/1999 13:00 51152 9F9E726F
************************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M011_ (Country = Generic)
FixPak Corrective Service levels and disk layouts 49
July 1, 1999 - Warp 4 FixPak XR_M011
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.___ 16 04/07/1999 09:25 33280 4DCE8447
************************************************************************
Product location on CSD: A:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
Fixpak name: XR_M011_ (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\*
Files contained in Fixpak for product:
FixPak Corrective Service levels and disk layouts 50
July 1, 1999 - Warp 4 FixPak XR_M011
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
APPDBUTL.DLL APPDBUTL.DL_ 16 09/24/1998 12:44 25013 B03740C5
APPSTART.EXE APPSTART.EX_ 16 09/24/1998 12:45 33864 F3D9B794
NCAPPUTL.EXE NCAPPUTL.EX_ 16 05/11/1998 10:54 12612 F048440D
OS2LDR OS2LDR.___ 16 04/07/1999 09:25 33280 6DA92137
PMLOGON.EXE PMLOGON.EX_ 16 09/24/1998 12:49 40107 6ECF0A76
PRNCFG.DLL PRNCFG.DL_ 16 09/24/1998 12:51 58258 1083DD95
TDESK.DLL TDESK.DL_ 16 09/24/1998 12:48 3769 CC72A5DC
TLOGOFF.EXE TLOGOFF.EX_ 16 09/24/1998 12:48 9577 DB742894
TOBJECT.DLL TOBJECT.DL_ 16 09/24/1998 12:48 4876 54B32CDC
TSHUTDWN.EXE TSHUTDWN.EX_ 16 09/24/1998 12:48 8611 BB45D1FD
FixPak Corrective Service levels and disk layouts 51
July 1, 1999 - Warp 4 FixPak XR_M011
11.0 SPACE UTILIZATION
The FixPak installation process requires free space on the following
drives:
Space needed Drive
Up to 2MB C:
Up to 2MB Boot drive (4MB if boot is C:)
Up to 22MB Drive with most free space, holds deferred files if
A:SERVICE method used.
Up to 35MB FixPak Archive/Backup for product with CSD level of
XR_4000
Up to 34MB 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.
11.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE
Warning: Make sure you read and understand the following before removing
the Archive and Backup files and directories.
You can recover the space used for FixPak Archive and Backup files as
long as you understand that doing this prevents you from being able to
backout to the previous Backup or Archive level. If it becomes necessary
at a later time to backout a FixPak, the only way you can do this is to
reinstall Warp.
Do the following to delete the FixPak Backup and Archive files and remove
the files used by CSF to keep track of what service has been applied to
your system.
1. Delete every instance of the following files on your system
(search every drive and every directory they contain).
■ LOGF0000.* (can be OS2 or MPM)
■ LOGSTART.* (can be OS2 or MPM)
■ LOGARCH.* (can be OS2 or MPM)
■ CSF_*.*
■ FIXSTART
2. Delete the files in the FixPak Archive and Backup directories on
your harddisk.
3. Remove the FixPak Archive and Backup directories with the RMDIR
command.
Space Utilization 52
July 1, 1999 - Warp 4 FixPak XR_M011
11.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