To begin the IBM ThinkPad 710T fix procedure, change drives to the drive where
the FIXIT disk is inserted.

example:    A:

Then type:  FIXIT <drive where OS/2 resides>

example:    FIXIT C:

FIXIT will update your CONFIG.SYS to include the new power management driver for
the IBM ThinkPad 710T.  It will also update the PCMCIA and mouse drivers, and
install a fix for COM.SYS.

The original CONFIG.SYS will reside in CONFIG.710.  Make sure that CONFIG.710
doesn't exist prior to running FIXIT.  If it does, your original CONFIG.SYS will
not be backed up.

The following describes the COM.SYS fix for the IBM ThinkPad 710T.

===============================================================================


APAR included in this fix package is:
PJ08728
 TRAP000D CS:EIP  08F0:00001406 CSLIM 0000299F REV. 6.514 IN
 COM.SYS WHEN PROTECTONLY=YES.

***  NOTE *******
You have been sent a full-module replacement of the fix.
Presently patch files are not available. They will be provided
in the near future. The INSTALLF.EXE install procedure still
handles full-module replacement. Please follow the directions
below to install the fix. You must use this install procedure
to keep your system in a serviceable state. Your EA's will not
be preserved with full-module replacement. However you can
restore your EA's manually since your current module is archived.
*****************

                                                       August 3, 1993

INSTALLF.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:

INSTALLF.EXE -- the fix installation program.

PATCH.EXE    -- the program that applies the fix to the OS/2 2.1 GA-level
                system module.

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.

*.RTP        -- the patch file containing the fix for each module being fixed.
                For example, if the module PMWIN.DLL is being fixed, the patch
                file would be PMWIN.RTP.

Fixes are applied to your system modules using "patches" instead of replacing
them with new full-sized system modules. A patch file contains the fix for a
system module. A patch can ONLY be applied to an OS/2 2.1 GA-level system
module. 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 patch file is applied to its corresponding system module for the first
time, the patch file is saved in the same directory as the system module that is
being fixed. This is considered the "current" patch. If another patch file is
applied to the same system module, the current patch in the modules' directory
is backed-up on the same drive you specified to archive files to, and the new
patch file becomes the current patch file in the modules' directory. For
example, if you specified D:, the patch files would be saved in D:\BACKUP.
If there were ever a need to return your system to a previous fix level, the
patch files would be available to do this. This is called a "Backout"
capability.

**** NOTE 1 ********************************************************************

Presently Backout is not supported in INSTALLF.EXE. If you have a need to return
your system to a previous fix level, you will be required to copy the original
OS/2 2.1 GA level module from the \ARCHIVE 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 3 items just
described to you: 1.) the archived OS/2 2.1 GA-level system modules, 2.) the
backed-up patch files, and 3.) 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.

The patch files are stored in the directory \BACKUP on the same drive you
specified to archive the system modules. Again, DO NOT delete this directory or
lose the diskettes on which the files are stored. They are REQUIRED if you
ever have the need to return your system to a previous fix level.

**** END NOTE 2 ****************************************************************



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

1.) PATCHING -- INSTALLF.EXE uses PATCH.EXE to apply a patch to an OS/2 2.1
                GA-level system module. As described before, the corresponding
                patch file for any given system module will have a file-name
                extension of .RTP. For example, if the module PMGRE.DLL is being
                fixed, the patch file would be PMGRE.RTP. The most recent patch
                file applied will be stored in the same directory as the module
                being fixed. Again, DO NOT erase this file. Once INSTALLF.EXE
                has been started, it is important that you allow it to finish
                installing all of the patches that you have received.

2.) 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.

3.) BACKING-UP -- This is the process of saving patch files that exist from
                  previous fixes in the directory \BACKUP on the specified
                  logical drive. INSTALLF.EXE looks here for patch files if
                  there were ever a need to return the system to a previous fix
                  level. If it is the first time that a patch is being applied
                  to a system module, and you need to return the system to the
                  previous level, then INSTALLF.EXE would look in \ARCHIVE for
                  the GA-level module.

4.) 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 uses EAUTIL.EXE to maintain EA's that might exist on system modules
that are being fixed. EAUTIL.EXE must be present in the directory \OS2.
INSTALLF.EXE will look on the drive you specified where OS/2 2.1 is installed.
INSTALLF.EXE will attempt to patch a system module in 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 patched is actually located in \OS2\DLL_BAK, you would enter that
path-name when prompted.

**** END NOTE 3 ****************************************************************

To Install the fix(es), do the following:

    1. Boot your system with the OS/2 2.1 Installation Diskette.

    2. When prompted, insert Disk 1.

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

    4. INSTALLF A: C: D:

       A:   - drive and path where you are installing the fix from
       C:   - drive OS/2 is installed on ( usually C: )
       D:   - drive where you are backing up the modules being replaced

      More information on INSTALLF:

      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 patches from either your disk
                drive or diskette drive. If you choose to apply the patches 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 patched stored, AND, where patch files
                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 patches 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:


Once INSTALLF.EXE has been started, it is important that you allow it to finish
installing all of the patches 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.


*********************************************************************

Additional information:

 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 ****************************************************************
