From:	milton DOT moura AT mail DOT telepac DOT pt-nospam (Milton Moura)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: allegro 3 crashes win95
Date:	Tue, 23 Dec 1997 01:51:56 GMT
Lines:	37
Message-ID:	<349f1934.79476@news.telepac.pt>
References:	<349d7955 DOT 1413968 AT news DOT telepac DOT pt> <67kr85$ric AT bgtnsc03 DOT worldnet DOT att DOT net>
Reply-To:	milton DOT moura AT mail DOT telepac DOT pt-nospam
NNTP-Posting-Host:	194.65.243.148
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On 22 Dec 1997 04:44:53 GMT, "Steve Patton" <leaphe AT pemail DOT net> wrote:

>I have Win95, and I haven't run into any problems.  There's a few points I
>might suggest for you to try out.  Try making a simple program, that linkes
>liballeg.a to your  code.  And in the code, just do allegro_init(), and
>exit.  If it works, then it's something else, such as you do not have the
>proper hardware, or if you're running the install_timer(), and your DOS
>window does not allow programs to detect Win95, then that might do
>something.  But if allegro_init() crashes your computer, you either have a
>corrupt copy of liballeg.a, delete, and recompile everything, or it's not
>Allegro and somethign completely different.

thanks for your help, but i found it to be none of the above.
the problem is in the set_gfx_mode() function. 

I was calling it like this:

set_gfx_mode(GFX_AUTODETECT,640,480,0,0);

and it ran fine in DOS, but crashed under win95. 
I tried changing the GFX_AUTODETECT to GFX_VESA1, GFX_VESA2B etc...
and even to GFX_S3 which is my card's driver and it still crashed. 
(I have a s3 trio64v+, 1mb)

I could only make it run by setting the resolution to 320x200, no
matter wich driver I used.

so, is this an allegro problem or is it win95 that is fu**ing up?
doesnt seem to be a hardware problem cuz all video modes run fine
under pure DOS.

thanks.

-
extacy^garbage
www.catalao.pt/coders/garbage
milton DOT moura AT mail DOT telepac DOT pt

- Raw text -