+=====================================================================+
|           FixPax for IBM OS/2 WARP 3.0 SYSLEVEL XR03000             |
|                                                                     |
|           Second release                       03/06/95             |
+=====================================================================+

                              IMPORTANT

  DOWNLOADING THE SERVICE FIX THAT FOLLOWS, INDICATES YOUR ACCEPTANCE OF
  THE FOLLOWING TERMS AND CONDITIONS:

  - YOU MUST BE, AND YOU AGREE THAT YOU ARE, A PRIOR LICENSEE
    OF OS/2 VERSION 3.0
  - YOU MAY MAKE COPIES OF THE OS/2 VERSION 3.0 SERVICE FIX
    EQUAL TO THE NUMBER OF LICENSED COPIES OF OS/2 VERSION
    3.0 YOU POSSESS
  - YOU MAY ONLY USE THIS SERVICE FIX FOR MAINTENANCE PURPOSES
  - ALL OTHER TERMS AND CONDITIONS OF YOUR OS/2 VERSION 3.0
    LICENSE AGREEMENT APPLY TO THIS SERVICE FIX; HOWEVER,
    THIS DOES NOT EXTEND ANY WARRANTY OUTLINED IN SUCH
    AGREEMENT.

+=====================================================================+
|                     FixPak release 1 notes                          |
+=====================================================================+
If you have successfully applied the first release of this FixPak there
is no reason or need for you to apply this one. If you have a Future
Domain SCSI and received a message like the following at boot after the
FixPak was completely installed

  "OS2 is unable to operate your hard drive or diskette drives. The
  system is stopped. Correct the preceding error and restart the system."

you can recover by unpacking the archived files from your archive directory
to the right location on your boot drive.

As an example, if your archive directory was D:\ARCH and you were booting
Warp from C: then you would enter the following commands to restore the
files to their original state.

UNPACK D:\ARCH\FD16-700.AD_ C:\OS2\BOOT
UNPACK D:\ARCH\FD7000EX.AD_ C:\OS2\BOOT
UNPACK D:\ARCH\FD8XX.AD_    C:\OS2\BOOT

+=====================================================================+
|                        Space Utilization                            |
+=====================================================================+
The FixPak install process needs to write some files to your C: drive
even if C: is not where you 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 file will be on your boot drive in the \OS2\DLL
directory:

                     Min   Max
                     ---   ---
    IBMCSFLK.DLL     33k   33k
    --------------------------
    Totals           33k   33k

On your boot drive 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 the drive being serviced in the \OS2\INSTALL directory:

                     Min   Max
                     ---   ---
    LOGF0000.OS2     10k   100k
    LOGSTART.OS2     10k   100k
    LOCARCH.C         5k    15K
    ---------------------------
    Totals           25k   215k

On the drive with the most free space in the \IBMCSFLK\FIX directory
(and sub-directories) files that had service deferred because they were
locked (in use) are placed in unpacked format. The amount of space this
requires varies but can be between 1 and 4MB. These files are then moved
to the correct directory as part of the Locked File process when you reboot,
the directory and subdirectories are then removed.

+=====================================================================+
|                        Installation Notes                           |
+=====================================================================+
1) You will need the OS/2 Warp 3.0 Corrective Service Facility boot
   disks to install this FixPak. These files should be available from
   the same place you got this FixPak from as

   WARPBDSK.1DK - Corrective Service Facility disk 1
   WARPBDSK.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 compressed file.

   To create diskettes from the disk image files you need LOADDSKF.EXE.
   This is also available from the same place you got this FixPak from
   as

   LDF.COM      - Self extracting file that will create LOADDSKF.EXE.
                  Place in a separate directory on your harddisk then
                  enter LDF.

      - or -

   LOADDF.ZIP   - File compressed with PKZIP, contains LOADDSKF.EXE.
                  Requires PKUNZIP or UNZIP to extract original files
                  from 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:

   a. Enter LOADDSKF WARPBDSK.1DK A: /F
        Label as CSF DISK Diskette 1                          (SP DISK 1)

   b. Enter LOADDSKF WARPBDSK.2DK A: /F
        Label as CSF DISK Diskette 2                          (SP DISK 2)

   c. Enter LOADDSKF XR0W005.1DK A: /F
        Label as FixPak XR0W005 Corrective Service Diskette 1 (CSF DISK 1)

   d. Enter LOADDSKF XR0W005.2DK A: /F
        Label as FixPak XR0W005 Corrective Service Diskette 2  (CSF DISK 2)

   e. Enter LOADDSKF XR0W005.3DK A: /F
        Label as FixPak XR0W005 Corrective Service Diskette 3  (CSF DISK 3)

