🚀 go-pugleaf

benrg@ocf.berkeley.edu (Ben Rudiak-Gould) writes:

>First of all, the file DOCS\VERSION in my DJGPP distribution says,
>"This distribution of DOS 386/G++ is version 1.05".  Does yours
>really say, "2.2.2", or are you talking about the version number of
>something else?  If the former, where did you get that version?

djgpp 1.08 is derived from gcc 2.2.2

>In article <25586@castle.ed.ac.uk> eonu24@castle.ed.ac.uk (I Reid) writes:

>>Question 2: Trident 8900 driver problems.
>>

>I ran into this problem as well, and solved it.  The drivers have only
>two routines--one to set a graphics mode and one to do a bank-switch.
>A little bit of experimentation revealed that the bank-switch routine
>was the one causing the problem.  I noticed that the source code had a
>notice saying it was derived from VGAKIT 3.4.  I have 4.1 and it works
>fine.  So, I changed the bank-switch code in tridnt89.asm to conform
>to the new VGAKIT code, and now it works fine as well.

The trident driver in Csaba's excellent LIBGRX contrib package contains
a similiar patch... I haven't checked if its identical.

Also, I noticed that bank switching fails right after you do a printf
to a graphics mode.. the next few graphics writes ALWAYS end up in the
first bank. I haven't gotten around to reproducing this in small code, so
I don't know if its a go32 problem or a board problem. My first guess
would be to blame the board. We all know that Trident == Bug_ridden_lazy_DOG!

In any case, at least when my app spews error messages to stdout I know where
in the picture the problem is, since it ends up in the top part of the
screen - MUST be a feature :-)

In addition, I've been having problems with the 1024x768 mode too. Nobody
but me has seen them (btw. I have a 8900B). Oh lord / won't ya buy me / a
local bus s3...



-- 
nyet@cco.caltech.edu
nyet@aerospace.aero.org