From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DPMI identification
Date: Tue, 26 Oct 1999  0:32:51
Organization: Aspen Technology, Inc.
Lines: 20
Message-ID: <3814f6b3.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 991024091205 DOT 29385A-100000 AT is>
NNTP-Posting-Host: dcloan.aco.aspentech.com
X-NewsEditor: ED-1.5.8
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> A table that summarizes this testing is attached below.  The three
> cases where the vendor string was garbled did produce an ASCIIZ
> string, but its contents included control characters.
> 
> Charles, it seems that it is safe to include this function in CWSDPMI,
> since none of the DPMI servers crashed, except DR-DOS 7, which crashes for
> every DJGPP program.

I still have some reservations about this, since I'm convinced the right
thing to do is to test the functionality instead of the provider - but I
did code it up in my WIP and it currently shows "5.0" "CWSDPMI".  Beware,
however, you will probably all have to buy bigger disks since it added
an extra 42 bytes to the size of the image :-)

>   Windows 2000 beta 3            Succeeds            Vendor string garbled

This is fascinating.  Microsoft enhancing DPMI support?  I am amazed.

I suspect the control characters are some special entry point or something
really special...