Date:	Mon, 18 Oct 1999 19:09:00 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Kalum Somaratna <kalum AT ToughGuy DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: spawnvpe hanging and bash GPF after running non-DJGPP exe
In-Reply-To:	<199910190220.UAA14581@lakdiva.slt.lk>
Message-ID:	<Pine.SUN.3.91.991018190256.6354C-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 18 Oct 1999, Kalum Somaratna wrote:

> May be the problem lies not with PMODE/W V1.33 but with 
> CWSDPMI.

This is possible, but unlikely.  There's no way CWSDPMI could invalidate 
the Int 31 entry in the IDT.

> I suggest this because 
> 1. when I load CWSDPMI as the DPMI host and try to run a 
> PMODE/W V1.33 program PMODE says 'Error could not allocate 
> page table memory' and aborts. However without CWSDPMI the 
> program runs under plain dos perfectly.

This is not the same problem as reported by the person who started this 
thread.  He had no problems running PMODE/W programs from DJGPP programs, 
but after the PMODE program exited, the first Int 31h call would crash.

What you see is a different problem.  I don't know what causes it.

> Clearly there is either a problem with either PMODE/W's Page 
> table allocating method or something wrong with CWSDPMI.

If you want to help resolve this issue, please contact Charles Sandmann 
<sandmann AT clio DOT rice DOT edu> and ask him for guidance.  I don't have access 
to PMODE/W and cannot debug this myself.  If you find clear evidence what 
is wrong about mixing PMODE/W and CWSDPMI in your case, and if the 
problem can be fixed by CWSDPMI, I'm sure Charles will try to do it for 
the next release.

> Please tell me if my testing's have any significance regarding the 
> current problem.

It doesn't seem so, but I might be mistaken.

- Raw text -