X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	"Alexei A. Frounze" <alexfru AT chat DOT ru>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: RHIDE fix
Date:	Wed, 9 Jan 2002 00:08:01 +0300
Lines:	47
Message-ID:	<a1gnfo$qf15s$4@ID-57378.news.dfncis.de>
References:	<a1cvgu$ppagh$1 AT ID-57378 DOT news DOT dfncis DOT de> <3C3AF0B8 DOT 8CF1C2D9 AT inti DOT gov DOT ar>
NNTP-Posting-Host:	ppp140-48.dialup.mtu-net.ru (62.118.140.48)
X-Trace:	fu-berlin.de 1010557241 27755708 62.118.140.48 (16 [57378])
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2615.200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2615.200
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

salvador <salvador AT inti DOT gov DOT ar> wrote in message
news:3C3AF0B8 DOT 8CF1C2D9 AT inti DOT gov DOT ar...
> "Alexei A. Frounze" wrote:
>
> > I recall RHIDE messed up the screen or made it black due to buggy
> > implementation of some VGA BIOS functions (namely 0x1c00, 0x1C01,
0x1C02).
> > I've made a fix for that, which appears to work (at least here, it cures
the
> > problem for the text mode).
> >
> > If anybody is interested, I may release it and make available from my
site.
>
> What exactly is this fix? Are you implementing the functions or replacing
them
> by a "do nothing"?

exactly by replacing by dummy ones, which simply XOR AL, AL so that AL is
never 0x1C upon IRET -- this is the way to:
1st don't give any chance to the buggy routines
2nd disable the functions in a legal way (when supported, they should return
AL=0x1C)
Of course, this doesn't
1st fix anything in RHIDE because it's not resposible for gfx card problems
2nd fix those buggy functions
But this allows me to use RHIDE just about as easily as I used to use IDE in
Turbo Pascal and Turbo C/C++: Alt+F5 works, Alt+X doesn't blacken the screen
forever either. So, obviously an improvement.
I don't know who's the current maintainer of RHIDE (you or Andris), but in
my opinion, there should have been a special command-line option to disable
use of these functions. For me to fix this damn problem it did cost of:
writing a TSR, which logged all Int0x10 calls and saved to a file -- the 1st
program. Finding the buggy function -- the 2nd, test program, writing yet
another TSR to intercept calls to buggy functions -- the 3rd program. But I
was not heard a year ago, when I had this problem on my other computer and
having it now on my current. So I took over. :)

Good Luck
--
Alexei A. Frounze
http://alexfru.chat.ru
http://alexfru.narod.ru
http://welcome.to/pmode/

- Raw text -