philbo@dhw68k.cts.com (Phil Lindsay) (03/27/91)
From: philbo@dhw68k.cts.com (Phil Lindsay)
Newsgroups: comp.sys.windows.programmer
Subject: HIMEM/QEMM511 Problem: Keyboard Shift state locks...
References:
Sender:
Followup-To:
Distribution: na
Organization: Wolfskill & Dowling residence; Anaheim, CA (USA)
Keywords: QEMM HIMEM KEY WINDOWS
Has anyone experienced keyboard problems with their machines when
running 386 memory managers or HIMEM? The problems I am having
are: 1. The shift state locks, the top QWERTY row of my keyboard won't
produce numbers and the keys ",./" always input as "<>?" ... 2. When
the cursor pad is used (not numeric cursor pad) I get single
character 9's every once in a while when cursoring around. The
problem seems to persist more when I run programs like PWB, TurboC or
Brief. ...Any ideas? Thanks in advance. -phil
--
Phil Lindsay - "Patents threaten future technology"
Internet: philbo@dhw68k.cts.com Phone: Wrk7143852311 Hm7142891201
UUCP: {spsd,zardox,felix}!dhw68k!philbo
USMAIL: 152A S. Cross Creek Rd, Orange, Ca. 92669hd7x@vax5.cit.cornell.edu (Sanjay Aiyagari) (04/03/91)
In article <1991Mar27.064315.28498@dhw68k.cts.com>, philbo@dhw68k.cts.com (Phil Lindsay) writes: > Has anyone experienced keyboard problems with their machines when > running 386 memory managers or HIMEM? The problems I am having > are: 1. The shift state locks, the top QWERTY row of my keyboard won't > produce numbers and the keys ",./" always input as "<>?" ... 2. When > the cursor pad is used (not numeric cursor pad) I get single > character 9's every once in a while when cursoring around. The > problem seems to persist more when I run programs like PWB, TurboC or > Brief. ...Any ideas? Thanks in advance. -phil Yes, this exact problem happened on my friend's computer. What was happening was that for some reason, bit 0 of the BIOS shift state byte at 0:417 was somehow getting and STAYING set. Thus, the computer thinks the right shift is permanently down. To fix it, type the following program into DEBUG: xor ax,ax mov ds,ax and byte ptr [417],f0 ret Call this program whatever you want (say FIXKEY.COM) and put it on the line following WIN in your AUTOEXEC. This is quite a weird problem, and it was quite a challenge using DEBUG to do a d 0:417 to check the shift status byte when I first saw this problem. (I had to use Alt+numeric keypad for all the numbers!) Sanjay Aiyagari (hd7x@vax5.cit.cornell.edu)