OS/2 Shareware BBS: 17 Fixes30/17-Fixes30.zip/kbd16077.zip/PJ16077.APR

Text File | 1994-12-08 | 12KB | 143 lines

.FO OFF
.RH ON
Item Number  PJ16077      - OPN
.SP 2
.RH OFF
  APAR Identifier ...... PJ16077      Last Changed ........ 94/12/08
  SYSTEM HANGS ON WARP DISK1 WITH A BLANK SCREEN, CURSOR BLINKING
  IN TOP LEFT. IBMKBD.SYS BROKEN/REGRESSED.

  Symptom ...... AB MKBCMAPAR         Status ........... OPEN
  Severity ................... 1      Date Closed .........
  Component .......... 562260100      Duplicate of .........
  Reported Release ......... 300      Fixed Release ............
  Component Name OS/2 WARP V3         Special Types ..
  Current Target Date ..              Type of Relief ..Not Available
  SCP ................... OS/2        Platform ............ OS/2

  Status Detail: Not Available

  PE PTF List:

  PTF List:


  Parent APAR:
  Child APAR list:


  ERROR DESCRIPTION:
  Booting up the system to do WARP installation.
  Goes thru installation disk and prompts for disk1 as normal.
  Goes thru OS/2 logo, "loading please wait" panel and then
  screen turns blank, cursor goes in top left, floppy light goes
  off and system appears to be hung. Ctrl+Alt+Del does not work
  at this point and a hard reset has to be performed.
  If an Alt+F2 is done on Installation Diskette then on disk1 it
  shows all driver being loaded up and after "testcfg.sys" it
  goes to hang. Modify the config.sys on disk1 and have
  PROTSHELL=CMD.EXE
  and now it brings up an OS/2 full screen but the prompt keeps
  rolling as if <enter> key is stuck down.
  .
  The problem is occuring on different kind of clone systems.
  Right now there are three users reporting the same problem and
  they all have relatively newer AMI BIOS.
   40-E301-000000-10111111-121593-UMC498-H
   40-0100-009999-00111111-040493-80486-H
   40-E300-001437-00111111-121593-GREEN-H


  LOCAL FIX:
  The keyboard driver (IBMKBD.SYS) from OS/2 v2.11 or WARP Beta
  II should allow WARP to installed successfully.
  .
  L1OK
  ...
  There is a workaround available for this problem. PJ16077
  opened for the hang on OEM systems on disk1 with a black screen
  is related to a keyboard code problem.
  .
   To verify the problem is PJ16077
  .
  1) The user should copy config.sys PROTSHELL= statement under
     the original statement.
  2) type REM in front of the first statement.
  3) Then change the second PROTSHELL statement to = CMD.EXE ( we
     want to boot to a command prompt)
  4) Try the install again.
  5) This time instead of hanging the system should boot to an
     OS/2 fullscreen and the prompt should keep scrolling as if
     the ENTER key were being held down.  If this is what the
     user is seeing then this confirms PJ16077.
  .
   There are currenlty two workarounds to this problem:
  .
  1) The user can use the BETA Warp copy of IBMKBD.SYS file.
     This file is located on disk1. If the user does not have the
     beta copy they can obtain the copy from our SDM BBS system
     at 407-443-8000.
  .
  (sign on as a new user if you do not already have an account)
  .
   After signing on they will do a "F" command to go to FILE
   menu, then an "S" command for select.., then input "12" when
   prompted for an area for the private exchange, then do a "D"
   command for download, the filename is IBMKBD.SYS.
  .
  2) The user should rename the original ibmkbd.sys file on disk1
     prior to replacing it with the newly downloaded file.
  3) Start the install again.
  .
   This has worked for the majority of users seeing this problem.
   If it does not, then they can try the following:
  .
   1)If they have a 2.11 or earlier version of OS/2 they need to
     get the KBD01.SYS file located in the \os2 directory.
  .
   2)Rename the KBDBASE.SYS file on the WARP disk1 to KBDBASE.ORG
   3)Copy the KBD01.SYS file to the WARP1 disk1 as KBDBASE.SYS
   4)Edit the WARP config.sys file to REM out the
     BASEDEV=IBMKBD.SYS statement.
   5)Retry the Install.
  .
  If none of these work the user may have a keyboard which is
  truly not being seen as an enhanced keyboard by the system.  It


  may have worked in prior versions of OS/2, but it probably
  really was being seen as an AT style keyboard
  .
  The symptoms to see if this true is to enter the E editor under
  the OS/2 version.  Type some data, press enter, type more date
  so you have at least two lines, then try to use the extended
  keys( keys loctaed between the numpad and the keyboard area).
  If they just do not work or they display an alpha
  or beta character for any key pressed then the keyboard is
  being seen as an AT style keyboard and not a true enhanced
  type.
  .
  This problem is due to keyboard itself not coming back in the
  IBM specified time limit with its Hardware ID Bytes when
  queried by the the device driver. The norm is to default to an
  AT style when this happens as this is how those
  keyboards work.  Under previous versions these keyboards had no
  problems installing, but then showed this type behavior.  It
  appears in WARP, they may be part of the problem installing so
  the user can try another brandname keyboard to install to see
  if this works.
  .
  Known 2.11 and prior keyboards that MAY have experienced this
  problem as being seen as an AT style were SOME Mitsumi,
  Compudyne, Zena, Tangent, BTC, and DTC 101 series, Honeywell,
  Fujitsu and other no name brands usually the lower end priced
  keyboards.
  .
  The problem is being worked to identify a solution, however, if
  it is found to be due to these keyboards not returning their
  hardware bytes in the time specified they will still default to
  AT style keyboards after a sucessful install and the user
  should be aware this latter problem is not an IBM code
  issue.
  .