Date: Sun, 08 Oct 2000 15:12:10 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Peter Remmers" <Peter DOT Remmers AT t-online DOT de>
Message-Id: <8296-Sun08Oct2000151209+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h
CC: djgpp AT delorie DOT com
In-reply-to: <8rporf$r6s$15$1@news.t-online.com> (Peter.Remmers@t-online.de)
Subject: Re: strange interrupt chaining problem with keyboard interrupt
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1001005075606 DOT 3958E-100000 AT is> <8rhi12$4up$10$1 AT news DOT t-online DOT com> <9003-Thu05Oct2000231854+0300-eliz AT is DOT elta DOT co DOT il> <8rj5td$l0o$14$1 AT news DOT t-online DOT com> <7458-Fri06Oct2000114142+0300-eliz AT is DOT elta DOT co DOT il> <8rliej$ecd$14$1 AT news DOT t-online DOT com> <2110-Sun08Oct2000073544+0300-eliz AT is DOT elta DOT co DOT il> <8rp9h0$j9f$15$1 AT news DOT t-online DOT com> <2561-Sun08Oct2000122936+0300-eliz AT is DOT elta DOT co DOT il> <8rporf$r6s$15$1 AT news DOT t-online DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Peter Remmers" <Peter DOT Remmers AT t-online DOT de>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sun, 8 Oct 2000 14:21:15 +0200
> 
> "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> schrieb...
> 
> > If keyb.com is the culprit, it is clear why Shift keys are treated
> > differently (I'd expect the right Alt key to be special as well): they
> > produce special keys and switch the keyboard between the ASCII and
> > your localized input mode.
> 
> Why are the shift keys treated differently?
> Yes, they produce characters that are different from the default US
> keyboard layout (in combination with the other keys. But so do the
> right Alt key

That's why I said that I'd expect the right Alt key to also behave
like the Shift keys.  I don't claim I understand everything in this
riddle (I do know that I now have one more reason for hating KEYB.COM,
though ;-).

> It seems, we are not much further than at the beginning...

How so?  We have learned that KEYB.COM somehow causes this
problem--that's quite an achievement, IMHO.  If you can afford
uninstalling KEYB.COM, yoiu already have a solution.

If uninstalling KEYB.COM is not an option, I'd first try to find out
whether the mere fact that you "lcall" the old handler causes the
problem, and whether the system is wedged before or after lcall
returns.  It might be a good idea to write a short test program which
tests these aspect without hooking the keyboard interrupt: all you
need is to get the address of the old handler.