home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 28 Fixes4x
/
28-Fixes4x.zip
/
xr_m013.1dk
/
README.1ST
< prev
next >
Wrap
Text File
|
2000-04-03
|
138KB
|
3,476 lines
< Installation instructions for Warp 4 FixPak XR_M013
April 3, 2000
This FixPak makes the products it services Year 2000 ready
Build level 14.040
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.142 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
April 3, 2000 - Warp 4 FixPak XR_M013
April 3, 2000 - Warp 4 FixPak XR_M013
Page ii
April 3, 2000 - Warp 4 FixPak XR_M013
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3
3.0.1 Suspend/Resume Hang . . . . . . . . . . . . . . . . . . . . 3
3.0.2 Warp 4 Revision number changed . . . . . . . . . . . . . . . 3
3.0.3 Changes you may see due to source convergence . . . . . . . 3
3.0.4 Security Applications Work Around . . . . . . . . . . . . . 4
3.0.5 Cannot install on WSoD Release 2 . . . . . . . . . . . . . . 4
3.0.6 New PopUps During FixPak 12 Install . . . . . . . . . . . . 4
3.0.7 Device Drivers removed from Fixpak . . . . . . . . . . . . . 4
3.0.8 Can't install Warp 4 . . . . . . . . . . . . . . . . . . . . 4
3.0.9 Please use Fixtool f.142 or later . . . . . . . . . . . . . 5
3.0.10 OS2DUMP split into two versions . . . . . . . . . . . . . . 5
3.0.11 TRAP in ES16881$ after FP10 applied . . . . . . . . . . . . 6
3.0.12 System Sounds not working after FixPak applied . . . . . . 6
3.0.13 Using Display Recovery Choices . . . . . . . . . . . . . . 7
3.0.14 Installation of Java 1.1.4 . . . . . . . . . . . . . . . . 7
3.0.15 DSPRES.DLL included in this FixPak . . . . . . . . . . . . 7
3.0.16 No products found . . . . . . . . . . . . . . . . . . . . . 8
3.0.17 Previous installation interrupted . . . . . . . . . . . . . 8
3.0.18 Unable to open Archive directory . . . . . . . . . . . . . 9
3.0.19 RC 932 doing CID install of Warp 4 . . . . . . . . . . . . 9
3.0.20 Multimedia no longer selectable . . . . . . . . . . . . . 10
3.0.21 MMPARTS.DLL/USER.EXE popup during install . . . . . . . . 10
3.0.22 CSF0208 No products were found on the target ... . . . . 11
3.0.23 CSF0248 Archive path is shared between mismatched . . . . 11
3.0.24 CSF0249 Error opening or creating archive file. . . . . . 11
3.0.25 Printer installation process change . . . . . . . . . . . 11
3.0.26 Configuration Installation Distribution ( CID ) . . . . . 12
4.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 13
4.0.1 Print Screen SET parameter for APAR JR11837 . . . . . . . . 13
4.0.2 New Message Box in fix for APAR JR12954 . . . . . . . . . . 13
4.0.3 RAS file changes . . . . . . . . . . . . . . . . . . . . . 13
4.0.4 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 14
4.0.5 Windows printer drivers leave a zombie thread running . . . 14
4.0.6 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . . . . 15
4.0.7 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . . . 15
4.0.8 Intermittent hangs . . . . . . . . . . . . . . . . . . . . 15
5.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1 New RAS Utilities added . . . . . . . . . . . . . . . . . . . . 16
5.2 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 16
5.3 Querying file dates for files after Dec 31, 1999 in REXX . . . 17
5.4 Enhanced support for Workspace On-Demand . . . . . . . . . . . 17
5.4.1 PMLOGON user exits . . . . . . . . . . . . . . . . . . . . 17
Contents iii
April 3, 2000 - Warp 4 FixPak XR_M013
5.4.2 Setup strings for public applications . . . . . . . . . . . 20
5.4.3 Command line options for TLOGOFF and TSHUTDWN . . . . . . . 21
5.4.4 PMLOGON No Progress Indicator option . . . . . . . . . . . 21
5.4.5 PMLOGON No System Modal Window option . . . . . . . . . . . 22
5.5 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.5.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 22
5.5.2 Where Euro is not supported . . . . . . . . . . . . . . . . 23
5.5.3 Printing the Euro . . . . . . . . . . . . . . . . . . . . . 24
5.6 New Warp Registry Editor . . . . . . . . . . . . . . . . . . . 24
5.7 WorkSpace On Demand . . . . . . . . . . . . . . . . . . . . . . 24
5.8 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.9 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 25
5.10 Joliet-2 support in CDFS.IFS . . . . . . . . . . . . . . . . . 25
5.11 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 25
5.11.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 25
5.11.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 27
5.12 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 28
5.12.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 28
5.12.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.12.3 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.12.4 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.13 REXX New Fuction . . . . . . . . . . . . . . . . . . . . . . . 30
5.14 Other README files . . . . . . . . . . . . . . . . . . . . . . 30
6.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 31
6.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 31
6.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 31
6.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 32
6.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . . . . 32
6.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 33
6.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 33
6.4 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 34
7.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 36
7.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 36
7.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 36
7.3 Method 2: Install from alternate bootable media . . . . . . . . 37
7.4 Additional Corrective Service Facility information . . . . . . 38
7.5 FixPaks on CD-ROM . . . . . . . . . . . . . . . . . . . . . . . 38
8.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 39
8.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 40
9.0 FixPak Corrective Service levels and disk layouts . . . . . . . 41
10.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 56
10.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 56
10.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 57
Contents iv
April 3, 2000 - Warp 4 FixPak XR_M013
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_M013 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_M013 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
April 3, 2000 - Warp 4 FixPak XR_M013
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
April 3, 2000 - Warp 4 FixPak XR_M013
3.0 INSTALLATION NOTES
3.0.1 SUSPEND/RESUME HANG
There is a known problem with suspend/resume on Thinkpads (or anything
else that uses APM). The problem appears to be an interaction between the
OS/2 kernel and the APM.SYS device driver. The workaround is to rem out
APM.SYS and VAPM.SYS from CONFIG.SYS. We plan to release an interim fix
for this problem as soon as a solution is found.
3.0.2 WARP 4 REVISION NUMBER CHANGED
As of FixPak XR_M013 we've converged the souce lines with Warp Server for
e-business. This is what causes the initial boot screen to display as
14.040_W4 and the internal version to be reported as 4.50 as well. Some
program might interpret this as you not running the correct version of
OS/2.
If this occurs, please use OS2VER to set the proper version number to be
reported to the program.
To do so, you must edit a SYSTEM HIDDEN READONLY file, OS2VER, in the
root of the boot drive. Then add a line in the format of 40=executable
file name and save the file and reset the attributes.
Note: To unhide the file OS2VER, perform the following steps:
1. Open an OS/2 window.
2. Change to drive letter where OS/2 is installed.
3. Enter "cd\" to get to the root directory.
4. Enter OS/2 command "attrib -s -h -r os2ver" to unhide OS2VER.
5. Edit OS2VER to add line above ; save
6. Enter OS/2 command "attrib +r +s +h os2ver" to hide OS2VER.
7. Reboot system.
3.0.3 CHANGES YOU MAY SEE DUE TO SOURCE CONVERGENCE
Due to the Source Line convergence for OS/2 Warp 4 with the Warp Server
for e-Business source code, you might see references to Warp Server for
e-business being reported by some device drivers or executables. This is
not a problem and may be ignored.
Installation Notes 3
April 3, 2000 - Warp 4 FixPak XR_M013
3.0.4 SECURITY APPLICATIONS WORK AROUND
Users of some security-related ISS (security) packages such as Utimaco's
SafeGuard Professional, will have to add a new line to config.sys:
■ FAKEISS=YES
This works around a limitiation of some legacy ISS drivers. This is not a
problem for the Tivoli ISS driver.
3.0.5 CANNOT INSTALL ON WSOD RELEASE 2
If you get a message stating "No products found to service" when trying
to install on WorkSpace on-Demand Release 2, you may have a corrupted
syslevel.os2 file. Copy the syslevel.os2 file from the installation CD
or from a working WSoD R2 system and retry the installation. Be sure to
use Fixtool 1.42 to service your WSoD R2 system. This will prevent the
syslevel.os2 file corruption. Previous versions of the Fixtool fail to
correct a problem with the previous CSD level field in the syslevel.os2
file.
3.0.6 NEW POPUPS DURING FIXPAK 12 INSTALL
If you get a popup for module VIOTBL.ISO, VIOTBL.DCP, BDIME.DLL, or
COUNTRY.SYS during installation of this FixPak, reply "OK" to replace
these modules with the ones in this FixPak.
3.0.7 DEVICE DRIVERS REMOVED FROM FIXPAK
Beginning with Warp 4 FixPak XR_M011 and Warp 3 FixPak 41, most OS/2
Device Drivers have been moved to a separate Device Driver FixPak. The
first
Device Driver FixPak, XR_D001, is now available where this FixPak is
available.
3.0.8 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.
Installation Notes 4
April 3, 2000 - Warp 4 FixPak XR_M013
3.0.9 PLEASE USE FIXTOOL F.142 OR LATER
Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
Corrective Service Facility f.142 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.142 you will get a "CSF0208 No
products were found on the target system to service" message.
3.0.10 OS2DUMP SPLIT INTO TWO VERSIONS
OS2Dump has been split into two versions. If you are installing this
fixpak on PS/2 model 9595 machines, use the version located on the last
fixpak diskette. Also, if you are running older hardware (486s or early
Pentiums), you may wish to use the OS2Dump located on the last fixpak
diskette.
We have encountered some problems with early implementations of the PCI
Bus BIOS extensions (INT 1A) on certain processors and BIOS levels. We
are not sure how many different machines and BIOSes are affected. We do
know many of the PS/2 model 9595s have the problem. The end result of
this is that the version of OS2Dump which supports PCI Bus machines does
not work on some older hardware. In order to continue to support the
full range of hardware that OS/2 runs on, we have divided OS2Dump into a
PCI version and an non-PCI version. If you are running fairly recent
hardware, the PCI version of OS2Dump will work on your machine whether or
not it has a PCI bus. All BIOS problems have been worked out.
To reiterate, the problem occurs only on older hardware. If you are
running a 486 or early Pentium (P60 or less), you may wish to use the
non-PCI version located on the last fixpak diskette. If you are running a
9595, you must use the non-PCI version located on the last fixpak
diskette.
If, after installing this FixPak, you encounter problems taking a
standalone dump and your system fits description above, perform the
following steps to install the non-PCI version of OS2DUMP located on last
disk of this FixPak:
1. Open an OS/2 window.
2. Change to drive letter where OS/2 is installed.
3. Enter "cd\" to get to the root directory.
4. Enter OS/2 command "attrib -s -h -r os2dump" to unhide OS2DUMP.
5. Enter "ren os2dump os2dump.pci"; save PCI version of OS2DUMP.
6. Insert last disk of FixPak in drive A.
7. Copy a:\os2dump
8. Enter OS/2 command "attrib +r +s +h os2dump" to hide OS2DUMP.
Installation Notes 5
April 3, 2000 - Warp 4 FixPak XR_M013
9. Reboot system.
3.0.11 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.
3.0.12 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
Installation Notes 6
April 3, 2000 - Warp 4 FixPak XR_M013
5. Repeat for each of the above files
6. Reboot your system. This resolved the problem on a TP760 and may also
resolve the problem on other hardware.
3.0.13 USING DISPLAY RECOVERY CHOICES
If you have the "Display Recovery Choices at each system startup"
function active on your system, you need to disable it before you apply a
FixPak if
■ The system is running
■ The boot partition will be serviced.
The problem with using this function is that the Corrective Service
Facility (CSF) updates the current CONFIG.SYS with entries to run the
Locked File Device Driver (LFDD) the next time you boot the system. This
is done to replace files that are currently in use (locked) by the
system.
The Recovery choices function replaces the current CONFIG.SYS with the
one that is associated with the recovery choice you select, wiping out
the LFDD entries. This means the LFDD does not run at boot time and the
deferred files will not get updated, therefore the FixPak does not get
completely applied.
Note: It is not necessary to disable this function if you install a
FixPak by booting from the CSF disks or from another OS/2 partition.
3.0.14 INSTALLATION OF JAVA 1.1.4
Installation of Java 1.1.4 on top of this FixPak will down-level portions
of the ULS support. If this occurs, Euro currency support will not work
correctly. To recover, re-install this FixPak. This will allow both Java
1.1.4 and Euro support to work correctly.
3.0.15 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.
Installation Notes 7
April 3, 2000 - Warp 4 FixPak XR_M013
3.0.16 NO PRODUCTS FOUND
If you see a "No products were found on the target system to service"
message while applying this FixPak, there is probably a mismatch between
the data in \OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this
FixPak.
Compare the data for the OS/2 Base Operating System from the SYSLEVEL
command output with the same values listed at the end of this document in
the "FixPak Corrective Service levels and disk layouts" section. They
must be identical.
If these values are correct, check for the following files on any OS/2
boot drive in the \OS2\INSTALL directory.
LOGF0000.OS2
LOGSTART.OS2
LOGARCH.OS2
Check for the following files in your MMOS2\INSTALL directory.
LOGF0000.MPM
LOGSTART.MPM
LOGARCH.MPM
Also check for the following file:
C:\CSF_SEL.000
If these files exist, rename them and try the FixPak installation again.
Delete the renamed files after the FixPak has been applied.
3.0.17 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
Installation Notes 8
April 3, 2000 - Warp 4 FixPak XR_M013
If any exist, rename them and try the FixPak installation again. Delete
the renamed files after the FixPak has been applied.
3.0.18 UNABLE TO OPEN ARCHIVE DIRECTORY
If you get a message about problems with the Archive directory (for
example, cannot find or unable to open), then the most probable cause is
that you applied a previous FixPak and have since deleted the FixPak
ARCHIVE or BACKUP directory.
To recover from this, follow the "No files to service" and "Previous
installation interrupted" steps listed above.
3.0.19 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
Installation Notes 9
April 3, 2000 - Warp 4 FixPak XR_M013
unpack a:\fix\os2.1\uhpfs.dl_ c:\tempwork
8. Make backup copies of CHKDSK.SYS, CHKDSK32.DLL and UHPFS.DLL from the
DISK_3 directory of your CID tree.
9. Copy CHKDSK.SYS from c:\tempwork to the DISK_3 directory of your CID
tree
10.Copy CHKDSK32.DLL from c:\tempwork to the DISK_3 directory of your CID
tree
11.Copy UHPFS.DLL from c:\tempwork to the DISK_3 directory of your CID
tree
12.Make a backup copy of the BUNDLE file on DISK_0
13.Copy DISK_0\BUNDLE c:\tempwork
14.Copy PACK2.EXE to c:\tempwork. If you don't have this file you can get
it using your Web browser from
ftp://ps.software.ibm.com/ps/products/os2/fixes/v4warp
15.PACK2 CHKDSK32.EXE bundle /H:\OS2\CHKDSK32.EXE /A
Note: This adds CHKDSK32.EXE to the bundle file. Enter "unpack bundle
/show" to verify it's really there.
16.Copy the updated BUNDLE back to the DISK_0 directory
17.Delete the c:\tempwork directory and files.
18.Copy the files SCSIADDS and PRESCHEK from DISK_4 to DISK_5.
19.Do the CID install
3.0.20 MULTIMEDIA NO LONGER SELECTABLE
IBM Multimedia Presentation Manager/2 (MPM) is now fully integrated into
the base OS/2. As part of this change, the \MMOS2\INSTALL\SYSLEVEL.MPM
file has been deleted. This means you will no longer see it as a
selectable entry in the Serviceable Products window when using the
A:SERVICE method of installation.
3.0.21 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL
If you get a popup about MMPARTS.DLL or USER.EXE during install, reply
"OK" to replace it.
Installation Notes 10
April 3, 2000 - Warp 4 FixPak XR_M013
3.0.22 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET ...
This means no SYSLEVEL files was found that had a CSD Level, COMPID,
Version and Type that matched any of the SYSLEVEL files supported by this
FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2
in the OS2/INSTALL directory on your boot drive. Compare this data with
the data contained in the README.1ST file on FixPak disk 1.
To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2
and copy SYSLEVEL.OS2 from your Warp 4 installation DISK 1.
3.0.23 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED
1. The Archive path you specified (or was previously specified) contains
files from a different release of OS/2. You need to specify a
different Archive path.
2. You have a bad SYSLEVEL.OS2 or SYSLEVEL.MPM file. Both must have the
same Current CSD Level, Version, Type and Component ID if you point
both Fixpak Archives to the same location.
Check \OS2\INSTALL\SYSLEVEL.OS2 and \MMOS2\INSTALL\SYSLEVEL.MPM. If
either is wrong, place the last FixPak disk in A: and run FIXSYSL.CMD
to correct SYSLEVEL.OS2 problems or SYSZMPM.CMD to fix SYSLEVEL.MPM
problems.
3.0.24 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.
Typically this means the FixPak Archive directory has been deleted but
the files that point to it still exist. You need to delete the
LOGF000.OS2 and LOGSTART.OS2 files from your OS2/INSTALL directory.
LOGSTART.OS2 has the R/O attribute set and it needs to be reset before
the file can be deleted. There may also be a LOGARCH.OS2 file that needs
to be deleted.
This can also occur for Multi Media Presentation Manager/2 (MMPM). You
would then need to delete the LOGF0000.MPM and LOGSTART.MPM files from
the \MMOS2\INSTALL directory and possibly LOGARCH.MPM if it exists.
3.0.25 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.
Installation Notes 11
April 3, 2000 - Warp 4 FixPak XR_M013
3.0.26 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )
Read the README.CID on Disk # 1 for an example of how to set up a
response file to do a CID install.
Installation Notes 12
April 3, 2000 - Warp 4 FixPak XR_M013
4.0 POST INSTALLATION NOTES
4.0.1 PRINT SCREEN SET PARAMETER FOR APAR JR11837
Add the following environment varible line to CONFIG.SYS to print active
window during Print Screen operation:
SET PM_PRINTSCREEN_ACTIVE_WINDOW=ON
The WINDOW with focus will print when a Print Screen operation is
initiated.
For the default Print Screen operatin, perform either of these steps:
Remove line "SET_PM_PRINTSCREEN_ACTIVE_WINDOW=ON" from CONFIG.SYS or
change the line to read:
"SET_PM_PRINTSCREEN_ACTIVE_WINDOW=OFF"
Note: System must be re-booted after any CONFIG.SYS changes.
4.0.2 NEW MESSAGE BOX IN FIX FOR APAR JR12954
With FixPak 10 installed, if you tried to create Utility Disks and
selected "Use files from hard disk if they exist" you would get a SYS3175
trap. This was caused by a much larger AIC7870.ADD file causing the
diskette to fill up before all files were copied to it.
With FixPak 11 you will now get a "Diskette Full" message box that says
"Remove unwanted files and press OK.".
This means you should delete from the diskette in your A: drive, files
that are not needed on your system. Good candidates for deletion are the
CD-ROM drivers and harddisk drivers you do not need. You can check
CONFIG.SYS in the root of your boot drive to see if a file is used. If
not it can be deleted.
When you delete a file, also delete or REM out that line in CONFIG.SYS on
the diskette in A:.
4.0.3 RAS FILE CHANGES
Beginning with FixPak 11, the following files are being added to the
\OS2\SYSTEM directory. If they also exist in the \OS2 directory you can
delete them as they are no longer needed there.
■ DTRACE.EXE
Post Installation Notes 13
April 3, 2000 - Warp 4 FixPak XR_M013
■ TRACEFMT.EXE
■ TRSPOOL.EXE
If you do not delete them from the \OS2 directory, they will be serviced
the same as the ones in the \OS2\SYSTEM directory to keep them current.
Also, the following files in the \OS2\SYSTEM\RAS directory can be deleted
as they have been superseded as shown:
File Superseded by
MDTRACE.doc DTRACE.DOC
MTRSPOOL.DOC TRSPOOL.DOC
4.0.4 SETTING IRQ9 PROCESSING IN CONFIG.SYS FOR VPIC.SYS
Some applications like PCAS (and some terminal emulators) have problems
sharing IRQ9 in a VDM. Since the DOS Virtual Device drivers are not
loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added
starting with Warp 3 FixPak 38 and Warp 4 FixPak 8.
To prevent sharing of IRQ9 in a VDM, add the following statement in
config.sys:
device=x:\os2\mdos\vpicparm.sys irq9_off
(x: is your OS/2 boot drive)
Next, in the settings for the program that requires exclusive access to
IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON.
When you next boot your system, VDMs will not share IRQ9.
4.0.5 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING
A problem occurs with some Windows printer drivers where a zombie thread
is left running after the program that loaded it is exited.
This does not occur when the program is run from a Seamless instance of
PROGMAN or from a Full Screen session because when these are exited the
whole WINOS2 Subsystem is exited.
This problem has been reported for the Adobe and Hewlett Packard Windows
printer drivers. To correct this problem for people running with these
drivers ONLY who have experienced symptoms such as:
■ exiting a program running seamlessly after printing or
■ setting up a printer and seeing the icon not being unhatched and/or
■ not being able to start another copy of the program
Post Installation Notes 14
April 3, 2000 - Warp 4 FixPak XR_M013
Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot*
section:
■ backgroundtasks=run_enum.exe,hpfbkg02.exe
then restart WINOS2.
Note: There may be other drivers that have the same problem. If you
experiences a similar problem with other drivers, please report it so the
correct SYSTEM.INI entry can be determined.
4.0.6 APAR JR09494 (TRAP EXITING WINOS2 WITH MWAVE AUDIO)
The fix for APAR JR09434 (trap exiting winos2 with MWAVE audio) requires
a new MWAVEVDD.SYS dated 11/96 or later. This file is available from the
IBM PC Company web site at http://www.pc.ibm.com.
4.0.7 SYS3170 INSTALLING LOTUS SMARTSUITE 96
A problem was discovered when attempting to install Lotus SmartSuite 96
with a early version of the Matrox video driver. A SYS3170 occurs after
pressing the button to start copying the files to the hard disk.
The problem does not occur with the current Matrox driver available on
the Web at
http://www.matrox.com/mgaweb/drivers/ftp_os2.htm
A work around that does not involve downloading files from the web, is to
switch your display driver to VGA during the install and after it has
completed, restore the Matrox driver.
4.0.8 INTERMITTENT HANGS
If you experience intermittent hangs of your system, check your LIBPATH
statement in CONFIG.SYS to see if SOM.DLL is in a directory other than,
and ahead of, OS2\DLL.
If yes, either change the LIBPATH statement to move the directory after
OS2\DLL or try renaming SOM.DLL to SOM.DLO.
One known cause of this is VisualAge C++. It has a version of SOM.DLL in
its DLL library and the installation puts this library ahead of OS2\DLL
in the LIBPATH statement.
Post Installation Notes 15
April 3, 2000 - Warp 4 FixPak XR_M013
5.0 NEW FUNCTION
It is our policy not to include new function in FixPaks. However, as with
any policy there may be exceptions. If any exception occurs in the
future, we will communicate them to you in this section of the
README.1ST.
5.1 NEW RAS UTILITIES ADDED
Two new RAS utilities are included for Pak 13: PSFILES.EXE and
PSSEMS.EXE.
PSFILES.EXE can dump out information about open files on the system. By
default, it dumps out the information for all processes. Alternately,
"PSFILES xxx" will dump out information for PID xxx (xxx is a hex number,
e.g. from PSTAT).
PSSEMS.EXE can dump out information about open 32 bit semaphores on the
system. By default it prints out all the shared (i.e. system-wide)
semaphores. Usage is: pssems [/n] [hex_pid | /a] ; where /n suppresses
shared semaphores and /a prints pruivate sems for all system processes.
Note: These RAS Utilities are added to the OS2 directory on your system.
5.2 SERVICEABILITY (RAS) ENHANCEMENTS
With FixPak 35 for Warp 3.0 and FixPak 10 for Warp 4.0 major enhancements
were provided to the system diagnostic tools (RAS Enhancements). They
provide major functional enhancements to the System Trace and Process
Dump facilities. Full details of these enhancements can be found in the
README.DBG file that will be found in the \OS2\INSTALL directory after
this FixPak is installed.
Other associated documentation may be found in:
■ OS2\SYSTEM\RAS\TRACE.DOC
■ OS2\SYSTEM\RAS\DTRACE.DOC
■ OS2\SYSTEM\RAS\PROCDUMP.DOC
■ OS2\SYSTEM\RAS\TRSPOOL.DOC
Always refer to README.DBG for details of any RAS enhancements delivered
with a FixPak.
New Function 16
April 3, 2000 - Warp 4 FixPak XR_M013
5.3 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX
Existing REXX functions return file dates with a two digit year only.
While these functions are Year 2000 tolerant (i.e. the results will be
correct for files dated after Dec 31, 1999) they require some additional
logic in existing programs to handle the returned date correctly when
they are compared with other file dates.
Since the output format of the existing functions could not be changed
for compatibility reasons, new options have been added to the REXX
interpreter to return file dates with the year formatted with 4 digits.
Two functions have been extended to support the new format. The syntax to
retrieve the file date in 4 digit format is as follows:
/********************************************/
/* Use STREAM QUERY TIMESTAMP to query file */
/* date in 4 digit format */
/********************************************/
Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP")
/***********************************************/
/* Use option "L" with SysFileTree to return a */
/* list of files with long date format */
/***********************************************/
Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
Call SysLoadFuncs
Call SysFileTree "C:\*.*", "Files", "L"
Do i = 1 To Files.0
Say Files.i
End
These extensions are available in both classic REXX and Object REXX on
OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these
extensions in your program you have to make sure that you are running the
right level of REXX
5.4 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND
5.4.1 PMLOGON USER EXITS
This function, provided by PMLOGON, allows system integrators to have
REXX code executed at specific points during the startup and logon
sequence. By default, user exits are disabled in PMLOGON.EXE. To enable
user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the
CONFIG.SYS file must be added. The /URX parameter specifies the location
and name of the user exit command file:
New Function 17
April 3, 2000 - Warp 4 FixPak XR_M013
Execution Parameter User Exit command file that will be
executed
------------------- -----------------------------------
/URX \OS2\PMLOGURX.CMD
/URX:<filename>.CMD <filename>.CMD located in one of the
locations specified by the PATH
environment variable
/URX:d:\<path>\<filename>.CMD d:\<path>\<filename>.CMD
The same command file is called for ALL user exits. The FIRST parameter
supplied to the command file indicates the exit that it is being called
for. The REXX command file is called for all these exits, even if it does
not need to process all of the exits. The REXX command file must be able
to return error free if it receives an exit number that it does not need
to handle. The following user exits are available:
New Function 18
April 3, 2000 - Warp 4 FixPak XR_M013
First Parameter Exit Description
--------------- ----------------
0 Executes ONCE per boot, before the requester
is started. There is no user logged on at this
time. This exit may return a string that is
processed exactly as the following execution
parameters set in RUNWORKPLACE of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately after the execution
parameters. See Note 2 below on /AUTO processing.
1 Executes ONCE per logon, after the requester
is started, but before logon occurs. There is no
user logged on at this time. This exit may return
a string that is processed exactly as the
following execution parameters set in RUNWORKPLACE
of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately before logon. See
Note 2 below on /AUTO processing.
2 Executes ONCE per logon, after the requester is
started and after logon occurs. There is a user
logged on at this time, but the Desktop has not
been started and the objects are not displayed.
No returns are processed.
3 Executes ONCE per logon, after the Desktop has
been started and the objects are created but not
currently displayed, but immediately before
control is passed to the Desktop. The icons are
fixed at this point. There is a user logged on
at this time. No returns are processed.
4 Executes immediately after a failed logon. The
second parameter passed to the exit contains the
return code from the logon API. This exit may
return a string that is processed exactly as the
execution parameters set in RUNWORKPLACE of
CONFIG.SYS for the following parameters only:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
This exit is processed immediately and logon is
retried with the new parameters regardless of
the /AUTO switch. See Note 2 below on /AUTO
New Function 19
April 3, 2000 - Warp 4 FixPak XR_M013
processing. If no string is returned, then the
normal logon failure or password expired message
box is displayed.
Note 1: The session environment for the REXX command file is that
of PMLOGON.EXE and, therefore, does not contain any input or
output facility. For example, "PULL" from the keyboard and
"SAY" to the console do not work.
Note 2: The /AUTO parameter is validated at every step (for example,
after command line processing, after exit 0 returns, and
after exit 1 returns). It is turned off if insufficient
information (such as no user ID) is provided at that stage
for an automatic logon. If the user ID is supplied by the
exit, that exit must also provide the /AUTO parameter in
order for an auto logon to work.
5.4.2 SETUP STRINGS FOR PUBLIC APPLICATIONS
The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific
Workplace Shell WPProgram setup strings that are provided when creating
public applications on the WorkSpace On-Demand Desktop. In particular,
the ICONPOS setup string can be defined for a public application so that
the Administrator can identify where application icons are placed on the
WorkSpace On-Demand Desktop.
When a WorkSpace On-Demand Administrator creates a public application, a
new environment variable must be added to the application to provide a
setup string. The parameter name is NCC_SETUP_POST and the parameter
value can consist of any of the setup strings specified below. Each
setup string consists of a KEYNAME, followed immediately by an equal
('=') sign and a VALUE. Multiple setup strings can be passed in the
NCC_SETUP_POST environment variable by separating each setup string with
a semicolon (';'). The creation of this parameter can be performed
either using the WorkSpace On-Demand Public Applications Notebook (on the
Parameters page) or using a Command Line Interface (CLI). The following
is an example of one parameter:
NCC_SETUP_POST=ICONPOS=10,10;
The NCC_SETUP_POST environment variable will be searched for when each
WorkSpace On-Demand public application is created. If it is found, its
value will be used when creating the public application on the WorkSpace
On-Demand Desktop.
The following KEYNAME values are permitted for setup strings:
New Function 20
April 3, 2000 - Warp 4 FixPak XR_M013
Keyname Value Description
------- ----- -----------
CCVIEW DEFAULT Specifies the default value for
concurrent views
YES Creates new views
NO Displays the open view
ICONFILE filename Sets the object's icon.
ICONPOS x,y Sets the initial icon position in
a folder. The "x" and "y" values
represent the position in the object's
folder in percentage coordinates.
ICONRESOURCE id,module Sets the object's icon. The "id"
is the icon resource ID in the dynamic
link library (DLL) "module."
Refer to the Workplace Shell Programming Reference for a description and
definition of the above setup strings.
Note: The NCC_SETUP_POST environment variable exists in the current
environment when the public application with which it is associated is
running.
5.4.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN
Three command line options have been added to both TLOGOFF.EXE and
TSHUTDWN.EXE:
1. /Q -- causes these programs not to display the UPM/LAN
copyright window.
2. /N -- causes no confirmation message boxes to be displayed.
Note: If these parameters are not capitalized, they are ignored.
5.4.4 PMLOGON NO PROGRESS INDICATOR OPTION
An execution parameter has been added to PMLOGON that causes the progress
indicator window not to be displayed during all of logon processing. That
parameter is /NOPI and can be specified only from the RUNWORKPLACE line
in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit,
it is ignored.
New Function 21
April 3, 2000 - Warp 4 FixPak XR_M013
5.4.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION
An execution parameter has been added to PMLOGON which prevents PMLOGON
from setting any of its windows to be system modal after user exit 1 is
executed on the first boot or anytime after a logoff. The parameter is
/NOSM1 and can only be specified from the RUNWORKPLACE line in
CONFIG.SYS. If /NOSM1 is returned as a parameter from a user REXX exit,
it is ignored.
5.5 EURO SUPPORT
The European Monetary Union is creating the Euro as a new common currency
for Europe. As part of this effort the European Commission has
introduced a new character which represents the Euro. This character
looks like an uppercase C with two horizontal lines through it. The Euro
will come into existence on January 1, 1999 for use in banking. Euro
notes and coins will be issued starting January 2002.
5.5.1 BASE OS/2 SUPPORT
The OS/2 basic support for Euro consists of adding the Euro character to
fonts, codepages, and keyboards. The Euro is added to all display and
ATM fonts and to the Times New Roman MT 30 TrueType font which is
available with Java 1.1. The Euro is added to all western European
keyboards and the US International keyboard. The Euro can be used in
base OS/2, Presentation Manager, and in DOS. The Euro is not supported
in WinOS2.
The Euro character is added to these OS/2 base and PM codepages:
850 0xD5 PC Latin 1 base + PM
857 0xD5 PC Turkish base + PM
1004 0x80 Windows Extended base + PM
1250 0x80 Windows Latin 2 PM
1251 0x88 Windows Cyrillic PM
1252 0x80 Windows Latin 1 PM
1254 0x80 Windows Turkish PM
1257 0x80 Windows Baltic PM
The Euro character is added to these fonts.
New Function 22
April 3, 2000 - Warp 4 FixPak XR_M013
Courier (bitmap)
Courier (ATM)
Helv (bitmap)
Helvetica (ATM)
System Monospace (bitmap)
System Proportional (bitmap)
System VIO (bitmap)
Times New Roman (ATM)
Times New Roman MT 30 (TrueType - Java 1.1)
Tms Rmn (bitmap)
WarpSans (bitmap)
The Euro character is added to these OS/2 keyboards:
Belgium be altgr-e
Canada ca altgr-e
Canadian French cf altgr-e
Denmark dk altgr-5
Finland su (fi) altgr-5
France fr altgr-e
Germany gr (de) altgr-e
Germany(453) de453 altgr-e
Iceland ic (is) altgr-5
Iceland 101 is458 altgr-5
Italy it altgr-5
Italy extended it142 altgr-5
Latin America la altgr-e
Netherlands nl altgr-e
Norway no altgr-5
Portugal po altgr-5
Spain sp (es) altgr-5
Sweden sv altgr-5
Swiss French sf altgr-e
Swiss German sg (sd) altgr-e
Turkey tr179 altgr-e
Turkey 440 tr440 altgr-e
UK uk altgr-4
UK 168 uk168 altgr-e
US International ux altgr-e
5.5.2 WHERE EURO IS NOT SUPPORTED
The Euro is not supported in WinOS2. This character is not supported in
the Windows-1252 codepage used in WinOS2. This character is not
available on the WinOS2 keyboards. This character is not available in
the WinOS2 supplied TrueType fonts:
New Function 23
April 3, 2000 - Warp 4 FixPak XR_M013
Arial (Windows TrueType)
Courier New (Windows TrueType)
The Euro is not in the 437 (US English) or 863 (Canadian French)
codepages. You must use codepage 850 to get the Euro. The Euro is not
on the US keyboard. You can use the US International (ux) keyboard
instead.
5.5.3 PRINTING THE EURO
Existing printers do not support the Euro in device fonts. You need to
select a font which is not mapped to a device font in order to print the
Euro. The Euro will print correctly on printers where the system fonts
are used. When there are problems, a dotless-i is normally printed
instead of the Euro.
For PostScript printers, it is necessary to disable device fonts to print
the Euro in one of the base PostScript fonts (Helvetica, Times Roman,
Courier). To do this:
1. Open the properties of the Printer object
2. Select the Print Driver tab
3. Select Job Properties
4. Select the Output tab
5. Deselect "Use printer device fonts"
5.6 NEW WARP REGISTRY EDITOR
See the README.REG file on the first FixPak disk for details.
5.7 WORKSPACE ON DEMAND
WorkSpace on Demand Release 1 is supported starting with FixPak 5
(XR_M005). WorkSpace on Demand Release 2 is supported starting with
FixPak 11 (XR_M011).
5.8 IBM OPEN32
This FixPak includes updates to the IBM Open32 Application Programming
Interfaces (APIs).
New Function 24
April 3, 2000 - Warp 4 FixPak XR_M013
5.9 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
Future updates for GRADD and other video drivers (when they are released)
will be found via the internet at:
■ http://service.software.ibm.com/pslaunch.html
5.10 JOLIET-2 SUPPORT IN CDFS.IFS
Joliet is a Microsoft extension to the ISO 9660 CD-ROM file system which
adds Unicode and longname support. Presently both Windows 95 and Windows
NT 4.0 support the Joliet-2 and Joilet-3 formats. Beginning with Warp 3
Fixpak 32 and Warp 4 Fixpak 4, you can enable the Joliet-2 support by
adding the '/w' option to the CDFS.IFS statement in CONFIG.SYS.
Joilet-3 format is not supported.
5.11 NEW (IMPROVED) CHKDSK
This version of CHKDSK offers significant improvements for High
Performance File System (HPFS) drives. CHKDSK now fixes all errors found
on HPFS drives in a single pass, operating faster, and with less memory
than previous versions. It contains better error detection and
correction algorithms, and creates a log file so service personnel can
determine what errors it found and how it corrected them. Finally, only
the amount of physical memory in your system limits the size of the
largest drive CHKDSK can check at boot time (autocheck).
Improvements in this version of CHKDSK are for HPFS drives only. No
changes occurred to checking File Allocation Table (FAT) drives. This
enhanced CHKDSK operates on IBM OS/2 Warp 3.0 and higher, including IBM
Warp 4, IBM Warp Server 4 and IBM Warp Server 4 SMP. This new CHKDSK
version will not run on version of OS/2 before OS/2 Warp 3.0.
5.11.1 USING THE NEW CHKDSK
The interface to CHKDSK remains CHKDSK.COM and PMCHKDSK. No changes
occurred to the CHKDSK command line parameters or messages.
The first time this version of CHKDSK runs on a fast formatted drive, it
will report harmless errors. These errors go away once CHKDSK is run
with the /F option.
Note: OS/2 Warp Install uses fast format.
New Function 25
April 3, 2000 - Warp 4 FixPak XR_M013
Unlike prior versions of CHKDSK, large drives ( > 8GB) may be autochecked
if sufficient memory is available. The amount of memory required can
vary between 16MB and 48MB depending on the size of the drive. To enable
the autochecking of large drives, the following line must be added to
your config.sys:
BASEDEV=CHKDSK.SYS
This device driver allows CHKDSK to access memory normally reserved for
the system during the boot process. Due to this, if CHKDSK has to use
this memory:
■ The memory will not be available for the system to use in completing
the boot process
■ Errors may occur later in the boot process.
Hence, the chkdsk.sys device driver is smart enough to recognize when
CHKDSK has used this reserved memory and will reboot the system
automatically after all HPFS drives have been checked. Since the drives
were checked before the reboot, CHKDSK will not have to check them after
the reboot and the system will boot normally.
Note: For those wishing to run unattended: In order to prevent the
system from pausing between autocheck and the reboot, we recommend that
the statement PAUSEONERROR=NO be in the CONFIG.SYS.
When you don't have enough physical (real) memory to autocheck large
drives, you must use virtual memory from SWAPPER.DAT. The technique is
to check the large drives between the time OS/2 starts and PM begins. To
start OS/2, the swap file and device drivers must reside on an unaffected
drive. The drives to be checked must not appear in the autocheck list in
the IFS statement for HPFS (or HPFS386).
This technique involves the following steps:
1. Remove the drive letter of the affected drive(s) from the autocheck
list in the IFS statement for HPFS (or HPFS386).
2. If you are using HPFS, add /QUIET to the IFS statement for HPFS.
3. If you are using HPFS386.IFS, add POPUPERRORS=NO below the
[filesystem] section of the HPFS386.INI file. Support for the
POPUPERRORS parameter requires OS/2 LAN Server FixPak IP08265 or
higher for LS 5.0 or FixPak IP08503 or higher for LS 5.1. In addition,
the POPUPERRORS parameter ONLY suppresses HFS0102 messages.
4. Add a CALL statement to your config.sys. This CALL statement will
call CHKDSK.COM, and will tell it what drive to check. This CALL
statement must appear after the LIBPATH=, SET PATH=, and SET DPATH=
statements, but before any other CALL statements in your CONFIG.SYS
file.
New Function 26
April 3, 2000 - Warp 4 FixPak XR_M013
Calls to CHKDSK in STARTUP.CMD are not necessary, when using this method
or the base device driver (chkdsk.sys) method.
Example: The computer boots from drive C (moderate HPFS or FAT sized
drive). Drive D (large HPFS) requires more RAM to check than installed
in the machine.
Original IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:CD
New IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:C /QUIET
The CALL statement to use is:
CALL=C:\OS2\CHKDSK.COM D: /C
The /C option tells CHKDSK to check the drive only if it is "dirty" and
it needs checking.
If you need to boot from diskettes to check an HPFS drive, you must have
the following files on the diskette you wish to run CHKDSK from:
CHKDSK.COM
CHKDSK32.DLL
UHPFS.DLL
The BOOTDISK.EXE program has been updated to create new utility diskettes
with the proper files.
5.11.2 CHKDSK LOG FORMATTER
CHKDSK creates a binary service log file (chkdsk.log) on the root of the
drive being checked during autocheck or whenever the /F option is
invoked. The previous log file is saved as chkdsk.old. A formatter for
this log file can be found at:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe
This is a self extracting ZIP file. Place it in a directory in your path
and enter CHKLOGPK. This will create the following files:
New Function 27
April 3, 2000 - Warp 4 FixPak XR_M013
message.txt
msghdr.txt
pmchklog.exe
range.txt
readme
They should all have a date of 05/14/97 or later (May 14, 1997).
This is a tool used by OS/2 service to format and view the new CHKDSK log
entries. There is no support for this tool. You are welcome to use it
but if you have problems with it or do not understand the output DO NOT
contact IBM for assistance as none will be provided.
5.12 AUTOMATED TRAP SCREEN LOGGING
Whenever an application program traps, the trap information is (now)
automatically logged in the POPUPLOG.OS2 file. This is a cumulative file
that is by default located in the root directory of the bootable
partition. Should this file become too large then it may be erased or
pruned (reduced in size). The system will automatically re-create it if
it does not exist.
The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used
to control trap screen behavior (see below).
5.12.1 SUPPRESSPOPUPS
SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior. That
is, to disable logging and to have trap screens displayed unless
specifically overridden by an application's use of the DosError API.
SUPPRESSPOPUPS=x: will disable trap screen display for all processes and
will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or
partition.
If SUPPRESSPOPUPS is omitted then the behavior is as described above
under "Automated Trap Screen Logging".
5.12.2 TRAPLOG
The TRAPLOG command allows dynamic control of trap information logging.
The command syntax is:
TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]
New Function 28
April 3, 2000 - Warp 4 FixPak XR_M013
where:
■ x: specifies that trap information is to be logged in
x:\POPUPLOG.OS2, x: being any partition drive letter.
■ NOLOG disables logging of trap information.
■ POPUPS enables the trap information pop-up message (SYS3175).
■ NOPOPUPS disables the trap information pop-up message.
5.12.3 TRAPDUMP
The TRAPDUMP command allows the conditions under which a trap will
initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak
29, the System Dump setting could only be manipulated from CONFIG.SYS by
use of the TRAPDUMP statement.
Use of this command should be made under the direction of service
personnel.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred, thus under rare
circumstances data can be lost.
The command syntax is:
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]
where:
■ ON enables all application and system traps to initiate a System Dump.
■ OFF disables automatic dump initiation.
■ R0 enables only Ring 0 traps to initiate a System Dump.
■ x: specifies the Dump Partition.
■ NOCHECK overrides the system level check for WARP 4.0, since use of
this command on a system level prior to FixPak 29 is equivalent to the
SYSDUMP command.
5.12.4 SYSDUMP
The SYSDUMP command forces a System Dump to be initiated, regardless of
the TRAPDUMP settings. This command is provided for the use of service
personnel to allow Dump Initiation to be automated through use of a
command file.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
New Function 29
April 3, 2000 - Warp 4 FixPak XR_M013
The system behaves as if a fatal crash has occurred thus under rare
circumstances data can be lost.
The command syntax is:
SYSDUMP [/NOPROMPT]
where:
■ NOPROMPT allows the Dump to proceed without the prompt and response to
message:
"Do you want to force a system dump? (Y/N)"
5.13 REXX NEW FUCTION
New Function has been added in REXX. Please see the "Other README Files"
for documentation pointers. This new function was added to FP 13 and
later.
5.14 OTHER README FILES
There are other README files containing information you may want to
review. All except README.DBG are found on the first FixPak disk and are
not copied to your system when the Fixpak is installed. README.DBG will
be copied to the \OS2\INSTALL directory during installation beginning
with Fixpak 10 and Fixpak 41.
File Use
README2 Problems fixed in each FixPak (APAR list)
README.CID Installing FixPaks via CID
README.REG Use of the Warp Registry Editor REGEDIT2.EXE
README.DBG Tips on debugging OS/2 Warp and details on the latest
Serviceability (RAS) Enhancements (3.0 and 4.0).
READREXX.TXT New RexxUtil Function documentation added in this FixPak.
New Function 30
April 3, 2000 - Warp 4 FixPak XR_M013
6.0 CORRECTIVE SERVICE FACILITY
6.0.1 REQUIRED CSF LEVEL
You should use release level f.142 or later of the OS/2 Corrective
Service Facility to install this FixPak.
Bootable diskettes are no longer provided starting with the F.138B CSF
build. Instead, you now get a self-extracting ZIP file which contains the
following:
archctl.cmd
build.lvl
csfpans.dll
filefix.dll
fpinst.cmd
fservice.exe
fservice.msg
ibmcsflk.dll
ibmcsflk.exe
ibmcsflk.msg
ibmcsflk.sys
msg.dll
nls.dll
pack.exe
read.me
readme.inf
response.lan
response.wp3
response.wp4
service.exe
service.hlp
shpiinst.dll
unpack.exe
unpack2.exe
viocalls.dll
Follow the directions in the READ.ME file to use the new CSF code. It
covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
from one of several alternative boot methods.
6.0.2 WHERE YOU CAN FIND CSF CODE
The Corrective Service Facility code is available from many places,
including, but not limited to, the following:
Source How to access
Corrective Service Facility 31
April 3, 2000 - Warp 4 FixPak XR_M013
Internet(FTP) Anonymous FTP to ftp.software.ibm.com in the
"/ps/products/os2/fixtool" directory.
Internet(WWW) Point your Web Browser at
ftp://service.boulder.ibm.com/ps/products/os2/fixtool
Intranet(FTP) Anonymous FTP to os2service.austin.ibm.com in the
"f:\fixpacks\fixtool" directory.
6.0.3 CREATING FIXPAK DISKETTES
Use LOADDSKF.EXE to create the diskettes. For each disk image, place a
2MB HD (1.44MB formatted) diskette in A:.
Warning: DO NOT use a 1MB (720KB formatted) diskette because you might
have problems trying to install this FixPak.
For each diskette image in the FixPak, do the following:
Enter LOADDSKF XR_M013.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_M013
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through 35.
Examples:
XR_M013.ADK = 10
XR_M013.FDK = 15
XR_M013.LDK = 21
etc.
6.1 RESIDUAL FIXPAK FILES FROM OS/2 2.11 OR WARP 3
If the following is true:
1. You upgraded your system from OS/2 2.11 or Warp 3
2. You applied one or more FixPaks to the previous system
3. You HAVE NOT applied a Warp 4 FixPak
Corrective Service Facility 32
April 3, 2000 - Warp 4 FixPak XR_M013
You will have files and directories left on your harddisk that will cause
problems when installing a Warp 4 FixPak.
To prevent these problems from occurring, do the following before
applying your first Warp 4 FixPak.
On your Warp 4 boot drive:
■ Delete \OS2\INSTALL\LOGF0000.OS2
■ ATTRIB -R \OS2\INSTALL\LOGSTART.OS2
■ Delete \OS2\INSTALL\LOGSTART.OS2
On the drive where Multimedia Presentation Manager is installed:
Note: This can be your Warp 4 boot drive or any other drive on your
system. Check the "SET MMBASE=" statement in CONFIG.SYS to determine
which drive this is.
■ Delete \MMOS2\INSTALL\LOGF0000.MPM
■ ATTRIB -R \MMOS2\INSTALL\LOGSTART.MPM
■ Delete \MMOS2\INSTALL\LOGSTART.MPM
Remove the old Archive and Backup directories and SERVICE.LOG file to
recover the space they are using.
You should also remove the FixPak Archive and Backup directories left
over from your updated OS/2 2.11 or Warp 3 system at this time as well as
the \OS2\INSTALL\SERVICE.LOG file.
6.2 READ-ONLY FILES
Some files being updated by this FixPak may have the Read-Only attribute
set. If you are using the A:SERVICE method to install this FixPak you
will be asked if you want the files replaced.
Press the "OK" button.
6.3 SYSLEVEL FILE LOCATIONS
This FixPak will service directories based on the location of a supported
SYSLEVEL.OS2 file. Please check your system to make sure extra copies of
this file are not located in directories other than:
\OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)
If additional copies of these files are found in other locations on your
hard disk then CSF will try to service files as follows:
Corrective Service Facility 33
April 3, 2000 - Warp 4 FixPak XR_M013
For \OS2\INSTALL\SYSLEVEL.OS2
..\..\ all files in a directory two levels above (toward the
root). This should be the root directory of your boot
drive.
..\* all files in a directory one level above (toward the root)
and all subdirectories below. This should be the OS2
directory and subdirectories.
..\..\VT\* all files in the VT directory and subdirectories.
..\..\PSFONTS\* all files in the PSFONTS directory and subdirectories.
..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories.
..\..\OPENDOC\* all files in the OPENDOC directory and subdirectories.
6.4 RELOCATED OS/2 FILE SUPPORT
If you have moved OS/2 files or directories to a drive other than the one
the SYSLEVEL.OS2 file is on, do the following in order to have them
serviced:
■ Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
OS\2 Warp 4 partition to be serviced.
In this file, place the full path to the directories you want to be
serviced. Assuming your boot drive is C: and you installed Multimedia
on the D: drive and manually moved WINOS2 support to the E: drive:
Corrective Service Facility 34
April 3, 2000 - Warp 4 FixPak XR_M013
D:\MMOS2
D:\MMOS2\DLL
D:\MMOS2\DSP
D:\MMOS2\HELP
D:\MMOS2\IMAGES
D:\MMOS2\INETTEMP
D:\MMOS2\INSTALL
D:\MMOS2\MACROS
D:\MMOS2\MOVIES
D:\MMOS2\SOUNDS
D:\MMOS2\SOUNDS\DESKTOP
D:\MMOS2\SOUNDS\GARDEN
D:\MMOS2\SOUNDS\OCEAN
D:\MMOS2\SOUNDS\SPACE
E:\OS2\MDOS\WINOS2
E:\OS2\MDOS\WINOS2\SYSTEM
E:\OS2\MDOS\WINOS2\TEMP
Note: Leave this file for any future OS/2 Warp 4 FixPaks you might apply.
The easy way to create this file is to use the DIR command with the /A:D
/S /B parameters and pipe the output to a file.
dir d:\mmos2 /a:d /s /b > anyfile
Then copy that data into the USERDIRS.OS2 file.
With CSF release level F.137B or later, you can use wildcards, so your
USERDIRS.OS2 file would be much simpler and would look like:
D:\MMOS2\*
E:\OS2\MDOS\WINOS2\*
Corrective Service Facility 35
April 3, 2000 - Warp 4 FixPak XR_M013
7.0 INSTALLATION PROCESS
7.1 BEFORE INSTALLATION
Before installing any FixPak, run CHKDSK /F against all drives on your
system to correct any file system errors that might be present. You
cannot do this while OS/2 is active. You must shut down and run CHKDSK by
one of the following methods:
■ Boot from your Installation, DISK 1 and DISK 2 diskettes. If your
file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL
on it in your A: drive before issuing the CHKDSK command.
■ Boot from the Utilities disk you created via the "Create Utility
Diskettes" icon in the System Setup folder.
■ Boot from a different OS/2 partition.
Once CHKDSK has completed, reboot your system then shutdown all running
applications before starting the FixPak installation.
7.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
Note: CS_???.EXE below means CS_142 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_M013
Corrective Service Diskette 1 in drive A. Repeat for the rest of the
FixPak disks when requested to do so.
It can take a considerable length of time for the Corrective Service
Facility to scan your hard disk for serviceable files. In some cases, it
has taken as long as 40 minutes. Please be patient and allow this
process to complete.
If this is the first OS/2 Warp FixPak you have applied to this system,
then enter the path to the directory where a copy of replaced files will
be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)
Note: This ARCHIVE directory is not related to the ARCHIVES directory
built into OS/2 Warp 3 and Warp 4. Please specify a different path. You
must specify a different ARCHIVE directory for each product to be
serviced.
Installation Process 36
April 3, 2000 - Warp 4 FixPak XR_M013
If this is not the first OS/2 Warp FixPak, then enter the path to the
BACKUP directory where a copy of replaced files will be stored (for
example, D:\BACKUP).
Note: You must specify a different BACKUP directory for each product to
be serviced.
Make sure there is sufficient space available on the drive you specify
for archive or backup. Even though these files are kept in compressed
(PACK2) format, they can take up a lot of space on the drive.
During the installation process you may see messages about Archiving,
Updating and Deferring service.
■ Archiving saves a compressed copy of the original file in the ARCHIVE
or BACKUP path you specified.
■ Updating means the original files are replaced with the new ones from
this FixPak.
■ Deferring service means the file to be updated is currently in use by
the system and cannot be updated. The new files from the FixPak are
placed in unpacked format in the \IBMCSFLK\FIX directory on the drive
with the most free space. They are processed by the locked file
device driver during reboot after you shut down the system.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
You will see the following during reboot of the system if you applied
service to the OS/2 partition you were booted from.
The locked file driver is loaded.
Processing locked files
Processing complete
The system will do one automatic reboot after the Locked File Device
Driver has completed.
7.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA
Note: CS_???.EXE below means CS_142 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Installation Process 37
April 3, 2000 - Warp 4 FixPak XR_M013
Here are some additional notes:
This method does not prompt the user for any information. No interaction
with the user takes place other than requests to put the next diskette in
drive A. All serviceable partitions on your system will be updated
automatically unless you have modified the default response file. Be
especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
this method because they can cause CSF to apply service to directories
you do not want serviced.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. Please be
patient and allow this process to complete.
Note: You can edit the response file to control some of the actions taken
by FSERVICE.EXE while applying a FixPak. See the READ.ME file or use the
VIEW command to look at the file README.INF. They are part of
CS_???.EXE.
7.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility, like how to
backout a FixPak, is available from the README.INF file on the first
Corrective Service Facility disk. To view this file, place CSF disk 1 in
drive A and enter VIEW A:\README.INF.
There is also some additional information in the READ.ME file.
7.5 FIXPAKS ON CD-ROM
Both the IBM Technical Connection and the IBM Developer Connection
contain the latest OS/2 and LAN FixPaks that were available at publishing
time.
The IBM Technical Connection homepage on the World Wide Web is located
at:
■ http://www.ibm.com/Support/techconn/index.htm
The IBM Developer Connection homepage on the World Wide Web is located
at:
■ http://www.developer.ibm.com/devcon/titlepg.htm
Check these WWW sites for content and ordering information.
Installation Process 38
April 3, 2000 - Warp 4 FixPak XR_M013
8.0 CSD LEVEL OF SYSLEVEL.OS2
The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
partition will be updated with the name of the FixPak when it is applied.
This is a major change from previous CSF releases. The Prior CSD level
field will be left asis. This means when you use the SYSLEVEL command to
look at the release levels of products on your system, you will see the
following for SYSLEVEL.OS2.
Before a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR04000
Prior CSD level: XR04000
After a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0M008
Prior CSD level: XR04000
All fix information is recorded in SERVICE.LOG. Look at the file
\OS2\INSTALL\SERVICE.LOG
on your boot drive for information relating to the installation of
FixPaks on your system.
Additionally, you can use the VER /R command to see the current revision
of OS/2 installed. The response will look like the following for this
FixPak:
The Operating System/2 Version is 4.50
Revision 14.040
The first page of this document has a line that looks like:
Build Level: nn.nnn
CSD level of SYSLEVEL.OS2 39
April 3, 2000 - Warp 4 FixPak XR_M013
That is the number you should see for this FixPak when you issue the VER
/R command.
8.0.1 NEW SYSLEVEL.FPK
A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning with
XR_M004. It is titled "OS/2 Warp 4 Service Level". It contains the name
of the currently installed FixPak in both the Current and Previous CSD
level fields and is located in the same directory the SYSLEVEL.OS2 file
is located in which should be \OS2\INSTALL.
The easiest way to look at SYSLEVEL information is to use the SYSLEVEL
command and redirect the output to a file then edit the file and search
for SYSLEVEL.FPK.
CSD level of SYSLEVEL.OS2 40
April 3, 2000 - Warp 4 FixPak XR_M013
9.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 14.040
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M013_ (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_M013_ (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_M013_ (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 41
April 3, 2000 - Warp 4 FixPak XR_M013
..\..\OS2\INSTALL Stub File: @INSTDIR
..\..\OS2\APPS Stub File: @APPSDIR
..\..\OS2\SYSTEM\RAS Stub File: @RASDIR
..\..\OS2\SYSTEM\TRACE Stub File: @TRACDIR
..\..\LANGUAGE\CODEPAGE Stub File: @CDPGDIR
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
APPEND.EXE APPEND.EX_ 18 01/21/2000 10:43 7602 0FFA6ABA
ARACONV.EXE ARACONV.EX_ 15 11/23/1999 20:12 39927 79285D3C
ASIACOL.DLL ASIACOL.DL_ 11 12/02/1999 14:20 158758 1EC933A1
ASSIGN.COM ASSIGN.CO_ 18 01/21/2000 10:44 2684 0C1FE846
ATTRIB.EXE ATTRIB.EX_ 16 01/21/2000 10:44 37789 BAAFDFB9
AVIO.DLL AVIO.DL_ 15 02/08/2000 16:35 53925 B923490C
BACKUP.EXE BACKUP.EX_ 17 01/21/2000 10:53 35040 3D0F38CD
BDCALL32.DLL BDCALL32.DL_ 16 11/23/1999 20:11 33519 761AA009
BDIME.DLL BDIME.DL_ 17 11/23/1999 20:12 11911 652663B5
BDVIEW.DLL BDVIEW.DL_ 16 03/29/2000 09:04 34888 FF4C86C2
BDWPCLS.DLL BDWPCLS.DL_ 17 03/29/2000 09:03 20144 A5A0AB5E
BE.KBL BE.KB_ 18 12/02/1999 14:19 972 19CF6F43
BLDLEVEL.EXE BLDLEVEL.EX_ 15 03/01/2000 13:37 43986 1446FAE4
BOOTDISK.EXE BOOTDISK.EX_ 15 03/16/2000 08:20 65015 8EC9707B
BOOTDISK.HLP BOOTDISK.HL_ 18 03/15/2000 12:12 11831 8C7EA778
BVHINIT.DLL BVHINIT.DL_ 17 02/08/2000 11:03 11158 48EFF693
BVHMPA.DLL BVHMPA.DL_ 17 02/09/2000 11:36 15293 442B07F2
BVHVGA.DLL BVHVGA.DL_ 16 02/08/2000 11:04 31875 6908BDDD
BVHWNDW.DLL BVHWNDW.DL_ 17 02/08/2000 11:04 16803 7A2B0F8D
BVSCALLS.DLL BVSCALLS.DL_ 18 03/31/2000 08:44 512 9257EEBF
BY.KBL BY.KB_ 18 12/02/1999 14:19 1292 7D712D68
CA.KBL CA.KB_ 18 12/02/1999 14:19 1214 14E5D27D
CACHE.EXE CACHE.EX_ 17 02/16/2000 14:13 11822 2F082540
CARDINFO.DAT CARDINFO.DA_ 18 12/23/1999 12:44 54979 4547E040
CCHUSER.DLL CCHUSER.DL_ 14 02/22/2000 13:27 63731 A022B41B
CDFS.IFS CDFS.IF_ 16 02/16/2000 14:29 45197 55C1EC08
CDFS.TDF CDFS.TD_ 18 02/16/2000 14:29 2113 78118068
CDROM.TBL CDROM.TB_ 18 03/15/2000 09:36 4371 F176BE53
CF.KBL CF.KB_ 18 12/02/1999 14:19 956 B1186A3B
CHKDSK.COM CHKDSK.CO_ 15 01/21/2000 10:44 70720 77DCA279
CHKDSK.SYS CHKDSK.SY_ 18 02/16/2000 14:14 795 3BACB45C
CHKDSK32.DLL CHKDSK32.DL_ 12 02/16/2000 14:26 139227 FC293D21
CHKDSK32.EXE CHKDSK32.EX_ 18 02/16/2000 14:14 6417 4645BC60
CLOCK01.SYS CLOCK01.SY_ 18 01/28/2000 16:11 4588 C8194155
CLOCK02.SYS CLOCK02.SY_ 18 01/28/2000 16:11 4318 998906D8
CMD.EXE CMD.EX_ 13 01/21/2000 10:47 89888 B8C7C2DE
FixPak Corrective Service levels and disk layouts 42
April 3, 2000 - Warp 4 FixPak XR_M013
COMM.DRV COMM.DR_ 18 12/02/1999 17:56 9552 294235F2
COMMAND.COM COMMAND.CO_ 16 01/21/2000 10:46 42726 8BECAEDC
COMP.COM COMP.CO_ 16 01/21/2000 10:48 35881 DFCFA9EF
CONTROL.PM CONTROL.PM_ 18 03/15/2000 09:43 8474 EE521A82
COUNTRY.SYS COUNTRY.SY_ 17 01/21/2000 10:50 50947 191B6A0B
COUR.OFM COUR.OF_ 18 11/22/1999 11:22 6163 E932E1E2
COUR.PFB COUR.PF_ 10 11/22/1999 11:23 137111 48042447
COUR.PFM COU1.PF_ 18 11/22/1999 11:22 674 EB15F168
COURB.OFM COURB.OF_ 18 11/22/1999 11:22 6173 30B84A2B
COURB.PFB COURB.PF_ 10 11/22/1999 11:23 140829 503DA434
COURB.PFM COUR1.PF_ 18 11/22/1999 11:22 679 1EF9BF6B
COURBI.OFM COURBI.OF_ 18 11/22/1999 11:22 6187 0F6925D1
COURBI.PFB COURBI.PF_ 11 11/22/1999 11:23 136240 16421DEB
COURBI.PFM COURB1.PF_ 18 11/22/1999 11:22 685 50390DEF
COURI.OFM COURI.OF_ 18 11/22/1999 11:22 6178 31CF133A
COURI.PFB COURI.PF_ 10 11/22/1999 11:23 137394 714935E2
COURI.PFM COUR2.PF_ 18 11/22/1999 11:22 681 A6EEB6A2
COURIER.FON COURIER.FO_ 15 03/28/2000 14:05 77826 1916A760
COURIERI.FON COURIERI.FO_ 15 03/28/2000 14:00 86641 0B3CDE50
CPG01256.TBL CPG01256.TB_ 18 11/22/1999 12:17 27264 A51D21BD
CREX.MSG CREX.MS_ 18 11/22/1999 11:41 2865 809B8E0E
CREXUTIL.DLL CREXUTIL.DL_ 14 11/24/1999 11:10 68119 4D4A8CB7
CREXX.DLL CREXX2.DL_ 10 11/22/1999 11:40 266031 BFD32A5F
CYRIME.DLL CYRIME.DL_ 17 03/28/2000 13:44 21529 6A2F73B3
CZ.KBL CZ.KB_ 18 12/02/1999 14:19 1014 B5779C79
DDINSTAL.EXE DDINSTAL.EX_ 16 03/15/2000 11:57 35367 DE1B5076
DE.KBL DE.KB_ 18 12/02/1999 14:19 958 96D63DA3
DE453.KBL DE453.KB_ 18 12/02/1999 14:19 1354 B6DDCDA1
DEBUG.EXE DEBUG.EX_ 17 01/21/2000 10:48 27233 FB58A530
DF_DEB.EXE DF_DEB.EX_ 13 03/31/2000 09:25 137525 C320C960
DF_RET.EXE DF_RET.EX_ 13 03/31/2000 08:45 137493 F0A7EF0D
DIBDRVR.DLL DIBDRVR.DL_ 18 03/28/2000 14:05 5627 7A9A771B
DICTATE.EXE DICTATE.EX_ 15 05/06/1998 11:58 51391 460F01B4
DICTDLL.DLL DICTDLL.DL_ 15 12/21/1997 01:28 51187 2FAC90F6
DISKCOMP.COM DISKCOMP.CO_ 16 01/21/2000 10:53 41697 EFC726BF
DISKCOPY.COM DISKCOPY.CO_ 16 01/21/2000 10:54 46196 76A10E98
DISPLAY.DLL DISPLAY.DL_ 15 02/08/2000 10:53 46574 F71FEDF6
DIVE.DLL DIVE.DL_ 14 02/08/2000 14:15 69662 E2A3EEAF
DK.KBL DK.KB_ 18 12/02/1999 14:19 928 F1C631AE
DMISL.EXE DMISL.EX_ 13 02/16/2000 04:50 114198 6CBA2186
DMQSPROF.DLL DMQSPROF.DL_ 16 02/08/2000 11:02 39033 887F280C
DOSCALL1.DLL DOSCALL1.DL_ 8 03/31/2000 08:44 137513 A47A5979
DOSCALL1.SYM DOSCALL1.SY_ 16 03/31/2000 08:44 43636 7AFB8B45
DOSCALL1.TDF DOSCALL1.TD_ 18 03/31/2000 08:44 5534 938E92AE
DOSKEY.COM DOSKEY.CO_ 18 01/21/2000 10:48 6243 B655A811
DOSKRNL DOSKRNL.___ 17 03/31/2000 08:45 31497 B6919668
DRVMAP.INF DRVMAP.IN_ 18 03/15/2000 09:41 12986 0AD46334
DSPIMRI.DLL DSPIMRI.DL_ 17 02/08/2000 11:15 17446 A2D83DC6
DSPINSTL.EXE DSPINSTL.EX_ 12 02/09/2000 11:16 117976 044B0A24
DSPRES.DLL DSPRES1.DL_ 8 03/28/2000 14:00 376488 05A22B07
DSPRES.DLL DSPRES.DL_ 7 03/28/2000 14:00 376488 05EB6B07
FixPak Corrective Service levels and disk layouts 43
April 3, 2000 - Warp 4 FixPak XR_M013
DTRACE.DOC DTRACE.DO_ 17 11/22/1999 11:25 75371 58765F89
DTRACE.EXE DTRACE1.EX_ 15 02/16/2000 04:57 48906 DCCC0372
DTRACE.EXE DTRACE.EX_ 15 02/16/2000 04:57 48906 DCCC0372
E.EXE E.EX_ 14 03/15/2000 16:30 61159 8837D657
EAUTIL.EXE EAUTIL.EX_ 16 01/21/2000 10:48 38000 FEAF15D2
EDLIN.COM EDLIN.CO_ 18 01/21/2000 10:49 8348 8EF5F8F6
EHXDLMRI.DLL EHXDLMRI.DL_ 17 03/15/2000 16:30 13861 5293B907
EJECT.EXE EJECT.EX_ 17 01/21/2000 10:58 25650 37926995
EL.KBL EL.KB_ 18 12/02/1999 14:19 1396 AA77753C
EL459.KBL EL459.KB_ 18 12/02/1999 14:19 1372 B9F1C22A
ENGINE.EXE ENGINE.EX_ 3 07/23/1997 11:39 440424 CA47CBAA
EPM.EXE EPM.EX_ 17 11/23/1999 17:44 19680 EABCB32B
ERLOGGER.EXE ERLOGGER.EX_ 16 02/15/2000 11:46 34280 EC340C8E
ERRLOG.DLL ERRLOG.DL_ 14 02/15/2000 11:46 72806 D08B4384
ERRTXT.DLL ERRTXT.DL_ 17 03/15/2000 11:21 26714 7302FB5D
ES.KBL ES.KB_ 18 12/02/1999 14:19 920 9E1D8BDF
ETKC603.DLL ETKC603.DL_ 12 11/23/1999 16:02 136124 B18E8724
ETKE603.DLL ETKE603.DL_ 6 11/23/1999 16:02 767421 C1741876
EZP2MRI.DLL EZP2MRI.DL_ 15 02/22/2000 12:17 95262 B5D2EE01
FDISK.COM FDISK.CO_ 14 01/21/2000 10:56 114878 E2E9FD53
FDISKPM.DLL FDISKPM.DL_ 18 01/21/2000 10:56 10805 64BB655D
FDISKPM.EXE FDISKPM.EX_ 11 01/21/2000 10:56 63044 55C12B70
FDISKPMH.HLP FDISKPMH.HL_ 17 01/21/2000 10:56 14372 5E065EBB
FFCONFIG.DLL FFCONFIG.DL_ 17 02/15/2000 11:49 20551 0D5CCA25
FFDUMP.DLL FFDUMP.DL_ 15 02/15/2000 12:52 41217 D917D111
FFGUI.DLL FFGUI.DL_ 17 02/15/2000 11:49 18683 FC1C58D8
FFIPC.DLL FFIPC.DL_ 17 02/15/2000 11:49 27201 F8447B12
FFPCT.DLL FFPCT.DL_ 17 02/15/2000 11:49 21588 96F2178A
FFPROBE.DLL FFPROBE.DL_ 17 02/15/2000 12:19 24680 77EEA8E3
FFST.DLL FFST.DL_ 17 01/21/2000 14:58 11425 B9B2970A
FFSTCONF.EXE FFSTCONF.EX_ 14 02/15/2000 12:52 68781 D7CA7DCA
FFSTPCT.EXE FFSTPCT.EX_ 14 02/15/2000 12:52 69555 89C6901A
FI.KBL FI.KB_ 18 12/02/1999 14:19 940 6D323B78
FILT.DLL FILT.DL_ 17 02/08/2000 14:25 22890 9AD05FD8
FIND.EXE FIND.EX_ 17 01/21/2000 10:49 31085 9120676F
FKA.DLL FKA.DL_ 17 11/22/1999 11:46 13997 66CDC379
FORMAT.COM FORMAT.CO_ 15 01/21/2000 10:49 72064 FEF63CB6
FR.KBL FR.KB_ 18 12/02/1999 14:19 950 2F0602AF
FSFILTER.SYS FSFILTER.SY_ 17 03/31/2000 08:46 12714 6619DC78
GDI.EXE GDI.EX_ 10 12/02/1999 16:20 225776 8E4C9987
GRADD.SYS GRADD.SY_ 18 02/09/2000 11:57 2146 C85001C0
GRAFTABL.COM GRAFTABL.CO_ 18 01/21/2000 10:49 9648 EC8C71FC
GRE2VMAN.DLL GRE2VMAN.DL_ 17 02/09/2000 15:34 18221 0F347DED
GSVINST.EXE GSVINST.EX_ 16 03/15/2000 16:33 34351 DCF8E8EA
HARDERR.EXE HARDERR.EX_ 18 03/31/2000 08:44 14889 B26D4F19
HDMON.EXE HDMON.EX_ 14 02/15/2000 11:54 75047 0DF818C3
HELPMGR.DLL HELPMGR.DL_ 9 03/28/2000 14:02 250157 0A7799A7
HELPMSG.EXE HELPMSG.EX_ 16 01/21/2000 10:50 37280 5EF039F1
HELV.FON HELV.FO_ 11 03/28/2000 14:05 171252 6E13043B
HELV.OFM HELV.OF_ 18 11/22/1999 11:22 6793 C346E30D
HELV.PFB HELV.PF_ 11 11/22/1999 11:23 120578 FEA723CE
FixPak Corrective Service levels and disk layouts 44
April 3, 2000 - Warp 4 FixPak XR_M013
HELV.PFM HEL1.PF_ 18 11/22/1999 11:22 1096 C722994F
HELVB.OFM HELVB.OF_ 18 11/22/1999 11:22 6785 94469EB7
HELVB.PFB HELVB.PF_ 11 11/22/1999 11:23 123085 0037BF2B
HELVB.PFM HELV1.PF_ 18 11/22/1999 11:22 1089 DA484E9E
HELVBI.OFM HELVBI.OF_ 18 11/22/1999 11:22 6787 40A6DDD9
HELVBI.PFB HELVBI.PF_ 11 11/22/1999 11:23 124245 46A14EBC
HELVBI.PFM HELVB1.PF_ 18 11/22/1999 11:22 1087 06B4029D
HELVI.FON HELVI.FO_ 11 03/28/2000 14:00 199523 419B9D42
HELVI.OFM HELVI.OF_ 18 11/22/1999 11:22 6772 3B1391CD
HELVI.PFB HELVI.PF_ 11 11/22/1999 11:24 123355 48DC5DF0
HELVI.PFM HELV2.PF_ 18 11/22/1999 11:22 1079 4D475EFF
HPFS.IFS HPFS.IF_ 12 02/16/2000 14:11 141378 E8E239F9
HPFS.TDF HPFS.TD_ 18 02/16/2000 14:11 1620 57A464BE
HPMGRMRI.DLL HPMGRMRI.DL_ 17 03/28/2000 14:02 21881 523751BD
HR.KBL HR.KB_ 18 12/02/1999 14:19 982 F9ACC43A
HU.KBL HU.KB_ 18 12/02/1999 14:19 1006 B7E7BFEE
IBM1004 IBM1004.___ 18 12/02/1999 14:12 3584 7FAB8F9A
IBM1125 IBM1125.___ 18 12/02/1999 14:12 4320 49271362
IBM1131 IBM1131.___ 18 12/02/1999 14:12 4320 41CE38D2
IBM1140 IBM1140.___ 18 12/02/1999 14:12 2816 BA66925F
IBM1141 IBM1141.___ 18 12/02/1999 14:12 2784 DB6A6815
IBM1142 IBM1142.___ 18 12/02/1999 14:12 2816 683DBD10
IBM1143 IBM1143.___ 18 12/02/1999 14:12 2816 4CDFBBF1
IBM1144 IBM1144.___ 18 12/02/1999 14:12 2784 A4C542C0
IBM1145 IBM1145.___ 18 12/02/1999 14:12 2784 16F1A3EF
IBM1146 IBM1146.___ 18 12/02/1999 14:12 2816 E60B0DE2
IBM1147 IBM1147.___ 18 12/02/1999 14:12 2784 D809B1C2
IBM1148 IBM1148.___ 18 12/02/1999 14:12 2816 DBF5090C
IBM1250 IBM1250.___ 18 12/02/1999 14:12 3552 E5E3D8EF
IBM1251 IBM1251.___ 18 12/02/1999 14:12 3328 82754405
IBM1252 IBM1252.___ 18 12/02/1999 14:12 3552 9E4CF0CA
IBM1253 IBM1253.___ 18 12/02/1999 14:12 3552 22C6863B
IBM1254 IBM1254.___ 18 12/02/1999 14:12 3552 6E1AF660
IBM1255 IBM1255.___ 18 12/02/1999 14:12 3808 D4DB815C
IBM1256 IBM1256.___ 18 12/02/1999 14:12 4320 87492626
IBM1257 IBM1257.___ 18 12/02/1999 14:12 3296 71D045AE
IBM813 IBM813.___ 18 12/02/1999 14:12 3072 6FC3049A
IBM850 IBM850.___ 18 12/02/1999 14:12 4320 711A5C6A
IBM852 IBM852.___ 18 12/02/1999 14:12 4608 FD6091E2
IBM857 IBM857.___ 18 12/02/1999 14:12 4352 1C9CC3B1
IBM859 IBM859.___ 18 12/02/1999 14:12 4320 91237B25
IBM862 IBM862.___ 18 12/02/1999 14:12 4576 EFD40C60
IBM864 IBM864.___ 18 12/02/1999 14:12 4576 597C361B
IBM869 IBM869.___ 18 12/02/1999 14:12 4320 3121F46D
IBM923 IBM923.___ 18 12/02/1999 14:12 2784 6A67CBE9
IBM924 IBM924.___ 18 12/02/1999 14:12 2784 7CFE4155
IBMOPTNS.DLL IBMOPTNS.DL_ 17 12/23/1999 12:44 22330 03511AEC
ICONEDIT.EXE ICONEDIT.EX_ 13 11/23/1999 15:50 109536 A8A705F1
IFGDI2VM.DRV IFGDI2VM.DR_ 15 02/09/2000 11:38 93168 E4BA622F
INSCFG32.DLL INSCFG32.DL_ 13 03/15/2000 11:41 32530 6724883D
INST_DOS.EXE INST_DOS.EX_ 16 03/28/2000 14:00 36470 CD6C333F
FixPak Corrective Service levels and disk layouts 45
April 3, 2000 - Warp 4 FixPak XR_M013
INSTALL.EXE INSTALL.EX_ 7 03/22/2000 14:05 384264 EBFAEA4A
IOPROC.DLL IOPROC.DL_ 16 02/08/2000 16:36 37880 46AB6C09
IS.KBL IS.KB_ 18 12/02/1999 14:19 940 552D8147
IS458.KBL IS458.KB_ 18 12/02/1999 14:19 928 2234464B
ISGDI2VM.DRV ISGDI2VM.DR_ 15 02/08/2000 11:07 92048 817F9B62
IT.KBL IT.KB_ 18 12/02/1999 14:19 876 2AF0890D
IT142.KBL IT142.KB_ 18 12/02/1999 14:19 854 FF50CE82
JOIN.EXE JOIN.EX_ 18 01/21/2000 10:50 4520 DAF8AEF9
JPEGIO.DLL JPEGIO.DL_ 15 02/08/2000 16:37 44357 2FA1FFBD
KERNEL.SDF KERNEL.SD_ 14 03/31/2000 08:45 58993 74A81307
KERNELD.SDF KERNELD.SD_ 14 03/31/2000 08:45 59138 D982A1B5
KEYBOARD.DCP KEYBOARD.DC_ 17 12/02/1999 14:21 315109 639280C8
KRNLBDEV.TDF KRNLBDEV.TD_ 18 03/31/2000 10:18 4207 7D2A68A4
KRNLBFS.TDF KRNLBFS.TD_ 18 03/31/2000 10:18 4411 E7176424
KRNLBLDR.TDF KRNLBLDR.TD_ 18 03/31/2000 10:18 5334 0A1F0CB8
KRNLBPG.TDF KRNLBPG.TD_ 18 03/31/2000 10:18 3184 45544005
KRNLBSEL.TDF KRNLBSEL.TD_ 18 03/31/2000 10:18 2783 51DCDE9F
KRNLBSEM.TDF KRNLBSEM.TD_ 18 03/31/2000 10:19 1792 8E61811F
KRNLBSM.TDF KRNLBSM.TD_ 18 03/31/2000 10:19 1196 20C542BC
KRNLBTK.TDF KRNLBTK.TD_ 18 03/31/2000 10:19 12405 1A654D19
KRNLBTOM.TDF KRNLBTOM.TD_ 18 03/31/2000 10:19 1012 F04B41D7
KRNLBVDM.TDF KRNLBVDM.TD_ 18 03/31/2000 10:19 13167 E7BDB8E2
KRNLBVM.TDF KRNLBVM.TD_ 18 03/31/2000 10:19 5542 B27A5E44
KRNLDDEV.TDF KRNLDDEV.TD_ 18 03/31/2000 10:07 4182 BA48581D
KRNLDFS.TDF KRNLDFS.TD_ 18 03/31/2000 10:07 4302 92D05147
KRNLDLDR.TDF KRNLDLDR.TD_ 18 03/31/2000 10:07 5362 14D8BB4F
KRNLDPG.TDF KRNLDPG.TD_ 18 03/31/2000 10:07 3240 BA910D79
KRNLDSEL.TDF KRNLDSEL.TD_ 18 03/31/2000 10:07 2870 D8AE267B
KRNLDSEM.TDF KRNLDSEM.TD_ 18 03/31/2000 10:08 1932 A60DF1AE
KRNLDSM.TDF KRNLDSM.TD_ 18 03/31/2000 10:08 1221 170FDBAA
KRNLDTK.TDF KRNLDTK.TD_ 18 03/31/2000 10:08 12358 40ED6DEC
KRNLDTOM.TDF KRNLDTOM.TD_ 18 03/31/2000 10:08 1040 F4B28676
KRNLDVDM.TDF KRNLDVDM.TD_ 18 03/31/2000 10:08 13167 7F6873B8
KRNLDVM.TDF KRNLDVM.TD_ 18 03/31/2000 10:08 5629 D29B61EF
KRNLRDEV.TDF KRNLRDEV.TD_ 18 03/31/2000 09:12 4207 130F8CDB
KRNLRFS.TDF KRNLRFS.TD_ 18 03/31/2000 09:12 4411 942100CB
KRNLRLDR.TDF KRNLRLDR.TD_ 18 03/31/2000 09:12 5334 A05F2C95
KRNLRPG.TDF KRNLRPG.TD_ 18 03/31/2000 09:12 3184 44959306
KRNLRSEL.TDF KRNLRSEL.TD_ 18 03/31/2000 09:12 2783 D93EDF0E
KRNLRSEM.TDF KRNLRSEM.TD_ 18 03/31/2000 09:12 1792 3939482F
KRNLRSM.TDF KRNLRSM.TD_ 18 03/31/2000 09:12 1196 D396992F
KRNLRTK.TDF KRNLRTK.TD_ 18 03/31/2000 09:12 12321 942AC0BC
KRNLRTOM.TDF KRNLRTOM.TD_ 18 03/31/2000 09:12 984 31FA5513
KRNLRVDM.TDF KRNLRVDM.TD_ 18 03/31/2000 09:12 13027 C3127A23
KRNLRVM.TDF KRNLRVM.TD_ 18 03/31/2000 09:12 5542 E03286FE
LABEL.COM LABEL.CO_ 17 01/21/2000 10:54 33805 72B530CA
LFAPI.DLL LFAPI.DL_ 17 02/15/2000 11:46 21178 EEED1109
LIBCM.DLL LIBCM.DL_ 9 11/22/1999 11:45 210916 5BC599EE
LIBCN.DLL LIBCN.DL_ 15 11/22/1999 11:45 57340 693A0B04
LIBCS.DLL LIBCS.DL_ 10 11/22/1999 11:45 192386 7E2C4EA7
LIBUNI.DLL LIBUNI.DL_ 14 12/02/1999 14:22 81372 54DD2EB4
FixPak Corrective Service levels and disk layouts 46
April 3, 2000 - Warp 4 FixPak XR_M013
LMDLL.DLL LMDLL.DL_ 15 01/28/2000 16:16 76973 D22E54B0
LOCALE.DLL LOCALE.DL_ 13 12/02/1999 14:19 107901 0B97BACF
MAIN.CPL MAIN.CP_ 13 12/02/1999 16:32 147680 01DC3A80
MAKETSF.EXE MAKETSF.EX_ 16 02/16/2000 04:57 37516 04D70FA5
MAPTSF.CMD MAPTSF.CM_ 18 11/22/1999 11:25 16803 20CB489D
MEM.EXE MEM.EX_ 16 01/21/2000 10:57 39716 7DBA88D6
MIDI.SYS MIDI.SY_ 17 01/28/2000 15:34 26328 FA7B81A8
MIDIMCD.DLL MIDIMCD.DL_ 18 02/08/2000 14:17 4118 1A41C0C7
MIGRATE.EXE MIGRATE.EX_ 12 03/15/2000 12:09 118411 35742D19
MINSTALL.EXE MINSTALL.EX_ 11 12/23/1999 12:45 152582 377840C2
MINXOBJ.DLL MINXOBJ.DL_ 16 03/29/2000 09:13 31886 C9038041
MIRRORS.DLL MIRRORS.DL_ 7 11/22/1999 11:42 444744 4D936628
MMODPTS.DLL MMODPTS.DL_ 9 12/23/1999 12:37 184022 AF76CF61
MMPARTS.DLL MMPARTS.DL_ 2 02/08/2000 14:20 1532264 117EC463
MMPM.DLL MMPM.DL_ 7 02/08/2000 14:39 432015 C3520FF8
MMPTMRI.DLL MMPTMRI.DL_ 12 12/23/1999 12:35 229394 630AFE06
MMSNIFF.DLL MMSNIFF.DL_ 16 01/28/2000 16:04 33298 C3A3B23D
MMSOUND.DRV MMSOUND.DR_ 18 12/02/1999 16:48 3456 97C7C550
MODE.COM MODE.CO_ 14 01/21/2000 10:50 64245 214BC4BA
MONCALLS.DLL MONCALLS.DL_ 18 03/31/2000 08:44 2866 9AD3450D
MONCALLS.TDF MONCALLS.TD_ 18 03/31/2000 08:44 1139 4D67022B
MORE.COM MORE.CO_ 17 01/21/2000 10:50 34855 E1734E59
MPGIO.DLL MPGIO.DL_ 14 02/08/2000 16:37 59269 F03A1DE5
MSG.DLL MSG.DL_ 18 03/31/2000 08:44 512 88F1049E
NAMEADD.EXE NAMEADD.EX_ 17 11/24/1999 13:10 23040 3DC869A2
NAMECOPY.EXE NAMECOPY.EX_ 17 11/24/1999 13:10 23040 1C05214E
NAMEDEL.EXE NAMEDEL.EX_ 17 11/24/1999 13:10 23040 65C869A3
NAMEDSP.DLL NAMEDSP.DL_ 12 11/22/1999 11:43 123411 49573C12
NAMEEXT.EXE NAMEEXT.EX_ 17 11/24/1999 13:10 23040 9DC869A5
NAMEFW.DLL NAMEFW.DL_ 14 11/22/1999 11:43 72312 8C92E183
NAMEMOD.EXE NAMEMOD.EX_ 17 11/24/1999 13:10 23040 4DC869A3
NAMEMOVE.EXE NAMEMOVE.EX_ 17 11/24/1999 13:10 23040 2405214C
NAMEREXX.DLL NAMEREXX.DL_ 13 11/22/1999 11:43 97811 93EA370C
NAMPIPES.DLL NAMPIPES.DL_ 18 03/31/2000 08:44 1024 2472B80B
NL.KBL NL.KB_ 18 12/02/1999 14:19 954 87DF721D
NLS.DLL NLS.DL_ 18 03/31/2000 08:44 512 D1A5474F
NO.KBL NO.KB_ 18 12/02/1999 14:19 920 54ED10D3
NWIAPI.DLL NWIAPI.DL_ 17 02/14/2000 09:26 14770 B9DC9BAC
OREXUTIL.DLL ORXUTIL2.DL_ 16 11/24/1999 11:10 41175 9BC70D41
OREXX.DLL OREXX2.DL_ 6 11/24/1999 11:10 490355 38E00EB5
OS2CHAR.DLL OS2CHAR.DL_ 18 03/31/2000 08:44 512 1828B088
OS2CHAR.TDF OS2CHAR.TD_ 18 03/31/2000 08:44 13889 D839119A
OS2DASD.DMD OS2DASD.DM_ 16 01/28/2000 14:16 40910 33A26D1A
OS2DUMP OS2DUMP.___ 17 03/31/2000 09:13 15101 8F5406EA
OS2K386.EXE OS2K386.EX_ 14 12/02/1999 16:22 80306 CBDCD240
OS2KRNL OS2KRNL.___ 4 03/31/2000 09:12 824387 43BF77B8
OS2KRNLD.SYM OS2KRNLD.SY_ 12 03/31/2000 10:07 188132 73DFEAE3
OS2KRNLR.SYM OS2KRNLR.SY_ 12 03/31/2000 09:12 165924 F3907610
OS2KRNLR.TDF OS2KRNLR.TD_ 18 03/31/2000 09:12 16968 35DECBC5
OS2LDR.MSG OS2LDR.MS_ 18 03/28/2000 14:22 8926 E0415041
OS2MM.DLL OS2MM.DL_ 9 12/23/1999 12:45 219652 84ADE09E
FixPak Corrective Service levels and disk layouts 47
April 3, 2000 - Warp 4 FixPak XR_M013
OS2SM.DLL OS2SM.DL_ 18 03/28/2000 15:25 1598 870BD205
OS2UGL OS2UGL.___ 18 12/02/1999 14:12 15616 ACFC69CA
OSO001.MSG OSO001.MS_ 14 02/07/2000 16:02 175420 0B8808E8
OSO001H.MSG OSO001H.MS_ 13 02/07/2000 16:02 240278 F8C69AFB
PARALLEL.PDR PARALLEL.PD_ 17 02/22/2000 12:12 15850 0BC0126B
PCMCIA.TBL PCMCIA.TB_ 18 03/15/2000 09:33 1109 C9A65CA5
PDUMPSYS.EXE PDUMPSYS.EX_ 16 02/16/2000 05:03 34365 B4411E9E
PDUMPUSR.EXE PDUMPUSR.EX_ 16 02/16/2000 05:03 34363 D4DEC13F
PICV.DLL PICV.DL_ 17 03/28/2000 14:01 26200 594EEB53
PICVIEW.DLL PICVIEW.DL_ 17 03/28/2000 14:01 13858 2C0D7C04
PICVIEW.EXE PICVIEW.EX_ 14 03/28/2000 14:01 69658 55DDDE9B
PL.KBL PL.KB_ 18 12/02/1999 14:19 980 F2F990B5
PL457.KBL PL457.KB_ 18 12/02/1999 14:19 882 AECFD959
PMATM.DLL PMATM.DL_ 9 11/24/1999 12:23 224343 1C473B97
PMBIDI.DLL PMBIDI.DL_ 17 11/23/1999 20:11 13611 08D96136
PMCHKDSK.DLL PMCHKDSK.DL_ 18 01/21/2000 10:59 7199 E1E0969C
PMCHKDSK.EXE PMCHKDSK.EX_ 16 01/21/2000 10:59 28695 31222A25
PMCLIP.DLL PMCLIP.DL_ 17 03/28/2000 15:05 21249 D9224B6E
PMCTLS.DLL PMCTLS.DL_ 5 03/29/2000 06:13 588066 C8A3A1AF
PMCTLS.SYM PMCTLS.SY_ 16 03/29/2000 06:13 44660 BEA15352
PMDDE.DLL PMDDE.DL_ 17 03/29/2000 06:22 28332 35C19F1D
PMDDEML.DLL PMDDEML.DL_ 16 03/28/2000 14:50 27706 2A114A07
PMDF.EXE PMDF.EX_ 8 02/16/2000 05:02 262788 CA4FC698
PMDFMSG.DLL PMDFMSG.DL_ 15 02/15/2000 11:53 44516 953338C7
PMDRAG.DLL PMDRAG.DL_ 18 03/28/2000 13:50 1731 801F66B4
PMGPI.DLL PMGPI.DL_ 9 03/28/2000 13:39 248446 E728C79C
PMGPI.TDF PMGPI.TD_ 18 03/28/2000 13:39 12338 FD149677
PMGRE.DLL PMGRE.DL_ 18 03/28/2000 13:37 2231 B3BE2F7F
PMGRE.TDF PMGRE.TD_ 18 03/29/2000 06:14 1062 4AE99025
PMMERGE.DLL PMMERGE.DL_ 3 03/29/2000 06:14 1268435 BFFB6242
PMMERGE.SYM PMMERGE.SY_ 13 03/29/2000 06:14 117492 D31B1093
PMMLE.DLL PMMLE.DL_ 18 03/28/2000 15:30 673 7E270A51
PMMRGRES.DLL PMMRGRES.DL_ 13 03/28/2000 13:52 134144 B6AACABC
PMPIC.DLL PMPIC.DL_ 15 03/28/2000 14:01 47206 2171F653
PMPIC.TDF PMPIC.TD_ 18 03/28/2000 15:04 400 AAA2ACFB
PMPRE.DLL PMPRE.DL_ 15 02/08/2000 10:53 46574 37BEF4EA
PMPRINT.QPR PMPRINT.QP_ 17 02/22/2000 12:00 11835 46199027
PMREXX.EXE PMREXX.EX_ 9 03/01/2000 13:35 78885 610F908C
PMSDMRI.DLL PMSDMRI.DL_ 17 03/28/2000 13:49 15872 01B50293
PMSEEK.EXE PMSEEK.EX_ 16 01/21/2000 10:59 30773 ED363AA0
PMSHAPI.DLL PMSHAPI.DL_ 18 03/28/2000 13:47 4549 BDE5FDDF
PMSHAPI.TDF PMSHAPI.TD_ 18 03/29/2000 06:14 6726 159C5462
PMSHELL.EXE PMSHELL.EX_ 18 03/29/2000 09:10 6028 E72EFC61
PMSHLTKT.DLL PMSHLTKT.DL_ 16 11/22/1999 11:43 44232 A1C12E0F
PMSPL.DLL PMSPL.DL_ 8 02/24/2000 15:32 277251 7E020B83
PMSPL.SYM PMSPL.SY_ 17 02/24/2000 15:32 32340 4BBEA832
PMSPL.TDF PMSPL.TD_ 18 02/24/2000 15:32 4491 7AC9FF62
PMSPOOL.EXE PMSPOOL.EX_ 18 02/14/2000 09:25 8566 6F36C7D9
PMUNIF.DLL PMUNIF.DL_ 15 03/28/2000 14:01 43823 F89E4C46
PMVDMP.DLL PMVDMP.DL_ 15 03/28/2000 14:05 45317 0D175013
PMVDMP.TDF PMVDMP.TD_ 18 03/29/2000 06:22 2661 08022C24
FixPak Corrective Service levels and disk layouts 48
April 3, 2000 - Warp 4 FixPak XR_M013
PMVIOP.DLL PMVIOP.DL_ 14 03/28/2000 14:04 64204 8BCE47EA
PMVIOP.SYM PMVIOP.SY_ 18 03/28/2000 14:04 7620 59B39944
PMVIOP.TDF PMVIOP.TD_ 18 03/29/2000 06:22 3551 262BE6CD
PMWIN.DLL PMWIN.DL_ 18 03/28/2000 13:42 11264 898EE194
PMWIN.TDF PMWIN.TD_ 18 03/29/2000 06:14 9567 72CF29E6
PMWIN32.SDF PMWIN32.SD_ 16 03/28/2000 13:44 313392 B4B17F96
PMWINX.DLL PMWINX.DL_ 5 03/28/2000 14:00 530827 980645D5
PMWP.DLL PMWP.DL_ 1 03/29/2000 09:10 1063613 5BC4DA5A
PMWP.SYM PMWP.SY_ 14 03/29/2000 09:10 103780 322967BE
PMWP.TDF PMWP.TD_ 18 03/29/2000 09:10 13825 D2FF131A
PMWPMRI.DLL PMWPMRI.DL_ 15 03/15/2000 16:09 54311 05F999DA
PNP.DLL PNP.DL_ 15 03/29/2000 09:22 28297 9CADD035
PNP.SYS PNP.SY_ 18 01/28/2000 15:38 2152 ACA60D16
PNPMRI.DLL PNPMRI.DL_ 17 03/15/2000 16:20 31781 1AD3BEF1
PO.KBL PO.KB_ 18 12/02/1999 14:19 926 E96C77FF
PRINT.COM PRINT.CO_ 17 01/21/2000 10:50 34177 53518871
PROCDUMP.DOC PROCDUMP.DO_ 17 11/22/1999 11:25 62998 552CE87C
PROCDUMP.EXE PROCDUMP.EX_ 15 02/16/2000 05:03 47135 302327D1
PROGMAN.EXE PROGMAN.EX_ 15 12/02/1999 16:29 115328 99CE07B6
PSFILES.EXE PSFILES.EX_ 18 01/21/2000 10:50 8421 DA5EEF8A
PSSDMON.EXE PSSDMON.EX_ 16 01/04/2000 12:47 27117 E4D775F7
PSSEMS.EXE PSSEMS.EX_ 17 01/21/2000 10:50 9445 0B7A6BD0
PSTAT.EXE PSTAT.EX_ 17 01/21/2000 10:50 11189 747D55CA
QUECALLS.DLL QUECALLS.DL_ 18 03/31/2000 08:44 1024 A32D429E
QUECALLS.TDF QUECALLS.TD_ 18 03/31/2000 08:44 1299 34785685
RAS001.MSG RAS001.MS_ 17 01/21/2000 14:12 26260 E85AC6E9
RASH.MSG RASH.MS_ 18 01/21/2000 14:12 11856 5A823C88
README.CID README.CI_ 17 03/15/2000 09:42 48422 37B71502
README.DBG README.DB_ 18 11/22/1999 11:42 2463 324C4615
RECOVER.COM RECOVER.CO_ 16 01/21/2000 10:59 46656 6A44CD54
REGCONV.EXE REGCONV.EX_ 16 11/24/1999 13:02 39446 ED4551E8
REGEDIT.HLP REGEDIT.HL_ 17 12/02/1999 17:59 22682 FEEB2CA5
REGEDIT2.EXE REGEDIT2.EX_ 4 11/24/1999 13:10 949760 7EC2BD87
REGISTRY.DLL REGISTRY.DL_ 10 11/24/1999 13:02 81440 E24B1433
REGISTRY.MSG REGISTRY.MS_ 18 11/24/1999 13:10 629 E72A3620
REGISTRY.TDF REGISTRY.TD_ 18 11/24/1999 13:02 984 E7DBD05C
REPLACE.EXE REPLACE.EX_ 16 01/21/2000 11:00 41072 3D2D3148
RESTORE.EXE RESTORE.EX_ 17 01/21/2000 11:00 39232 25AC0244
REX.MSG REX.MS_ 18 11/22/1999 11:41 2865 5E61D657
REXX.DLL CREXX1.DL_ 10 11/22/1999 11:40 266031 33D48B8E
REXX.DLL OREXX1.DL_ 6 11/24/1999 11:10 490355 1A177246
REXX.IMG REXX.IM_ 14 11/24/1999 11:10 283636 D719F99D
REXXAPI.DLL REXXAPI.DL_ 17 11/22/1999 11:40 40995 0C93F324
REXXC.EXE REXXC.EX_ 18 11/24/1999 11:10 2758 D07F33FF
REXXCRT.DLL REXXCRT.DL_ 14 11/22/1999 11:40 80331 1BDB499A
REXXUTIL.DLL REXXUTIL.DL_ 14 11/24/1999 11:10 68119 4D4EA38F
REXXUTIL.DLL ORXUTIL1.DL_ 15 11/24/1999 11:10 41175 1BC741EF
RINSTPRN.EXE RINSTPRN.EX_ 10 02/22/2000 12:18 195012 637E4661
RMINFO.DLL RMINFO.DL_ 17 01/28/2000 14:09 23696 C93978B5
RO.KBL RO.KB_ 18 12/02/1999 14:19 944 AB98C941
RSPDDI.EXE RSPDDI.EX_ 17 03/15/2000 11:58 22585 D4B05396
FixPak Corrective Service levels and disk layouts 49
April 3, 2000 - Warp 4 FixPak XR_M013
RSPDSPI.EXE RSPDSPI.EX_ 13 02/09/2000 11:16 97222 6B76061E
RSPIMRI.DLL RSPIMRI.DL_ 6 02/08/2000 11:16 17455 301F32B6
RSPINST.EXE RSPINST.EX_ 8 02/29/2000 10:05 428896 B6D61CD4
RSRV.EXE RSRV.EX_ 13 11/22/1999 11:43 77955 3921E418
RU.KBL RU.KB_ 18 12/02/1999 14:19 1144 48A542E0
RXVIDCFG.DLL RXVIDCFG.DL_ 17 02/09/2000 11:37 14741 A1BDAF07
SBFILTER.DLL SBFILTER.DL_ 17 02/09/2000 11:39 14861 430E56B4
SCENTER.DLL SCENTER.DL_ 1 02/24/2000 15:46 293927 CAFE872B
SD.KBL SD.KB_ 18 12/02/1999 14:19 1036 6ED7C72E
SEAMLESS.DLL SEAMLESS.DL_ 16 03/29/2000 06:23 49167 4EA7F519
SECUTIL.DLL SECUTIL.DL_ 17 01/04/2000 12:47 21468 EE210C88
SEINST.EXE SEINST.EX_ 16 03/15/2000 11:44 37955 3B440D15
SEMAINT.EXE SEMAINT.EX_ 5 02/18/2000 16:54 67840 947EE32E
SERIAL.PDR SERIAL.PD_ 17 02/23/2000 11:52 19062 84CC03D0
SESAPI.DLL SESAPI.DL_ 17 01/04/2000 09:08 24203 6D54FAD7
SESDD32.SYS SESDD32.SY_ 14 01/04/2000 12:47 118834 8B2D1702
SESMGR.DLL SESMGR.DL_ 18 03/31/2000 08:44 1536 46610565
SESMGR.TDF SESMGR.TD_ 18 03/31/2000 08:44 1877 941F3F60
SETBOOT.EXE SETBOOT.EX_ 4 01/21/2000 10:56 20400 90EAE6F6
SETDEFV.CMD SETDEFV.CM_ 18 06/23/1998 16:25 1652 AA7ED9EC
SF.KBL SF.KB_ 18 12/02/1999 14:19 1036 304D8793
SHPIINST.DLL SHPIINST.DL_ 16 03/28/2000 16:50 37310 39E1BA43
SK.KBL SK.KB_ 18 12/02/1999 14:19 1008 41F7D014
SL.KBL SL.KB_ 18 12/02/1999 14:19 982 51F7B464
SOFTDRAW.DLL SOFTDRAW.DL_ 6 03/28/2000 13:33 416439 4C14D187
SOM.DLL SOM.DL_ 13 06/30/1999 16:33 92009 A7AC8E45
SORT.EXE SORT.EX_ 17 01/21/2000 10:51 32047 3EBB42F3
SPCHOBJ.DLL SPCHOBJ.DL_ 12 12/21/1997 01:27 132899 90045CF7
SPL1B.DLL SPL1B.DL_ 18 02/14/2000 09:25 7125 8590C44A
SPOOLCP.DLL SPOOLCP.DL_ 18 02/14/2000 09:38 10210 C716BF98
SQ.KBL SQ.KB_ 18 12/02/1999 14:19 824 4B34805A
SSM.DLL SSM.DL_ 18 02/08/2000 14:15 4118 21E0FD17
SSMDD.SYS SSMDD.SY_ 17 02/08/2000 14:15 36813 00B86BE2
STRACE.EXE STRACE.EX_ 15 01/21/2000 11:01 42967 71D98D58
SUBST.EXE SUBST.EX_ 18 01/21/2000 10:50 4520 5EF57ABF
SV.KBL SV.KB_ 18 12/02/1999 14:19 946 801D0FAB
SVMC.DLL SVMC.DL_ 13 02/08/2000 16:35 98391 96501EFC
SVSH.DLL SVSH.DL_ 17 02/08/2000 16:35 23454 2F16AC1B
SW.DLL SW.DL_ 14 02/08/2000 16:34 66505 A458FFD1
SWITCHRX.CMD SWITCHRX.CM_ 18 11/22/1999 11:41 7928 1FCA9FC0
SYMB.PFM SYM1.PF_ 18 11/22/1999 11:22 679 EAD8E0BD
SYSDUMP.EXE SYSDUMP.EX_ 17 02/16/2000 05:03 23581 32339E8D
SYSINST2.EXE SYSINST2.EX_ 12 02/29/2000 10:00 184512 17CDF6B5
SYSINSTX.COM SYSINSTX.CO_ 16 01/21/2000 10:51 40128 470095C4
SYSLEVEL.EXE SYSLEVEL.EX_ 16 02/18/2000 17:05 44976 B891F768
SYSLEVEL.FPK SYSLEVEL.FP_ 18 11/15/1999 15:37 165 3527E2F0
SYSLEVEL.MSG SYSLEVEL.MS_ 18 02/18/2000 17:05 1445 FA952C3F
SYSLOGPM.EXE SYSLOGPM.EX_ 12 02/15/2000 11:46 139231 09E80BFC
SYSMONO.FON SYSMONO.FO_ 17 03/28/2000 14:05 21294 E0186863
SYSMONOI.FON SYSMONOI.FO_ 16 03/28/2000 14:00 35841 D3DE340F
SYSSPLIT.CMD SYSSPLIT.CM_ 18 11/22/1999 11:25 3712 A30841C8
FixPak Corrective Service levels and disk layouts 50
April 3, 2000 - Warp 4 FixPak XR_M013
TDFLST.CMD TDFLST.CM_ 18 11/22/1999 11:25 13564 7B5F3592
TEDIT.EXE TEDIT.EX_ 17 01/21/2000 11:01 9390 4F62F6A4
TEDIT.HLP TEDIT.HL_ 18 01/21/2000 10:07 14596 AFE13771
TESTCFG.SYS TESTCFG.SY_ 18 01/28/2000 15:25 9808 F7E85604
TEXTCON1.EXE TEXTCON1.EX_ 16 11/23/1999 20:12 34083 CD5C696F
TFFLST.CMD TFFLST.CM_ 18 11/22/1999 11:25 4638 E2FE15D0
TIMES.FON TIMES.FO_ 12 03/28/2000 14:05 166150 1C9E9977
TIMESI.FON TIMESI.FO_ 11 03/28/2000 14:00 181173 39330866
TNR.OFM TNR.OF_ 18 11/22/1999 11:22 6809 F7F5154B
TNR.PFB TNR.PF_ 10 11/22/1999 11:24 145785 BD3CBE3E
TNR.PFM TN1.PF_ 18 11/22/1999 11:22 1103 4721CE38
TNRB.OFM TNRB.OF_ 18 11/22/1999 11:22 6825 76C21109
TNRB.PFB TNRB.PF_ 10 11/22/1999 11:24 148564 FD4AD0FF
TNRB.PFM TNR1.PF_ 18 11/22/1999 11:22 1112 60448943
TNRBI.OFM TNRBI.OF_ 18 11/22/1999 11:22 6839 8051C7B5
TNRBI.PFB TNRBI.PF_ 9 11/22/1999 11:24 159652 79893739
TNRBI.PFM TNRB1.PF_ 18 11/22/1999 11:22 1118 618A75CD
TNRI.OFM TNRI.OF_ 18 11/22/1999 11:22 6830 23B85DE2
TNRI.PFB TNRI.PF_ 9 11/22/1999 11:24 157010 5E813576
TNRI.PFM TNR2.PF_ 18 11/22/1999 11:22 1114 526E659D
TR.KBL TR.KB_ 18 12/02/1999 14:19 962 5DC99B6F
TR440.KBL TR440.KB_ 18 12/02/1999 14:19 1042 CD220063
TRACE.DOC TRACE.DO_ 17 01/21/2000 10:05 64057 45DDD515
TRACE.EXE TRACE.EX_ 16 01/21/2000 11:01 35328 55D997F7
TRACEDLL.DLL TRACEDLL.DL_ 15 02/16/2000 04:57 46987 A23413F0
TRACEFMT.EXE TRACEFMT.EX_ 11 01/21/2000 11:05 156571 16F92B6D
TRACEGET.EXE TRACGET1.EX_ 17 02/16/2000 04:57 22026 F16944AB
TRACEGET.EXE TRACEGET.EX_ 16 02/16/2000 04:57 22026 F16944AB
TRAPDUMP.EXE TRAPDUMP.EX_ 17 02/16/2000 05:03 23068 86D265D5
TRAPLOG.EXE TRAPLOG.EX_ 17 02/16/2000 05:03 22559 C9F24352
TRC0000.TFF TRC0000.TF_ 18 03/31/2000 09:11 189 4EDB25C1
TRC0001.TFF TRC0001.TF_ 18 11/24/1999 13:02 1370 17F81D51
TRC0003.TFF TRC0003.TF_ 18 03/31/2000 09:11 1503 8535868E
TRC0004.TFF TRC0004.TF_ 18 03/31/2000 09:11 4754 06CD826C
TRC0005.TFF TRC0005.TF_ 17 03/31/2000 09:12 39591 D7E635B8
TRC0006.TFF TRC0006.TF_ 18 03/31/2000 09:12 12356 81C0674E
TRC0007.TFF TRC0007.TF_ 18 03/06/2000 16:43 3336 6019D5C7
TRC0008.TFF TRC0008.TF_ 18 01/28/2000 14:07 544 472396D2
TRC0010.TFF TRC0010.TF_ 18 03/31/2000 08:44 13647 C636E43D
TRC0012.TFF TRC0012.TF_ 18 03/31/2000 08:44 1247 4B0FA0CD
TRC0016.TFF TRC0016.TF_ 18 03/31/2000 08:44 1673 8106BC80
TRC0017.TFF TRC0017.TF_ 18 03/31/2000 08:44 5561 FEB3BD26
TRC0018.TFF TRC0018.TF_ 18 03/31/2000 08:44 39488 7B261361
TRC006D.TFF TRC006D.TF_ 18 12/23/1999 12:43 24181 FB8B0C54
TRC00C0.TFF TRC00C0.TF_ 18 03/29/2000 06:14 15970 EE02FC65
TRC00C2.TFF TRC00C2.TF_ 17 03/29/2000 06:14 25994 8E380961
TRC00C3.TFF TRC00C3.TF_ 18 03/29/2000 06:14 3984 1EEF4A94
TRC00C4.TFF TRC00C4.TF_ 18 03/28/2000 15:04 288 624E3DA4
TRC00C5.TFF TRC00C5.TF_ 18 03/28/2000 13:39 32994 870D9AD8
TRC00C6.TFF TRC00C6.TF_ 18 02/24/2000 15:32 7146 F49BAD2D
TRC0100.TFF TRC0100.TF_ 18 03/31/2000 09:12 7153 82AB3B30
FixPak Corrective Service levels and disk layouts 51
April 3, 2000 - Warp 4 FixPak XR_M013
TRC0101.TFF TRC0101.TF_ 1 03/31/2000 09:12 7310 9DE98BED
TRC0102.TFF TRC0102.TF_ 18 03/31/2000 09:12 23821 314A4CA2
TRC0103.TFF TRC0103.TF_ 18 03/31/2000 09:12 9470 BCDC891D
TRC0104.TFF TRC0104.TF_ 18 03/31/2000 09:12 5075 9F651C0E
TRC0105.TFF TRC0105.TF_ 18 03/31/2000 09:12 22963 CF63767C
TRC0106.TFF TRC0106.TF_ 18 03/31/2000 09:12 1549 8736508F
TRC0108.TFF TRC0108.TF_ 18 03/31/2000 09:12 9505 A2F6DBC7
TRC0109.TFF TRC0109.TF_ 18 03/31/2000 09:12 2535 CF7CF990
TRC010A.TFF TRC010A.TF_ 18 03/31/2000 09:12 1130 4A88C17E
TRC0118.TFF TRC0118.TF_ 18 02/16/2000 14:13 2526 475CF705
TRC0119.TFF TRC0119.TF_ 18 02/16/2000 14:31 3786 6E21DCCC
TRC012C.TFF TRC012C.TF_ 18 03/29/2000 06:22 5361 796B92E8
TRC012D.TFF TRC012D.TF_ 18 03/29/2000 06:22 7870 F9F5F197
TRC012E.TFF TRC012E.TF_ 18 03/29/2000 09:10 32972 8DAFA212
TRCFORMT.DLL TRCFORMT.DL_ 17 01/21/2000 11:05 26647 57EF1397
TRCUST.EXE TRCUST.EX_ 15 01/21/2000 11:02 98773 190794C1
TREE.COM TREE.CO_ 17 01/21/2000 10:51 34185 A1D517F4
TRSPOOL.DOC TRSPOOL.DO_ 18 11/22/1999 11:25 6638 7C5EA5A2
TRSPOOL.EXE TRSPOOL1.EX_ 16 02/16/2000 04:57 27974 B84DF89E
TRSPOOL.EXE TRSPOOL.EX_ 16 02/16/2000 04:57 27974 B84DF85C
TRSTOP.EXE TRSTOP.EX_ 17 02/16/2000 04:57 17190 F6BF2AE3
TRUETYPE.DLL TRUETYPE.DL_ 12 11/24/1999 12:24 128695 4A283E78
UA.KBL UA.KB_ 18 12/02/1999 14:19 1476 FDE05051
UCDFS.DLL UCDFS.DL_ 17 02/16/2000 14:27 13264 C114D3AA
UCONV.DLL UCONV.DL_ 17 12/02/1999 14:21 22819 AAC74ECC
UHPFS.DLL UHPFS.DL_ 14 02/16/2000 14:26 104976 DB501EE0
UK.KBL UK.KB_ 18 12/02/1999 14:19 816 F2EA3FB9
UK168.KBL UK168.KB_ 18 12/02/1999 14:19 850 B439BA28
ULSACT01.MSG ULSACT01.MS_ 18 11/23/1999 13:33 907 CD00A341
ULSCAU01.MSG ULSCAU01.MS_ 18 11/23/1999 13:33 899 5B2CC12F
ULSDET01.MSG ULSDET01.MS_ 11 11/23/1999 13:33 903 A0B0F7BE
ULSERR01.MSG ULSERR01.MS_ 18 11/23/1999 13:33 1967 D5B3FAC5
UNICODE.SYS UNICODE.SY_ 17 12/02/1999 14:13 20014 71363075
UNIKBD.DLL UNIKBD.DL_ 16 12/02/1999 14:13 28515 89F40D57
UNINSTAL.EXE UNINSTAL.EX_ 13 03/22/2000 14:05 97177 34B59E17
UNPACK2.EXE UNPACK2.EX_ 15 03/16/2000 08:22 79936 D658AB78
USER.EXE USER.EX_ 7 12/02/1999 16:42 281088 45403B7A
USINTER.KBL USINTER.KB_ 18 12/02/1999 14:19 1032 5FE33FD9
VBIOS.SYS VBIOS.SY_ 18 11/23/1999 09:17 8816 6035F9BA
VCMOS.SYS VCMOS.SY_ 18 11/23/1999 09:17 2272 B1168EC4
VDMA.SYS VDMAPS2.SY_ 17 11/23/1999 09:17 14329 80562837
VDMA.SYS VDMAAT.SY_ 18 11/23/1999 09:17 11465 88ECE746
VDPMI.SYS VDPMI.SY_ 17 11/23/1999 09:18 30626 DD010B18
VDPX.SYS VDPX.SY_ 17 11/23/1999 09:19 26322 3172BE9B
VGA.DSP VGA.DS_ 18 03/15/2000 11:19 8731 FDA18435
VIDEOCFG.DLL VIDEOCFG.DL_ 16 02/08/2000 11:03 37998 738F20CA
VIEW.EXE VIEW.EX_ 16 03/28/2000 14:02 27620 E72AE357
VIOCALLS.DLL VIOCALLS.DL_ 18 03/31/2000 08:44 2048 FA72EB99
VIOTBL.DCP VIOTBL.DC_ 16 12/02/1999 14:20 225355 406F489E
VIOTBL.ISO VIOTBL.IS_ 16 12/02/1999 14:21 230105 2FD7721C
VMAN.DLL VMAN.DL_ 15 02/09/2000 15:34 46553 DB15923C
FixPak Corrective Service levels and disk layouts 52
April 3, 2000 - Warp 4 FixPak XR_M013
VMANWIN.SYS VMANWIN.SY_ 18 02/09/2000 11:15 3024 91B7B809
VPIC.SYS VPIC.SY_ 18 11/23/1999 09:20 9942 281F32DA
VPICPARM.SYS VPICPARM.SY_ 8 11/23/1999 09:20 736 95C51DBB
VTIMER.SYS VTIMER.SY_ 18 11/23/1999 09:20 10560 C0AF4515
VW32S.SYS VW32S.SY_ 7 11/23/1999 09:22 18338 52CBEA9A
VWIN.SYS VWIN.SY_ 17 11/23/1999 09:21 27104 94AE82C6
WCFGMRI.DLL WCFGMRI.DL_ 18 01/21/2000 13:16 6182 24825E21
WD24B.DSP WD24B.DS_ 18 03/15/2000 11:19 32662 6883B5CF
WELCMMRI.DLL WELCMMRI.DL_ 17 02/16/2000 15:43 14409 DEB34A10
WINCFG.DLL WINCFG.DL_ 17 03/29/2000 09:13 13379 7C5FC2AD
WINFILE.EXE WINFILE.EX_ 13 12/02/1999 16:31 146960 265456E2
WINSCLIP.DLL WINSCLIP.DL_ 17 12/02/1999 16:27 14848 C63E0396
WINSDDE.DLL WINSDDE.DL_ 17 12/02/1999 16:27 18432 A6C7AF73
WINSHELD.EXE WINSHELD.EX_ 17 12/02/1999 16:27 22528 F1801F6D
WINSMSG.DLL WINSMSG.DL_ 17 12/02/1999 16:27 28441 ED6C8A9E
WPCLS.IMP WPCLS.IM_ 18 11/22/1999 11:40 8661 DA18DFC2
WPCOMET.DLL WPCOMET.DL_ 18 03/28/2000 13:53 8656 E6CB2792
WPCONFIG.DLL WPCONFIG.DL_ 8 03/15/2000 16:11 266116 59DD60B4
WPCONMRI.DLL WPCONMRI.DL_ 17 01/21/2000 13:16 32304 D7790A13
WPDSRVP.DLL WPDSRVP.DL_ 2 03/29/2000 09:28 14194 8F0AF4DE
WPHELP.HLP WPHELP.HL_ 5 02/24/2000 15:36 841366 01FE714B
WPINET.DLL WPINET.DL_ 13 03/29/2000 09:28 117180 E9DCEA66
WPINTMRI.DLL WPINTMRI.DL_ 18 02/22/2000 12:11 11324 ACF86E7F
WPMSG.HLP WPMSG.HL_ 16 03/15/2000 11:04 50198 9EB8EB75
WPPRINT.DLL WPPRINT.DL_ 2 03/29/2000 09:16 364010 E4C1D37A
WPPRINT.HLP WPPRINT.HL_ 15 01/21/2000 13:21 71408 DF806E0F
WPPRTMRI.DLL WPPRTMRI.DL_ 15 02/24/2000 15:31 66683 C556120E
WPREXX.IMP WPREXX.IM_ 18 11/22/1999 11:40 6313 410B163F
WPSINIT.WPS WPSINIT.WP_ 18 11/22/1999 11:40 15877 ACA97B19
WPSINST.CMD WPSINST.CM_ 18 11/22/1999 11:40 2813 986D141E
WW.EXE WW.EX_ 18 07/16/1998 14:31 8305 1E171079
WWDLL.DLL WWDLL.DL_ 8 12/21/1997 01:29 276981 9F80E37B
WWHOOK.DLL WWHOOK.DL_ 17 12/21/1997 01:29 27230 5071DBC4
XCOPY.EXE XCOPY.EX_ 16 01/21/2000 10:51 52576 7FD76B45
XPG00420.TBL XPG00420.TB_ 18 11/22/1999 12:17 27264 08667C09
XPG00864.TBL XPG00864.TB_ 18 11/22/1999 12:17 27264 26725C67
************************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
Fixpak name: XR_M013_ (Country = Generic)
Pre-requisite CSD Level: XR_4000_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
FixPak Corrective Service levels and disk layouts 53
April 3, 2000 - Warp 4 FixPak XR_M013
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
OS2LDR OS2LDR.___ 18 03/31/2000 08:42 45056 52DAC542
************************************************************************
Product location on CSD: A:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
Fixpak name: XR_M013_ (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:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
APPDBUTL.DLL APPDBUTL.DL_ 18 02/25/2000 12:15 25015 46879016
APPSTART.EXE APPSTART.EX_ 18 02/25/2000 12:15 33854 9A3FFE76
NCAPPUTL.EXE NCAPPUTL.EX_ 18 02/25/2000 12:15 12648 73E16BCA
OS2LDR OS2LDR.___ 18 02/15/2000 14:39 45056 6F826302
PMLOGON.EXE PMLOGON.EX_ 18 01/24/2000 11:20 40109 5D5B81C3
PRNCFG.DLL PRNCFG.DL_ 18 01/24/2000 11:21 58258 E0003042
TDESK.DLL TDESK.DL_ 18 01/25/2000 01:53 6653 E9923660
FixPak Corrective Service levels and disk layouts 54
April 3, 2000 - Warp 4 FixPak XR_M013
TLOGOFF.EXE TLOGOFF.EX_ 18 01/25/2000 01:53 9579 22A8C9F6
TOBJECT.DLL TOBJECT.DL_ 18 01/25/2000 01:53 7312 E87F3724
TSHUTDWN.EXE TSHUTDWN.EX_ 18 01/25/2000 01:53 8693 57802BB0
************************************************************************
Product location on CSD: A:\FIX\OS2.4
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
Fixpak name: XR_M013_ (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\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
APPSTART.EXE APPSTART.EX_ 18 03/22/2000 10:08 35018 33D40578
NCAPPUTL.EXE NCAPPUTL.EX_ 18 03/22/2000 10:08 19054 C04511EB
OS2LDR OS2LDR.___ 18 02/15/2000 14:39 45056 6F674302
TSHUTDWN.EXE TSHUTDWN.EX_ 18 02/15/2000 12:41 10793 1E09808D
FixPak Corrective Service levels and disk layouts 55
April 3, 2000 - Warp 4 FixPak XR_M013
10.0 SPACE UTILIZATION
The FixPak installation process requires free space on the following
drives:
Space needed Drive
Up to 2MB C:
Up to 2MB Boot drive (4MB if boot is C:)
Up to 22MB Drive with most free space, holds deferred files if
A:SERVICE method used.
Up to 37MB FixPak Archive/Backup for product with CSD level of
XR_4000
Up to 37MB FixPak Archive/Backup for product with CSD level of
XR_4010
Note: The lines labeled "FixPak Archive/Backup for product with CSD level
of" will be on the drive you specify and will occupy up to the size
indicated for the Archive and for the Backup directories. If, for
example, the indicated size is 30MB then the space actually occupied on
the drive can be up to 60MB.
10.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE
Warning: Make sure you read and understand the following before removing
the Archive and Backup files and directories.
You can recover the space used for FixPak Archive and Backup files as
long as you understand that doing this prevents you from being able to
backout to the previous Backup or Archive level. If it becomes necessary
at a later time to backout a FixPak, the only way you can do this is to
reinstall Warp.
Do the following to delete the FixPak Backup and Archive files and remove
the files used by CSF to keep track of what service has been applied to
your system.
1. Delete every instance of the following files on your system
(search every drive and every directory they contain).
■ LOGF0000.* (can be OS2 or MPM)
■ LOGSTART.* (can be OS2 or MPM)
■ LOGARCH.* (can be OS2 or MPM)
■ CSF_*.*
■ FIXSTART
2. Delete the files in the FixPak Archive and Backup directories on
your harddisk.
3. Remove the FixPak Archive and Backup directories with the RMDIR
command.
Space Utilization 56
April 3, 2000 - Warp 4 FixPak XR_M013
10.0.2 TRADEMARKS
The following terms are trademarks of the International Business Machines
Corporation in the United States or other countries or both:
■ IBM
■ OS/2
■ WorkSpace On-Demand
Other company, product, and service names may be trademarks or service
marks of others.
Space Utilization 57