From:	rs AT redplanet DOT com DOT cy (Rotes Sapiens)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: A funny with hooking interrupts
Date:	Thu, 24 Jul 1997 12:32:50 GMT
Organization:	Customer of Connect.com.au P/L, Adelaide, Australia
Lines:	27
Message-ID:	<33d58105.2334916@192.189.54.145>
References:	<11F855EE6 AT fs2 DOT mt DOT umist DOT ac DOT uk>
NNTP-Posting-Host:	spider74.cobweb.com.au
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Thu, 17 Jul 1997 20:02:26 GMT, "Anthony.Appleyard"
<MCLSSAA2 AT fs2 DOT mt DOT umist DOT ac DOT uk> wrote:

>  I wrote a Gnu C++ program which uses the program below to hook interrupt 9
>so that it can detect all key presses and also key releases. With thanks to
>Eli Zaretski for help. It works OK on my desktop. But if run on a Toshiba
>Satellite laptop, the program runs OK, and duly calls clearreadkeys() before
>exiting, but sometimes the laptop has errors after the program has exited:-
>  (1) Sometimes on exit from the program, there is a DOS prompt, then
>something about "Bad TTR" or something like that, and a hex dump, then another
>DOS prompt. After that, the laptop <seems> to run OK.

I've seen things like this happen when 1.  the interrupt hasn't been
unhooked and uninstalled when the program exits, 2. there is some sort
of problem uninstalling the interrupt, and it triggers after the
program exits.

>  (2) Yesterday I ran the program, and exited OK; but when I then typed WIN at
>the DOS prompt, Windows started as far as the initial blue screen that says
>`WINDOWS' etc in big letters, then locked tight & I had to press ctrl-alt-del.

When something has gone wrong with the interrupts, dos programs may
run ok, but windows may crash.


Does anyone know where this !@#$%! six wheeled robot came from?

- Raw text -