From:	Ryan Shaw <kathleen AT iafrica DOT com DOT na>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: RHIDE keyboard problem
Date:	Fri, 01 May 1998 00:30:38 +0200
Organization:	UUNET Internet Africa
Lines:	35
Message-ID:	<3548FB8E.4EA7E63E@iname.com>
References:	<m0yToks-000S3EC AT inti DOT gov DOT ar>
NNTP-Posting-Host:	dup11-wvb.iafrica.com.na
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Salvador Eduardo Tropea (SET) wrote:

> Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be> wrote:
>
> > Robert Hoehne wrote:
> > > RHIDE does _NOT_ hook any interrupt, so it can't be, that some
> > > interrupt isn't unhooked by RHIDE.
> >
> > Doesn't RHIDE use Allegro code to hook the keyboard interrupt. I thought
> > it did!
>
> No. RHIDE never used it. My editor used it but Robert asked to avoid it because
> it could produce problems. Currently all is using calls to BIOS or reading the
> BIOS Data Area.
>
> SET
> ------------------------------------ 0 --------------------------------
> Visit my home page: http://set-soft.home.ml.org/
> or
> http://www.geocities.com/SiliconValley/Vista/6552/
> Salvador Eduardo Tropea (SET). (Electronics Engineer)
> Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
> ICQ: 2951574
> Address: Curapaligue 2124, Caseros, 3 de Febrero
> Buenos Aires, (1678), ARGENTINA
> TE: +(541) 759 0013

  Although I haven't seen the original message posted, I've also encountered an
ocassional problem with the keyboard in programs using Allegro (if that was the
program).  I found that pressing CTRL would return RHIDE to normal usage... If
nobody has noticed this solution I suppose the solution to the problem would be
somewhere within the keyflags of RHIDE upon returning after executing a program?

- Raw text -