[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: Keyboard mystery
- Subject: Re: Keyboard mystery
- From: J R FOX jr_fox@xxxxxxxxxx
- Date: Sun, 23 Dec 2018 00:56:33 +0000 (UTC)
Hardware would have been my first thought. One of the three Unicomp keyboards I ordered was defective
out of the box, and had to be returned for repair or replacement. Certain keypresses either did nothing, or
"machine-gunned" that letter -- though intermittently. If _that_ can happen, why not a return of the wrong
scan code ? But since you were dealing with more than one set of hardware, that is essentially ruled out.
Jordan
--------------------------------------------
On Sat, 12/22/18, wrote:
Subject: Re: Keyboard mystery
To: xywrite@xxxxxxxxxxxxx
Date: Saturday, December 22, 2018, 3:39 PM
Reply to note from cld@xxxxxxxxxx
Sat, 22 Dec 2018 18:15:12 -0500
Another data point:
The problem occurs when I load KBD
files other than my customary one,
e.g., the factory-issued XY4.KBD and
XY4-3.KBD files. This decisively
rules out the KBD file, I think. And
it's not U2, because the same
thing happens even if I don't load U2.
It's not hardware, because the
hardware hasn't changed on either of my
machines. vDosPlus hasn't
changed in quite a while, more's the
pity. Could it be a Windows
update? No change in Windows keyboard
behavior, so that doesn't seem
likely.
Curiouser and curiouser....
--
Carl Distefano
cld@xxxxxxxxxx