Message-ID: <354CEDC2.35CF67EE@gmx.net>
Date: Sun, 03 May 1998 22:20:50 +0000
From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization: none provided
MIME-Version: 1.0
To: Vik DOT Heyndrickx AT rug DOT ac DOT be
CC: djgpp-workers AT delorie DOT com
Subject: Re: compatibility issues with BIOS functions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 27 Apr 1998 Vik Heyndrickx wrote:

> Some user reported keyboard problems with RHIDE. It wouldn't read the
> keyboard properly and RHIDE showed truly erratic behaviour. After
> removing the KBDBUF.SYS driver from config.sys everything works as it
> would with most of us.
> I haven't really searched why this fails with RHIDE, but I have a good
> idea. 
> I think RHIDE is peeking into BIOS area to see whether a keystroke is
> available and read it afterwards using the BIOS function of interrupt
> 0x16. That is potentially dangerous since device drivers can alter the
> functioning of the BIOS.

Exactly because of this known problem, RHIDE has a commandline
switch named -K to use the BIOS calls instead of using direct
accessing the BIOS area.

Run

rhide -h

to get a list of available options for RHIDE.

Robert
-- 
******************************************************
* email:   Robert Hoehne <robert DOT hoehne AT gmx DOT net>     *
* Post:    Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW:     http://www.tu-chemnitz.de/~sho/rho        *
******************************************************