From: Danilo Godec <danilo.godec@agenda.si>
To: linux-msdos@vger.kernel.org
Subject: DOSEMU keyboard problem
Date: Mon, 08 Feb 2010 09:32:39 +0100 [thread overview]
Message-ID: <4B6FCC27.6050006@agenda.si> (raw)
I fixed the performance issue - there was a leftover .dosemurc in users
home directories, which included the '$_cpu_emu = "full"'.
But I now have a new problem regarding keyboard. I'm using Netterm
telnet client, because it has excelent custom keyboard and character
mapping abilities and it supports pass-through printing. I need mapping
because the application is using an old, outdated and non-standard
YUSCII encoding (check http://en.wikipedia.org/wiki/YUSCII for more info).
On new DOSEMU there is a problem - when I press one of the 'home',
'end', 'page up', 'page down' or 'insert' keys, DOSEMU seems to 'hang' -
but not completely. It still accepts CTRL-C and 'space' - but nothing
else. This only happens if I use Netterm in conjunction with new DOSEMU.
It works if I use Putty and it also works with Netterm and old DOSEMU
(where the connection settings are exactly the same).
I used 'showkey' to check what Netterm actually sends for those keys::
HOME - ^[[1~
END - ^[[4~
PAGE UP - ^[[5~
PAGE DOWN - ^[[6~
INSERT - ^[[2~
These codes are the same that Putty sends and these keys work both in
Linux (old and new server) and old DOSEMU...
I tried changing '$_layout', but that didn't change anything.
Any ideas?
Regards, Danilo
next reply other threads:[~2010-02-08 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 8:32 Danilo Godec [this message]
2010-02-08 9:40 ` DOSEMU keyboard problem Danilo Godec
2010-02-08 13:18 ` Bart Oldeman
2010-02-08 19:36 ` Danilo Godec
-- strict thread matches above, loose matches on Subject: below --
2003-02-15 6:01 dosemu " Clarence Dang
2003-02-13 11:17 ssabchew
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=4B6FCC27.6050006@agenda.si \
--to=danilo.godec@agenda.si \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox