APAR= PJ12214
DATA IS CORRUPTED ON A: FLOPPY DRIVE ON RETURN FROM DOSDEVIOCTL
CALL TO LOCK FLOPPY DEVICE.

******************************************************************************
INSTALLK.EXE --

Please read the following information about the fix installation program BEFORE
you attempt to install the fixes provided. The ABSTRACT explains how the fixes
are applied to your system, and how they are managed so that additional fixes
can be applied in the future. Following the ABSTRACT are the installation
instructions, complete with examples of how to invoke the installation program.
Following the installation instructions are the descriptions of the fixes you
have received and the OS/2 system module being fixed.

ABSTRACT:
---------

The fix diskette you received contains the following files:

INSTALLK.EXE -- the fix installation program.

MODULE.LOG -- input file that tells the installation program which OS/2 system
modules are being fixed, the file containing the fix for each
module, and the location of the modules following an OS/2 2.1
installation.

*.* -- the modules containing the fix for each APAR described above.

README.1ST -- Fix installation instructions.

README.DOC -- this file, which contains the description of each APAR fixed in
the modules provided, an explanation of the files contained on
the diskette, an explanation of how fixes are applied to your
system, and instructions on how to invoke INSTALLF.EXE.

Presently, the fixes provided are new full-sized system modules, which will
replace the corresponding OS/2 2.1 GA-level system modules. Eventually, fixes
will be applied to your system modules using "patches" instead of replacing them
with new full-sized system modules. A patch can ONLY be applied to an OS/2 2.1
GA-level system module, so it's important that you follow the instructions
provided so that fixes can be applied in the future to both system modules that
have already been fixed and those that haven't. INSTALLF.EXE will "archive" the
system module being fixed to either your disk or a diskette. One of the
parameters you specify when invoking INSTALLF.EXE allows you to choose the drive
where you want the files archived, but whatever you choose, it is absolutely
necessary that you maintain these files as they will be needed each time you
want to apply fixes to your system. For example, if you specified D:, the
modules would be archived in D:\ARCHIVE.

When a fixed system module replaces the corresponding OS/2 2.1 GA-level system
module for the first time, the OS/2 2.1 GA-level system module is saved in the
\ARCHIVE directory of the drive you specified when invoking INSTALLF.EXE. This
is considered the "current" fix. If the same system module needs to be replaced
again, the current fixed system module is backed-up on the same drive you
specified to archive files to, and the new fixed system module is copied to the
directory where the current system module had been. For example, if you
specified D:, the current system module would be saved in D:\BACKUP.

**** NOTE 1 ********************************************************************
Presently, "true" Backout is not supported in INSTALLF.EXE. If you have a need
to return your system to the OS/2 2.1 GA-level (ie. you need to reinstall a fix
due to some failure), you will be required to copy the OS/2 2.1 GA-level module
you need from the \ARCHIVE directory into the directory where the corresponding
system module exists. If you have a need to return your system to a previous fix
level, you will be required to copy the system module you need from the \BACKUP
directory into the directory where the corresponding system module exists.
**** END NOTE 1 ****************************************************************

INSTALLF.EXE maintains a record of all fixes applied to your system in the log
file LOGU001.OS2. This log file is maintained on the same drive where you have
OS/2 2.1 installed, and in the directory \OS2\INSTALL. Another parameter you
specify when invoking INSTALLF.EXE is the drive where OS/2 2.1 is installed. For
example, if OS/2 2.1 is installed on the C: drive, the log file would be
maintained in C:\OS2\INSTALL.

**** NOTE 2 ********************************************************************
IT IS ABSOLUTELY NECESSARY that you maintain the location of the 2 items just
described to you: 1.) the archived OS/2 2.1 GA-level system modules, and 2.) the
log file LOGU001.OS2. The archived system modules and the log file are REQUIRED
each time you want to apply fixes to your system. If you specified the disk
drive on which you want to store the system modules, DO NOT delete the directory
\ARCHIVE, AND, DO NOT delete the directory \OS2\INSTALL where the log file is
stored. If you specified a diskette drive on which you want to store these
files, DO NOT erase the contents or lose the diskettes. If these files are not
available, you will have to re-install the OS/2 2.1 GA-level diskettes if you
want to apply new fixes.
**** END NOTE 2 ****************************************************************


KEY PROCEDURES PERFORMED BY INSTALLF.EXE:
-----------------------------------------

1.) ARCHIVING -- This is the process of storing an OS/2 2.1 GA-level system
module in the directory \ARCHIVE on the specified logical
drive.

