From: diegodc AT arrakis DOT es (diego)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Graphic debuging problem
Date: Sat, 22 Nov 1997 13:50:25 GMT
Organization: NetSat Inc.
Lines: 72
Message-ID: <3476e319.0@news.arrakis.es>
References: <m0xVyJn-000S1kC AT inti DOT gov DOT ar>
NNTP-Posting-Host: caladan.arrakis.es
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

	Hello again, and thanks to Salvador Eduardo Tropea for answering me.

	I have tried what SET said but it did NOT work. Even more, I have
realized that RHIDE also gets confused in PLAIN TEXT MODE! (I think
I'm gonna cry....). [Snip] 

	Sometimes when I do a SIMPLE printf it shows results in the middle of
the source I'm debugging, so have to keypress ALT+F5 twice to get it
ok again (of course that nothing is on the user screen).

	Anyway,  I answer what SET asked me to see if it helps to solve at
least one of the two problems! Thank to you all (but specially to
SET).

"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar> wrote:


>> 1)	First of all, I must tell you that I am programing (if almost
>> ramdom keypading around can be called "to program") in C whith RHIDE
>> v1.4. 
>> 	As I am having bugs in a graphic program module (who doesn't, uh?),
>> I'm trying to debug it. 
>> 	So when run until cursor it changes to the user grphic screen. No
>> problem so far, but as I try to go on tracing I have to keystroke
>> alt+F5 (to changeback to the ide)
>> 	and it shows a user text mode screen (the MSDOS one). Pressing alt+F5
>> again returns to the RHIDE window and can go on tracing, but when
>> pressed alt+F5 again it will NO longer show the graphic mode user
>> screen, but the text mode user screen instead.
>> 	(How is it supossed to debug a graphic module whitohut seeing what it
>> does?!! Maybe it's a useful exercise to improve abstract thinking,
>> uh?)
>> 	Anyway, if you knew why it happens, or knew how to solve it, please do
>> tell me about. 
>1) Try calling RHIDE with -G 1
	I did but it didn't work (neither -G 2, -G 3, ..., by the way, where
on earth did you find what option -G # means?)

>2) Do you have a VESA card?
	Yes,  a S3 trio V64+ (VESA 1.0), but also tried a software dirver to
simulate VESA 2.0 extensions.

>3) Are you setting the mode using BIOS?
	I'm afraid I do NOT know at all, but if you mean if I called RHIDE
whith -b option, I have just tried (and it still does not work).

>4) Can you install an Hercules monitor/card to yourr PC?
	No.

> 
>> 2)	The thing is that if I try *ANY* SVGA graphic mode under a
>> WINDOWS 95's MSDOS window (even in whole screen mode) the system gets
>> hanged up (you know, a only-cold-reboot-solution crash).
>> 	It all happens just as I initgraph() with a SVGA mode (just like a
>> *simple* 640x480x256colors). I know the .exe is ok because it DOES
>> work in PLAIN MSDOS.
>1) Other applications can do it in your system?
	Yes, even the 1024x768x256.

>2) Do you have the original drivers of your card installed? (The ones with W95 
>aren't so good, the ones in Direct X can fail, M$ warns about it).
	Yes, but there is no *.grd in them.

>3) How did you configured GRX? (board, etc).
	No, just did make and used it. Is there any other configuration? I
have found many *.GRD drivers in the djgpp\drivers\ directory, but
NONE OF THEM was a S3 or a VESA driver.



==> Diego Dominguez <==	diegodc AT arrakis DOT es