2) If you installed OS/2 Warp 3.0 from a CD-ROM some files being updated
   may have the Read Only attribute set. This will cause the update
   program to ask you if you want them replaced. Answer OK.

3) If the following files are not updated on your system after this
   FixPak has been applied then you must install this FixPak a second
   time without backing out the first install. This should correctly
   update these files:

          USERS.SCR
          WINOS2.COM
          WINSMSG.DLL

   To check if the files were updated look at the SERVICE.LOG in the
   \OS2\INSTALL directory. There should be two entries for each file.
   The entries should look (for example) like one of the following:

         Archiving for x:\WINDOWS\SYSTEM\USERS.SCR.
         Updating x:\WINDOWS\SYSTEM\USERS.SCR

                         or

         Archiving for x:\WINDOWS\SYSTEM\USERS.SCR.
         Deferring service of x:\WINDOWS\SYSTEM\USERS.SCR

     (x: is the drive where Microsoft Windows is installed.)

   If the entries are not there then you need to repeat the install of
   this FixPak as mentioned above. Do not back out the first install
   of this FixPak. Just repeat the install a second time.

   If this does not update the above files then you will need to do this
   manually as follows.

   - Locate where the above files reside in your Windows directory.
       Normally WINOS2.COM will be in C:\WINDOWS.
       Normally USERS.SCR will be in C:\WINDOWS\SYSTEM.
       Normally WINSMSG.DLL will be in C:\WINDOWS\SYSTEM.

   - Make a backup copy of each of the files.

   - Place FixPak XR0W005 Corrective Service disk 2 in A:.
   - Enter UNPACK A:\FIX\OS2.1\WINOS2.CO_ C:\WINDOWS

   - Place FixPak XR0W005 Corrective Service disk 3 in A:.
   - Enter UNPACK A:\FIX\OS2.1\USERS.SC_ C:\WINDOWS\SYSTEM
   - Enter UNPACK A:\FIX\OS2.1\WINSMSG.DL_ C:\WINDOWS\SYSTEM

4) Important for MultiMedia users. Perform the following before applying
   this FixPak if you have MultiMedia installed on your system and
   MVPRODD.SYS and/or CS4231.SYS are in the MMOS2 directory.

   By default a FixPak will only update files in the root (\) and OS2
   (\OS2) directory (and it's subdirectories). To update files in other
   directories like MMOS2 for MVPRODD.SYS and S4231.SYS contained in
   this FixPak you need to do the following:

   - Create a file USERDIRS.OS2 in the \OS2\INSTALL directory of the
     OS\2 Warp partition to be serviced.

   - Locate where MVPRODD.SYS and CS4231.SYS are currently located on
     your system. If they are not on your system then you do not need
     to do this step. If it is C:\MMOS2 (for instance) place a line in
     this file as shown:

     C:\MMOS2

     DO NOT include the trailing backslash.

     Note: This capability will also work if you have moved any of the
           directories that would normally be under \OS2 to other drives.
           Just add them to the above file.

     Note: Leave this file for any future OS/2 Warp FixPaks you may
           apply.

5) 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 (XR03000), therefore
   the SYSLEVEL is not changed. All fix information is recorded in the
   SERVICE.LOG.

   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 release level and other related
   information use the SYSLEVEL command.

6) If you get a "No files to service" message while applying this FixPak
   then the Current CSD level or Component ID of the "IBM OS/2 Base
   Operating System" is incorrect. Correct values must be:

         Current CSD level: XR03000
              Component Id: 562260100

   If these values are correct then check for the following files:

         CSF_SEL.000
         LOGF0000.OS2
         LOGSTART.OS2

   If any of them exist then rename them and try the FixPak install again.
   If it works then delete the renamed files.

7) See the README2 file on this same disk for a list of APARs fixed.

