Return to BSD News archive
Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!uunet!gossip.pyramid.com!decwrl!csus.edu!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Intel Keyboard BUG?
Message-ID: <jmonroyC5F175.G8x@netcom.com>
Keywords: keyboard bug intel
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
Date: Tue, 13 Apr 1993 09:33:05 GMT
Lines: 43
INTEL BUG ?
-----------
I found this on comp.periphs. I may be of interest to
those working on console programming, if you don't already
have this information.
====================================================================
From: br.pct@RLG.Stanford.EDU (Peter C. Tam)
Subject: P8742AH intel keyboard controller
Organization: Research Libraries Group, Inc.
Date: Tue, 30 Mar 1993 01:55:42 GMT
Strange Story:
I was able to re-program the keyboard controller INSIDE Windows
3.1 keyboard device driver to do no scan code conversion ONLY ON A
COMPUADD 333. For an IBM PS2, AST 386, COMPUADD 433, COMPUADD 325
they just ignore the programming, and remain in scan code translation
mode.
Is this related to the BIOS of each micro? COMPUADD 333 has
Phoenix BIOS 1.10.1, COMPUADD 333 & 433 has Phoenix BIOS 1.10.0.
Swapping the keyboard controller (P8742AH Intel Chip) between
CompuADD 325 and CompuADD 333 makes no difference.
Does the above description indicates it is a ROM BIOS difference?
AST 386 has AST386 BIOS, PS2 well must have IBM microchannel....
For COMPUADD 433, even worse thing happens, it only goes into
no scan code translation only after it exit Windows 3.1!!
Can anyone tell me what do I miss here???? & Thanks for any info!!!
___________________________________________________________________________
Jesus Monroy Jr jmonroy@netcom.com
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________