<  TIPS for recovering from FixPak problems















  

  
  



  October 18, 1996

  
  
  
  OS/2 Fix Distribution
  Personal System Products
  Austin, Tx
  
  
  (c) Copyright International Business Machines Corporation, 1994, 1996.
  All rights Reserved.

  October 18, 1996 - Warp FixPak TIPS



                    October 18, 1996 - Warp FixPak TIPS

  CONTENTS


    Recovering from Installation problems ............................ 1
    No files to service .............................................. 1
    Previous installation interrupted ................................ 2
    Unable to open Archive directory ................................. 2

    System problems after FixPak installation ........................ 3
    OS/2 is unable to operate your hard disk or diskette drive.  ..... 3
    Updating systems with the CMD chipset ............................ 4
    RZ1000 and CMD640 Data Problems (APAR=PJ19409) ................... 4
    RIPL failure ..................................................... 5
    SYS3175 when opening LS 4.0 Lan Server Administration ............ 6
    Traps when canceling print jobs after FixPak is installed ........ 7
    Novell Requester ................................................. 7
    CC:Mail for OS/2 ................................................. 7
    Rapid Resume Fix ................................................. 8
    No Window list when you press Ctrl+Esc ........................... 8
    IBM CODE/400 at V3R1M0 level ..................................... 8
    TCP/IP at level WR08152 .......................................... 9
    DOSCALL1.DLL Error ............................................... 9
    Problem with AUTODRV2.SYS after FixPak install ................... 9

    Recovering FixPak Archive and Backup space ...................... 11

    Additional problems and fixes ................................... 12
    SYS2070/SYS0182 in WPPRINT.DLL .................................. 12
    Keyboard input doesn't reach windows which have the focus ....... 13
    Intermittent TRAP 000E after installing this FixPak ............. 13
    TRAP 000E at startup with ESS688 Sound Source ................... 13
    Drives object or folder view is blank ........................... 13
    IBM ADSM client does not work properly .......................... 14
    WinOS/2 communications application drops connection ............. 14
    SERVICE.EXE SYS3175 while applying FixPak ....................... 14
    "OS/2 is unable to operate your hard disk or diskette drive" .... 14
    Unable to access previously working IDE CD-ROM drive ............ 15
    "Application Error" dialog in WinOS/2 seamless sessions ......... 15
    "Unrecoverable Application Error" in WinOS/2 seamless apps ...... 15
    Visual artifacts remain when pop-up windows are erased .......... 15
    Color values incorrect in Solid Color Palette object ............ 16
    DOS game WarCraft II reports not enough memory .................. 16
    WPS 5908 " " error dialog ....................................... 16
    TRAP 000E starting WinOS/2 sessions ............................. 16
    Clear and Simple Performance Plus v3 Optimizer window hangs ..... 17
    Mouse pointer remains centered on screen, does not move ......... 17
    Lantastic for OS/2 fails to install ............................. 17
    TDGammon colors are incorrect after applying FixPak ............. 17
    Unable to access SyQuest EZ-Drive (IDE) after applying FixPak ... 17
    Intermittent system hangs when PMQSIZE running .................. 18
    MMPM/2 not serviced when using FSERVICE ......................... 18

  
                                                            Contents  ii


                    October 18, 1996 - Warp FixPak TIPS

    System Setup -> Add Programs .................................... 18
    WebExplorer/2 makes increased demands on swap file .............. 18

    Related information ............................................. 20
    WARPINST ........................................................ 20
    The "SIQ fix" ................................................... 20
    PCI and RZ1000 or CMD640 EIDE chipset ........................... 21
    HTML version of Mr. McKenneys document "OS/2 Warp FixPack 17 Update"  21












































  
                                                           Contents  iii


                    October 18, 1996 - Warp FixPak TIPS

  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  1


                    October 18, 1996 - Warp FixPak TIPS

  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  2


                    October 18, 1996 - Warp FixPak TIPS

  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 moves 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
      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.





  
                            System problems after FixPak installation  3


                    October 18, 1996 - Warp FixPak TIPS

  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


  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.

  
                            System problems after FixPak installation  4


                    October 18, 1996 - Warp FixPak TIPS

  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:

  IBM's benchmarks show no system performance degradation from disabling
  the read-ahead mode in either the RZ1000 or CMD640 IDE PCI interface
  chips.


  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 this FixPak 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).

  
                            System problems after FixPak installation  5


                    October 18, 1996 - Warp FixPak TIPS

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


  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

  
                            System problems after FixPak installation  6


                    October 18, 1996 - Warp FixPak TIPS

      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



  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 the "README.1ST" file.

  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 OS2Cx.EXE (OS2C1, OS2C2, OS2C3, etc.). 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).


  
                            System problems after FixPak installation  7


                    October 18, 1996 - Warp FixPak TIPS

  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.


  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

  
                            System problems after FixPak installation  8


                    October 18, 1996 - Warp FixPak TIPS

  with this fixpack.


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

  Ž   Verify that all RUN statements have the fully qualified PATH to
      the file.
  Ž   .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.


  PROBLEM WITH AUTODRV2.SYS AFTER FIXPAK INSTALL

  If you get the following message after installing this FixPak

     The system cannot find the file "AUTODRV2.SYS". This device driver,
     program or data file is not located in the default directory.


  and you responded OK to a popup dialog about the files listed below
  being newer on your harddisk than in the FixPak, or you did not

  
                            System problems after FixPak installation  9


                    October 18, 1996 - Warp FixPak TIPS

  receive the popup dialogs then you can try backing them out to the
  Backup or Archive versions.

  Note: Use Backup if this is not the first FixPak applied to your
  system. Use Archive otherwise.

  Ž   AUTODRV2.SYS
  Ž   IBM2SS01.SYS
  Ž   PCM2ATA.ADD
  Ž   PCMCIA.SYS

  Do the following to backout these files.

  Note: x: means your OS/2 Warp boot drive. Also, AUTODRV2.SYS resides
  in two directories, make sure you replace both copies.

  1.  Shut down your system.
  2.  Reboot with your Installation or Utility disks.
  3.  Rename x:\AUTODRV2.SYS to AUTODRV2.SYO
  4.  Rename x:\OS2\AUTODRV2.SYS to AUTODRV2.SYO
  5.  Rename x:\OS2\PCM2ATA.ADD to PCM2ATA.ADO
  6.  Rename x:\OS2\PCMCIA.SYS to PCMCIA.SYO
  7.  Change to the FixPak Backup or Archive directory
  8.  Enter  UNPACK AUTODRV2.SY_ x:\
  9.  Enter  UNPACK AUTODRV2.SY_ x:\OS2
  10. Enter  UNPACK IBM2SS01.SY_ x:\OS2
  11. Enter  UNPACK PCM2ATA.AD_ x:\OS2
  12. Enter  UNPACK PCMCIA.SY_ x:\OS2
  13. Reboot your system























  
                           System problems after FixPak installation  10


                    October 18, 1996 - Warp FixPak TIPS

  RECOVERING FIXPAK ARCHIVE AND BACKUP SPACE

  Warning: Make sure you read and understand the following before
  removing the Archive and Backup files and directories.

  You can recover the space used for FixPak Archive and Backup files as
  long as you understand that doing this prevents you from being able to
  backout to the previous Backup or Archive level. If it becomes
  necessary at a later time to backout a FixPak, the only way you can do
  this is to reinstall Warp.

  Do the following to delete the FixPak Backup and Archive files and
  remove the files used by CSF to keep track of what service has been
  applied to your system.

  1.  Delete every instance of the following files on your system
      (search every drive and every directory they contain).
      Ž   LOGF0000.*   (can be OS2 or MPM)
      Ž   LOGSTART.*   (can be OS2 or MPM)
      Ž   LOGARCH.*    (can be OS2 or MPM)
      Ž   CSF_*.*
      Ž   FIXSTART
  2.  Delete the files in the FixPak Archive and Backup directories on
      your harddisk.
  3.  Remove the FixPak Archive and Backup directories with the RMDIR
      command.


























  
                          Recovering FixPak Archive and Backup space  11


                    October 18, 1996 - Warp FixPak TIPS

  ADDITIONAL PROBLEMS AND FIXES

  The following problems and fixes or work-arounds are extracted from a
  document called "OS/2 Warp FixPack 17 Update" which was created and is
  maintained by Frank McKenney of McKenney Associates.

  Frank has graciously consented to allow us (IBM) to extract much of
  the data from his document for inclusion in this TIPs file. In most
  cases the data that follows is exactly as in Frank's original document
  except where references to FixPak 17 (XR_W017) have been made more
  generic.


  SYS2070/SYS0182 IN WPPRINT.DLL

  Two sources have confirmed that this is one of several possible
  results of installing this FixPak using a back-level set of CSF Boot
  Diskettes. In this particular case, the FixPak version of WPPRINT.DLL
  has been installed, but the corresponding PMSPL.DLL file has not.

  Fix: Obtain the F.127 release CSF Boot Diskettes and reinstall this
  FixPak.  Since the system has been left in an unusable state, simply
  rerunning SERVICE.EXE is not an option.

  Ž   Obtain current level CSF Boot Diskettes and reinstall this FixPak
      by booting from CSF Boot Diskette 1. Note that this will
      1.  update all serviceable partitions and it will
      2.  not apply this FixPak to any installed copies of Multimedia
          Presentation Manager extensions (MMPM/2) unless you modify the
          RESPONSE.FIL control file on CSF Boot Diskette 2.

  Ž   Re-boot and press Alt-F1 when the boot-blob (small white
      rectangle) appears, then, at the selection screen, press C to open
      a full screen command prompt. Using the examples from the
      README.1ST file, restore the pre-FixPak copy of WPPRINT.DLL from
      the FixPak Archive or Backup directory. Reboot. Once the system is
      operational, obtain the F.127 CSF Boot Diskettes and reapply this
      FixPak.

  Note: Systems where FixPak XR_W016 had been previously installed may
  not see this specific problem. It appears that the XR_W016 PMSPL.DLL
  is "close enough" to this FixPak version so the error is avoided.
  However, the absence of this particular error does <not> mean that
  other problems won't eventually surface as the result of using
  back-level CSF Boot Diskettes for installation.







  
                                       Additional problems and fixes  12


                    October 18, 1996 - Warp FixPak TIPS

  KEYBOARD INPUT DOESN'T REACH WINDOWS WHICH HAVE THE FOCUS

  Occasionally, when the focus is shifted to a window (as reflected by
  its title bar changing color), keyboard input is ignored. Mouse clicks
  and movement are responded to, but any keystrokes (with the possible
  exception of Ctl-Alt-Del) are not acted upon by the application.  This
  occurs mainly (perhaps exclusively) with "character mode" (VIO)
  windows, such as the OS/2 and DOS command prompts.

  Workaround: Click on another window, then back on the original.


  INTERMITTENT TRAP 000E AFTER INSTALLING THIS FIXPAK

  This may be the result of using a backlevel set of CSF Boot Diskettes,
  so please check the SERVICE.EXE file if you run into this problem.

  Workaround: Back out FixPak.


  TRAP 000E AT STARTUP WITH ESS688 SOUND SOURCE

  Users with ESS688 sound support (COMPAQ, other laptops) may see a TRAP
  000E when STARTUP.WAV plays during WPS startup.

  Workaround: Comment out the SSMDD.SYS entry in CONFIG.SYS. If the TRAP
  000E error no longer occurs, try restoring the previous version of
  SSMDD.SYS.

  Note: The workaround may cause problems with WinOS/2 session sound
  (dialog box with only an exclamation point, loss of WPS Sounds). If
  this happens, reinstall the August ESS688 drivers from the ESS
  Technologies BBS.


  DRIVES OBJECT OR FOLDER VIEW IS BLANK

  Occasionally the Drives object will be empty when opened, and the
  pop-up menu "Refresh now" item has no effect. Over time other windows
  stop repainting, and eventually a Shutdown or Ctl-Alt-Del reboot is
  required.

  Note: This should not be confused with a different problem which
  causes occasional four-second WPS/PM "pauses" when refreshing or
  repainting a PM window or WPS container. The "hang" also causes
  incorrect font display, may be display driver-related (Cirrus
  GD-543x?), and predates this FixPak.

  Workaround: None known. Back out FixPak if severe.



  
                                       Additional problems and fixes  13


                    October 18, 1996 - Warp FixPak TIPS

  IBM ADSM CLIENT DOES NOT WORK PROPERLY

  When running the IBM ADSTAR Distributed Storage Manager client,  drive
  lines never appear. IBM has created APARs IC11363 and PJ21756 to track
  this problem.

  Workarounds:

  Ž   Run ADSM from the command line. For details on how to use this
      interface, type DSMC HELP.
  Ž   Apply fix IC12349 (includes the V2R1L0.2 ASDSM client) from

      ftp://index.storsys.ibm.com/adsm/temp/ic12349.exe




  WINOS/2 COMMUNICATIONS APPLICATION DROPS CONNECTION

  Microsoft Mail Remote disconnects after transferring small amounts of
  data.

  Workaround: Restore the pre-FixPak copies of COM.SYS and VCOM.SYS.

  Note: This workaround may be effective for other WinOS/2
  communications problems seen after applying this FixPak.


  SERVICE.EXE SYS3175 WHILE APPLYING FIXPAK

  PMMERGE may be reported. Currently this is being attributed to a lack
  of disk space and/or backlevel CSF Boot Diskettes.

  Workaround: Make sure you are using level F.127 CSF Boot Diskettes and
  have at least 20 Mb of free space in your Archive or Backup partition.


  "OS/2 IS UNABLE TO OPERATE YOUR HARD DISK OR DISKETTE DRIVE"

  CMD640 EIDE PCI chipset. This is caused by the use of FixPak-level
  IBM1S506.ADD and IBMIDECD.FLT drivers without the corresponding CMD640
  drivers being added to CONFIG.SYS.

  Workaround: Add CMD640.ADD and CMDATAPI.FLT entries to CONFIG.SYS per
  the instructions in README.1ST ("UPDATING SYSTEMS WITH THE CMD
  CHIPSET").






  
                                       Additional problems and fixes  14


                    October 18, 1996 - Warp FixPak TIPS

  UNABLE TO ACCESS PREVIOUSLY WORKING IDE CD-ROM DRIVE

  CMD640 EIDE PCI chipset. CMDATAPI.FLT driver missing from CONFIG.SYS
  or driver not being initialized due to use of /FL parameter on
  IBM1S506.ADD driver.

  Workaround: Ensure that the CMDATAPI.FLT driver has been added to
  CONFIG.SYS per the instructions in README.1ST ("UPDATING SYSTEMS WITH
  THE CMD CHIPSET"). If the /FL parameter has been added to
  IBM1S506.ADD, remove it.


  "APPLICATION ERROR" DIALOG IN WINOS/2 SEAMLESS SESSIONS

  The dialog "Application Error: Application Closing" may apear for no
  apparent reason when WinOS/2 applications are being run in "seamless"
  mode (windowed on the WPS Desktop). When the pop-up is acknowledged,
  processing may or may not continue. Only certain applications seem to
  be affected (Corel Draw and PhotoPaint, MS PowerPoint, VMMPEG, Xing
  Streamworks, and the MSWin Media (AVI) Player have been mentioned),
  but this may be system-dependent.

  Workarounds:

  Ž   Run the application(s) from a WinOS/2 Full Screen session.
  Ž   Restore the pre-FixPak copies of WINSHELD.EXE and WINOS2.COM from
      the Archive or Backup directory.
  Ž   Restore the MSWindows directory from a backup of the directory
      made prior to installing this FixPak.



  "UNRECOVERABLE APPLICATION ERROR" IN WINOS/2 SEAMLESS APPS

  This message appears shortly after starting certain WinOS/2
  applications in seamless mode, and the application ends. Netscape and
  HoTMetaL Pro have been mentioned as having this problem.

  Workaround: None currently known.


  VISUAL ARTIFACTS REMAIN WHEN POP-UP WINDOWS ARE ERASED

  Reported with FileManager/2 "popup" window descriptions and popup
  windows using WM_SAVEBITS style.

  Workaround: None known.





  
                                       Additional problems and fixes  15


                    October 18, 1996 - Warp FixPak TIPS

  COLOR VALUES INCORRECT IN SOLID COLOR PALETTE OBJECT

  Workaround: Use the Create another menu option from the bad object's
  pop-up menu to create a second Solid Color Palette object. This one
  will have the correct values.


  DOS GAME WARCRAFT II REPORTS NOT ENOUGH MEMORY

  WCII may also report "error resetting digital sound" and possibly
  other errors.

  Workaround: Restore the pre-FixPak copies of DOSKRNL, VDPMI.SYS, and
  possibly VKBD.SYS. See also 'war2os2.zip' in the /incoming directory
  of hobbes.nmsu.edu.


  WPS 5908 " " ERROR DIALOG

  The following dialog may be seen when opening a freshly-formatted
  diskette from the Drives object:

    5908 " "
    An error has occurred and the message is not accessible. Contact the
    supplier of the application.


  This is an annoyance, but not, as far as I can tell, serious. It is
  apparently being triggered when the "EA DATA. SF" and "WP ROOT. SF"
  files have not yet been created on the diskette. Presumably this could
  affect other removable media (e.g. IOMEGA ZIP drives). This odd dialog
  has been seen as far back as FP13, and may appear under other
  circumstances.

  Workaround: Click on the [OK] button. If you opened a Tree or Icon
  view, the problem will be corrected when you close the view (the files
  will be created on the diskette).


  TRAP 000E STARTING WINOS/2 SESSIONS

  ATI Mach64-based display adapter.

  Workaround: Update the display driver from the ATI BBS or from the IBM
  PC Company FTP site at

      ftp://ftp.pcco.ibm.com/pub/os2_drivers/mach64.zip.





  
                                       Additional problems and fixes  16


                    October 18, 1996 - Warp FixPak TIPS

  CLEAR AND SIMPLE PERFORMANCE PLUS V3 OPTIMIZER WINDOW HANGS

  Workaround: Obtain the C&S v3.2 update package, either from the C&S
  Home Page at http://www.clear-simple.com/ or from the OS/2 Shareware
  BBS at (703) 385-4325.


  MOUSE POINTER REMAINS CENTERED ON SCREEN, DOES NOT MOVE

  Moving the mouse or clicking the mouse buttons does not have any
  visible effect on the mouse pointer, but MemSize/Pulse show that the
  system is responding to the activity.

  Workaround:

  Ž   Check the mouse-related entries in CONFIG.SYS and correct them if
      necessary.
  Ž   Restore the pre-FixPak version of MOUSE.SYS. If this does not fix
      the problem, try backing out PDDEVICE.SYS, and COM.SYS as well.



  LANTASTIC FOR OS/2 FAILS TO INSTALL

  Lantastic for OS/2 installation procedure exits without any error
  message, but installation has not completed.

  Workaround: Back out FixPak, install Lantastic, then reapply FixPak.
  Once it has been completely installed, Lantastic should work properly.


  TDGAMMON COLORS ARE INCORRECT AFTER APPLYING FIXPAK

  Changes made to the Settings notebook colors have no effect.

  Workaround: None known. One user has reported that reinstalling
  TDGammon fixed the problem. Another user reported that it did not.


  UNABLE TO ACCESS SYQUEST EZ-DRIVE (IDE) AFTER APPLYING FIXPAK

  Reinstalling the SyQuest drivers does not correct the problem.

  Workaround: None known.








  
                                       Additional problems and fixes  17


                    October 18, 1996 - Warp FixPak TIPS

  INTERMITTENT SYSTEM HANGS WHEN PMQSIZE RUNNING

  PMQSIZE is a utility which increases the size of the OS/2 message
  queue in order to reduce the effect of applications which "hog" the
  queue. The FixPak "SIQ fix" code addresses this problem in a more
  comprehensive manner, so PMQSIZE is no longer needed.

  Workaround: Remove PMQSIZE from STARTUP.CMD


  MMPM/2 NOT SERVICED WHEN USING FSERVICE

  If this FixPak is applied using FSERVICE (booting from the CSF Boot
  Diskettes) the MMPM/2 product (normally in the \MMOS2 directory) will
  not be updated. To update MMPM/2 support to this FixPak level, either
  run A:\SERVICE and select the appropriate MMPM/2 product or make the
  appropriate changes to the RESPONSE.FIL control file on CSF Boot
  Diskette 2 and re-run FSERVICE.

  Note:  This is simply a result of the control statements in the
  default RESPONSE.FIL, which can be customized as required. It does not
  apply to this FixPak when installed using A:\SERVICE.


  SYSTEM SETUP -> ADD PROGRAMS

  The Add Programs object's "Add new programs" option ignores its
  previous efforts and treats all programs as "new"; it will replace
  previously-created objects with new ones each time it is run. The old
  objects will vanish, even if they have been moved, customized settings
  will be lost, and the links between shadows and the old objects will
  be broken.

  Workaround:

  Ž   Revert to the pre-FixPak version of MIGRATE.EXE.
  Ž   Avoid using the "Add new programs" option when running Add
      Programs.



  WEBEXPLORER/2 MAKES INCREASED DEMANDS ON SWAP FILE

  Many users have reported that WE/2 causes the swap file to grow more
  quickly, and much larger, than it did before this FixPak was
  installed. A number of users have reported only minor increases in
  swap requirements, or none. The reasons for this are unclear.

  Workaround: Limit the amount of document/image caching done by WE/2.
  Using the Configure->Caching menu item, turn on the Disable all
  caching checkbox. If this fixes the problem, turn caching back on, but

  
                                       Additional problems and fixes  18


                    October 18, 1996 - Warp FixPak TIPS

  set limits on the amount of caching WE/2 will do. Several users have
  also recommended turning off the "Display images while downloading"
  option.

















































  
                                       Additional problems and fixes  19


                    October 18, 1996 - Warp FixPak TIPS

  RELATED INFORMATION

  The following information is related to Warp FixPaks and was also
  extracted from Mr. McKenneys document.


  WARPINST

  IBM released FixPack-level Installation Diskette update kits with Warp
  FixPacks 5 and 10 (WFWIN5.ZIP, WFWIN10.ZIP). A replacement update
  package, known as "WARPINST vn.nnn", can be obtained from supported
  IBM PSP distribution sites such as TalkLink, AOL, and CompuServe
  (vn.nnn will be the same as the FixPak Build level in the FixPak
  README.1ST file).  This file will be updated as each new Warp FixPak
  is released.

  WARPINST can also be retrieved from the IBM Internet PSP support site
  at

      ftp://service.boulder.ibm.com

  in the

      /ps/products/os2/fixes/v3.0warp/english-us/warpinst directory.




  THE "SIQ FIX"

  One of the fixes included in this FixPak is something called the "SIQ
  fix".  The FixPak README.1ST file shows how to activate this fix, but
  it doesn't provide any details on how the "SIQ fix" works, or what
  exactly is being fixed. The following summary may be helpful.

  While OS/2 is a generally robust system, there are times when it will
  stop responding to user input. When this condition is the result of a
  hardware problem, such as an adapter failure, all activity ceases and
  a restart is required. However, in other cases there is activity on
  the screen to indicate that the system is still capable of performing
  useful work (e.g.  output continues scrolling in a window, the hands
  on the System Clock object keep moving, previously-started file
  transfers continue). All that seems to be missing is a way to get the
  system's attention.

  This FixPak contains changes to the normal OS/2 input handling support
  which are specifically intended to reduce the frequency of such
  problems, and to make it less likely that application software to
  cause these kinds of problems. Because these changes affect the
  behavior of user applications, the changes are disabled by default,
  but they can be enabled by adding the following line to CONFIG.SYS:

  
                                                 Related information  20


                    October 18, 1996 - Warp FixPak TIPS

        SET PM_ASYNC_FOCUS_CHANGE=ON


  Once this code is enabled, when an application fails to respond to
  system requests within a reasonable time (the default is two seconds,
  but this may be adjusted), OS/2 will flag the application as
  "non-responsive" and allow other applications a chance to receive
  input. If the offending application later responds to OS/2's queries,
  it will be returned to "normal" status and OS/2 will allow it to
  receive user input again.

  At the same time, the FixPak support for cancelling an application
  from the OS/2 Workplace Shell Window List has been enhanced to
  recognize these "non-responsive" applications and make additional
  efforts to shut them down when the user requests. The improvements
  will also make sure that if an application is in a "non-responsive"
  state when OS/2 starts to shut down, additional efforts will be made
  to cancel the application as cleanly as possible.

  The February issue of IBM's online OS/2 Warp Newsletter has an article
  that goes into a little more depth on this topic. You can locate this
  issue, and previous issues, at

    http://www.austin.ibm.com/pspinfo/newsletters.html.




  PCI AND RZ1000 OR CMD640 EIDE CHIPSET

  If you have a PCI bus motherboard which uses the RZ1000 or CMD640 EIDE
  support chipset, you should obtain a copy of Roedy Green's EIDE Bugs
  FAQ.  It is available by anonymous ftp from the following sites:

      ftp://ftp.cdrom.com/.4/os2/sysutil/eidete19.zip
      ftp://garbo.uwasa.fi/pc/diskutil/eidete19.zip




  HTML VERSION OF MR. MCKENNEYS DOCUMENT "OS/2 WARP FIXPACK 17 UPDATE"

  The Team OS/2 Cincinnati User Group has created an HTML version of
  this document and made it available to the Internet community at

      http://www.cincyteamos2.org/.






  
                                                 Related information  21