2.) BACKING-UP -- This is the process of saving current fixed system modules
that exist from previous fixes in the directory \BACKUP on the
specified logical drive. If there is ever a need to return the
system to a previous fix level, then you can copy the system
module you need from this directory into the directory where
the corresponding system module exists.

3.) SERVICE LOGGING -- INSTALLF.EXE maintains a record of all service activity
performed on your system in the file LOGU001.OS2.
INSTALLF.EXE requires this file to determine if fixes
have ever been applied to your system, and if so, where
to locate the files that have been stored. If you are
installing multiple fixes from a pervasive 'pak',
INSTALLF.EXE will record the service information to the
temporary file LOGU001.BAK. When all fixes have been
applied, LOGU001.BAK will be written to LOGU001.OS2. If
you interrupt INSTALLF.EXE while it is applying fixes, do
not erase LOGU001.BAK. INSTALLF.EXE needs this file to
continue applying fixes when you re-run INSTALLF.EXE.



INSTALLATION INSTRUCTIONS:
--------------------------

**** NOTE 3 ********************************************************************
INSTALLF.EXE will attempt to copy the fixed system module into the path where it
was installed during the installation of OS/2 2.1. If the file does not exist in
the assumed path, you will be prompted for its location. For example, if the
file being replaced is actually located in \OS2\DLL_BAK, you would enter that
path-name when prompted.
**** END NOTE 3 ****************************************************************



1.) If the system module being fixed is being used by the operating system, it
will be necessary to do the following so that a patch can be applied:

a.) Start your system using the OS/2 2.1 Installation Diskette.

b.) When prompted, insert Diskette 1.

c.) When prompted to continue or escape, press the ESC key to get to a
command prompt. Continue to step 2.

2.) To install the fixes, type the following at the command prompt and then
press enter:

INSTALLF source dest arch-back

where:

source is the source drive where the files from the fix diskette can be
found. INSTALLF.EXE can apply the fixes from either your disk
drive or diskette drive. If you choose to apply the fixes from
your disk drive, make sure you copy ALL files from the fix
diskette to the disk drive. For example, if you copied the files
from the fix diskette to C:\FIX, then source would be C:\FIX. If
you want to apply fixes from the diskette drive, then source
would be A:.

dest is the drive letter of the system partition where OS/2 2.1 is
installed. For example, if OS/2 2.1 is installed on C:, then
dest would be C:.

arch-back is the logical drive where you want the OS/2 2.1 GA-level
modules that are being fixed stored, AND, where fixed modules
from previous fixes are backed-up. The directories \ARCHIVE and
\BACKUP will be created. For example, if you want these files
stored on your D: drive, then arch-back would be D:. If you want
these files stored on a diskette in your A: drive, then
arch-back would be A:.

EXAMPLE: If you choose to install the fixes from your A: diskette drive,
and OS/2 2.1 is installed on C:, and you want \ARCHIVE and \BACKUP
on your D: drive, then you would enter the following:

INSTALLF A: C: D:

As soon as INSTALLF.EXE has been started, it is important that you allow it to
finish installing all of the fixes that you have received. The message "Fix
successfully installed" will be displayed when the installation is complete. If
this message does not appear, or INSTALLF.EXE ended for some other reason,
please follow the error message and re-run INSTALLF.EXE if necessary.

3.) The service log maintained in \OS2\INSTALL\LOGU001.OS2 is stored in an
unreadable format. If there is a service requirement to view the service
log, you can view the log file by entering the following:

INSTALLF drive

where:

drive is the drive where OS/2 2.1 is installed.

EXAMPLE: If OS/2 2.1 is installed on the C: drive, you would enter the
following:

INSTALLF C:

If you would like to print the log file, simply redirect the output of the
previous command to a print device attached to your system. For example:

INSTALLF C: > lpt1:

**** NOTE 4 ********************************************************************
We suggest that you store INSTALLF.EXE on your disk drive so that if you ever
need to view the service log, the program is available to do so.
**** END NOTE 4 ****************************************************************

APAR= PJ12214
DATA IS CORRUPTED ON A: FLOPPY DRIVE ON RETURN FROM DOSDEVIOCTL
CALL TO LOCK FLOPPY DEVICE.

******************************************************************************
INSTALLK.EXE --

Please read the following information about the fix installation program BEFORE
you attempt to install the fixes provided. The ABSTRACT explains how the fixes
are applied to your system, and how they are managed so that additional fixes
can be applied in the future. Following the ABSTRACT are the installation
instructions, complete with examples of how to invoke the installation program.
Following the installation instructions are the descriptions of the fixes you
have received and the OS/2 system module being fixed.

