home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.ibm.pc.hardware:23405 comp.os.msdos.programmer:9054 comp.sys.ibm.pc:482 comp.sys.ibm.pc.programmer:370 comp.sys.ibm.pc.misc:12241
- Path: sparky!uunet!spool.mu.edu!uwm.edu!rutgers!cmcl2!panix!schuster
- From: schuster@panix.com (Michael Schuster)
- Newsgroups: comp.sys.ibm.pc.hardware,comp.os.msdos.programmer,comp.sys.ibm.pc,comp.sys.ibm.pc.programmer,comp.sys.ibm.pc.misc
- Subject: Re: Why does HIMEM.SYS not work with some keyboard chips?
- Message-ID: <1992Sep4.124920.15914@panix.com>
- Date: 4 Sep 92 12:49:20 GMT
- References: <1992Sep4.023741.3497@leela.cs.orst.edu>
- Organization: PANIX Public Access Unix & Internet, NYC
- Lines: 17
-
- In article <1992Sep4.023741.3497@leela.cs.orst.edu> youngqd@atlantis.CS.ORST.EDU (Dean Youngquist) writes:
- >My keyboard stopped responding after I installed HIMEM.SYS today. After
- >some fussing and fretting I determined that this only happened with
- >AWARD keyboard BIOS 1.5. I changed to another keyboard BIOS chip and
- >the problem was solved. BTW it was on a Hyundai 286. How could an other-
- >wise working keyboard chip stop working because of HIMEM.SYS ? Has anyone
- >else had this problem ?
-
- The first 64K of upper memory is accessed by toggling the A20 address
- line via an unused output port of the keyboard controller. If your
- keyboard controller has shitty code (Award is FAMOUS for this; try
- OS/2 for a real treat) it may produce unpredictable results.
-
- --
- _______________________________Mike Schuster________________________________
- NY Pub. Access UNIX/Internet: schuster@panix.com | 70346.1745@CompuServe.COM
- The Portal (R) System: schuster@cup.portal.com | MCI Mail,GEnie: MSCHUSTER
-