Date: Thu, 05 Oct 2000 23:18:55 +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: <9003-Thu05Oct2000231854+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: <8rhi12$4up$10$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>
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: Thu, 5 Oct 2000 11:35:34 +0200
> >
> > Are you sure the program indeed locks up?
> 
> Yes, I'm sure. The counters on the screen don't count up
> anymore, which means the interrupt handler doesn't get called
> anymore. Also, the keytest function doesn't print any codes,
> and Ctrl-Break, which normally brings me back to rhide, doesn't
> work either.
> 
> > What happens if you press another key after one of the above keys?
> 
> Nothing. I don't even get an interrupt for the break-code of the
> shift key. The make-code is the last thing that happens.

How about locking everything that the interrupt handler touches?  Did
you do that?  The code you posted doesn't show.

> If I process every key in my ISR myself, and stuff the raw scancodes
> into the BIOS keyboard buffer, my keytest() really gets the raw
> codes, and ALL keys, including shift and num-lock etc. DO work.

Did you try to disable the keyboard hooking in the DJGPP startup code?
If so, did it change anything?