Bug#389878: dosemu: Some keys are wrong under X

[Bart Oldeman]

The changes at the below URL may help; although they are in SVN I
think that code hasn't changed much recently so they can apply to
1.2.2 without too much trouble.

http://dosemu.svn.sourceforge.net/viewvc/dosemu?view=rev&revision=1604

Bart


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389878: dosemu: Some keys are wrong under X

[Andreas Ferber]

Good news, everyone,

this is related to bug #394318 (xserver-xorg-core: XkbGetKeyboard() is
broken), which prevents dosemu from using the Xkb keyboard map to
configure its keyboard mapping and forcing it to fall back to the
non-Xkb way of doing things.

However, this should not lead to failure of the keyboard mapping, so
dosemu itself seems to have some bug in the non-Xkb keyboard mapping
code. Unfortunately, I don't know enough about the X API to provide
any more insight into this.

Interestingly, there seems to be some difference between the testing
(1.2.2-5) and experimental (1.3.3-1) versions. The testing version
wrongly maps the "3"-key as "u" for me, whereas the experimental
version gets this particular key right. Other keys however are the
same in both versions.

Andreas
-- 
Andreas Ferber  | MarcanT Internet-Services GmbH
| Ravensberger Str. 10G
| D-33602 Bielefeld
[EMAIL PROTECTED] | 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389878: dosemu: Some keys are wrong under X

[Sven Joachim]

Hello,

I'm facing the same problem with a locally compiled dosemu 1.3.3.
IIRC it started after upgrading to X.Org 7.1, before that dosemu had
worked fine.  The keyboard layout in ~/.dosemurc does not matter.

Would it be of help if I post my xorg.conf?

Regards,

Sven



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389878: dosemu: Some keys are wrong under X

[Milan Kocián]

hello,

I found one interesting item. I use gnome keyboard switcher (Keyboard
Indicator 2.14.3). When I had defined two layouts in KI (and probably
more), keyboard in dosemu is bad. But when I leave only one layout in
KI, keyboard in dosemu is ok.

I hope, this may help.

Regards,

-- 
Milan Kocián <[EMAIL PROTECTED]>

Bug#389878: dosemu: Some keys are wrong under X

[Milan Kocián]

hello,

I can confirm this bug on my PC.

Why can help purge/install of dosemu packages?

- latest unstable
- kernel 2.6.18

Shall I send any log? 

Regards,

Milan Kocian



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389878: dosemu: Some keys are wrong under X

[Piotr Sulecki]

Package: dosemu
Version: 1.2.2-5
Severity: important


Two keys are mapped to other keys while working under X. Namely, 'r' is
mapped to 't' and 'i' is mapped to '.'. This makes the letters completely
unusable inside xdosemu.

The culprit may be in the keycode->keynum mapping. The relevant part of
'debug +X' is:

X: focus in
X: KeymapNotify event
X: CapsLockMask = 0x2
X: CapsLockKeycode = 0x42
X: NumLockMask = 0x10
X: NumLockKeycode = 0x4d
X: ScrollLockMask = 0x0
X: ScrollLockKeycode = 0x4e
X: AltMask = 0x8
X: AltGrMask = 0x80
X: InsLockMask = 0x0
X: No keyboard Description!
mapping keycode:9  -> keynum: 0x01
mapping keycode:10  -> keynum: 0x02
mapping keycode:11  -> keynum: 0x03
mapping keycode:12  -> keynum: 0x04
mapping keycode:13  -> keynum: 0x05
mapping keycode:14  -> keynum: 0x06
mapping keycode:15  -> keynum: 0x07
mapping keycode:16  -> keynum: 0x08
mapping keycode:17  -> keynum: 0x09
mapping keycode:18  -> keynum: 0x0a
mapping keycode:19  -> keynum: 0x0b
mapping keycode:20  -> keynum: 0x0c
mapping keycode:21  -> keynum: 0x0d
mapping keycode:22  -> keynum: 0x0e
mapping keycode:23  -> keynum: 0x0f
mapping keycode:24  -> keynum: 0x10
mapping keycode:25  -> keynum: 0x11
mapping keycode:26  -> keynum: 0x12
mapping keycode:27  -> keynum: 0x14
mapping keycode:28  -> keynum: 0x14
mapping keycode:29  -> keynum: 0x15
mapping keycode:30  -> keynum: 0x16
mapping keycode:31  -> keynum: 0x34
.
. [cut out some lines]
.
mapping keycode:60  -> keynum: 0x34

