From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro, spawnl, and PMODE/DJ...problems??
Date: Wed, 4 Mar 1998 19:00:16 +0000
Organization: None
Message-ID: <DPizHDAATa$0EwRP@talula.demon.co.uk>
References: <34FCD658 DOT 666D2596 AT nh DOT ultranet DOT com>
 <Pine DOT SUN DOT 3 DOT 91 DOT 980304104033 DOT 6541O-100000 AT is>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 22
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

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