From: Jan Willem Stumpel <jstumpel@planet.nl>
To: linux-msdos@vger.kernel.org
Subject: Keyboard weirdness
Date: Sat, 24 Jul 2004 13:03:43 +0200 [thread overview]
Message-ID: <4102420F.5050003@my.home> (raw)
In-Reply-To: <41021BCE.6030905@zgod.cjb.net>
On my new computer (on which I compiled dosemu again) the keyboard
behaves strangely in xdosemu: lots of keys do not work. E.g. qwertyuiop
becomes qwt.
The problem can be largely fixed by setting $_X_keycode = (off) -- apart
from the letter s which still does not work! The s key also does not
work in dosemu on the console.
I get the same problem with 2 different keyboards (normal and usb).
In the past (previous computer) it worked fine with the default setting.
Now the problem happens with dosemu 1.2, 1.3.0, 1.3.1 in the same way. I
don't have any other problems with Linux on this machine.
There seem to be 3 types of keys:
type 1: keys that work even with $_X_keycode = (auto) (e.g. q,w,t)
type 2: keys that only work if $_X_keycode = (off) (e.g. e,r)
type 3: the letter s.
I tried running xdosemu -Dk -O. Each time I press a key lots of
diagnostic messages appear. They are different for the 3 types of keys.
The last message is:
For type 1: HELPER: get_bios_key() returned 0000
For type 2: put_symbol: modifiers=0000 keysym=0065 [for letter e]
For type 3: put_keynum_r(break) called with invalid keynum ff:00
Outside xdosemu, with xev, the three types of keys behave exactly the same.
Regards, Jan
next prev parent reply other threads:[~2004-07-24 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 22:00 [Fwd: No upper case A or S] Ted Swart
2004-07-24 8:20 ` No upper case A or S Julius Schwartzenberg
2004-07-24 11:03 ` Jan Willem Stumpel [this message]
2004-07-24 11:30 ` Keyboard weirdness Bart Oldeman
2004-07-24 12:10 ` Jan Willem Stumpel
2004-07-24 13:03 ` Bart Oldeman
2004-07-24 18:30 ` Jan Willem Stumpel
2004-07-24 11:35 ` JLB
2004-07-29 1:00 ` No upper case A or S Julius Schwartzenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4102420F.5050003@my.home \
--to=jstumpel@planet.nl \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.