Message-Id: <m0zx9R2-000S79C@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: "Fran ois Poirier" <fpoirier AT aei DOT ca>
Date: Mon, 4 Jan 1999 09:52:18 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Subject: Re: RHIDE BUG
CC: djgpp AT delorie DOT com
In-reply-to: <368C0B07.46F9F473@aei.ca>
X-mailer: Pegasus Mail for Windows (v2.54)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-printable to 8bit by delorie.com id HAA12200
Reply-To: djgpp AT delorie DOT com

"François Poirier" <fpoirier AT aei DOT ca> wrote:

> I finally fix my bug.
> It was my Matrox Millenium BIOS ver 2.4 that has a bug.
> I upgraded it to version 3.0 and now its fine.(Its a programmabled bios
> and we can d/l upgrade to their site).
> I read that their was also a font that was misplaced on the card BIOS
> and could  have cause problem with the new VESA extension 3.0.
> (They totaly remove this font I think it was a 8x12 font).

Isn't the first time that people having problems with RHIDE solves it 
upgrading BIOS or W95 drivers. 

> But still I know someone who as the same problem
> with some trident cards. 

I have a Trident 9440 and no problems, I think is something in the setup of 
that machine. Robert started developing RHIDE using a Trident 9440 too.

> It will be interresting to understand
> the real nature of the bug. See Ya.

Sure, but I know about *a lot* of buggy configurations and I think the 
problem is different in each case. I think the most common problems are lated 
to:

1) Wrong implementation of the VESA BIOS "save/get state" service. This 
service isn't used by games and common applications and hence is very poorly 
tested. 
2) Wrong VGA virtualization in the W9x drivers. They intercept all the I/O 
and emulates a lot of stuff, is very common to see errors.

SET

> Salvador Eduardo Tropea (SET) wrote:
> 
> > "François Poirier" <fpoirier AT aei DOT ca> wrote:
> >
> > > I have a strange bug with RHIDE 1.4
> > > I use WIN95 OSR2 with 32 megs of ram
> > > Problem: I cant exit RHIDE or dosshell
> > > the screen is black and I have to switch back
> > > to windows and then to DOS to "unfreeze" it.
> > > My gcc compiler is 2.8.1 and work fine in the command line.
> > > An answer would be appreciated.
> >
> > Most probably a bug in your W$ drivers.
> > Run RHIDE from a batch file containing:
> >
> > >>>>>
> > rhide
> > mode co80
> > <<<<<
> >
> > It should work.
> >
> > 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
> 
> 
> 
> 
> 
------------------------------------ 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