Date: Sun, 5 Jan 1997 11:45:37 -0600 (CST)
From: Andrew Deren <aderen AT eecs DOT uic DOT edu>
Reply-To: Andrew Deren <aderen AT eecs DOT uic DOT edu>
To: djgpp <djgpp AT delorie DOT com>
Subject: : Allegro problem.
In-Reply-To: <9aDsRPA2ikzyEwu$@talula.demon.co.uk>
Message-ID: <Pine.SUN.3.95.970105111516.630A-100000@bert.eecs.uic.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I have a S3 card. The example programs work fine, almost always only
sometimes I get that message on them. When I do a simple program right
after compiling it works fine, but when I run it next time W95 complains
about it...Strange isn't it? Is there any oroder that initializing
functions must be called (allegro_init, set_gfx_mose, install_mouse,
install_timer, install_keyboard...)?
I figured a way around it. when the win95 starts I go straight to DOS mode
and the programs seems to work fine.  However restarting in MS-Dos mose
from Windows does not help.
Also, I compiled the program with debug info in it and when I looked at
the code using GDB there was a couple of instructions: "invalid", I do not
know much about assembler but it did not seems OK.
Is there something wrong with my Graphics card? Or what is it?
Please help. Thanks!


On Sat, 4 Jan 1997, Shawn Hargreaves wrote:

> Andrew Deren writes:
> >I just got the Allegro package, after I read so much about it. I did not
> >have any problems installing it, but when I try running programs done with
> >Allegro under Win95 DosPrompt, it kicks me back to windows with message:
> >"Your program accessed memory currently in use at 000004CC from C000:4E20"
> 
> Argh! That's in the middle of the BIOS area, which Allegro shouldn't be
> messing with, except for possibly reading parts of it during the video
> card setup. The ATI driver checks an ID string from C000:0031, and it is
> possible that the VESA drivers could read from that address, but nothing
> should be _writing_ to the BIOS area, and I can't imagine a read would
> make windows complain. What graphics card do you have?
> 
> A couple of things to try:
> 
> Run examples\ex1.exe    - simple mode 13h graphics test
> Run examples\ex5.exe    - keyboard interrupt test
> Run examples\ex6.exe    - mouse test
> Run examples\ex7.exe    - timer interrupt test
> 
> Let me know what happens, and I'll suggest some more things to try...
> 
> /*
>  *  Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
>  *  Ghoti: 'gh' as in 'enough', 'o' as in 'women', and 'ti' as in 'nation'.
>  */
>