Date: Sun, 4 Jul 1999 16:21:31 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: exobot AT my-deja DOT com
cc: djgpp AT delorie DOT com
Subject: Re: DPMI and CALDERA-DOS
In-Reply-To: <7lfr7s$dpm$1@nnrp1.deja.com>
Message-ID: <Pine.SUN.3.91.990704162110.13333X-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 1 Jul 1999 exobot AT my-deja DOT com wrote:

> thanks for your response, but I think the
> problem is not the Installation of djgpp
> or rhide, it is the DPMI-server itself.

Thank you for the detailed description of the problem.

However, I still don't see how you can rule out the other
possibilities that I mentioned, namely, the setup of DJGPP/RHIDE and
bugs in either RHIDE or the library.  These problems may be subtle
enough to only raise their ugly head when you use the Caldera DPMI
server.

So I would still recommend to produce a small test program that shows
the problem with redirection of the standard streams, and then run
that program under a debugger to see what exactly fails there when you
use the TaskManager.

>    1.3. TaskManager enabled, running 2 Tasks
>         with programms needing DPMI (Hello world)
>      - I get the error mesage:
>        "Warning: cannot open swap file C:\cwsdpmi.swp"
>      - or the system crashes.

This is expected: since CWSDPMI is loaded by every task, there are two
or more copies of CWSDPMI trying to use the same swap file in the
read-write mode, which will certainly fail in interesting ways...