home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.ib.com
/
2003-04-09_ftp.ibm.com-os2.zip
/
warp.update.kit
/
xr_w017
/
xr_w017.1dk
/
README.1ST
< prev
next >
Wrap
Text File
|
1996-01-26
|
67KB
|
2,042 lines
< Installation instructions for Warp FixPak XR_W017
Build level 8.241 (2nd release)
Supported CSD levels
XR_3000 Warp for Windows
XR_3001 Warp with WIN-OS/2
XR_3002 Warp for Windows Manufacturing Refresh
XR_3003 Warp with WIN-OS/2 Connect
XR_3004 Warp for Windows Manufacturing Refresh Connect
XR_3005 Warp with WIN-OS/2 Server
OS/2 Fix Distribution
Personal System Products
Boca Raton, Fl
(c) Copyright International Business Machines Corporation, 1996.
All rights Reserved.
January 25 1996 Warp FixPak XR_W017
January 25 1996 Warp FixPak XR_W017
CONTENTS
Terms and Conditions ............................................. 1
Who should not install this FixPak ............................... 2
Installation Notes ............................................... 3
Do not use your system once the FixPak installation is started . 3
What is the SIQ (Single Input Queue) feature ................... 3
How it works ................................................. 3
Popup message about newer file on harddisk than is in FixPak ... 4
Common File Dialog Interface changes ........................... 4
Dell machines and font editing ................................. 4
Corrective Service Facility Boot Diskettes ....................... 5
Read-Only files .................................................. 6
Relocated OS/2 file support ...................................... 7
Installation Process ............................................. 8
Method 1: Install from booted OS/2 partition. ................... 8
Method 2: Boot from Corrective Service Disk 1. ................. 10
Additional Corrective Service Facility information .............. 10
Recovering from Installation problems ........................... 11
No files to service ........................................... 11
Previous installation interrupted ............................. 12
Unable to open Archive directory .............................. 12
System problems after FixPak installation ....................... 13
OS/2 is unable to operate your hard disk or diskette drive. .. 13
RIPL failure .................................................. 14
Updating systems with the CMD chipset ......................... 15
RZ1000 and CMD640 Data Problems (APAR=PJ19409) ................ 15
SYS3175 when opening LS 4.0 Lan Server Administration ......... 17
Traps when canceling print jobs after FixPak is installed ..... 18
Novell Requester .............................................. 18
CC:Mail for OS/2 .............................................. 18
Rapid Resume Fix .............................................. 18
No Window list when you press Ctrl+Esc ........................ 19
IBM CODE/400 at V3R1M0 level .................................. 19
Problems with Visual REXX applications ........................ 19
TCP/IP at level WR08152 ....................................... 20
DOSCALL1.DLL Error ............................................ 20
CSD level of SYSLEVEL.OS2 ....................................... 21
List of problems fixed in the FixPak ............................ 21
Where Fixes can be found ........................................ 22
FixPak Corrective Service levels and disk layouts ............... 23
Contents ii
January 25 1996 Warp FixPak XR_W017
Space Utilization ............................................... 32
Contents iii
January 25 1996 Warp FixPak XR_W017
TERMS AND CONDITIONS
IMPORTANT
---------
IMPORTANT - PLEASE READ THE FOLLOWING TERMS AND CONDITIONS.
DOWNLOADING THE FixPak XR_W017 SERVICE FIXES THAT FOLLOW
INDICATES YOUR ACCEPTANCE OF THE FOLLOWING TERMS AND CONDITIONS:
A) YOU MUST BE, AND AGREE THAT YOU ARE, A CURRENT LICENSEE OF
OS/2;
B) YOU MAY MAKE COPIES OF THE OS/2 SERVICE FIXES EQUAL TO THE
NUMBER OF LICENSED COPIES OF OS/2 YOU POSSESS;
C) YOU MAY ONLY USE THE SERVICE FIXES INCLUDED WITH FixPak XR_W017
FOR MAINTENANCE PURPOSES;
D) YOU MAY ONLY USE THE WIN-OS/2 SERVICE FIXES INCLUDED WITH FixPak
XR_W017 TO MAINTAIN COPIES OF OS/2 WITH WIN-OS/2;
E) ALL OTHER TERMS AND CONDITIONS OF YOUR OS/2 LICENSE
AGREEMENTS APPLY TO THE SERVICE FIXES; HOWEVER, THIS DOES NOT
EXTEND ANY WARRANTY AND/OR SERVICES, INCLUDING BUT NOT LIMITED
TO THE "GETTING STARTED" PERIOD, OUTLINED IN SUCH AGREEMENTS.
Terms and Conditions 1
January 25 1996 Warp FixPak XR_W017
WHO SHOULD NOT INSTALL THIS FIXPAK
Do not install this FixPak if either of the following applies to you:
APTIVA M Series
OS/2 FixPaks can not be installed on Aptiva M series models that were
preloaded with OS/2 Warp. However, if you installed (or reinstalled)
a shrinkwrapped version of OS/2 Warp on these models, you can install
the FixPak. Contact OS/2 Technical Support if you need assistance in
this process.
DCF/2 users
DCF/2 will not work with this FixPak or any FixPak since XR_W009. If
you must apply this FixPak then you have to uncompress your harddisk
and not use DCF/2.
IBM is working with the DCF/2 developers to resolve this problem.
Who should not install this FixPak 2
January 25 1996 Warp FixPak XR_W017
INSTALLATION NOTES
DO NOT USE YOUR SYSTEM ONCE THE FIXPAK INSTALLATION IS STARTED
Once you begin a FixPak installation, do not try to use your system
for any other purpose. Doing so may yield unexpected problems which
can cause the FixPak installation to fail.
WHAT IS THE SIQ (SINGLE INPUT QUEUE) FEATURE
The "SIQ" feature is new with FixPak XR_W017. It allows the user to
take focus away from an application that is monopolizing the message
queue. When the FixPak is installed, the SIQ feature is disabled
(OFF).
How it works
When you request a focus change for example, by clicking on another
application or pressing Ctl+Esc the application that has the focus
should respond to the message in x milliseconds. If the application
does not respond within that time, OS/2 determines that the
application is not responding to messages and flags the application
queue as bad. It then switches focus to the desired application.
OS/2 will monitor the queue marked as bad to see when it does start
responding to messages. It will mark the queue as good when this
occurs.
To enable the SIQ feature, put a SET PM_ASYNC_FOCUS_CHANGE statement
in CONFIG.SYS and reboot.
The parameters to the SET command are:
SET PM_ASYNC_FOCUS_CHANGE=ON | ON x | OFF
The default is OFF (disabled).
To turn it on (enable) put the following in the CONFIG.SYS file and
reboot:
SET PM_ASYNC_FOCUS_CHANGE=ON
To change the timeout value put the following in the CONFIG.SYS file
and reboot:
Installation Notes 3
January 25 1996 Warp FixPak XR_W017
SET PM_ASYNC_FOCUS_CHANGE=ON x
where x is in milliseconds (default is 2000 (2 seconds))
If you think you are having problems with SIQ, a way to isolate a
problem is to raise the timeout to 5000 milliseconds (5 seconds). If
that does not help, turn it off. If there is a SIQ feature problem,
this will help us (IBM) isolate it.
POPUP MESSAGE ABOUT NEWER FILE ON HARDDISK THAN IS IN FIXPAK
If you get a popup stating that a newer file exists on your harddisk
than is in the FixPak, and it is one of the following files, select
the "No" button so you DO NOT replace the newer file with the older
one.
■ AUTODRV2.SYS 6-09-95 4:24p
■ IBM2SS01.SYS 7-09-95 2:03p
■ PCM2ATA.ADD 6-10-95 3:30p
■ PCMCIA.SYS 6-09-95 4:23p
COMMON FILE DIALOG INTERFACE CHANGES
The Common File Dialog interface has been rearranged to improve
usability. The changes are:
■ "Type of file" field moved below the Open filename.
■ "Drive" and "Directory" controls were swapped with the "File"
control.
DELL MACHINES AND FONT EDITING
When editing fonts, users of Dell machines may discover a slight
regression. When a font size is edited, the Font Palette is updated
correctly; however, should users browse (select around) the palette,
they might, at times, notice an inconsistency between the font size
displayed on the palette and the one that is displayed on the font
editor. In all cases, the font size displayed on the Font Palette is
the correct size for the font when it is dragged to the target (for
example, the desktop, folder, or application).
Installation Notes 4
January 25 1996 Warp FixPak XR_W017
CORRECTIVE SERVICE FACILITY BOOT DISKETTES
You will need the OS/2 Warp 3.0 Corrective Service Facility Boot
Diskettes to install this FixPak. These files should be available from
the same place you got this FixPak.
CSFBOOT.1DK - Corrective Service Facility disk 1
CSFBOOT.2DK - Corrective Service Facility disk 2
- or -
WKICKR.ZIP - File compressed with PKZIP. Contains both of the
above disk images. Requires PKUNZIP or UNZIP to
extract original files from the compressed file.
To create diskettes from the disk image files, you need LOADDSKF.EXE.
This is also available from the same place you obtained this FixPak.
LDF.COM - Self-extracting file that will create LOADDSKF.EXE.
Place in a separate directory on your hard disk
and then enter LDF.
- or -
LOADDF.ZIP - File compressed with PKZIP that contains LOADDSKF.EXE.
Requires PKUNZIP or UNZIP to extract original files
from the compressed file.
Note: LOADDSKF.EXE is also on any CD-ROM version of OS/2.
Use LOADDSKF.EXE to create the diskettes. For each disk image, place a
2MB HD (1.44MB formatted) diskette in A:. DO NOT use a 1MB (720KB
formatted) diskette because you might have problems trying to install
this FixPak.
1. Enter LOADDSKF CSFBOOT.1DK A: /F. Label the diskette as CSF DISK
Diskette 1 (SP DISK 1).
2. Enter LOADDSKF CSFBOOT.2DK A: /F. Label the diskette as CSF DISK
Diskette 2 (SP DISK 2).
3. Enter LOADDSKF XR_W017.1DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 1 (CSF DISK 1).
4. Enter LOADDSKF XR_W017.2DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 2 (CSF DISK 2).
5. Enter LOADDSKF XR_W017.3DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 3 (CSF DISK 3).
Installation Notes 5
January 25 1996 Warp FixPak XR_W017
6. Enter LOADDSKF XR_W017.4DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 4 (CSF DISK 4).
7. Enter LOADDSKF XR_W017.5DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 5 (CSF DISK 5).
8. Enter LOADDSKF XR_W017.6DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 6 (CSF DISK 6).
9. Enter LOADDSKF XR_W017.7DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 7 (CSF DISK 7).
10. Enter LOADDSKF XR_W017.8DK A: /F. Label the diskette as FixPak
XR_W017 Corrective Service Diskette 8 (CSF DISK 8).
READ-ONLY FILES
If you installed OS/2 Warp 3.0 from a CD-ROM, some files being updated
might have the Read-Only attribute set. This will cause the update
program to ask you if you want the files replaced. Answer OK.
Installation Notes 6
January 25 1996 Warp FixPak XR_W017
RELOCATED OS/2 FILE SUPPORT
This FixPak will service directories based on the location of
supported SYSLEVEL.OS2 and SYSLEVEL.MPM files. Please check your
system to make sure extra copies of these files are not located in
directories other than:
\OS2\INSTALL\SYSLEVEL.OS2 on the boot drive of your OS/2 partition(s)
\MMOS2\INSTALL\SYSLEVEL.MPM on any partition
If additional copies of these files are found in other locations on
your hard disk then CSF will try to service files as follows:
For SYSLEVEL.OS2
..\..\ all files in a directory two levels above (toward the root).
This should be the root directory of your boot drive.
..\* all files in a directory one level above (toward the root) and
all subdirectories below. This should be the OS2 directory and
subdirectories.
For SYSLEVEL.MPM
..\* all files in a directory one level above (toward the root) and
all subdirectories below. This should be the MMOS2 directory and
subdirectories.
If you have moved OS/2 files or directories, do the following in order
to have them serviced:
1. Create a file named USERDIRS.OS2 in the \OS2\INSTALL directory of
the OS\2 Warp partition to be serviced.
In this file, place the full path to the directory you want to be
serviced. Examples would be:
C:\JSI\*
D:\JSI\SH\*
Be sure to include the trailing * (asterisk) after the last
backslash.
Note: Leave this file for any future OS/2 Warp FixPaks you might
apply.
Relocated OS/2 file support 7
January 25 1996 Warp FixPak XR_W017
INSTALLATION PROCESS
Before installing any FixPak, run CHKDSK /F against all drives on your
system to correct any file system errors that might be present. You
cannot do this while OS/2 is active. You must shut down and run CHKDSK
by one of the following methods:
■ Boot from your Installation and DISK 1 diskettes you used to
install OS/2 with. If your file system is HPFS, then put the
diskette with CHKDSK and UHPFS.DLL on it in your A: drive before
issuing the CHKDSK command.
■ Boot from the Utilities disk you created via the "Create Utility
Diskettes" icon in the System Setup folder.
■ Boot from a different OS/2 partition.
To Install this FixPak use one of the following methods:
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.
4. Follow the displayed instructions. When prompted to insert
Corrective Service Diskette 1 (not CSF DISK Diskette 1), place
FixPak XR_W017 Corrective Service Diskette 1 in drive A. Repeat
for the rest of the FixPak disks when requested to do so.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. In
some cases, it has taken as long as 40 minutes. Please be patient
and allow this process to complete.
5. If this is the first OS/2 Warp FixPak you have applied to this
system, then enter the path to the ARCHIVE directory where a copy
of replaced files will be stored (for example, D:\ARCHIVE).
Installation Process 8
January 25 1996 Warp FixPak XR_W017
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. This occurs only if you
apply service to the OS/2 partition you are booted from.
■ 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
\OS2\INSTALL\IBMCSFLK\FIX directory on your Warp boot drive.
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.
Installation Process 9
January 25 1996 Warp FixPak XR_W017
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 might then do an automatic reboot. In some cases, it
might do an additional reboot.
METHOD 2: BOOT FROM CORRECTIVE SERVICE DISK 1.
This method does not prompt the user for any information. No
interaction with the user takes place other than requests to put the
next diskette in drive A. All serviceable partitions on your system
will be updated automatically. Be especially careful of extra
SYSLEVEL.OS2 or SYSLEVEL.MPM files when using this method because they
can cause CSF to apply service to directories you do not want
serviced.
1. Shut down your OS/2 system.
2. Insert CSF DISK Diskette 1 in drive A.
3. Press Ctrl+Alt+Del to boot the disk in drive A.
Service will be applied to ALL partitions that contain a version of
OS/2 that is supported by this FixPak. See the section "FixPak
Corrective Service Notes" for the CSD levels this FixPak applies to.
Note: It can take a considerable length of time for the Corrective
Service Facility to scan your hard disk for serviceable files. In some
cases it has taken as long as 40 minutes. Please be patient and allow
this process to complete.
ADDITIONAL CORRECTIVE SERVICE FACILITY INFORMATION
Additional information on the Corrective Service Facility is available
from the README.INF file on the first Corrective Service Facility
disk. To view this file, place CSF disk 1 in drive A and enter VIEW
A:\README.INF.
Installation Process 10
January 25 1996 Warp FixPak XR_W017
RECOVERING FROM INSTALLATION PROBLEMS
This section describes some procedures you can follow to recover from
problems found while trying to install a FixPak.
NO FILES TO SERVICE
If you see a "No files to service" message while applying this FixPak,
the Current CSD level or Component ID of the "IBM OS/2 Base Operating
System" might not be supported by this FixPak.
Correct values must be:
OS/2 Version OS/2 Base Operating System Multimedia Presentation Manager
------------------ -------------------------- --------------------------
Warp for Windows Current CSD level: XR_3000 Current CSD level: XR_3000
Component ID: 562260100 Component ID: 562137400
Warp with WIN-OS/2 Current CSD level: XR_3001 Current CSD level: XR_3001
Component ID: 562274700 Component ID: 562274700
Warp for Windows Current CSD level: XR_3002 Current CSD level: XR_3002
Mfg Refresh Component ID: 562260100 Component ID: 562260100
Warp with WIN-OS/2 Current CSD level: XR_3003 Current CSD level: XR_3003
Connect Component ID: 562274700 Component ID: 562274700
Warp for Windows Current CSD level: XR_3004 Current CSD level: XR_3004
Mfg Refresh Connect Component ID: 562260100 Component ID: 562260100
Warp with WIN-OS/2 Current CSD level: XR_3005 Current CSD level: XR_3005
Server Component ID: 562274700 Component ID: 562274700
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
Recovering from Installation problems 11
January 25 1996 Warp FixPak XR_W017
Also check for the following file:
C:\CSF_SEL.000
If these files exist, rename them and try the FixPak installation
again. If the installation is successful, delete the renamed files.
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 file:
C:\FIXSTART
If it exists, rename it and try the FixPak installation again. If it
works, delete the renamed file. If this does not resolve the problem,
follow the procedure "Recovering from Installation problems".
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 deleted the FixPak ARCHIVE
or BACKUP directory.
To recover from this, follow the "No files to service" and "Previous
installation interrupted" steps.
Recovering from Installation problems 12
January 25 1996 Warp FixPak XR_W017
SYSTEM PROBLEMS AFTER FIXPAK INSTALLATION
This section describes problems that can occur after applying this
FixPak. It also describes how to recover from these problems.
OS/2 IS UNABLE TO OPERATE YOUR HARD DISK OR DISKETTE DRIVE.
If, after installing this FixPak, you get the following message:
OS/2 is unable to operate your hard disk or diskette drive.
The system is stopped. Correct the preceding error and
restart the system.
Do the following:
1. Boot your system in one of the followin ways
■ With your OS/2 Warp Installation "Install disk" and "DISK 1".
■ From another bootable OS/2 partition.
■ From a bootable DOS partition or DOS bootable diskette if your
OS/2 Warp partition uses the FAT file system and not the HPFS
file system.
■ From your Utility disks if you created them via the "Create
Utility Disks" Icon in "System Setup folder".
2. Edit the CONFIG.SYS file on your Warp boot drive. Add /FL to the
end of the BASEDEV=IBM1S506.ADD line.
Note: You can use the TEDIT editor which is a text editor and does
not require the Workplace Shell to be running.
a. CD x: (x: is your Warp boot drive)
b. \OS2\TEDIT CONFIG.SYS
c. /IBM1S506 (locate the IBM1S506 line, case
sensitive)
d. Press the Esc key (this move the cursor into the
edit area)
e. Add /FL to the end of the BASEDEV=IBM1S506.ADD line. Leave a
space between the last character of the existing line and the
/FL
f. Press F2 to save the change
System problems after FixPak installation 13
January 25 1996 Warp FixPak XR_W017
g. Press F3 to quit
3. Press Ctrl+Alt+Del to reboot your system.
If this resolves your problem then please read "Updating systems with
the CMD chipset" and "RZ1000 and CMD640 Data Problems (APAR=PJ19409)"
(the next two sections of this document) for additional changes you
can make to your CONFIG.SYS file.
RIPL FAILURE
If RIPL (Remote IPL) of a work station fails after the FixPak is
applied when it worked prior to applying the FixPak, the probable
cause is a downlevel SOM.DLL in the \IBMLAN\RPL\IBMLAN\NETLIB
directory.
After applying fixpack 17 to the \IBMLAN\RPL\OS2.30 directory
tree on a LAN Server 4.0 RIPL server, the following procedure
must be followed to complete the update:
1. Change to the d:\IBMLAN\RPL\IBMLAN\NETLIB directory.
Where d: is the drive where \IBMLAN\RPL is installed.
2. Create a new sub-directory, SOMBAK.
MD SOMBAK
3. Copy the SOM*.DLL files to the SOMBAK directory.
COPY SOM*.DLL SOMBAK\
4. Erase the SOM*.DLL files in the d:\IBMLAN\RPL\IBMLAN\NETLIB
directory.
ERASE SOM*.DLL
5. Determine if there are any other versions of OS/2 installed
in the Remote IPL tree. Look for the following
sub-directories:
d:\IBMLAN\RPL\OS2.20 (OS/2 2.0)
d:\IBMLAN\RPL\OS2.21 (OS/2 2.10/2.11)
6. If any other versions of OS/2 are installed in the Remote
IPL tree, do the following:
a. Change to the d:\IBMLAN\RPL\OS2.2x\OS2\DLL (where x is 0
and/or 1) directory.
b. Compare the date/timestamp of the SOM.DLL file with
System problems after FixPak installation 14
January 25 1996 Warp FixPak XR_W017
the file d:\IBMLAN\RPL\IBMLAN\NETLIB\SOMBAK\SOM.DLL.
c. If the ..\OS2\DLL\SOM.DLL is older than the one in
d:\IBMLAN\RPL\IBMLAN\NETLIB\SOMBAK, copy the files
saved in step 3.
COPY d:\IBMLAN\RPL\IBMLAN\NETLIB\SOMBAK\*.DLL
Note: If the RIPLINST.EXE utility is subsequently used to
reload the d:\IBMLAN\RPL\OS2.2x directory tree(s),
the saved SOM*.DLL files will have to be re-copied
from d:\IBMLAN\RPL\IBMLAN\NETLIB\SOMBAK.
UPDATING SYSTEMS WITH THE CMD CHIPSET
If you are installing this FixPak on a machine that has the CMD PCI
IDE chipset, you must modify your CONFIG.SYS after the FixPak has been
installed.
Add the following statements to your CONFIG.SYS file:
BASEDEV=CMD640X.ADD (add this line below BASEDEV=IBM1S506.ADD)
BASEDEV=CMDATAPI.FLT (add this line below BASEDEV=IBMIDECD.FLT)
RZ1000 AND CMD640 DATA PROBLEMS (APAR=PJ19409)
Problem Description: IDE disks can incur possible data read conflicts
that can cause data problems.
OS/2 Versions: All versions of OS/2 Warp
To verify the existence of this problem on your system, turn on the
verbose option on the IBM1S506.ADD. After installing the update per
the instructions above, edit CONFIG.SYS and add the /V (verbose)
switch option to the IBM1S506.ADD line:
BASEDEV=IBM1S506.ADD /V
If your CONFIG.SYS file does not have this line, add it any place
before the line:
BASEDEV=CMD640X.ADD
System problems after FixPak installation 15
January 25 1996 Warp FixPak XR_W017
After adding the /V and rebooting your system, you might see the
following on the third line of disk information during start-up:
PCI Rev: 02.00 RZ1000 PCI to IDE IC, Rev: 0x01 VID:0x1000 DID:0x1042
or
PCI Rev: 02.00 CMD640 PCI to IDE IC, Rev: 0x01 VID:0x1095 DID:0x0640
If this information is displayed your system does contain an RZ1000 or
CMD640 chip and is susceptible to the above problem.
Note: On some systems this message might be displayed for only a brief
time during system boot.
If no such line appears, then you can revert to the originally shipped
device drivers or leave the new drivers installed.
Note: This fix has no effect on other IDE systems.
Remove the /V option from the CONFIG.SYS file if you no longer want
the verbose information displayed.
Fix Description:
To fix data problems with the RZ1000 and CMD640 chips, disable
Read-ahead mode in the OS/2 IBM1S506.ADD and CMD640X.ADD device
drivers. These are generic device drivers which fix all the above
releases and are compatible with systems that DO NOT use the RZ1000 or
CMD640x chips.
The new IBM1S506 device driver detects the RZ1000 and disables
read-ahead for both RZ1000 IDE channels. The IBM1S506 device driver
also detects the CMD640x chip and disables read-ahead for the primary
IDE channel.
The new CMD640X device driver detects the CMD640 chip and disables
read-ahead mode for both IDE channels.
Also included with this fix distribution are the corresponding ATAPI
CD-ROM device drivers so as to remain synchronized with IDE drivers.
IBM1S506.ADD -> Generic IDE/ATA Device Driver
IBMIDECD.FLT -> Generic IDE/ATAPI Device Driver
CMD640X.ADD -> CMD Optimized IDE/ATA Device Driver
CMDATAPI.FLT -> CMD Optimized IDE/ATAPI Device Driver
Performance Impact:
System problems after FixPak installation 16
January 25 1996 Warp FixPak XR_W017
IBM's benchmarks show no system performance degradation from disabling
the read-ahead mode in either the RZ1000 or CMD640 IDE PCI interface
chips.
SYS3175 WHEN OPENING LS 4.0 LAN SERVER ADMINISTRATION
Contact IBM LAN support and request the fix for APAR IC11718 which is
IP08169 (LS40GUI.ZIP on Internet and BBSes).
If you need a temporary solution while waiting to obtain the fix,
backout SOM.DLL to the pre-FixPak level as follows
1. Shut down your system.
2. Reboot and press Alt-F1 when you see "OS/2" and a white block in
the top left corner of the screen.
3. Press C to goto a command prompt.
4. Rename x:\OS2\DLL\SOM.DLL to SOMFP.DLL (x: is your OS/2 boot
drive)
5. Change to the FixPak archive directory
6. Enter UNPACK SOM.DL_ x:\OS2\DLL (x: is your OS/2 boot
drive)
7. Enter EXIT
Your system will reboot with the pre-FixPak version of SOM.DLL in
place. The SYS3175 problem should be resolved.
Once you receive and apply the fix for APAR IC11718 you should do the
following to reinstall SOM.DLL from this FixPak.
1. Shut down your system.
2. Reboot and press Alt-F1 when you see "OS/2" and a white block in
the top left corner of the screen.
3. Press C to goto a command prompt.
4. Delete x:\OS2\DLL\SOM.DLL (x: is your OS/2 boot
drive)
5. Rename x:\OS2\DLL\SOMFP.DLL to SOM.DLL (x: is your OS/2 boot
drive)
6. Enter EXIT
System problems after FixPak installation 17
January 25 1996 Warp FixPak XR_W017
TRAPS WHEN CANCELING PRINT JOBS AFTER FIXPAK IS INSTALLED
If you experience a trap when canceling print jobs using a LaserJet
driver, download the LaserJet driver FixPak XR0P012, revision level
30.453 or later from any of the sites listed in the "Where fixes can
be found" section of this document.
If you are using the IBMNULL printer driver, call service for APAR
PJ19995.
NOVELL REQUESTER
If you are using Novell Requester for OS/2, you need to obtain the
latest version of OS2C1.EXE. The number for the Novell BBS is
801-221-5197.
CC:MAIL FOR OS/2
If you are unable to open the settings notebook for any CC:Mail object
(Mouse button 2 on a CC:Mail object and click on "Settings"), then you
need CC:Mail for OS/2 client 1.03C (or later).
RAPID RESUME FIX
If you are using the IBM Rapid Resume function, you need to update a
module on your system. On the last diskette of this FixPak are two
directories named DIR_ONE and DIR_TWO. Depending on your machine
type, you need the files in one of these directories. Put the
diskette with these directories into drive A.
On IBM machine types PC100, PC300, PC700 and Aptiva 2144-Pxx (xx = the
different model numbers), enter the following command:
COPY A:\DIR_ONE\VCMOS.SYS ?:\OS2\MDOS
(? = the OS/2 drive being serviced)
On IBM machine type Aptiva 2144-Mxx (xx = the different model
numbers), enter the following command:
COPY A:\DIR_TWO\VCMOS.SYS ?:\OS2\MDOS
(? = the OS/2 drive being serviced)
During the next boot, this update will take effect.
System problems after FixPak installation 18
January 25 1996 Warp FixPak XR_W017
NO WINDOW LIST WHEN YOU PRESS CTRL+ESC
If after applying this FixPak you no longer get the Window list when
you press Ctrl+Esc, check the CONFIG.SYS file on your OS/2 boot
partition for the following line:
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,LAUNCHPAD
If you are missing the TASKLIST keyword, that is the cause of this
problem. Add it to the line as shown above.
Until OS/2 Warp FixPak XR_W014, the removal of TASKLIST from the SET
AUTOSTART line in CONFIG.SYS had no effect. This was a problem that
was fixed in FixPak 14 and all subsequent FixPaks.
IBM CODE/400 AT V3R1M0 LEVEL
You will experience a problem if you attempt to install IBM CODE/400
after applying the fixpack. Please ensure that IBM CODE/400 is
installed BEFORE the fixpack is applied.
For users of the IBM CODE/400 product at the V3R1M0 level, you need to
ensure you have the PTF SF28110 for product 5763CD1 installed or you
will encounter a problem in file EVFWLIST.EXE when running CODE/400
with this fixpack.
PROBLEMS WITH VISUAL REXX APPLICATIONS
If you have problems with visual REXX applications like VX/REXX or
VisPro/Rexx try backing out the REXX DLLs applied by this FixPak as
follows:
Note: x: means your OS/2 Warp boot drive.
1. Shut down your system.
2. Reboot and press Alt-F1 when you see "OS/2" and a white block in
the top left corner of the screen.
3. Press C to goto a command prompt.
4. Rename x:\OS2\DLL\REXX.DLL to REXX.DLO
5. Rename x:\OS2\DLL\REXXAPI.DLL to REXXAPI.DLO
6. Rename x:\OS2\DLL\REXXUTIL.DLL to REXXUTIL.DLO
7. Change to the FixPak archive directory
System problems after FixPak installation 19
January 25 1996 Warp FixPak XR_W017
8. Enter UNPACK REXX.DL_ x:\OS2\DLL
9. Enter UNPACK REXXAPI.DL_ x:\OS2\DLL
10. Enter UNPACK REXXUTIL.DL_ x:\OS2\DLL
11. Enter EXIT
TCP/IP AT LEVEL WR08152
A problem can occur in TCP/IP file TCPIPDLL.DLL at service level
WR08152. Contact IBM LAN Support for a fix to this problem.
DOSCALL1.DLL ERROR
If after installation of the Fixpack and upon REBOOT an error is
received "C0000005" from DOSCALL1.DLL (there may be two DOSCALL1.DLL
errors received), make the following adjustments to the RUN statements
in CONFIG.SYS. REBOOT after each adjustment to check if the error has
been removed.
Note - start with RUN statements that are not associated with IBM LAN
Requester or MPTS. The error has been found with the RUN statement for
COMETRUN.EXE (no PATH) and MWSTART.EXE (move to STARTUP.CMD).
1).Verify that all RUN statements have the fully qualified PATH to the
file.
2).REM the RUN statement out of CONFIG.SYS and place it in the
STARTUP.CMD
file (remember to leave off the "RUN=" and only put the PATH and
file name).
These changes can be made in the following manner: If the system
continues to boot after the error(s) open an OS/2 window and edit
CONFIG.SYS using the command "TEDIT CONFIG.SYS". If the system halts,
either reboot, press Alt-F1 when the white rectangle is in the upper
left corner, select "C" from the menu and edit CONFIG.SYS using the
command "TEDIT CONFIG.SYS", or reboot from the Installation diskettes,
go to a command prompt and edit CONFIG.SYS using the command "TEDIT
CONFIG.SYS".
TEDIT can also be used to edit STARTUP.CMD after making changes to
CONFIG.SYS.
System problems after FixPak installation 20
January 25 1996 Warp FixPak XR_W017
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 states it will. This FixPak is not a Service Level
change. It upgrades the existing service level (XR_300n); therefore
the SYSLEVEL is not changed. All fix information is recorded in the
SERVICE.LOG file.
Look at the file
\OS2\INSTALL\SERVICE.LOG
for information relating to the installation of this (or any) FixPak
on your system. To see the current level and other related information
use the SYSLEVEL command.
Use the VER /R command to see the current revision of OS/2 installed.
The response will look like the following for this FixPak:
The Operating System/2 Version is 3.00
Revision 8.241
-- or --
The Operating System/2 Version is 3.01
Revision 8.241
Look at the README.1ST file on the first FixPak disk of any FixPak for the
"Build Level: n.nnn" line. That is the number you should see for that
FixPak when you issue the VER /R command.
LIST OF PROBLEMS FIXED IN THE FIXPAK
See the README2 file on the first FixPak disk for a list of APARs
fixed.
CSD level of SYSLEVEL.OS2 21
January 25 1996 Warp FixPak XR_W017
WHERE FIXES CAN BE FOUND
You can find other files, such as new drivers or fixes for specific
video cards, from the following locations:
■ CompuServe - Subscribers can download fixes from the OS/2 Support
Forum (GO OS2SUPPO).
■ IBM OS/2 BBS - Subscribers can download fixes 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 - Customers with access to Internet services can download
fixes using the following methods:
Anonymous FTP to "ftp.software.ibm.com" (IP Address 198.17.57.67)
FixPaks are located in the "/ps/products/os2/fixes" directory.
World Wide Web (WWW) access via:
IBM Software Manufacturing Solutions ftp://service.boulder.ibm.com
Full path is ftp://service.boulder.ibm.com/ps/products/os2/
■ Prodigy - Subscribers can download fixes from the OS2CLUB in the
Download Library, IBM Files, Fixes area. Files are updated weekly
and are available on Friday.
■ PCC BBS - Customers can call the IBM Personal Computer Company BBS
in Raleigh, NC, and download fixes from the public area. You can
access this BBS at 1-919-517-0001.
■ America On Line - Subscribers can download fixes from the OS/2
Area.
Where Fixes can be found 22
January 25 1996 Warp FixPak XR_W017
FIXPAK CORRECTIVE SERVICE LEVELS AND DISK LAYOUTS
Build Level: 8.241
Product location on CSD: A:\FIX\OS2.1
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3000_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3001_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3002_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3003_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3004_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
FixPak Corrective Service levels and disk layouts 23
January 25 1996 Warp FixPak XR_W017
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\..\
..\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
AHA152X.ADD AHA152X.AD_ 6 10/30/95 14:54 38060
AHA164X.ADD AHA164X.AD_ 6 10/30/95 14:52 19716
AIC7770.ADD AIC7770.AD_ 5 10/30/95 14:54 42428
AIC7870.ADD AIC7870.AD_ 5 10/30/95 14:55 34124
APM.SYS APM.SY_ 6 10/30/95 15:16 6704
ARCINST.EXE ARCINST.EX_ 6 12/05/95 02:15 21358
ARCRECOV.EXE ARCRECOV.EX_ 6 12/05/95 02:16 24635
AUTODRV2.SYS AUTODRV2.SY_ 6 06/09/95 16:24 10862
BTSCSI.ADD BTSCSI.AD_ 6 10/30/95 15:01 22485
BVHVGA.DLL BVHVGA.DL_ 5 12/04/95 19:44 31054
BVHWNDW.DLL BVHWNDW.DL_ 6 12/04/95 19:45 12664
CDFS.IFS CDFS.IF_ 6 12/04/95 21:34 41795
CDROM.TBL CDROM.TB_ 6 05/19/95 17:16 3949
CHKDSK.COM CHKDSK.CO_ 5 12/04/95 23:07 68656
CMD.EXE CMD.EX_ 5 01/12/96 12:38 79360
CMD640X.ADD CMD640X.AD_ 5 10/30/95 17:35 35924
CMDATAPI.FLT CMDATAPI.FL_ 6 10/30/95 15:03 21554
COM.SYS COM.SY_ 6 10/30/95 15:15 16912
COMMAND.COM COMMAND.CO_ 5 12/04/95 23:16 52972
DATABASE.DAT DATABASE.DA_ 5 12/05/95 00:19 83419
DATABASE.TXT DATABASE.TX_ 5 08/17/95 09:30 609497
DETNE2.SYS DETNE2.SY_ 6 10/30/95 14:41 5640
DISPLAY.DLL DISPLAY.DL_ 5 12/04/95 22:32 44196
DOSCALL1.DLL DOSCALL1.DL_ 4 12/04/95 22:44 123186
DOSKRNL DOSKRNL.___ 6 12/04/95 19:53 30077
DPT20XX.ADD DPT20XX.AD_ 6 10/30/95 14:59 24254
DSPINSTL.EXE DSPINSTL.EX_ 5 12/05/95 00:35 170424
E.EXE E.EX_ 5 12/04/95 22:57 70917
EAUTIL.EXE EAUTIL.EX_ 5 12/04/95 23:23 37984
FD16-700.ADD FD16-700.AD_ 6 11/29/95 21:59 31260
FD7000EX.ADD FD7000EX.AD_ 6 11/29/95 22:01 20848
FD8XX.ADD FD8XX.AD_ 6 11/29/95 22:02 30030
FDISK.COM FDISK.CO_ 5 12/04/95 21:50 110245
FORMAT.COM FORMAT.CO_ 5 12/04/95 23:34 68880
FSFILTER.SYS FSFILTER.SY_ 6 01/06/96 08:53 12988
HELPMGR.DLL HELPMGR.DL_ 4 12/04/95 23:30 176108
HELPMSG.EXE HELPMSG.EX_ 5 12/04/95 23:34 36256
HPFS.IFS HPFS.IF_ 5 12/09/95 15:17 143938
IBM16AFS.EXE IBM16AFS.EX_ 6 11/29/95 22:03 3177
FixPak Corrective Service levels and disk layouts 24
January 25 1996 Warp FixPak XR_W017
IBM1FLPY.ADD IBM1FLPY.AD_ 6 10/30/95 14:47 31170
IBM1S506.ADD IBM1S506.AD_ 6 10/30/95 15:13 30636
IBM2AMB1.SYS IBM2AMB1.SY_ 6 11/29/95 22:18 12437
IBM2AST1.SYS IBM2AST1.SY_ 6 11/29/95 22:18 10047
IBM2CAD1.SYS IBM2CAD1.SY_ 6 11/29/95 22:20 12479
IBM2CMQ1.SYS IBM2CMQ1.SY_ 6 11/29/95 22:18 10085
IBM2FLPY.ADD IBM2FLPY.AD_ 6 10/30/95 14:47 13754
IBM2IDE.ADD IBM2IDE.AD_ 6 10/30/95 15:13 31396
IBM2MAT1.SYS IBM2MAT1.SY_ 6 11/29/95 22:20 10067
IBM2NCR1.SYS IBM2NCR1.SY_ 6 11/29/95 22:19 10047
IBM2NEC1.SYS IBM2NEC1.SY_ 6 11/29/95 22:19 10047
IBM2SCSI.ADD IBM2SCSI.AD_ 6 10/30/95 14:50 32691
IBM2SS01.SYS IBM2SS01.SY_ 6 07/09/95 14:03 13203
IBM2SS02.SYS IBM2SS02.SY_ 6 11/29/95 22:17 10477
IBM2TOS1.SYS IBM2TOS1.SY_ 6 11/29/95 22:17 10054
IBM2ZEN1.SYS IBM2ZEN1.SY_ 6 11/29/95 22:17 10047
IBM2ZOS1.SYS IBM2ZOS1.SY_ 6 11/29/95 22:19 10063
IBMIDECD.FLT IBMIDECD.FL_ 6 10/30/95 15:14 20358
IBMKBD.SYS IBMKBD.SY_ 6 07/18/95 09:31 5612
ICMEMCDD.SYS ICMEMCDD.SY_ 6 11/29/95 22:22 13932
ICMEMFMT.EXE ICMEMFMT.EX_ 5 11/29/95 22:24 51031
ICMEMMTD.SYS ICMEMMTD.SY_ 6 11/29/95 22:23 8300
KBDBASE.SYS KBDBASE.SY_ 6 10/30/95 15:17 28501
KEYBOARD.DCP KEYBOARD.DC_ 6 12/04/95 23:36 157804
LINK386.EXE LINK386.EX_ 4 12/04/95 23:53 154164
LMS205.ADD LMS205.AD_ 6 10/30/95 15:14 36380
LMS206.ADD LMS206.AD_ 6 10/30/95 15:14 38732
MIGRATE.EXE MIGRATE.EX_ 3 12/05/95 00:12 173644
MINXOBJ.DLL MINXOBJ.DL_ 6 12/05/95 00:30 37543
MIRRORS.DLL MIRRORS.DL_ 3 11/07/95 16:36 705196
MITFX001.ADD MITFX001.AD_ 6 10/30/95 15:08 20488
MOUSE.SYS MOUSE.SY_ 6 10/30/95 15:15 18169
NPXEMLTR.DLL NPXEMLTR.DL_ 6 12/04/95 23:58 20692
NWIAPI.DLL NWIAPI.DL_ 6 12/04/95 18:56 10075
OS2ASPI.DMD OS2ASPI.DM_ 6 10/30/95 14:45 10970
OS2CDROM.DMD OS2CDROM.DM_ 6 10/30/95 15:05 26580
OS2CHAR.DLL OS2CHAR.DL_ 6 12/04/95 22:37 512
OS2DASD.DMD OS2DASD.DM_ 6 10/30/95 14:44 34228
OS2DUMP OS2DUMP.___ 6 12/04/95 19:02 16909
OS2KRNL OS2KRNL.___ 2 01/11/96 17:23 571508
OS2LDR OS2LDR.___ 6 12/04/95 18:59 30208
OS2LDR.MSG OS2LDR.MS_ 6 12/04/95 19:02 8430
OS2MM.DLL OS2MM.DL_ 4 11/27/95 20:21 366710
OSO001.MSG OSO001.MS_ 5 12/04/95 18:21 174390
OSO001H.MSG OSO001H.MS_ 5 12/04/95 18:22 240113
PCM2ATA.ADD PCM2ATA.AD_ 6 06/10/95 15:30 23110
PCMCIA.SYS PCMCIA.SY_ 5 11/29/95 22:10 47622
PCMCIA.TBL PCMCIA.TB_ 6 01/24/95 19:28 1681
PMCTLS.DLL PMCTLS.DL_ 3 01/25/96 11:43 612218
PMDDE.DLL PMDDE.DL_ 6 12/05/95 00:25 24008
PMDRAG.DLL PMDRAG.DL_ 6 12/16/95 13:10 1731
FixPak Corrective Service levels and disk layouts 25
January 25 1996 Warp FixPak XR_W017
PMGPI.DLL PMGPI.DL_ 4 12/08/95 22:38 335438
PMGRE.DLL PMGRE.DL_ 6 12/12/95 21:15 2231
PMMERGE.DLL PMMERGE.DL_ 1 01/19/96 19:39 1186306
PMMLE.DLL PMMLE.DL_ 6 12/08/95 16:06 673
PMPRINT.QPR PMPRINT.QP_ 6 12/04/95 19:13 12249
PMSDMRI.DLL PMSDMRI.DL_ 6 12/08/95 16:06 12800
PMSHAPI.DLL PMSHAPI.DL_ 6 11/14/95 14:04 4549
PMSPL.DLL PMSPL.DL_ 4 12/04/95 19:35 211690
PMVDMP.DLL PMVDMP.DL_ 5 12/22/95 14:34 45851
PMVIOP.DLL PMVIOP.DL_ 5 12/22/95 14:33 54070
PMWIN.DLL PMWIN.DL_ 6 01/18/96 12:23 11264
PMWP.DLL PMWP.DL_ 2 12/04/95 20:56 939461
PMWPMRI.DLL PMWPMRI.DL_ 5 12/04/95 20:31 45342
POINTDD.SYS POINTDD.SY_ 2 08/09/95 16:23 1811
PRINT01.SYS PRINT01.SY_ 6 10/30/95 15:33 11038
PRINT02.SYS PRINT02.SY_ 6 10/30/95 15:33 10166
QUECALLS.DLL QUECALLS.DL_ 6 12/04/95 22:36 1024
RESERVE.SYS RESERVE.SY_ 6 10/30/95 14:41 5702
RESTORE.EXE RESTORE.EX_ 6 12/05/95 00:03 36080
REXX.DLL REXX.DL_ 4 09/07/95 10:20 254768
REXXAPI.DLL REXXAPI.DL_ 6 08/17/95 09:34 33735
REXXUTIL.DLL REXXUTIL.DL_ 6 06/09/95 16:49 30331
RSPDSPI.EXE RSPDSPI.EX_ 5 12/05/95 00:46 141752
RSPINST.EXE RSPINST.EX_ 4 12/04/95 22:00 342752
RUPINST2.EXE RUPINST2.EX_ 4 12/04/95 21:52 151024
SBCD2.ADD SBCD2.AD_ 1 10/30/95 15:08 18834
SEAMLESS.DLL SEAMLESS.DL_ 5 12/22/95 14:39 42112
SEMAINT.EXE SEMAINT.EX_ 5 12/05/95 00:07 65984
SESMGR.DLL SESMGR.DL_ 6 12/04/95 19:40 1536
SETBOOT.EXE SETBOOT.EX_ 6 12/04/95 21:48 19632
SIPANEL2.DLL SIPANEL2.DL_ 6 12/04/95 21:37 49472
SOM.DLL SOM.DL_ 4 10/27/95 21:00 130955
SOM.IR SOM.IR_ 4 10/27/95 21:00 496503
SOMD.DLL SOMD.DL_ 2 10/27/95 21:00 434110
SOMD.MSG SOMD.MS_ 5 10/27/95 21:01 15056
SOMDD.EXE SOMDD.EX_ 6 10/27/95 21:01 37904
SOMDSVR.EXE SOMDSVR.EX_ 6 10/27/95 21:01 34912
SOMEM.DLL SOMEM.DL_ 5 10/27/95 21:00 59700
SOMIR.DLL SOMIR.DL_ 5 10/27/95 21:01 132044
SOMK.MSG SOMK.MS_ 6 10/27/95 21:01 3718
SOMS.DLL SOMS.DL_ 6 10/27/95 21:01 31138
SOMTC.DLL SOMTC.DL_ 5 10/27/95 21:01 42432
SOMU.DLL SOMU.DL_ 5 10/27/95 21:01 126228
SONY31A.ADD SONY31A.AD_ 6 10/30/95 15:11 32588
SS2PCIC1.SYS SS2PCIC1.SY_ 6 11/29/95 22:16 10549
SS2TCIC1.SYS SS2TCIC1.SY_ 6 11/29/95 22:16 12595
SSVLSI.SYS SSVLSI.SY_ 6 11/29/95 22:20 6502
SYSINST1.EXE SYSINST1.EX_ 6 12/04/95 21:45 4224
SYSINST2.EXE SYSINST2.EX_ 5 12/04/95 21:51 149856
SYSINSTX.COM SYSINSTX.CO_ 5 12/04/95 19:04 39472
SYSLEVEL.SDS SYSLEVEL.SD_ 6 12/07/95 21:35 254
FixPak Corrective Service levels and disk layouts 26
January 25 1996 Warp FixPak XR_W017
SYSLEVEL.SEM SYSLEVEL.SE_ 6 12/07/95 21:35 191
SYSLEVEL.SIR SYSLEVEL.SI_ 6 12/07/95 21:35 188
SYSLEVEL.SRK SYSLEVEL.SR_ 6 12/07/95 21:35 185
SYSLEVEL.SUT SYSLEVEL.SU_ 6 12/07/95 21:35 177
SYSTEM.TDF SYSTEM.TD_ 6 01/19/96 17:10 82893
SYSTEM.TFF SYSTEM.TF_ 6 01/19/96 17:10 109330
TEDIT.EXE TEDIT.EX_ 6 12/05/95 00:07 9390
TESTCFG.SYS TESTCFG.SY_ 6 10/30/95 15:33 5434
TRACEFMT.DLL TRACEFMT.DL_ 6 12/05/95 00:33 18061
TRACEFMT.EXE TRACEFMT.EX_ 5 12/05/95 00:38 53793
UCDFS.DLL UCDFS.DL_ 6 12/04/95 21:24 13264
UHPFS.DLL UHPFS.DL_ 4 12/09/95 15:12 187088
UNPACK2.EXE UNPACK2.EX_ 5 12/05/95 00:11 79792
VBIOS.SYS VBIOS.SY_ 6 12/05/95 00:07 8688
VCMOS.SYS VCMOS.SY_ 6 01/06/96 08:40 2272
VCOM.SYS VCOM.SY_ 6 12/05/95 00:09 12384
VDPMI.SYS VDPMI.SY_ 6 12/05/95 00:11 22337
VDPX.SYS VDPX.SY_ 6 12/04/95 23:56 25857
VKBD.SYS VKBD.SY_ 6 12/05/95 00:11 23575
VLPT.SYS VLPT.SY_ 6 12/05/95 00:16 10113
VPIC.SYS VPIC.SY_ 6 12/05/95 00:12 9894
VTIMER.SYS VTIMER.SY_ 6 12/05/95 00:12 9936
VWIN.SYS VWIN.SY_ 6 12/05/95 00:18 24592
VXGA.SYS VXGA.SY_ 6 12/05/95 00:01 24772
WPCMPNP.DLL WPCMPNP.DL_ 2 12/05/95 00:33 131769
WPCONFIG.DLL WPCONFIG.DL_ 3 12/04/95 22:28 253747
WPHELP.HLP WPHELP.HL_ 3 12/05/95 00:16 704236
WPPRINT.DLL WPPRINT.DL_ 1 12/04/95 22:04 349829
WPPRTMRI.DLL WPPRTMRI.DL_ 5 12/04/95 22:04 47482
XDFH.MSG XDFH.MS_ 3 12/04/95 23:25 1045
*************************************************************
Product location on CSD: A:\FIX\OS2.2
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3000_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3002_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
FixPak Corrective Service levels and disk layouts 27
January 25 1996 Warp FixPak XR_W017
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3004_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\..\
..\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
COMMS.SCR COMMS.SC_ 6 12/04/95 18:49 2560
FIXMGR.DLL FIXMGR.DL_ 6 12/04/95 18:49 2048
GDIS.SCR GDIS.SC_ 6 12/04/95 18:49 6144
INSTALL.EXE INSTALL.EX_ 6 05/05/95 19:31 466324
MCISEQS.SCR MCISEQS.SC_ 6 12/04/95 18:48 2048
TIMERS.SCR TIMERS.SC_ 6 12/04/95 18:51 2048
USERS.SCR USERS.SC_ 6 12/04/95 18:49 17408
WINOS2.COM WINOS2.CO_ 6 12/04/95 18:49 31866
WINSCLIP.DLL WINSCLIP.DL_ 6 12/04/95 18:50 20480
WINSDDE.DLL WINSDDE.DL_ 6 12/04/95 18:50 24064
WINSHELD.EXE WINSHELD.EX_ 6 12/04/95 18:50 23552
WINSMSG.DLL WINSMSG.DL_ 6 12/04/95 18:50 29184
*************************************************************
Product location on CSD: A:\FIX\OS2.3
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3001_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3003_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
FixPak Corrective Service levels and disk layouts 28
January 25 1996 Warp FixPak XR_W017
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\..\
..\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
COMM.DRV COMM.DR_ 7 06/12/95 16:58 9520
COMMDLG.DLL COMMDLG.DL_ 6 01/19/96 11:46 89296
GDI.EXE GDI.EX_ 7 01/19/96 11:48 226000
INSTALL.EXE INSTALL.EX_ 7 12/04/95 21:45 476318
OS2K386.EXE OS2K386.EX_ 6 01/19/96 11:49 80066
S8514.DRV S8514.DR_ 7 06/12/95 16:53 89744
USER.EXE USER.EX_ 7 01/19/96 11:52 276736
WINSCLIP.DLL WINSCLIP.DL_ 7 01/19/96 11:50 14848
WINSDDE.DLL WINSDDE.DL_ 6 01/19/96 11:50 17920
WINSHELD.EXE WINSHELD.EX_ 6 01/19/96 11:50 20992
WINSMSG.DLL WINSMSG.DL_ 6 01/19/96 11:49 24857
*************************************************************
Product location on CSD: A:\FIX\OS2.4
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3003_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3004_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM OS/2 Base Operating System"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
FixPak Corrective Service levels and disk layouts 29
January 25 1996 Warp FixPak XR_W017
_____________________________________________________________
Default directories:
..\..\
..\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
REXX.DLL REXX.DL_ 7 12/13/95 19:50 248416
REXXAPI.DLL REXXAPI.DL_ 7 12/13/95 19:50 33415
REXXUTIL.DLL REXXUTIL.DL_ 7 12/13/95 19:50 30315
*************************************************************
Product location on CSD: A:\FIX\MPM.5
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3000_
System Id: 1000
Component Id: 562137400
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3001_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3002_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.00
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3003_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.01
FixPak Corrective Service levels and disk layouts 30
January 25 1996 Warp FixPak XR_W017
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3004_
System Id: 1000
Component Id: 562260100
Archive is ON for this product.
_____________________________________________________________
Product name: "IBM Multimedia Presentation Manager/2"
Standard Edition 3.01
Fixpak name: XR_W017_ (Country = Generic)
Pre-requisite CSD Level: XR_3005_
System Id: 1000
Component Id: 562274700
Archive is ON for this product.
_____________________________________________________________
Default directories:
..\*
Files contained in Fixpak for product:
Filename Name on CSD Disk# Date Time Size
------------ ------------ ----- -------- ----- -------
AUDIOSH.DLL AUDIOSH.DL_ 6 11/27/95 19:00 532
BUSAUDIO.SYS BUSAUDIO.SY_ 7 11/27/95 18:48 27949
CS4231.SYS CS4231.SY_ 7 06/15/95 15:39 33145
ES688DD.SYS ES688DD.SY_ 7 11/27/95 18:34 44944
MEMSH.DLL MEMSH.DL_ 8 11/27/95 18:31 12752
MMPM.DLL MMPM.DL_ 7 11/27/95 20:36 704504
MPGIO.DLL MPGIO.DL_ 7 11/27/95 18:53 25219
MVPRODD.SYS MVPRODD.SY_ 7 11/27/95 19:09 52074
SB16D2.SYS SB16D2.SY_ 7 11/29/95 10:34 62378
SBAWED2.SYS SBAWED2.SY_ 7 11/27/95 10:18 88490
SSM.DLL SSM.DL_ 6 11/27/95 18:13 1044
SSMDD.SYS SSMDD.SY_ 7 11/27/95 18:15 33272
FixPak Corrective Service levels and disk layouts 31
January 25 1996 Warp FixPak XR_W017
SPACE UTILIZATION
The FixPak installation process needs to write some files to your C:
drive even if C: is not the drive boot Warp from. These files will be
deleted when service is complete.
Min Max
--- ---
PACK.EXE 60k 60k
IBMCSFLK.EXE 11k 11k
IBMCSFLK.SYS 4k 4k
IBMCSFLK.DLL 33k 33k
IBMCSFLK.MSG 1k 1k
FIXSTART 2k 15k
CSF_SEL.000 1k 2k
--------------------------
Totals 112k 126k
Additionally, the following files will be on your boot drive:
Space Utilization 32
January 25 1996 Warp FixPak XR_W017
In the \OS2\DLL directory:
Min Max
--- ---
IBMCSFLK.DLL 33k 33k
--------------------------
Totals 33k 33k
In the \OS2\INSTALL directory:
Min Max
--- ---
SERVICE.LOG 10k 60K
IBMCSFLK.EXE 11k 11k
IBMCSFLK.SYS 4k 4k
IBMCSFLK.DLL 33k 33k
IBMCSFLK.MSG 1k 1k
IBMCSFLK.LST 1k 15K
--------------------------
Totals 60k 124k
On all drives being serviced in the directory a supported SYSLEVL
file was found in:
Min Max
--- ---
LOGF0000.OS2 10k 100k
LOGSTART.OS2 10k 100k
LOCARCH.OS2 5k 15K
---------------------------
Totals 25k 215k
Files that had service deferred because they were locked (in use by
the system), are placed in unpacked format in the \IBMCSFLK\FIX
directory tree on the drive with the most free space.
The amount of space this requires varies but can be between 1 and
12MB. These files are then moved to the correct directory on the Warp
boot drive as part of the Locked File processing which occurs when you
reboot. The directory and subdirectories are removed as part of this
processing.
Space Utilization 33