Message-ID: <8D53104ECD0CD211AF4000A0C9D60AE3BDE2EF@probe-2.acclaim-euro.net>
From: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: Allegro - why doesnt this work??
Date: Fri, 26 Mar 1999 11:54:39 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain
Reply-To: djgpp AT delorie DOT com

Christopher Nelson writes:
> On my system, this causes problems because the driver
> in DD doesn't work right. Try to explicity set it to 
> GFX_VGA. That ought to do it.

Hardcoding a particular driver name into your executable is not a 
very good idea. That may work around a particular problem on your
machine, but it is also a good way to make sure your program won't 
work correctly for anyone else, who might have different hardware to
you and thus need different drivers.

If the autodetect isn't working properly, the best thing to do would
be to investigate and find out why. If there is a bug in Allegro, try
to locate exactly what is going wrong so it can be fixed. If the
problem is with your system setup, try to remove whatever driver is
causing the problem, eg. to disable those modes in Display Doctor,
or contact SciTech and get them to fix the problem if it turns out
to be their error.

If you don't have the time or inclination to fix it properly, use the
config file to specify what drivers you want to use on your machine
(see Allegro docs for details). This sort of thing belongs in a
per-machine config file, not the sources for a program that may be
run on more than one machine.


	Shawn Hargreaves.