From mboxrd@z Thu Jan 1 00:00:00 1970 From: Javier Tarifa Subject: Re: Alt+o key combination misbehaving Date: Mon, 11 May 2009 10:40:50 +0200 Message-ID: <4A07E492.6030308@adbosch.es> References: <4A02EFB6.3030902@adbosch.es> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <4A02EFB6.3030902@adbosch.es> Sender: linux-msdos-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: linux-msdos@vger.kernel.org Javier Tarifa escribi=F3: > Just when I thought that I had all the keys I needed working on dosem= u=20 > I've found one that I don't know how to fix. > I use dosemu via ssh, and I thought that all alt+letter combination=20 > were working ok until yesterday, when I found out that alt+o behaves=20 > strangely. In the program > I need to use it, it simply hangs everything until I start to bash th= e=20 > keyboard franticly. > In the ScanCode Show program (get it here if you want to test it :=20 > ftp://ftp.simtel.net/pub/simtelnet/msdos/keyboard/scode22.zip) you ca= n=20 > see that the first alt+o keypress never shows, and subsequent presses= =20 > either: > 1.- Show the alt+o keypress and the new keypress normally if they're = a=20 > ctrl+something or alt+something; > 2.- Don't show the alt+o keypress neither the new keypress, but a new= ,=20 > strange one if they're a single keypress. For example, ctr+o, g show= =20 > a result of SHIFT Num 5 Strange thing I've found out: It only doesn't work well when I connect=20 throught putty, connecting throught ssh works as expected. The only difference I see in the boot.log is that when I connect=20 throught ssh, it says "CONF: dosemu running on _console", but when I=20 connect throught putty it says "CONF: dosemu running on _xterm". -- To unsubscribe from this list: send the line "unsubscribe linux-msdos" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html