From:	William Lachance <billl AT synapse DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Help! Allegro dies when the mouse moves
Date:	Wed, 23 Apr 1997 17:14:54 -0700
Organization:	Synapse Internet <www.synapse.net>
Lines:	30
Message-ID:	<335EA5FE.1293@synapse.net>
References:	<335DBC04 DOT 538E AT eik DOT bme DOT hu>
Reply-To:	billl AT synapse DOT net
NNTP-Posting-Host:	harp-06.synapse.net
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Dr. Andras Sólyom wrote:
> 
> I think this has been answered many times in the past, but I was not
> interested in it then... I have Allegro 2.2 I have no problem with it on
> my 100 MHz Pentium system (40Mbyte mem.20Mbytes free HDD), but on a 486
> DX2 66Mhz system (16 Mbyte memory, 50Mbyte free HDD) most of the demos
> locks up the machine after the graphics detection screen.
> The same Djgpp 2 distribution is installed  on both machine and I
> compiled the demos on the target machine (it should not make any
> difference). Can anyone tell me what could be wrong? Thanks.

The VBE/AF driver had this effect on my machine (486/66 with an
ATI Mach32). I'm not sure if this is the case with everyone else 
-- but in any event, if you want to find out, try recompiling a 
program to use the VESA_2L driver instead of GFX_AUTODETECT 
(which will use VBE/AF first if available). If it works after doing 
that, then try altering graphics.c so that it doesn't use VBE/AF 
as an autodetected driver, then recompile the entire lib. From
then on, Allegro won't use VBE/AF unless you explicitly tell it
to.

I imagine this problem will be gone in the future, once the VBE/AF
driver is more rigorously tested and debugged. That's the 
impression I got after exchanging a little bit of mail on the subject
with the author of Allegro, in any event.

Cheers,

William Lachance
billl AT synapse DOT net

- Raw text -