Message-ID:	<D1FB30BBA491D1118E6D006097BCAE3911C265@Probe-nt-2a.Probe.co.uk>
From:	Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To:	djgpp AT delorie DOT com
Subject:	Re: Allegro, spawnl, and PMODE/DJ...problems...Still,even w/3.0??
Date:	Thu, 5 Mar 1998 12:01:16 -0000
MIME-Version:	1.0

Brian Sturk writes:
> 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.
[...]
> 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.

It is quite possible that you just won't be able to make this work:
I don't know what issues there are with spawning programs that use
different DPMI servers like this, but in general I think it would be
much safer if you could avoid doing this altogether :-)

Things to try:

- spawn some different programs, and see if this is a generic problem
or only limited to a particular child prog.

- copy allegro.cfg into the same directory as your grabber.exe, edit
the "data = start /w notepad" line near the end of the file to invoke
some program of your own, run the grabber, and use the shell edit
(ctrl+Z) command on a binary data object. Does this work correctly?

- take your simple program that worked, and try to find out exactly
what is the difference from the more complex code that has problems,
by gradually adding or removing things until you can locate exactly
what is the culprit.

	Shawn Hargreaves.

- Raw text -