ABSTRACT:
---------

The fix diskette you received contains the following files:

INSTALLK.EXE -- the fix installation program.

MODULE.LOG -- input file that tells the installation program which OS/2 system
modules are being fixed, the file containing the fix for each
module, and the location of the modules following an OS/2 2.1
installation.

*.* -- the modules containing the fix for each APAR described above.

README.1ST -- Fix installation instructions.

README.DOC -- this file, which contains the description of each APAR fixed in
the modules provided, an explanation of the files contained on
the diskette, an explanation of how fixes are applied to your
system, and instructions on how to invoke INSTALLF.EXE.

Presently, the fixes provided are new full-sized system modules, which will
replace the corresponding OS/2 2.1 GA-level system modules. Eventually, fixes
will be applied to your system modules using "patches" instead of replacing them
with new full-sized system modules. A patch can ONLY be applied to an OS/2 2.1
GA-level system module, so it's important that you follow the instructions
provided so that fixes can be applied in the future to both system modules that
have already been fixed and those that haven't. INSTALLF.EXE will "archive" the
system module being fixed to either your disk or a diskette. One of the
parameters you specify when invoking INSTALLF.EXE allows you to choose the drive
where you want the files archived, but whatever you choose, it is absolutely
necessary that you maintain these files as they will be needed each time you
want to apply fixes to your system. For example, if you specified D:, the
modules would be archived in D:\ARCHIVE.

When a fixed system module replaces the corresponding OS/2 2.1 GA-level system
module for the first time, the OS/2 2.1 GA-level system module is saved in the
\ARCHIVE directory of the drive you specified when invoking INSTALLF.EXE. This
is considered the "current" fix. If the same system module needs to be replaced
again, the current fixed system module is backed-up on the same drive you
specified to archive files to, and the new fixed system module is copied to the
directory where the current system module had been. For example, if you
specified D:, the current system module would be saved in D:\BACKUP.

**** NOTE 1 ********************************************************************
Presently, "true" Backout is not supported in INSTALLF.EXE. If you have a need
to return your system to the OS/2 2.1 GA-level (ie. you need to reinstall a fix
due to some failure), you will be required to copy the OS/2 2.1 GA-level module
you need from the \ARCHIVE directory into the directory where the corresponding
system module exists. If you have a need to return your system to a previous fix
level, you will be required to copy the system module you need from the \BACKUP
directory into the directory where the corresponding system module exists.
**** END NOTE 1 ****************************************************************

INSTALLF.EXE maintains a record of all fixes applied to your system in the log
file LOGU001.OS2. This log file is maintained on the same drive where you have
OS/2 2.1 installed, and in the directory \OS2\INSTALL. Another parameter you
specify when invoking INSTALLF.EXE is the drive where OS/2 2.1 is installed. For
example, if OS/2 2.1 is installed on the C: drive, the log file would be
maintained in C:\OS2\INSTALL.

**** NOTE 2 ********************************************************************
IT IS ABSOLUTELY NECESSARY that you maintain the location of the 2 items just
described to you: 1.) the archived OS/2 2.1 GA-level system modules, and 2.) the
log file LOGU001.OS2. The archived system modules and the log file are REQUIRED
each time you want to apply fixes to your system. If you specified the disk
drive on which you want to store the system modules, DO NOT delete the directory
\ARCHIVE, AND, DO NOT delete the directory \OS2\INSTALL where the log file is
stored. If you specified a diskette drive on which you want to store these
files, DO NOT erase the contents or lose the diskettes. If these files are not
available, you will have to re-install the OS/2 2.1 GA-level diskettes if you
want to apply new fixes.
**** END NOTE 2 ****************************************************************


KEY PROCEDURES PERFORMED BY INSTALLF.EXE:
-----------------------------------------

1.) ARCHIVING -- This is the process of storing an OS/2 2.1 GA-level system
module in the directory \ARCHIVE on the specified logical
drive.

2.) BACKING-UP -- This is the process of saving current fixed system modules
that exist from previous fixes in the directory \BACKUP on the
specified logical drive. If there is ever a need to return the
system to a previous fix level, then you can copy the system
module you need from this directory into the directory where
the corresponding system module exists.

