From: Damian Yerrick Newsgroups: comp.os.msdos.djgpp Subject: Re: GRX VESA driver Organization: Pin Eight Software http://pineight.8m.com/ Message-ID: References: <3A5F2A19 DOT 119396F1 AT ma DOT tum DOT de> <93nghs$ou1$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <3A62CB89 DOT B3E420A5 AT ma DOT tum DOT de> X-Newsreader: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 20 X-Trace: /Kkf2K5YlkAl4KuJP6Zd0O8d2OW0rX3sQwlYTpc0/D8X2KYS9xMRFqEbXqlEic6HDih7LELrNh1j!K98TfCQlXwDdA82l4hyTAr+unl4XWXqs2PeRCMdSdkJdSmytnKWWQJjO/A0VtRaM5cL8/oEsZ90o!ON4WiA== X-Complaints-To: abuse AT gte DOT net X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly NNTP-Posting-Date: Wed, 17 Jan 2001 04:17:29 GMT Distribution: world Date: Wed, 17 Jan 2001 04:17:32 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com On Mon, 15 Jan 2001 11:06:01 +0100, Waldemar Schultz wrote: >Hans-Bernhard Broeker schrieb: >> >> 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. Surprisingly, the workaround is palette animation. If I were to encounter such a problem in my Allegro applications, I'd just set_palette() once a second. (I don't use GRX; consult the GRX docs for an equivalent function.)