From:	Brian Sturk <bsturk AT nh DOT ultranet DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Allegro, spawnl, and PMODE/DJ...problems...Still,even w/3.0??
Date:	Wed, 04 Mar 1998 21:59:07 -0500
Organization:	Contractor
Lines:	59
Message-ID:	<34FE14FB.7E6809C4@nh.ultranet.com>
References:	<34FCD658 DOT 666D2596 AT nh DOT ultranet DOT com>
	<Pine DOT SUN DOT 3 DOT 91 DOT 980304104033 DOT 6541O-100000 AT is> <DPizHDAATa$0EwRP AT talula DOT demon DOT co DOT uk> <34FDF880 DOT 8577D87B AT nh DOT ultranet DOT com>
NNTP-Posting-Host:	d9.dial-10.exr.nh.ultra.net
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Well I tried 3.0 and it didn't help any.  My guess at first was that it's not
necessarily a problem with Allegro.  I got the same behavior for spawning a program
(that uses PMODE/W for those who haven't been following the thread) with 3.0 as with
2.2.  When I didn't call allegro_exit() the program wasn't spawned at all.  When I
did call allegro_exit() before spawning the program it spawned OK but gave the error
I gave in my previous message upon returning.  The thread I had been following a
while ago had similar behavior when trying to spawn an app that used PMODE/W.  The
rememdy mentioned in the thread was to use PMODE/DJ instead of CWSDPMI.  It still
isn't working for me.  As I had mentioned in a previous message I wrote a small
couple line program that spawned the program and it worked and returned fine.  I'm
not sure where to go from here.
Brian Sturk wrote:

> Thanks...I had been using 2.2. I think the keyboard interrupt wasn't getting
> remapped/released according to a thread I followed in this newsgroup a while ago
> (if my memory serves me right). I'll try upgrading to 3.0.  I appreciate your
> time!
>
> Shawn Hargreaves wrote:
>
> > Eli Zaretskii writes:
> > >Can any Allegro guru help here?  I don't know enough about Allegro to
> > >understand the implication of spawning a child program and calling
> > >`allegro_exit' before that.
> >
> > I think that should be ok. The allegro_exit() routine will restore the
> > original hardware state and unhook all IRQ's, so it should then be safe
> > to spawn other programs (this was very buggy prior to Allegro 3.0,
> > though, so it is important to use that and not v2.2).
> >
> > In fact it also seems ok to spawn programs without removing Allegro
> > first as well, as in the case of the ex33 program that shells to a
> > command prompt while leaving a MIDI file playing in the timer handler.
> >
> > I don't still have the original post, but to whoever was having these
> > problems: check the ex33 program, and the shell edit command in the
> > grabber, and see if these function correctly on your machine...
> >
> > --
> > Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
> > "Pigs use it for a tambourine" - Frank Zappa
>
> --
> Curator of the Unofficial Homepage for Borland C++ Builder
> http://www.nh.ultranet.com/~bsturk
>
> "HOL" The Hardware Obstruction Layer    The NTChrist
> Whatever happened to Pong???    Frank Black, The Pixies



--
Curator of the Unofficial Homepage for Borland C++ Builder
http://www.nh.ultranet.com/~bsturk

"HOL" The Hardware Obstruction Layer    The NTChrist
Whatever happened to Pong???    Frank Black, The Pixies

- Raw text -