home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Spezial
/
SPEZIAL2_97.zip
/
SPEZIAL2_97.iso
/
UPDATE
/
WARP4FXD
/
readme.1st
< prev
next >
Wrap
Text File
|
1997-10-07
|
60KB
|
1,872 lines
< Installation instructions for Warp 4 FixPak XRGM003
August 29, 1997
Build level 9.027
This FixPak applies to:
CSD Level: XRG4000
Component ID: 5639A6100
Version: 4.00
Type: 0C
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1994, 1996.
All rights Reserved.
August 29, 1997 - Warp 4 FixPak XRGM003
August 29, 1997 - Warp 4 FixPak XRGM003
CONTENTS
FixPak Controlled distribution ................................... 1
Terms and Conditions ............................................. 2
Installation Notes ............................................... 3
No reboot after Locked File Device Driver completes ............ 3
Popups for UNPACK2.EXE ......................................... 3
Multimedia no longer selectable ................................ 3
If you have installed FixPak XRGM000 ........................... 3
If you have installed controlled FixPak XRGM001 ................ 4
APAR JR09494 (trap exiting WINOS2 with MWAVE audio) ............ 5
MMPARTS.DLL/USER.EXE popup during install ...................... 5
CSF0212 Archive path is shared between mismatched ... ......... 5
CSF0214 Error opening or creating archive file. ............... 5
CSF0208 No products were found on the target system to service . 5
Printer installation process change ............................ 5
Configuration Installation Distribution ( CID ) ................ 6
Do not use your system once the FixPak installation is started . 6
Post Installation Notes .......................................... 7
SYS3170 installing Lotus SmartSuite 96 ......................... 7
Intermittent pause with IBM Thinkpad 760E/ED/ELD/EL ............ 7
New Function ..................................................... 8
New (improved) CHKDSK ............................................ 8
Using the new CHKDSK ........................................... 8
CHKDSK log formatter .......................................... 10
Automated Trap Screen Logging ................................. 11
SUPPRESSPOPUPS ................................................ 11
TRAPLOG ....................................................... 11
TRAPDUMP ...................................................... 12
SYSDUMP ....................................................... 12
New README.DBG .................................................. 13
Corrective Service Facility Installation Diskettes .............. 14
Required CSF level ............................................ 14
Where you can find CSF ........................................ 14
Creating FixPak diskettes ..................................... 15
Residual FixPak files from OS/2 2.11 or Warp 3 .................. 15
Read-Only files ................................................. 16
SYSLEVEL file locations ......................................... 16
Relocated OS/2 file support ..................................... 17
Installation Process ............................................ 19
Before installation ............................................. 19
Method 1: Install from booted OS/2 partition. .................. 19
Method 2: Boot from Corrective Service Disk 1. ................. 21
Additional Corrective Service Facility information .............. 21
Contents ii
August 29, 1997 - Warp 4 FixPak XRGM003
CSD level of SYSLEVEL.OS2 ....................................... 22
FixPak Corrective Service levels and disk layouts ............... 23
Space Utilization ............................................... 30
Recovering FixPak ARCHIVE and BACKUP space .................... 30
Contents iii
August 29, 1997 - Warp 4 FixPak XRGM003
FIXPAK CONTROLLED DISTRIBUTION
This FixPak is not to be posted to public areas of BBS systems or the
Internet. It is intended solely for OS/2 customers who have reported a
problem to IBM that has been identifed as being fixed in this FixPak.
If you downloaded this FixPak from a public BBS or public site on the
Internet be aware that it was not placed there by IBM and that
installation of this FixPak may leave you with an unsupported OS/2
system.
FixPak Controlled distribution 1
August 29, 1997 - Warp 4 FixPak XRGM003
TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XRGM003 for 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 XRGM003 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 2
August 29, 1997 - Warp 4 FixPak XRGM003
INSTALLATION NOTES
NO REBOOT AFTER LOCKED FILE DEVICE DRIVER COMPLETES
If you apply or backout (remove) this Fixpak using the A:SERVICE
method, the automatic reboot after the Locked File Device Driver has
completed may not occur. Wait a short time (30 seconds or so) then
press Ctrl+Alt+Del to force the reboot.
POPUPS FOR UNPACK2.EXE
If you apply this Fixpak using the A:SERVICE method, you may get two
popup messages for UNPACK2.EXE. In both cases, press the "OK" button
and UNPACK2.EXE will be correctly updated.
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.
IF YOU HAVE INSTALLED FIXPAK XRGM000
If you have installed Warp 4 FixPak XRGM000, three files were updated
that are not in FixPak XRGM002 and need to be backed out to the Warp 4
GA level. They are:
12-13-96 10:35a 10120 0 \MMOS2\MPPM.EXE
12-05-96 5:12p 34645 0 \OS2\BOOT\KBDBASE.SYS
12-05-96 5:39p 53161 0 \OS2\MDOS\VKBD.SYS
The uplevel MPPM.EXE causes the Media Player to fail.
The uplevel KBDBASE.SYS results in a local TELNET session not having a
keyboard unless the TELNET session on the target system has the focus.
The uplevel VKBD.SYS causes NumLock to come without pressing the
NumLock key.
To fix these problems you can either back out the entire FixPak (VIEW
the README.INF file on the first FixPak disk for instructions) or back
out just these three files as follows:
Installation Notes 3
August 29, 1997 - Warp 4 FixPak XRGM003
1. Rename x:\MMOS2\MPPM.EXE to MPPM.000
2. Rename x:\OS2\BOOT\KBDBASE.SYS to KBDBASE.000
3. Rename x:\OS2\MDOS\VKBD.SYS to VKBD.000
4. Change to your FixPak Archive directory.
5. Use the UNPACK command to restore the saved files to your Warp 4
boot drive
UNPACK MPPM.EX_ x:\MMOS2
UNPACK KBDBASE.SY_ x:\OS2\BOOT
UNPACK VKBD.SY_ x:\OS2\MDOS
6. Shutdown and reboot your system.
Note: x: is your Warp 4 boot drive.
IF YOU HAVE INSTALLED CONTROLLED FIXPAK XRGM001
If you have installed the controlled version of Warp 4 FixPak XRGM001,
one file was updated that is not in the public FixPak XRGM002 and
needs to be backed out to the Warp 4 GA level. It is:
12-05-96 5:39p 53161 0 \OS2\MDOS\VKBD.SYS
The uplevel VKBD.SYS causes NumLock to come without pressing the
NumLock key.
To fix this problem you can either back out the entire FixPak (VIEW
the README.INF file on the first FixPak disk for instructions) or back
out just this file as follows:
1. Rename x:\OS2\MDOS\VKBD.SYS to VKBD.000
2. Change to your FixPak Archive directory.
3. Use the UNPACK command to restore the saved file to your Warp 4
boot drive
UNPACK VKBD.SY_ x:\OS2\MDOS
4. Shutdown and reboot your system.
Note: x: is your Warp 4 boot drive.
Installation Notes 4
August 29, 1997 - Warp 4 FixPak XRGM003
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.
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.
*======================================================================
CSF0212 ARCHIVE PATH IS SHARED BETWEEN MISMATCHED ...
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.
CSF0214 ERROR OPENING OR CREATING ARCHIVE FILE.
Also CSF0215, CSF0216, CSF0217 and CSF0249.
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.
CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET SYSTEM TO SERVICE
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.
PRINTER INSTALLATION PROCESS CHANGE
If you install a new printer by clicking MB2 on the Printer icon in
the templates folder then clicking on Install, the printer object will
now be created in the Printer folder, not on the Desktop.
Installation Notes 5
August 29, 1997 - Warp 4 FixPak XRGM003
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.
DO NOT USE YOUR SYSTEM ONCE THE FIXPAK INSTALLATION IS STARTED
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.
Installation Notes 6
August 29, 1997 - Warp 4 FixPak XRGM003
POST INSTALLATION NOTES
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.
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
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
Post Installation Notes 7
August 29, 1997 - Warp 4 FixPak XRGM003
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.
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.
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
New Function 8
August 29, 1997 - Warp 4 FixPak XRGM003
completing the boot process
Ä Errors may occur later in the boot process.
Hence, the chkdsk.sys device driver is smart enough to recognize when
CHKDSK has used this reserved memory and will reboot the system
automatically after all HPFS drives have been checked. Since the
drives were checked before the reboot, CHKDSK will not have to check
them after the reboot and the system will boot normally.
Note: For those wishing to run unattended: In order to prevent the
system from pausing between autocheck and the reboot, we recommend
that the statement PAUSEONERROR=NO be in the CONFIG.SYS.
When you don't have enough physical (real) memory to autocheck large
drives, you must use virtual memory from SWAPPER.DAT. The technique
is to check the large drives between the time OS/2 starts and PM
begins. To start OS/2, the swap file and device drivers must reside
on an unaffected drive. The drives to be checked must not appear in
the autocheck list in the IFS statement for HPFS (or HPFS386).
This technique involves the following steps:
1. Remove the drive letter of the affected drive(s) from the
autocheck list in the IFS statement for HPFS (or HPFS386).
2. If you are using HPFS, add /QUIET to the IFS statement for HPFS.
3. If you are using HPFS386, add POPUPERRORRS=NO to the HPFS386.INI
file.
4. Add a CALL statement to your config.sys. This CALL statement will
call CHKDSK.COM, and will tell it what drive to check. This CALL
statement must appear after the LIBPATH=, SET PATH=, and SET
DPATH= statements, but before any other CALL statements in your
CONFIG.SYS file.
Calls to CHKDSK in STARTUP.CMD are not necessary, when using this
method or the base device driver (chkdsk.sys) method.
Example: The computer boots from drive C (moderate HPFS or FAT sized
drive). Drive D (large HPFS) requires more RAM to check than
installed in the machine.
New Function 9
August 29, 1997 - Warp 4 FixPak XRGM003
Original IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:CD
New IFS statement:
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AUTOCHECK:C /QUIET
The CALL statement to use is:
CALL=C:\OS2\CHKDSK.COM D: /C
The /C option tells CHKDSK to check the drive only if it is "dirty"
and it needs checking.
If you need to boot from diskettes to check an HPFS drive, you must
have the following files on the diskette you wish to run CHKDSK from:
CHKDSK.COM
CHKDSK32.DLL
UHPFS.DLL
The BOOTDISK.EXE program has been updated to create new utility
diskettes with the proper files.
CHKDSK LOG FORMATTER
CHKDSK creates a binary service log file (chkdsk.log) on the root of
the drive being checked during autocheck or whenever the /F option is
invoked. The previous log file is saved as chkdsk.old. A formatter
for this log file can be found at:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/chklogpk.exe
This is a self extracting ZIP file. Place it in a directory in your
path and enter CHKLOGPK. This will create the following files:
message.txt
msghdr.txt
pmchklog.exe
range.txt
readme
They should all have a date of 05/14/97 or later (May 14, 1997).
New Function 10
August 29, 1997 - Warp 4 FixPak XRGM003
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.
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).
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".
TRAPLOG
The TRAPLOG command allows dynamic control of trap information
logging.
The command syntax is:
TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]
where:
Ä x: specifies that trap information is to be logged in
x:\POPUPLOG.OS2, x: being any partition drive letter.
Ä NOLOG disables logging of trap information.
Ä POPUPS enables the trap information pop-up message (SYS3175).
Ä NOPOPUPS disables the trap information pop-up message.
New Function 11
August 29, 1997 - Warp 4 FixPak XRGM003
TRAPDUMP
The TRAPDUMP command allows the conditions under which a trap will
initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak
29, the System Dump setting could only be manipulated from CONFIG.SYS
by use of the TRAPDUMP statement.
Use of this command should be made under the direction of service
personnel.
Warning: The initiation of a System Dump causes an immediate
termination of the system without any shutdown. No file system
shutdown is performed. The system behaves as if a fatal crash has
occurred, thus under rare circumstances data can be lost.
The command syntax is:
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]
where:
Ä ON enables all application and system traps to initiate a System
Dump.
Ä OFF disables automatic dump initiation.
Ä R0 enables only Ring 0 traps to initiate a System Dump.
Ä x: specifies the Dump Partition.
Ä NOCHECK overrides the system level check for WARP 4.0, since use
of this command on a system level prior to FixPak 29 is equivalent
to the SYSDUMP command.
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]
New Function 12
August 29, 1997 - Warp 4 FixPak XRGM003
where:
Ä NOPROMPT allows the Dump to proceed without the prompt and
response to message:
"Do you want to force a system dump? (Y/N)"
NEW README.DBG
This FixPak introduces a new README.DBG file which contains
information on debugging OS/2 Warp 3.0 or 4.0.
New Function 13
August 29, 1997 - Warp 4 FixPak XRGM003
CORRECTIVE SERVICE FACILITY INSTALLATION DISKETTES
REQUIRED CSF LEVEL
You must use release level F.133 or later of the OS/2 Corrective
Service Facility Diskettes to install this FixPak. Check the
BUILD.LVL file on the first CSF disk for the level you are using. If
it does not have a BUILD.LVL file then it is older than the F.133
level and should not be used.
WHERE YOU CAN FIND CSF
The Corrective Service Facility disk images are available in the
WKICKR.ZIP file from many places, including, but not limited to, the
following:
Source How to access
CompuServe Subscribers can download from the OS/2 Support Forum
(GO OS2SUPPO), in Library 23, IBM FILE.
IBM OS/2 BBS Subscribers can download from the Software Download
Library. U.S. customers who are not subscribers can
call 1-800-547-1283 for information on how to
subscribe.
Internet(FTP) Anonymous FTP to ftp.software.ibm.com (IP Address
198.17.57.66) in the "/ps/products/os2/fixes"
directory.
Internet(WWW) Point your Web Browser at
ftp://service.boulder.ibm.com/ps/products/os2/fixes
PCC BBS Customers can call the IBM Personal Computer Company
BBS In Raleigh NC, and download from the public area.
You can access this BBS at 1-919-517-0001.
AOL America OnLine subscribers can download from the OS/2
Area.
Follow the instructions contained in the WKICKR.TXT file to create the
Corrective Service Facility disks. Label them (write) as:
Corrective Service Facility Installation Diskettes 14
August 29, 1997 - Warp 4 FixPak XRGM003
CSF DISK Diskette 1
(SP DISK 1)
CSF DISK Diskette 2
(SP DISK 2)
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 XRGM003.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XRGM003
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through
26.
Examples:
XRGM003.ADK = 10
XRGM003.FDK = 15
XRGM003.LDK = 21
etc.
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
You will have files and directories left on your harddisk that will
cause problems when installing a Warp 4 FixPak.
Corrective Service Facility Installation Diskettes 15
August 29, 1997 - Warp 4 FixPak XRGM003
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.
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.
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:
For \OS2\INSTALL\SYSLEVEL.OS2
Corrective Service Facility Installation Diskettes 16
August 29, 1997 - Warp 4 FixPak XRGM003
..\..\ 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 under the root directory.
..\..\VT\* all files in all subdirectories under the VT directory.
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:
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.
Corrective Service Facility Installation Diskettes 17
August 29, 1997 - Warp 4 FixPak XRGM003
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 Installation Diskettes 18
August 29, 1997 - Warp 4 FixPak XRGM003
INSTALLATION PROCESS
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.
Reboot your system then shutdown all running applications.
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 XRGM003 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
Installation Process 19
August 29, 1997 - Warp 4 FixPak XRGM003
of replaced files will be stored (for example, D:\ARCHIVE).
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
Installation Process 20
August 29, 1997 - Warp 4 FixPak XRGM003
The system will do one automatic reboot after the Locked File
Device Driver has completed.
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 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.FIL on CSF Disk 1 to control some of
the actions taken by FSERVICE.EXE while applying a FixPak. Use the
VIEW command to look at the file README.INF on the first CSF disk for
more information on this.
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.
Installation Process 21
August 29, 1997 - Warp 4 FixPak XRGM003
CSD LEVEL OF SYSLEVEL.OS2
The Current CSD level for the "IBM OS/2 Base Operating System" will
not be changed by installation of this FixPak even though the
SERVICE.LOG file indicates it will. This FixPak is not a Service Level
change. It upgrades the existing service level (XRG4000); therefore
the SYSLEVEL is not changed. All fix information is recorded in the
SERVICE.LOG file.
Look at the file
\OS2\INSTALL\SERVICE.LOG
on your boot drive for information relating to the installation of
this (or any) FixPak on your system. To see the current level and
other related information use the SYSLEVEL command.
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.025
The first page of this document has a line that looks like:
Build Level: n.nnn
That is the number you should see for this FixPak when you issue the
VER /R command.
CSD level of SYSLEVEL.OS2 22
August 29, 1997 - Warp 4 FixPak XRGM003
FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 9.027
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Basisbetriebssystem"
Standard Edition 4.00
Fixpak name: XRGM003_ (Country = Germany)
Pre-requisite CSD Level: XRG4000_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\..\
..\*
..\..\vt
..\..\vt\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
AHA152X.ADD AHA152X.AD_ 11 06/27/97 13:52 44208
AHA164X.ADD AHA164X.AD_ 11 06/27/97 13:50 20022
AHA6360.SNP AHA6360.SN_ 10 06/26/97 15:27 27395
AIC7770.ADD AIC7770.AD_ 10 06/27/97 13:52 42558
AIC7870.ADD AIC7870.AD_ 10 04/10/97 16:52 39870
AIC7870.SNP AIC7870.SN_ 11 06/26/97 15:28 9104
APM.SYS APM.SY_ 11 06/26/97 14:57 9922
APMDAEMN.EXE APMDAEMN.EX_ 12 06/26/97 15:52 2733
BLDLEVEL.EXE BLDLEVEL.EX_ 11 07/30/97 12:11 21523
BOOTDISK.EXE BOOTDISK.EX_ 10 07/30/97 11:15 54026
BTSCSI.ADD BTSCSI.AD_ 11 06/26/97 15:03 26569
BVSCALLS.DLL BVSCALLS.DL_ 12 11/07/96 20:54 512
CDFS.IFS CDFS.IF_ 11 07/30/97 10:01 45610
CDROM.TBL CDROM.TB_ 12 11/12/96 13:38 4365
CHKDSK.COM CHKDSK.CO_ 10 07/30/97 11:49 71744
CHKDSK.SYS CHKDSK.SY_ 12 06/16/97 14:37 747
CHKDSK32.DLL CHKDSK32.DL_ 8 07/30/97 11:47 121895
CHKDSK32.EXE CHKDSK32.EX_ 11 07/30/97 11:36 6417
CLIFI.EXE CLIFI.EX_ 10 06/17/97 10:21 56108
CLOCK01.SYS CLOCK01.SY_ 12 06/26/97 15:36 4164
CLOCK02.SYS CLOCK02.SY_ 12 06/26/97 15:36 4150
CMD.EXE CMD.EX_ 9 07/30/97 11:57 75288
CMD640X.ADD CMD640X.AD_ 11 06/27/97 15:31 36038
CMDATAPI.FLT CMDATAPI.FL_ 11 06/27/97 13:59 21724
COM.SYS COM.SY_ 11 04/11/97 12:26 18751
COMMAND.COM COMMAND.CO_ 10 07/30/97 11:54 60460
FixPak Corrective Service levels and disk layouts 23
August 29, 1997 - Warp 4 FixPak XRGM003
COUR.OFM COUR.OF_ 12 04/30/97 11:59 4237
COUR.PFB COUR.PF_ 9 04/30/97 11:59 62921
COURB.OFM COURB.OF_ 12 04/30/97 11:59 4245
COURB.PFB COURB.PF_ 9 04/30/97 11:59 62399
COURBI.OFM COURBI.OF_ 12 04/30/97 11:59 4259
COURBI.PFB COURBI.PF_ 9 04/30/97 11:59 64511
COURI.OFM COURI.OF_ 12 04/30/97 11:59 4252
COURI.PFB COURI.PF_ 9 04/30/97 11:59 65056
CREX.MSG CREX.MS_ 12 09/19/96 15:44 2865
CREXUTIL.DLL CREXUTIL.DL_ 11 06/11/97 00:34 29689
CREXX.DLL CREXX.DL_ 7 06/11/97 00:34 266015
DETNE2.SYS DETNE2.SY_ 11 06/26/97 14:56 5658
DF_DEB.EXE DF_DEB.EX_ 8 06/18/97 18:00 150049
DF_RET.EXE DF_RET.EX_ 8 07/30/97 10:16 149051
DICTATE.EXE DICTATE.EX_ 10 04/01/97 15:36 51523
DICTDLL.DLL DICTDLL.DL_ 10 04/01/97 15:37 51363
DISPLAY.DLL DISPLAY.DL_ 10 07/14/97 16:44 46574
DIVE.DLL DIVE.DL_ 9 06/16/97 13:36 69640
DMQSPROF.DLL DMQSPROF.DL_ 10 05/19/97 17:38 43533
DOSCALL1.DLL DOSCALL1.DL_ 8 07/30/97 10:11 123794
DOSCALL1.SYM DOSCALL1.SY_ 10 07/14/97 15:37 41524
DOSCALL1.TDF DOSCALL1.TD_ 12 07/30/97 10:11 2312
DOSKRNL DOSKRNL.___ 11 07/30/97 09:53 30581
DPT20XX.ADD DPT20XX.AD_ 11 06/27/97 13:57 24700
DRVMAP.INF DRVMAP.IN_ 12 07/30/97 08:58 13194
DSPINSTL.EXE DSPINSTL.EX_ 8 07/30/97 11:10 118344
E.EXE E.EX_ 10 07/30/97 17:23 61719
EAUTIL.EXE EAUTIL.EX_ 11 07/30/97 12:01 38496
ENGINE.EXE ENGINE.EX_ 4 03/11/97 10:06 439716
EPM.EXE EPM.EX_ 11 07/30/97 13:14 19681
FD16-700.ADD FD16-700.AD_ 11 06/27/97 15:42 34152
FD7000EX.ADD FD7000EX.AD_ 11 06/27/97 15:43 20758
FD8XX.ADD FD8XX.AD_ 11 06/27/97 13:56 29954
FDISK.COM FDISK.CO_ 9 07/30/97 12:14 114848
FFST.DLL FFST.DL_ 11 04/03/97 19:03 11425
FILT.DLL FILT.DL_ 11 07/22/97 17:56 22864
FORMAT.COM FORMAT.CO_ 10 07/30/97 12:03 71456
FSFILTER.SYS FSFILTER.SY_ 11 07/30/97 10:14 12972
GDI.EXE GDI.EX_ 7 07/31/97 12:04 225312
GRADD.SYS GRADD.SY_ 12 11/06/96 11:47 1259
GRE2VMAN.DLL GRE2VMAN.DL_ 11 05/20/97 11:49 16230
HELPMGR.DLL HELPMGR.DL_ 6 06/16/97 14:58 249623
HELPMSG.EXE HELPMSG.EX_ 11 07/30/97 12:04 37280
HELV.OFM HELV.OF_ 12 07/15/97 14:40 4873
HELV.PFB HELV.PF_ 9 04/30/97 11:59 58156
HELVB.OFM HELVB.OF_ 12 07/15/97 14:40 4857
HELVB.PFB HELVB.PF_ 9 04/30/97 11:59 59821
HELVBI.OFM HELVBI.OF_ 11 07/15/97 14:40 4859
HELVBI.PFB HELVBI.PF_ 9 04/30/97 11:59 61860
HELVI.OFM HELVI.OF_ 11 07/15/97 14:40 4844
HELVI.PFB HELVI.PF_ 9 04/30/97 11:59 61367
FixPak Corrective Service levels and disk layouts 24
August 29, 1997 - Warp 4 FixPak XRGM003
HPFS.IFS HPFS.IF_ 9 07/30/97 11:28 141378
IBM16AFS.EXE IBM16AFS.EX_ 12 06/27/97 15:43 3177
IBM1FLPY.ADD IBM1FLPY.AD_ 11 06/27/97 13:46 35318
IBM1S506.ADD IBM1S506.AD_ 10 06/27/97 12:25 65290
IBM2AMB1.SYS IBM2AMB1.SY_ 11 06/27/97 12:31 12453
IBM2AST1.SYS IBM2AST1.SY_ 11 06/27/97 12:31 10047
IBM2CAD1.SYS IBM2CAD1.SY_ 11 06/27/97 12:33 12495
IBM2CMQ1.SYS IBM2CMQ1.SY_ 11 06/27/97 12:31 10101
IBM2FLPY.ADD IBM2FLPY.AD_ 11 06/27/97 15:40 14420
IBM2MAT1.SYS IBM2MAT1.SY_ 11 06/27/97 12:32 10083
IBM2NCR1.SYS IBM2NCR1.SY_ 11 06/27/97 12:32 10063
IBM2NEC1.SYS IBM2NEC1.SY_ 11 06/27/97 12:32 10063
IBM2SCSI.ADD IBM2SCSI.AD_ 11 06/27/97 15:40 33149
IBM2SS01.SYS IBM2SS01.SY_ 11 06/27/97 14:09 27087
IBM2SS02.SYS IBM2SS02.SY_ 11 06/27/97 14:09 22835
IBM2TOS1.SYS IBM2TOS1.SY_ 11 06/27/97 12:31 10054
IBM2ZEN1.SYS IBM2ZEN1.SY_ 11 06/27/97 12:30 10047
IBM2ZOS1.SYS IBM2ZOS1.SY_ 11 06/27/97 12:32 10079
IBM4612.SYS IBM4612.SY_ 11 05/01/97 11:43 10180
IBMIDECD.FLT IBMIDECD.FL_ 11 06/27/97 12:25 23900
IBMKBD.SYS IBMKBD.SY_ 11 11/14/96 10:47 7770
ICMEMCDD.SYS ICMEMCDD.SY_ 11 06/27/97 12:34 13932
ICMEMFMT.EXE ICMEMFMT.EX_ 10 06/27/97 12:35 50932
ICMEMMTD.SYS ICMEMMTD.SY_ 11 06/27/97 12:35 8300
INSTALL.DLL INSTALL.DL_ 5 07/30/97 10:22 351287
INSTALL.EXE INSTALL.EX_ 6 07/30/97 10:35 384770
INST_DOS.EXE INST_DOS.EX_ 10 06/16/97 14:55 36522
IPSRAID.ADD IPSRAID.AD_ 11 06/27/97 14:00 18714
ISGDI2VM.DRV ISGDI2VM.DR_ 2 05/20/97 11:15 86600
KBDBASE.SYS KBDBASE.SY_ 11 07/10/97 10:35 34133
KERNEL.SDF KERNEL.SD_ 10 11/07/96 21:11 467330
KERNELD.SDF KERNELD.SD_ 10 11/07/96 21:12 468657
KEYBOARD.DCP KEYBOARD.DC_ 11 06/16/97 16:30 275644
LIBUNI.DLL LIBUNI.DL_ 1 06/06/97 20:59 177021
LINK386.EXE LINK386.EX_ 8 05/02/97 08:54 145229
LMS206.ADD LMS206.AD_ 8 06/27/97 12:25 38706
MIGRATE.EXE MIGRATE.EX_ 8 07/30/97 11:10 118732
MINXOBJ.DLL MINXOBJ.DL_ 10 06/16/97 17:29 31746
MIRRORS.DLL MIRRORS.DL_ 5 09/19/96 15:53 444744
MITFX001.ADD MITFX001.AD_ 11 06/27/97 09:45 20492
MMODPTS.DLL MMODPTS.DL_ 7 06/16/97 13:44 186716
MMPARTS.DLL MMPARTS.DL_ 1 07/30/97 14:19 1532318
MMPM.DLL MMPM.DL_ 5 07/30/97 14:25 430753
MOUSE.SYS MOUSE.SY_ 11 07/09/97 18:19 18681
NAMECSSP.DLL NAMECSSP.DL_ 10 10/16/96 15:25 61171
NAMEDSP.DLL NAMEDSP.DL_ 8 07/22/97 19:22 123427
NAMEFT.DLL NAMEFT.DL_ 9 10/16/96 15:27 66322
NAMEFW.DLL NAMEFW.DL_ 9 06/16/97 15:49 72328
NAMEINFO.DLL NAMEINFO.DL_ 10 07/22/97 19:24 47957
NAMEINI.DLL NAMEINI.DL_ 10 07/22/97 19:24 59027
NAMEOSP.DLL NAMEOSP.DL_ 6 07/22/97 19:23 52725
FixPak Corrective Service levels and disk layouts 25
August 29, 1997 - Warp 4 FixPak XRGM003
NAMEREXX.DLL NAMEREXX.DL_ 8 07/22/97 19:24 97779
NAMEREXX.MSG NAMEREXX.MS_ 12 07/30/97 15:19 5132
OREXUTIL.DLL ORXUTIL2.DL_ 11 06/06/97 13:17 28885
OS2ASPI.DMD OS2ASPI.DM_ 11 06/27/97 13:45 11096
OS2CDROM.DMD OS2CDROM.DM_ 11 07/09/97 18:26 27356
OS2CHAR.TDF OS2CHAR.TD_ 12 07/30/97 10:11 13194
OS2DASD.DMD OS2DASD.DM_ 11 06/27/97 13:44 35434
OS2DUMP OS2DUMP.___ 11 06/09/97 17:11 17350
OS2K386.EXE OS2K386.EX_ 9 07/31/97 12:06 80674
OS2KRNL OS2KRNL.___ 3 07/30/97 09:33 599179
OS2KRNL.TDF OS2KRNL.TD_ 11 07/30/97 09:33 13992
OS2KRNLD.SYM OS2KRNLD.SY_ 8 07/30/97 09:46 180292
OS2KRNLR.SYM OS2KRNLR.SY_ 8 07/30/97 09:32 163268
OS2LDR OS2LDR.___ 11 07/30/97 09:12 33280
OS2LDR.MSG OS2LDR.MS_ 12 07/30/97 09:13 9779
OS2NS.EXE OS2NS.EX_ 10 07/22/97 19:23 44980
OS2SCSI.DMD OS2SCSI.DM_ 11 06/27/97 13:44 11614
OSO001.MSG OSO001.MS_ 9 07/29/97 11:05 220233
OSO001H.MSG OSO001H.MS_ 4 07/29/97 11:05 294967
PCM2ATA.ADD PCM2ATA.AD_ 11 06/27/97 14:05 27938
PCMCIA.SYS PCMCIA.SY_ 11 06/27/97 14:03 48646
PCMCIA.TBL PCMCIA.TB_ 12 04/03/97 13:55 4100
PMATM.DLL PMATM.DL_ 3 06/03/97 14:51 233651
PMCHKDSK.DLL PMCHKDSK.DL_ 12 07/30/97 12:16 5151
PMCLIP.DLL PMCLIP.DL_ 11 04/08/97 17:36 21189
PMCTLS.DLL PMCTLS.DL_ 4 07/30/97 14:41 581860
PMCTLS.SYM PMCTLS.SY_ 10 07/14/97 16:57 43860
PMDDE.DLL PMDDE.DL_ 7 07/30/97 15:14 28264
PMDDEML.DLL PMDDEML.DL_ 11 06/16/97 14:20 27210
PMDRAG.DLL PMDRAG.DL_ 12 07/30/97 14:41 1731
PMGPI.DLL PMGPI.DL_ 7 06/16/97 14:18 228570
PMGPI.TDF PMGPI.TD_ 12 06/16/97 14:18 10913
PMGRE.DLL PMGRE.DL_ 12 06/16/97 23:52 2231
PMGRE.TDF PMGRE.TD_ 12 07/11/97 10:47 1062
PMMERGE.DLL PMMERGE.DL_ 2 07/30/97 14:45 1163625
PMMERGE.SYM PMMERGE.SY_ 9 07/14/97 17:04 113812
PMMLE.DLL PMMLE.DL_ 12 06/16/97 14:30 673
PMPRINT.QPR PMPRINT.QP_ 11 07/30/97 16:37 11785
PMSDMRI.DLL PMSDMRI.DL_ 11 07/30/97 14:41 12800
PMSHAPI.DLL PMSHAPI.DL_ 12 04/08/97 16:45 4549
PMSHAPI.TDF PMSHAPI.TD_ 12 07/11/97 10:47 6187
PMSPL.DLL PMSPL.DL_ 7 07/30/97 16:36 264634
PMSPL.SYM PMSPL.SY_ 11 07/14/97 19:56 30836
PMSPL.TDF PMSPL.TD_ 12 07/30/97 16:36 4138
PMVDMP.DLL PMVDMP.DL_ 10 07/30/97 15:15 43799
PMVIOP.DLL PMVIOP.DL_ 10 07/30/97 15:14 59058
PMVIOP.SYM PMVIOP.SY_ 11 07/14/97 17:41 6420
PMWIN.DLL PMWIN.DL_ 3 07/30/97 14:33 11264
PMWIN.TDF PMWIN.TD_ 11 07/11/97 10:47 12612
PMWIN32.SDF PMWIN32.SD_ 11 06/06/97 19:11 299485
PMWINX.DLL PMWINX.DL_ 2 07/30/97 15:08 578175
FixPak Corrective Service levels and disk layouts 26
August 29, 1997 - Warp 4 FixPak XRGM003
PMWP.DLL PMWP.DL_ 3 07/30/97 16:20 922169
PMWP.SYM PMWP.SY_ 10 07/14/97 19:25 100244
PMWPMRI.DLL PMWPMRI.DL_ 10 07/30/97 16:20 57381
PNP.DLL PNP.DL_ 11 06/16/97 17:53 28297
PNP.SYS PNP.SY_ 12 06/26/97 15:24 2152
POINTDD.SYS POINTDD.SY_ 12 07/09/97 18:30 2823
PRINT01.SYS PRINT01.SY_ 11 07/10/97 10:24 12590
PRINT02.SYS PRINT02.SY_ 11 07/10/97 10:24 11766
PSSDMON.EXE PSSDMON.EX_ 11 03/31/97 21:54 25437
PSTAT.EXE PSTAT.EX_ 11 07/30/97 12:06 10339
QUECALLS.DLL QUECALLS.DL_ 12 11/07/96 20:51 1024
QUECALLS.TDF QUECALLS.TD_ 12 07/30/97 10:11 1299
RAS001.MSG RAS001.MS_ 11 07/30/97 15:29 32532
README.CID README.CI_ 11 07/30/97 08:58 67377
RESERVE.SYS RESERVE.SY_ 11 06/26/97 14:56 5704
RESTORE.EXE RESTORE.EX_ 11 07/30/97 12:20 36928
REX.MSG REX.MS_ 12 09/19/96 15:44 2865
REXX.DLL REXX.DL_ 7 06/11/97 00:34 266015
REXX.IMG REXX.IM_ 9 03/31/97 17:35 274220
REXXAPI.DLL REXXAPI.DL_ 11 03/31/97 17:35 29091
REXXC.EXE REXXC.EX_ 12 03/31/97 17:35 1980
REXXCRT.DLL REXXCRT.DL_ 10 03/31/97 17:35 61195
REXXUTIL.DLL ORXUTIL1.DL_ 11 06/06/97 13:17 28885
REXXUTIL.DLL REXXUTIL.DL_ 11 06/11/97 00:34 29689
RSPDSPI.EXE RSPDSPI.EX_ 8 07/30/97 11:11 95816
RSPINST.EXE RSPINST.EX_ 6 07/30/97 10:49 428592
RSRV.EXE RSRV.EX_ 9 07/22/97 19:22 77987
SBCD2.ADD SBCD2.AD_ 5 06/27/97 09:12 18820
SCENTER.DLL SCENTER.DL_ 6 07/30/97 17:17 291869
SEAMLESS.DLL SEAMLESS.DL_ 10 07/30/97 15:15 49167
SECUTIL.DLL SECUTIL.DL_ 11 03/31/97 21:54 21468
SEINST.EXE SEINST.EX_ 10 07/30/97 10:28 37441
SEMAINT.EXE SEMAINT.EX_ 10 07/30/97 10:29 67488
SESAPI.DLL SESAPI.DL_ 11 06/06/97 20:24 24219
SESDD32.SYS SESDD32.SY_ 10 06/16/97 15:53 127024
SESMGR.DLL SESMGR.DL_ 12 11/07/96 20:45 1536
SESMGR.TDF SESMGR.TD_ 12 07/30/97 10:11 1643
SETBOOT.EXE SETBOOT.EX_ 11 07/30/97 12:13 16546
SETDEFV.CMD SETDEFV.CM_ 12 12/13/96 11:23 1652
SOFTDRAW.DLL SOFTDRAW.DL_ 6 04/30/97 14:44 409595
SONY31A.ADD SONY31A.AD_ 11 07/09/97 18:29 32738
SPCHOBJ.DLL SPCHOBJ.DL_ 7 04/01/97 15:35 132899
SS2PCIC1.SYS SS2PCIC1.SY_ 11 06/27/97 14:08 19087
SS2TCIC1.SYS SS2TCIC1.SY_ 11 06/27/97 14:08 22824
SVMC.DLL SVMC.DL_ 8 07/30/97 13:53 97785
SVSH.DLL SVSH.DL_ 11 07/30/97 13:53 23452
SYSINSTX.COM SYSINSTX.CO_ 10 07/30/97 12:07 39472
SYSTEM.TDF SYSTEM.TD_ 11 07/30/97 12:21 18358
SYSTEM.TFF SYSTEM.TF_ 11 07/30/97 12:21 45067
TEDIT.EXE TEDIT.EX_ 11 07/30/97 12:20 9506
TEDIT.HLP TEDIT.HL_ 12 07/30/97 08:58 14596
FixPak Corrective Service levels and disk layouts 27
August 29, 1997 - Warp 4 FixPak XRGM003
TESTCFG.SYS TESTCFG.SY_ 11 06/27/97 09:13 9808
TNR.OFM TNR.OF_ 12 04/30/97 11:59 4940
TNR.PFB TNR.PF_ 8 04/30/97 11:59 74248
TNRB.OFM TNRB.OF_ 12 04/30/97 11:59 4950
TNRB.PFB TNRB.PF_ 9 04/30/97 11:59 68902
TNRBI.OFM TNRBI.OF_ 11 04/30/97 11:59 4964
TNRBI.PFB TNRBI.PF_ 8 04/30/97 11:59 73914
TNRI.OFM TNRI.OF_ 11 04/30/97 11:59 4955
TNRI.PFB TNRI.PF_ 9 04/30/97 11:59 73592
TRACEFMT.EXE TRACEFMT.EX_ 5 07/30/97 15:37 128004
TRC0003.TFF TRC0003.TF_ 12 12/12/96 17:56 1503
TRC0004.TFF TRC0004.TF_ 12 06/16/97 13:23 4754
TRC0005.TFF TRC0005.TF_ 11 07/30/97 09:46 30574
TRC0006.TFF TRC0006.TF_ 11 12/12/96 17:19 12356
TRC0007.TFF TRC0007.TF_ 12 06/27/97 13:44 1394
TRC0008.TFF TRC0008.TF_ 12 06/26/97 14:55 544
TRC0010.TFF TRC0010.TF_ 12 07/30/97 10:11 3638
TRC0016.TFF TRC0016.TF_ 12 07/30/97 10:11 1673
TRC0017.TFF TRC0017.TF_ 12 07/30/97 10:11 4799
TRC0018.TFF TRC0018.TF_ 11 07/30/97 10:11 37028
TRC006D.TFF TRC006D.TF_ 11 10/16/96 13:16 24181
TRC00C0.TFF TRC00C0.TF_ 11 07/11/97 10:47 13791
TRC00C2.TFF TRC00C2.TF_ 11 07/11/97 10:47 29873
TRC00C3.TFF TRC00C3.TF_ 12 07/11/97 10:47 3984
TRC00C4.TFF TRC00C4.TF_ 12 06/11/97 02:01 242
TRC00C5.TFF TRC00C5.TF_ 11 06/16/97 14:18 26439
TRC00C6.TFF TRC00C6.TF_ 12 07/30/97 16:36 5675
TRUETYPE.DLL TRUETYPE.DL_ 9 07/29/97 17:08 67416
UCDFS.DLL UCDFS.DL_ 10 07/30/97 09:55 13264
UCONV.DLL UCONV.DL_ 11 06/06/97 20:59 24311
UHPFS.DLL UHPFS.DL_ 9 07/30/97 11:47 111120
ULSACT01.MSG ULSACT01.MS_ 12 10/15/96 11:19 907
ULSCAU01.MSG ULSCAU01.MS_ 12 10/15/96 11:19 899
ULSDET01.MSG ULSDET01.MS_ 4 10/15/96 11:19 903
ULSERR01.MSG ULSERR01.MS_ 12 10/15/96 11:19 1967
UNPACK2.EXE UNPACK2.EX_ 10 12/05/95 00:11 79792
USER.EXE USER.EX_ 7 07/31/97 12:34 278112
VBIOS.SYS VBIOS.SY_ 11 07/30/97 12:24 8192
VCDROM.SYS VCDROM.SY_ 1 06/26/97 15:29 6880
VCMOS.SYS VCMOS.SY_ 12 07/30/97 12:24 2272
VCOM.SYS VCOM.SY_ 11 06/26/97 15:29 12384
VDPMI.SYS VDPMI.SY_ 9 07/30/97 12:25 30624
VDPX.SYS VDPX.SY_ 11 07/30/97 12:27 26112
VDSK.SYS VDSK.SY_ 11 06/26/97 15:29 10384
VIDEOPMI.DLL VIDEOPMI.DL_ 10 05/19/97 17:39 42247
VIOCALLS.DLL VIOCALLS.DL_ 12 04/08/97 17:36 2048
VKBD.SYS VKBD.SY_ 11 06/26/97 15:30 25292
VLPT.SYS VLPT.SY_ 11 06/26/97 15:30 10113
VMAN.DLL VMAN.DL_ 11 05/20/97 11:18 25221
VMANWIN.SYS VMANWIN.SY_ 11 05/19/97 17:37 2880
VMOUSE.SYS VMOUSE.SY_ 11 06/09/97 12:53 18704
FixPak Corrective Service levels and disk layouts 28
August 29, 1997 - Warp 4 FixPak XRGM003
VPIC.SYS VPIC.SY_ 11 07/30/97 12:30 9894
VTIMER.SYS VTIMER.SY_ 11 06/11/97 12:40 9936
VW32S.SYS VW32S.SY_ 11 07/30/97 12:31 18288
VWIN.SYS VWIN.SY_ 11 07/30/97 12:30 26896
WD24B.DSP WD24B.DS_ 2 04/03/97 13:55 12050
WINSCLIP.DLL WINSCLIP.DL_ 11 07/31/97 12:14 14848
WINSHELD.EXE WINSHELD.EX_ 11 07/31/97 12:14 22016
WINSMSG.DLL WINSMSG.DL_ 11 07/31/97 12:14 26905
WPCLS.IMP WPCLS.IM_ 12 03/31/97 17:35 8661
WPCONFIG.DLL WPCONFIG.DL_ 7 07/30/97 16:27 229702
WPHELP.HLP WPHELP.HL_ 4 07/30/97 13:32 907211
WPINET.DLL WPINET.DL_ 8 07/30/97 17:07 115384
WPPRINT.DLL WPPRINT.DL_ 5 06/16/97 17:38 352538
WPPRTMRI.DLL WPPRTMRI.DL_ 10 07/30/97 16:33 67385
WPREXX.IMP WPREXX.IM_ 12 03/31/97 17:35 6313
WPSINIT.WPS WPSINIT.WP_ 11 03/31/97 17:35 15877
WW.EXE WW.EX_ 11 04/01/97 15:37 8305
WWDLL.DLL WWDLL.DL_ 6 07/23/97 10:45 273149
WWHOOK.DLL WWHOOK.DL_ 11 04/01/97 15:43 27230
XCOPY.EXE XCOPY.EX_ 10 07/30/97 12:08 51920
FixPak Corrective Service levels and disk layouts 29
August 29, 1997 - Warp 4 FixPak XRGM003
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 12MB Drive with most free space, holds deferred files
RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE
Warning: Make sure you read and understand the following before
removing the Archive and Backup files and directories.
You can recover the space used for FixPak Archive and Backup files as
long as you understand that doing this prevents you from being able to
backout to the previous Backup or Archive level. If it becomes
necessary at a later time to backout a FixPak, the only way you can do
this is to reinstall Warp.
Do the following to delete the FixPak Backup and Archive files and
remove the files used by CSF to keep track of what service has been
applied to your system.
1. Delete every instance of the following files on your system
(search every drive and every directory they contain).
Ä LOGF0000.* (can be OS2 or MPM)
Ä LOGSTART.* (can be OS2 or MPM)
Ä LOGARCH.* (can be OS2 or MPM)
Ä CSF_*.*
Ä FIXSTART
2. Delete the files in the FixPak Archive and Backup directories on
your harddisk.
3. Remove the FixPak Archive and Backup directories with the RMDIR
command.
Space Utilization 30