From: david sharp <dsharp AT interport DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro
Date: Tue, 16 Feb 1999 11:29:29 -0500
Lines: 20
Message-ID: <36C99CE9.73E9@interport.net>
References: <36C8F08D DOT 8C7D969A AT cats DOT ucsc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: S0CBbER/OiGTkEMSR6HSe28UydZOuD7+W8XNdYVI2XY=
X-Complaints-To: abuse AT rcn DOT com
NNTP-Posting-Date: 16 Feb 1999 16:35:11 GMT
X-Mailer:  Mozilla 3.03Gold (Win16; I)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eric Berenson wrote:
[ ... ] 
> With VBEAF installed on a fine system and graphics board, why doesn't
> this work?
> 
>   allegro_init();
>   set_color_depth(8);
>   set_gfx_mode_("VBEAF", 800, 600, 0, 0 );
[ ... ]
> IVE  BEEN STUCK FOR 2 WEEKS ON THIS.

this is a bug in Allegro.
the Allegro library should know that you
would work for two weeks on a problem with
set_gfx_mode without looking it up in
the documentation. After about one week of causing
your computer to crash consistently, shouldn't
Allegro automatically direct you to the documentation 
on the particular function causing the problem? 
i should think so.