home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 28 Fixes4x
/
28-Fixes4x.zip
/
xr_m009.rm1
< prev
next >
Wrap
Text File
|
1998-11-14
|
115KB
|
3,191 lines
< Installation instructions for Warp 4 FixPak XR_M009
November 10, 1998
This FixPak makes the products it services Year 2000 ready
Build level 9.033
Release 2
This FixPak applies to:
CSD Level: XR_4000 Warp 4
Component ID: 5639A6100
Version: 4.00
Type: 0C
CSD Level: XR_4010 WorkSpace On Demand
Component ID: 5639A6100
Version: 4.00
Type: 0C
Requires Corrective Service Facility release F.139 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
November 10, 1998 - Warp 4 FixPak XR_M009
November 10, 1998 - Warp 4 FixPak XR_M009
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Second Release notice . . . . . . . . . . . . . . . . . . . . . 3
3.0.1 PMWP.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.0.2 CLOCK01.SYS . . . . . . . . . . . . . . . . . . . . . . . . 4
4.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 5
4.0.1 System Sounds not working after FixPak applied . . . . . . . 5
4.0.2 IBM1S506.ADD driver removed from FixPak . . . . . . . . . . 6
4.0.3 AIC7870.ADD driver removed from FixPak . . . . . . . . . . . 6
4.0.4 Using Display Recovery Choices . . . . . . . . . . . . . . . 6
4.0.5 Installation of Java 1.1.4 . . . . . . . . . . . . . . . . . 7
4.0.6 DSPRES.DLL included in this FixPak . . . . . . . . . . . . . 7
4.0.7 No products were found . . . . . . . . . . . . . . . . . . . 7
4.0.8 Previous installation interrupted . . . . . . . . . . . . . 8
4.0.9 Unable to open Archive directory . . . . . . . . . . . . . . 8
4.0.10 RC 932 doing CID install of Warp 4 . . . . . . . . . . . . 8
4.0.11 Multimedia no longer selectable . . . . . . . . . . . . . 10
4.0.12 MMPARTS.DLL/USER.EXE popup during install . . . . . . . . 10
4.0.13 CSF0208 No products were found . . . . . . . . . . . . . . 10
4.0.14 CSF0248 Archive path is shared between mismatched . . . . 10
4.0.15 CSF0249 Error opening or creating archive file. . . . . . 10
4.0.16 Printer installation process change . . . . . . . . . . . 11
4.0.17 Configuration Installation Distribution ( CID ) . . . . . 11
5.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 12
5.0.1 Setting IRQ9 processing in config.sys for VPIC.SYS . . . . 12
5.0.2 Windows printer drivers leave a zombie thread running . . . 12
5.0.3 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . . . . 13
5.0.4 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . . . 13
5.0.5 Intermittent hangs . . . . . . . . . . . . . . . . . . . . 13
5.0.6 Intermittent pause with IBM Thinkpad 760E/ED/ELD/EL . . . . 13
5.0.7 APM users . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 Querying file dates for files after Dec 31, 1999 in REXX . . . 15
6.2 Enhanced support for Workspace On-Demand . . . . . . . . . . . 16
6.2.1 PMLOGON user exits . . . . . . . . . . . . . . . . . . . . 16
6.2.2 Setup strings for public applications . . . . . . . . . . . 18
6.2.3 Command line options for TLOGOFF and TSHUTDWN . . . . . . . 19
6.2.4 PMLOGON No Progress Indicator option . . . . . . . . . . . 19
6.2.5 PMLOGON No System Modal Window option . . . . . . . . . . . 20
6.3 Fixed IDE Hard Drive and Removable Media Support . . . . . . . 20
6.4 Euro Support . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.4.1 Base OS/2 support . . . . . . . . . . . . . . . . . . . . . 20
6.4.2 Where euro is not supported . . . . . . . . . . . . . . . . 22
Contents ii
November 10, 1998 - Warp 4 FixPak XR_M009
6.4.3 Printing the euro . . . . . . . . . . . . . . . . . . . . . 23
6.5 New Warp Registry Editor . . . . . . . . . . . . . . . . . . . 23
6.6 WorkSpace On Demand . . . . . . . . . . . . . . . . . . . . . . 23
6.7 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.8 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 23
6.9 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . . . . 24
6.9.1 Using the new CHKDSK . . . . . . . . . . . . . . . . . . . 24
6.9.2 CHKDSK log formatter . . . . . . . . . . . . . . . . . . . 26
6.10 Automated Trap Screen Logging . . . . . . . . . . . . . . . . 26
6.10.1 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . . . . 27
6.10.2 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.10.3 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.10.4 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.11 Other README files . . . . . . . . . . . . . . . . . . . . . . 28
7.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 30
7.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 30
7.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 30
7.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 31
7.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . . . . 31
7.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 32
7.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 32
7.4 Relocated OS/2 file support . . . . . . . . . . . . . . . . . . 33
8.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 35
8.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 35
8.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 35
8.3 Method 2: Install from alternate bootable media . . . . . . . . 36
8.4 Additional Corrective Service Facility information . . . . . . 37
8.5 FixPaks on CD-ROM . . . . . . . . . . . . . . . . . . . . . . . 37
9.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 38
9.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . . . . 39
10.0 FixPak Corrective Service levels and disk layouts . . . . . . 40
11.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 52
11.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 52
11.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 53
Contents iii
November 10, 1998 - Warp 4 FixPak XR_M009
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_M009 for OS/2 Warp 4
indicates your acceptance of the following terms and conditions:
1. You must be, and agree that you are, a current licensee of OS/2 Warp
4.
2. You may make copies of the OS/2 Service Fixes equal to the number of
licensed copies of OS/2 Warp 4 you possess.
3. You may only use the OS/2 Warp 4 Service Fixes included with FixPak
XR_M009 for maintenance purposes.
4. All other terms and conditions of your OS/2 Warp 4 license agreements
apply to the Service Fixes; however, this does not extend any warranty
and/or services, including but not limited to the "Initial
Installation" period, outlined in such agreements.
Terms and Conditions 1
November 10, 1998 - Warp 4 FixPak XR_M009
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
November 10, 1998 - Warp 4 FixPak XR_M009
3.0 SECOND RELEASE NOTICE
This is the second release of Fixpak XR_M009.
3.0.1 PMWP.DLL
The initial release was withdrawn due to a problem found in PMWP.DLL that
could cause the Workplace Shell to hang.
To resolve the problem we have placed the Fixpak 8 level of PMWP.DLL in
Fixpak 9.
This means the following APARs are no longer fixed in Fixpak 9 and will
be fixed in Fixpak 10 or later.
APAR= JR12483
OS2.INI FILE GROWS LARGE IN SIZE AND CONTAIN INVALID ENTRIES.
SYSTEM TRAPS WITH SYS3175.
APAR= JR11852
SYSTEM HANGS WHEN FILE SAVE IN DIRECTORY OF ASSOCIATED PROGRAM.
APAR= JR12294
DRIVE OBJECT NOTEBOOK DETAILS PAGE AND SHELL ARCHIVING BOTH
SHOW TOO LITTLE DRIVE SPACE.
If you have already installed Fixpak 9, you can install the 2nd release
over it which will replace PMWP.DLL or you can manually replace this file
with PMWP.DLL from Fixpak 8.
To do the manual replacement, download PMWP.ZIP from:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/english-us/xr_m009/
Unzip the file (use PKUNZIP or UNZIP), then:
■ .Shutdown your system then reboot. When you see the white block with
OS/2 in the top left corner of the screen, press Alt+F1 the press F2
when the Recovery Choices screen is displayed to get to a command
prompt.
■ Rename \os2\dll\pmwp.dll pmwp.fp9
■ Copy the downloaded and unzipped PMWP.DLL to \os2\dll.
■ Press Ctrl+Alt+Del to reboot your system.
Second Release notice 3
November 10, 1998 - Warp 4 FixPak XR_M009
3.0.2 CLOCK01.SYS
We also took this opportunity to replace CLOCK01.SYS with the one shipped
with Warp 3 Fixpak 36 and Warp 4 Fixpak 7 as the one shipped in Warp 3
Fixpaks 37 and 38 and Warp 4 Fixpaks 8 and 9 can cause strange clock
behavior on some machines.
This means the following APAR is no longer fixed in Fixpak 9 and will be
fixed in Fixpak 10 or later (was not listed in the README2).
APAR= JR25495
DOSGETDATETIME RETURNS BAD VALUES OR EXPERIENCES
SUDDEN JUMPS IN VALUES. SEE PJ25912
Symptoms include the minute jumping 2 minutes for every minute that
elapsed or jumping from the 29th of the month to the 1st of the next
month at midnight (i.e. 10/29 jumps to 11/01).
These symptoms have been seen on the following machines and may occur on
others:
■ IBM PC340
■ IBM Valuepoint N37s
■ Toshiba Satellite 210 Laptop
■ Toshiba Satellite 420 Laptop
This problem is being tracked by IBM under Warp 3 APAR PJ25912 and Warp 4
APAR JR12447.
To see if your system has this problem after applying the first release
of this Fixpak, do the following:
1. Shutdown all applications
2. Start the System Clock program from the System Setup folder
3. Click mouse button 2 on the clock face, select properties.
4. Click on the "View" tab
5. Select "Both date and time" under Information
6. Select "Digital" under Mode.
7. Click on the "Date/Time" tab
8. Set system time to 11:59:30
9. Set system date to 29
10.Close the Properties window
Watch the date as the time crosses midnight. If it jumps to the 1st of
the month then you have the problem and need to apply the second release
of this Fixpak to your system. If it doesn't jump then you do not have
the problem and do not need to apply this second release of Fixpak 9.
In either case, reset the clock to the correct date and time after the
test.
Second Release notice 4
November 10, 1998 - Warp 4 FixPak XR_M009
4.0 INSTALLATION NOTES
4.0.1 SYSTEM SOUNDS NOT WORKING AFTER FIXPAK APPLIED
If, after applying a FixPak, your System Sounds no longer work or you get
an error message stating "Error in closing CD device: Invalid device ID
given" when you close the CD Player, it may be caused by the FixPak
replacing the following files in your MMOS2 directory tree:
\MMOS2\DLL\DIVE.DLL
\MMOS2\DLL\MMPM.DLL
\MMOS2\DLL\MPGIO.DLL
\MMOS2\SSMDD.SYS
\MMOS2\DLL\SVMC.DLL
\MMOS2\DLL\SVSH.DLL
To recover, restore these files from your FixPak Backup or Archive
directory.
1. Boot from another partition, your Installation or Utility disks.
2. Rename the existing files in the MMOS2 directory tree so they will not
be overlayed when you restore the older files.
3. Change to the FixPak Backup directory if there is one. If not then
change to the FixPak Archive directory.
Note: The names may not be Backup or Archive. They will be whatever
you called them when you applied a FixPak.
4. For each of the above files, enter
UNPACK source target
Where "source" is the filename.ext of the file in the Backup or Archive
directory, like DIVE.DL_ or SSMDD.SY_
"target" is the fully qualified path of where to place the file,
like C:\MMOS2\DLL or C:\MMOS2
5. Repeat for each of the above files
6. Reboot your system. This resolved the problem on a TP760 and may also
resolve the problem on other hardware.
Installation Notes 5
November 10, 1998 - Warp 4 FixPak XR_M009
4.0.2 IBM1S506.ADD DRIVER REMOVED FROM FIXPAK
We have temporarily removed the IBM1S506.ADD file from our Fixpaks. To
get the latest available, try the OS/2 DD Pak Online at
http://service.software.ibm.com/os2ddpak/html/
4.0.3 AIC7870.ADD DRIVER REMOVED FROM FIXPAK
We have temporarily removed the AIC7870.ADD file from our Fixpaks. To get
the latest available, try the OS/2 DD Pak Online at
http://service.software.ibm.com/os2ddpak/html/
or try the Adaptec Web site at http://www.adaptec.com.
4.0.4 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.
Installation Notes 6
November 10, 1998 - Warp 4 FixPak XR_M009
4.0.5 INSTALLATION OF JAVA 1.1.4
Installation of Java 1.1.4 on top of this FixPak will down-level portions
of the ULS support. If this occurs, Euro currency support will not work
correctly. To recover, re-install this FixPak. This will allow both Java
1.1.4 and Euro support to work correctly.
4.0.6 DSPRES.DLL INCLUDED IN THIS FIXPAK
DSPRES.DLL has been added to this FixPak for support for Euro character
display. This file can sometimes be overwritten by video device driver
installation. If this occurs, an updated version is located in
\OS2\INSTALL\VGA. This updated file can be copied into the \OS2\DLL
directory.
4.0.7 NO PRODUCTS WERE FOUND
If you see a "No products were found" message while applying this FixPak,
there is probably a mismatch between the data in
\OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this FixPak.
Compare the data for the OS/2 Base Operating System from the SYSLEVEL
command output with the same values listed at the end of this document in
the "FixPak Corrective Service levels and disk layouts" section. They
must be identical.
If these values are correct, check for the following files on any OS/2
boot drive in the \OS2\INSTALL directory.
LOGF0000.OS2
LOGSTART.OS2
LOGARCH.OS2
Check for the following files in your MMOS2\INSTALL directory.
LOGF0000.MPM
LOGSTART.MPM
LOGARCH.MPM
Also check for the following file:
C:\CSF_SEL.000
If these files exist, rename them and try the FixPak installation again.
Delete the renamed files after the FixPak has been applied.
Installation Notes 7
November 10, 1998 - Warp 4 FixPak XR_M009
4.0.8 PREVIOUS INSTALLATION INTERRUPTED
If you get a message that the previous installation of a FixPak was
interrupted (whether true or not), check for the following files and
directory on all drives:
Files:
FIXSTART
IBMCSFLK.LST
IBMCSFLK.CSF
CSF_*
Directory:
IBMCSFLK
If any exist, rename them and try the FixPak installation again. Delete
the renamed files after the FixPak has been applied.
4.0.9 UNABLE TO OPEN ARCHIVE DIRECTORY
If you get a message about problems with the Archive directory (for
example, cannot find or unable to open), then the most probable cause is
that you applied a previous FixPak and have since deleted the FixPak
ARCHIVE or BACKUP directory.
To recover from this, follow the "No files to service" and "Previous
installation interrupted" steps listed above.
4.0.10 RC 932 DOING CID INSTALL OF WARP 4
If you get a RC (Return Code) 932 while doing a CID install of Warp 4 and
you are using RSPINST.EXE from FixPak 3 or later, you will need to do the
following.
1. Create a temporary work directory somewhere on your harddrive.
assume it's c:\tempwork
2. Locate the section called "FixPak Corrective Service levels and disk
layouts".
3. Locate CHKDSK.SYS, CHKDSK32.DLL, CHKDSK32.EXE and UHPFS.DLL and
record what disks they are found on.
Note: For FixPak 3, they are on disks 12, 8, 12 and 9 respectively.
This will change for later FixPaks.
Installation Notes 8
November 10, 1998 - Warp 4 FixPak XR_M009
4. Place FixPak disk 12 in A: and enter
unpack a:\fix\os2.1\chkdsk.sy_ c:\tempwork
5. Place FixPak disk 8 in A: and enter
unpack a:\fix\os2.1\chkdsk32.dl_ c:\tempwork
6. Place FixPak disk 12 in A: and enter
unpack a:\fix\os2.1\chkdsk32.ex_ c:\tempwork
7. Place FixPak disk 9 in A: and enter
unpack a:\fix\os2.1\uhpfs.dl_ c:\tempwork
8. Make backup copies of CHKDSK.SYS, CHKDSK32.DLL and UHPFS.DLL from the
DISK_3 directory of your CID tree.
9. Copy CHKDSK.SYS from c:\tempwork to the DISK_3 directory of your CID
tree
10.Copy CHKDSK32.DLL from c:\tempwork to the DISK_3 directory of your CID
tree
11.Copy UHPFS.DLL from c:\tempwork to the DISK_3 directory of your CID
tree
12.Make a backup copy of the BUNDLE file on DISK_0
13.Copy DISK_0\BUNDLE c:\tempwork
14.Copy PACK2.EXE to c:\tempwork. If you don't have this file you can get
it using your Web browser from
ftp://ps.software.ibm.com/ps/products/os2/fixes/v4warp
15.PACK2 CHKDSK32.EXE bundle /H:\OS2\CHKDSK32.EXE /A
Note: This adds CHKDSK32.EXE to the bundle file. Enter "unpack bundle
/show" to verify it's really there.
16.Copy the updated BUNDLE back to the DISK_0 directory
17.Delete the c:\tempwork directory and files.
18.Copy the files SCSIADDS and PRESCHEK from DISK_4 to DISK_5.
19.Do the CID install
Installation Notes 9
November 10, 1998 - Warp 4 FixPak XR_M009
4.0.11 MULTIMEDIA NO LONGER SELECTABLE
IBM Multimedia Presentation Manager/2 (MPM) is now fully integrated into
the base OS/2. As part of this change, the \MMOS2\INSTALL\SYSLEVEL.MPM
file has been deleted. This means you will no longer see it as a
selectable entry in the Serviceable Products window when using the
A:SERVICE method of installation.
4.0.12 MMPARTS.DLL/USER.EXE POPUP DURING INSTALL
If you get a popup about MMPARTS.DLL or USER.EXE during install, reply
"Yes" to replace it.
4.0.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.
4.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.
4.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.
Installation Notes 10
November 10, 1998 - Warp 4 FixPak XR_M009
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.
4.0.16 PRINTER INSTALLATION PROCESS CHANGE
If you install a new printer by clicking MB2 on the Printer icon in the
templates folder then clicking on Install, the printer object will now be
created in the Printer folder, not on the Desktop.
4.0.17 CONFIGURATION INSTALLATION DISTRIBUTION ( CID )
Read the README.CID on Disk # 1 for an example of how to set up a
response file to do a CID install.
Installation Notes 11
November 10, 1998 - Warp 4 FixPak XR_M009
5.0 POST INSTALLATION NOTES
5.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.
5.0.2 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING
A problem occurs with some Windows printer drivers where a zombie thread
is left running after the program that loaded it is exited.
This does not occur when the program is run from a Seamless instance of
PROGMAN or from a Full Screen session because when these are exited the
whole WINOS2 Subsystem is exited.
This problem has been reported for the Adobe and Hewlett Packard Windows
printer drivers. To correct this problem for people running with these
drivers ONLY who have experienced symptoms such as:
■ exiting a program running seamlessly after printing or
■ setting up a printer and seeing the icon not being unhatched and/or
■ not being able to start another copy of the program
Add the following line in OS2\MDOS\WINOS2\SYSTEM.INI in the *boot*
section:
■ backgroundtasks=run_enum.exe,hpfbkg02.exe
then restart WINOS2.
Note: There may be other drivers that have the same problem. If you
experiences a similar problem with other drivers, please report it so the
correct SYSTEM.INI entry can be determined.
Post Installation Notes 12
November 10, 1998 - Warp 4 FixPak XR_M009
5.0.3 APAR JR09494 (TRAP EXITING WINOS2 WITH MWAVE AUDIO)
The fix for APAR JR09434 (trap exiting winos2 with MWAVE audio) requires
a new MWAVEVDD.SYS dated 11/96 or later. This file is available from the
IBM PC Company web site at http://www.pc.ibm.com.
5.0.4 SYS3170 INSTALLING LOTUS SMARTSUITE 96
A problem was discovered when attempting to install Lotus SmartSuite 96
with a early version of the Matrox video driver. A SYS3170 occurs after
pressing the button to start copying the files to the hard disk.
The problem does not occur with the current Matrox driver available on
the Web at
http://www.matrox.com/mgaweb/drivers/ftp_os2.htm
A work around that does not involve downloading files from the web, is to
switch your display driver to VGA during the install and after it has
completed, restore the Matrox driver.
5.0.5 INTERMITTENT HANGS
If you experience intermittent hangs of your system, check your LIBPATH
statement in CONFIG.SYS to see if SOM.DLL is in a directory other than,
and ahead of, OS2\DLL.
If yes, either change the LIBPATH statement to move the directory after
OS2\DLL or try renaming SOM.DLL to SOM.DLO.
One known cause of this is VisualAge C++. It has a version of SOM.DLL in
its DLL library and the installation puts this library ahead of OS2\DLL
in the LIBPATH statement.
5.0.6 INTERMITTENT PAUSE WITH IBM THINKPAD 760E/ED/ELD/EL
If you have an IBM Thinkpad 760E/ED/ELD/EL that exhibits sluggish
harddisk behavior (pausing intermittently with hard drive light on) after
this FixPak has been applied, add the /!BM parameter to the
BASEDEV=IBM1S506.ADD statement (if present) in your CONFIG.SYS. This
will disable the Bus Mastering function whose default has been changed
from OFF to ON.
If your CONFIG.SYS has the statement
BASEDEV=PIIXIDE.ADD
Post Installation Notes 13
November 10, 1998 - Warp 4 FixPak XR_M009
you must remark out the statement by inserting REM as the first
characters on the line as shown below.
REM BASEDEV=PIIXIDE.ADD
BASEDEV=IBM1S506.ADD /A:0 /!BM /U:1 /ATAPI /FORCE
5.0.7 APM USERS
APM users will need to add the following statement after the
DEVICE=\OS2\BOOT\APM.SYS statement in their CONFIG.SYS:
RUN=\OS2\BOOT\APMDAEMN.EXE
This will complete the fix for APAR JR09869.
Post Installation Notes 14
November 10, 1998 - Warp 4 FixPak XR_M009
6.0 NEW FUNCTION
It is our policy not to include new function in FixPaks. However, as with
any policy there may be exceptions. If any exception occurs in the
future, we will communicate them to you in this section of the
README.1ST.
6.1 QUERYING FILE DATES FOR FILES AFTER DEC 31, 1999 IN REXX
Existing REXX functions return file dates with a two digit year only.
While these functions are Year 2000 tolerant (i.e. the results will be
correct for files dated after Dec 31, 1999) they require some additional
logic in existing programs to handle the returned date correctly when
they are compared with other file dates.
Since the output format of the existing functions could not be changed
for compatibility reasons, new options have been added to the REXX
interpreter to return file dates with the year formatted with 4 digits.
Two functions have been extended to support the new format. The syntax to
retrieve the file date in 4 digit format is as follows:
/********************************************/
/* Use STREAM QUERY TIMESTAMP to query file */
/* date in 4 digit format */
/********************************************/
Say Stream("C:\CONFIG.SYS", "C", "QUERY TIMESTAMP")
/***********************************************/
/* Use option "L" with SysFileTree to return a */
/* list of files with long date format */
/***********************************************/
Call RxFuncAdd "SysLoadFuncs", "RexxUtil", "SysLoadFuncs"
Call SysLoadFuncs
Call SysFileTree "C:\*.*", "Files", "L"
Do i = 1 To Files.0
Say Files.i
End
These extensions are available in both classic REXX and Object REXX on
OS/2 Warp 3 and Warp 4 since fix pack versions 35 and 6. If you use these
extensions in your program you have to make sure that you are running the
right level of REXX
New Function 15
November 10, 1998 - Warp 4 FixPak XR_M009
6.2 ENHANCED SUPPORT FOR WORKSPACE ON-DEMAND
6.2.1 PMLOGON USER EXITS
This function, provided by PMLOGON, allows system integrators to have
REXX code executed at specific points during the startup and logon
sequence. By default, user exits are disabled in PMLOGON.EXE. To enable
user exits, an execution parameter (/URX) in the RUNWORKPLACE line of the
CONFIG.SYS file must be added. The /URX parameter specifies the location
and name of the user exit command file:
Execution Parameter User Exit command file that will be
executed
------------------- -----------------------------------
/URX \OS2\PMLOGURX.CMD
/URX:<filename>.CMD <filename>.CMD located in one of the
locations specified by the PATH
environment variable
/URX:d:\<path>\<filename>.CMD d:\<path>\<filename>.CMD
The same command file is called for ALL user exits. The FIRST parameter
supplied to the command file indicates the exit that it is being called
for. The REXX command file is called for all these exits, even if it does
not need to process all of the exits. The REXX command file must be able
to return error free if it receives an exit number that it does not need
to handle. The following user exits are available:
New Function 16
November 10, 1998 - Warp 4 FixPak XR_M009
First Parameter Exit Description
--------------- ----------------
0 Executes ONCE per boot, before the requester
is started. There is no user logged on at this
time. This exit may return a string that is
processed exactly as the following execution
parameters set in RUNWORKPLACE of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately after the execution
parameters. See Note 2 below on /AUTO processing.
1 Executes ONCE per logon, after the requester
is started, but before logon occurs. There is no
user logged on at this time. This exit may return
a string that is processed exactly as the
following execution parameters set in RUNWORKPLACE
of CONFIG.SYS:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
It is processed immediately before logon. See
Note 2 below on /AUTO processing.
2 Executes ONCE per logon, after the requester is
started and after logon occurs. There is a user
logged on at this time, but the Desktop has not
been started and the objects are not displayed.
No returns are processed.
3 Executes ONCE per logon, after the Desktop has
been started and the objects are created but not
currently displayed, but immediately before
control is passed to the Desktop. The icons are
fixed at this point. There is a user logged on
at this time. No returns are processed.
4 Executes immediately after a failed logon. The
second parameter passed to the exit contains the
return code from the logon API. This exit may
return a string that is processed exactly as the
execution parameters set in RUNWORKPLACE of
CONFIG.SYS for the following parameters only:
/U: /UF: /P: /PF: /D: /DF: /PW /AUTO /NONFLE
This exit is processed immediately and logon is
retried with the new parameters regardless of
the /AUTO switch. See Note 2 below on /AUTO
New Function 17
November 10, 1998 - Warp 4 FixPak XR_M009
processing. If no string is returned, then the
normal logon failure or password expired message
box is displayed.
Note 1: The session environment for the REXX command file is that
of PMLOGON.EXE and, therefore, does not contain any input or
output facility. For example, "PULL" from the keyboard and
"SAY" to the console do not work.
Note 2: The /AUTO parameter is validated at every step (for example,
after command line processing, after exit 0 returns, and
after exit 1 returns). It is turned off if insufficient
information (such as no user ID) is provided at that stage
for an automatic logon. If the user ID is supplied by the
exit, that exit must also provide the /AUTO parameter in
order for an auto logon to work.
6.2.2 SETUP STRINGS FOR PUBLIC APPLICATIONS
The NCAPPUTL.EXE utility of WorkSpace On-Demand allows for specific
Workplace Shell WPProgram setup strings that are provided when creating
public applications on the WorkSpace On-Demand Desktop. In particular,
the ICONPOS setup string can be defined for a public application so that
the Administrator can identify where application icons are placed on the
WorkSpace On-Demand Desktop.
When a WorkSpace On-Demand Administrator creates a public application, a
new environment variable must be added to the application to provide a
setup string. The parameter name is NCC_SETUP_POST and the parameter
value can consist of any of the setup strings specified below. Each
setup string consists of a KEYNAME, followed immediately by an equal
('=') sign and a VALUE. Multiple setup strings can be passed in the
NCC_SETUP_POST environment variable by separating each setup string with
a semicolon (';'). The creation of this parameter can be performed
either using the WorkSpace On-Demand Public Applications Notebook (on the
Parameters page) or using a Command Line Interface (CLI). The following
is an example of one parameter:
NCC_SETUP_POST=ICONPOS=10,10;
The NCC_SETUP_POST environment variable will be searched for when each
WorkSpace On-Demand public application is created. If it is found, its
value will be used when creating the public application on the WorkSpace
On-Demand Desktop.
The following KEYNAME values are permitted for setup strings:
New Function 18
November 10, 1998 - Warp 4 FixPak XR_M009
Keyname Value Description
------- ----- -----------
CCVIEW DEFAULT Specifies the default value for
concurrent views
YES Creates new views
NO Displays the open view
ICONFILE filename Sets the object's icon.
ICONPOS x,y Sets the initial icon position in
a folder. The "x" and "y" values
represent the position in the object's
folder in percentage coordinates.
ICONRESOURCE id,module Sets the object's icon. The "id"
is the icon resource ID in the dynamic
link library (DLL) "module."
Refer to the Workplace Shell Programming Reference for a description and
definition of the above setup strings.
Note: The NCC_SETUP_POST environment variable exists in the current
environment when the public application with which it is associated is
running.
6.2.3 COMMAND LINE OPTIONS FOR TLOGOFF AND TSHUTDWN
Three command line options have been added to both TLOGOFF.EXE and
TSHUTDWN.EXE:
1. /Q -- causes these programs not to display the UPM/LAN
copyright window.
2. /N -- causes no confirmation message boxes to be displayed.
Note: If these parameters are not capitalized, they are ignored.
6.2.4 PMLOGON NO PROGRESS INDICATOR OPTION
An execution parameter has been added to PMLOGON that causes the progress
indicator window not to be displayed during all of logon processing. That
parameter is /NOPI and can be specified only from the RUNWORKPLACE line
in CONFIG.SYS. If /NOPI is returned as a parameter from a user REXX exit,
it is ignored.
New Function 19
November 10, 1998 - Warp 4 FixPak XR_M009
6.2.5 PMLOGON NO SYSTEM MODAL WINDOW OPTION
An execution parameter has been added to PMLOGON which prevents PMLOGON
from setting any of its windows to be system modal after user exit 1 is
executed on the first boot or anytime after a logoff. The parameter is
/NOSM1 and can only be specified from the RUNWORKPLACE line in
CONFIG.SYS. If /NOSM1 is returned as a parameter from a user REXX exit,
it is ignored.
6.3 FIXED IDE HARD DRIVE AND REMOVABLE MEDIA SUPPORT
FixPak 35 (FP35) for Warp 3 and FixPak 6 (FP6) for Warp 4 extended
support for fixed Enhanced IDE drives to sizes up to 8.4GB and added new
caching HPFS and FAT file system support for removable media drives such
as SCSI Syquest Syjet 1.5GB portable hard drive and the Iomega jaz 1GB
and 2GB personal hard drives.
FixPak 39 for Warp 3 and FixPak 9 for Warp 4 contain updates to the
support in FP35 and FP6, extending support to fixed Enhanced IDE drives
greater than 8.4GB, fixing some problems, and adding additional
documentation on removable media support.
See the README.RMS file on the first FixPak diskette for complete
information on large IDE Hard Drive and Removable Media Support.
6.4 EURO SUPPORT
The European Monetary Union is creating the euro as a new common currency
for Europe. As part of this effort the European Commission has
introduced a new character which represents the euro. This character
looks like an uppercase C with two horizontal lines through it. The euro
will come into existence on January 1, 1999 for use in banking. Euro
notes and coins will be issued starting January 2002.
6.4.1 BASE OS/2 SUPPORT
The OS/2 basic support for Euro consists of adding the euro character to
fonts, codepages, and keyboards. The euro is added to all display and
ATM fonts and to the Times New Roman MT 30 TrueType font which is
available with Java 1.1. The euro is added to all western European
keyboards and the US International keyboard. The euro can be used in
base OS/2, Presentation Manager, and in DOS. The euro is not supported
in WinOS2.
The euro character is added to these OS/2 base and PM codepages:
New Function 20
November 10, 1998 - Warp 4 FixPak XR_M009
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)
The euro character is added to these OS/2 keyboards:
New Function 21
November 10, 1998 - Warp 4 FixPak XR_M009
Belgium be altgr-e
Canada ca altgr-e
Canadian French cf altgr-e
Denmark dk altgr-5
Finland su (fi) altgr-5
France fr altgr-e
Germany gr (de) altgr-e
Germany(453) de453 altgr-e
Iceland ic (is) altgr-5
Iceland 101 is458 altgr-5
Italy it altgr-5
Italy extended it142 altgr-5
Latin America la altgr-e
Netherlands nl altgr-e
Norway no altgr-5
Portugal po altgr-5
Spain sp (es) altgr-5
Sweden sv altgr-5
Swiss French sf altgr-e
Swiss German sg (sd) altgr-e
Turkey tr179 altgr-e
Turkey 440 tr440 altgr-e
UK uk altgr-4
UK 168 uk168 altgr-e
US International ux altgr-e
6.4.2 WHERE EURO IS NOT SUPPORTED
The euro is not supported in WinOS2. This character is not supported in
the Windows-1252 codepage used in WinOS2. This character is not
available on the WinOS2 keyboards. This character is not available in
the WinOS2 supplied TrueType fonts:
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 22
November 10, 1998 - Warp 4 FixPak XR_M009
6.4.3 PRINTING THE EURO
Existing printers do not support the euro in device fonts. You need to
select a font which is not mapped to a device font in order to print the
euro. The euro will print correctly on printers where the system fonts
are used. When there are problems, a dotless-i is normally printed
instead of the euro.
For PostScript printers, it is necessary to disable device fonts to print
the euro in one of the base PostScript fonts (Helvetica, Times Roman,
Courier). To do this:
1. Open the properties of the Printer object
2. Select the Print Driver tab
3. Select Job Properties
4. Select the Output tab
5. Deselect "Use printer device fonts"
6.5 NEW WARP REGISTRY EDITOR
See the README.REG file on the first FixPak disk for details.
6.6 WORKSPACE ON DEMAND
WorkSpace on Demand is supported starting with FixPak 5 (XR_M005).
6.7 IBM OPEN32
This FixPak includes updates to the IBM Open32 Application Programming
Interfaces (APIs).
6.8 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
Future updates for GRADD and other video drivers (when they are released)
will be found via the internet at:
■ http://service.software.ibm.com/pslaunch.html
New Function 23
November 10, 1998 - Warp 4 FixPak XR_M009
6.9 NEW (IMPROVED) CHKDSK
This version of CHKDSK offers significant improvements for High
Performance File System (HPFS) drives. CHKDSK now fixes all errors found
on HPFS drives in a single pass, operating faster, and with less memory
than previous versions. It contains better error detection and
correction algorithms, and creates a log file so service personnel can
determine what errors it found and how it corrected them. Finally, only
the amount of physical memory in your system limits the size of the
largest drive CHKDSK can check at boot time (autocheck).
Improvements in this version of CHKDSK are for HPFS drives only. No
changes occurred to checking File Allocation Table (FAT) drives. This
enhanced CHKDSK operates on IBM OS/2 Warp 3.0 and higher, including IBM
Warp 4, IBM Warp Server 4 and IBM Warp Server 4 SMP. This new CHKDSK
version will not run on version of OS/2 before OS/2 Warp 3.0.
6.9.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 24
November 10, 1998 - Warp 4 FixPak XR_M009
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 25
November 10, 1998 - Warp 4 FixPak XR_M009
If you need to boot from diskettes to check an HPFS drive, you must have
the following files on the diskette you wish to run CHKDSK from:
CHKDSK.COM
CHKDSK32.DLL
UHPFS.DLL
The BOOTDISK.EXE program has been updated to create new utility diskettes
with the proper files.
6.9.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.
6.10 AUTOMATED TRAP SCREEN LOGGING
Whenever an application program traps, the trap information is (now)
automatically logged in the POPUPLOG.OS2 file. This is a cumulative file
that is by default located in the root directory of the bootable
partition. Should this file become too large then it may be erased or
pruned (reduced in size). The system will automatically re-create it if
it does not exist.
The TRAPLOG command and SUPPRESSPOPUPS CONFIG.SYS statement may be used
to control trap screen behavior (see below).
New Function 26
November 10, 1998 - Warp 4 FixPak XR_M009
6.10.1 SUPPRESSPOPUPS
SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior. That
is, to disable logging and to have trap screens displayed unless
specifically overridden by an application's use of the DosError API.
SUPPRESSPOPUPS=x: will disable trap screen display for all processes and
will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or
partition.
If SUPPRESSPOPUPS is omitted then the behavior is as described above
under "Automated Trap Screen Logging".
6.10.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.
6.10.3 TRAPDUMP
The TRAPDUMP command allows the conditions under which a trap will
initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak
29, the System Dump setting could only be manipulated from CONFIG.SYS by
use of the TRAPDUMP statement.
Use of this command should be made under the direction of service
personnel.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred, thus under rare
circumstances data can be lost.
The command syntax is:
New Function 27
November 10, 1998 - Warp 4 FixPak XR_M009
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]
where:
■ ON enables all application and system traps to initiate a System Dump.
■ OFF disables automatic dump initiation.
■ R0 enables only Ring 0 traps to initiate a System Dump.
■ x: specifies the Dump Partition.
■ NOCHECK overrides the system level check for WARP 4.0, since use of
this command on a system level prior to FixPak 29 is equivalent to the
SYSDUMP command.
6.10.4 SYSDUMP
The SYSDUMP command forces a System Dump to be initiated, regardless of
the TRAPDUMP settings. This command is provided for the use of service
personnel to allow Dump Initiation to be automated through use of a
command file.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred thus under rare
circumstances data can be lost.
The command syntax is:
SYSDUMP [/NOPROMPT]
where:
■ NOPROMPT allows the Dump to proceed without the prompt and response to
message:
"Do you want to force a system dump? (Y/N)"
6.11 OTHER README FILES
There are other README files containing information you may want to
review. They are all found on the first FixPak disk.
File Use
README2 Problems fixed in each FixPak (APAR list)
New Function 28
November 10, 1998 - Warp 4 FixPak XR_M009
README.CID Installing FixPaks via CID
README.DBG Tips on debugging OS/2 Warp (3.0 and 4.0)
README.REG Use of the Warp Registry Editor REGEDIT2.EXE
README.RMS Using the new Removable Media Support
New Function 29
November 10, 1998 - Warp 4 FixPak XR_M009
7.0 CORRECTIVE SERVICE FACILITY
7.0.1 REQUIRED CSF LEVEL
You should use release level F.139 or later of the OS/2 Corrective
Service Facility to install this FixPak.
Bootable diskettes are no longer provided starting with the F.138B CSF
build. Instead, you now get a self-extracting ZIP file which contains the
following:
8-11-98 4:46p 101 0 build.lvl
2-11-97 10:51a 60304 0 csfpans.dll
8-10-98 2:57a 88354 61 filefix.dll
6-29-98 10:24a 840 0 fpinst.cmd
8-11-98 4:46p 299216 0 fservice.exe
1-26-98 11:00a 12806 0 fservice.msg
7-19-96 3:47p 33031 49 ibmcsflk.dll
7-30-98 5:15p 15725 0 ibmcsflk.exe
5-02-95 4:17p 516 0 ibmcsflk.msg
7-26-96 4:00p 3860 0 IBMCSFLK.SYS
9-23-94 3:17a 512 49 msg.dll
9-23-94 3:16a 512 49 nls.dll
9-23-94 5:23a 58256 0 pack.exe
8-11-98 4:43p 20928 0 read.me
5-02-95 4:14p 27497 0 readme.INF
6-29-98 10:24a 654 0 response.lan
6-29-98 10:24a 3364 0 response.wp3
6-29-98 10:24a 4201 0 response.wp4
8-11-98 4:45p 325968 3543 service.exe
5-02-95 4:14p 21068 0 service.hlp
10-07-94 2:08p 47189 49 shpiinst.dll
9-23-94 5:24a 72048 0 unpack.exe
9-23-94 5:25a 77200 0 unpack2.exe
9-23-94 3:28a 2048 49 viocalls.dll
Follow the directions in the READ.ME file to use the new CSF code. It
covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
from one of several alternative boot methods.
7.0.2 WHERE YOU CAN FIND CSF CODE
The Corrective Service Facility code is available from many places,
including, but not limited to, the following:
Source How to access
Corrective Service Facility 30
November 10, 1998 - Warp 4 FixPak XR_M009
Internet(FTP) Anonymous FTP to ftp.software.ibm.com in the
"/ps/products/os2/fixtool" directory.
Internet(WWW) Point your Web Browser at
ftp://service.boulder.ibm.com/ps/products/os2/fixtool
Intranet(FTP) Anonymous FTP to os2service.austin.ibm.com in the
"f:\fixpacks\fixtool" directory.
7.0.3 CREATING FIXPAK DISKETTES
Use LOADDSKF.EXE to create the diskettes. For each disk image, place a
2MB HD (1.44MB formatted) diskette in A:.
Warning: DO NOT use a 1MB (720KB formatted) diskette because you might
have problems trying to install this FixPak.
For each diskette image in the FixPak, do the following:
Enter LOADDSKF XR_M009.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_M009
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through 35.
Examples:
XR_M009.ADK = 10
XR_M009.FDK = 15
XR_M009.LDK = 21
etc.
7.1 RESIDUAL FIXPAK FILES FROM OS/2 2.11 OR WARP 3
If the following is true:
1. You upgraded your system from OS/2 2.11 or Warp 3
2. You applied one or more FixPaks to the previous system
3. You HAVE NOT applied a Warp 4 FixPak
Corrective Service Facility 31
November 10, 1998 - Warp 4 FixPak XR_M009
You will have files and directories left on your harddisk that will cause
problems when installing a Warp 4 FixPak.
To prevent these problems from occurring, do the following before
applying your first Warp 4 FixPak.
On your Warp 4 boot drive:
■ Delete \OS2\INSTALL\LOGF0000.OS2
■ ATTRIB -R \OS2\INSTALL\LOGSTART.OS2
■ Delete \OS2\INSTALL\LOGSTART.OS2
On the drive where Multimedia Presentation Manager is installed:
Note: This can be your Warp 4 boot drive or any other drive on your
system. Check the "SET MMBASE=" statement in CONFIG.SYS to determine
which drive this is.
■ Delete \MMOS2\INSTALL\LOGF0000.MPM
■ ATTRIB -R \MMOS2\INSTALL\LOGSTART.MPM
■ Delete \MMOS2\INSTALL\LOGSTART.MPM
Remove the old Archive and Backup directories and SERVICE.LOG file to
recover the space they are using.
You should also remove the FixPak Archive and Backup directories left
over from your updated OS/2 2.11 or Warp 3 system at this time as well as
the \OS2\INSTALL\SERVICE.LOG file.
7.2 READ-ONLY FILES
Some files being updated by this FixPak may have the Read-Only attribute
set. If you are using the A:SERVICE method to install this FixPak you
will be asked if you want the files replaced.
Press the "OK" button.
7.3 SYSLEVEL FILE LOCATIONS
This FixPak will service directories based on the location of a supported
SYSLEVEL.OS2 file. Please check your system to make sure extra copies of
this file are not located in directories other than:
\OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)
If additional copies of these files are found in other locations on your
hard disk then CSF will try to service files as follows:
Corrective Service Facility 32
November 10, 1998 - Warp 4 FixPak XR_M009
For \OS2\INSTALL\SYSLEVEL.OS2
..\..\ all files in a directory two levels above (toward the
root). This should be the root directory of your boot
drive.
..\* all files in a directory one level above (toward the root)
and all subdirectories below. This should be the OS2
directory and subdirectories.
..\..\VT\* all files in the VT directory and subdirectories.
..\..\PSFONTS\* all files in the PSFONTS directory and subdirectories.
..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories.
..\..\OPENDOC\* all files in the OPENDOC directory and subdirectories.
7.4 RELOCATED OS/2 FILE SUPPORT
If you have moved OS/2 files or directories to a drive other than the one
the SYSLEVEL.OS2 file is on, do the following in order to have them
serviced:
■ Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of the
OS\2 Warp 4 partition to be serviced.
In this file, place the full path to the directories you want to be
serviced. Assuming your boot drive is C: and you installed Multimedia
on the D: drive and manually moved WINOS2 support to the E: drive:
Corrective Service Facility 33
November 10, 1998 - Warp 4 FixPak XR_M009
D:\MMOS2
D:\MMOS2\DLL
D:\MMOS2\DSP
D:\MMOS2\HELP
D:\MMOS2\IMAGES
D:\MMOS2\INETTEMP
D:\MMOS2\INSTALL
D:\MMOS2\MACROS
D:\MMOS2\MOVIES
D:\MMOS2\SOUNDS
D:\MMOS2\SOUNDS\DESKTOP
D:\MMOS2\SOUNDS\GARDEN
D:\MMOS2\SOUNDS\OCEAN
D:\MMOS2\SOUNDS\SPACE
E:\OS2\MDOS\WINOS2
E:\OS2\MDOS\WINOS2\SYSTEM
E:\OS2\MDOS\WINOS2\TEMP
Note: Leave this file for any future OS/2 Warp 4 FixPaks you might apply.
The easy way to create this file is to use the DIR command with the /A:D
/S /B parameters and pipe the output to a file.
dir d:\mmos2 /a:d /s /b > anyfile
Then copy that data into the USERDIRS.OS2 file.
With CSF release level F.137B or later, you can use wildcards, so your
USERDIRS.OS2 file would be much simpler and would look like:
D:\MMOS2\*
E:\OS2\MDOS\WINOS2\*
Corrective Service Facility 34
November 10, 1998 - Warp 4 FixPak XR_M009
8.0 INSTALLATION PROCESS
8.1 BEFORE INSTALLATION
Before installing any FixPak, run CHKDSK /F against all drives on your
system to correct any file system errors that might be present. You
cannot do this while OS/2 is active. You must shut down and run CHKDSK by
one of the following methods:
■ Boot from your Installation, DISK 1 and DISK 2 diskettes. If your
file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL
on it in your A: drive before issuing the CHKDSK command.
■ Boot from the Utilities disk you created via the "Create Utility
Diskettes" icon in the System Setup folder.
■ Boot from a different OS/2 partition.
Once CHKDSK has completed, reboot your system then shutdown all running
applications before starting the FixPak installation.
8.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
Follow the instructions in the READ.ME file that comes in the CS_139.EXE
self-extracting zip file. This explains how to use the CS_139.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Here are some additional notes:
Follow the displayed instructions. When prompted to insert Corrective
Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_M009
Corrective Service Diskette 1 in drive A. Repeat for the rest of the
FixPak disks when requested to do so.
It can take a considerable length of time for the Corrective Service
Facility to scan your hard disk for serviceable files. In some cases, it
has taken as long as 40 minutes. Please be patient and allow this
process to complete.
If this is the first OS/2 Warp FixPak you have applied to this system,
then enter the path to the directory where a copy of replaced files will
be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)
Note: This ARCHIVE directory is not related to the ARCHIVES directory
built into OS/2 Warp 3 and Warp 4. Please specify a different path. You
must specify a different ARCHIVE directory for each product to be
serviced.
Installation Process 35
November 10, 1998 - Warp 4 FixPak XR_M009
If this is not the first OS/2 Warp FixPak, then enter the path to the
BACKUP directory where a copy of replaced files will be stored (for
example, D:\BACKUP).
Note: You must specify a different BACKUP directory for each product to
be serviced.
Make sure there is sufficient space available on the drive you specify
for archive or backup. Even though these files are kept in compressed
(PACK2) format, they can take up a lot of space on the drive.
During the installation process you may see messages about Archiving,
Updating and Deferring service.
■ Archiving saves a compressed copy of the original file in the ARCHIVE
or BACKUP path you specified.
■ Updating means the original files are replaced with the new ones from
this FixPak.
■ Deferring service means the file to be updated is currently in use by
the system and cannot be updated. The new files from the FixPak are
placed in unpacked format in the \IBMCSFLK\FIX directory on the drive
with the most free space. They are processed by the locked file
device driver during reboot after you shut down the system.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
You will see the following during reboot of the system if you applied
service to the OS/2 partition you were booted from.
The locked file driver is loaded.
Processing locked files
Processing complete
The system will do one automatic reboot after the Locked File Device
Driver has completed.
8.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA
Follow the instructions in the READ.ME file that comes in the CS_139.EXE
self-extracting zip file. This explains how to use the CS_139.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Here are some additional notes:
Installation Process 36
November 10, 1998 - Warp 4 FixPak XR_M009
This method does not prompt the user for any information. No interaction
with the user takes place other than requests to put the next diskette in
drive A. All serviceable partitions on your system will be updated
automatically unless you have modified the default response file. Be
especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
this method because they can cause CSF to apply service to directories
you do not want serviced.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. Please be
patient and allow this process to complete.
Note: You can edit the response file to control some of the actions taken
by FSERVICE.EXE while applying a FixPak. See the READ.ME file or use the
VIEW command to look at the file README.INF. They are part of
CS_139.EXE.
8.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility, like how to
backout a FixPak, is available from the README.INF file on the first
Corrective Service Facility disk. To view this file, place CSF disk 1 in
drive A and enter VIEW A:\README.INF.
There is also some additional information in the READ.ME file.
8.5 FIXPAKS ON CD-ROM
Both the IBM Technical Connection and the IBM Developer Connection
contain the latest OS/2 and LAN FixPaks that were available at publishing
time.
The IBM Technical Connection homepage on the World Wide Web is located
at:
■ http://www.ibm.com/Support/techconn/index.htm
The IBM Developer Connection homepage on the World Wide Web is located
at:
■ http://www.developer.ibm.com/devcon/titlepg.htm
Check these WWW sites for content and ordering information.
Installation Process 37
November 10, 1998 - Warp 4 FixPak XR_M009
9.0 CSD LEVEL OF SYSLEVEL.OS2
The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
partition will be updated with the name of the FixPak when it is applied.
This is a major change from previous CSF releases. The Prior CSD level
field will be left asis. This means when you use the SYSLEVEL command to
look at the release levels of products on your system, you will see the
following for SYSLEVEL.OS2.
Before a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR04000
Prior CSD level: XR04000
After a FixPak is applied using the F.138B CSF build (or later)
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0M008
Prior CSD level: XR04000
All fix information is recorded in SERVICE.LOG. Look at the file
\OS2\INSTALL\SERVICE.LOG
on your boot drive for information relating to the installation of
FixPaks on your system.
Additionally, you can use the VER /R command to see the current revision
of OS/2 installed. The response will look like the following for this
FixPak:
The Operating System/2 Version is 4.00
Revision 9.033
The first page of this document has a line that looks like:
Build Level: n.nnn
CSD level of SYSLEVEL.OS2 38
November 10, 1998 - Warp 4 FixPak XR_M009
That is the number you should see for this FixPak when you issue the VER
/R command.
9.0.1 NEW SYSLEVEL.FPK
A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning with
XR_M004. It is titled "OS/2 Warp 4 Service Level". It contains the name
of the currently installed FixPak in both the Current and Previous CSD
level fields and is located in the same directory the SYSLEVEL.OS2 file
is located in which should be \OS2\INSTALL.
The easiest way to look at SYSLEVEL information is to use the SYSLEVEL
command and redirect the output to a file then edit the file and search
for SYSLEVEL.FPK.
CSD level of SYSLEVEL.OS2 39
November 10, 1998 - Warp 4 FixPak XR_M009
10.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Product location on CSD: L:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
New CSD Level: XR_M009_ (Country = Generic)
Pre-requisite CSD Level: XR_4000_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
New CSD Level: XR_M009_ (Country = Generic)
Pre-requisite CSD Level: XR_4010_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\..\
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- ---------- ----- -------
AHA152X.ADD AHA152X.AD_ 15 02/09/1998 11:38 44208
AHA164X.ADD AHA164X.AD_ 15 02/09/1998 11:38 20022
AHA6360.SNP AHA6360.SN_ 15 02/09/1998 12:20 27395
AIC7770.ADD AIC7770.AD_ 14 02/09/1998 11:39 42558
AIC7870.SNP AIC7870.SN_ 16 02/09/1998 12:21 9104
APM.SYS APM.SY_ 16 02/06/1998 11:55 11412
APMDAEMN.EXE APMDAEMN.EX_ 16 02/09/1998 12:52 2733
ART.DLL ART.DL_ 9 06/17/1997 10:15 202952
ART.HLP ART.HL_ 16 04/18/1997 16:16 11980
ARTADMIN.EXE ARTADMIN.EX_ 13 06/17/1997 10:15 78693
ARTCHRON.EXE ARTCHRON.EX_ 14 07/25/1997 10:01 58994
ARTFI.EXE ARTFI.EX_ 14 06/17/1997 10:15 61482
ARTFIR.DLL ARTFIR.DL_ 15 01/16/1998 16:06 30614
FixPak Corrective Service levels and disk layouts 40
November 10, 1998 - Warp 4 FixPak XR_M009
ARTINET.DLL ARTINET.DL_ 13 06/17/1997 10:15 66252
ARTR.DLL ARTR.DL_ 13 01/16/1998 16:06 80629
ARTREG.EXE ARTREG.EX_ 13 06/17/1997 10:15 66193
ARTREGR.DLL ARTREGR.DL_ 15 01/16/1998 16:06 38138
ARTSTART.DLL ARTSTART.DL_ 16 11/12/1996 13:43 17419
ASIACOL.DLL ASIACOL.DL_ 10 06/16/1998 17:16 158732
AVIO.DLL AVIO.DL_ 13 09/30/1998 10:09 53923
BDIME.DLL BDIME.DL_ 16 05/11/1998 10:32 11879
BE.KBL BE.KB_ 16 12/12/1997 22:59 956
BLDLEVEL.EXE BLDLEVEL.EX_ 14 09/15/1998 11:32 43974
BOOTDISK.EXE BOOTDISK.EX_ 14 09/25/1998 11:44 60941
BOOTDISK.HLP BOOTDISK.HL_ 16 09/25/1998 11:44 10892
BSAUDIO.SNP BSAUDIO.SN_ 16 02/09/1998 12:22 5756
BTSCSI.ADD BTSCSI.AD_ 15 02/09/1998 11:41 26569
BVSCALLS.DLL BVSCALLS.DL_ 16 09/25/1998 11:52 512
BY.KBL BY.KB_ 16 01/22/1998 10:14 1276
CA.KBL CA.KB_ 16 12/12/1997 22:59 1198
CACHE.EXE CACHE.EX_ 16 09/24/1998 09:49 11820
CARDINFO.DAT CARDINFO.DA_ 16 09/29/1998 14:49 54979
CDFS.IFS CDFS.IF_ 15 10/23/1998 13:17 45173
CDROM.TBL CDROM.TB_ 16 11/12/1996 13:38 4365
CF.KBL CF.KB_ 16 12/12/1997 22:59 940
CHKDSK.COM CHKDSK.CO_ 14 09/25/1998 11:55 70208
CHKDSK.SYS CHKDSK.SY_ 16 10/03/1997 03:54 747
CHKDSK32.DLL CHKDSK32.DL_ 5 07/24/1998 13:47 121895
CHKDSK32.EXE CHKDSK32.EX_ 16 09/24/1998 09:50 6417
CLOCK01.SYS CLOCK01.SY_ 16 04/27/1998 17:07 4400
CLOCK02.SYS CLOCK02.SY_ 16 06/12/1998 20:10 4282
CMD.EXE CMD.EX_ 12 09/25/1998 11:58 74280
CMPXCHG8.SYS CMPXCHG8.SY_ 16 01/23/1998 17:03 2634
COM.SYS COM.SY_ 15 02/09/1998 11:48 18799
COMM.DRV COMM.DR_ 16 09/16/1998 20:46 9552
COMMAND.COM COMMAND.CO_ 14 09/25/1998 11:57 53375
CONTROL.PM CONTROL.PM_ 16 05/05/1998 01:48 8474
COUNTRY.SYS COUNTRY.SY_ 16 01/08/1998 11:31 38803
COUR.OFM COUR.OF_ 16 01/07/1998 23:34 4236
COUR.PFB COUR.PF_ 10 01/07/1998 23:34 112702
COUR.PFM COU1.PF_ 16 01/07/1998 23:34 674
COURB.OFM COURB.OF_ 16 01/07/1998 23:34 4246
COURB.PFB COURB.PF_ 10 01/07/1998 23:34 116938
COURB.PFM COUR1.PF_ 16 01/07/1998 23:34 679
COURBI.OFM COURBI.OF_ 16 01/07/1998 23:34 4260
COURBI.PFB COURBI.PF_ 10 01/07/1998 23:34 112484
COURBI.PFM COURB1.PF_ 16 01/07/1998 23:34 685
COURI.OFM COURI.OF_ 16 01/07/1998 23:34 4251
COURI.PFB COURI.PF_ 10 01/07/1998 23:34 113244
COURI.PFM COUR2.PF_ 16 01/07/1998 23:34 681
COURIER.FON COURIER.FO_ 15 01/16/1998 17:56 104183
CREX.MSG CREX.MS_ 16 09/19/1996 15:44 2865
CREXUTIL.DLL CREXUTIL.DL_ 14 12/16/1997 13:09 48397
CREXX.DLL CREXX2.DL_ 9 12/16/1997 13:09 266047
FixPak Corrective Service levels and disk layouts 41
November 10, 1998 - Warp 4 FixPak XR_M009
DDINSTAL.EXE DDINSTAL.EX_ 14 09/25/1998 11:35 35367
DE.KBL DE.KB_ 16 12/12/1997 22:59 942
DE453.KBL DE453.KB_ 16 12/12/1997 22:59 1338
DETNE2.SYS DETNE2.SY_ 16 02/09/1998 11:33 5658
DF_DEB.EXE DF_DEB.EX_ 7 10/23/1998 13:20 150007
DF_RET.EXE DF_RET.EX_ 12 10/23/1998 13:20 149009
DIBDRVR.DLL DIBDRVR.DL_ 16 10/22/1997 23:20 2267
DICTATE.EXE DICTATE.EX_ 13 05/06/1998 11:58 51391
DICTDLL.DLL DICTDLL.DL_ 14 12/21/1997 01:28 51187
DISPLAY.DLL DISPLAY.DL_ 14 08/05/1998 16:49 46574
DIVE.DLL DIVE.DL_ 13 09/29/1998 16:01 69640
DK.KBL DK.KB_ 16 06/16/1998 17:15 912
DMQSPROF.DLL DMQSPROF.DL_ 14 08/05/1998 16:46 43533
DOSCALL1.DLL DOSCALL1.DL_ 11 10/12/1998 13:59 124298
DOSCALL1.SYM DOSCALL1.SY_ 15 10/12/1998 13:59 41716
DOSCALL1.TDF DOSCALL1.TD_ 16 10/12/1998 13:59 2312
DOSKRNL DOSKRNL.___ 15 10/12/1998 13:56 30569
DRVMAP.INF DRVMAP.IN_ 16 04/03/1997 13:54 12986
DSPINSTL.EXE DSPINSTL.EX_ 11 09/25/1998 11:41 117816
DSPRES.DLL DSPRES1.DL_ 9 01/16/1998 17:54 411990
DSPRES.DLL DSPRES.DL_ 9 01/16/1998 17:54 411990
E.EXE E.EX_ 13 09/24/1998 11:32 61719
EAUTIL.EXE EAUTIL.EX_ 15 09/25/1998 11:59 37984
EJECT.EXE EJECT.EX_ 15 01/09/1998 16:20 25648
ENGINE.EXE ENGINE.EX_ 6 07/23/1997 11:39 440424
EPM.EXE EPM.EX_ 15 07/16/1998 13:18 19684
ERLOGGER.EXE ERLOGGER.EX_ 14 09/15/1998 13:45 34320
ERRLOG.DLL ERRLOG.DL_ 13 09/15/1998 13:45 72594
ES.KBL ES.KB_ 16 06/16/1998 17:15 904
ETKC603.DLL ETKC603.DL_ 11 12/16/1997 15:06 135759
ETKE603.DLL ETKE603.DL_ 5 05/07/1998 09:10 754050
FD16-700.ADD FD16-700.AD_ 15 02/26/1998 13:57 34152
FD7000EX.ADD FD7000EX.AD_ 15 02/09/1998 11:40 20758
FD8XX.ADD FD8XX.AD_ 15 02/09/1998 11:40 29954
FDISK.COM FDISK.CO_ 13 09/25/1998 12:03 113658
FDISKPM.DLL FDISKPM.DL_ 16 12/15/1997 16:17 7731
FDISKPM.EXE FDISKPM.EX_ 13 09/25/1998 12:04 63042
FFST.DLL FFST.DL_ 16 04/03/1997 19:03 11425
FFSTCONF.EXE FFSTCONF.EX_ 13 09/15/1998 13:52 68669
FFSTPCT.EXE FFSTPCT.EX_ 8 09/15/1998 13:52 69583
FI.KBL FI.KB_ 16 06/16/1998 17:15 924
FILT.DLL FILT.DL_ 15 09/29/1998 16:10 22888
FORMAT.COM FORMAT.CO_ 14 09/25/1998 11:59 69920
FR.KBL FR.KB_ 16 12/12/1997 22:59 934
FSFILTER.SYS FSFILTER.SY_ 16 10/23/1998 13:19 12988
GDI.EXE GDI.EX_ 9 09/16/1998 18:39 225744
GRADD.SYS GRADD.SY_ 16 10/16/1997 18:49 1195
GRE2VMAN.DLL GRE2VMAN.DL_ 15 08/20/1998 09:36 17899
HDMON.EXE HDMON.EX_ 12 07/23/1998 18:15 74487
HELPMGR.DLL HELPMGR.DL_ 8 09/25/1998 11:15 250115
HELPMSG.EXE HELPMSG.EX_ 15 09/25/1998 12:00 36256
FixPak Corrective Service levels and disk layouts 42
November 10, 1998 - Warp 4 FixPak XR_M009
HELV.FON HELV.FO_ 12 01/16/1998 17:56 264425
HELV.OFM HELV.OF_ 16 05/06/1998 16:34 4865
HELV.PFB HELV.PF_ 11 05/06/1998 16:34 101942
HELV.PFM HEL1.PF_ 16 05/06/1998 16:34 1096
HELVB.OFM HELVB.OF_ 16 05/06/1998 16:34 4857
HELVB.PFB HELVB.PF_ 11 05/06/1998 16:34 104404
HELVB.PFM HELV1.PF_ 16 05/06/1998 16:34 1089
HELVBI.OFM HELVBI.OF_ 16 05/06/1998 16:34 4859
HELVBI.PFB HELVBI.PF_ 11 05/06/1998 16:34 105074
HELVBI.PFM HELVB1.PF_ 16 05/06/1998 16:34 1087
HELVI.OFM HELVI.OF_ 16 05/06/1998 16:34 4844
HELVI.PFB HELVI.PF_ 11 05/06/1998 16:34 103996
HELVI.PFM HELV2.PF_ 16 05/06/1998 16:34 1079
HPFS.IFS HPFS.IF_ 12 09/24/1998 09:48 141378
IBM1004 IBM1004.___ 16 08/06/1998 13:37 3552
IBM1125 IBM1125.___ 16 08/06/1998 13:37 4320
IBM1131 IBM1131.___ 16 08/06/1998 13:37 4320
IBM1250 IBM1250.___ 16 08/06/1998 13:38 3552
IBM1251 IBM1251.___ 16 08/06/1998 13:38 3296
IBM1252 IBM1252.___ 16 08/06/1998 13:38 3552
IBM1253 IBM1253.___ 16 08/06/1998 13:38 3552
IBM1254 IBM1254.___ 16 08/06/1998 13:38 3552
IBM1255 IBM1255.___ 16 08/06/1998 13:38 3808
IBM1256 IBM1256.___ 16 08/06/1998 13:38 3808
IBM1257 IBM1257.___ 16 08/06/1998 13:38 3296
IBM16AFS.EXE IBM16AFS.EX_ 16 02/26/1998 13:59 3177
IBM1FLPY.ADD IBM1FLPY.AD_ 15 06/12/1998 18:21 35450
IBM2AMB1.SYS IBM2AMB1.SY_ 16 02/26/1998 14:20 12453
IBM2AST1.SYS IBM2AST1.SY_ 16 02/26/1998 14:19 10047
IBM2CAD1.SYS IBM2CAD1.SY_ 16 02/26/1998 14:22 12495
IBM2CMQ1.SYS IBM2CMQ1.SY_ 16 02/26/1998 14:20 10101
IBM2FLPY.ADD IBM2FLPY.AD_ 16 02/09/1998 11:36 14420
IBM2MAT1.SYS IBM2MAT1.SY_ 16 02/26/1998 14:21 10083
IBM2NCR1.SYS IBM2NCR1.SY_ 16 02/26/1998 14:21 10063
IBM2NEC1.SYS IBM2NEC1.SY_ 16 02/26/1998 14:20 10063
IBM2SCSI.ADD IBM2SCSI.AD_ 15 09/19/1998 13:02 33145
IBM2SS01.SYS IBM2SS01.SY_ 15 02/26/1998 15:05 27102
IBM2SS02.SYS IBM2SS02.SY_ 16 02/26/1998 15:05 22835
IBM2TOS1.SYS IBM2TOS1.SY_ 16 02/26/1998 14:19 10054
IBM2ZEN1.SYS IBM2ZEN1.SY_ 16 02/26/1998 14:19 10047
IBM2ZOS1.SYS IBM2ZOS1.SY_ 16 02/26/1998 14:21 10079
IBM4612.SYS IBM4612.SY_ 16 02/26/1998 14:22 10180
IBM850 IBM850.___ 16 08/06/1998 13:38 4320
IBM857 IBM857.___ 16 08/06/1998 13:38 4320
IBMATAPI.FLT IBMATAPI.FL_ 15 06/12/1998 20:37 30436
IBMIDECD.FLT IBMIDECD.FL_ 15 09/30/1998 21:14 24136
IBMKBD.SYS IBMKBD.SY_ 16 08/07/1998 14:22 7834
IBMOPTNS.DLL IBMOPTNS.DL_ 15 09/29/1998 14:49 18744
ICMEMCDD.SYS ICMEMCDD.SY_ 16 02/26/1998 14:24 13932
ICMEMFMT.EXE ICMEMFMT.EX_ 14 02/26/1998 14:26 44276
ICMEMMTD.SYS ICMEMMTD.SY_ 16 02/26/1998 14:25 7788
FixPak Corrective Service levels and disk layouts 43
November 10, 1998 - Warp 4 FixPak XR_M009
ICONEDIT.EXE ICONEDIT.EX_ 12 07/23/1998 16:08 109504
IFGDI2VM.DRV IFGDI2VM.DR_ 14 08/20/1998 09:35 91560
INSTALL.EXE INSTALL.EX_ 6 09/25/1998 11:23 384536
INST_DOS.EXE INST_DOS.EX_ 14 05/07/1998 11:23 36466
IOPROC.DLL IOPROC.DL_ 14 09/30/1998 10:10 37878
IPSRAID.ADD IPSRAID.AD_ 16 04/17/1998 12:04 19922
IS.KBL IS.KB_ 16 06/16/1998 17:15 924
IS458.KBL IS458.KB_ 16 06/16/1998 17:15 912
ISGDI2VM.DRV ISGDI2VM.DR_ 14 08/04/1998 17:47 90176
IT.KBL IT.KB_ 16 06/16/1998 17:15 860
IT142.KBL IT142.KB_ 16 06/16/1998 17:15 838
KBDBASE.SYS KBDBASE.SY_ 15 08/07/1998 14:26 31061
KERNEL.SDF KERNEL.SD_ 14 11/07/1996 21:11 467330
KERNELD.SDF KERNELD.SD_ 14 11/07/1996 21:12 468657
KEYBOARD.DCP KEYBOARD.DC_ 15 08/06/1998 18:28 303562
LIBCM.DLL LIBCM.DL_ 9 10/07/1997 00:18 210916
LIBCN.DLL LIBCN.DL_ 14 10/07/1997 00:18 57340
LIBCS.DLL LIBCS.DL_ 9 10/07/1997 00:18 192386
LIBUNI.DLL LIBUNI.DL_ 13 08/06/1998 13:37 80906
LMS206.ADD LMS206.AD_ 15 02/09/1998 11:46 38706
LOCALE.DLL LOCALE.DL_ 1 06/16/1998 18:15 83160
MIDI.SYS MIDI.SY_ 16 02/06/1998 12:48 21834
MIDIMCD.DLL MIDIMCD.DL_ 16 09/29/1998 16:02 532
MIGRATE.EXE MIGRATE.EX_ 11 09/25/1998 11:40 118313
MINSTALL.EXE MINSTALL.EX_ 10 09/29/1998 14:50 152580
MINXOBJ.DLL MINXOBJ.DL_ 14 09/24/1998 11:05 31778
MIRRORS.DLL MIRRORS.DL_ 6 09/19/1996 15:53 444744
MITFX001.ADD MITFX001.AD_ 16 02/09/1998 11:44 20492
MMODPTS.DLL MMODPTS.DL_ 9 09/29/1998 14:42 184020
MMPARTS.DLL MMPARTS.DL_ 2 09/29/1998 16:13 1532250
MMPM.DLL MMPM.DL_ 6 09/29/1998 16:22 431769
MMSOUND.DRV MMSOUND.DR_ 16 09/16/1998 19:18 3456
MOUSE.SYS MOUSE.SY_ 15 02/09/1998 11:46 19587
MPGIO.DLL MPGIO.DL_ 13 09/30/1998 10:11 59267
NAMEADD.EXE NAMEADD.EX_ 15 12/12/1997 23:24 23040
NAMECOPY.EXE NAMECOPY.EX_ 15 12/12/1997 23:24 23040
NAMECSSP.DLL NAMECSSP.DL_ 13 10/28/1997 13:00 61155
NAMEDEL.EXE NAMEDEL.EX_ 15 12/12/1997 23:24 23040
NAMEDSP.DLL NAMEDSP.DL_ 11 10/28/1997 13:00 123411
NAMEEXT.EXE NAMEEXT.EX_ 15 12/12/1997 23:24 23040
NAMEFT.DLL NAMEFT.DL_ 13 10/28/1997 13:00 66306
NAMEFW.DLL NAMEFW.DL_ 12 10/28/1997 13:00 72312
NAMEINFO.DLL NAMEINFO.DL_ 14 10/28/1997 13:00 47941
NAMEINI.DLL NAMEINI.DL_ 13 10/28/1997 13:00 59011
NAMEMOD.EXE NAMEMOD.EX_ 15 12/12/1997 23:24 23040
NAMEMOVE.EXE NAMEMOVE.EX_ 15 12/12/1997 23:24 23040
NAMEOSP.DLL NAMEOSP.DL_ 13 10/28/1997 13:00 52725
NL.KBL NL.KB_ 16 12/12/1997 22:59 938
NO.KBL NO.KB_ 16 06/16/1998 17:15 904
NWIAPI.DLL NWIAPI.DL_ 16 09/25/1998 12:02 14768
OREXUTIL.DLL ORXUTIL2.DL_ 14 12/16/1997 13:09 33405
FixPak Corrective Service levels and disk layouts 44
November 10, 1998 - Warp 4 FixPak XR_M009
OREXX.DLL OREXX2.DL_ 7 05/06/1998 16:31 442389
OS2ASPI.DMD OS2ASPI.DM_ 16 02/06/1998 12:13 11096
OS2CDROM.DMD OS2CDROM.DM_ 15 02/09/1998 11:43 27356
OS2CHAR.TDF OS2CHAR.TD_ 16 10/12/1998 13:59 13194
OS2DASD.DMD OS2DASD.DM_ 15 08/07/1998 12:19 40894
OS2DUMP OS2DUMP.___ 16 10/12/1998 13:53 17351
OS2K386.EXE OS2K386.EX_ 13 09/16/1998 18:42 80306
OS2KRNL OS2KRNL.___ 3 10/12/1998 13:54 601505
OS2KRNL.TDF OS2KRNL.TD_ 16 10/12/1998 13:54 14002
OS2KRNLD.SYM OS2KRNLD.SY_ 11 10/12/1998 13:56 182420
OS2KRNLR.SYM OS2KRNLR.SY_ 11 10/12/1998 13:54 159860
OS2LDR.MSG OS2LDR.MS_ 16 09/25/1998 11:46 8368
OS2MM.DLL OS2MM.DL_ 8 09/29/1998 14:50 219650
OS2NS.EXE OS2NS.EX_ 14 10/28/1997 14:18 44964
OS2SCSI.DMD OS2SCSI.DM_ 16 08/07/1998 12:20 11606
OS2UGL OS2UGL.___ 16 08/06/1998 13:39 11488
OS2UGLG OS2UGLG.___ 16 12/12/1997 22:59 8928
OSO001.MSG OSO001.MS_ 13 09/24/1998 09:00 178141
OSO001H.MSG OSO001H.MS_ 12 09/24/1998 09:01 241582
PARALLEL.PDR PARALLEL.PD_ 15 09/24/1998 11:27 15848
PCIBUS.SNP PCIBUS.SN_ 16 02/09/1998 12:17 2496
PCM2ATA.ADD PCM2ATA.AD_ 15 02/26/1998 15:00 27938
PCMCIA.SYS PCMCIA.SY_ 15 02/26/1998 14:58 48646
PCMCIA.TBL PCMCIA.TB_ 16 07/24/1998 12:34 5114
PICV.DLL PICV.DL_ 15 09/25/1998 11:14 26200
PICVIEW.DLL PICVIEW.DL_ 16 12/16/1997 17:02 10786
PMATM.DLL PMATM.DL_ 8 09/15/1998 09:12 223963
PMCHKDSK.DLL PMCHKDSK.DL_ 16 11/04/1996 16:44 4127
PMCHKDSK.EXE PMCHKDSK.EX_ 15 09/25/1998 12:04 28183
PMCLIP.DLL PMCLIP.DL_ 15 10/22/1997 23:19 21295
PMCTLS.DLL PMCTLS.DL_ 4 10/08/1998 12:12 584546
PMCTLS.SYM PMCTLS.SY_ 15 10/08/1998 12:12 44084
PMDDE.DLL PMDDE.DL_ 15 05/07/1998 11:26 28304
PMDDEML.DLL PMDDEML.DL_ 15 02/12/1998 10:12 27710
PMDF.EXE PMDF.EX_ 8 09/15/1998 13:53 232952
PMDRAG.DLL PMDRAG.DL_ 16 10/08/1998 12:10 1731
PMGPI.DLL PMGPI.DL_ 8 09/15/1998 12:12 228998
PMGPI.TDF PMGPI.TD_ 16 09/15/1998 12:12 10913
PMGRE.DLL PMGRE.DL_ 16 09/15/1998 12:08 2231
PMGRE.TDF PMGRE.TD_ 16 10/08/1998 12:14 1062
PMMERGE.DLL PMMERGE.DL_ 1 10/08/1998 12:14 1238971
PMMERGE.SYM PMMERGE.SY_ 12 10/08/1998 12:14 115172
PMMLE.DLL PMMLE.DL_ 16 09/15/1998 12:25 673
PMPIC.DLL PMPIC.DL_ 14 09/25/1998 11:14 47206
PMPRINT.QPR PMPRINT.QP_ 16 09/24/1998 11:06 11729
PMSDMRI.DLL PMSDMRI.DL_ 16 07/23/1998 17:08 13312
PMSEEK.EXE PMSEEK.EX_ 15 09/25/1998 12:05 31285
PMSHAPI.DLL PMSHAPI.DL_ 16 10/22/1997 22:53 4549
PMSHAPI.TDF PMSHAPI.TD_ 16 10/08/1998 12:14 6162
PMSPL.DLL PMSPL.DL_ 8 09/25/1998 12:01 272838
PMSPL.SYM PMSPL.SY_ 15 09/25/1998 12:01 32228
FixPak Corrective Service levels and disk layouts 45
November 10, 1998 - Warp 4 FixPak XR_M009
PMSPL.TDF PMSPL.TD_ 16 09/25/1998 12:01 4549
PMVDMP.DLL PMVDMP.DL_ 14 10/08/1998 12:25 42867
PMVIOP.DLL PMVIOP.DL_ 13 10/08/1998 12:25 58958
PMVIOP.SYM PMVIOP.SY_ 16 10/08/1998 12:25 6628
PMWIN.DLL PMWIN.DL_ 16 10/08/1998 12:05 11264
PMWIN.TDF PMWIN.TD_ 16 10/08/1998 12:14 8565
PMWIN32.SDF PMWIN32.SD_ 15 10/28/1997 18:56 299617
PMWINX.DLL PMWINX.DL_ 5 09/15/1998 12:43 530319
PMWP.DLL PMWP.DL_ 3 08/24/1998 14:21 925595
PMWP.SYM PMWP.SY_ 13 09/24/1998 11:01 100420
PMWPMRI.DLL PMWPMRI.DL_ 14 09/15/1998 14:52 54821
PNP.DLL PNP.DL_ 15 09/24/1998 11:15 28297
PNP.SYS PNP.SY_ 16 02/09/1998 12:18 2152
PO.KBL PO.KB_ 16 06/16/1998 17:15 910
POINTDD.SYS POINTDD.SY_ 16 02/09/1998 12:14 2823
PRINT01.SYS PRINT01.SY_ 16 01/06/1998 13:44 12590
PRINT02.SYS PRINT02.SY_ 16 12/05/1997 11:31 11766
PROGMAN.EXE PROGMAN.EX_ 13 09/16/1998 18:54 115328
PSSDMON.EXE PSSDMON.EX_ 15 05/07/1998 12:16 25981
PSTAT.EXE PSTAT.EX_ 16 09/25/1998 12:01 10339
QUECALLS.DLL QUECALLS.DL_ 16 09/25/1998 11:51 1024
QUECALLS.TDF QUECALLS.TD_ 16 10/12/1998 13:59 1299
RAS001.MSG RAS001.MS_ 3 07/23/1997 18:57 25739
README.CID README.CI_ 15 06/17/1997 10:14 60916
REGCONV.EXE REGCONV.EX_ 14 08/06/1998 13:43 39446
REGEDIT.HLP REGEDIT.HL_ 15 09/16/1998 20:50 22682
REGEDIT2.EXE REGEDIT2.EX_ 4 08/06/1998 13:45 950784
REGISTRY.DLL REGISTRY.DL_ 14 05/05/1998 00:46 81438
REGISTRY.MSG REGISTRY.MS_ 16 08/06/1998 13:45 629
REGISTRY.TDF REGISTRY.TD_ 16 05/05/1998 00:46 7616
REPLACE.EXE REPLACE.EX_ 15 01/15/1998 00:59 37483
RESERVE.SYS RESERVE.SY_ 16 02/09/1998 11:33 5704
RESOURCE.SYS RESOURCE.SY_ 14 08/07/1998 12:02 55372
RESTORE.EXE RESTORE.EX_ 15 09/25/1998 12:05 36256
REX.MSG REX.MS_ 16 09/19/1996 15:44 2865
REXX.DLL CREXX1.DL_ 9 12/16/1997 13:09 266047
REXX.DLL OREXX1.DL_ 7 05/06/1998 16:31 442389
REXX.IMG REXX.IM_ 12 05/06/1998 16:31 275440
REXXAPI.DLL REXXAPI.DL_ 15 07/23/1998 15:54 29603
REXXC.EXE REXXC.EX_ 16 03/31/1997 17:35 1980
REXXCRT.DLL REXXCRT.DL_ 13 03/31/1997 17:35 61195
REXXUTIL.DLL REXXUTIL.DL_ 6 12/16/1997 13:09 48397
REXXUTIL.DLL ORXUTIL1.DL_ 14 12/16/1997 13:09 33405
RINSTPRN.EXE RINSTPRN.EX_ 9 07/23/1998 19:43 194586
RSPDDI.EXE RSPDDI.EX_ 15 09/25/1998 11:35 22073
RSPDSPI.EXE RSPDSPI.EX_ 12 09/25/1998 11:41 95352
RSPINST.EXE RSPINST.EX_ 7 09/25/1998 11:32 428960
RSRV.EXE RSRV.EX_ 12 10/28/1997 14:19 77955
RU.KBL RU.KB_ 16 12/12/1997 22:59 1128
SBCD2.ADD SBCD2.AD_ 13 02/09/1998 11:44 18820
SCENTER.DLL SCENTER.DL_ 7 09/24/1998 11:28 291373
FixPak Corrective Service levels and disk layouts 46
November 10, 1998 - Warp 4 FixPak XR_M009
SD.KBL SD.KB_ 16 12/12/1997 22:59 1020
SEAMLESS.DLL SEAMLESS.DL_ 15 10/08/1998 12:25 49679
SECUTIL.DLL SECUTIL.DL_ 15 05/07/1998 12:15 21468
SEINST.EXE SEINST.EX_ 14 01/17/1998 04:20 37441
SEMAINT.EXE SEMAINT.EX_ 14 01/17/1998 04:20 67376
SERIAL.PDR SERIAL.PD_ 15 09/24/1998 11:05 19060
SESAPI.DLL SESAPI.DL_ 15 09/24/1998 10:09 24283
SESDD32.SYS SESDD32.SY_ 13 09/15/1998 13:36 118832
SESMGR.DLL SESMGR.DL_ 16 09/25/1998 11:49 1536
SESMGR.TDF SESMGR.TD_ 16 10/12/1998 13:59 1643
SETBOOT.EXE SETBOOT.EX_ 2 09/25/1998 12:03 17196
SETDEFV.CMD SETDEFV.CM_ 16 06/23/1998 16:25 1652
SF.KBL SF.KB_ 16 12/12/1997 22:59 1020
SOFTDRAW.DLL SOFTDRAW.DL_ 7 09/16/1998 18:23 400939
SOM.DLL SOM.DL_ 12 08/13/1996 09:29 88763
SONY31A.ADD SONY31A.AD_ 15 02/09/1998 11:45 32738
SPCHOBJ.DLL SPCHOBJ.DL_ 11 12/21/1997 01:27 132899
SPL1B.DLL SPL1B.DL_ 16 09/25/1998 12:01 5077
SS2PCIC1.SYS SS2PCIC1.SY_ 16 02/26/1998 15:04 19087
SS2TCIC1.SYS SS2TCIC1.SY_ 16 02/26/1998 15:04 22824
SSM.DLL SSM.DL_ 16 09/29/1998 16:01 1556
SSMDD.SYS SSMDD.SY_ 9 09/29/1998 16:09 36813
SV.KBL SV.KB_ 16 06/16/1998 17:15 930
SVMC.DLL SVMC.DL_ 12 09/30/1998 10:08 98389
SVSH.DLL SVSH.DL_ 15 09/30/1998 10:09 23452
SW.DLL SW.DL_ 13 09/30/1998 10:08 66499
SWITCHRX.CMD SWITCHRX.CM_ 16 05/06/1998 16:31 7928
SYMB.PFM SYM1.PF_ 16 10/10/1997 01:03 679
SYSINST2.EXE SYSINST2.EX_ 11 09/25/1998 11:27 184560
SYSINSTX.COM SYSINSTX.CO_ 15 09/25/1998 12:01 39472
SYSLEVEL.EXE SYSLEVEL.EX_ 14 01/17/1998 04:18 42848
SYSLEVEL.FPK SYSLEVEL.FP_ 16 09/21/1998 16:19 165
SYSLOGPM.EXE SYSLOGPM.EX_ 10 09/15/1998 13:45 138955
SYSMONO.FON SYSMONO.FO_ 15 05/07/1998 11:29 46255
SYSMONOI.FON SYSMONOI.FO_ 15 01/16/1998 17:54 42146
SYSTEM.TDF SYSTEM.TD_ 16 09/25/1998 12:06 18358
SYSTEM.TFF SYSTEM.TF_ 16 09/25/1998 12:06 45067
TEDIT.EXE TEDIT.EX_ 16 11/04/1996 16:50 9390
TEDIT.HLP TEDIT.HL_ 16 11/04/1996 14:56 14596
TESTCFG.SYS TESTCFG.SY_ 16 02/09/1998 12:15 9808
TIMES.FON TIMES.FO_ 12 01/16/1998 17:57 257547
TNR.OFM TNR.OF_ 16 02/12/1998 10:05 4882
TNR.PFB TNR.PF_ 10 02/12/1998 10:05 119332
TNR.PFM TN1.PF_ 16 02/12/1998 10:05 1103
TNRB.OFM TNRB.OF_ 16 02/12/1998 10:05 4898
TNRB.PFB TNRB.PF_ 10 02/12/1998 10:05 123083
TNRB.PFM TNR1.PF_ 16 02/12/1998 10:05 1112
TNRBI.OFM TNRBI.OF_ 16 02/12/1998 10:05 4912
TNRBI.PFB TNRBI.PF_ 10 02/12/1998 10:05 134003
TNRBI.PFM TNRB1.PF_ 16 02/12/1998 10:05 1118
TNRI.OFM TNRI.OF_ 16 02/12/1998 10:05 4903
FixPak Corrective Service levels and disk layouts 47
November 10, 1998 - Warp 4 FixPak XR_M009
TNRI.PFB TNRI.PF_ 10 02/12/1998 10:05 131366
TNRI.PFM TNR2.PF_ 16 02/12/1998 10:05 1114
TR.KBL TR.KB_ 16 12/12/1997 22:59 946
TR440.KBL TR440.KB_ 16 06/16/1998 17:15 1026
TRACEDLL.DLL TRACEDLL.DL_ 14 07/23/1998 18:11 44555
TRACEFMT.EXE TRACEFMT.EX_ 11 07/23/1998 18:12 127972
TRAPDUMP.EXE TRAPDUMP.EX_ 4 01/15/1998 00:42 14928
TRC0001.TFF TRC0001.TF_ 16 05/05/1998 00:46 17414
TRC0003.TFF TRC0003.TF_ 16 12/12/1996 17:56 1503
TRC0004.TFF TRC0004.TF_ 16 01/15/1998 00:23 4754
TRC0005.TFF TRC0005.TF_ 16 10/12/1998 13:56 30602
TRC0006.TFF TRC0006.TF_ 16 12/12/1996 17:19 12356
TRC0007.TFF TRC0007.TF_ 16 02/09/1998 11:35 1394
TRC0008.TFF TRC0008.TF_ 16 02/06/1998 11:51 544
TRC0010.TFF TRC0010.TF_ 16 10/12/1998 13:59 3638
TRC0016.TFF TRC0016.TF_ 16 10/12/1998 13:59 1673
TRC0017.TFF TRC0017.TF_ 16 10/12/1998 13:59 4799
TRC0018.TFF TRC0018.TF_ 16 10/12/1998 13:59 37028
TRC006D.TFF TRC006D.TF_ 16 06/23/1998 19:40 24181
TRC00C0.TFF TRC00C0.TF_ 16 10/08/1998 12:14 13739
TRC00C2.TFF TRC00C2.TF_ 16 10/08/1998 12:14 21391
TRC00C3.TFF TRC00C3.TF_ 16 10/08/1998 12:14 3984
TRC00C4.TFF TRC00C4.TF_ 16 09/25/1998 11:14 242
TRC00C5.TFF TRC00C5.TF_ 16 09/15/1998 12:12 26439
TRC00C6.TFF TRC00C6.TF_ 16 09/25/1998 12:01 6331
TRCUST.EXE TRCUST.EX_ 12 05/12/1998 14:12 96413
TRUETYPE.DLL TRUETYPE.DL_ 10 09/15/1998 09:13 128485
UA.KBL UA.KB_ 16 01/22/1998 10:14 1460
UCDFS.DLL UCDFS.DL_ 16 10/21/1996 09:24 13264
UCONV.DLL UCONV.DL_ 15 08/06/1998 13:37 23841
UHPFS.DLL UHPFS.DL_ 13 09/24/1998 09:50 105488
UK.KBL UK.KB_ 16 12/12/1997 22:59 800
UK168.KBL UK168.KB_ 16 12/12/1997 22:59 834
ULSACT01.MSG ULSACT01.MS_ 7 10/07/1997 15:24 907
ULSCAU01.MSG ULSCAU01.MS_ 4 10/07/1997 15:24 899
ULSDET01.MSG ULSDET01.MS_ 1 10/07/1997 15:24 903
ULSERR01.MSG ULSERR01.MS_ 16 10/07/1997 15:24 1967
UNINSTAL.EXE UNINSTAL.EX_ 12 09/25/1998 11:39 99641
UNPACK2.EXE UNPACK2.EX_ 13 09/25/1998 11:46 79792
USER.EXE USER.EX_ 3 09/16/1998 19:12 280928
USINTER.KBL USINTER.KB_ 16 12/12/1997 22:59 1016
VBIOS.SYS VBIOS.SY_ 16 09/24/1998 09:50 8816
VCDROM.SYS VCDROM.SY_ 16 02/09/1998 12:22 6880
VCMOS.SYS VCMOS.SY_ 16 09/24/1998 09:50 2272
VCOM.SYS VCOM.SY_ 16 02/06/1998 13:02 12384
VDMA.SYS VDMAPS2.SY_ 16 09/24/1998 09:50 14281
VDMA.SYS VDMAAT.SY_ 16 09/24/1998 09:50 11417
VDPMI.SYS VDPMI.SY_ 15 09/24/1998 09:51 30624
VDPX.SYS VDPX.SY_ 15 09/24/1998 09:51 26112
VDSK.SYS VDSK.SY_ 16 02/06/1998 13:02 10384
VGA.DSP VGA.DS_ 16 05/05/1998 01:48 3094
FixPak Corrective Service levels and disk layouts 48
November 10, 1998 - Warp 4 FixPak XR_M009
VIEW.EXE VIEW.EX_ 15 09/25/1998 11:15 26828
VIOCALLS.DLL VIOCALLS.DL_ 16 09/25/1998 11:16 2048
VIOTBL.DCP VIOTBL.DC_ 15 08/06/1998 18:29 214980
VIOTBL.ISO VIOTBL.IS_ 14 08/06/1998 18:28 219849
VKBD.SYS VKBD.SY_ 15 02/26/1998 14:39 25641
VLPT.SYS VLPT.SY_ 16 02/06/1998 13:03 10113
VMAN.DLL VMAN.DL_ 15 08/20/1998 09:35 26093
VMANWIN.SYS VMANWIN.SY_ 16 01/13/1998 18:27 2880
VMOUSE.SYS VMOUSE.SY_ 16 02/06/1998 13:03 18704
VPIC.SYS VPIC.SY_ 16 09/24/1998 09:51 9942
VPICPARM.SYS VPICPARM.SY_ 15 09/24/1998 09:51 736
VTIMER.SYS VTIMER.SY_ 16 09/24/1998 09:51 9936
VW32S.SYS VW32S.SY_ 16 09/24/1998 09:52 18320
VWIN.SYS VWIN.SY_ 15 09/24/1998 09:51 26896
WCFGMRI.DLL WCFGMRI.DL_ 16 07/23/1998 19:04 2596
WD24B.DSP WD24B.DS_ 16 04/03/1997 13:55 12050
WINCFG.DLL WINCFG.DL_ 16 09/24/1998 11:05 12839
WINFILE.EXE WINFILE.EX_ 12 09/16/1998 18:55 146960
WINSCLIP.DLL WINSCLIP.DL_ 16 09/16/1998 18:51 14848
WINSDDE.DLL WINSDDE.DL_ 10 09/16/1998 18:51 18432
WINSHELD.EXE WINSHELD.EX_ 16 09/16/1998 18:51 22016
WINSMSG.DLL WINSMSG.DL_ 16 09/16/1998 18:50 27929
WPCLS.IMP WPCLS.IM_ 16 03/31/1997 17:35 8661
WPCONFIG.DLL WPCONFIG.DL_ 8 09/24/1998 11:05 246054
WPCONMRI.DLL WPCONMRI.DL_ 15 07/23/1998 19:04 27694
WPHELP.HLP WPHELP.HL_ 5 10/29/1997 16:28 841366
WPINET.DLL WPINET.DL_ 12 09/24/1998 11:26 115384
WPMSG.HLP WPMSG.HL_ 14 12/16/1997 15:18 50198
WPPRINT.DLL WPPRINT.DL_ 2 09/25/1998 12:00 363930
WPPRINT.HLP WPPRINT.HL_ 14 10/10/1997 05:48 71408
WPPRTMRI.DLL WPPRTMRI.DL_ 14 09/25/1998 12:00 66681
WPREXX.IMP WPREXX.IM_ 16 03/31/1997 17:35 6313
WPSINIT.WPS WPSINIT.WP_ 16 03/31/1997 17:35 15877
WPSINST.CMD WPSINST.CM_ 11 05/06/1998 16:31 2813
WW.EXE WW.EX_ 14 04/01/1997 15:37 8305
WWDLL.DLL WWDLL.DL_ 4 12/21/1997 01:29 276981
WWHOOK.DLL WWHOOK.DL_ 15 12/21/1997 01:29 27230
XCOPY.EXE XCOPY.EX_ 14 09/25/1998 12:01 51152
*************************************************************
Product location on CSD: L:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.00
New CSD Level: XR_M009_ (Country = Generic)
Pre-requisite CSD Level: XR_4000_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
_____________________________________________________________
Default directories:
FixPak Corrective Service levels and disk layouts 49
November 10, 1998 - Warp 4 FixPak XR_M009
..\..\
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- ---------- ----- -------
OS2LDR OS2LDR.___ 16 07/28/1998 17:25 33280
*************************************************************
Product location on CSD: L:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 4.01
New CSD Level: XR_M009_ (Country = Generic)
Pre-requisite CSD Level: XR_4010_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\..\
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in CSD for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- ---------- ----- -------
APPDBUTL.DLL APPDBUTL.DL_ 16 09/24/1998 12:44 25013
APPSTART.EXE APPSTART.EX_ 16 09/24/1998 12:45 33864
NCAPPUTL.EXE NCAPPUTL.EX_ 16 05/11/1998 10:54 12612
OS2LDR OS2LDR.___ 16 07/28/1998 17:25 33280
PMLOGON.EXE PMLOGON.EX_ 16 09/24/1998 12:49 40107
FixPak Corrective Service levels and disk layouts 50
November 10, 1998 - Warp 4 FixPak XR_M009
PRNCFG.DLL PRNCFG.DL_ 16 09/24/1998 12:51 58258
TDESK.DLL TDESK.DL_ 16 09/24/1998 12:48 3769
TLOGOFF.EXE TLOGOFF.EX_ 16 09/24/1998 12:48 9577
TOBJECT.DLL TOBJECT.DL_ 16 09/24/1998 12:48 4876
TSHUTDWN.EXE TSHUTDWN.EX_ 16 09/24/1998 12:48 8611
FixPak Corrective Service levels and disk layouts 51
November 10, 1998 - Warp 4 FixPak XR_M009
11.0 SPACE UTILIZATION
The FixPak installation process requires free space on the following
drives:
Space needed Drive
Up to 2MB C:
Up to 2MB Boot drive (4MB if boot is C:)
Up to 22MB Drive with most free space, holds deferred files if
A:SERVICE method used.
Up to 34MB FixPak Archive/Backup for product with CSD level of
XR_4000
Up to 34MB FixPak Archive/Backup for product with CSD level of
XR_4010
Note: The lines labeled "FixPak Archive/Backup for product with CSD level
of" will be on the drive you specify and will occupy up to the size
indicated for the Archive and for the Backup directories. If, for
example, the indicated size is 30MB then the space actually occupied on
the drive can be up to 60MB.
11.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE
Warning: Make sure you read and understand the following before removing
the Archive and Backup files and directories.
You can recover the space used for FixPak Archive and Backup files as
long as you understand that doing this prevents you from being able to
backout to the previous Backup or Archive level. If it becomes necessary
at a later time to backout a FixPak, the only way you can do this is to
reinstall Warp.
Do the following to delete the FixPak Backup and Archive files and remove
the files used by CSF to keep track of what service has been applied to
your system.
Space Utilization 52
November 10, 1998 - Warp 4 FixPak XR_M009
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.
11.0.2 TRADEMARKS
The following terms are trademarks of the International Business Machines
Corporation in the United States or other countries or both:
■ IBM
■ OS/2
■ WorkSpace On-Demand
Other company, product, and service names may be trademarks or service
marks of others.
Space Utilization 53