From:	Waldemar Schultz <schultz AT ma DOT tum DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: GRX VESA driver
Date:	Mon, 15 Jan 2001 11:06:01 +0100
Organization:	[posted via] Leibniz-Rechenzentrum, Muenchen (Germany)
Lines:	20
Message-ID:	<3A62CB89.B3E420A5@ma.tum.de>
References:	<3A5F2A19 DOT 119396F1 AT ma DOT tum DOT de> <93nghs$ou1$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host:	pcritter10.mathematik.tu-muenchen.de
Mime-Version:	1.0
X-Trace:	wsc10.lrz-muenchen.de 979553169 26245 131.159.69.74 (15 Jan 2001 10:06:09 GMT)
X-Complaints-To:	news AT lrz-muenchen DOT de
NNTP-Posting-Date:	15 Jan 2001 10:06:09 GMT
X-Mailer:	Mozilla 4.73 [de]C-CCK-MCD DT (Win98; U)
X-Accept-Language:	de,en,en-US
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hans-Bernhard Broeker schrieb:
> 
> Waldemar Schultz <schultz AT ma DOT tum DOT de> wrote:
> > I experienced a 'bug ?' in GRX 2.3.2 video handling:
> 
> That's not a bug in GRX, it's a bug in your graphics card's VESA
> implementation and/or Windows driver. Sadly, this bug is so common in
> today's cards that it's easy to forget that any card's drivers indeed
> do get it right.
> 
> If GRX is to blame for anything, then for not using a workaround for
> that common bug.
most probably you are right, as I could not reproduce the behaviour om my old
home computer with W95. But I still wonder how Allegro programmers did it to get
around.

-- 
 Gruss Waldemar Schultz.
 Technische Universität München, Zentrum Mathematik M1, D 80290 München
 Tel: +49 (0)89 2892 8226        FAX: +49 (0)89 2892 8228

- Raw text -