+=====================================================================+
|                        Installation Process                         |
+=====================================================================+
To INSTALL this fix perform the following steps:

 1. Insert CSF DISK Diskette 1 in A:.

 2. Open an OS/2 window or Full Screen.

 3. Enter a:\service and press the ENTER key.

    Note: DO NOT boot CSF DISK Diskette 1. This method is only for
          use with CID install and requires a response file tailored
          to your system.

 4. Follow displayed instructions. When prompted to insert Corrective
    Service Diskette 1 (not CSF DISK Diskette 1) place FixPak XR0W005
    Corrective Service Diskette 1 in a:. Repeat for disk 2 and disk 3
    when requested to do so.

 5. If this is the first OS/2 v3.0 Warp FixPak you have applied to
    this system then enter the path where a copy of replaced file(s)
    will be stored in the ARCHIVE directory, Ex. D:\ARCHIVE.

    Note: This ARCHIVE directory is not related to the ARCHIVES directory
          built into OS/2 Warp 3.0. Please specify a different path.

    If this is not the first OS/2 Warp v3.0 FixPak then enter the path
    where a copy of replaced file(s) will be stored in the BACKUP directory,
    EX. D:\BACKUP.

    For either case make sure there is a sufficient space available. Even
    though these files are kept in compressed (PACK2) format they will
    require 4.5MB 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. Please select
    Continue.

    During the install process you will see messages about Archiving,
    Updating and Deferring service.

    - Archiving saves a copy of the original file in the archive path you
      specified.

    - Updating means the original files is replaced with the new one 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 the \OS2\INSTALL\IBMCSFLK\FIX directory on your Warp
      boot drive in unpacked format for use by the locked file device
      driver during reboot after you shutdown.

 7. Select NO for redisplay of "Product List" when displayed (after
    the first part of the FixPak apply process has completed) if this
    is displayed.

 8. Click Cancel and Exit to close the Corrective Service Facility window
    if necessary.

 9. Shut down and reboot your system.

10. You should see the following during reboot.

    The locked file driver is loaded.

           Processing locked files

           Processing complete

    At this point the system may do an automatic reboot.

Note: The entries in CONFIG.SYS for Locked File device driver support will
      remain after the installation has completed. This means that every
      time you boot you will see the message about "Locked File device
      driver". You can remove these entries from CONFIG.SYS and then
      delete the IBMCSFLK.* files from your harddisk.

      The CONFIG.SYS entries will look similar to the following:

      DEVICE=C:\OS2\INSTALL\IBMCSFLK.SYS C:\OS2\INSTALL\IBMCSFLK.LST
      RUN=C:\OS2\INSTALL\IBMCSFLK.EXE C:\OS2\INSTALL\IBMCSFLK.LST

      C: above will actually be your Warp boot partition.

+=====================================================================+
|                  FixPak Corrective Service Notes                    |
+=====================================================================+
Product name:  "IBM Operativsystem/2"
Standard Edition  3.00
FixPak name:  XRNW005_   (Country = Norway)
Pre-requisite CSD Level:  XRN3000_
System Id:  1000
Component Id:  562260100
Archive is ON for this product.

Files contained in CSD for product:

