Date: Thu, 15 Oct 1998 12:37:29 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: John Elliott <jce AT seasip DOT demon DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Running multiple DJGPP apps from 16-bit
In-Reply-To: <908392312.2282.1.nnrp-04.c2de7091@news.demon.co.uk>
Message-ID: <Pine.SUN.3.91.981015123659.15214G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Wed, 14 Oct 1998, John Elliott wrote:

>   One of the desk accessories is a DJGPP program. GEM loads this and then
> lets it run. When it blocks and GEM regains control, the accessory and the
> DPMI host are in a __dpmi_int() call and expecting it to return.
> 
>  GEM then runs another DJGPP program (either application or desk accessory), 
> which crashes. My guess is that a second DJGPP program can't be started from 
> real mode while the first one is suspended in a __dpmi_int() call. 

One thing I don't understand is where does CWSDPMI fit into this
picture.  Do you maybe load CWSDPMI resident before GEM?  Or do you
let the DJGPP program to load it during startup as usual?

Also, please post several examples of the messages printed when the
second DJGPP program crashes, and a bit more details about what
happens after it crashes (is the entire machine wedged? does the first
DJGPP program still work? etc.).