From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug Report on RHIDE
Date: Tue, 10 Mar 1998 19:25:26 +0000
Organization: None
Message-ID: <es1E$CAmOZB1Ew00@talula.demon.co.uk>
References: <D1FB30BBA491D1118E6D006097BCAE391317DB AT Probe-nt-2a DOT Probe DOT co DOT uk>
 <6e1m4o$kni AT sjx-ixn2 DOT ix DOT netcom DOT com>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 17
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

matthew p. conte writes:
>It still happens with 3.0, Shawn.  I've had to develop lightning fast
>Ctrl-F9 reflexes just for that reason...  =)

Does the same problem happen when you run Allegro programs from
command.com? (type test.exe, press right-shift+enter to run it, release
the shift key from within the program, press Esc to quit, type something
and see if it comes out in capitals or not).

I don't know how the Rhide keyboard handler works, but if this works
correctly I suspect the solution must be to make Rhide check this BIOS
flag before and after spawning any other programs.


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
"Pigs use it for a tambourine" - Frank Zappa