From: Stefan Ring <stefanrin@gmail.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0 of 1] Fix for DOS keyboard problems
Date: Mon, 24 Aug 2009 10:44:19 +0200 [thread overview]
Message-ID: <53e878390908240144v4c99fb89i7ac204356128d38f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0908241218190.2200@linmac.oyster.ru>
2009/8/24 malc <av1474@comtv.ru>:
> There's other DOS application that exhibits erroneous keyboard
> beahviour and i was curious whether your hack "fixes" it too (alas
> it doesn't) - Command and Conquer, the demo can be found at:
>
> http://www.dosgamesarchive.com/download/command-and-conquer/
>
> Keyboard is dysfunctional in both the setup and the game. What i'm
> wondering now if this is a indeed pckbd or BIOS problem, but Bochs
> where the former can be verified refuses to work on my machines,
> perhaps someone could give it a try and report here?
I will try to run C&C in Bochs, and I'm definitely not surprised that
my hack doesn't fix that as I'm almost 100% certain that it does its
own keyboard processing and bypasses the BIOS entirely (as virtually
all games do).
next prev parent reply other threads:[~2009-08-24 8:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 10:54 [Qemu-devel] [PATCH 0 of 1] Fix for DOS keyboard problems Stefan Ring
2009-08-23 10:54 ` [Qemu-devel] [PATCH 1 " Stefan Ring
2009-08-23 12:44 ` [Qemu-devel] [PATCH 0 " Jamie Lokier
2009-08-23 17:20 ` Stefan Ring
2009-08-23 21:55 ` Jamie Lokier
2009-08-23 22:54 ` Stefan Ring
2009-08-24 7:50 ` Hans de Bruin
2009-08-24 9:24 ` Jamie Lokier
2009-08-24 9:41 ` Hans de Bruin
2009-08-24 8:21 ` malc
2009-08-24 8:44 ` Stefan Ring [this message]
2009-08-24 8:49 ` malc
2009-08-24 9:22 ` Jamie Lokier
2009-08-24 9:27 ` Stefan Ring
2009-08-24 9:31 ` Stefan Ring
2009-08-24 15:11 ` Stefan Ring
2009-08-24 15:34 ` malc
2009-08-24 15:38 ` Stefan Ring
2009-08-24 15:40 ` malc
2009-08-25 14:50 ` malc
2009-08-24 13:03 ` Stefan Ring
2009-08-24 13:07 ` Stefan Ring
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=53e878390908240144v4c99fb89i7ac204356128d38f@mail.gmail.com \
--to=stefanrin@gmail.com \
--cc=av1474@comtv.ru \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).