Date: Thu, 16 May 1996 16:13:36 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Cc: djgpp AT delorie DOT com
Subject: Re: Bugs in CWSDPMI and FSDB
In-Reply-To: <30829676B0@fs2.mt.umist.ac.uk>
Message-Id: <Pine.SUN.3.91.960516160645.5771G-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 16 May 1996, A.Appleyard wrote:

> Like I said, djgpp should have stayed independent of non-Gnu DPMI's and their
> bugs and oddities; on entry it should have exited from any existing protected
> mode to real mode and then had within itself its own DPMI-equivalent.

That is based on misunderstanding (IMHO).  The problems which started 
this thread are OUTSIDE DJGPP.  It is not CWSDPMI that makes the machine 
reboot, it's Windows!  In my experience, many commercial vendors would in 
such cases say it's Windows' fault, go yell on uncle Bill.

When DJGPP runs under a DPMI server, it cannot ``exit from any existing
protected mode''.  Many DPMI environments (Windows is a notable example)
just won't let you do this.  You don't want that your DJGPP programs will
cause a GPF or pop messages like ``This application has compromised the
system integrity and will be terminated'' when run under Windows, do you?