From: steve_chew AT uk DOT ibm DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro and SB05_DJ2 problem
Date: 5 Mar 1997 14:26:38 GMT
Organization: IBM Austin
Lines: 17
Message-ID: <5fjvqu$1u54@ausnews.austin.ibm.com>
References: <3319eaa3 DOT 7656395 AT ursa DOT smsu DOT edu> <5feeam$1u2a AT ausnews DOT austin DOT ibm DOT com> <331add31 DOT 3781849 AT ursa DOT smsu DOT edu> <5fh0jb$1u5k AT ausnews DOT austin DOT ibm DOT com> <331c94e6 DOT 815065 AT ursa DOT smsu DOT edu>
Reply-To: steve_chew AT uk DOT ibm DOT com
NNTP-Posting-Host: steve.csnsg.uk.ibm.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In <331c94e6 DOT 815065 AT ursa DOT smsu DOT edu>, aho450s AT nic DOT smsu DOT edu (Tony O'Bryan) writes:

Well, I built Allegro 2.2 (like the 3d !) and linked the new liballeg to my program
and again, no problems. I too use blit() along with sb_mod_play() and 
sb_mix_sample(). 

I use DJGPP v2 on a P100 with an AWE32 sound card - have you produced a small
test program that demonstrates the problem ? Maybe I could try it on mine.  

>The same problem occurs with Allegro 2.11.  Through experimentation, I have
>narrowed the culprit to the blit() command.  I haven't scoured the blit() code
>to see what could possibly be causing the problem, but the problem goes away if
>I remove all references to blit().  Since the code in question uses only one
>blit() command (in a loop), it was easy to positively identify.
>