Filename      Name on CSD   Disk#  Date      Time   Size
------------  ------------  -----  --------  -----  -------
AHA152X.ADD   AHA152X.AD_     2    12/12/94  15:36    38044
AHA164X.ADD   AHA164X.AD_     3    12/12/94  15:36    19716
AIC7870.ADD   AIC7870.AD_     2    12/15/94  16:01    34092
ARCINST.EXE   ARCINST.EX_     3    02/03/95  19:44    21774
ARCRECOV.EXE  ARCRECOV.EX_    2    02/03/95  19:45    24635
BTSCSI.ADD    BTSCSI.AD_      3    12/12/94  15:40    22737
CHKDSK.COM    CHKDSK.CO_      2    02/03/95  20:47    69168
COM.SYS       COM.SY_         3    12/12/94  15:46    16888
CS4231.SYS    CS4231.SY_      3    01/04/95  15:33    33145
DOSCALL1.DLL  DOSCALL1.DL_    1    02/03/95  21:02   137084
E.EXE         E.EX_           2    02/03/95  20:42    70917
HPFS.IFS      HPFS.IF_        2    02/03/95  19:53   135746
IBM1FLPY.ADD  IBM1FLPY.AD_    2    12/15/94  15:57    31058
IBM1S506.ADD  IBM1S506.AD_    3    01/15/95  21:21    28328
IBM2AMB1.SYS  IBM2AMB1.SY_    3    12/12/94  17:01    13708
IBM2AST1.SYS  IBM2AST1.SY_    3    12/12/94  17:00    11201
IBM2CAD1.SYS  IBM2CAD1.SY_    3    12/12/94  17:04    13743
IBM2CMQ1.SYS  IBM2CMQ1.SY_    3    12/12/94  17:01    11240
IBM2FLPY.ADD  IBM2FLPY.AD_    3    01/06/95  19:17    13754
IBM2MAT1.SYS  IBM2MAT1.SY_    3    12/12/94  17:03    11201
IBM2NCR1.SYS  IBM2NCR1.SY_    3    12/12/94  17:02    11201
IBM2NEC1.SYS  IBM2NEC1.SY_    3    12/12/94  17:02    11201
IBM2SCSI.ADD  IBM2SCSI.AD_    3    12/01/94  11:39    32629
IBM2SS01.SYS  IBM2SS01.SY_    3    12/12/94  16:59    14367
IBM2SS02.SYS  IBM2SS02.SY_    3    12/12/94  17:00    11576
IBM2TOS1.SYS  IBM2TOS1.SY_    3    12/12/94  16:59    11217
IBM2ZEN1.SYS  IBM2ZEN1.SY_    3    12/12/94  16:58    11201
IBM2ZOS1.SYS  IBM2ZOS1.SY_    3    12/12/94  17:03    11217
IBMIDECD.FLT  IBMIDECD.FL_    3    01/10/95  20:47    20490
IBMKBD.SYS    IBMKBD.SY_      3    01/06/95  20:05     5572
MITFX001.ADD  MITFX001.AD_    3    01/24/95  20:15    20482
MVPRODD.SYS   MVPRODD.SY_     2    01/10/95  19:44    52074
OS2DASD.DMD   OS2DASD.DM_     2    01/04/95  20:52    33578
OS2DUMP       OS2DUMP.___     3    01/10/95  17:24    12251
OS2KRNL       OS2KRNL.___     1    02/02/95  21:23   556026
OS2LDR        OS2LDR.___      3    01/10/95  17:23    30208
OS2MM.DLL     OS2MM.DL_       2    01/30/95  18:44   372854
PCMCIA.SYS    PCMCIA.SY_      3    01/24/95  20:20    41990
PCMCIA.TBL    PCMCIA.TB_      1    12/12/94  15:21     1681
PMGRE.DLL     PMGRE.DL_       3    12/12/94  18:58     2216
PMMERGE.DLL   PMMERGE.DL_     1    02/03/95  21:55   873150
PMSHAPI.DLL   PMSHAPI.DL_     3    02/03/95  20:35     4549
PMWP.DLL      PMWP.DL_        2    02/03/95  19:55   933881
PRINT01.SYS   PRINT01.SY_     3    01/04/95  21:23    11038
PRINT02.SYS   PRINT02.SY_     3    01/04/95  21:23    10166
RESERVE.SYS   RESERVE.SY_     3    12/12/94  15:31     5686
SBCD2.ADD     SBCD2.AD_       3    12/12/94  15:42    18834
SESMGR.DLL    SESMGR.DL_      3    02/03/95  20:09     1536
SONY31A.ADD   SONY31A.AD_     3    12/15/94  16:06    32480
SYSTEM.TDF    SYSTEM.TD_      3    02/02/95  22:14    71980
SYSTEM.TFF    SYSTEM.TF_      2    02/02/95  22:14   183417
UHPFS.DLL     UHPFS.DL_       2    02/03/95  20:02   181968
USERS.SCR     USERS.SC_       2    01/18/95  15:27    16896
VCOM.SYS      VCOM.SY_        3    02/14/95  14:56    12384
VWIN.SYS      VWIN.SY_        1    12/12/94  21:46    24560
WINOS2.COM    WINOS2.CO_      2    01/31/95  08:43    31502
WINSMSG.DLL   WINSMSG.DL_     3    01/18/95  15:29    28672
WPPRINT.DLL   WPPRINT.DL_     2    02/03/95  20:06   369285

+=====================================================================+
|                           Additional Notes                          |
+=====================================================================+

1: To view the Corrective Service Facility documentation:

   A. Insert Corrective Service Facility disk 1 in A:

   B. Enter view a:readme.inf and press the ENTER key
