Sponsored by ScheduPerformance, Inc.
  Guaranteed faster user response/throughput for your OS/2 programs!
New Version 2.4 of Priority Master II at http://www.prioritymaster.com

****************************** WarpCast ******************************
Source: L. Mark Stone (LMStone@ibm.net)
Moderator: Dirk Terrell (admin@os2ss.com)
**********************************************************************
 
If a user creates a BootOS2 partition on their hard disk 
after using CSF139, subsequent servicing of the BootOS2 
partition will also service the partition from which 
BootOS2 was generated.

CSF139 modifies the syslevel.os2 file of the partition 
being serviced by (among other things) adding the full 
drive:\pathname of the directories serviced.

BootOS2 copies the syslevel.os2 file to the new BootOS2 
partition, as part of the BootOS2 installation.

The following scenario will result in the unintended 
servicing of a production partition to a reduced service 
level:

1. User uses CSF139 to backout previously applied fixpack 
   and bring Drive D:, the Production partition, to 9.023.
3. User, while booted from D:, creates a BOOTOS2 partition 
   on Drive E:
2. User runs CSF139 to bring Drive D: to 9.032
4. User runs CSF139 to bring BOOTOS2 partition to 9.029
5. Both Drive D: and Drive E: will be serviced to 9.029, 
   EVEN THOUGH THE USER ONLY SELECTED DRIVE E: TO BE
   SERVICED!

There are two interim "solutions:"

1. Never service a BOOTOS2 partition if that BOOTOS2 
partition is created from another partition previously 
serviced with CSF139.

2. After creating a BOOTOS2 partition, replace the 
syslevel.os2 file by copying the GA-level syslevel.os2 file 
from the installation diskettes.

The IBM Fixpack folks and Ken Kahn are aware of this 
problem.




----------------------------------------------------------------------
To subscribe, unsubscribe, or for more information on
WarpCast, visit: http://www.warpcast.com/
----------------------------------------------------------------------