3.) SERVICE LOGGING -- INSTALLF.EXE maintains a record of all service activity
performed on your system in the file LOGU001.OS2.
INSTALLF.EXE requires this file to determine if fixes
have ever been applied to your system, and if so, where
to locate the files that have been stored. If you are
installing multiple fixes from a pervasive 'pak',
INSTALLF.EXE will record the service information to the
temporary file LOGU001.BAK. When all fixes have been
applied, LOGU001.BAK will be written to LOGU001.OS2. If
you interrupt INSTALLF.EXE while it is applying fixes, do
not erase LOGU001.BAK. INSTALLF.EXE needs this file to
continue applying fixes when you re-run INSTALLF.EXE.



INSTALLATION INSTRUCTIONS:
--------------------------

**** NOTE 3 ********************************************************************
INSTALLF.EXE will attempt to copy the fixed system module into the path where it
was installed during the installation of OS/2 2.1. If the file does not exist in
the assumed path, you will be prompted for its location. For example, if the
file being replaced is actually located in \OS2\DLL_BAK, you would enter that
path-name when prompted.
**** END NOTE 3 ****************************************************************



1.) If the system module being fixed is being used by the operating system, it
will be necessary to do the following so that a patch can be applied:

a.) Start your system using the OS/2 2.1 Installation Diskette.

b.) When prompted, insert Diskette 1.

c.) When prompted to continue or escape, press the ESC key to get to a
command prompt. Continue to step 2.

2.) To install the fixes, type the following at the command prompt and then
press enter:

INSTALLF source dest arch-back

where:

source is the source drive where the files from the fix diskette can be
found. INSTALLF.EXE can apply the fixes from either your disk
drive or diskette drive. If you choose to apply the fixes from
your disk drive, make sure you copy ALL files from the fix
diskette to the disk drive. For example, if you copied the files
from the fix diskette to C:\FIX, then source would be C:\FIX. If
you want to apply fixes from the diskette drive, then source
would be A:.

dest is the drive letter of the system partition where OS/2 2.1 is
installed. For example, if OS/2 2.1 is installed on C:, then
dest would be C:.

arch-back is the logical drive where you want the OS/2 2.1 GA-level
modules that are being fixed stored, AND, where fixed modules
from previous fixes are backed-up. The directories \ARCHIVE and
\BACKUP will be created. For example, if you want these files
stored on your D: drive, then arch-back would be D:. If you want
these files stored on a diskette in your A: drive, then
arch-back would be A:.

EXAMPLE: If you choose to install the fixes from your A: diskette drive,
and OS/2 2.1 is installed on C:, and you want \ARCHIVE and \BACKUP
on your D: drive, then you would enter the following:

INSTALLF A: C: D:

As soon as INSTALLF.EXE has been started, it is important that you allow it to
finish installing all of the fixes that you have received. The message "Fix
successfully installed" will be displayed when the installation is complete. If
this message does not appear, or INSTALLF.EXE ended for some other reason,
please follow the error message and re-run INSTALLF.EXE if necessary.

3.) The service log maintained in \OS2\INSTALL\LOGU001.OS2 is stored in an
unreadable format. If there is a service requirement to view the service
log, you can view the log file by entering the following:

INSTALLF drive

where:

drive is the drive where OS/2 2.1 is installed.

EXAMPLE: If OS/2 2.1 is installed on the C: drive, you would enter the
following:

INSTALLF C:

If you would like to print the log file, simply redirect the output of the
previous command to a print device attached to your system. For example:

INSTALLF C: > lpt1:

**** NOTE 4 ********************************************************************
We suggest that you store INSTALLF.EXE on your disk drive so that if you ever
need to view the service log, the program is available to do so.
**** END NOTE 4 ****************************************************************

**** DISCLAIMER *********************************************************
This fix will only be supported until the release of the ServicePak for
OS/2 2.1 which contains it. At that time, to receive continued support
you should obtain that ServicePak.
*************************************************************************

To INSTALL this fix perform the following steps :

1. Boot your system from the OS/2 2.1 Installation diskette

2. Insert diskette #1 when prompted to do so

3. Press the Esc key when the "Welcome to OS/2" screen appears

4. Insert Fix diskette into drive A

5. [A:\]Enter "installf a: c: c:" and press the enter key

a= Drive letter of Fix source

c= Drive letter where OS/2 2.1 is installed

c= Drive letter where a copy of the module(s) being replaced
will be stored.

6. Shut system down and reboot

Note: If the module(s) for this fix is/are NOT being accessed by the
system at the time of install, start at step 4 above by
changing the default drive to A: in an OS/2 Window or
Full Screen.

For detailed information about APARS included and the Fix installation process,
read the README.DOC file on this diskette.