home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PC-Online 1998 February
/
PCOnline_02_1998.iso
/
filesbbs
/
os2
/
xrgm005.arj
/
XRGM005.ZIP
/
XRGM005.1DK
/
README.1ST
< prev
next >
Wrap
Text File
|
1997-12-02
|
82KB
|
2,162 lines
< Installation instructions for Warp 4 FixPak XRGM005
December 2, 1997
Build level 9.029
This FixPak applies to:
CSD Level: XRG4000
Component ID: 5639A6100
Version: 4.00
Type: 0C
CSD Level: XRG4010
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.
December 2, 1997 - Warp 4 FixPak XRGM005
December 2, 1997 - Warp 4 FixPak XRGM005
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . 1
2.0 Installation Notes . . . . . . . . . . . . . . . . . . . . 2
2.0.1 No files to service . . . . . . . . . . . . . . . . . 2
2.0.2 Previous installation interrupted . . . . . . . . . . 2
2.0.3 Unable to open Archive directory . . . . . . . . . . . 3
2.0.4 RC 932 doing CID install of Warp 4 . . . . . . . . . . 3
2.0.5 Windows printer drivers leave a zombie thread running 4
2.0.6 Multimedia no longer selectable . . . . . . . . . . . 5
2.0.7 If you have installed FixPak XRGM000 . . . . . . . . . 5
2.0.8 If you have installed controlled FixPak XRGM001 . . . 6
2.0.9 APAR JR09494 (trap exiting WINOS2 with MWAVE audio) . 7
2.0.10 MMPARTS.DLL/USER.EXE popup during install . . . . . . 7
2.0.11 CSF0212 Archive path is shared between mismatched . . 7
2.0.12 CSF0214 Error opening or creating archive file. . . 7
2.0.13 CSF0208 No products were found . . . . . . . . . . . 7
2.0.14 Printer installation process change . . . . . . . . . 8
2.0.15 Configuration Installation Distribution ( CID ) . . . 8
2.0.16 Do not use your system . . . . . . . . . . . . . . . 8
3.0 Post Installation Notes . . . . . . . . . . . . . . . . . 9
3.0.1 SYS3170 installing Lotus SmartSuite 96 . . . . . . . . 9
3.0.2 Intermittent pause with IBM Thinkpad 760E/ED/ELD/EL . 9
4.0 New Function . . . . . . . . . . . . . . . . . . . . . . 10
4.1 New Warp Registry Editor . . . . . . . . . . . . . . . . 10
4.2 IBM Open32 . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . 10
4.4 New (improved) CHKDSK . . . . . . . . . . . . . . . . . . 10
4.4.1 Using the new CHKDSK . . . . . . . . . . . . . . . . 11
4.4.2 CHKDSK log formatter . . . . . . . . . . . . . . . . 12
4.4.3 Automated Trap Screen Logging . . . . . . . . . . . . 13
4.4.4 SUPPRESSPOPUPS . . . . . . . . . . . . . . . . . . . 13
4.4.5 TRAPLOG . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.6 TRAPDUMP . . . . . . . . . . . . . . . . . . . . . . 14
4.4.7 SYSDUMP . . . . . . . . . . . . . . . . . . . . . . . 15
4.5 Other README files . . . . . . . . . . . . . . . . . . . 15
5.0 Corrective Service Facility Installation Diskettes . . . 16
5.0.1 Required CSF level . . . . . . . . . . . . . . . . . 16
5.0.2 Where you can find CSF . . . . . . . . . . . . . . . 16
5.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . 17
5.1 Residual FixPak files from OS/2 2.11 or Warp 3 . . . . . 17
5.2 Read-Only files . . . . . . . . . . . . . . . . . . . . . 18
5.3 SYSLEVEL file locations . . . . . . . . . . . . . . . . . 18
5.4 Relocated OS/2 file support . . . . . . . . . . . . . . . 19
6.0 Installation Process . . . . . . . . . . . . . . . . . . 21
Contents ii
December 2, 1997 - Warp 4 FixPak XRGM005
6.1 Before installation . . . . . . . . . . . . . . . . . . . 21
6.2 Method 1: Install from booted OS/2 partition. . . . . . 21
6.3 Method 2: Boot from Corrective Service Disk 1. . . . . . 23
6.4 Additional Corrective Service Facility information . . . 23
6.5 FixPaks on CD-ROM . . . . . . . . . . . . . . . . . . . . 23
7.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . 25
7.0.1 New SYSLEVEL.FPK . . . . . . . . . . . . . . . . . . 25
8.0 FixPak Corrective Service levels and disk layouts . . . . 26
9.0 Space Utilization . . . . . . . . . . . . . . . . . . . . 35
9.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . 35
Contents iii
December 2, 1997 - Warp 4 FixPak XRGM005
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XRGM005 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 XRGM005 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
December 2, 1997 - Warp 4 FixPak XRGM005
2.0 INSTALLATION NOTES
2.0.1 NO FILES TO SERVICE
If you see a "No files to service" message while applying this
FixPak, there is probably a mismatch between the data in
\OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this FixPak.
Compare the data for the OS/2 Base Operating System from the
SYSLEVEL command output with the same values listed at the end of
this document in the "FixPak Corrective Service levels and disk
layouts" section. They must be identical.
If these values are correct, check for the following files on any
OS/2 boot drive in the \OS2\INSTALL directory.
LOGF0000.OS2
LOGSTART.OS2
LOGARCH.OS2
Check for the following files in your MMOS2\INSTALL directory.
LOGF0000.MPM
LOGSTART.MPM
LOGARCH.MPM
Also check for the following file:
C:\CSF_SEL.000
If these files exist, rename them and try the FixPak installation
again. Delete the renamed files after the FixPak has been applied.
2.0.2 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:
Installation Notes 2
December 2, 1997 - Warp 4 FixPak XRGM005
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.
2.0.3 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.
2.0.4 RC 932 DOING CID INSTALL OF WARP 4
If you get a RC (Return Code) 932 while doing a CID install of Warp
4 and you are using RSPINST.EXE from FixPak 3 or later, you will
need to do the following.
1. Create a temporary work directory somewhere on your harddrive.
assume it's c:\tempwork
2. Locate the section called "FixPak Corrective Service levels and
disk layouts".
3. Locate CHKDSK.SYS, CHKDSK32.DLL, CHKDSK32.EXE and UHPFS.DLL and
record what disks they are found on.
Note: For FixPak 3, they are on disks 12, 8, 12 and 9
respectively. This will change for later FixPaks.
4. Place FixPak disk 12 in A: and enter
unpack a:\fix\os2.1\chkdsk.sy_ c:\tempwork
5. Place FixPak disk 8 in A: and enter
Installation Notes 3
December 2, 1997 - Warp 4 FixPak XRGM005
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.Do the CID install
2.0.5 WINDOWS PRINTER DRIVERS LEAVE A ZOMBIE THREAD RUNNING
A problem occurs with some Windows printer drivers where a zombie
thread is left running after the program that loaded it is exited.
This does not occur when the program is run from a Seamless
instance of PROGMAN or from a Full Screen session because when
these are exited the whole WINOS2 Subsystem is exited.
Installation Notes 4
December 2, 1997 - Warp 4 FixPak XRGM005
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.
2.0.6 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.
2.0.7 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.
Installation Notes 5
December 2, 1997 - Warp 4 FixPak XRGM005
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:
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.
2.0.8 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 6
December 2, 1997 - Warp 4 FixPak XRGM005
2.0.9 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.
2.0.10 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.
*======================================================================
2.0.11 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.
2.0.12 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.
2.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.
Installation Notes 7
December 2, 1997 - Warp 4 FixPak XRGM005
2.0.14 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.
2.0.15 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.
2.0.16 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.
Installation Notes 8
December 2, 1997 - Warp 4 FixPak XRGM005
3.0 POST INSTALLATION NOTES
3.0.1 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.
3.0.2 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 9
December 2, 1997 - Warp 4 FixPak XRGM005
4.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.
4.1 NEW WARP REGISTRY EDITOR
See the README.REG file on the first FixPak disk for details.
4.2 IBM OPEN32
This fixpak include updates to the IBM Open32 Application
Programming Interfaces (APIs).
4.3 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
Updates for the GRADD and other video drivers can be found via the
internet at:
■ http://service.software.ibm.com/pslaunch.html
4.4 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.
New Function 10
December 2, 1997 - Warp 4 FixPak XRGM005
4.4.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.
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).
New Function 11
December 2, 1997 - Warp 4 FixPak XRGM005
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.
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.
4.4.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:
New Function 12
December 2, 1997 - Warp 4 FixPak XRGM005
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.
4.4.3 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).
4.4.4 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".
New Function 13
December 2, 1997 - Warp 4 FixPak XRGM005
4.4.5 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.
4.4.6 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.
New Function 14
December 2, 1997 - Warp 4 FixPak XRGM005
4.4.7 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)"
4.5 OTHER README FILES
There are other README files containing information you may want to
review. These files are found on the first FixPak disk.
File Use
README2 Problems fixed in each FixPak (APAR list)
README.REG Explanation of the Warp Registry Editor REGEDIT2.EXE
README.CID Tips on installing FixPaks via CID
README.DBG Tips on debugging OS/2 Warp (3.0 and 4.0)
New Function 15
December 2, 1997 - Warp 4 FixPak XRGM005
5.0 CORRECTIVE SERVICE FACILITY INSTALLATION DISKETTES
5.0.1 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.
5.0.2 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 16
December 2, 1997 - Warp 4 FixPak XRGM005
CSF DISK Diskette 1
(SP DISK 1)
CSF DISK Diskette 2
(SP DISK 2)
5.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 XRGM005.?DK A: /F (? can be 1 through 9, A through
Z).
Label the diskette as
FixPak XRGM005
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10
through 26.
Examples:
XRGM005.ADK = 10
XRGM005.FDK = 15
XRGM005.LDK = 21
etc.
5.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 Installation Diskettes 17
December 2, 1997 - Warp 4 FixPak XRGM005
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.
5.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.
5.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 Installation Diskettes 18
December 2, 1997 - Warp 4 FixPak XRGM005
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 under the root directory.
..\..\VT\* all files in all subdirectories under the VT directory.
5.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:
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
Corrective Service Facility Installation Diskettes 19
December 2, 1997 - Warp 4 FixPak XRGM005
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 Installation Diskettes 20
December 2, 1997 - Warp 4 FixPak XRGM005
6.0 INSTALLATION PROCESS
6.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.
Reboot your system then shutdown all running applications.
6.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
This method allows you to select the products (partitions) to be
serviced.
This is the method you should use if you have more than one OS/2
partition and want to control which one is serviced.
Note: You can use a diskette drive other than A: with this method.
If your 3.5" diskette drive is B:, use B: where A: is mentioned in
the following steps. (this method only).
1. Insert CSF DISK Diskette 1 in drive A.
2. Open an OS/2 window or full-screen session.
3. Type A:\SERVICE and press the Enter key.
Note: You could also use the "Drives" object for A: and double
click on the "SERVICE.EXE" Icon to start the install.
4. Follow the displayed instructions. When prompted to insert
Corrective Service Diskette 1 (not CSF DISK Diskette 1), place
FixPak XRGM005 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
Installation Process 21
December 2, 1997 - Warp 4 FixPak XRGM005
copy 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 22
December 2, 1997 - Warp 4 FixPak XRGM005
The system will do one automatic reboot after the Locked File
Device Driver has completed.
6.3 METHOD 2: BOOT FROM CORRECTIVE SERVICE DISK 1.
This method does not prompt the user for any information. No
interaction with the user takes place other than requests to put
the next diskette in drive A. All serviceable partitions on your
system will be updated automatically. Be especially careful of
extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using this method
because they can cause CSF to apply service to directories you do
not want serviced.
1. Shut down your OS/2 system.
2. Insert CSF DISK Diskette 1 in drive A.
3. Press Ctrl+Alt+Del to boot the disk in drive A.
Service will be applied to ALL partitions that contain a version of
OS/2 that is supported by this FixPak. See the section "FixPak
Corrective Service 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.
6.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.
6.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:
Installation Process 23
December 2, 1997 - Warp 4 FixPak XRGM005
■ http://domino.www.ibm.com/Support//techconn/
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 24
December 2, 1997 - Warp 4 FixPak XRGM005
7.0 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 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.029
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.
7.0.1 NEW SYSLEVEL.FPK
A SYSLEVEL.FPK file has been added to all Warp 4 FixPaks, beginning
with XRGM004. 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 25
December 2, 1997 - Warp 4 FixPak XRGM005
8.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 9.029
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Basisbetriebssystem"
Standard Edition 4.00
Fixpak name: XRGM005_ (Country = Germany)
Pre-requisite CSD Level: XRG4000_
System Id: 1000
Component Id: 5639A6100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Basisbetriebssystem"
Standard Edition 4.00
Fixpak name: XRGM005_ (Country = Germany)
Pre-requisite CSD Level: XRG4010_
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_ 12 08/18/97 18:54 44208
AHA164X.ADD AHA164X.AD_ 13 08/18/97 18:53 20022
AHA6360.SNP AHA6360.SN_ 12 10/14/97 10:55 27395
AIC7770.ADD AIC7770.AD_ 12 08/18/97 18:55 42558
AIC7870.ADD AIC7870.AD_ 12 04/10/97 16:52 39870
AIC7870.SNP AIC7870.SN_ 13 08/18/97 19:47 9104
APM.SYS APM.SY_ 13 08/18/97 18:43 9922
APMDAEMN.EXE APMDAEMN.EX_ 13 08/18/97 20:25 2733
ASIACOL.DLL ASIACOL.DL_ 8 11/02/97 02:56 158732
BDIME.DLL BDIME.DL_ 13 10/16/97 15:32 11879
BLDLEVEL.EXE BLDLEVEL.EX_ 13 11/18/97 18:26 21523
BOOTDISK.EXE BOOTDISK.EX_ 11 11/18/97 17:11 60941
BOOTDISK.HLP BOOTDISK.HL_ 13 11/18/97 17:11 10785
BSAUDIO.SNP BSAUDIO.SN_ 13 10/14/97 10:55 5756
BTSCSI.ADD BTSCSI.AD_ 13 08/18/97 18:59 26569
BVSCALLS.DLL BVSCALLS.DL_ 13 10/03/97 03:03 512
CDFS.IFS CDFS.IF_ 12 11/18/97 16:18 45610
CDROM.TBL CDROM.TB_ 13 11/12/96 13:38 4365
FixPak Corrective Service levels and disk layouts 26
December 2, 1997 - Warp 4 FixPak XRGM005
CHKDSK.COM CHKDSK.CO_ 11 11/18/97 18:12 71744
CHKDSK.SYS CHKDSK.SY_ 13 10/03/97 03:54 747
CHKDSK32.DLL CHKDSK32.DL_ 10 11/18/97 18:11 121895
CHKDSK32.EXE CHKDSK32.EX_ 13 11/18/97 18:01 6417
CLOCK01.SYS CLOCK01.SY_ 13 08/18/97 20:05 4160
CLOCK02.SYS CLOCK02.SY_ 13 08/18/97 20:05 4040
CMD.EXE CMD.EX_ 10 11/18/97 18:16 75556
CMD640X.ADD CMD640X.AD_ 12 08/18/97 19:01 36038
CMDATAPI.FLT CMDATAPI.FL_ 13 08/18/97 19:01 21724
COM.SYS COM.SY_ 13 04/11/97 12:26 18751
COMMAND.COM COMMAND.CO_ 12 11/18/97 18:15 60460
COUR.OFM COUR.OF_ 13 10/10/97 01:03 4228
COUR.PFB COUR.PF_ 9 10/10/97 01:03 112516
COUR.PFM COU1.PF_ 13 10/10/97 01:03 730
COURB.OFM COURB.OF_ 13 10/10/97 01:03 4238
COURB.PFB COURB.PF_ 9 10/10/97 01:03 116734
COURB.PFM COUR1.PF_ 13 10/10/97 01:03 735
COURBI.OFM COURBI.OF_ 13 10/10/97 01:03 4252
COURBI.PFB COURBI.PF_ 9 10/10/97 01:03 112275
COURBI.PFM COURB1.PF_ 13 10/10/97 01:03 741
COURI.OFM COURI.OF_ 13 10/10/97 01:03 4243
COURI.PFB COURI.PF_ 9 10/10/97 01:03 113042
COURI.PFM COUR2.PF_ 13 10/10/97 01:03 737
CREX.MSG CREX.MS_ 13 09/19/96 15:44 2865
CREXUTIL.DLL CREXUTIL.DL_ 12 06/11/97 00:34 29689
CREXX.DLL CREXX.DL_ 8 06/11/97 00:34 266015
DETNE2.SYS DETNE2.SY_ 13 08/18/97 18:42 5658
DF_DEB.EXE DF_DEB.EX_ 10 10/22/97 23:48 150579
DF_RET.EXE DF_RET.EX_ 10 11/18/97 16:28 149581
DIBDRVR.DLL DIBDRVR.DL_ 13 10/22/97 23:20 2267
DICTATE.EXE DICTATE.EX_ 11 04/01/97 15:36 51523
DICTDLL.DLL DICTDLL.DL_ 11 07/23/97 11:57 51179
DISPLAY.DLL DISPLAY.DL_ 11 10/22/97 14:51 46574
DIVE.DLL DIVE.DL_ 11 11/11/97 15:46 69640
DMQSPROF.DLL DMQSPROF.DL_ 12 10/13/97 16:20 43565
DOSCALL1.DLL DOSCALL1.DL_ 9 11/18/97 16:25 124426
DOSCALL1.SYM DOSCALL1.SY_ 12 11/18/97 16:25 41636
DOSCALL1.TDF DOSCALL1.TD_ 13 11/18/97 16:25 2312
DOSKRNL DOSKRNL.___ 12 11/18/97 16:13 30581
DRVMAP.INF DRVMAP.IN_ 13 11/18/97 13:58 13194
DSPINSTL.EXE DSPINSTL.EX_ 10 11/18/97 17:07 118312
E.EXE E.EX_ 11 11/18/97 20:07 61719
EAUTIL.EXE EAUTIL.EX_ 12 11/18/97 18:19 38496
ENGINE.EXE ENGINE.EX_ 2 07/23/97 11:39 440424
EPM.EXE EPM.EX_ 6 11/18/97 15:38 19681
ERLOGGER.EXE ERLOGGER.EX_ 12 11/18/97 18:02 34320
ERRLOG.DLL ERRLOG.DL_ 10 11/18/97 18:01 72594
FD16-700.ADD FD16-700.AD_ 12 08/18/97 18:57 34152
FD7000EX.ADD FD7000EX.AD_ 13 08/18/97 18:57 20758
FD8XX.ADD FD8XX.AD_ 13 08/18/97 18:58 29954
FDISK.COM FDISK.CO_ 11 11/18/97 18:27 114848
FixPak Corrective Service levels and disk layouts 27
December 2, 1997 - Warp 4 FixPak XRGM005
FFST.DLL FFST.DL_ 13 04/03/97 19:03 11425
FFSTCONF.EXE FFSTCONF.EX_ 11 11/18/97 18:15 68669
FFSTPCT.EXE FFSTPCT.EX_ 11 11/18/97 18:15 69583
FILT.DLL FILT.DL_ 12 11/18/97 16:17 22864
FORMAT.COM FORMAT.CO_ 11 11/18/97 18:20 71456
FSFILTER.SYS FSFILTER.SY_ 13 11/18/97 16:27 12972
GDI.EXE GDI.EX_ 8 09/02/97 17:00 225792
GRADD.SYS GRADD.SY_ 13 10/16/97 18:49 1195
GRE2VMAN.DLL GRE2VMAN.DL_ 13 10/28/97 15:07 17259
HELPMGR.DLL HELPMGR.DL_ 7 10/19/97 14:43 249623
HELPMSG.EXE HELPMSG.EX_ 12 11/18/97 18:21 37280
HELV.OFM HELV.OF_ 13 10/10/97 01:03 4858
HELV.PFB HELV.PF_ 10 10/10/97 01:03 101581
HELV.PFM HEL1.PF_ 13 10/10/97 01:03 1150
HELVB.OFM HELVB.OF_ 13 10/10/97 01:03 4850
HELVB.PFB HELVB.PF_ 10 10/10/97 01:03 103882
HELVB.PFM HELV1.PF_ 13 10/10/97 01:03 1143
HELVBI.OFM HELVBI.OF_ 13 10/10/97 01:03 4852
HELVBI.PFB HELVBI.PF_ 9 10/10/97 01:03 104647
HELVBI.PFM HELVB1.PF_ 13 10/10/97 01:03 1141
HELVI.OFM HELVI.OF_ 13 10/10/97 01:03 4837
HELVI.PFB HELVI.PF_ 9 10/10/97 01:03 103585
HELVI.PFM HELV2.PF_ 13 10/10/97 01:03 1133
HPFS.IFS HPFS.IF_ 10 11/18/97 17:20 141378
IBM16AFS.EXE IBM16AFS.EX_ 13 08/18/97 18:58 3177
IBM1FLPY.ADD IBM1FLPY.AD_ 12 08/18/97 18:49 35318
IBM1S506.ADD IBM1S506.AD_ 12 08/18/97 19:13 65272
IBM2AMB1.SYS IBM2AMB1.SY_ 13 08/18/97 19:24 12453
IBM2AST1.SYS IBM2AST1.SY_ 13 08/18/97 19:24 10047
IBM2CAD1.SYS IBM2CAD1.SY_ 13 08/18/97 19:26 12495
IBM2CMQ1.SYS IBM2CMQ1.SY_ 13 08/18/97 19:24 10101
IBM2FLPY.ADD IBM2FLPY.AD_ 13 08/18/97 18:49 14420
IBM2MAT1.SYS IBM2MAT1.SY_ 13 08/18/97 19:25 10083
IBM2NCR1.SYS IBM2NCR1.SY_ 13 08/18/97 19:25 10063
IBM2NEC1.SYS IBM2NEC1.SY_ 13 08/18/97 19:25 10063
IBM2SCSI.ADD IBM2SCSI.AD_ 12 08/18/97 18:50 33161
IBM2SS01.SYS IBM2SS01.SY_ 13 08/18/97 20:18 27087
IBM2SS02.SYS IBM2SS02.SY_ 13 08/18/97 20:18 22835
IBM2TOS1.SYS IBM2TOS1.SY_ 13 08/18/97 19:24 10054
IBM2ZEN1.SYS IBM2ZEN1.SY_ 13 08/18/97 19:23 10047
IBM2ZOS1.SYS IBM2ZOS1.SY_ 13 08/18/97 19:25 10079
IBM4612.SYS IBM4612.SY_ 13 10/29/97 18:40 10180
IBMIDECD.FLT IBMIDECD.FL_ 13 08/18/97 19:14 23900
IBMKBD.SYS IBMKBD.SY_ 13 11/14/96 10:47 7770
ICMEMCDD.SYS ICMEMCDD.SY_ 13 10/14/97 10:55 13932
ICMEMFMT.EXE ICMEMFMT.EX_ 12 10/14/97 10:55 44276
ICMEMMTD.SYS ICMEMMTD.SY_ 13 10/14/97 10:55 7788
IFGDI2VM.DRV IFGDI2VM.DR_ 12 11/04/97 15:31 86392
INSTALL.EXE INSTALL.EX_ 6 11/18/97 16:41 384722
INST_DOS.EXE INST_DOS.EX_ 12 10/22/97 23:18 36466
IPSRAID.ADD IPSRAID.AD_ 13 06/28/97 11:01 19894
FixPak Corrective Service levels and disk layouts 28
December 2, 1997 - Warp 4 FixPak XRGM005
ISGDI2VM.DRV ISGDI2VM.DR_ 12 11/04/97 14:28 85072
KBDBASE.SYS KBDBASE.SY_ 12 07/25/97 16:15 34133
KERNEL.SDF KERNEL.SD_ 12 11/07/96 21:11 467330
KERNELD.SDF KERNELD.SD_ 12 11/07/96 21:12 468657
KEYBOARD.DCP KEYBOARD.DC_ 12 11/24/97 18:28 275644
LIBC.MSG LIBC.MS_ 13 11/24/97 17:34 9590
LIBCM.DLL LIBCM.DL_ 8 10/07/97 00:18 210916
LIBCN.DLL LIBCN.DL_ 11 10/07/97 00:18 57340
LIBCREG.MSG LIBCREG.MS_ 13 11/24/97 17:34 760
LIBCS.DLL LIBCS.DL_ 8 10/07/97 00:18 192386
LIBUNI.DLL LIBUNI.DL_ 11 11/02/97 02:55 80650
LMS206.ADD LMS206.AD_ 12 08/18/97 19:15 38706
LOCALE.DLL LOCALE.DL_ 11 11/02/97 02:55 65688
MIGRATE.EXE MIGRATE.EX_ 10 11/18/97 17:06 118761
MINXOBJ.DLL MINXOBJ.DL_ 12 11/18/97 19:04 31778
MIRRORS.DLL MIRRORS.DL_ 5 09/19/96 15:53 444744
MITFX001.ADD MITFX001.AD_ 13 08/18/97 19:09 20492
MMODPTS.DLL MMODPTS.DL_ 8 11/11/97 17:13 184020
MMPARTS.DLL MMPARTS.DL_ 1 11/18/97 16:46 1532246
MMPM.DLL MMPM.DL_ 6 11/18/97 16:52 430793
MOUSE.SYS MOUSE.SY_ 13 08/18/97 19:15 19587
NAMEADD.EXE NAMEADD.EX_ 13 10/28/97 16:34 23040
NAMECOPY.EXE NAMECOPY.EX_ 13 10/28/97 16:34 23040
NAMECSSP.DLL NAMECSSP.DL_ 11 11/14/97 18:12 61123
NAMEDEL.EXE NAMEDEL.EX_ 13 10/28/97 16:34 23040
NAMEDSP.DLL NAMEDSP.DL_ 9 11/14/97 18:12 123427
NAMEEXT.EXE NAMEEXT.EX_ 13 10/28/97 16:34 23040
NAMEFT.DLL NAMEFT.DL_ 11 11/14/97 18:12 66274
NAMEFW.DLL NAMEFW.DL_ 10 11/14/97 18:12 72312
NAMEINFO.DLL NAMEINFO.DL_ 2 11/14/97 18:12 47973
NAMEINI.DLL NAMEINI.DL_ 11 11/14/97 18:12 59027
NAMEMOD.EXE NAMEMOD.EX_ 13 10/28/97 16:34 23040
NAMEMOVE.EXE NAMEMOVE.EX_ 13 10/28/97 16:34 23040
NAMEOSP.DLL NAMEOSP.DL_ 7 11/14/97 18:12 52725
NWIAPI.DLL NWIAPI.DL_ 13 10/10/97 05:52 14800
OREXUTIL.DLL ORXUTIL2.DL_ 12 06/06/97 13:17 28885
OS2ASPI.DMD OS2ASPI.DM_ 13 08/18/97 18:47 11096
OS2CDROM.DMD OS2CDROM.DM_ 13 08/18/97 19:06 27356
OS2CHAR.TDF OS2CHAR.TD_ 13 11/18/97 16:25 13194
OS2DASD.DMD OS2DASD.DM_ 12 08/18/97 18:46 35434
OS2DUMP OS2DUMP.___ 13 10/03/97 15:51 17335
OS2K386.EXE OS2K386.EX_ 11 09/02/97 17:00 80674
OS2KRNL OS2KRNL.___ 3 11/18/97 15:59 599579
OS2KRNL.TDF OS2KRNL.TD_ 13 11/18/97 15:59 13992
OS2KRNLD.SYM OS2KRNLD.SY_ 9 11/18/97 16:08 180196
OS2KRNLR.SYM OS2KRNLR.SY_ 10 11/18/97 15:59 163220
OS2LDR.MSG OS2LDR.MS_ 13 11/18/97 15:44 9779
OS2NS.EXE OS2NS.EX_ 11 11/14/97 18:34 44964
OS2SCSI.DMD OS2SCSI.DM_ 13 08/18/97 18:46 11614
OSO001.MSG OSO001.MS_ 8 11/18/97 15:07 220233
OSO001H.MSG OSO001H.MS_ 1 11/18/97 15:07 294967
FixPak Corrective Service levels and disk layouts 29
December 2, 1997 - Warp 4 FixPak XRGM005
PARALLEL.PDR PARALLEL.PD_ 13 11/18/97 19:54 15944
PCIBUS.SNP PCIBUS.SN_ 13 10/14/97 10:55 2496
PCM2ATA.ADD PCM2ATA.AD_ 13 08/18/97 20:14 27938
PCMCIA.SYS PCMCIA.SY_ 12 08/18/97 20:12 48646
PCMCIA.TBL PCMCIA.TB_ 13 04/03/97 13:55 4100
PMATM.DLL PMATM.DL_ 3 10/02/97 17:19 340039
PMCHKDSK.DLL PMCHKDSK.DL_ 13 11/18/97 18:29 5151
PMCHKDSK.EXE PMCHKDSK.EX_ 12 11/18/97 18:29 28183
PMCLIP.DLL PMCLIP.DL_ 13 10/22/97 23:19 21295
PMCTLS.DLL PMCTLS.DL_ 5 11/18/97 17:09 582642
PMCTLS.SYM PMCTLS.SY_ 12 11/18/97 17:09 43860
PMDDE.DLL PMDDE.DL_ 12 11/18/97 17:44 28342
PMDDEML.DLL PMDDEML.DL_ 12 10/19/97 14:02 27298
PMDF.EXE PMDF.EX_ 7 11/18/97 18:17 232952
PMDRAG.DLL PMDRAG.DL_ 13 11/18/97 17:09 1731
PMGPI.DLL PMGPI.DL_ 7 11/05/97 16:07 229054
PMGPI.TDF PMGPI.TD_ 13 11/05/97 16:07 10913
PMGRE.DLL PMGRE.DL_ 13 10/20/97 14:43 2231
PMGRE.TDF PMGRE.TD_ 13 11/06/97 17:25 1062
PMMERGE.DLL PMMERGE.DL_ 2 11/18/97 17:12 1219619
PMMERGE.SYM PMMERGE.SY_ 10 11/06/97 17:25 115092
PMMLE.DLL PMMLE.DL_ 13 10/22/97 22:56 673
PMPRINT.QPR PMPRINT.QP_ 13 11/18/97 19:15 11817
PMSDMRI.DLL PMSDMRI.DL_ 13 11/18/97 17:09 12800
PMSEEK.EXE PMSEEK.EX_ 12 11/18/97 18:29 31285
PMSHAPI.DLL PMSHAPI.DL_ 13 10/22/97 22:53 4549
PMSHAPI.TDF PMSHAPI.TD_ 13 11/06/97 17:25 6187
PMSPL.DLL PMSPL.DL_ 7 11/18/97 19:13 274374
PMSPL.SYM PMSPL.SY_ 12 11/18/97 19:13 32196
PMSPL.TDF PMSPL.TD_ 13 11/18/97 19:13 4549
PMVDMP.DLL PMVDMP.DL_ 12 11/18/97 17:45 43317
PMVIOP.DLL PMVIOP.DL_ 11 11/18/97 17:45 59058
PMVIOP.SYM PMVIOP.SY_ 13 11/18/97 17:45 6596
PMWIN.DLL PMWIN.DL_ 13 11/18/97 17:01 11264
PMWIN.TDF PMWIN.TD_ 13 11/06/97 17:25 12612
PMWIN32.SDF PMWIN32.SD_ 12 10/28/97 18:56 299617
PMWINX.DLL PMWINX.DL_ 5 11/18/97 17:39 529951
PMWP.DLL PMWP.DL_ 3 11/18/97 18:56 923419
PMWP.SYM PMWP.SY_ 11 11/18/97 18:56 100308
PMWPMRI.DLL PMWPMRI.DL_ 11 11/18/97 18:57 57381
PNP.DLL PNP.DL_ 12 11/18/97 19:30 28297
PNP.SYS PNP.SY_ 13 08/18/97 19:39 2152
POINTDD.SYS POINTDD.SY_ 13 08/18/97 19:29 2823
PRINT01.SYS PRINT01.SY_ 13 07/25/97 16:26 12590
PRINT02.SYS PRINT02.SY_ 13 07/25/97 16:26 11766
PSSDMON.EXE PSSDMON.EX_ 12 10/08/97 11:44 25981
PSTAT.EXE PSTAT.EX_ 13 11/18/97 18:22 10339
QUECALLS.DLL QUECALLS.DL_ 13 10/03/97 03:01 1024
QUECALLS.TDF QUECALLS.TD_ 13 11/18/97 16:25 1299
RAS001.MSG RAS001.MS_ 13 11/18/97 18:00 32532
README.CID README.CI_ 12 11/18/97 13:58 67377
FixPak Corrective Service levels and disk layouts 30
December 2, 1997 - Warp 4 FixPak XRGM005
REGCONV.EXE REGCONV.EX_ 11 11/24/97 17:34 39446
REGEDIT.HLP REGEDIT.HL_ 13 08/22/97 18:24 22682
REGEDIT2.EXE REGEDIT2.EX_ 4 11/24/97 17:35 950784
REGISTRY.DLL REGISTRY.DL_ 12 10/28/97 16:31 81438
REGISTRY.MSG REGISTRY.MS_ 13 11/24/97 17:35 731
REGISTRY.TDF REGISTRY.TD_ 13 10/28/97 16:31 7616
RESERVE.SYS RESERVE.SY_ 13 08/18/97 18:42 5704
RESTORE.EXE RESTORE.EX_ 12 11/18/97 18:31 36928
REX.MSG REX.MS_ 13 09/19/96 15:44 2865
REXX.DLL REXX.DL_ 8 06/11/97 00:34 266015
REXX.IMG REXX.IM_ 11 03/31/97 17:35 274220
REXXAPI.DLL REXXAPI.DL_ 12 03/31/97 17:35 29091
REXXC.EXE REXXC.EX_ 13 03/31/97 17:35 1980
REXXCRT.DLL REXXCRT.DL_ 11 03/31/97 17:35 61195
REXXUTIL.DLL REXXUTIL.DL_ 12 06/11/97 00:34 29689
REXXUTIL.DLL ORXUTIL1.DL_ 12 06/06/97 13:17 28885
RSPDSPI.EXE RSPDSPI.EX_ 10 11/18/97 17:07 95848
RSPINST.EXE RSPINST.EX_ 4 11/18/97 16:51 429024
RSRV.EXE RSRV.EX_ 10 11/14/97 18:34 78051
SBCD2.ADD SBCD2.AD_ 13 08/18/97 19:09 18820
SCENTER.DLL SCENTER.DL_ 7 11/18/97 20:02 291647
SEAMLESS.DLL SEAMLESS.DL_ 12 11/18/97 17:46 49167
SECUTIL.DLL SECUTIL.DL_ 13 10/08/97 11:43 21468
SEINST.EXE SEINST.EX_ 12 11/18/97 16:37 37441
SEMAINT.EXE SEMAINT.EX_ 11 11/18/97 16:37 67696
SERIAL.PDR SERIAL.PD_ 13 11/18/97 19:04 19180
SESAPI.DLL SESAPI.DL_ 12 10/08/97 11:42 24283
SESDD32.SYS SESDD32.SY_ 11 10/08/97 11:45 127568
SESMGR.DLL SESMGR.DL_ 13 10/03/97 02:59 1536
SESMGR.TDF SESMGR.TD_ 13 11/18/97 16:25 1643
SETBOOT.EXE SETBOOT.EX_ 13 11/18/97 18:27 16546
SETDEFV.CMD SETDEFV.CM_ 13 12/13/96 11:23 1652
SOFTDRAW.DLL SOFTDRAW.DL_ 6 10/19/97 13:42 413271
SONY31A.ADD SONY31A.AD_ 12 08/18/97 19:11 32738
SPCHOBJ.DLL SPCHOBJ.DL_ 9 04/01/97 15:35 132899
SPL1B.DLL SPL1B.DL_ 13 10/10/97 05:51 5077
SS2PCIC1.SYS SS2PCIC1.SY_ 13 08/18/97 20:17 19087
SS2TCIC1.SYS SS2TCIC1.SY_ 13 08/18/97 20:17 22824
SSMDD.SYS SSMDD.SY_ 13 11/18/97 16:14 36813
SVMC.DLL SVMC.DL_ 10 11/18/97 16:19 97785
SVSH.DLL SVSH.DL_ 12 11/18/97 16:20 23452
SYMB.PFM SYM1.PF_ 13 10/10/97 01:03 679
SYSINSTX.COM SYSINSTX.CO_ 12 11/18/97 18:22 39472
SYSLEVEL.FPK SYSLEVEL.FP_ 13 10/09/97 15:15 165
SYSLOGPM.EXE SYSLOGPM.EX_ 9 11/18/97 18:00 138955
SYSTEM.TDF SYSTEM.TD_ 13 11/18/97 18:32 18358
SYSTEM.TFF SYSTEM.TF_ 13 11/18/97 18:32 45067
TEDIT.EXE TEDIT.EX_ 13 11/18/97 18:32 9506
TEDIT.HLP TEDIT.HL_ 13 11/18/97 13:58 14596
TESTCFG.SYS TESTCFG.SY_ 13 08/18/97 19:31 9808
TNR.OFM TNR.OF_ 13 10/10/97 01:03 4867
FixPak Corrective Service levels and disk layouts 31
December 2, 1997 - Warp 4 FixPak XRGM005
TNR.PFB TNR.PF_ 8 10/10/97 01:03 124390
TNR.PFM TN1.PF_ 13 10/10/97 01:03 1156
TNRB.OFM TNRB.OF_ 13 10/10/97 01:03 4883
TNRB.PFB TNRB.PF_ 8 10/10/97 01:03 126116
TNRB.PFM TNR1.PF_ 13 10/10/97 01:03 1165
TNRBI.OFM TNRBI.OF_ 13 10/10/97 01:03 4897
TNRBI.PFB TNRBI.PF_ 5 10/10/97 01:03 139122
TNRBI.PFM TNRB1.PF_ 13 10/10/97 01:03 1171
TNRI.OFM TNRI.OF_ 13 10/10/97 01:03 4888
TNRI.PFB TNRI.PF_ 8 10/10/97 01:03 135239
TNRI.PFM TNR2.PF_ 13 10/10/97 01:03 1167
TRACEDLL.DLL TRACEDLL.DL_ 11 10/08/97 01:48 44555
TRACEFMT.EXE TRACEFMT.EX_ 9 11/18/97 18:11 127972
TRC0001.TFF TRC0001.TF_ 13 10/28/97 16:31 17414
TRC0003.TFF TRC0003.TF_ 13 12/12/96 17:56 1503
TRC0004.TFF TRC0004.TF_ 13 06/16/97 13:23 4754
TRC0005.TFF TRC0005.TF_ 13 11/18/97 16:08 30574
TRC0006.TFF TRC0006.TF_ 13 12/12/96 17:19 12356
TRC0007.TFF TRC0007.TF_ 13 08/18/97 18:46 1394
TRC0008.TFF TRC0008.TF_ 13 08/18/97 18:39 544
TRC0010.TFF TRC0010.TF_ 13 11/18/97 16:25 3638
TRC0016.TFF TRC0016.TF_ 13 11/18/97 16:25 1673
TRC0017.TFF TRC0017.TF_ 12 11/18/97 16:25 4799
TRC0018.TFF TRC0018.TF_ 13 11/18/97 16:25 37028
TRC006D.TFF TRC006D.TF_ 13 10/16/96 13:16 24181
TRC00C0.TFF TRC00C0.TF_ 13 11/06/97 17:25 13791
TRC00C2.TFF TRC00C2.TF_ 13 11/06/97 17:25 29873
TRC00C3.TFF TRC00C3.TF_ 13 11/06/97 17:25 3984
TRC00C4.TFF TRC00C4.TF_ 13 10/22/97 23:18 242
TRC00C5.TFF TRC00C5.TF_ 13 11/05/97 16:07 26439
TRC00C6.TFF TRC00C6.TF_ 13 11/18/97 19:13 6331
TRUETYPE.DLL TRUETYPE.DL_ 9 11/07/97 14:32 125573
UCDFS.DLL UCDFS.DL_ 13 11/18/97 16:14 13264
UCONV.DLL UCONV.DL_ 12 11/02/97 01:26 23841
UHPFS.DLL UHPFS.DL_ 11 11/18/97 18:11 107536
ULSACT01.MSG ULSACT01.MS_ 13 10/07/97 15:24 907
ULSCAU01.MSG ULSCAU01.MS_ 5 10/07/97 15:24 899
ULSDET01.MSG ULSDET01.MS_ 3 10/07/97 15:24 903
ULSERR01.MSG ULSERR01.MS_ 13 10/07/97 15:24 1967
USER.EXE USER.EX_ 7 09/02/97 17:02 278304
VBIOS.SYS VBIOS.SY_ 13 11/18/97 18:34 8192
VCDROM.SYS VCDROM.SY_ 13 10/14/97 10:55 6880
VCMOS.SYS VCMOS.SY_ 13 11/18/97 18:34 2272
VCOM.SYS VCOM.SY_ 13 10/14/97 10:55 12384
VDPMI.SYS VDPMI.SY_ 13 11/18/97 18:35 30624
VDPX.SYS VDPX.SY_ 13 11/18/97 18:35 26112
VDSK.SYS VDSK.SY_ 13 10/14/97 10:55 10384
VIDEOPMI.DLL VIDEOPMI.DL_ 9 10/22/97 14:56 42535
VIOCALLS.DLL VIOCALLS.DL_ 1 10/22/97 23:20 2048
VKBD.SYS VKBD.SY_ 13 10/14/97 11:51 25612
VLPT.SYS VLPT.SY_ 13 10/14/97 10:55 10113
FixPak Corrective Service levels and disk layouts 32
December 2, 1997 - Warp 4 FixPak XRGM005
VMAN.DLL VMAN.DL_ 12 11/10/97 17:23 25613
VMANWIN.SYS VMANWIN.SY_ 10 10/16/97 18:41 2880
VMOUSE.SYS VMOUSE.SY_ 13 10/14/97 10:55 18704
VPIC.SYS VPIC.SY_ 13 11/18/97 18:37 9894
VPRPMI.SYS VPRPMI.SY_ 13 08/12/96 05:19 4473
VTIMER.SYS VTIMER.SY_ 13 11/18/97 18:37 9936
VW32S.SYS VW32S.SY_ 13 11/18/97 18:38 18288
VWIN.SYS VWIN.SY_ 4 11/18/97 18:37 26896
WCFGMRI.DLL WCFGMRI.DL_ 7 11/18/97 19:03 3108
WD24B.DSP WD24B.DS_ 13 04/03/97 13:55 12050
WINCFG.DLL WINCFG.DL_ 13 11/18/97 19:03 12839
WINSCLIP.DLL WINSCLIP.DL_ 13 08/22/97 17:20 14848
WINSDDE.DLL WINSDDE.DL_ 13 08/22/97 17:20 17408
WINSHELD.EXE WINSHELD.EX_ 13 09/02/97 17:00 22016
WINSMSG.DLL WINSMSG.DL_ 13 08/22/97 17:20 27929
WPCLS.IMP WPCLS.IM_ 13 03/31/97 17:35 8661
WPCONFIG.DLL WPCONFIG.DL_ 7 11/18/97 19:03 235896
WPCONMRI.DLL WPCONMRI.DL_ 13 11/18/97 19:03 26158
WPHELP.HLP WPHELP.HL_ 4 11/18/97 15:57 922489
WPINET.DLL WPINET.DL_ 10 11/18/97 19:51 115384
WPMSG.HLP WPMSG.HL_ 12 11/18/97 15:57 56427
WPPRINT.DLL WPPRINT.DL_ 6 11/18/97 19:09 363252
WPPRINT.HLP WPPRINT.HL_ 11 11/18/97 19:10 84903
WPPRTMRI.DLL WPPRTMRI.DL_ 10 11/18/97 19:10 68675
WPREXX.IMP WPREXX.IM_ 13 03/31/97 17:35 6313
WPSINIT.WPS WPSINIT.WP_ 13 03/31/97 17:35 15877
WW.EXE WW.EX_ 13 04/01/97 15:37 8305
WWDLL.DLL WWDLL.DL_ 6 11/25/97 09:37 273149
WWHOOK.DLL WWHOOK.DL_ 12 07/23/97 11:58 27230
XCOPY.EXE XCOPY.EX_ 12 11/18/97 18:23 51920
*************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "IBM OS/2 Basisbetriebssystem"
Standard Edition 4.00
Fixpak name: XRGM005_ (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:
FixPak Corrective Service levels and disk layouts 33
December 2, 1997 - Warp 4 FixPak XRGM005
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
OS2LDR OS2LDR.___ 13 11/18/97 15:44 33280
*************************************************************
Product location on CSD: A:\FIX\OS2.3
Product name: "IBM OS/2 Basisbetriebssystem"
Standard Edition 4.00
Fixpak name: XRGM005_ (Country = Germany)
Pre-requisite CSD Level: XRG4010_
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
------------ ------------ ----- -------- ----- -------
OS2LDR OS2LDR.___ 13 10/31/97 10:05 33280
FixPak Corrective Service levels and disk layouts 34
December 2, 1997 - Warp 4 FixPak XRGM005
9.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 12MB Drive with most free space, holds deferred files
9.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE
Warning: Make sure you read and understand the following before
removing the Archive and Backup files and directories.
You can recover the space used for FixPak Archive and Backup files
as long as you understand that doing this prevents you from being
able to backout to the previous Backup or Archive level. If it
becomes necessary at a later time to backout a FixPak, the only way
you can do this is to reinstall Warp.
Do the following to delete the FixPak Backup and Archive files and
remove the files used by CSF to keep track of what service has been
applied to your system.
1. Delete every instance of the following files on your system
(search every drive and every directory they contain).
■ LOGF0000.* (can be OS2 or MPM)
■ LOGSTART.* (can be OS2 or MPM)
■ LOGARCH.* (can be OS2 or MPM)
■ CSF_*.*
■ FIXSTART
2. Delete the files in the FixPak Archive and Backup directories on
your harddisk.
3. Remove the FixPak Archive and Backup directories with the RMDIR
command.
Space Utilization 35