<![CDATA[< Installation instructions for Warp Server for e-business FixPak
XR_E001
April 25, 2000
This FixPak makes the products it services Year 2000 ready
Build level 14.040
This FixPak applies to:
CSD Level: XR_4500 Warp Server for e-business (UNI)
Component ID: 5639A6150
Version: 4.50
Type: 0S
CSD Level: XR_4500 Warp Server for e-business (SMP)
Component ID: 5639A5550
Version: 4.50
Type: 0S
Requires Corrective Service Facility release f.142 or later
OS/2 Fix Distribution
Personal System Products
Austin, Tx
(c) Copyright International Business Machines Corporation, 1981, 1998.
All rights Reserved.
April 25, 2000 - Warp Server for e-business FixPak XR_E001
April 25, 2000 - Warp Server for e-business FixPak XR_E001
CONTENTS
1.0 Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Do not use your system . . . . . . . . . . . . . . . . . . . . . 2
3.0 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . 3
4.0 Platform Specific Drivers (PSDs) . . . . . . . . . . . . . . . . 4
4.0.1 Please use Fixtool f.142 or later . . . . . . . . . . . . . 6
4.0.2 Using Display Recovery Choices . . . . . . . . . . . . . . . 6
4.0.3 No products found . . . . . . . . . . . . . . . . . . . . . 6
4.0.4 Previous installation interrupted . . . . . . . . . . . . . 7
4.0.5 Unable to open Archive directory . . . . . . . . . . . . . . 7
4.0.6 CSF0208 No products were found on the target ... . . . . . 8
4.0.7 CSF0249 Error opening or creating archive file. . . . . . . 8
4.0.8 Printer installation process change . . . . . . . . . . . . 8
4.0.9 Configuration Installation Distribution ( CID ) . . . . . . 8
5.0 Post Installation Notes . . . . . . . . . . . . . . . . . . . . 9
6.0 New Function . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1 New RAS Utilities added . . . . . . . . . . . . . . . . . . . . 10
6.2 JFS lazywrite parameters on the IFS= line in config.sys . . . . 10
6.3 Graphics Adapter Device Drivers (GRADD) . . . . . . . . . . . . 11
6.4 REXX New Function . . . . . . . . . . . . . . . . . . . . . . . 11
6.5 Other README files . . . . . . . . . . . . . . . . . . . . . . 12
7.0 Corrective Service Facility . . . . . . . . . . . . . . . . . . 13
7.0.1 Required CSF level . . . . . . . . . . . . . . . . . . . . 13
7.0.2 Where you can find CSF code . . . . . . . . . . . . . . . . 13
7.0.3 Creating FixPak diskettes . . . . . . . . . . . . . . . . . 14
7.1 Read-Only files . . . . . . . . . . . . . . . . . . . . . . . . 14
7.2 SYSLEVEL file locations . . . . . . . . . . . . . . . . . . . . 15
7.3 Relocated Warp Server for e-business file support . . . . . . . 15
8.0 Installation Process . . . . . . . . . . . . . . . . . . . . . 17
8.1 Before installation . . . . . . . . . . . . . . . . . . . . . . 17
8.2 Method 1: Install from booted OS/2 partition. . . . . . . . . 17
8.3 Method 2: Install from alternate bootable media . . . . . . . . 18
8.4 Additional Corrective Service Facility information . . . . . . 19
9.0 CSD level of SYSLEVEL.OS2 . . . . . . . . . . . . . . . . . . . 20
9.0.1 FixPak Syslevel File . . . . . . . . . . . . . . . . . . . 20
10.0 FixPak Corrective Service levels and disk layouts . . . . . . 21
11.0 Space Utilization . . . . . . . . . . . . . . . . . . . . . . 28
11.0.1 Recovering FixPak ARCHIVE and BACKUP space . . . . . . . . 28
11.0.2 TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . 29
Contents ii
April 25, 2000 - Warp Server for e-business FixPak XR_E001
1.0 TERMS AND CONDITIONS
Important - please read the following terms and conditions.
Downloading the Service Fixes included in FixPak XR_E001 for Warp Server
for e-business indicates your acceptance of the following terms and
conditions:
1. You must be, and agree that you are, a current licensee of Warp Server
for e-business.
2. You may make copies of the Warp Server for e-business Service Fixes
equal to the number of licensed copies of Warp Server for e-business
you possess.
3. You may only use the Warp Server for e-business Service Fixes included
with FixPak XR_E001 for maintenance purposes.
4. All other terms and conditions of your Warp Server for e-business
license agreements apply to the Service Fixes; however, this does not
extend any warranty and/or services, including but not limited to the
"Initial Installation" period, outlined in such agreements.
Terms and Conditions 1
April 25, 2000 - Warp Server for e-business FixPak XR_E001
2.0 DO NOT USE YOUR SYSTEM
Once you begin a FixPak installation, do not try to use your system for
any other purpose. Doing so may yield unexpected problems which can cause
the FixPak installation to fail.
Do not use your system 2
April 25, 2000 - Warp Server for e-business FixPak XR_E001
3.0 INSTALLATION NOTES
Installation Notes 3
April 25, 2000 - Warp Server for e-business FixPak XR_E001
4.0 PLATFORM SPECIFIC DRIVERS (PSDS)
In Warp Server for e-business SMP, we have removed all the platform
specific code from the operating system, and placed it into platform
specific drivers. These drivers provide an abstraction layer for the
underlying hardware by allowing the OS to call generic functions to
perform platform specific operations without worrying about the actual
hardware implementation. This allows us to support new platforms without
modifying the operating system.
PSD's are specified in CONFIG.SYS by using the PSD keyword, and must
conform to the 8.3 file naming convention (e.g. PSD=BELIZE.PSD). They
cannot contain either drive, or path information because OS/2 cannot
process such information at the stage of the startup sequence when the
PSD statements are processed. The root directory of the startup
partition is first searched for the specified file name, then the \OS2
directory of the startup partition. If drive or path information is
included in a PSD statement, an error is generated.
PSD parameters may be specified after the PSD's name, and may be a
maximum of 1024 characters long. The parameter string is not interpreted,
or parsed by OS/2, it is passed verbatim, as an ASCIIZ string when the
PSD's Install function is invoked.
If multiple PSD statements are encountered. OS/2 will load each PSD in
the order listed in CONFIG.SYS, and call the PSD's install function. The
first PSD which successfully installs, will be the one OS/2 uses.
PSD statements are processed before BASEDEV, IFS, and DEVICE statements.
Please note that any time you add or make changes to the CONFIG.SYS file,
you must restart the system in order for the changes to become effective.
The CONFIG.SYS file is read only during system startup. Anything added to
this file after system initialization does not work until you restart the
system.
This PSD has the following syntax for its argument line:
[/apic] [/p=<n>] [/nmi=[l]int<n>] [/pic=[l]int<n>] [/prec=<pstr>]
Where:
/apic indicates that the PSD should enable symetric interrupt
mode.
/p indicates that the system should be configured for <n>
processors where <n> is a decimal number (ie 5, 8, 12).
/nmi indicates to the system a default signal route for NMIs.
This allows the route to be specified for NMIs if there
isn't one defined by the MP configuration tables set up
by BIOS.
Platform Specific Drivers (PSDs) 4
April 25, 2000 - Warp Server for e-business FixPak XR_E001
By using the /prec option (see below), it is possible to
override what is in the MP configuration tables in the
event that they have been built incorrectly by the BIOS.
The argument is "int<n>" or "lint<n>". The first case
indicates the interrupt pin number to which the NMI signal
is wired on the I/O apic. The second case indicates the
interrupt poin number to which the NMI signal is wired on
the local apic. <n> is a decimal number (ie 0, 3, 12).
/pic indicates to the system a default signal route for the
8259 interrupt controller when the system is running in
"virtual wire" mode. This allows the route to be specified
for the interrupt controller if there isn't one defined by
the MP configuration tables set up by BIOS. By using the
/prec option (see below), it is possbile to override what is
in the MP configuration tables in the event that they have
been built incorrectly by the BIOS.
/prec indicates to the system the precedence order to be used in
determining the routing for the NMI signal and the
interrupt signal from the interrupt controller. This
allows control over the choosing of a routing entry when
there is more than one entry.
There are three (3) possible entries that can describe a
route:
route to the I/O APIC
route to the Local APIC
route described by argument(s) to the PSD
The first two may be specified in the MP configuration tables
that are built by the BIOS. The third may be specified on the
argument line to the PSD.
Each type of route is described by one letter. "i" for the
I/O APIC routes, "l" for the local APIC routes, and "d" for
the routes described by the argument line to the PSD.
The precedence string is *exactly* 3 characters long. The
first character indicates the type of routes to be considered
first, the second indicates the routes to be considered next
and the third indicates the routes that are to be considered
last.
As an example, "ild" indicates that I/O APIC routes are to
considered first, followed by local APIC routes and finally
routes specified on the argument line. In contrast, "dil"
indicates that routes on the argument line are to be considered
first, then the I/O APIC and finally the local APIC.
Platform Specific Drivers (PSDs) 5
April 25, 2000 - Warp Server for e-business FixPak XR_E001
Note: The arguments to the PSD are NOT case sensitive.
4.0.1 PLEASE USE FIXTOOL F.142 OR LATER
For Warp Server for e-business FixPak 01, you must use Corrective Service
Facility f.142 or later.
If you try to use a CSF level prior to f.142 you may get a "CSF0208 No
products were found on the target system to service" message.
4.0.2 USING DISPLAY RECOVERY CHOICES
If you have the "Display Recovery Choices at each system startup"
function active on your system, you need to disable it before you apply a
FixPak if
þ The system is running
þ The boot partition will be serviced.
The problem with using this function is that the Corrective Service
Facility (CSF) updates the current CONFIG.SYS with entries to run the
Locked File Device Driver (LFDD) the next time you boot the system. This
is done to replace files that are currently in use (locked) by the
system.
The Recovery choices function replaces the current CONFIG.SYS with the
one that is associated with the recovery choice you select, wiping out
the LFDD entries. This means the LFDD does not run at boot time and the
deferred files will not get updated, therefore the FixPak does not get
completely applied.
Note: It is not necessary to disable this function if you install a
FixPak by booting from the CSF disks or from another OS/2 partition.
4.0.3 NO PRODUCTS FOUND
If you see a "No products were found on the target system to service"
message while applying this FixPak, there is probably a mismatch between
the data in \OS2\INSTALL\SYSLEVEL.OS2 and what is supported by this
FixPak.
Compare the data for the Warp Server for e-business 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.
Platform Specific Drivers (PSDs) 6
April 25, 2000 - Warp Server for e-business FixPak XR_E001
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.
4.0.4 PREVIOUS INSTALLATION INTERRUPTED
If you get a message that the previous installation of a FixPak was
interrupted (whether true or not), check for the following files and
directory on all drives:
Files:
FIXSTART
IBMCSFLK.LST
IBMCSFLK.CSF
CSF_*
Directory:
IBMCSFLK
If any exist, rename them and try the FixPak installation again. Delete
the renamed files after the FixPak has been applied.
4.0.5 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.
Platform Specific Drivers (PSDs) 7
April 25, 2000 - Warp Server for e-business FixPak XR_E001
To recover from this, follow the "No files to service" and "Previous
installation interrupted" steps listed above.
4.0.6 CSF0208 NO PRODUCTS WERE FOUND ON THE TARGET ...
This means no SYSLEVEL files was found that had a CSD Level, COMPID,
Version and Type that matched any of the SYSLEVEL files supported by this
FixPak. Run the SYSLEVEL command and record the output for SYSLEVEL.OS2
in the OS2/INSTALL directory on your boot drive. Compare this data with
the data contained in the README.1ST file on FixPak disk 1.
To recover from this, rename the existing SYSLEVEL.OS2 file to SYSL.OS2
and copy SYSLEVEL.OS2 from your Warp Server for e-business found on
installation DISK 1.
4.0.7 CSF0249 ERROR OPENING OR CREATING ARCHIVE FILE.
Typically this means the FixPak Archive directory has been deleted but
the files that point to it still exist. You need to delete the
LOGF000.OS2 and LOGSTART.OS2 files from your OS2/INSTALL directory.
LOGSTART.OS2 has the R/O attribute set and it needs to be reset before
the file can be deleted. There may also be a LOGARCH.OS2 file that needs
to be deleted.
This can also occur for Multi Media Presentation Manager/2 (MMPM). You
would then need to delete the LOGF0000.MPM and LOGSTART.MPM files from
the \MMOS2\INSTALL directory and possibly LOGARCH.MPM if it exists.
4.0.8 PRINTER INSTALLATION PROCESS CHANGE
If you install a new printer by clicking MB2 on the Printer icon in the
templates folder then clicking on Install, the printer object will now be
created in the Printer folder, not on the Desktop.
4.0.9 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.
Platform Specific Drivers (PSDs) 8
April 25, 2000 - Warp Server for e-business FixPak XR_E001
5.0 POST INSTALLATION NOTES
Post Installation Notes 9
April 25, 2000 - Warp Server for e-business FixPak XR_E001
6.0 NEW FUNCTION
It is our policy not to include new function in FixPaks. However, as with
any policy there may be exceptions. If any exception occurs in the
future, we will communicate them to you in this section of the
README.1ST.
6.1 NEW RAS UTILITIES ADDED
Two new RAS utilities are included for Pak 01: PSFILES.EXE and
PSSEMS.EXE.
PSFILES.EXE can dump out information about open files on the system. By
default, it dumps out the information for all processes. Alternately,
"PSFILES xxx" will dump out information for PID xxx (xxx is a hex number,
e.g. from PSTAT).
PSSEMS.EXE can dump out information about open 32 bit semaphores on the
system By default it prints out all the shared (i.e. system-wide)
semaphores. Usage is: pssems [/n] [hex_pid | /a] ; where /n suppresses
shared semaphores and /a prints pruivate sems for all system processes.
Note: These RAS Utilities are added to the OS2 directory on your system.
6.2 JFS LAZYWRITE PARAMETERS ON THE IFS= LINE IN CONFIG.SYS
IFS=jfs.ifs /L:OFF
IFS=jfs.ifs /L:synctime,maxage,bufferidle
(JFS ignores any characters between the L (or l) and the colon, so valid
flags are /L: /LAZY: /LW: /lazywrite: etc.)
OFF forces asynchonous writes to be immediately initiated.
synctime is the interval at which the sync thread runs. Default = 64
maxage is the longest time that a frequently modified file is kept in
cache
default = synctime*4
bufferidle is the time indicating a "recent" change. Changes newer than
this value are not written unless the last write was older than
maxage. default = MIN(1,synctime/8)
(All parameters in seconds)
New Function 10
April 25, 2000 - Warp Server for e-business FixPak XR_E001
IFS=C:\OS2\JFS.IFS /L:64
synctime = 32, maxage = 128, bufferidle = 4
IFS=C:\OS2\JFS.IFS /LW:10,60,5
synctime = 10, maxage = 60, bufferidle = 5
IFS=C:\OS2\JFS.IFS /LAZYWRITE:4,60
synctime = 4, maxage = 60, bufferidle = 1
IFS=C:\OS2\JFS.IFS /lazy:off
All writes initiated immediately (synctime=1, maxage=bufferidle=0)
Note: sync thread still runs since trivial things like marking an
inode accessed are still deferred.
The cachejfs.exe command allows the lazywrite parameters to be changed
immediately. The syntax is to the IFS line, except that the /L: prefix
is optional. In addition, the cachejfs command can modify the minimum
and maximum number of free cache buffers to be maintained. Calling
cachejfs with no parameters reports the current settings.
CACHEJFS [[/LAZYWRITE:]{OFF|syncTime[,maxAge[,bufferIdle]]}]
/MINFREE:minfree
/MAXFREE:maxfree
6.3 GRAPHICS ADAPTER DEVICE DRIVERS (GRADD)
Future updates for GRADD and other video drivers (when they are released)
will be found via the internet at:
þ http://service.software.ibm.com/pslaunch.html
6.4 REXX NEW FUNCTION
New Function has been added in REXX. Please see the "Other README Files"
for documentation pointers. This new function was added to FP 1 and
later.
New Function 11
April 25, 2000 - Warp Server for e-business FixPak XR_E001
6.5 OTHER README FILES
There are other README files containing information you may want to
review. All README files are found on the first FixPak disk and are not
copied to your system when the Fixpak is installed.
File Use
README2 Problems fixed in each FixPak (APAR list)
README.CID Installing FixPaks via CID
README.DBG Description of Debug files for Warp Server for e-business
debugging.
READREXX.TXT New RexxUtil Function documentation added in this FixPak.
New Function 12
April 25, 2000 - Warp Server for e-business FixPak XR_E001
7.0 CORRECTIVE SERVICE FACILITY
7.0.1 REQUIRED CSF LEVEL
You should use release level f.142 or later of the OS/2 Corrective
Service Facility to install this FixPak.
Bootable diskettes are no longer provided starting with the F.138B CSF
build. Instead, you now get a self-extracting ZIP file which contains the
following:
archctl.cmd
build.lvl
csfpans.dll
filefix.dll
fpinst.cmd
fservice.exe
fservice.msg
ibmcsflk.dll
ibmcsflk.exe
ibmcsflk.msg
ibmcsflk.sys
msg.dll
nls.dll
pack.exe
read.me
readme.inf
response.lan
response.wp3
response.wp4
service.exe
service.hlp
shpiinst.dll
unpack.exe
unpack2.exe
viocalls.dll
Follow the directions in the READ.ME file to use the new CSF code. It
covers the use of SERVICE.EXE and FSERVICE.EXE from a booted partition or
from one of several alternative boot methods.
7.0.2 WHERE YOU CAN FIND CSF CODE
The Corrective Service Facility code is available from many places,
including, but not limited to, the following:
Source How to access
Corrective Service Facility 13
April 25, 2000 - Warp Server for e-business FixPak XR_E001
Internet(FTP) Anonymous FTP to ftp.software.ibm.com in the
"/ps/products/os2/fixtool" directory.
Internet(WWW) Point your Web Browser at
ftp://service.boulder.ibm.com/ps/products/os2/fixtool
Intranet(FTP) Anonymous FTP to os2service.austin.ibm.com in the
"f:\fixpacks\fixtool" directory.
7.0.3 CREATING FIXPAK DISKETTES
Use LOADDSKF.EXE to create the diskettes. For each disk image, place a
2MB HD (1.44MB formatted) diskette in A:.
Warning: DO NOT use a 1MB (720KB formatted) diskette because you might
have problems trying to install this FixPak.
For each diskette image in the FixPak, do the following:
Enter LOADDSKF XR_E001.?DK A: /F (? can be 1 through 9, A through Z).
Label the diskette as
FixPak XR_E001
Corrective Service Diskette ?
(CSF DISK ?)
Note: For diskette images ADK through ZDK, use the numbers 10 through 35.
Examples:
XR_E001.ADK = 10
XR_E001.FDK = 15
XR_E001.LDK = 21
etc.
7.1 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.
Corrective Service Facility 14
April 25, 2000 - Warp Server for e-business FixPak XR_E001
7.2 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
..\..\ all files in a directory two levels above (toward the
root). This should be the root directory of your boot
drive.
..\* all files in a directory one level above (toward the root)
and all subdirectories below. This should be the OS2
directory and subdirectories.
..\..\VT\* all files in the VT directory and subdirectories.
..\..\PSFONTS\* all files in the PSFONTS directory and subdirectories.
..\..\LANGUAGE\* all files in the LANGUAGE directory and subdirectories.
..\..\OPENDOC\* all files in the OPENDOC directory and subdirectories.
7.3 RELOCATED WARP SERVER FOR E-BUSINESS FILE SUPPORT
If you have moved Warp Server for e-business 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
Warp Server for e-business partition to be serviced.
In this file, place the full path to the directories you want to be
serviced. Assuming your boot drive is C: and you installed Multimedia
on the D: drive and manually moved WINOS2 support to the E: drive:
Corrective Service Facility 15
April 25, 2000 - Warp Server for e-business FixPak XR_E001
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 Warp Server for e-business FixPaks
you might apply. The easy way to create this file is to use the DIR
command with the /A:D /S /B parameters and pipe the output to a file.
dir d:\mmos2 /a:d /s /b > anyfile
Then copy that data into the USERDIRS.OS2 file.
With CSF release level F.142 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 16
April 25, 2000 - Warp Server for e-business FixPak XR_E001
8.0 INSTALLATION PROCESS
8.1 BEFORE INSTALLATION
Before installing any FixPak, run CHKDSK /F against all drives on your
system to correct any file system errors that might be present. You
cannot do this while OS/2 is active. You must shut down and run CHKDSK by
one of the following methods:
þ Boot from your Installation, DISK 1 and DISK 2 diskettes. If your
file system is HPFS, then put the diskette with CHKDSK and UHPFS.DLL
on it in your A: drive before issuing the CHKDSK command.
þ Boot from the Utilities disk you created via the "Create Utility
Diskettes" icon in the System Setup folder.
þ Boot from a different OS/2 partition.
Once CHKDSK has completed, reboot your system then shutdown all running
applications before starting the FixPak installation.
8.2 METHOD 1: INSTALL FROM BOOTED OS/2 PARTITION.
Note: CS_???.EXE below means CS_142 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Here are some additional notes:
Follow the displayed instructions. When prompted to insert Corrective
Service Diskette 1 (not CSF DISK Diskette 1), place FixPak XR_E001
Corrective Service Diskette 1 in drive A. Repeat for the rest of the
FixPak disks when requested to do so.
It can take a considerable length of time for the Corrective Service
Facility to scan your hard disk for serviceable files. In some cases, it
has taken as long as 40 minutes. Please be patient and allow this
process to complete.
If this is the first OS/2 Warp FixPak you have applied to this system,
then enter the path to the directory where a copy of replaced files will
be stored (for example, D:\ARCHIVE or E:\FIXPAK\ARC, etc.)
Note: This ARCHIVE directory is not related to the ARCHIVES directory
built into OS/2 Warp 3 and Warp 4. Please specify a different path. You
must specify a different ARCHIVE directory for each product to be
serviced.
Installation Process 17
April 25, 2000 - Warp Server for e-business FixPak XR_E001
If this is not the first OS/2 Warp FixPak, then enter the path to the
BACKUP directory where a copy of replaced files will be stored (for
example, D:\BACKUP).
Note: You must specify a different BACKUP directory for each product to
be serviced.
Make sure there is sufficient space available on the drive you specify
for archive or backup. Even though these files are kept in compressed
(PACK2) format, they can take up a lot of space on the drive.
During the installation process you may see messages about Archiving,
Updating and Deferring service.
þ Archiving saves a compressed copy of the original file in the ARCHIVE
or BACKUP path you specified.
þ Updating means the original files are replaced with the new ones from
this FixPak.
þ Deferring service means the file to be updated is currently in use by
the system and cannot be updated. The new files from the FixPak are
placed in unpacked format in the \IBMCSFLK\FIX directory on the drive
with the most free space. They are processed by the locked file
device driver during reboot after you shut down the system.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
You will see the following during reboot of the system if you applied
service to the OS/2 partition you were booted from.
The locked file driver is loaded.
Processing locked files
Processing complete
The system will do one automatic reboot after the Locked File Device
Driver has completed.
8.3 METHOD 2: INSTALL FROM ALTERNATE BOOTABLE MEDIA
Note: CS_???.EXE below means CS_142 or later.
Follow the instructions in the READ.ME file that comes in the CS_???.EXE
self-extracting zip file. This explains how to use the CS_???.EXE file
and the various ways you can install a FixPak with this level of CSF
code.
Installation Process 18
April 25, 2000 - Warp Server for e-business FixPak XR_E001
Here are some additional notes:
This method does not prompt the user for any information. No interaction
with the user takes place other than requests to put the next diskette in
drive A. All serviceable partitions on your system will be updated
automatically unless you have modified the default response file. Be
especially careful of extra SYSLEVEL.OS2 or SYSLEVEL.MPM files when using
this method because they can cause CSF to apply service to directories
you do not want serviced.
See the section "FixPak Corrective Service levels and disk layouts" for
the CSD levels this FixPak applies to.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. Please be
patient and allow this process to complete.
Note: You can edit the response file to control some of the actions taken
by FSERVICE.EXE while applying a FixPak. See the READ.ME file or use the
VIEW command to look at the file README.INF. They are part of
CS_???.EXE.
8.4 ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility, like how to
backout a FixPak, is available from the README.INF file on the first
Corrective Service Facility disk. To view this file, place CSF disk 1 in
drive A and enter VIEW A:\README.INF.
There is also some additional information in the READ.ME file.
Installation Process 19
April 25, 2000 - Warp Server for e-business FixPak XR_E001
9.0 CSD LEVEL OF SYSLEVEL.OS2
The Current CSD level field of the SYSLEVEL.OS2 file in each serviced
partition will be updated with the name of the FixPak when it is applied.
All fix information is recorded in SERVICE.LOG. Look at the file
\OS2\INSTALL\SERVICE.LOG
on your boot drive for information relating to the installation of
FixPaks on your system.
Additionally, you can use the VER /R command to see the current revision
of OS/2 installed. The response will look like the following for this
FixPak:
The Operating System/2 Version is 4.50
Revision 14.040
The first page of this document has a line that looks like:
Build Level: n.nnn
That is the number you should see for this FixPak when you issue the VER
/R command.
9.0.1 FIXPAK SYSLEVEL FILE
A SYSLEVEL.FPK will be added to the OS2\INSTALL directory when this
FixPak is installed. It is titled "OS/2 Warp Server for e-business
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 20
April 25, 2000 - Warp Server for e-business FixPak XR_E001
10.0 FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 14.040
Product location on CSD: A:\FIX\OS2.1
Product name: "Warp Server for e-business Base Operating System (UNI)"
Standard Edition 4.50
Fixpak name: XR_E001_ (Country = Generic)
Pre-requisite CSD Level: XR_4500_
System Id: 1000
Component Id: 5639A6150
Archive is ON for this product.
________________________________________________________________________
Product name: "Warp Server for e-business Base Operating System (SMP)"
Standard Edition 4.50
Fixpak name: XR_E001_ (Country = Generic)
Pre-requisite CSD Level: XR_4500_
System Id: 1000
Component Id: 5639A5550
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\TOPOBJ
..\..\TOPOBJ\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Will create the following directories
..\..\ Stub File: @ROOTDIR
..\..\OS2 Stub File: @OS2DIR
..\..\OS2\DLL Stub File: @DLLDIR
..\..\OS2\HELP Stub File: @HELPDIR
..\..\OS2\INSTALL Stub File: @INSTDIR
..\..\OS2\INSTALL\UNI Stub File: @UNIDIR
..\..\OS2\INSTALL\SMP Stub File: @SMPDIR
..\..\OS2\SYSTEM Stub File: @SYSTDIR
FixPak Corrective Service levels and disk layouts 21
April 25, 2000 - Warp Server for e-business FixPak XR_E001
..\..\OS2\PDPSI\PMDF\WARP45_U Stub File: @WARP45U
..\..\OS2\PDPSI\PMDF\WARP45_S Stub File: @WARP45S
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
ANSI.SYS ANSI.SY_ 10 01/21/2000 10:53 7480 C85F77C8
ATTRIB.EXE ATTRIB.EX_ 10 01/21/2000 10:44 37789 BA7F9FB9
CACHE.EXE CACHE.EX_ 10 02/16/2000 14:13 11822 07082540
CACHEJFS.EXE CACHEJFS.EX_ 10 04/05/2000 09:28 43882 83B0A6BA
CCHMAIN.EXE CCHMAIN.EX_ 7 03/29/2000 09:26 199344 4DDA5985
CHKDSK.COM CHKDSK.CO_ 9 01/21/2000 10:44 70720 77DCA279
CHKDSK.SYS CHKDSK.SY_ 10 02/16/2000 14:14 795 3BACAF48
CHKDSK32.DLL CHKDSK32.DL_ 8 02/16/2000 14:26 139227 FC293D21
CHKLGJFS.EXE CHKLGJFS.EX_ 9 04/05/2000 09:41 87435 810817FC
CLRBBLKS.EXE CLRBBLKS.EX_ 9 04/05/2000 09:27 34974 0805912D
CMD.EXE CMD.EX_ 8 01/21/2000 10:47 89888 B8C7C403
CREX.MSG CREX.MS_ 10 03/27/2000 14:23 2865 87F98E0E
CREXUTIL.DLL CREXUTIL.DL_ 9 03/27/2000 14:23 68119 4D4C3337
CREXX.DLL CREXX2.DL_ 7 03/27/2000 14:23 266031 E14B2A5F
DDINSTAL.EXE DDINSTAL.EX_ 10 03/15/2000 11:57 35367 DE1B5076
DEFRAGFS.EXE DEFRAGFS.EX_ 9 04/05/2000 09:41 33994 A20E887B
DF_DEB.EXE DF_DEB.SM_ 8 03/31/2000 09:47 145137 4A17810E
DF_DEB.EXE DF_DEB.UN_ 8 03/31/2000 11:01 137525 C32262A0
DF_RET.EXE DF_RET.SM_ 8 03/31/2000 09:00 145105 E8392A18
DF_RET.EXE DF_RET.UN_ 8 03/31/2000 08:45 137493 F1E3EF0D
DOSCALL1.DLL DOSCALL1.SM_ 7 03/31/2000 08:59 144786 004F89E4
DOSCALL1.DLL DOSCALL1.UN_ 7 03/31/2000 08:44 137513 A47B3279
DOSCALL1.SYM DOSC1SYM.SM_ 10 03/31/2000 08:59 43972 CE433291
DOSCALL1.SYM DOSC1SYM.UN_ 10 03/31/2000 08:44 43636 7AFBC145
DOSKRNL DOSKRNL.___ 10 03/31/2000 08:45 31497 CA319668
DSPIMRI.DLL DSPIMRI.DL_ 10 04/13/2000 10:33 25638 5C96CF0B
DSPINSTL.EXE DSPINSTL.EX_ 8 04/13/2000 10:33 174616 926BA9AA
E.EXE E.EX_ 9 03/15/2000 16:30 61159 8837D89B
EAUTIL.EXE EAUTIL.EX_ 10 01/21/2000 10:48 38000 FEAF15D2
ENGINE.DLL ENGINE.DL_ 10 04/05/2000 09:25 43330 1B93C929
ETKE603.DLL ETKE603.DL_ 5 11/23/1999 16:02 767421 C1741876
EXTENDFS.EXE EXTENDFS.EX_ 10 04/05/2000 09:41 29304 9C49402F
FFIPC.DLL FFIPC.DL_ 10 02/15/2000 11:49 27201 F844F092
FIBASE.RSP FIBASE.RS_ 9 04/02/2000 21:38 981855 A0FFF1FF
GRE2VMAN.DLL GRE2VMAN.DL_ 10 04/18/2000 09:40 20653 3414D7C7
GSVDAEMN.EXE GSVDAEMN.EX_ 10 01/28/2000 14:13 4848 657ECB28
GSVINST.EXE GSVINST.EX_ 10 03/15/2000 16:33 34351 DCF8E883
HELPMGR.DLL HELPMGR.DL_ 3 04/18/2000 10:09 277411 C976852D
HPFS.IFS HPFS.IF_ 8 02/16/2000 14:11 141378 E8BD99F9
HPFS.TDF HPFS.TD_ 10 02/16/2000 14:11 1620 57A464BE
INSCFG32.DLL INSCFG32.DL_ 10 03/15/2000 11:41 32530 6724883D
FixPak Corrective Service levels and disk layouts 22
April 25, 2000 - Warp Server for e-business FixPak XR_E001
INSTALL.EXE INSTALL.EX_ 6 03/16/2000 08:07 407227 5AE5418C
JAVA.RSP JAVA.RS_ 10 03/15/2000 11:19 453012 F7666E6D
JFS.IFS JFS.IF_ 7 04/05/2000 14:55 170664 307C8E3E
JFS.MSG JFS.MS_ 10 04/05/2000 09:26 12619 4763FB92
JFS.TDF JFS.TD_ 10 04/05/2000 14:55 16706 5414E862
JFSCHK32.EXE JFSCHK32.EX_ 10 04/05/2000 09:27 6493 09153474
JFSH.MSG JFSH.MS_ 10 04/05/2000 09:26 9515 4A628C35
KERNEL.SDF KRNLRSDF.SM_ 9 03/31/2000 09:00 59320 A77BDFDA
KERNEL.SDF KRNLRSDF.UN_ 9 03/31/2000 08:45 58993 74A851C7
KERNELD.SDF KRNLDSDF.SM_ 9 03/31/2000 09:47 59486 CB7D58E8
KERNELD.SDF KRNLDSDF.UN_ 9 03/31/2000 12:15 59138 6E02A1B6
KEYBOARD.DCP KEYBOARD.DC_ 10 12/02/1999 14:21 315109 639280C8
LOGDUMP.EXE LOGDUMP.EX_ 8 04/05/2000 09:41 78712 C8B4F97E
LVM.DLL LVM.DL_ 1 04/05/2000 09:22 148191 10495BA9
LVM.EXE LVM.EX_ 7 04/05/2000 09:48 92928 79541CE1
LVM.MSG LVM.MS_ 10 04/05/2000 09:24 17255 DBBD7523
LVMALERT.EXE LVMALERT.EX_ 10 04/05/2000 09:38 22784 087F6CB5
LVMGUI.ZIP LVMGUI.ZI_ 8 04/05/2000 09:24 452346 7D507347
LVMH.MSG LVMH.MS_ 10 04/05/2000 09:24 18703 76B0B4B5
NAMEREXX.DLL NAMEREXX.DL_ 6 03/27/2000 14:26 97811 93EA52AC
OREXUTIL.DLL ORXUTIL2.DL_ 9 03/27/2000 14:23 42823 AA36F8D5
OREXX.DLL OREXX2.DL_ 5 03/27/2000 14:23 490355 38ED1A55
OS2APIC.PSD OS2APIC.PS_ 10 03/31/2000 09:02 31232 0EDBAB78
OS2DASD.DMD OS2DASD.DM_ 9 04/05/2000 09:36 37421 78E0D44F
OS2DUMP OS2DUMP.___ 10 03/31/2000 12:13 15197 13734DDD
OS2KRNL OS2KRNL.SM_ 3 03/31/2000 08:56 884502 9F66998C
OS2KRNL OS2KRNL.UN_ 4 03/31/2000 08:41 824485 20E86D19
OS2KRNLB.SYM KRNLBSYM.SM_ 7 03/31/2000 09:57 190388 C3DE6C77
OS2KRNLB.SYM KRNLBSYM.UN_ 8 03/31/2000 09:35 183300 DD36ADB4
OS2KRNLD.SYM KRNLDSYM.SM_ 2 03/31/2000 09:45 195716 02F43A70
OS2KRNLD.SYM KRNLDSYM.UN_ 8 03/31/2000 09:23 188132 9500711C
OS2KRNLR.SYM KRNLRSYM.SM_ 8 03/31/2000 08:56 170468 38D778FC
OS2KRNLR.SYM KRNLRSYM.UN_ 8 03/31/2000 08:41 165924 3DB3D0A5
OS2LDR OS2LDR.SM_ 10 03/31/2000 11:03 43008 755F6A61
OS2LDR OS2LDR.UN_ 10 03/31/2000 11:02 45056 540AC542
OS2LVM.DMD OS2LVM.DM_ 10 04/05/2000 09:38 31471 7AAA80B0
OSO001.MSG OSO001.MS_ 9 02/07/2000 16:02 175420 0B8808E8
OSO001H.MSG OSO001H.MS_ 9 02/07/2000 16:02 240278 F8C69AFB
PICV.DLL PICV.DL_ 10 04/18/2000 10:07 29784 B58D5F3B
PMCTLS.DLL PMCTLS.DL_ 2 04/18/2000 09:57 644468 69576C98
PMCTLS.SYM PMCTLSYM.SM_ 10 04/18/2000 09:57 44660 BE668352
PMCTLS.SYM PMCTLSYM.UN_ 10 04/18/2000 09:57 44660 BE679152
PMDDEML.DLL PMDDEML.DL_ 10 04/18/2000 09:51 28278 F9338E04
PMGPI.DLL PMGPI.DL_ 6 04/18/2000 09:46 373634 290D3B3A
PMGPI.TDF PMGPI.TD_ 10 04/18/2000 09:46 12338 A3F49676
PMGRE.DLL PMGRE.DL_ 10 04/18/2000 09:43 2231 D1BE2F7D
PMGRE.TDF PMGRE.TD_ 10 04/18/2000 09:59 1062 3008EB3A
PMMERGE.DLL PMMERGE.DL_ 1 04/18/2000 09:59 1268435 E6CB753B
PMMERGE.SYM PMMERSYM.SM_ 8 04/18/2000 09:59 117492 389FC139
PMMERGE.SYM PMMERSYM.UN_ 8 04/18/2000 09:59 117492 389FC139
PMREXX.EXE PMREXX.EX_ 9 04/11/2000 14:42 78885 BD152557
FixPak Corrective Service levels and disk layouts 23
April 25, 2000 - Warp Server for e-business FixPak XR_E001
PMSHAPI.DLL PMSHAPI.DL_ 10 04/18/2000 09:53 4549 DBE5FDDD
PMSHAPI.TDF PMSHAPI.TD_ 10 04/18/2000 09:59 6726 C5B82ACA
PMSPL.DLL PMSPL.DL_ 6 02/24/2000 15:32 277251 7E020B83
PMSPL.SYM PMSPLSYM.SM_ 10 02/24/2000 15:32 32340 4BBEA8F5
PMSPL.SYM PMSPLSYM.UN_ 10 02/24/2000 15:32 32340 4BBEA8F5
PMVIOP.DLL PMVIOP.DL_ 9 04/18/2000 10:11 65768 03DA1371
PMVIOP.SYM PMVIOSYM.SM_ 10 04/18/2000 10:11 7620 FFB3993E
PMVIOP.SYM PMVIOSYM.UN_ 10 04/18/2000 10:11 7620 FFB3993E
PMWINX.DLL PMWINX.DL_ 3 04/18/2000 10:06 530827 1B0645D6
PMWP.DLL PMWP.DL_ 2 03/29/2000 09:10 1063613 5BC4DA5A
PMWP.SYM PMWPSYM.SM_ 9 03/29/2000 09:10 103780 322967BE
PMWP.SYM PMWPSYM.UN_ 9 03/29/2000 09:10 103780 322967BE
PMWP.TDF PMWP.TD_ 10 03/29/2000 09:10 13825 D2FF131A
PMWPMRI.DLL PMWPMRI.DL_ 9 03/15/2000 16:09 54311 05F999D2
PNP.DLL PNP.DL_ 10 03/29/2000 09:22 28297 9CADD035
PNP.SYS PNP.SY_ 10 01/28/2000 15:38 2152 ACA60C85
PRINTPNP.PND PRINTPNP.PN_ 10 02/24/2000 15:08 14105 587E7543
PSFILES.EXE PSFILES.EX_ 5 01/21/2000 10:50 8421 DA5EEF8A
PSSEMS.EXE PSSEMS.EX_ 10 01/21/2000 10:50 9445 0B7A6BD0
PSTAT.EXE PSTAT.EX_ 8 01/21/2000 10:50 11189 E47D55C4
QUECALLS.DLL QUECALLS.DL_ 10 03/31/2000 12:14 1024 A32F1956
QUECALLS.TDF QUECALLS.TD_ 10 03/31/2000 08:44 1299 34785685
README.CID README.CI_ 10 03/15/2000 09:42 48422 37B71502
REGEDIT2.EXE REGEDIT2.EX_ 4 11/24/1999 13:10 949760 92C2BD85
REX.MSG REX.MS_ 10 03/27/2000 14:23 2865 6D3B3657
REXX.DLL CREXX1.DL_ 7 03/27/2000 14:23 266031 76C48B8E
REXX.DLL OREXX1.DL_ 5 03/27/2000 14:23 490355 1A3164C6
REXX.IMG REXX.IM_ 9 03/27/2000 14:23 283636 D7ED399D
REXXAPI.DLL REXXAPI.DL_ 10 03/27/2000 14:23 40995 2E3F3324
REXXC.EXE REXXC.EX_ 10 03/27/2000 14:23 2758 D085CDFF
REXXCRT.DLL REXXCRT.DL_ 9 04/18/2000 09:33 79348 C116A7D8
REXXUTIL.DLL REXXUTIL.DL_ 9 03/27/2000 14:23 68119 4D504317
REXXUTIL.DLL ORXUTIL1.DL_ 9 03/27/2000 14:23 42823 AA515995
RINSTPRN.EXE RINSTPRN.EX_ 7 02/22/2000 12:18 195012 E27E4663
RSPDDI.EXE RSPDDI.EX_ 10 03/15/2000 11:58 22585 D4B0536B
RSPDSPI.EXE RSPDSPI.EX_ 8 04/13/2000 10:33 143398 640CD6CE
RSPIMRI.DLL RSPIMRI.DL_ 10 04/13/2000 10:34 25647 63FA7A1E
RSPINST.EXE RSPINST.EX_ 6 03/16/2000 08:13 475472 6C79DE80
SCENTER.DLL SCENTER.DL_ 6 02/24/2000 15:46 293927 CAFD872B
SEAMLESS.DLL SEAMLESS.DL_ 10 04/18/2000 10:11 49167 11E7F519
SESDD32.SYS SESDD32.SY_ 9 01/04/2000 12:47 118834 8B2CC722
SESMGR.DLL SESMGR.DL_ 10 03/31/2000 12:14 1536 46610CE5
SESMGR.TDF SESMGR.TD_ 10 03/31/2000 08:44 1877 941F3F60
SHELL.SDF SHELLSDF.SM_ 10 03/31/2000 09:00 21279 F30E0B5B
SHELL.SDF SHELLSDF.UN_ 10 03/31/2000 09:00 21279 F30E0B5B
SOFTDRAW.DLL SOFTDRAW.DL_ 5 04/18/2000 09:39 467527 96D2B7BA
SYSLEVEL.EXE SYSLEVEL.EX_ 10 03/15/2000 11:41 44512 C58740A9
SYSLEVEL.FPK SYSLEVEL.FP_ 7 11/29/1999 14:00 165 C6150A2E
SYSLEVEL.MSG SYSLEVEL.MS_ 10 03/15/2000 11:41 1445 FA94C4DF
TRACE.EXE TRACE.EX_ 10 01/21/2000 11:01 35328 55D997F7
TRAPDUMP.EXE TRAPDUMP.EX_ 10 02/16/2000 05:03 23068 86D265D5
FixPak Corrective Service levels and disk layouts 24
April 25, 2000 - Warp Server for e-business FixPak XR_E001
TRC012F.TFF TRC012F.TF_ 10 04/05/2000 14:55 35285 5AFF5E53
TRCUST.EXE TRCUST.EX_ 9 01/21/2000 11:02 98773 190794C1
UHPFS.DLL UHPFS.DL_ 9 02/16/2000 14:26 104976 DB4E48E0
UJFS.DLL UJFS.DL_ 6 04/05/2000 14:55 237131 88D75625
USBAUDIO.SYS USBAUDIO.SY_ 10 01/28/2000 16:48 25332 86356AEB
USBCOM.SYS USBCOM.SY_ 10 01/28/2000 16:48 18294 3DD54BAE
USBD.SYS USBD.SY_ 10 02/15/2000 09:15 18342 BD940DDE
USBHID.SYS USBHID.SY_ 10 01/28/2000 16:48 12060 3A1E5FD2
USBMON.EXE USBMON.EX_ 10 02/24/2000 15:51 20105 B9D7AE4F
USBMOUSE.SYS USBMOUSE.SY_ 10 01/28/2000 16:48 11898 B719A5CC
USBPRT.HLP USBPRT.HL_ 1 01/21/2000 13:48 6293 E153E73A
USBPRT.PDR USBPRT.PD_ 9 03/14/2000 12:13 39857 24DEEEEA
USBUHCD.SYS USBUHCD.SY_ 10 01/28/2000 16:48 23342 F82AD233
USBUHCD2.SYS USBUHCD2.SY_ 10 01/28/2000 16:48 23342 027263DB
USER.EXE USER.EX_ 7 12/02/1999 16:42 281088 453EF87A
VCU.EXE VCU.EX_ 7 04/05/2000 13:58 130631 238A3BAB
VCU.MSG VCU.MS_ 10 04/05/2000 09:24 1760 7E73CFDA
VMAN.DLL VMAN.DL_ 9 04/18/2000 09:40 60953 64D19979
VMANWIN.SYS VMANWIN.SY_ 10 04/11/2000 13:25 3024 91B58A09
VWIN.SYS VWIN.SY_ 9 11/23/1999 09:21 27104 94AE52E6
WINSCLIP.DLL WINSCLIP.DL_ 3 12/02/1999 16:27 14848 663E0372
WINSHELD.EXE WINSHELD.EX_ 10 12/02/1999 16:27 22528 F1801F6D
WINSMSG.DLL WINSMSG.DL_ 4 12/02/1999 16:27 28441 ED6C8A9E
WPREXX.IMP WPREXX.IM_ 10 03/27/2000 14:23 6313 83FB163F
************************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "Warp Server for e-business Base Operating System (UNI)"
Standard Edition 4.50
Fixpak name: XR_E001_ (Country = Generic)
Pre-requisite CSD Level: XR_4500_
System Id: 1000
Component Id: 5639A6150
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\..\OS2\dll
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
DOSCALL1.DLL DCALLUNI.___ 10 03/31/2000 08:44 137513 A47B3279
OS2KRNL KRNLUNI.___ 11 03/31/2000 08:41 824485 20E7EE6C
OS2LDR LDRUNI.___ 10 03/31/2000 11:02 45056 540AC542
************************************************************************
Product location on CSD: A:\FIX\OS2.3
FixPak Corrective Service levels and disk layouts 25
April 25, 2000 - Warp Server for e-business FixPak XR_E001
Product name: "Warp Server for e-business Base Operating System (SMP)"
Standard Edition 4.50
Fixpak name: XR_E001_ (Country = Generic)
Pre-requisite CSD Level: XR_4500_
System Id: 1000
Component Id: 5639A5550
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\..\
..\..\OS2\dll
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
DOSCALL1.DLL DCALLSMP.___ 10 03/31/2000 08:59 144786 004F89E4
OS2KRNL KRNLSMP.___ 12 03/31/2000 08:56 884502 9F66C38C
OS2LDR LDRSMP.___ 10 03/31/2000 11:03 43008 755F6A61
************************************************************************
Product location on CSD: A:\FIX\OS2.4
Product name: "Warp Server for e-business Base Operating System (UNI)"
Standard Edition 4.50
Fixpak name: XR_E001_ (Country = Generic)
Pre-requisite CSD Level: XR_4500_
System Id: 1000
Component Id: 5639A6150
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\TOPOBJ
..\..\TOPOBJ\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
FixPak Corrective Service levels and disk layouts 26
April 25, 2000 - Warp Server for e-business FixPak XR_E001
PMDF.EXE PMDF.EX_ 11 02/16/2000 05:02 262788 724FC6A3
************************************************************************
Product location on CSD: A:\FIX\OS2.5
Product name: "Warp Server for e-business Base Operating System (SMP)"
Standard Edition 4.50
Fixpak name: XR_E001_ (Country = Generic)
Pre-requisite CSD Level: XR_4500_
System Id: 1000
Component Id: 5639A5550
Archive is ON for this product.
________________________________________________________________________
Default directories:
..\*
..\..\MMOS2
..\..\MMOS2\*
..\..\VT
..\..\VT\*
..\..\TOPOBJ
..\..\TOPOBJ\*
..\..\PSFONTS
..\..\PSFONTS\*
..\..\LANGUAGE
..\..\LANGUAGE\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size Checksum
------------ ------------ ----- ---------- ----- ------- --------
PMDF.EXE PMDF.EX_ 11 02/15/2000 11:51 260184 4DBCBF81
FixPak Corrective Service levels and disk layouts 27
April 25, 2000 - Warp Server for e-business FixPak XR_E001
11.0 SPACE UTILIZATION
The FixPak installation process requires free space on the following
drives:
Space needed Drive
Up to 2MB C:
Up to 2MB Boot drive (4MB if boot is C:)
Up to 22MB Drive with most free space, holds deferred files if
A:SERVICE method used.
Up to 25MB FixPak Archive/Backup for product with CSD level of
XR_4500
Note: The lines labeled "FixPak Archive/Backup for product with CSD level
of" will be on the drive you specify and will occupy up to the size
indicated for the Archive and for the Backup directories. If, for
example, the indicated size is 30MB then the space actually occupied on
the drive can be up to 60MB.
11.0.1 RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE
Warning: Make sure you read and understand the following before removing
the Archive and Backup files and directories.
You can recover the space used for FixPak Archive and Backup files as
long as you understand that doing this prevents you from being able to
backout to the previous Backup or Archive level. If it becomes necessary
at a later time to backout a FixPak, the only way you can do this is to
reinstall Warp.
Do the following to delete the FixPak Backup and Archive files and remove
the files used by CSF to keep track of what service has been applied to
your system.
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 28
April 25, 2000 - Warp Server for e-business FixPak XR_E001
11.0.2 TRADEMARKS
The following terms are trademarks of the International Business Machines
Corporation in the United States or other countries or both:
þ IBM
þ OS/2
þ WorkSpace On-Demand
Other company, product, and service names may be trademarks or service
marks of others.
Space Utilization 29
]]>