Check the lines with keycodes 27:28 and 31:60; you'll see they are
translated to the same keynum.

How can I fix this mapping? It broke not more than a month ago.

Regards,

Piotr Sulecki.

-- Package-specific info:
##
# This file is the system-wide dosemu.conf or the per-user ~/.dosemurc,
# included by global.conf or dosemu.bin.
#
# ./doc/README.txt (chapter 2.) contains a description of the syntax
# and the usage of dosemu.conf and .dosemurc.
#
# The commented-out values are defaults, here for documentation purposes
# only. Options marked [priv] cannot be changed in ~/.dosemurc.
#
# (optional) access rights are defined in
#
#  /etc/dosemu/dosemu.users or /etc/dosemu.users
#
##



# Notes for editing this file:
#
#   In$_xxx = (n)n is a numerical or boolean value
#  = =
#   In$_zzz = "s"s is a string
#
# Please note that all options are commented out by default!
# Remove the # in front of the $ to change an option.


##
## CPU settings: define the CPU features to DOSEMU.

# CPU shown to DOS, valid values:  "80[345]86"
# or "emulated" for non-native CPU (386 in this case) Default: 80386

$_cpu = "80486"

# if possible use Pentium cycle counter. Default: off

# $_rdtsc = (off)

# CPU speed, used in conjunction with the TSC
# Default 0 = calibrated by dosemu, else given (e.g.166.666)

# $_cpuspeed = (0)

# emulated FPU, (off) or (on), default = (on)

# $_mathco = (on)

# 0 = all CPU power to DOSEMU; default = 1 = nicest, then higher:more CPU power

# $_hogthreshold = (1)

##
## Disk and file system settings

# List of hdimages or boot directories under 
# ~/.dosemu, the system config directory (/etc/dosemu by default), or
# syshdimagedir (/var/lib/dosemu by default) assigned in this order
# such as "hdimage_c directory_d hdimage_e"
# Absolute pathnames are also allowed.
# If the name begins with '/dev/', then partion access is done instead of
# virtual hdimage such as "/dev/hda1" or "/dev/hda1:ro" for readonly
# Currently mounted devices and swap are refused. Hdimages and devices may
# be mixed such as "hdimage_c /dev/hda1 /dev/hda3:ro"
# Note: 'wholedisk' is _not_ supported. Default: "drives/*"

$_hdimage = "freedos:ro freedos.img incoming /cdrom"

# if you want to boot from a virtual floppy:
# file name of the floppy image under DOSEMU_LIB_DIR
# e.g. "floppyimage" disables $_hdimage
#  "floppyimage +hd" does _not_ disable $_hdimage. Default: ""

# $_vbootfloppy = ""

# floppy drive types: "threeinch" or "fiveinch" or "atapi" or empty,
# if non-existant. Optionally the device may be appended such as
# "threeinch:/dev/fd0". Default: "threeinch" for A:, "" for B:

# $_floppy_a = "threeinch"
# $_floppy_b = ""

# list of generic SCSI devices to make available for the builtin aspi driver
# (format of an entry is 'device:type:mappedtarget' such as
# "sg2:WORM sg3:Sequential-Access:6 sg4:CD-ROM" or
# "sg2:4 sg3:1:6 sg4:5" (which are equal). Default: ""

# $_aspi = ""

# whether to lock the full file on lredired drives for file locking requests
# or just one byte

# $_full_file_locks = (off)

# config.sys   -> config.XXX; default="" or 3 char.,

# $_emusys = ""

# system.ini   -> system.XXX; default="" or 3 char., (for Windows 3.