From:	mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: wierd problem in Allegro 3.0
Date:	Wed, 15 Apr 1998 22:22:59 GMT
Organization:	[posted via] Easynet UK
Lines:	29
Message-ID:	<353515fd.9237060@news.easynet.co.uk>
References:	<353362C2 DOT 5556 AT cc DOT umanitoba DOT ca> <01bd6876$1b9633a0$3df706c3 AT mbizon DOT nordnet DOT fr>
NNTP-Posting-Host:	foot.easynet.co.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On 15 Apr 1998 12:57:56 GMT, "Maxime" <mbizon AT nordnet DOT fr> wrote:

>I've got the same problem with Allegro 3.0. According to the debugger, the
>problem comes from the set_gfx_mode function.
>Please help us.

If you make a compilable program to demonstrate the problem, other
people reading your message will be able to see what you are doing and
(hopefully) show you what you are doing wrong.  Try to make the
example as short as possible, while still being compilable.  Don't
post code that won't compile (unless that is what the problem is).

The first thing you should do is see whether or not the `ex1' example
program runs.  This program should set a 320x200 8-bit colour mode,
print a message, and wait for a keypress.  You should find it in the
`examples' subdirectory of Allegro, and it should already have been
compiled for you by Allegro's build process.

If this program fails, something is very wrong -- let us know.  If
this program works properly then you're doing something wrong in your
source code -- show us some source code so that we can see what you're
doing wrong.

Without seeing your source, I'd guess that you forgot to call
`allegro_init' before `set_gfx_mode'.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

- Raw text -