did suse change from Xfree to Xorg ?

Yes!

I've got the same issue, but I'm on a Gentoo-sys.

Changing to suse 10 real soon. Let's see if this baby works, then

Hi Qbix,

thanks for your concern and help!

Yes, as far as I understand, Suse changed:

In 9.1 the package XFree86-4.3.99.902-40 was installed.
In 9.3 it is xorg-x11-server 6.8.2-30.1 instead.
(Is there a way to check which X-server is really active?)

Happy Linux,

Arjuna2000

If your system has it, you could try xdpyinfo. It would be right near the top.
(There's quite a bit of information from that, it would be best to pipe the info to something else if your terminal can't handle that many lines. Personally I'd use something like-
xdpyinfo | less
-with the line upwards being the symbol on the keyboard being the line up with a spot missing- NOT a colon. No idea where it would be on your keyboard, or even if your keyboard has it. Failing that you could try-
xdpyinfo > xdpyinfo.txt
- then view that file however you choose)

If you don't have it, then you could check in the X logs. On my system they're at /var/log/XFree86.0.log . No idea about your distro or or what the xorg logs are called.

xdpyinfo works and shows "X.Org version: 6.8.2".

But does this mean DosBox does not yet completely work with XOrg?

Happy Linux,

Arjuna2000

dougdahl wrote:

If your system has it, you could try xdpyinfo. It would be right near the top. (There's quite a bit of information from that, it […]
Show full quote

If your system has it, you could try xdpyinfo. It would be right near the top.
(There's quite a bit of information from that, it would be best to pipe the info to something else if your terminal can't handle that many lines. Personally I'd use something like-
xdpyinfo | less
-with the line upwards being the symbol on the keyboard being the line up with a spot missing- NOT a colon. No idea where it would be on your keyboard, or even if your keyboard has it. Failing that you could try-
xdpyinfo > xdpyinfo.txt
- then view that file however you choose)

If you don't have it, then you could check in the X logs. On my system they're at /var/log/XFree86.0.log . No idea about your distro or or what the xorg logs are called.

I have found a workaround now:

the special keys do not work for German keyboard layout but they do work for US.

So the workaround is:
- in the shell set the keyboard temporarily to US: setxkbmap us
- start dosbox
- in dosbox mount a directory containing the German keyboard files (e.g. mount to drive C:) and call: c:\keyb gr (you need keyb.exe and gr.kl for that)
- now most keys work (at least the keys between "L" and "Return")
- the key left from "Z" still does not work but could be mapped to some function key (F2 ...) using the keymapper (see readme)
- after ending the dosbox session set the keyboard back to German: setxkbmap de

Happy Linux,
Arjuna2000

Use the recent CVS sources to compile dosbox, create a new
dosbox.conf and set the entry "usescancodes" to true. All keys
should work then, also the 102-key (left to Z/Y with <>).
Hope this works for you.

Are there any disadvantages to usescancodes=true? I'm just wondering why it's not on by default.

As i have only windows/linux available for testing, it's very unlikely
to work on other systems (sorta disadvantage 😉

Well, can you enable it by default on those tested platforms? #if defined(WIN32) || defined(linux)

Should be limited to Xorg systems as far as this
can be detected (otherwise there's no benefit in
using this additional translation layer), might
be changed by times.