From: Brian Sturk Newsgroups: comp.os.msdos.djgpp Subject: Re: Allegro, spawnl, and PMODE/DJ...problems?? Date: Wed, 04 Mar 1998 19:57:36 -0500 Organization: Contractor Lines: 39 Message-ID: <34FDF880.8577D87B@nh.ultranet.com> References: <34FCD658 DOT 666D2596 AT nh DOT ultranet DOT com> NNTP-Posting-Host: d8.dial-10.exr.nh.ultra.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk 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