Message-ID: <F77915E7F086D31197F4009027CC81C907FB8B@probe-2.as-london.acclaim.com>
From: Shawn Hargreaves <SHargreaves AT acclaimstudios DOT co DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: winallegro and install_int()
Date: Tue, 9 Nov 1999 10:55:07 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Reply-To: djgpp AT delorie DOT com

Ryan M Gumbs writes:
> i've been using the most current allegro wip (all3927) and MSVC.

Questions about Windows compilers don't really belong on a djgpp
newsgroup: it would be better to ask this on the Allegro list.

> allegro_init();
> install_timer();
> install_int(myclock, 1);
> LOCK_VARIABLE(globalclock)
> LOCK_FUNCTION(myclock)

You really ought to lock the memory _before_ you install the
interrupt, not just after! But you don't actually need to lock
memory in Windows, anyway (those functions are noops).

> my code crashed whenever it tries to install the interrupt.

Do the Allegro test programs and examples also crash? Assuming
that they are ok, I'd suggest you start with something like 
extimer.c, and try to figure out whatever you are doing 
differently to it. Or post a small but complete example source,
so we can actually compile and test your code.


	Shawn Hargreaves.