home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 17 Fixes30
/
17-Fixes30.zip
/
xr_w041.1dk
/
README.1ST
< prev
next >
Wrap
Text File
|
1999-07-02
|
148KB
|
3,526 lines
< Installation instructions for Warp FixPak XR_W041
July 2, 1999
This FixPak makes the products it services Year 2000 ready
Build level 8.265
This FixPak applies to:
XR_3005 Warp Server
XR_3006 Warp Server SMP
Requires Corrective Service Facility release f.141 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
July 2, 1999 - Warp 3 FixPak XR_W041
July 2, 1999 - Warp 3 FixPak XR_W041
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3
3.0.1 Device Drivers removed from Fixpak . . . . . . . . . . . . . 3
3.0.2 Please use Fixtool f.141 or later . . . . . . . . . . . . . 3
3.0.3 Can't install Warp 3 . . . . . . . . . . . . . . . . . . . . 3
3.0.4 OS2DUMP split into two versions . . . . . . . . . . . . . . 3
3.0.5 Using Display Recovery Choices . . . . . . . . . . . . . . . 4
3.0.6 DSPINSTL.EXE failure . . . . . . . . . . . . . . . . . . . . 4
3.0.7 Additional diskette image for Warp v3 FixPaks . . . . . . . 5
3.0.8 Windows printer drivers leave a zombie thread running . . . 5
3.0.9 Updated Corrective Service Facility (CSF) . . . . . . . . . 6
3.0.10 Syslevel Correction Programs . . . . . . . . . . . . . . . 6
3.0.11 If Installing on a Preloaded System . . . . . . . . . . . . 6
3.0.12 Newer file on harddisk than is in FixPak . . . . . . . . . 7
3.0.13 CSF0208 No products were found . . . . . . . . . . . . . . 7
3.0.14 CSF0248 Archive path is shared between mismatched . . . . . 7
3.0.15 CSF0249 Error opening or creating archive file. . . . . . 8
3.0.16 Configuration Installation Distribution ( CID ) . . . . . . 8
3.0.17 Read-Only files . . . . . . . . . . . . . . . . . . . . . . 8
3.0.18 DATABASE files removed from FixPak . . . . . . . . . . . . 8
4.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 9
4.0.1 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . . 9
4.0.2 IPE on boot after FixPak 35 installed on UNI systems . . . . 9
4.0.3 Installation of Java 1.1.4 or Java 1.1.6 . . . . . . . . . 10
4.0.4 Files removed from FixPaks (33 and up) . . . . . . . . . . 10
4.0.5 DSPRES.DLL included in FixPaks . . . . . . . . . . . . . . 10
4.0.6 DOSCALL1.DLL Trap on Thinkpads that use MWAVE . . . . . . . 10
4.0.7 Trap D or E in LAN Distance . . . . . . . . . . . . . . . . 11
4.0.8 Screen corruption using Lotus Notes 4.1 . . . . . . . . . . 11
4.0.9 Dell machines and font editing . . . . . . . . . . . . . . 12
5.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 SES supported on SMP with FP38 or later . . . . . . . . . . . . 13
5.2 Querying file dates for files after Dec 31, 1999 in REXX . . . 13
5.3 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 14
5.4 Serviceability (RAS) Enhancements . . . . . . . . . . . . . . . 14
5.5 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.5.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 15
5.5.2 Where euro is not supported . . . . . . . . . . . . . . . . 16
5.5.3 Printing the euro . . . . . . . . . . . . . . . . . . . . . 17
5.6 New Print fuctions . . . . . . . . . . . . . . . . . . . . . . 17
5.7 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.8 If you have installed OpenDoc . . . . . . . . . . . . . . . . . 18
5.9 Joliet-2 support in CDFS.IFS . . . . . . . . . . . . . . . . . 18
Contents ii
July 2, 1999 - Warp 3 FixPak XR_W041
5.10 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . 19
5.10.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 19
5.10.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 21
5.11 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 21
5.11.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 22
5.11.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.12 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.13 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.14 Other README files . . . . . . . . . . . . . . . . . . . . . . 23
5.15 Reserve Drive Letters Added . . . . . . . . . . . . . . . . . 24
5.16 What is the SIQ (Single Input Queue) feature . . . . . . . . . 25
5.16.1 How it works . . . . . . . . . . . . . . . . . . . . . . . 25
5.17 Common File Dialog Interface changes . . . . . . . . . . . . . 26
6.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 27
6.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 27
6.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 27
6.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 27
7.0 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 29
8.0 LAN Server/Warp Server Remote IPL Considerations . . . . . . . 30
9.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 32
9.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 32
9.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 32
9.3 Method 2: Boot from Corrective Service Disk 1. . . . . . . . . 34
9.4 Additional Corrective Service Facility information . . . . . . 34
10.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . 35
10.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 36
11.0 FixPak Corrective Service levels and disk layouts . . . . . . 37
12.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 57
13.0 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . . . 58
14.0 Recovering from problems . . . . . . . . . . . . . . . . . . . 59
Contents iii
July 2, 1999 - Warp 3 FixPak XR_W041
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_W041 for OS/2 Warp 3
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
3.
2. You may make copies of the OS/2 Service Fixes equal to the number of
licensed copies of OS/2 Warp 3 you possess.
3. You may only use the OS/2 Warp 3 Service Fixes included with FixPak
XR_W041 for maintenance purposes.
4. All other terms and conditions of your OS/2 Warp 3 license agreements
apply to the Service Fixes; however, this does not extend any warranty
and/or services, including but not limited to the "Initial
Installation" period, outlined in such agreements.
Terms and Conditions 1
July 2, 1999 - Warp 3 FixPak XR_W041
2.0 DO NOT USE YOUR SYSTEM
Once you begin a FixPak installation, do not try to use your system for
any other purpose. Doing so may yield unexpected problems which can cause
the FixPak installation to fail.
Do not use your system 2
July 2, 1999 - Warp 3 FixPak XR_W041
3.0 INSTALLATION NOTES
3.0.1 DEVICE DRIVERS REMOVED FROM FIXPAK
Beginning with Warp 4 FixPak XR_M011 and Warp 3 FixPak XR_W041, most OS/2
Device Drivers have been moved to a separate Device Driver FixPak. The
first one will be XR_D001 which is scheduled for a later release.
To avoid potential Device Driver problems with the installation of Warp 4
FixPak XR_M011 and Warp 3 FixPak XR_W041, your system should be at FixPak
level XR_M005 or higher for Warp 4 and XR_W032 or higher for Warp 3.
3.0.2 PLEASE USE FIXTOOL F.141 OR LATER
Beginning with Warp 3 FixPak 40 and Warp 4 FixPak 10, you must use
Corrective Service Facility f.141 or later. It has fixes for problems
found in the F.138B and F.139 builds as well as a fix to support RIPL
servers where there may be in excess of 250 SYSLEVEL files. It also
handles the type 1 (All FixPaks prior to 40 and 10) and type 2 (FixPaks
40 and 10 and later) FixPaks.
If you try to use a CSF level prior to F.138B you will get a "CSF0208 No
products were found on the target system to service" message.
3.0.3 CAN'T INSTALL WARP 3
If you can't get Warp 3 installed, check the OS/2 Device Driver Pak
Online at:
http://service.software.ibm.com/os2ddpak/readme.htm#disk1
for the latest available device drivers to update your Installation disks
with.
3.0.4 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
Installation Notes 3
July 2, 1999 - Warp 3 FixPak XR_W041
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.
3.0.5 USING DISPLAY RECOVERY CHOICES
If you have the "Display Recovery Choices at each system startup"
function active on your system, you need to disable it before you apply a
FixPak if
■ The system is running
■ The boot partition will be serviced.
The problem with using this function is that the Corrective Service
Facility (CSF) updates the current CONFIG.SYS with entries to run the
Locked File Device Driver (LFDD) the next time you boot the system. This
is done to replace files that are currently in use (locked) by the
system.
The Recovery choices function replaces the current CONFIG.SYS with the
one that is associated with the recovery choice you select, wiping out
the LFDD entries. This means the LFDD does not run at boot time and the
deferred files will not get updated, therefore the FixPak does not get
completely applied.
Note: It is not necessary to disable this function if you install a
FixPak by booting from the CSF disks or from another OS/2 partition.
3.0.6 DSPINSTL.EXE FAILURE
DSPINSTL.EXE may fail when installing OEM versions of non-IBM video
device drivers. For Uni-processor versions of Warp, the archived version
of the file can be used as a workaround. For SMP versions, contact IBM
for a temporary fix. A subsequent FixPak will correct this problem.
Installation Notes 4
July 2, 1999 - Warp 3 FixPak XR_W041
3.0.7 ADDITIONAL DISKETTE IMAGE FOR WARP V3 FIXPAKS
We've added an additional diskette image to Warp v3 FixPaks. This disk
contains the directories and tools previously found on the last FixPak
disk.
This disk may contain the following:
■ BETA
■ DIR_ONE
■ DIR_TWO
■ SYSLEVEL
■ FIXSYSL.CMD
■ SYSZMPM.CMD
■ UPDTRIPL.EXE
Note: This DOES NOT increase the size of the FixPak
The SYSLEVEL directory contains corrected SYSLEVEL files for National
Language Versions (NLV) of Warp v3 products. The directory names have the
following meanings:
■ Directory Product
■ --------- -------------------------------------------------------
■ WARPSRV XR_3005 Warp Server
■ WRPSVSMP XR_3006 Warp Server SMP
3.0.8 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING
A problem occurs with some Windows printer drivers where a zombie thread
is left running after the program that loaded it is exited.
This does not occur when the program is run from a Seamless instance of
PROGMAN or from a Full Screen session because when these are exited the
whole WINOS2 Subsystem is exited.
This problem has been reported for the Adobe and Hewlett Packard Windows
printer drivers. To correct this problem for people running with these
drivers ONLY who have experienced symptoms such as:
■ exiting a program running seamlessly after printing or
■ setting up a printer and seeing the icon not being unhatched and/or
■ not being able to start another copy of the program
Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot*
section:
■ backgroundtasks=run_enum.exe,hpfbkg02.exe
Installation Notes 5
July 2, 1999 - Warp 3 FixPak XR_W041
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.
3.0.9 UPDATED CORRECTIVE SERVICE FACILITY (CSF)
Use CSF level f.141 or later for all Fixpaks. It is contained in
CS_140.EXE. This is a self-extracting ZIP file. It is not and does not
contain bootable disks.
See the READ.ME file for instructions on how to boot with diskettes along
with a lot of other useful information.
3.0.10 SYSLEVEL CORRECTION PROGRAMS
The FIXSYSL.CMD, located on the last disk of this FixPak, is included
for:
1. Warp systems that have applied an S3 video pak and the Current CSD
level is XR02110 (execute the syslevel command to find out);
2. APTIVA systems with a Current CSD level XR03005, Compid 562260100,
Type WP.
This program will set the Current CSD level to XR03002. Please run the
FIXSYSL program before installing this FixPak.
The SYSZMPM.CMD, located on the last disk of this FixPak, is included
for:
1. Warp Server SMP systems that have a Current CSD Level of XR06200 and a
Prior CSD Level of UN09407 in the \MMOS2\INSTALL\SYSLEVEL.MPM file.
2. Other Warp systems with incorrect Multimedia syslevel files.
This program will set the Current CSD level to XR03006 to allow service
to be applied to Multimedia files. Please run the SYSZMPM program before
installing this FixPak on Warp Server SMP systems.
3.0.11 IF INSTALLING ON A PRELOADED SYSTEM
Installing this FixPak on systems that were preloaded may cause a pop-up
to occur that is invalid. The pop-up claims that the following files
have a more recent date and/or version than the ones contained on your
system:
Installation Notes 6
July 2, 1999 - Warp 3 FixPak XR_W041
MMOS2\DLL\IOPRNLS.DLL
MMOS2\DLL\AMPMXMCD.DLL
MMOS2\DLL\AUDIOMCD.DLL
MMOS2\DLL\AUDIOSH.DLL
MMOS2\DLL\MMPM.DLL
OS2\INSTALL\SYSLEVEL.SUC
The proper action is to allow the FixPak installation to overwrite these
files with the ones supplied by the FixPak.
3.0.12 NEWER FILE ON HARDDISK THAN IS IN FIXPAK
If you get a popup stating that a newer file exists on your harddisk than
is in the FixPak. press the "OK" button unless you know for sure the file
on your harddisk is newer than the one in the Fixpak.
3.0.13 CSF0208 NO PRODUCTS WERE FOUND
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.14 CSF0248 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED
1. The Archive path you specified (or was previously specified) contains
files from a different release of OS/2. You need to specify a
different Archive path.
2. You have a bad SYSLEVEL.OS2 or SYSLEVEL.MPM file. Both must have the
same Current CSD Level, Version, Type and Component ID if you point
both FixPak Archives to the same location.
Check \OS2\INSTALL\SYSLEVEL.OS2 and \MMOS2\INSTALL\SYSLEVEL.MPM. If
either is wrong, place the last FixPak disk in A: and run FIXSYSL.CMD
to correct SYSLEVEL.OS2 problems or SYSZMPM.CMD to fix SYSLEVEL.MPM
problems.
Installation Notes 7
July 2, 1999 - Warp 3 FixPak XR_W041
3.0.15 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.16 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.
3.0.17 READ-ONLY FILES
If you installed OS/2 Warp 3.0 from a CD-ROM, some files being updated
may have the Read-Only attribute set. This will cause the update program
to ask you if you want the files replaced. Answer OK.
3.0.18 DATABASE FILES REMOVED FROM FIXPAK
DATABASE.TXT and DATABASE.DAT files have been removed from FixPak 29 and
will be left out of all future FixPaks. They are used to control the
Notebook settings for migrated applications during initial install or
selective install.
This has been done to protect customers who have customized these files.
Installation Notes 8
July 2, 1999 - Warp 3 FixPak XR_W041
4.0 POST INSTALLATION NOTES
4.0.1 SETTING IRQ9 PROCESSING IN CONFIG.SYS FOR VPIC.SYS
Some applications like PCAS (and some terminal emulators) have problems
sharing IRQ9 in a VDM. Since the DOS Virtual Device drivers are not
loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added
starting with Warp 3 FixPak 38 and Warp 4 FixPak 8.
To prevent sharing of IRQ9 in a VDM, add the following statement in
config.sys:
device=x:\os2\mdos\vpicparm.sys irq9_off
(x: is your OS/2 boot drive)
Next, in the settings for the program that requires exclusive access to
IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON.
When you next boot your system, VDMs will not share IRQ9.
4.0.2 IPE ON BOOT AFTER FIXPAK 35 INSTALLED ON UNI SYSTEMS
If you experience a kernel trap (black screen trap) or get a messages
stating that device drivers (such as CLOCK01.SYS) were not able to
install at boot time do the following:
1. Reboot and press Alt-F1 when the white block appears
2. Select C for command line
3. From the command line enter: TEDIT CONFIG.SYS
4. Add the following statement to the end of CONFIG.SYS:
TRACE=OFF,6
5. Reboot
Note: DO NOT use major code 6 trace events either from CONFIG.SYS or from
the command line.
A fix for this problem will be placed on "ftp://service.boulder.ibm.com"
in the "ps/products/os2/fixes/v3.0warp/english-us/xr_w035/" directory and
the NCS Support News page at
"http://ps.boulder.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa/fixnews.html"
will be updated when the fix is available.
Post Installation Notes 9
July 2, 1999 - Warp 3 FixPak XR_W041
4.0.3 INSTALLATION OF JAVA 1.1.4 OR JAVA 1.1.6
Installation of Java 1.1.4 or Java 1.1.6 on top of this FixPak will
down-level portions of the ULS support if you are not using the 1.2.2 (or
later) level of Feature Installer.
If this occurs, Euro currency support will not work correctly. To
recover, re-install this FixPak. This will allow both Java and Euro
support to work correctly.
4.0.4 FILES REMOVED FROM FIXPAKS (33 AND UP)
The following files, introduced in FixPak 26, have been merged into
LOCALE.DLL and were removed from FixPak 33 and all future Warp 3 FixPaks.
AR_AA.DLL EN_CA.DLL FR_CA.DLL LT_LT.DLL SH_BA.DLL
BG_BG.DLL EN_GB.DLL FR_CH.DLL LV_LV.DLL SK_SK.DLL
C.DLL EN_IE.DLL FR_FR.DLL MK_MK.DLL SL_SI.DLL
CA_ES.DLL EN_NZ.DLL HR_HR.DLL NL_BE.DLL SQ_AL.DLL
CS_CZ.DLL EN_US.DLL HU_HU.DLL NL_NL.DLL SR_SP.DLL
DA_DK.DLL EN_ZA.DLL IS_IS.DLL NO_NO.DLL SV_SE.DLL
DE_AT.DLL ES_ES.DLL IT_CH.DLL PL_PL.DLL TH_TH.DLL
DE_CH.DLL ES_LA.DLL IT_IT.DLL PT_BR.DLL TR_TR.DLL
DE_DE.DLL ET_EE.DLL IW_IL.DLL PT_PT.DLL UNIV.DLL
EL_GR.DLL FI_FI.DLL JA_JP.DLL RO_RO.DLL ZH_CN.DLL
EN_AU.DLL FR_BE.DLL KO_KR.DLL RU_RU.DLL ZH_TW.DLL
Additionally, ENULS.MSG was removed from FixPak 33 (and up) as it is no
longer needed.
4.0.5 DSPRES.DLL INCLUDED IN FIXPAKS
DSPRES.DLL has been added to FixPak 35 and up for support of Euro
character display. This file can sometimes be overwritten by video device
driver installation. If this occurs, an updated version is located in
\OS2\INSTALL\VGA. This updated file can be copied into the \OS2\DLL
directory.
4.0.6 DOSCALL1.DLL TRAP ON THINKPADS THAT USE MWAVE
After installing this FixPak on a Thinkpad that uses MWAVE and the LAN
while in a docking station you may encounter a DOSCALL1.DLL trap after
rebooting when the machine is undocked.
A fix has been made to the MWAVE MWNOTOS2.EXE to correct this problem.
The MWNOTOS2.EXE file can be found on the Internet along with a readme
(.doc file) on how to replace the file. The location is:
Post Installation Notes 10
July 2, 1999 - Warp 3 FixPak XR_W041
Point your Web browser at:
ftp://www3.pc.ibm.com/pub/pccbbs/mobiles/mwnotos2.exe
ftp://www3.pc.ibm.com/pub/pccbbs/mobiles/mwnotos2.doc
4.0.7 TRAP D OR E IN LAN DISTANCE
If you get a Trap D or E in the MACFH$1 device driver, at offset 126C,
while running LAN Distance, please call IBM Service for the LAN Distance
APAR IC14228.
4.0.8 SCREEN CORRUPTION USING LOTUS NOTES 4.1
There is a screen corruption problem when running Lotus Notes 4.1 in 256
colors on OS/2. This problem has been corrected in version 4.1.2.
Symptoms normally appear as anomilies in the fonts, such as parts of
characters or entire characters disappearing. This corruption can occur
at any resolution.
Since this only occurs when using 256 colors, an immediate work around is
to not use 256 colors. To change the number of colors displayed:
1. open the OS/2 System folder
2. open the System Setup folder
3. double click on the System icon in the System Setup folder
4. select a resolution that does not use 256 colors
5. close the folders
6. shutdown and reboot the machine
The fix for this problem is in the display device drivers. IBM supported
display device drivers will be available on the PCCBBS and Internet as
"Controlled" fixes. You should contact the IBM PSP Software Solution
Center at 1-800-992-4777 to obtain PCCBBS and Internet logon information
for display device drivers needed. The build level should be 0.041 or
above.
See "Where Fixes can be found" for where display device drivers can be
found once they have been publically released.
Post Installation Notes 11
July 2, 1999 - Warp 3 FixPak XR_W041
4.0.9 DELL MACHINES AND FONT EDITING
When editing fonts, users of Dell machines may discover a slight
regression. When a font size is edited, the Font Palette is updated
correctly; however, should users browse (select around) the palette, they
might, at times, notice an inconsistency between the font size displayed
on the palette and the one that is displayed on the font editor. In all
cases, the font size displayed on the Font Palette is the correct size
for the font when it is dragged to the target (for example, the desktop,
folder, or application).
Post Installation Notes 12
July 2, 1999 - Warp 3 FixPak XR_W041
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.
We apologize for not communicatiing this more clearly earlier and
specifically for not including information on IBM Open32 in the FixPak 26
(and subsequent) README.1ST.
5.1 SES SUPPORTED ON SMP WITH FP38 OR LATER
SES is supported on systems running Warp Server SMP once FixPak 38 or
later is installed.
You can get the IBM OS/2 Security Enabling Services from the Web at:
ftp://service.boulder.ibm.com/ps/products/os2/warp.update.kit/warpses/
5.2 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX
Existing REXX functions return file dates with a two digit year only.
While these functions are Year 2000 tolerant (i.e. the results will be
correct for files dated after Dec 31, 1999) they require some additional
logic in existing programs to handle the returned date correctly when
they are compared with other file dates.
Since the output format of the exisiting functions could not be changed
for compatibility reasons, new options have been added to the REXX
interpreter to return file dates with the year formatted with 4 digits.
Two functions have been extended to support the new format. The syntax to
retrieve the file date in 4 digit format is as follows:
New Function 13
July 2, 1999 - Warp 3 FixPak XR_W041
/********************************************/
/* Use STREAM QUERY TIMESTAMP to query file */
/* date in 4 digit format */
/********************************************/
Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP")
/***********************************************/
/* Use option "L" with SysFileTree to return a */
/* list of files with long date format */
/***********************************************/
Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
Call SysLoadFuncs
Call SysFileTree "C:\*.*", "Files", "L"
Do i = 1 To Files.0
Say Files.i
End
These extensions are available in both classic REXX and Object REXX on
OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these
extensions in your program you have to make sure that you are running the
right level of REXX
5.3 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
GRADD is supported on all Warp 3 releases beginning with FixPak 35.
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.4 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
New Function 14
July 2, 1999 - Warp 3 FixPak XR_W041
Always refer to README.DBG for details of any RAS enhancements delivered
with a FixPak.
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.
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)
New Function 15
July 2, 1999 - Warp 3 FixPak XR_W041
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:
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.
New Function 16
July 2, 1999 - Warp 3 FixPak XR_W041
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 PRINT FUCTIONS
The following print functions have been added starting at FixPak XR_W031
level:
■ Allow moving a print job from one print server to another server.
■ Allow moving all print jobs at once.
■ Define a backup print queue so that when a printer has problems, all
jobs will be sent to a backup print queue if the problem persists for
a specified number of minutes.
■ When creating a network print object, user will be prompted to create
a WINOS2 print configuration.
5.7 IBM OPEN32
Open32 is a new API set provided in OS/2 Warp 3 beginning with FixPak 26
to help ISVs migrate their Windows 32-bit applications to OS/2.
Approximately 750 APIs from the Win32 API set are included and provide
essentially the same functionality as the Windows NT 3.51 APIs of the
same name.
Applications such as Lotus SmartSuite 96 are enable by this set of APIs.
It is required that Open32 support be installed on OS/2 Warp 3 systems
that have FixPak 26 or higher installed. The Open32 code requires 20MB of
disk space on your OS/2 Warp 3 boot drive.
New Function 17
July 2, 1999 - Warp 3 FixPak XR_W041
It also creates a new \LANGUAGE directory on your boot drive and adds SET
ULSPATH=x:\LANGUAGE to CONFIG.SYS (x: is your boot drive).
If you are installing this FixPak on a machine that has an older version
of IBM Open32 (formerly known as Developer API Extensions or DAX) from
either FixPak 17 Special Edition or DevCon 9, then you must uninstall the
older version of Open32 before starting to install this new version.
If you no longer have the CD or diskettes to uninstall the older version
of Open32 then you must follow these steps:
1. In config.sys, delete the following line:
RUN=x:\OS2\RSRV.EXE
where x: is your boot drive.
2. Reboot your system
3. Delete the following files from your machine, where x: is your boot
drive.
x:\boot.dat
x:\registry.dat
x:\dos.dat
x:\os2\rsrv.exe
x:\os2\install\inst_dos.exe
x:\os2\install\reginit exe
5.8 IF YOU HAVE INSTALLED OPENDOC
If you have installed OpenDoc parts for Multimedia and you wish to keep
your OpenDOc support then DO NOT update Multimedia at all. To do this,
use the A:\SERVICE installation method and do not select Multimedia as a
product to be serviced.
5.9 JOLIET-2 SUPPORT IN CDFS.IFS
Joliet is a Microsoft extension to the ISO 9660 CD-ROM file system which
adds Unicode and longname support. Presently both Windows 95 and Windows
NT 4.0 support the Joliet-2 and Joilet-3 formats. Beginning with Warp 3
Fixpak 32 and Warp 4 Fixpak 4, you can enable the Joliet-2 support by
adding the '/w' option to the CDFS.IFS statement in CONFIG.SYS.
Joilet-3 format is not supported.
New Function 18
July 2, 1999 - Warp 3 FixPak XR_W041
5.10 NEW (IMPROVED) CHKDSK
This new version of CHKDSK offers significant improvements for High
Performance File System (HPFS) drives. CHKDSK now fixes all errors found
on HPFS drives in a single pass, operating faster, and with less memory
than previous versions. It contains better error detection and
correction algorithms, and creates a log file so service personnel can
determine what errors it found and how it corrected them. Finally, only
the amount of physical memory in your system limits the size of the
largest drive CHKDSK can check at boot time (autocheck).
Improvements in this version of CHKDSK are for HPFS drives only. No
changes occurred to checking File Allocation Table (FAT) drives. This
enhanced CHKDSK operates on IBM OS/2 Warp 3.0 and higher, including IBM
Warp 4, IBM Warp Server 4 and IBM Warp Server 4 SMP. This new CHKDSK
version will not run on version of OS/2 before OS/2 Warp 3.0.
5.10.1 USING THE NEW CHKDSK
The interface to CHKDSK remains CHKDSK.COM and PMCHKDSK. No changes
occurred to the CHKDSK command line parameters or messages.
The first time this version of CHKDSK runs on a fast formatted drive, it
will report harmless errors. These errors go away once CHKDSK is run
with the /F option.
Note: OS/2 Warp Install uses fast format.
Unlike prior versions of CHKDSK, large drives ( > 8GB) may be autochecked
if sufficient memory is available. The amount of memory required can
vary between 16MB and 48MB depending on the size of the drive. To enable
the autochecking of large drives, the following line must be added to
your config.sys:
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.
New Function 19
July 2, 1999 - Warp 3 FixPak XR_W041
Note: For those wishing to run unattended: In order to prevent the
system from pausing between autocheck and the reboot, we recommend that
the statement PAUSEONERROR=NO be in the CONFIG.SYS.
When you don't have enough physical (real) memory to autocheck large
drives, you must use virtual memory from SWAPPER.DAT. The technique is
to check the large drives between the time OS/2 starts and PM begins. To
start OS/2, the swap file and device drivers must reside on an unaffected
drive. The drives to be checked must not appear in the autocheck list in
the IFS statement for HPFS (or HPFS386).
This technique involves the following steps:
1. Remove the drive letter of the affected drive(s) from the autocheck
list in the IFS statement for HPFS (or HPFS386).
2. If you are using HPFS, add /QUIET to the IFS statement for HPFS.
3. If you are using HPFS386.IFS, add POPUPERRORS=NO below the
[filesystem] section of the HPFS386.INI file. Support for the
POPUPERRORS parameter requires OS/2 LAN Server FixPak IP08265 or
higher for LS 5.0 or FixPak IP08503 or higher for LS 5.1. In addition,
the POPUPERRORS parameter ONLY suppresses HFS0102 messages.
4. Add a CALL statement to your config.sys. This CALL statement will
call CHKDSK.COM, and will tell it what drive to check. This CALL
statement must appear after the LIBPATH=, SET PATH=, and SET DPATH=
statements, but before any other CALL statements in your CONFIG.SYS
file.
Calls to CHKDSK in STARTUP.CMD are not necessary, when using this method
or the base device driver (chkdsk.sys) method.
Example: The computer boots from drive C (moderate HPFS or FAT sized
drive). Drive D (large HPFS) requires more RAM to check than installed
in the machine.
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.
New Function 20
July 2, 1999 - Warp 3 FixPak XR_W041
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
Note: CHKDSK.COM, CHKDSK32.DLL and UHPFS.DLL from FixPak 30 will not work
on a Warp system with a service level prior to FixPak 29. This is because
of a new pack program introduced at FixPak 29 level.
5.10.2 CHKDSK LOG FORMATTER
CHKDSK creates a binary service log file (chkdsk.log) on the root of the
drive being checked during autocheck or whenever the /F option is
invoked. The previous log file is saved as chkdsk.old. A formatter for
this log file can be found at:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe
This is a self extracting ZIP file. Place it in a directory in your path
and enter CHKLOGPK. This will create the following files:
message.txt
msghdr.txt
pmchklog.exe
range.txt
readme
They should all have a date of 05/14/97 or later (May 14, 1997).
This is a tool used by OS/2 service to format and view the new CHKDSK log
entries. There is no support for this tool. You are welcome to use it
but if you have problems with it or do not understand the output DO NOT
contact IBM for assistance as none will be provided.
5.11 AUTOMATED TRAP SCREEN LOGGING
Whenever an application program traps, the trap information is (now)
automatically logged in the POPUPLOG.OS2 file. This is a cumulative file
that is by default located in the root directory of the bootable
partition. Should this file become too large then it may be erased or
pruned (reduced in size). The system will automatically re-create it if
it does not exist.
New Function 21
July 2, 1999 - Warp 3 FixPak XR_W041
The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used
to control trap screen behavior (see below).
5.11.1 SUPPRESSPOPUPS
SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior. That
is, to disable logging and to have trap screens displayed unless
specifically overridden by an application's use of the DosError API.
SUPPRESSPOPUPS=x: will disable trap screen display for all processes and
will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or
partition.
If SUPPRESSPOPUPS is omitted then the behavior is as described above
under "Automated Trap Screen Logging".
5.11.2 TRAPLOG
The TRAPLOG command allows dynamic control of trap information logging.
The command syntax is:
TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]
where:
■ x: specifies that trap information is to be logged in
x:\POPUPLOG.OS2, x: being any partition drive letter.
■ NOLOG disables logging of trap information.
■ POPUPS enables the trap information pop-up message (SYS3175).
■ NOPOPUPS disables the trap information pop-up message.
5.12 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.
New Function 22
July 2, 1999 - Warp 3 FixPak XR_W041
The command syntax is:
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]
where:
■ ON enables all application and system traps to initiate a System Dump.
■ OFF disables automatic dump initiation.
■ R0 enables only Ring 0 traps to initiate a System Dump.
■ x: specifies the Dump Partition.
■ NOCHECK overrides the system level check for WARP 4.0, since use of
this command on a system level prior to FixPak 29 is equivalent to the
SYSDUMP command.
5.13 SYSDUMP
The SYSDUMP command forces a System Dump to be initiated, regardless of
the TRAPDUMP settings. This command is provided for the use of service
personnel to allow Dump Initiation to be automated through use of a
command file.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred thus under rare
circumstances data can be lost.
The command syntax is:
SYSDUMP [/NOPROMPT]
where:
■ NOPROMPT allows the Dump to proceed without the prompt and response to
message:
"Do you want to force a system dump? (Y/N)"
5.14 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.
New Function 23
July 2, 1999 - Warp 3 FixPak XR_W041
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).
5.15 RESERVE DRIVE LETTERS ADDED
The Reserve Drive Letters feature has been added at Warp FixPak level
XR_W024 for Uni Processor versions of Warp 3. It is not included in the
SMP (Symmetric Multi Processors) version of Warp 3.
A modification has been made to the OS/2 kernel that will allow the user
to specify, through a CONFIG.SYS parameter, specific drive letters that
will not be allocated for local block mode devices during the processing
of CONFIG.SYS.
Currently, all versions of OS/2 assign drive letters sequentially
starting from drive C: for all local devices or disk partitions. Any
network use of drive letters starts after the last drive letter used for
local devices/partitions.
RESERVEDRIVELETTER can be used to force a specific drive letter to be
allocated to a network drive or a CDROM for example.
SYNTAX: RESERVEDRIVELETTER=x, where "x" is letter D thru Z.
Note: Multiple RESERVEDRIVELETTER statements are allowed but only the
last one is used.
During the processing of CONFIG.SYS, OS/2 allocates drive letters for all
BASEDEV= statements. In general, the only BASEDEV= statements that
allocate drive letters are those for the Disk Device Driver, which will
allocate 1 drive letter sequentially for each local disk partition. Three
local disk partitions would allocate C:,D:,E:.
After processing BASEDEV= statements, the system will honor the
RESERVEDRIVELETTER statement(s). If the RESERVEDRIVELETTER statement
conflicts with any drive letter already assigned to a local disk
partition, an error message will be generated and that RESERVEDRIVELETTER
statement will be ignored.
New Function 24
July 2, 1999 - Warp 3 FixPak XR_W041
The next processing occurs for DEVICE= statements. DEVICE= statements
for local block mode devices will assign drive letters, starting
sequentially immediately after the highest drive letter specified in a
RESERVEDRIVELETTER statement. Examples of local devices which use drive
letters are CDROM, R/W OPTICAL, TAPE, Virtual Disks (VDISK).
EXAMPLE: User has 2 local disk partitions, wants the E: drive letter to
be used as a network drive, has both a CDROM and a R/W optical drive, and
wants the CDROM drive letter to be K:.
Specify a RESERVEDRIVELETTER=J statement and insure that the DEVICE=
statement for the CDROM preceeds the DEVICE= statement for OPTICAL in
CONFIG.SYS. Note that all drive letters between E and J will be available
for use by programs or device drivers, which allocate drive letters for
non-local use like network redirectors.
5.16 WHAT IS THE SIQ (SINGLE INPUT QUEUE) FEATURE
The "SIQ" feature is new with FixPak XR_W017. It allows the user to take
focus away from an application that is monopolizing the message queue.
When the FixPak is installed, the SIQ feature is disabled (OFF).
5.16.1 HOW IT WORKS
When you request a focus change for example, by clicking on another
application or pressing Ctl+Esc the application that has the focus should
respond to the message in x milliseconds. If the application does not
respond within that time, OS/2 determines that the application is not
responding to messages and flags the application queue as bad. It then
switches focus to the desired application.
OS/2 will monitor the queue marked as bad to see when it does start
responding to messages. It will mark the queue as good when this occurs.
To enable the SIQ feature, put a SET PM_ASYNC_FOCUS_CHANGE statement in
CONFIG.SYS and reboot.
The parameters to the SET command are:
SET PM_ASYNC_FOCUS_CHANGE=ON | ON x | OFF
The default is OFF (disabled).
To turn it on (enable) put the following in the CONFIG.SYS file and
reboot:
SET PM_ASYNC_FOCUS_CHANGE=ON
New Function 25
July 2, 1999 - Warp 3 FixPak XR_W041
To change the timeout value put the following in the CONFIG.SYS file and
reboot:
SET PM_ASYNC_FOCUS_CHANGE=ON x
where x is in milliseconds (default is 2000 (2 seconds))
If you think you are having problems with SIQ, a way to isolate a problem
is to raise the timeout to 5000 milliseconds (5 seconds). If that does
not help, turn it off. If there is a SIQ feature problem, this will help
us (IBM) isolate it.
5.17 COMMON FILE DIALOG INTERFACE CHANGES
Beginning with FixPak XR_W017, the Common File Dialog interface has been
rearranged to improve usability. The changes are:
■ "Type of file" field moved below the Open filename.
■ "Drive" and "Directory" controls were swapped with the "File" control.
New Function 26
July 2, 1999 - Warp 3 FixPak XR_W041
6.0 CORRECTIVE SERVICE FACILITY
6.0.1 REQUIRED CSF LEVEL
You must use release level f.141 or later of the OS/2 Corrective Service
Facility to install this FixPak. Check the BUILD.LVL file for the level
you are using. If it does not have a BUILD.LVL file then it is old and
cannot be used.
6.0.2 WHERE YOU CAN FIND CSF CODE
The latest Corrective Service Facility code is available from:
ftp://service.boulder.ibm.com/ps/products/os2/fixtool/
Select the required language then the latest fixtool release (CS?140 at
the time this Fixpak was released).
The .TXT file has instructions. The .EXE is a self-extracting ZIP file
that contains the CSF code. See the READ.ME file contained in .EXE for
information on how to use the new CSF.
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_W041.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_W041
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK (if they exist), use the
numbers 10 through 36.
Corrective Service Facility 27
July 2, 1999 - Warp 3 FixPak XR_W041
Examples:
XR_W041.ADK = Corrective Service Diskette 10 (CSF DISK 10)
XR_W041.BDK = Corrective Service Diskette 11 (CSF DISK 11)
XR_W041.CDK = Corrective Service Diskette 12 (CSF DISK 12)
XR_W041.DDK = Corrective Service Diskette 13 (CSF DISK 13)
etc.
Corrective Service Facility 28
July 2, 1999 - Warp 3 FixPak XR_W041
7.0 RELOCATED OS/2 FILE SUPPORT
This FixPak will service directories based on the location of supported
SYSLEVEL.OS2 and SYSLEVEL.MPM files. Please check your system to make
sure extra copies of these files are not located in directories other
than:
\OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)
\MMOS2\INSTALL\SYSLEVEL.MPM on any partition
If additional copies of these files are found in other locations on your
hard disk then CSF will try to service files as follows:
For 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.
For SYSLEVEL.MPM
..\* all files in a directory one level above (toward the root) and
all subdirectories below. This should be the MMOS2 directory and
subdirectories.
If you have moved OS/2 files or directories, do the following in order to
have them serviced:
1. Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
OS\2 Warp partition to be serviced.
In this file, place the full path to the directory you want to be
serviced. Examples would be:
C:\JSI\*
D:\JSI\SH\*
Be sure to include the trailing * (asterisk) after the last backslash.
Note: Leave this file for any future OS/2 Warp FixPaks you might apply.
Relocated OS/2 file support 29
July 2, 1999 - Warp 3 FixPak XR_W041
8.0 LAN SERVER/WARP SERVER REMOTE IPL CONSIDERATIONS
The utility mentioned in this section is on the last FixPak disk.
■ UPDTRIPL.EXE
To support the OS/2 3.0 DAX function, the following updates must be made
to the Remote IPL(RIPL) control files:
■ Update the d:\IBMLAN\RPL\FITS\DEFALT30.FIT file to add the following
entry to the end of the file:
Z:\*.DAT OS2.30
■ For each RIPL client that is defined to boot OS/2 3.0, update the
d:\IBMLAN\RPL\FITS\client.FIT file to add the following entry to the
end of the file:
Z:\*.DAT OS2.30
Note: In the file name client is the name of the RIPL machine.
■ For each RIPL client that is defined to boot OS/2 3.0, run the
utility UPDTRIPL.EXE to update the client CONFIG.SYS and OS2.INI
files. You must specify the fully qualified path for both files as
parameters to UPDTRIPL.EXE.
The syntax of UPDTRIPL is:
UPDTRIPL client_config_sys client_os2_ini <client_boot_drive>
Each client copy of OS2.INI will be located in the
d:\IBMLAN\RPLUSER\client\OS2 directory. The os2.INI path parameter
for UPDTRIPL.EXE will be d:\IBMLAN\RPLUSER\client\OS2\OS2.INI.
Each client copy of CONFIG.SYS can be in two different directories,
depending on what type of video support the client is configured to
use. The two possibilites are:
1. If the client is configured for SVGA or S3SVGA support, the
CONFIG.SYS file will be located in the d:\IBMLAN\RPLUSER\client
directory.
Note: There will be a CONFIG.SYS file in the
d:\IBMLAN\RPL\MACHINES\client directory. However, it is not used
when the client is configured for SVGA or S3SVGA support.
2. If the client is configured for any other video type, the
CONFIG.SYS file will be located in the
d:\IBMLAN\RPL\MACHINES\client directory.
LAN Server/Warp Server Remote IPL Considerations 30
July 2, 1999 - Warp 3 FixPak XR_W041
If you are not sure which video type the client is configured to
use, do the following to determine which CONFIG.SYS the client is
using:
a. Edit the d:\IBMLAN\RPL\FITS\client.FIT file.
b. Search for the line that starts with Z:\CONFIG.SYS (assumes that
the client is using the default boot drive of Z:).
c. If the second field (target file name) is
MACHINES\client\CONFIG.SYS, the path is
d:\IBMLAN\RPL\MACHINES\client\CONFIG.SYS.
If the second field is \\servername\WRKFILES\client\CONFIG.SYS,
the path is d:\IBMLAN\RPLUSER\client\CONFIG.SYS.
Note: servername is the LAN server name.
■ Run the UPDTRIPL.EXE utility and update the default OS/2 3.0
CONFIG.SYS and OS2.INI files. The actual file names to update are
d:\IBMLAN\RPL\MACHINES\DEFALT30\CONFIG.DEF and
d:\IBMLAN\RPLUSER\DEFALT30\OS2\OS2.INI.
■ Check the Access Control Profile (ACP) for the
C:\IBMLAN\RPL\OS2.30\LANGUAGE directory. The RPLGROUP ID should have
RX access. Follow these steps to check the ACP:
1. Logon as administrator .
2. Open the drives folder under OS/2 system
3. Find the OS2.30\LANGUAGE folder under \IBMLAN\RPL
4. Select (Single-click with Left mouse button) the OS2.30\LANGUAGE
folder
5. From the pop-up menu (Single click with Right mouse button), select
"Manage Access"
6. Click on the Permissions Tab .
If the RPLGROUP ID does not have RX permissions, do the following:
1. Click on the Add button and select RPLGROUP, and click on OK
2. Add permissions Read and Execute and click on Change.
3. Click on Set (Bottom of the window)
4. Click on OK to propagate this Access Control Profile to all of the
resource's subdirectories.
LAN Server/Warp Server Remote IPL Considerations 31
July 2, 1999 - Warp 3 FixPak XR_W041
9.0 INSTALLATION PROCESS
9.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 and DISK 1 diskettes you used to install
OS/2 with. 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.
9.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
This method allows you to select the products (partitions) to be
serviced.
This is the method you should use if you have more than one OS/2
partition and want to control which one is serviced.
Note: You can use a diskette drive other than A: with this method. If
your 3.5" diskette drive is B:, use B: where A: is mentioned in the
following steps. (this method only).
1. Insert CSF DISK Diskette 1 in drive A.
2. Open an OS/2 window or full-screen session.
3. Type A:\SERVICE and press the Enter key.
Note: You could also use the "Drives" object for A: and double click
on the "SERVICE.EXE" Icon to start the install.
4. Follow the displayed instructions. When prompted to insert Corrective
Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_W041
Corrective Service Diskette 1 in drive A. Repeat for the rest of the
FixPak disks when requested to do so.
Note: 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.
5. If this is the first OS/2 Warp FixPak you have applied to this system,
then enter the path to the ARCHIVE directory where a copy of replaced
files will be stored (for example, D:\ARCHIVE).
Installation Process 32
July 2, 1999 - Warp 3 FixPak XR_W041
Note: This ARCHIVE directory is not related to the ARCHIVES directory
built into OS/2 Warp 3.0. Please specify a different path. You must
specify a different ARCHIVE directory for each product to be serviced.
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.
For either case, make sure there is sufficient space available on the
drive you specify. Even though these files are kept in compressed
(PACK2) format, they require between 7 and 12 MB of disk space.
6. Click on "OK".
7. You will see an "Application in use" dialog box showing a list of
locked files that cannot be serviced while the system is running. You
are given two choices - to Continue or Reboot. Select Continue.
8. During the installation process you might 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.
9. Select NO for a redisplay of the "Product List" after the first part
of the FixPak application process has completed if this message is
displayed.
10.Click Cancel and Exit to close the Corrective Service Facility window
if necessary.
11.Shut down and reboot your system.
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.
Installation Process 33
July 2, 1999 - Warp 3 FixPak XR_W041
9.3 METHOD 2: BOOT FROM CORRECTIVE SERVICE DISK 1.
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. 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.
1. Shut down your OS/2 system.
2. Insert CSF DISK Diskette 1 in drive A.
3. Press Ctrl+Alt+Del to boot the disk in drive A.
Service will be applied to ALL partitions that contain a version of OS/2
that is supported by this FixPak. See the section "FixPak Corrective
Service Notes" 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. In some
cases it has taken as long as 40 minutes. Please be patient and allow
this process to complete.
9.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility 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.
Installation Process 34
July 2, 1999 - Warp 3 FixPak XR_W041
10.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
something like the following for SYSLEVEL.OS2.
Before a FixPak is applied using the F.138B CSF build (or later) to a
Warp Connect system.
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 3.0 Component ID 562274700
Type 0C
Current CSD level: XR03003
Prior CSD level: XR03003
After a FixPak is applied using the F.138B CSF build (or later) to a Warp
Connect system.
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 3.0 Component ID 562274700
Type 0C
Current CSD level: XR0W040
Prior CSD level: XR03003
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 3.00
Revision n.nnn
The first page of this document has a line that looks like:
CSD level of SYSLEVEL.OS2 35
July 2, 1999 - Warp 3 FixPak XR_W041
Build Level: n.nnn
That is the number you should see for this FixPak when you issue the VER
/R command.
10.0.1 NEW SYSLEVEL.FPK
A SYSLEVEL.FPK file has been added to all Warp 3 FixPaks, beginning with
XR_W032. It is titled "OS/2 Warp 3 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 36
July 2, 1999 - Warp 3 FixPak XR_W041
11.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Product location on CSD: G:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
________________________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.02
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_3006_
System Id: 1000
Component Id: 5639A5500
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Will create the following directories
..\..\OS2\BOOK Stub File: @BOOKDIR
..\..\OS2\BOOT Stub File: @BOOTDIR
..\..\LANGUAGE\CODEPAGE Stub File: @CDEPDIR
..\..\OS2\DLL Stub File: @DLLDIR
..\..\OS2\HELP Stub File: @HELPDIR
..\..\OS2\INSTALL Stub File: @INSTDIR
..\..\LANGUAGE\KEYBOARD Stub File: @KEYBDIR
..\..\LANGUAGE\LOCALE Stub File: @LOCLDIR
..\..\OS2\MDOS Stub File: @MDOSDIR
..\..\OS2 Stub File: @OS2DIR
FixPak Corrective Service levels and disk layouts 37
July 2, 1999 - Warp 3 FixPak XR_W041
..\..\OS2\SYSTEM\PMDF Stub File: @PMDFDIR
..\..\OS2\SYSTEM\RAS Stub File: @RASDIR
..\..\OS2\SYSTEM Stub File: @SYSTDIR
..\..\OS2\SYSTEM\TRACE Stub File: @TRACDIR
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
AA.KBL AA.KB_ 11 04/09/1999 15:34 1200 597886AD
AA470.KBL AA470.KB_ 11 04/09/1999 15:34 1212 7546A488
ARCINST.EXE ARCINST.EX_ 10 04/12/1999 15:41 19798 20C0824E
ARCRECOV.EXE ARCRECOV.EX_ 10 04/12/1999 15:41 21871 D6E921CB
ASIACOL.DLL ASIACOL.DL_ 5 04/09/1999 15:37 158758 360EF63F
BA.KBL BA.KB_ 11 04/09/1999 15:34 980 EE4D90B0
BACKUP.EXE BACKUP.EX_ 10 04/12/1999 11:16 32736 6579B295
BDCALLS.DLL BDCALLS.DL_ 10 01/08/1998 18:09 37594 AB19A4D2
BE.KBL BE.KB_ 11 04/09/1999 15:34 972 47EAAF28
BG.KBL BG.KB_ 11 04/09/1999 15:34 1152 66CAA475
BG241.KBL BG241.KB_ 11 04/09/1999 15:34 1372 012C8BAB
BLDLEVEL.EXE BLDLEVEL.EX_ 10 04/12/1999 12:30 21523 9640532C
BOOT.COM BOOT.CO_ 10 04/12/1999 11:40 43056 B29DC23E
BOOTDISK.EXE BOOTDISK.EX_ 9 04/12/1999 13:17 48777 5DA1163C
BR.KBL BR.KB_ 11 04/09/1999 15:34 932 4F618D94
BR274.KBL BR274.KB_ 11 04/09/1999 15:34 852 ECBE2F29
BVHWNDW.DLL BVHWNDW.DL_ 10 02/17/1998 15:37 14233 8D9351FA
BVSCALLS.DLL BVSCALLS.DL_ 11 08/26/1998 01:32 512 4062D2D3
BY.KBL BY.KB_ 11 04/09/1999 15:34 1292 5060D151
CA.KBL CA.KB_ 11 04/09/1999 15:34 1214 B7CA68BE
CALC.EXE CALC.EX_ 10 03/09/1999 11:03 43056 4DBB480B
CALENDAR.EXE CALENDAR.EX_ 9 03/09/1999 11:04 59808 654093A6
CARDFILE.EXE CARDFILE.EX_ 9 03/09/1999 11:05 93184 8ADA0796
CARDINFO.DAT CARDINFO.DA_ 11 12/07/1998 10:00 29787 A7CC262B
CDFS.IFS CDFS.IF_ 10 04/12/1999 10:39 45151 87465DA4
CDFS.TDF CDFS.TD_ 11 04/12/1999 10:39 2113 79118068
CDROM.TBL CDROM.TB_ 11 03/12/1997 17:33 3658 2E9C608F
CF.KBL CF.KB_ 11 04/09/1999 15:34 956 96C22906
CHARMAP.EXE CHARMAP.EX_ 10 03/09/1999 11:17 22016 15A2A957
CHKDSK.COM CHKDSK.CO_ 8 04/12/1999 11:22 68656 1CCB0D34
CHKDSK.SYS CHKDSK.SY_ 11 01/09/1998 15:23 747 120CD4C8
CHKDSK32.DLL CHKDSK32.DL_ 7 04/12/1999 10:26 170023 79A65BD0
CHKDSK32.EXE CHKDSK32.EX_ 11 04/12/1999 10:15 6417 DE16AADB
CLDAPI.DLL CLDAPI.DL_ 10 12/04/1998 23:11 22217 04E59D17
CLIPBRD.EXE CLIPBRD.EX_ 10 03/09/1999 11:05 18496 B447409C
CLOCK.EXE CLOCK.EX_ 11 03/09/1999 11:06 16400 F030944F
CMD.EXE CMD.EX_ 7 04/12/1999 11:27 71552 815B1095
FixPak Corrective Service levels and disk layouts 38
July 2, 1999 - Warp 3 FixPak XR_W041
COMM.DRV COMM.DR_ 11 03/09/1999 12:59 9552 2A57B5F2
COMMAND.COM COMMAND.CO_ 9 04/12/1999 11:25 53014 8C933046
COMMDLG.DLL COMMDLG.DL_ 8 03/09/1999 11:01 87072 A6A7A78B
COMMONA.DSP COMMONA.DS_ 11 03/27/1998 14:21 429 CD1C47BE
CONTROL.EXE CONTROL.EX_ 10 03/09/1999 11:42 15856 2BA1BC09
COUNTRY.SYS COUNTRY.SY_ 11 04/12/1999 15:32 50932 0A626673
COUR.OFM COUR.OF_ 11 01/13/1998 14:37 4236 61F4AD1D
COUR.PFB COUR.PF_ 5 01/13/1998 14:37 112702 F4781C19
COUR.PFM COUR1.PF_ 11 01/13/1998 14:37 674 EB1E4968
COURB.OFM COURB.OF_ 11 01/13/1998 14:37 4246 9BB1D3E4
COURB.PFB COURB.PF_ 5 01/13/1998 14:37 116938 10A27222
COURB.PFM COU1.PF_ 11 01/13/1998 14:37 679 1EF9C16B
COURBI.OFM COURBI.OF_ 11 01/13/1998 14:37 4260 8E906AF3
COURBI.PFB COURBI.PF_ 5 01/13/1998 14:37 112484 87594829
COURBI.PFM COURB1.PF_ 11 01/13/1998 14:37 685 D0390DEF
COURI.OFM COURI.OF_ 11 01/13/1998 14:37 4251 429FA3B8
COURI.PFB COURI.PF_ 5 01/13/1998 14:37 113244 48B10D0F
COURI.PFM COUR2.PF_ 11 01/13/1998 14:37 681 A6EEB6C2
COURIER.FON COURIER.FO_ 10 01/19/1998 13:35 104183 CE3B8B00
CZ.KBL CZ.KB_ 11 04/09/1999 15:34 1014 4C4E42B8
DDEML.DLL DDEML.DL_ 10 03/09/1999 11:01 36864 BFC240CF
DDINSTAL.EXE DDINSTAL.EX_ 9 04/12/1999 12:00 35367 8C164092
DE.KBL DE.KB_ 11 04/09/1999 15:34 958 E417FFD5
DE453.KBL DE453.KB_ 11 04/09/1999 15:34 1354 0C1FC811
DISPLAY.DLL DISPLAY.DL_ 9 04/07/1999 15:46 46574 02EEAA8C
DK.KBL DK.KB_ 11 04/09/1999 15:34 928 3D2D683D
DMCOLOR.DLL DMCOLOR.DL_ 10 03/09/1999 12:10 18480 A0B80A14
DMQSPROF.DLL DMQSPROF.DL_ 9 08/26/1998 04:01 43278 776B6CF4
DRWATSON.EXE DRWATSON.EX_ 10 03/09/1999 11:55 26864 2F1AB16C
DSPINSTL.EXE DSPINSTL.EX_ 4 04/12/1999 12:37 112216 3547FF89
DSPRES.DLL DSPRES2.DL_ 4 01/19/1998 13:35 250598 F60E4E27
DSPRES.DLL DSPRES1.DL_ 4 01/19/1998 13:35 250598 F60F2627
DSPRES.DLL DSPRES.DL_ 4 01/19/1998 13:35 250598 F60F8627
DTRACE.DOC DTRACE.DO_ 10 01/07/1998 17:11 75371 73765F8B
DTRACE.EXE DTRACE.EX_ 8 04/12/1999 10:07 48906 59D7059F
E.EXE E.EX_ 9 04/12/1999 11:14 48389 6FAED8BE
EAUTIL.EXE EAUTIL.EX_ 10 04/12/1999 11:41 37984 F2218E04
EE.KBL EE.KB_ 11 04/09/1999 15:34 932 0C7B1D40
EJECT.EXE EJECT.EX_ 10 01/14/1998 16:27 25649 0575A5C8
EL.KBL EL.KB_ 11 04/09/1999 15:34 1396 B76E4B7E
EL220.KBL EL220.KB_ 11 04/09/1999 15:34 1428 06719AD1
EL459.KBL EL459.KB_ 11 04/09/1999 15:34 1372 8C941E52
ES.KBL ES.KB_ 11 04/09/1999 15:34 920 FF749BFC
EXPAND.EXE EXPAND.EX_ 10 03/09/1999 10:57 25432 C8747372
FDISK.COM FDISK.CO_ 7 04/12/1999 10:47 113658 E3D27C62
FDISKPM.DLL FDISKPM.DL_ 11 03/24/1998 16:10 8244 08483FBF
FDISKPM.EXE FDISKPM.EX_ 8 04/12/1999 10:47 63043 ED2738C5
FI.KBL FI.KB_ 11 04/09/1999 15:34 940 6FE4DEC8
FINSTALL.DLL FINSTALL.DL_ 6 03/09/1999 12:17 200368 11726450
FLASHPT.ADD FLASHPT.AD_ 9 03/22/1999 17:06 57125 184D7C69
FORMAT.COM FORMAT.CO_ 9 04/12/1999 11:50 69920 FA976BEA
FixPak Corrective Service levels and disk layouts 39
July 2, 1999 - Warp 3 FixPak XR_W041
FR.KBL FR.KB_ 11 04/09/1999 15:34 950 562DD4F5
FSFILTER.SYS FSFILTER.SY_ 11 04/12/1999 12:03 12988 C2828617
GDI.EXE GDI.EX_ 4 03/09/1999 11:31 225744 12AFFFDA
GRADD.SYS GRADD.SY_ 11 04/07/1999 17:44 1195 98CBC4DC
GRE2VMAN.DLL GRE2VMAN.DL_ 10 04/07/1999 17:43 17901 95F8D684
HARDERR.EXE HARDERR.EX_ 11 04/12/1999 10:51 9416 4DD5AE54
HELPMGR.DLL HELPMGR.DL_ 4 04/12/1999 11:46 176624 3BA02469
HELPMSG.EXE HELPMSG.EX_ 10 04/12/1999 11:51 36256 5C75B44D
HELV.FON HELV.FO_ 6 01/19/1998 13:36 264425 4DF3AFF3
HELV.OFM HELV.OF_ 11 03/12/1998 09:41 4865 E5B1D229
HELV.PFB HELV.PF_ 6 03/12/1998 09:41 101942 062961BB
HELV.PFM HEL1.PF_ 11 03/12/1998 09:41 1096 C7229657
HELVB.OFM HELVB.OF_ 11 03/12/1998 09:41 4857 C0D826BD
HELVB.PFB HELVB.PF_ 6 03/12/1998 09:41 104404 D1A00EE1
HELVB.PFM HELV1.PF_ 11 03/12/1998 09:41 1089 DA484DE0
HELVBI.OFM HELVBI.OF_ 11 03/12/1998 09:41 4859 F81293A2
HELVBI.PFB HELVBI.PF_ 6 03/12/1998 09:41 105074 CEC85E28
HELVBI.PFM HELVB1.PF_ 11 03/12/1998 09:41 1087 0654ED9D
HELVI.OFM HELVI.OF_ 11 03/12/1998 09:41 4844 499A03B7
HELVI.PFB HELVI.PF_ 6 03/12/1998 09:41 103996 F3AEF6CF
HELVI.PFM HELV2.PF_ 11 03/12/1998 09:41 1079 4D475D83
HPFS.IFS HPFS.IF_ 7 04/12/1999 10:31 144450 920E06CE
HPFS.TDF HPFS.TD_ 11 04/12/1999 10:31 1620 1E3A3A60
HR.KBL HR.KB_ 11 04/09/1999 15:34 982 04524FA3
HU.KBL HU.KB_ 11 04/09/1999 15:34 1006 A5381FC1
IBM1004 IBM1004.___ 11 04/09/1999 15:33 3584 8EF1D2DA
IBM1006 IBM1006.___ 11 04/09/1999 15:33 3040 9F3D16EA
IBM1008 IBM1008.___ 11 04/09/1999 15:33 2816 1D6F4BA2
IBM1025 IBM1025.___ 11 04/09/1999 15:33 2560 986B84AB
IBM1026 IBM1026.___ 11 04/09/1999 15:33 2560 045F5F07
IBM1027 IBM1027.___ 11 04/09/1999 15:33 2304 D8C3E865
IBM1028 IBM1028.___ 11 04/09/1999 15:33 3072 AB110D8F
IBM1038 IBM1038.___ 11 04/09/1999 15:33 4608 CAD157DA
IBM1041 IBM1041.___ 11 04/09/1999 15:33 3296 C8B7A1FD
IBM1043 IBM1043.___ 11 04/09/1999 15:33 3040 D3960D3E
IBM1046 IBM1046.___ 11 04/09/1999 15:33 3040 27576DA9
IBM1047 IBM1047.___ 11 04/09/1999 15:33 2304 D337A73A
IBM1051 IBM1051.___ 11 04/09/1999 15:33 3296 15CBB68F
IBM1088 IBM1088.___ 11 04/09/1999 15:33 3552 F27F8E09
IBM1089 IBM1089.___ 11 04/09/1999 15:33 2560 CF9D63E6
IBM1092 IBM1092.___ 11 04/09/1999 15:33 4832 5814A91C
IBM1097 IBM1097.___ 11 04/09/1999 15:33 3040 79006877
IBM1098 IBM1098.___ 11 04/09/1999 15:33 4576 9DA753D7
IBM1112 IBM1112.___ 11 04/09/1999 15:33 2528 F4C7A297
IBM1114 IBM1114.___ 11 04/09/1999 15:33 3552 60752DCA
IBM1115 IBM1115.___ 11 04/09/1999 15:33 3296 0204EEEE
IBM1116 IBM1116.___ 11 04/09/1999 15:33 3808 B2703DC6
IBM1117 IBM1117.___ 11 04/09/1999 15:33 3552 E8CCCEC9
IBM1118 IBM1118.___ 11 04/09/1999 15:33 4320 6D8E839D
IBM1119 IBM1119.___ 11 04/09/1999 15:33 4096 98B8B343
IBM1122 IBM1122.___ 11 04/09/1999 15:33 2560 655835E2
FixPak Corrective Service levels and disk layouts 40
July 2, 1999 - Warp 3 FixPak XR_W041
IBM1123 IBM1123.___ 11 04/09/1999 15:33 2528 A323E941
IBM1124 IBM1124.___ 11 04/09/1999 15:33 2528 CE9CBE79
IBM1125 IBM1125.___ 11 04/09/1999 15:33 4320 02358C47
IBM1131 IBM1131.___ 11 04/09/1999 15:33 4320 B3BAD682
IBM1200 IBM1200.___ 11 04/09/1999 15:33 2784 E57F8681
IBM1207 IBM1207.___ 11 04/09/1999 15:33 704 BF42079F
IBM1208 IBM1208.___ 11 04/09/1999 15:33 720 53F45153
IBM1250 IBM1250.___ 11 04/09/1999 15:33 3552 3B327CBF
IBM1251 IBM1251.___ 11 04/09/1999 15:33 3328 EC5ECAEC
IBM1252 IBM1252.___ 11 04/09/1999 15:33 3552 AEEDDBC1
IBM1253 IBM1253.___ 11 04/09/1999 15:33 3552 B265BFF8
IBM1254 IBM1254.___ 11 04/09/1999 15:33 3552 A8DFEE3A
IBM1255 IBM1255.___ 11 04/09/1999 15:33 3808 152518CD
IBM1256 IBM1256.___ 11 04/09/1999 15:33 4320 8CFB62EA
IBM1257 IBM1257.___ 11 04/09/1999 15:33 3296 2080348D
IBM1275 IBM1275.___ 11 04/09/1999 15:33 5600 EA2161C6
IBM1276 IBM1276.___ 11 04/09/1999 15:33 3072 AB270972
IBM1277 IBM1277.___ 11 04/09/1999 15:33 2816 375A9561
IBM1280 IBM1280.___ 11 04/09/1999 15:33 4832 D64F99F2
IBM1281 IBM1281.___ 11 04/09/1999 15:33 5344 BCE23BB2
IBM1282 IBM1282.___ 11 04/09/1999 15:33 5120 1ACFCA00
IBM1283 IBM1283.___ 11 04/09/1999 15:33 4832 B892D655
IBM1381 IBM1381.___ 8 04/09/1999 15:33 109792 5D338957
IBM1383 IBM1383.___ 8 04/09/1999 15:33 127344 23CFD8B8
IBM1386 IBM1386.___ 3 04/09/1999 15:33 125200 295908ED
IBM259 IBM259.___ 11 04/09/1999 15:33 4864 F6D0ABBB
IBM273 IBM273.___ 11 04/09/1999 15:33 2304 0F8843F7
IBM277 IBM277.___ 11 04/09/1999 15:33 2304 25CC48A2
IBM278 IBM278.___ 11 04/09/1999 15:33 2304 B71290CB
IBM280 IBM280.___ 11 04/09/1999 15:33 2272 5C9B9827
IBM282 IBM282.___ 11 04/09/1999 15:33 2272 2FEC2C92
IBM284 IBM284.___ 11 04/09/1999 15:33 2304 0FC1C396
IBM285 IBM285.___ 11 04/09/1999 15:33 2304 A3401CA5
IBM290 IBM290.___ 11 04/09/1999 15:33 2272 B5549281
IBM293 IBM293.___ 11 04/09/1999 15:33 3040 349B3700
IBM297 IBM297.___ 11 04/09/1999 15:33 2272 14553F53
IBM2TI1.EXE IBM2TI1.EX_ 11 05/13/1996 21:15 9886 3A48A23D
IBM2TI1.SYS IBM2TI1.SY_ 11 05/13/1996 21:15 9886 6A51A248
IBM300 IBM300.___ 8 04/09/1999 15:33 94432 80947F83
IBM301 IBM301.___ 9 04/09/1999 15:33 83168 2CA71676
IBM361 IBM361.___ 11 04/09/1999 15:33 3584 CAE20453
IBM363 IBM363.___ 11 04/09/1999 15:33 4864 73F4574C
IBM367 IBM367.___ 11 04/09/1999 15:33 2016 C4621B51
IBM37 IBM37.___ 11 04/09/1999 15:33 2304 43042630
IBM382 IBM382.___ 11 04/09/1999 15:33 3584 7C9B40DF
IBM383 IBM383.___ 11 04/09/1999 15:33 3584 EA574B65
IBM385 IBM385.___ 11 04/09/1999 15:33 3584 5CB36840
IBM386 IBM386.___ 11 04/09/1999 15:33 3584 8EBA4D48
IBM387 IBM387.___ 11 04/09/1999 15:33 3584 AF4AFD3A
IBM388 IBM388.___ 11 04/09/1999 15:33 3584 166ABA8B
IBM389 IBM389.___ 11 04/09/1999 15:33 3584 42F542AB
FixPak Corrective Service levels and disk layouts 41
July 2, 1999 - Warp 3 FixPak XR_W041
IBM391 IBM391.___ 11 04/09/1999 15:33 3584 C0A088BF
IBM392 IBM392.___ 11 04/09/1999 15:33 3584 04A37CE1
IBM393 IBM393.___ 11 04/09/1999 15:33 3584 0347670F
IBM394 IBM394.___ 11 04/09/1999 15:33 3584 A34377C1
IBM395 IBM395.___ 11 04/09/1999 15:33 3584 DF9ED7AD
IBM420 IBM420.___ 11 04/09/1999 15:33 3040 7AC041EB
IBM424 IBM424.___ 11 04/09/1999 15:33 2528 7653B4F8
IBM437 IBM437.___ 11 04/09/1999 15:33 4576 D21DF2C1
IBM500 IBM500.___ 11 04/09/1999 15:33 2304 D56F3E81
IBM813 IBM813.___ 11 04/09/1999 15:33 3072 B85A5B3F
IBM819 IBM819.___ 11 04/09/1999 15:33 2816 7B9B92EF
IBM829 IBM829.___ 11 04/09/1999 15:33 3840 FE70F736
IBM833 IBM833.___ 11 04/09/1999 15:33 2272 5810DC4D
IBM834 IBM834.___ 8 04/09/1999 15:33 148704 754FE0C3
IBM835 IBM835.___ 7 04/09/1999 15:33 125152 8454CE4D
IBM836 IBM836.___ 11 04/09/1999 15:33 2272 4C66A728
IBM837 IBM837.___ 8 04/09/1999 15:33 84704 9391EA05
IBM838 IBM838.___ 11 04/09/1999 15:33 2272 713EC852
IBM850 IBM850.___ 11 04/09/1999 15:33 4320 D815C34B
IBM851 IBM851.___ 11 04/09/1999 15:33 3840 7990F3E9
IBM852 IBM852.___ 11 04/09/1999 15:33 4608 6CD5CD71
IBM855 IBM855.___ 11 04/09/1999 15:33 4320 E61069ED
IBM856 IBM856.___ 11 04/09/1999 15:33 4064 2F6EB19A
IBM857 IBM857.___ 11 04/09/1999 15:33 4352 5EFE84D4
IBM860 IBM860.___ 11 04/09/1999 15:33 4320 1A5A7BE4
IBM861 IBM861.___ 11 04/09/1999 15:33 4064 E0A459F0
IBM862 IBM862.___ 11 04/09/1999 15:33 4576 1EAF3925
IBM863 IBM863.___ 11 04/09/1999 15:33 4096 940B5AD7
IBM864 IBM864.___ 11 04/09/1999 15:33 4576 64CD5028
IBM865 IBM865.___ 11 04/09/1999 15:33 4064 5C147563
IBM866 IBM866.___ 11 04/09/1999 15:33 4320 02136943
IBM868 IBM868.___ 11 04/09/1999 15:33 4576 EF57BF22
IBM869 IBM869.___ 11 04/09/1999 15:33 4320 B01582ED
IBM870 IBM870.___ 11 04/09/1999 15:33 2560 B5099E85
IBM871 IBM871.___ 11 04/09/1999 15:33 2304 A2B6D07A
IBM874 IBM874.___ 11 04/09/1999 15:33 2784 9B7C2741
IBM875 IBM875.___ 11 04/09/1999 15:33 2528 6C34063F
IBM878 IBM878.___ 11 04/09/1999 15:33 3328 92B84151
IBM891 IBM891.___ 11 04/09/1999 15:33 3296 8A62ABAC
IBM895 IBM895.___ 11 04/09/1999 15:33 2304 80220C09
IBM896 IBM896.___ 11 04/09/1999 15:33 2048 B04ACD25
IBM897 IBM897.___ 11 04/09/1999 15:33 3296 33FE015A
IBM903 IBM903.___ 11 04/09/1999 15:33 3296 8D0017B1
IBM904 IBM904.___ 11 04/09/1999 15:33 3040 169DC2B5
IBM907 IBM907.___ 11 04/09/1999 15:33 3808 44692568
IBM909 IBM909.___ 11 04/09/1999 15:33 3808 F69EA2A2
IBM910 IBM910.___ 11 04/09/1999 15:33 3808 2062A1F2
IBM912 IBM912.___ 11 04/09/1999 15:33 2560 5A96D744
IBM913 IBM913.___ 11 04/09/1999 15:33 2560 D8A99190
IBM914 IBM914.___ 11 04/09/1999 15:33 2560 5D3DADE2
IBM915 IBM915.___ 11 04/09/1999 15:33 2560 8899C3C1
FixPak Corrective Service levels and disk layouts 42
July 2, 1999 - Warp 3 FixPak XR_W041
IBM916 IBM916.___ 11 04/09/1999 15:33 2560 E2D138F0
IBM918 IBM918.___ 11 04/09/1999 15:33 3040 313DD1F1
IBM920 IBM920.___ 11 04/09/1999 15:33 2560 C2EB2A17
IBM921 IBM921.___ 11 04/09/1999 15:33 3040 ED4F1F6C
IBM922 IBM922.___ 11 04/09/1999 15:33 3040 A107357C
IBM930 IBM930.___ 8 04/09/1999 15:33 94976 25865AAB
IBM931 IBM931.___ 8 04/09/1999 15:33 94976 5059DB30
IBM933 IBM933.___ 8 04/09/1999 15:33 149248 ECD443EA
IBM935 IBM935.___ 8 04/09/1999 15:33 85248 705619A6
IBM937 IBM937.___ 7 04/09/1999 15:33 125696 E8DF997C
IBM939 IBM939.___ 7 04/09/1999 15:33 94976 81C851E9
IBM941 IBM941.___ 8 04/09/1999 15:33 87264 627C2ADF
IBM942 IBM942.___ 8 04/09/1999 15:33 83712 31794448
IBM943 IBM943.___ 8 04/09/1999 15:33 87808 A404FD62
IBM944 IBM944.___ 8 04/09/1999 15:33 112896 B88E959D
IBM946 IBM946.___ 8 04/09/1999 15:33 84736 D336691F
IBM947 IBM947.___ 7 04/09/1999 15:33 131808 65279921
IBM948 IBM948.___ 7 04/09/1999 15:33 125696 C43BBB16
IBM949 IBM949.___ 8 04/09/1999 15:33 136448 13CD9892
IBM950 IBM950.___ 6 04/09/1999 15:33 132352 6DA8A290
IBM952 IBM952.___ 9 04/09/1999 15:33 89856 07393D9F
IBM953 IBM953.___ 9 04/09/1999 15:33 83200 80B12D53
IBM954 IBM954.___ 8 04/09/1999 15:33 140864 557F9FB8
IBM955 IBM955.___ 9 04/09/1999 15:33 89856 84E09B1F
IBM964 IBM964.___ 6 04/09/1999 15:33 174456 0B397EE9
IBM970 IBM970.___ 8 04/09/1999 15:33 169776 B7FBFC3A
IBM971 IBM971.___ 9 04/09/1999 15:33 124160 C4391575
IFGDI2VM.DRV IFGDI2VM.DR_ 9 04/07/1999 16:06 92520 E81825AD
IL.KBL IL.KB_ 11 04/09/1999 15:34 1232 F1C76CC2
INSCFG32.DLL INSCFG32.DL_ 9 04/12/1999 08:51 32594 5691C58C
INSPGM32.DLL INSPGM32.DL_ 9 04/12/1999 08:52 41424 4E2ECBDD
IS.KBL IS.KB_ 11 04/09/1999 15:34 940 040B4152
IS458.KBL IS458.KB_ 11 04/09/1999 15:34 928 3D6742AF
ISGDI2VM.DRV ISGDI2VM.DR_ 9 04/07/1999 16:06 91328 13DF9230
IT.KBL IT.KB_ 11 04/09/1999 15:34 876 130F54A8
IT142.KBL IT142.KB_ 11 04/09/1999 15:34 854 D12D2A22
JP.KBL JP.KB_ 11 04/09/1999 15:34 6374 1FF7EDB6
KBDBASE.SYS KBDBASE.SY_ 10 04/08/1999 08:05 24957 D187534C
KEYB.COM KEYB.CO_ 11 04/12/1999 11:52 11573 BD48D3D1
KEYBOARD.DCP KEYBOARD.DC_ 10 04/09/1999 15:35 315109 74E816AF
KEYBOARD.DRV KEYBOARD.DR_ 11 03/09/1999 12:56 7568 D499A9D9
KR.KBL KR.KB_ 11 04/09/1999 15:34 724 E8D3BE6C
LA.KBL LA.KB_ 11 04/09/1999 15:34 916 84D10513
LIBCM.DLL LIBCM.DL_ 4 04/08/1999 16:09 210916 98DAC306
LIBCN.DLL LIBCN.DL_ 8 04/08/1999 16:08 57340 7BBE3105
LIBCS.DLL LIBCS.DL_ 4 04/08/1999 16:08 192386 978D3E9F
LIBUNI.DLL LIBUNI.DL_ 7 04/09/1999 15:32 81372 89A67904
LINK386.EXE LINK386.EX_ 6 04/12/1999 12:02 154164 9DECEE53
LOCALE.DLL LOCALE.DL_ 6 04/09/1999 15:33 107901 1ACCD15A
LT.KBL LT.KB_ 11 04/09/1999 15:34 1972 F4B94E9C
LV.KBL LV.KB_ 11 04/09/1999 15:34 1404 AA6A3BCC
FixPak Corrective Service levels and disk layouts 43
July 2, 1999 - Warp 3 FixPak XR_W041
LZEXPAND.DLL LZEXPAND.DL_ 10 03/09/1999 10:58 69040 082B4C29
MAIN.CPL MAIN.CP_ 7 03/09/1999 11:42 147680 EAD83A7F
MAKETSF.EXE MAKETSF.EX_ 9 04/12/1999 12:23 43104 094B1425
MAPTSF.CMD MAPTSF.CM_ 11 04/05/1999 09:56 16803 E9C1489C
MCICDA.DRV MCICDA.DR_ 11 03/09/1999 12:01 13824 DDA44321
MCISEQ.DRV MCISEQ.DR_ 10 03/09/1999 12:01 25328 F6013BE4
MCIWAVE.DRV MCIWAVE.DR_ 10 03/09/1999 12:00 28160 802B238C
MIDIMAP.DRV MIDIMAP.DR_ 9 03/09/1999 12:02 52800 F08C543E
MIGRATE.EXE MIGRATE.EX_ 6 04/12/1999 12:19 119434 B2AA19B2
MINXOBJ.DLL MINXOBJ.DL_ 10 04/12/1999 12:56 27423 99C551E6
MIRRORS.DLL MIRRORS.DL_ 2 03/12/1997 16:38 444744 4D9372B9
MK.KBL MK.KB_ 11 04/09/1999 15:34 1302 41F3D753
MMSOUND.DRV MMSOUND.DR_ 11 03/09/1999 11:56 3456 97C27950
MMSYSTEM.DLL MMSYSTEM.DL_ 9 03/09/1999 11:56 61648 517ECC25
MMTASK.TSK MMTASK.TS_ 11 03/09/1999 11:56 1104 8E1E7D5B
MOUSE.DRV MOUSE.DR_ 11 03/09/1999 12:59 10896 7B98464C
MPLAYER.EXE MPLAYER.EX_ 10 03/09/1999 12:04 33312 C20B034D
MPU401.DRV MPU401.DR_ 11 03/09/1999 12:00 7088 907D182B
MSADLIB.DRV MSADLIB.DR_ 11 03/09/1999 11:57 22048 829DE0E6
NL.KBL NL.KB_ 11 04/09/1999 15:34 954 A4EF6074
NO.KBL NO.KB_ 11 04/09/1999 15:34 920 6F219407
NOTEPAD.EXE NOTEPAD.EX_ 10 03/09/1999 11:06 32736 2A15B56F
NPXEMLTR.DLL NPXEMLTR.DL_ 10 08/26/1998 04:02 21812 4DB4E853
NWIAPI.DLL NWIAPI.DL_ 11 04/12/1999 08:46 9201 F1C26D6B
OLECLI.DLL OLECLI.DL_ 9 03/09/1999 10:59 83456 30B1BAF6
OS2CHAR.DLL OS2CHAR.DL_ 11 08/26/1998 00:50 512 E828A77D
OS2DASD.DMD OS2DASD.DM_ 10 03/22/1999 16:59 40876 0451B20B
OS2DUMP OS2DUMP.___ 11 07/02/1999 09:20 14301 05F526C0
OS2K386.EXE OS2K386.EX_ 7 03/09/1999 11:33 80306 5142D240
OS2LDR.MSG OS2LDR.MS_ 11 04/12/1999 08:48 8737 5E8DBAE1
OS2MM.DLL OS2MM.DL_ 3 12/07/1998 10:04 243830 D7015BE0
OS2UGL OS2UGL.___ 11 04/09/1999 15:33 15616 AC7FB976
OSO001.MSG OSO001.MS_ 7 12/04/1998 17:55 175769 8BE4D642
OSO001H.MSG OSO001H.MS_ 7 12/04/1998 17:55 241212 303B8881
PACKAGER.EXE PACKAGER.EX_ 9 03/09/1999 11:07 76464 B1B4C782
PBRUSH.EXE PBRUSH.EX_ 6 03/09/1999 11:09 183360 486BEABF
PDFSLA.EXE PDFSLA.EX_ 10 12/04/1998 23:27 18226 8A465978
PDUMPSYS.EXE PDUMPSYS.EX_ 9 04/12/1999 13:28 34365 5820CCDD
PDUMPUSR.EXE PDUMPUSR.EX_ 9 04/12/1999 13:28 34363 2591EC90
PL.KBL PL.KB_ 11 04/09/1999 15:34 980 A865EE5D
PL457.KBL PL457.KB_ 11 04/09/1999 15:34 882 3F4F66C8
PMATM.DLL PMATM.DL_ 2 03/15/1999 18:36 224319 91C7F566
PMBIND.DLL PMBIND.DL_ 10 04/12/1999 11:59 60162 7B6973E4
PMCHKDSK.EXE PMCHKDSK.EX_ 10 04/12/1999 12:04 28183 338609A7
PMCLIP.DLL PMCLIP.DL_ 10 04/12/1999 12:38 21249 AF696142
PMCTLS.DLL PMCTLS.DL_ 2 04/12/1999 08:58 568344 B1AFD0D7
PMDDE.DLL PMDDE.DL_ 10 04/12/1999 12:39 28206 E03D4117
PMDF.HLP PMDF.HL_ 7 01/09/1998 07:27 99751 BCE9E3DD
PMDFMSG.DLL PMDFMSG.DL_ 9 01/09/1998 07:28 44436 D5669EA9
PMDRAG.DLL PMDRAG.DL_ 11 04/12/1999 08:57 1731 801EFF0C
PMGPI.DLL PMGPI.DL_ 1 04/05/1999 15:11 222594 C0B2192C
FixPak Corrective Service levels and disk layouts 44
July 2, 1999 - Warp 3 FixPak XR_W041
PMGRE.DLL PMGRE.DL_ 11 04/14/1999 15:38 2231 B30E2F80
PMMLE.DLL PMMLE.DL_ 11 12/04/1998 18:40 673 FC270A79
PMPIC.DLL PMPIC.DL_ 9 04/12/1999 11:30 34870 42A64148
PMPIC.TDF PMPIC.TD_ 11 04/12/1999 11:30 400 1E12F515
PMPRINT.QPR PMPRINT.QP_ 10 10/14/1998 21:04 12657 9EA7F669
PMSDMRI.DLL PMSDMRI.DL_ 11 06/17/1998 16:54 13312 FD985BFF
PMSEEK.EXE PMSEEK.EX_ 10 04/12/1999 12:11 31285 7E29F660
PMSHAPI.DLL PMSHAPI.DL_ 11 01/08/1998 16:40 4549 4AE92C56
PMSPL.DLL PMSPL.DL_ 3 04/05/1999 18:03 285639 5DF042B7
PMSPL.TDF PMSPL.TD_ 11 04/05/1999 18:03 6930 5E8D2E7E
PMVDMP.DLL PMVDMP.DL_ 9 04/12/1999 11:12 42973 512E13A8
PMVDMP.TDF PMVDMP.TD_ 11 04/12/1999 11:12 1786 41C53F62
PMVIOP.DLL PMVIOP.DL_ 8 04/12/1999 11:11 57740 13793B68
PMVIOP.TDF PMVIOP.TD_ 11 04/12/1999 11:11 2326 3DC29FB6
PMWIN.DLL PMWIN.DL_ 11 04/19/1999 17:59 11264 901AE194
PMWP.DLL PMWP.DL_ 1 04/12/1999 15:57 963889 A7E9F927
PMWP.TDF PMWP.TD_ 11 04/12/1999 15:57 10855 27A84419
PMWPMRI.DLL PMWPMRI.DL_ 9 04/12/1999 15:42 46054 4C7AFC84
PO.KBL PO.KB_ 11 04/09/1999 15:34 926 880ECFFE
PRINTMAN.EXE PRINTMAN.EX_ 10 03/09/1999 11:43 43248 49D044E5
PROCDUMP.DOC PROCDUMP.DO_ 10 07/29/1998 18:07 63273 17F21459
PROCDUMP.EXE PROCDUMP.EX_ 9 04/12/1999 13:28 47647 6C55D79E
PROGMAN.EXE PROGMAN.EX_ 8 03/09/1999 11:40 115328 D9CE06C3
PSSDMON.EXE PSSDMON.EX_ 10 04/05/1999 19:58 27117 F6CC23D8
PSTAT.EXE PSTAT.EX_ 10 05/20/1999 16:16 11300 A4974578
PVDAPI.DLL PVDAPI.DL_ 10 12/04/1998 23:12 20398 7801606F
QUECALLS.DLL QUECALLS.DL_ 11 08/26/1998 01:30 1024 DB25D550
RAS001.MSG RAS001.MS_ 10 01/09/1998 07:20 25739 7A21EDDD
RASH.MSG RASH.MS_ 11 01/09/1998 07:20 11581 98CABC4F
README.DBG README.DB_ 11 05/20/1999 13:28 22934 0E0AEEF7
RECOVER.COM RECOVER.CO_ 9 04/12/1999 12:12 48704 97FFD456
RESTORE.EXE RESTORE.EX_ 10 04/12/1999 12:13 36080 D990E82D
REXX.DLL REXX.DL_ 4 04/05/1999 09:56 266031 2C928B8E
REXXAPI.DLL REXXAPI.DL_ 10 07/07/1998 16:42 40995 21EBF324
REXXUTIL.DLL REXXUTIL.DL_ 8 12/04/1998 17:08 49229 5FDA80BF
RMINFO.DLL RMINFO.DL_ 10 03/16/1999 08:58 23696 81FC1830
RO.KBL RO.KB_ 11 04/09/1999 15:34 944 B0003D4C
RSPDSPI.EXE RSPDSPI.EX_ 7 04/12/1999 12:37 93192 37D9B0C9
RU.KBL RU.KB_ 11 04/09/1999 15:34 1144 6F2AF864
RU441.KBL RU441.KB_ 11 04/09/1999 15:34 1260 0A634A58
S8514.DRV S8514.DR_ 9 03/09/1999 12:34 89776 E16C8A2F
SD.KBL SD.KB_ 11 04/09/1999 15:34 1036 18589C14
SEAMLESS.DLL SEAMLESS.DL_ 10 04/12/1999 11:53 49125 CC4F8FB0
SECUTIL.DLL SECUTIL.DL_ 10 12/04/1998 23:12 21468 DC32C4D7
SEMAINT.EXE SEMAINT.EX_ 9 04/12/1999 12:22 66064 BE4D0054
SESAPI.DLL SESAPI.DL_ 10 12/04/1998 18:06 24235 1E8DE76C
SESDB.DLL SESDB.DL_ 10 12/04/1998 23:11 23411 9FCC59F5
SESDMON.EXE SESDMON.EX_ 10 12/04/1998 23:15 26750 00D2EEC5
SESMGR.DLL SESMGR.DL_ 11 08/26/1998 00:51 1536 E6962291
SETBOOT.EXE SETBOOT.EX_ 10 04/12/1999 10:46 19760 AF3C692A
SETUP.EXE SETUP.EX_ 6 03/09/1999 11:12 182448 383B2DA4
FixPak Corrective Service levels and disk layouts 45
July 2, 1999 - Warp 3 FixPak XR_W041
SF.KBL SF.KB_ 11 04/09/1999 15:34 1036 EA004BF0
SHELL.DLL SHELL.DL_ 10 03/09/1999 11:39 32576 DAB197FA
SIPANEL2.DLL SIPANEL2.DL_ 10 04/12/1999 13:01 53712 9B38B8E8
SK.KBL SK.KB_ 11 04/09/1999 15:34 1008 7B5D6967
SL.KBL SL.KB_ 11 04/09/1999 15:34 982 BDBAC7E9
SLDAPI.DLL SLDAPI.DL_ 10 12/04/1998 23:11 22441 6A6BB02E
SND.CPL SND.CP_ 11 03/09/1999 12:03 8192 E04385DB
SNDBLST.DRV SNDBLST.DR_ 11 03/09/1999 11:58 13808 2C9A5351
SNDBLST2.DRV SNDBLST2.DR_ 10 03/09/1999 11:59 14464 8515E3BB
SOFTDRAW.DLL SOFTDRAW.DL_ 3 04/05/1999 14:48 401119 85E4F0CD
SOM.DLL SOM.DL_ 7 04/28/1997 18:07 92009 2CA29FCE
SOM.IR SOM.IR_ 5 03/12/1997 18:54 523185 402707DE
SOMD.DLL SOMD.DL_ 3 03/12/1997 18:54 270638 CE9F589C
SOMD.MSG SOMD.MS_ 11 03/12/1997 18:54 15056 67D977A7
SOMDD.EXE SOMDD.EX_ 10 03/12/1997 18:54 24928 3467526F
SOMDSVR.EXE SOMDSVR.EX_ 10 03/12/1997 18:54 22800 6E2FD8C2
SOMEM.DLL SOMEM.DL_ 9 03/12/1997 18:54 40132 8B338C45
SOMIR.DLL SOMIR.DL_ 6 03/12/1997 18:54 110972 56853A09
SOMK.MSG SOMK.MS_ 11 03/12/1997 18:54 3724 C7CDDC29
SOMS.DLL SOMS.DL_ 10 03/12/1997 18:54 23074 719E3284
SOMTC.DLL SOMTC.DL_ 9 03/12/1997 18:54 35768 5B67EDCB
SOMU.DLL SOMU.DL_ 7 03/12/1997 18:54 81652 DFFA1C6A
SOUND.DRV SOUND.DR_ 11 03/09/1999 10:29 3441 23A2AE74
SOUNDREC.EXE SOUNDREC.EX_ 9 03/09/1999 12:03 51305 048BD7B1
SQ.KBL SQ.KB_ 11 04/09/1999 15:34 824 4C421344
SR.KBL SR.KB_ 11 04/09/1999 15:34 1222 2995E69F
STRACE.INF STRACE.IN_ 7 01/09/1998 07:31 153828 8838BF30
SV.KBL SV.KB_ 11 04/09/1999 15:34 946 0677DA8D
SYMB.PFM SYM1.PF_ 11 06/17/1998 14:49 679 4558E0BD
SYSDUMP.EXE SYSDUMP.EX_ 9 01/09/1998 07:29 16000 FE2B4A73
SYSEDIT.EXE SYSEDIT.EX_ 8 03/09/1999 11:17 18896 1B6CA2AA
SYSINST1.EXE SYSINST1.EX_ 11 01/09/1998 06:54 4224 58970725
SYSINSTX.COM SYSINSTX.CO_ 10 04/12/1999 08:49 39472 6DFF1BF2
SYSLEVEL.EXE SYSLEVEL.EX_ 9 04/12/1999 11:49 42864 092F8F0F
SYSLEVEL.FPK SYSLEVEL.FP_ 11 05/13/1999 12:30 165 0D37B8E8
SYSLEVEL.SDS SYSLEVEL.SD_ 11 03/12/1997 18:54 265 73585845
SYSLEVEL.SEM SYSLEVEL.SE_ 11 03/12/1997 18:54 191 D0B72F4A
SYSLEVEL.SIR SYSLEVEL.SI_ 11 03/12/1997 18:54 188 A76911D0
SYSLEVEL.SRK SYSLEVEL.SR_ 11 03/12/1997 18:54 185 58859A08
SYSLEVEL.SUT SYSLEVEL.SUT 11 03/12/1997 18:54 177 A007547A
SYSLOG.DLL SYSLOG.DL_ 11 04/12/1999 12:35 5681 96E947B8
SYSLOG.EXE SYSLOG.EX_ 11 04/12/1999 12:35 7204 08188920
SYSLOGPM.EXE SYSLOGPM.EX_ 9 04/12/1999 12:36 35478 50EBAD14
SYSMONO.FON SYSMONO.FO_ 10 06/17/1998 17:03 46255 88EAB93D
SYSMONOI.FON SYSMONOI.FO_ 10 06/17/1998 17:03 46255 6803212B
SYSSPLIT.CMD SYSSPLIT.CM_ 11 01/07/1998 17:08 3712 A32F01C8
SYSTEM.DRV SYSTEM.DR_ 11 03/09/1999 11:45 2304 29EBBC72
TASKMAN.EXE TASKMAN.EX_ 11 03/09/1999 11:41 3744 960162F6
TDFLST.CMD TDFLST.CM_ 11 04/05/1999 09:56 13564 60FF3592
TEDIT.EXE TEDIT.EX_ 11 01/09/1998 04:02 9390 758DDFE2
TESTCFG.SYS TESTCFG.SY_ 11 03/22/1999 17:28 9808 AA65FDD7
FixPak Corrective Service levels and disk layouts 46
July 2, 1999 - Warp 3 FixPak XR_W041
TFFLST.CMD TFFLST.CM_ 11 04/05/1999 09:56 4638 0FFE15D0
TH.KBL TH.KB_ 11 04/09/1999 15:34 1184 1E707453
TH190.KBL TH190.KB_ 11 04/09/1999 15:34 1184 46A6A522
TIMER.DRV TIMER.DR_ 11 03/09/1999 11:57 4464 C3091288
TIMES.FON TIMES.FO_ 6 01/19/1998 13:36 257547 BD5801C9
TNR.OFM TNR.OF_ 11 02/12/1998 09:24 4882 D271B2C8
TNR.PFB TNR.PF_ 5 02/12/1998 09:24 119332 368A86F5
TNR.PFM TN1.PF_ 11 02/12/1998 09:24 1103 0CA1CE38
TNRB.OFM TNRB.OF_ 11 02/12/1998 09:24 4898 54F40409
TNRB.PFB TNRB.PF_ 5 02/12/1998 09:24 123083 AD834D17
TNRB.PFM TNR1.PF_ 11 02/12/1998 09:24 1112 6035E943
TNRBI.OFM TNRBI.OF_ 11 02/12/1998 09:24 4912 3A912F90
TNRBI.PFB TNRBI.PF_ 5 02/12/1998 09:24 134003 3B146DE1
TNRBI.PFM TNRB1.PF_ 11 02/12/1998 09:24 1118 8D8A75CB
TNRI.OFM TNRI.OF_ 11 02/12/1998 09:24 4903 80B3E811
TNRI.PFB TNRI.PF_ 5 02/12/1998 09:24 131366 2C12A764
TNRI.PFM TNR2.PF_ 11 02/12/1998 09:24 1114 126E6580
TOOLHELP.DLL TOOLHELP.DL_ 11 03/09/1999 11:03 14112 AA8CCC70
TOUCH.DRV TOUCH.DR_ 11 03/09/1999 12:59 15760 F9675CF5
TR.KBL TR.KB_ 11 04/09/1999 15:34 962 E11D8DB2
TR440.KBL TR440.KB_ 11 04/09/1999 15:34 1042 81B006FF
TRACE.DOC TRACE.DO_ 10 04/05/1999 09:56 64057 45DDD09D
TRACE.EXE TRACE.EX_ 9 04/12/1999 12:23 35168 F4BA36B6
TRACEFMT.EXE TRACEFMT.EX_ 5 04/05/1999 20:44 155698 33E6B25F
TRACEGET.EXE TRACEGET.EX_ 10 04/12/1999 12:23 22026 11274472
TRAPDUMP.EXE TRAPDUMP.EX_ 10 01/09/1998 07:30 16208 C5AD6465
TRAPLOG.EXE TRAPLOG.EX_ 10 01/09/1998 07:30 15056 5EE4C314
TRC0007.TFF TRC0007.TF_ 11 04/12/1999 11:39 1041 E77A7284
TRC00C4.TFF TRC00C4.TF_ 11 04/12/1999 11:30 289 DA465022
TRC00C6.TFF TRC00C6.TF_ 11 04/05/1999 18:03 11255 A3E26ADE
TRC0118.TFF TRC0118.TF_ 11 04/12/1999 10:31 2746 A3814141
TRC0119.TFF TRC0119.TF_ 11 04/12/1999 10:45 3786 6E141CCC
TRC012C.TFF TRC012C.TF_ 11 04/12/1999 11:12 3301 45E20225
TRC012D.TFF TRC012D.TF_ 11 04/12/1999 11:11 4739 B047B3B5
TRC012E.TFF TRC012E.TF_ 11 04/12/1999 15:57 25717 5A83D919
TRCUST.EXE TRCUST.EX_ 8 06/08/1999 11:54 99285 E7386155
TRSPOOL.DOC TRSPOOL.DO_ 11 04/05/1999 09:56 6638 7C5E9872
TRSPOOL.EXE TRSPOOL.EX_ 10 04/12/1999 12:23 27986 E0F14896
TW.KBL TW.KB_ 11 04/09/1999 15:34 780 978B2E8A
UA.KBL UA.KB_ 11 04/09/1999 15:34 1476 159E0855
UCDFS.DLL UCDFS.DL_ 11 01/08/1998 23:30 13264 8BD01F87
UCONV.DLL UCONV.DL_ 10 04/09/1999 15:32 22819 468668C3
UCSTBL.LST UCSTBL.LS_ 11 04/08/1999 16:04 1789 78EC6F42
UHPFS.DLL UHPFS.DL_ 6 04/12/1999 10:26 106000 0E4168D6
UK.KBL UK.KB_ 11 04/09/1999 15:34 816 F547878F
UK168.KBL UK168.KB_ 11 04/09/1999 15:34 850 9E48A829
ULS.REP ULS.RE_ 11 04/09/1999 15:34 19504 7FA9A41F
ULSACT01.MSG ULSACT01.MS_ 11 04/09/1999 15:34 907 D7B874D3
ULSCAU01.MSG ULSCAU01.MS_ 11 04/09/1999 15:34 899 5EAC12BC
ULSDET01.MSG ULSDET01.MS_ 1 04/09/1999 15:34 903 74D4E3DC
ULSERR01.MSG ULSERR01.MS_ 11 04/09/1999 15:34 1967 31C19CA7
FixPak Corrective Service levels and disk layouts 47
July 2, 1999 - Warp 3 FixPak XR_W041
UNICODE.SYS UNICODE.SY_ 10 04/09/1999 15:34 20014 B48E2EFA
UNIKBD.DLL UNIKBD.DL_ 10 04/09/1999 15:35 28515 F94C9516
UNPACK2.EXE UNPACK2.EX_ 8 04/12/1999 12:27 79776 1FE4BF6A
US.KBL US.KB_ 11 04/09/1999 15:34 774 416B3FF9
USDV.KBL USDV.KB_ 11 04/09/1999 15:34 942 631EADC7
USDVL.KBL USDVL.KB_ 11 04/09/1999 15:34 924 8DC2AC97
USDVR.KBL USDVR.KB_ 11 04/09/1999 15:34 942 9157A1F7
USER.EXE USER.EX_ 4 03/09/1999 11:51 280976 36556968
USINTER.KBL USINTER.KB_ 11 04/09/1999 15:34 1032 487BEDB9
VBIOS.SYS VBIOS.SY_ 11 04/12/1999 12:25 8816 353F89EB
VCDROM.SYS VCDROM.SY_ 2 04/05/1999 19:16 6864 E7D993CC
VCMOS.SYS VCMOS.SY_ 11 04/05/1999 19:37 2272 4DC719AB
VCOM.SYS VCOM.SY_ 11 04/12/1999 12:26 12384 EF0275E0
VDMA.SYS VDMAPS2.SY_ 11 04/05/1999 19:37 14329 EA71DE61
VDMA.SYS VDMAAT.SY_ 4 04/05/1999 19:37 11465 69542A6B
VDPMI.SYS VDPMI.SY_ 10 04/05/1999 19:39 22385 1082F83D
VDPX.SYS VDPX.SY_ 10 04/12/1999 12:05 25857 72101906
VDSK.SYS VDSK.SY_ 11 04/05/1999 19:39 10384 0F77511A
VER.DLL VER.DL_ 3 03/09/1999 11:02 9008 4CAA552A
VIOTBL.DCP VIOTBL.DC_ 9 04/09/1999 15:36 225355 407BA99E
VIOTBL.ISO VIOTBL.IS_ 9 04/09/1999 15:36 230105 2F2B721C
VKBD.SYS VKBD.SY_ 10 04/12/1999 12:27 25623 DB66F8B2
VLPT.SYS VLPT.SY_ 11 04/12/1999 12:29 10081 6505AC26
VMAN.DLL VMAN.DL_ 10 04/07/1999 21:39 26637 6C69F3CB
VMANWIN.SYS VMANWIN.SY_ 11 04/07/1999 17:40 3024 BCD10A9A
VW32S.SYS VW32S.SY_ 10 04/09/1999 18:46 18321 4902C6F2
VWIN.SYS VWIN.SY_ 10 04/05/1999 19:46 26896 13D2061E
WIN.COM WIN.CO_ 10 03/09/1999 11:52 44651 3501CCC4
WINFILE.EXE WINFILE.EX_ 7 03/09/1999 11:41 146960 FB8056DF
WINOS2.COM WINOS2.CO_ 11 03/09/1999 11:52 16592 347D55F5
WINSCLIP.DLL WINSCLIP.DL_ 10 03/09/1999 11:38 14848 063E0448
WINSDDE.DLL WINSDDE.DL_ 10 03/09/1999 11:38 18432 A7666F73
WINSHELD.EXE WINSHELD.EX_ 11 03/09/1999 11:38 22016 10F12B78
WINSMSG.DLL WINSMSG.DL_ 10 03/09/1999 11:37 28441 091BB9DC
WINVER.EXE WINVER.EX_ 11 03/09/1999 11:15 3904 63F2049C
WPCMPNP.DLL WPCMPNP.DL_ 7 01/09/1998 06:23 73433 305C4E06
WPCONFIG.DLL WPCONFIG.DL_ 3 08/26/1998 07:04 220139 CB6D0810
WPCONMRI.DLL WPCONMRI.DL_ 10 01/09/1998 06:42 16777 C0C8ECC4
WPHELP.HLP WPHELP.HL_ 2 04/12/1999 12:29 713080 B8BB16A2
WPPRINT.DLL WPPRINT.DL_ 3 04/12/1999 12:56 365648 1462B2DC
WPPRINT.HLP WPPRINT.HL_ 8 01/09/1998 06:13 71408 0A806DF2
WPPRTMRI.DLL WPPRTMRI.DL_ 9 01/09/1998 06:13 54486 EBE95633
WRITE.EXE WRITE.EX_ 5 03/09/1999 11:22 244976 78DE8130
WSPDBF.DRV WSPDBF.DR_ 8 03/09/1999 12:29 108512 E4DDD9D7
WSPDSBF.DRV WSPDSBF.DR_ 8 03/09/1999 12:31 109568 FB67AA91
WSPDSF.DRV WSPDSF.DR_ 8 03/09/1999 12:29 106032 75EC2817
WSPDSSF.DRV WSPDSSF.DR_ 8 03/09/1999 12:31 107088 4C5D3633
XCOPY.EXE XCOPY.EX_ 9 04/12/1999 12:29 51616 D96413CA
XDFH.MSG XDFH.MS_ 11 04/12/1999 11:47 1045 4FE75B47
************************************************************************
FixPak Corrective Service levels and disk layouts 48
July 2, 1999 - Warp 3 FixPak XR_W041
Product location on CSD: G:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
BVHVGA.DLL BVHVGA.DL_ 13 02/17/1998 15:37 31847 1B4AAB01
DF_DEB.EXE DF_DEB.EX_ 13 04/12/1999 11:16 134365 4399BA86
DF_RET.EXE DF_RET.EX_ 13 04/12/1999 11:16 134333 11A34C8A
DOSCALL1.DLL DOSCALL1.DL_ 12 04/12/1999 09:14 125358 21D28AB1
DOSCALL1.TDF DOSCALL1.TD_ 13 04/12/1999 09:14 5426 7AD85A03
DOSKRNL DOSKRNL.___ 13 04/12/1999 09:07 30509 4319A724
INSTALL.EXE INSTALL.EX_ 11 04/12/1999 10:58 302491 5D9BBABE
KERNEL.SDF KERNEL.SD_ 13 04/12/1999 11:20 55711 E96A4482
KERNELD.SDF KERNELD.SD_ 11 04/12/1999 11:21 55721 EF8EEFFC
KRNLBDEV.TDF KRNLBDEV.TD_ 13 06/08/1999 11:37 3289 CA4C17A6
KRNLBFS.TDF KRNLBFS.TD_ 13 06/08/1999 11:37 4215 91792EEB
KRNLBLDR.TDF KRNLBLDR.TD_ 13 06/08/1999 11:37 5472 0D008FDB
KRNLBPG.TDF KRNLBPG.TD_ 13 06/08/1999 11:37 3203 1194C00E
KRNLBSEL.TDF KRNLBSEL.TD_ 13 06/08/1999 11:38 2369 6AD3EBDB
KRNLBSEM.TDF KRNLBSEM.TD_ 13 06/08/1999 11:38 1353 1ED892DA
KRNLBSM.TDF KRNLBSM.TD_ 13 06/08/1999 11:37 1321 409DEE1E
KRNLBTK.TDF KRNLBTK.TD_ 13 06/08/1999 11:37 14030 95BCC0CC
KRNLBTOM.TDF KRNLBTOM.TD_ 13 06/08/1999 11:38 925 EC3500CD
KRNLBVDM.TDF KRNLBVDM.TD_ 13 06/08/1999 11:37 12485 889295BE
KRNLBVM.TDF KRNLBVM.TD_ 13 06/08/1999 11:38 5293 0D4CA0DA
KRNLDDEV.TDF KRNLDDEV.TD_ 13 06/08/1999 11:34 3289 B2F72F68
KRNLDFS.TDF KRNLDFS.TD_ 13 06/08/1999 11:34 4106 8BA119F2
KRNLDLDR.TDF KRNLDLDR.TD_ 13 06/08/1999 11:34 5500 72565726
KRNLDPG.TDF KRNLDPG.TD_ 13 06/08/1999 11:34 3284 C3907284
KRNLDSEL.TDF KRNLDSEL.TD_ 13 06/08/1999 11:35 2425 008A307F
KRNLDSEM.TDF KRNLDSEM.TD_ 13 06/08/1999 11:35 1493 5DE17907
FixPak Corrective Service levels and disk layouts 49
July 2, 1999 - Warp 3 FixPak XR_W041
KRNLDSM.TDF KRNLDSM.TD_ 13 06/08/1999 11:35 1321 9C6E9CAE
KRNLDTK.TDF KRNLDTK.TD_ 13 06/08/1999 11:34 14061 2FB06967
KRNLDTOM.TDF KRNLDTOM.TD_ 13 06/08/1999 11:35 953 FB25B24C
KRNLDVDM.TDF KRNLDVDM.TD_ 13 06/08/1999 11:34 12560 F63F6DCC
KRNLDVM.TDF KRNLDVM.TD_ 13 06/08/1999 11:35 5380 E4FF6F7F
KRNLRDEV.TDF KRNLRDEV.TD_ 13 06/08/1999 11:30 3289 6BA68F01
KRNLRFS.TDF KRNLRFS.TD_ 13 06/08/1999 11:30 4215 4738E182
KRNLRLDR.TDF KRNLRLDR.TD_ 13 06/08/1999 11:31 5472 C720EAFB
KRNLRPG.TDF KRNLRPG.TD_ 13 06/08/1999 11:31 3203 29B781A8
KRNLRSEL.TDF KRNLRSEL.TD_ 13 06/08/1999 11:31 2369 9BB604B7
KRNLRSEM.TDF KRNLRSEM.TD_ 13 06/08/1999 11:31 1353 8DF34DE5
KRNLRSM.TDF KRNLRSM.TD_ 13 06/08/1999 11:31 1321 0B5AD6C7
KRNLRTK.TDF KRNLRTK.TD_ 13 06/08/1999 11:31 13946 7FAE2D45
KRNLRTOM.TDF KRNLRTOM.TD_ 13 06/08/1999 11:31 897 15392159
KRNLRVDM.TDF KRNLRVDM.TD_ 13 06/08/1999 11:31 12317 49B73A3C
KRNLRVM.TDF KRNLRVM.TD_ 13 06/08/1999 11:31 5293 D43EB324
MONCALLS.TDF MONCALLS.TD_ 13 08/25/1998 20:47 1139 AF72F54A
OS2CHAR.TDF OS2CHAR.TD_ 13 04/12/1999 09:13 13889 09E319B9
OS2KRNL OS2KRNL.___ 11 06/08/1999 11:32 633444 65B62261
OS2KRNL.TDF OS2KRNL.TD_ 13 06/08/1999 11:30 16609 24EB25EA
OS2KRNLB.TDF OS2KRNLB.TD_ 13 06/08/1999 11:37 16609 DD4AF224
OS2KRNLD.TDF OS2KRNLD.TD_ 13 06/08/1999 11:34 16609 19A804DB
OS2LDR OS2LDR.___ 13 04/13/1999 08:19 33280 C9348A1D
PMDF.EXE PMDF.EX_ 13 04/12/1999 11:20 260108 DC6ECB0E
PMDFINST.CMD PMDFINST.CM_ 13 01/07/1998 17:10 18501 61C6F57D
PMGPI.TDF PMGPI.TD_ 13 04/05/1999 15:12 12338 E42CB7B1
PMGRE.TDF PMGRE.TD_ 13 04/19/1999 17:50 1062 73FD936B
PMMERGE.DLL PMMERGE.DL_ 12 04/19/1999 17:50 1321030 ECD486BB
PMSHAPI.TDF PMSHAPI.TD_ 13 04/19/1999 17:50 6751 F1357551
PMWIN.TDF PMWIN.TD_ 13 04/19/1999 17:50 13570 E15AC24D
PMWIN32.SDF PMWIN32.SD_ 13 04/12/1999 11:21 33419 96C72F35
QUECALLS.TDF QUECALLS.TD_ 13 04/12/1999 09:13 1319 E4A5FB9E
RSPINST.EXE RSPINST.EX_ 12 04/12/1999 11:08 289706 E6AA5C36
RUPINST2.EXE RUPINST2.EX_ 13 04/12/1999 11:03 173120 F3E0BCB5
SESDD32.SYS SESDD32.SY_ 13 04/12/1999 10:46 118833 C89E9FE2
SESMGR.TDF SESMGR.TD_ 13 04/12/1999 09:13 1877 BE645E40
SHELL.SDF SHELL.SD_ 13 04/12/1999 11:21 20425 50A17CB7
SOMCT.DLL SOMCT.DL_ 13 04/28/1997 18:06 42841 A706E813
SOMSEC.DLL SOMSEC.DL_ 13 04/28/1997 18:06 33214 2E34710F
SOMUC.DLL SOMUC.DL_ 13 04/28/1997 18:06 86276 C74B46D0
STRACE.EXE STRACE.EX_ 13 04/12/1999 11:22 41010 FD1585F5
SYSINST2.EXE SYSINST2.EX_ 13 04/12/1999 11:02 171808 E7C0AD2A
SYSLEVEL.SCT SYSLEVEL.SC_ 13 06/16/1998 17:42 187 9FAEACA3
SYSLEVEL.SUC SYSLEVEL.SUC 13 06/16/1998 17:42 191 665CE147
TRACE.HLP TRACE.HL_ 12 04/05/1999 18:12 29376 DF182054
TRACEFMT.ICO TRACEFMT.IC_ 13 03/12/1997 17:08 2692 510F1BCA
TRC0000.TFF TRC0000.TF_ 13 01/25/1999 10:24 189 FEDB2564
TRC0003.TFF TRC0003.TF_ 13 01/25/1999 10:24 1503 0B35868D
TRC0004.TFF TRC0004.TF_ 13 01/25/1999 10:25 4754 E78D826B
TRC0005.TFF TRC0005.TF_ 13 06/08/1999 11:37 38800 6EA34BE9
TRC0006.TFF TRC0006.TF_ 13 01/25/1999 09:53 12356 8E28674E
FixPak Corrective Service levels and disk layouts 50
July 2, 1999 - Warp 3 FixPak XR_W041
TRC0010.TFF TRC0010.TF_ 11 04/12/1999 09:14 13359 60B7A17F
TRC0016.TFF TRC0016.TF_ 13 04/12/1999 09:13 1719 B7E34E1F
TRC0017.TFF TRC0017.TF_ 13 04/12/1999 09:13 5561 3EB3BD51
TRC0018.TFF TRC0018.TF_ 13 04/12/1999 09:13 39488 1F261364
TRC00C0.TFF TRC00C0.TF_ 13 04/19/1999 17:50 16022 202F5453
TRC00C2.TFF TRC00C2.TF_ 13 04/19/1999 17:50 34340 FC688B85
TRC00C3.TFF TRC00C3.TF_ 13 04/19/1999 17:50 3984 2BEF4AA4
TRC00C5.TFF TRC00C5.TF_ 13 04/05/1999 15:12 32994 870502D8
TRC0100.TFF TRC0100.TF_ 13 06/08/1999 11:37 5409 60461DC3
TRC0101.TFF TRC0101.TF_ 13 06/08/1999 11:37 6954 700660DE
TRC0102.TFF TRC0102.TF_ 13 06/08/1999 11:37 23155 3461468B
TRC0103.TFF TRC0103.TF_ 13 06/08/1999 11:37 9828 DD759879
TRC0104.TFF TRC0104.TF_ 13 06/08/1999 11:37 5135 C64030E0
TRC0105.TFF TRC0105.TF_ 13 06/08/1999 11:37 27425 1885BE53
TRC0106.TFF TRC0106.TF_ 13 06/08/1999 11:37 1835 E1FAB2F7
TRC0107.TFF TRC0107.TF_ 12 06/08/1999 11:38 3732 2F07A4B4
TRC0108.TFF TRC0108.TF_ 13 06/08/1999 11:38 9082 4BC7F052
TRC0109.TFF TRC0109.TF_ 13 06/08/1999 11:38 1713 3840CCCD
TRC010A.TFF TRC010A.TF_ 13 06/08/1999 11:38 1029 FDEBAF1A
TRCFORMT.DLL TRCFORMT.DL_ 13 10/14/1998 20:27 26630 1C6843BB
VMOUSE.SYS VMOUSE.SY_ 13 04/05/1999 16:02 17280 95E1E35F
VPIC.SYS VPIC.SY_ 13 04/05/1999 16:03 9942 15874B9A
VPICPARM.SYS VPICPARM.SY_ 13 04/05/1999 16:03 736 76AC548D
VTIMER.SYS VTIMER.SY_ 13 04/05/1999 16:03 9936 3627CE77
VXGA.SYS VXGA.SY_ 13 02/17/1998 15:37 24771 07279733
************************************************************************
Product location on CSD: G:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.02
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_3006_
System Id: 1000
Component Id: 5639A5500
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size Checksum
FixPak Corrective Service levels and disk layouts 51
July 2, 1999 - Warp 3 FixPak XR_W041
------------ ------------ ----- ---------- ----- ------- --------
ALR.PSD ALR.PS_ 16 05/20/1999 15:30 18432 29F17AF0
CAVERUN.PSD CAVERUN.PS_ 16 05/20/1999 15:31 29184 8F3B0630
DF_DEB.EXE DF_DEB.EX_ 15 04/12/1999 13:24 142741 F1F5CEC1
DF_RET.EXE DF_RET.EX_ 13 04/12/1999 13:24 142709 E318D218
DOSCALL1.DLL DOSCALL1.DL_ 15 04/12/1999 10:55 137862 AC7FCD55
DOSCALL1.SYM DOSCALL1.SY_ 16 04/12/1999 10:55 42660 3F007A3D
DOSCALL1.TDF DOSCALL1.TD_ 16 04/12/1999 10:55 5534 923F3439
DOSKRNL DOSKRNL.___ 16 05/20/1999 16:15 30525 22833691
INSTALL.EXE INSTALL.EX_ 13 04/12/1999 13:07 304771 EFD24B01
KERNEL.SDF KERNEL.SD_ 16 04/12/1999 13:27 57011 F1AC0627
KERNELD.SDF KERNELD.SD_ 16 04/12/1999 13:27 57136 FAD367FC
KRNLBDEV.TDF KRNLBDEV.TD_ 16 06/30/1999 15:01 4282 A8D50ABE
KRNLBFS.TDF KRNLBFS.TD_ 16 06/30/1999 15:01 4542 BE305D78
KRNLBLDR.TDF KRNLBLDR.TD_ 16 06/30/1999 15:01 5609 7785C294
KRNLBPG.TDF KRNLBPG.TD_ 16 06/30/1999 15:01 3427 8C2AF53E
KRNLBSEL.TDF KRNLBSEL.TD_ 16 06/30/1999 15:02 2833 6B039589
KRNLBSEM.TDF KRNLBSEM.TD_ 16 06/30/1999 15:02 1764 A6C2E520
KRNLBSM.TDF KRNLBSM.TD_ 16 06/30/1999 15:01 1321 E333ECD8
KRNLBTK.TDF KRNLBTK.TD_ 16 06/30/1999 15:01 15826 221AAA9F
KRNLBTOM.TDF KRNLBTOM.TD_ 16 06/30/1999 15:02 1009 AC8E3D7B
KRNLBVDM.TDF KRNLBVDM.TD_ 16 06/30/1999 15:01 13976 525B14DB
KRNLBVM.TDF KRNLBVM.TD_ 16 06/30/1999 15:02 5542 4B7E8CF6
KRNLDDEV.TDF KRNLDDEV.TD_ 16 06/30/1999 14:55 4232 F12D0A86
KRNLDFS.TDF KRNLDFS.TD_ 16 06/30/1999 14:54 4433 0448AE96
KRNLDLDR.TDF KRNLDLDR.TD_ 16 06/30/1999 14:55 5637 BA5E7A3E
KRNLDPG.TDF KRNLDPG.TD_ 16 06/30/1999 14:55 3508 23F2BFBC
KRNLDSEL.TDF KRNLDSEL.TD_ 16 06/30/1999 14:55 2895 9A7E0F0B
KRNLDSEM.TDF KRNLDSEM.TD_ 16 06/30/1999 14:55 1932 A77707C2
KRNLDSM.TDF KRNLDSM.TD_ 16 06/30/1999 14:55 1321 ECD4D789
KRNLDTK.TDF KRNLDTK.TD_ 16 06/30/1999 14:55 15882 095C12C2
KRNLDTOM.TDF KRNLDTOM.TD_ 16 06/30/1999 14:56 1037 10B35199
KRNLDVDM.TDF KRNLDVDM.TD_ 16 06/30/1999 14:55 14026 2664CF5B
KRNLDVM.TDF KRNLDVM.TD_ 16 06/30/1999 14:55 5629 51839CE8
KRNLRDEV.TDF KRNLRDEV.TD_ 16 06/30/1999 14:58 4282 008C8AA4
KRNLRFS.TDF KRNLRFS.TD_ 16 06/30/1999 14:58 4542 C76D5AD1
KRNLRLDR.TDF KRNLRLDR.TD_ 16 06/30/1999 14:58 5609 0D8F5740
KRNLRPG.TDF KRNLRPG.TD_ 16 06/30/1999 14:58 3427 482DF88E
KRNLRSEL.TDF KRNLRSEL.TD_ 16 06/30/1999 14:58 2808 C8862509
KRNLRSEM.TDF KRNLRSEM.TD_ 16 06/30/1999 14:59 1764 659BC353
KRNLRSM.TDF KRNLRSM.TD_ 16 06/30/1999 14:58 1321 6BD3CBBE
KRNLRTK.TDF KRNLRTK.TD_ 16 06/30/1999 14:58 15742 C2240B2B
KRNLRTOM.TDF KRNLRTOM.TD_ 16 06/30/1999 14:59 981 8B2EAD4D
KRNLRVDM.TDF KRNLRVDM.TD_ 16 06/30/1999 14:58 13808 444D94B6
KRNLRVM.TDF KRNLRVM.TD_ 16 06/30/1999 14:58 5542 CB0B1125
MONCALLS.TDF MONCALLS.TD_ 16 08/26/1998 01:30 1139 AF5DB94A
OS2APIC.PSD OS2APIC.PS_ 16 05/20/1999 15:32 28160 7241D045
OS2CHAR.TDF OS2CHAR.TD_ 16 04/12/1999 10:55 13889 8BC27E0A
OS2KRNL OS2KRNL.___ 15 06/30/1999 14:59 728630 7EA8C632
OS2KRNL.TDF OS2KRNL.TD_ 16 06/30/1999 14:57 16837 7E44F25A
OS2KRNLB.SYM OS2KRNLB.SY_ 15 06/30/1999 15:00 192148 2E727273
FixPak Corrective Service levels and disk layouts 52
July 2, 1999 - Warp 3 FixPak XR_W041
OS2KRNLB.TDF OS2KRNLB.TD_ 16 06/30/1999 15:01 16837 2FE1C815
OS2KRNLD.SYM OS2KRNLD.SY_ 14 06/30/1999 14:54 195188 8AF856FC
OS2KRNLD.TDF OS2KRNLD.TD_ 16 06/30/1999 14:54 16867 E4C74FA7
OS2KRNLR.SYM OS2KRNLR.SY_ 15 06/30/1999 14:57 172308 3B2989EF
OS2LDR OS2LDR.___ 16 04/12/1999 08:47 35000 3A154201
PMCTLS.SYM PMCTLS.SY_ 16 04/12/1999 08:58 43508 04DFBC59
PMDD.SYM PMDD.SY_ 16 04/05/1999 19:18 2740 38F09CBF
PMDDE.SYM PMDDE.SY_ 16 04/12/1999 12:39 2500 15CA98DC
PMDF.EXE PMDF.EX_ 15 04/12/1999 13:27 260112 59B5B70B
PMDRAG.SYM PMDRAG.SY_ 16 04/12/1999 08:57 36 FC6E0F35
PMGPI.SYM PMGPI.SY_ 16 04/05/1999 15:11 45604 732DE052
PMGPI.TDF PMGPI.TD_ 16 04/05/1999 15:11 12338 242CB7A2
PMGRE.TDF PMGRE.TD_ 16 04/19/1999 18:04 1062 A8F40852
PMMERGE.DLL PMMERGE.DL_ 14 04/19/1999 18:05 1325198 76FDDB93
PMMERGE.SYM PMMERGE.SY_ 16 04/19/1999 18:04 92212 512E62A8
PMMLE.SYM PMMLE.SY_ 16 12/04/1998 18:40 36 CC1F5E9D
PMPIC.SYM PMPIC.SY_ 16 04/12/1999 11:30 8436 C698A71A
PMPRINT.SYM PMPRINT.SY_ 16 04/12/1999 11:01 1636 1A1ECD04
PMSHAPI.TDF PMSHAPI.TD_ 16 04/19/1999 18:04 6751 23AB18D5
PMSHELL.SYM PMSHELL.SY_ 16 04/12/1999 15:40 500 BDCB0018
PMSPL.SYM PMSPL.SY_ 16 04/05/1999 18:03 32372 7ED05605
PMSPOOL.SYM PMSPOOL.SY_ 16 10/14/1998 20:19 404 CCAB842C
PMVDMP.SYM PMVDMP.SY_ 16 04/12/1999 11:12 5268 22460386
PMVIOP.SYM PMVIOP.SY_ 16 04/12/1999 11:11 6404 288023A5
PMWIN.TDF PMWIN.TD_ 16 04/19/1999 18:04 13570 35353ECC
PMWIN32.SDF PMWIN32.SD_ 16 04/12/1999 13:28 33419 16C72313
PMWP.SYM PMWP.SY_ 16 04/12/1999 15:57 95972 C450F15E
PROLIANT.PSD PROLIANT.PS_ 16 05/20/1999 15:32 18944 96A85EE4
QUECALLS.TDF QUECALLS.TD_ 16 04/12/1999 10:55 1319 832D8629
RSPDDI.EXE RSPDDI.EX_ 16 04/12/1999 12:00 22073 0893A600
RSPINST.EXE RSPINST.EX_ 14 04/12/1999 13:17 290681 EB8A88E4
RUPINST2.EXE RUPINST2.EX_ 15 04/12/1999 13:11 172096 9E0215BD
SESDD32.SYS SESDD32.SY_ 16 04/12/1999 12:46 118833 6ADC8185
SESMGR.TDF SESMGR.TD_ 16 04/12/1999 10:55 1877 6B2B6434
SHELL.SDF SHELL.SD_ 16 04/12/1999 13:28 20425 4FBE7CB7
STRACE.EXE STRACE.EX_ 16 04/12/1999 13:29 41010 000C85F6
SYSINST2.EXE SYSINST2.EX_ 15 04/12/1999 13:11 170784 048EEAB5
SYSLOGPM.EXE SYSLOGPM.EX_ 16 04/12/1999 12:36 35478 50BD2D14
TRACE.HLP TRACE.HL_ 16 04/05/1999 20:44 29376 DFB82054
TRC0000.TFF TRC0000.TF_ 16 08/11/1998 19:53 189 CEDB268C
TRC0003.TFF TRC0003.TF_ 16 08/11/1998 19:53 1503 B3358691
TRC0004.TFF TRC0004.TF_ 16 08/11/1998 19:53 4754 6C8D826C
TRC0005.TFF TRC0005.TF_ 16 06/30/1999 15:01 39307 015F5D9A
TRC0006.TFF TRC0006.TF_ 16 08/11/1998 18:51 12356 AF80674E
TRC0010.TFF TRC0010.TF_ 14 04/12/1999 10:55 13647 C63F283D
TRC0016.TFF TRC0016.TF_ 16 04/12/1999 10:55 1719 7FE34E77
TRC0017.TFF TRC0017.TF_ 16 04/12/1999 10:55 5561 3EB3BDAB
TRC0018.TFF TRC0018.TF_ 16 04/12/1999 10:55 39488 BF261369
TRC00C0.TFF TRC00C0.TF_ 16 04/19/1999 18:04 16022 2037B513
TRC00C2.TFF TRC00C2.TF_ 15 04/19/1999 18:04 34340 06708B87
TRC00C3.TFF TRC00C3.TF_ 16 04/19/1999 18:04 3984 BEEF4AB4
FixPak Corrective Service levels and disk layouts 53
July 2, 1999 - Warp 3 FixPak XR_W041
TRC00C5.TFF TRC00C5.TF_ 16 04/05/1999 15:11 32994 870102D8
TRC0100.TFF TRC0100.TF_ 16 06/30/1999 15:01 7336 4F1BFB35
TRC0101.TFF TRC0101.TF_ 13 06/30/1999 15:01 7572 9862395B
TRC0102.TFF TRC0102.TF_ 16 06/30/1999 15:01 25989 EE4C4854
TRC0103.TFF TRC0103.TF_ 16 06/30/1999 15:01 10111 196CAA70
TRC0104.TFF TRC0104.TF_ 16 06/30/1999 15:01 5574 6BC99731
TRC0105.TFF TRC0105.TF_ 16 06/30/1999 15:01 31139 CE5FCB44
TRC0106.TFF TRC0106.TF_ 16 06/30/1999 15:01 1835 B1FAB1E8
TRC0107.TFF TRC0107.TF_ 16 06/30/1999 15:02 4632 AC35A3A7
TRC0108.TFF TRC0108.TF_ 16 06/30/1999 15:02 9505 A2F6DF13
TRC0109.TFF TRC0109.TF_ 16 06/30/1999 15:02 2483 7C05B7CF
TRC010A.TFF TRC010A.TF_ 15 06/30/1999 15:02 1175 66E5941E
TRCFORMT.DLL TRCFORMT.DL_ 16 10/14/1998 22:11 26630 1C8505BB
TRICRD.PSD TRICRD.PS_ 16 05/20/1999 15:33 4608 56022291
V1_EBI2.PSD V1_EBI2.PS_ 16 05/20/1999 15:32 19456 0B710E76
VIPERMP.PSD VIPERMP.PS_ 16 05/20/1999 15:33 6656 66D5B2A8
VMOUSE.SYS VMOUSE.SY_ 16 04/05/1999 19:40 17280 16AA8A4C
VPIC.SYS VPIC.SY_ 16 04/05/1999 19:40 9942 ADC6DBD2
VPICPARM.SYS VPICPARM.SY_ 16 04/05/1999 19:40 736 C3AC5479
VTIMER.SYS VTIMER.SY_ 16 04/05/1999 19:41 10576 E8DD634D
WYSE.PSD WYSE.PS_ 16 05/20/1999 15:33 3072 AF5D7906
************************************************************************
Product location on CSD: G:\FIX\MPM.4
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.01
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
________________________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 1.01.2
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_6200_
System Id: B020
Component Id: 562137400
Archive is ON for this product.
________________________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.02
New CSD Level: XR_W041_ (Country = Generic)
Pre-requisite CSD Level: XR_3006_
System Id: 1000
Component Id: 5639A5500
Archive is ON for this product.
________________________________________________________________________
Default directories:
FixPak Corrective Service levels and disk layouts 54
July 2, 1999 - Warp 3 FixPak XR_W041
..\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
AMPMXMCD.DLL AMPMXMCD.DL_ 17 12/07/1998 09:43 544 B6A2596D
AUDIOIF.DLL AUDIOIF.DL_ 17 12/07/1998 09:53 544 78F89813
AUDIOMCD.DLL AUDIOMCD.DL_ 17 12/07/1998 09:51 544 3C92541E
AUDIOSH.DLL AUDIOSH.DL_ 17 12/07/1998 09:38 532 F7D87B94
AUTOPROC.DLL AUTOPROC.DL_ 17 12/07/1998 10:08 17936 DF47B61C
AVIO.DLL AVIO.DL_ 17 12/07/1998 09:41 532 20C4245A
BUSAUDIO.SYS BUSAUDIO.SY_ 17 12/07/1998 09:35 28399 4A2968E5
CARDINFO.DLL CARDINFO.DL_ 17 12/07/1998 10:01 10768 C42FF25C
CS4231.SYS CS4231.SY_ 17 10/08/1996 00:36 35319 ACF3AC36
DIVE.DLL DIVE.DL_ 17 12/07/1998 09:26 69840 933863D6
ES688DD.SYS ES688DD.SY_ 17 10/19/1998 10:40 44958 EE1C9539
IOPRNLS.DLL IOPRNLS.DL_ 17 12/07/1998 09:25 3088 CEA8662B
MDM.DLL MDM.DL_ 17 12/07/1998 09:28 26036 51D2A6A7
MEMSH.DLL MEMSH.DL_ 17 12/07/1998 09:32 14144 055A0EDD
MMPM.DLL MMPM.DL_ 16 12/07/1998 10:11 723448 CF6A2C1A
MPGDC.DLL MPGDC.DL_ 17 12/07/1998 09:36 8912 5C89F5B5
MPGDCS.DLL MPGDCS.DL_ 17 12/07/1998 09:36 8768 7BCEC092
MPGIO.DLL MPGIO.DL_ 17 12/07/1998 09:37 59327 47A7FE5D
MPGIOS.DLL MPGIOS.DL_ 16 12/07/1998 09:37 63067 908AAB80
MPGIOS.SCR MPGIOS.SC_ 17 10/08/1996 01:14 1053 A395762D
MVPRODD.SYS MVPRODD.SY_ 17 11/21/1997 14:27 52074 565D5957
R0STUB.SYS R0STUB.SY_ 17 12/07/1998 09:38 8398 C4F35C7F
R565LUT8.LUT R565LUT8.LU_ 17 07/11/1996 18:10 263168 22447327
RMAUDIO.SYS RMAUDIO.SY_ 17 04/01/1999 15:41 26273 F4D49071
SB16D2.SYS SB16D2.SY_ 17 12/07/1998 09:30 62378 7699BF50
SBAWED2.SYS SBAWED2.SY_ 17 11/27/1995 10:18 88490 77FA4293
SMVSMRI.DLL SMVSMRI.DL_ 17 12/07/1998 10:07 5648 DE6F8457
SMVSPAGE.DLL SMVSPAGE.DL_ 17 12/07/1998 10:06 81440 7F50367E
SSM.DLL SSM.DL_ 17 12/07/1998 09:25 1044 C69C1347
SSMDD.SYS SSMDD.SY_ 17 12/07/1998 09:25 33484 5BBB6079
SSMPEG.DLL SSMPEG.DL_ 17 12/07/1998 09:36 30160 793A067F
SSMRES.DLL SSMRES.DL_ 17 12/07/1998 09:25 22364 F280FCD5
SVMC.DLL SVMC.DL_ 17 12/07/1998 09:40 532 730150CF
SVSH.DLL SVSH.DL_ 17 12/07/1998 09:42 23044 9B2235A4
SWVR.EXE SWVR.EX_ 17 12/07/1998 10:09 152326 89AACD23
VIDVCI.DLL VIDVCI.DL_ 17 10/19/1998 10:46 34864 41C8C682
WAVEPROC.DLL WAVEPROC.DL_ 17 12/07/1998 10:06 532 3FA082C0
Y644LUT8.LUT Y644LUT8.LU_ 17 07/11/1996 18:10 66560 88251A02
YUV_LUT8.LUT YUV_LUT8.LU_ 17 07/11/1996 18:10 263168 9C29B8C2
************************************************************************
Product location on CSD: G:\FIX\OS2.5
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
New CSD Level: XR_W041_ (Country = Generic)
FixPak Corrective Service levels and disk layouts 55
July 2, 1999 - Warp 3 FixPak XR_W041
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\*
..\..\LANGUAGE\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
FFST.DLL FFST.DL_ 18 09/05/1997 11:31 23583 8CDD7AE4
IBMDAPIN.EXE IBMDAPIN.EX_ 18 10/25/1996 12:49 66248 28C8A148
IBMDAPPM.EXE IBMDAPPM.EX_ 18 10/25/1996 12:49 51190 86BEEB6A
INST_DOS.EXE INST_DOS.EX_ 18 12/04/1998 20:35 36506 A5D85B5D
LIBAUX.DLL LIBAUX.DL_ 18 09/05/1997 11:30 113848 B55CBE3C
LIBTK.DLL LIBTK.DL_ 17 09/05/1997 11:30 1101576 DDE3379A
NAMEADD.EXE NAMEADD.EX_ 18 04/09/1999 16:34 20045 E3D220F5
NAMECOPY.EXE NAMECOPY.EX_ 18 04/09/1999 16:34 20045 D9364C75
NAMECSSP.DLL NAMECSSP.DL_ 18 01/21/1998 16:36 61155 ED25B521
NAMEDEL.EXE NAMEDEL.EX_ 18 04/09/1999 16:34 20045 33567977
NAMEDSP.DLL NAMEDSP.DL_ 17 04/09/1999 16:29 123411 9539D534
NAMEDUMP.EXE NAMEDUMP.EX_ 18 04/09/1999 16:34 20045 C16520EA
NAMEEXT.EXE NAMEEXT.EX_ 18 04/09/1999 16:34 20045 F1CE14CD
NAMEFT.DLL NAMEFT.DL_ 18 01/21/1998 16:49 66306 05DC15F6
NAMEFW.DLL NAMEFW.DL_ 18 04/05/1999 12:01 72312 E73E3ECD
NAMEINFO.DLL NAMEINFO.DL_ 18 04/09/1999 16:33 47925 C7A84CD1
NAMEINI.DLL NAMEINI.DL_ 18 04/09/1999 16:33 59011 B9A9793E
NAMEMOD.EXE NAMEMOD.EX_ 18 04/09/1999 16:34 20045 DF494D7D
NAMEMOVE.EXE NAMEMOVE.EX_ 18 04/09/1999 16:34 20045 3F809C79
NAMEOSP.DLL NAMEOSP.DL_ 18 04/09/1999 16:33 52709 6401BF8B
NAMEREXX.DLL NAMEREXX.DL_ 17 04/09/1999 16:34 156291 1D122E94
NAMEREXX.MSG NAMEREXX.MS_ 17 01/21/1998 16:47 4257 D09A395D
OS2NS.EXE OS2NS.EX_ 18 04/09/1999 16:33 44964 164A5D57
PMDDEML.DLL PMDDEML.DL_ 18 12/04/1998 19:11 27210 3FE6DA5F
PMWINX.DLL PMWINX.DL_ 17 12/04/1998 20:35 520559 1E814192
RSRV.EXE RSRV.EX_ 18 04/09/1999 16:30 77955 6F11D617
FixPak Corrective Service levels and disk layouts 56
July 2, 1999 - Warp 3 FixPak XR_W041
12.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 32MB FixPak Archive/Backup for product with CSD level of
XR_3005
Up to 33MB FixPak Archive/Backup for product with CSD level of
XR_3006
Up to 3MB FixPak Archive/Backup for product with CSD level of
XR_6200
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.
Space Utilization 57
July 2, 1999 - Warp 3 FixPak XR_W041
13.0 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.
Recovering FixPak ARCHIVE and BACKUP space 58
July 2, 1999 - Warp 3 FixPak XR_W041
14.0 RECOVERING FROM PROBLEMS
See the file "README.TIP" for information on recovering from FixPak
installation problems and resolving problems after the FixPak is
installed. It is located on the first FixPak disk which is:
FixPak XR_W041 Corrective Service Diskette 1 (CSF DISK 1).
This file is setup to print at 60 lines per page.
Recovering from problems 59