From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9609171345.AA13337@clio.rice.edu>
Subject: Re: DJGPP Installation Diagnostic Program
To: grendel AT ananke DOT amu DOT edu DOT pl
Date: Tue, 17 Sep 1996 08:45:36 -0600 (CDT)
Cc: robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de, djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.NEB.3.95.960917143635.20926A-100000@ananke.amu.edu.pl> from "Mark Habersack" at Sep 17, 96 02:40:38 pm
Content-Type: text
Content-Length: 693       

> Something else has just came to my mind: what if the user runs djverify on 286
> or 86 machine. I mean, I have never run any DJGPP program on such. Does the
> stub say something?

The stub notices that 32-bit DPMI is not available, tries to load CWSDPMI,
which does the processor type test, then issues a message if the machine
doesn't have enough bits ...  Then the stub fails with a No DPMI message.
Both CWSDPMI and the stub are 8088 clean (well, they have been at times,
who knows this week) up to the 80386  processor test.

I haven't checked PMODE to see if it's 8088 clean or how it behaves on
an XT.  When you mess up and get a 186+ instruction in the code it just
hangs on an XT...