Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <39D5F08B.B1B76EB1@phekda.freeserve.co.uk>
Date: Sat, 30 Sep 2000 14:54:19 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: DJGPP newsgroup <djgpp AT delorie DOT com>
Subject: Re: C Library: mmap() function
References: <970034480 DOT 596718 AT shelley DOT paradise DOT net DOT nz> <39d228f9 DOT sandmann AT clio DOT rice DOT edu> <a9m6tsst5lsjuup3ddp4tnm2uglmeunmsa AT 4ax DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

Damian Yerrick wrote:
> 
> On Wed, 27 Sep 2000 17:06:01, "Charles Sandmann"
> <sandmann AT clio DOT rice DOT edu> wrote:
>
> >You could write VXDs to extend Window's DPMI features.
> 
> No.  The latest version of Windows 9x does not support VXDs at all.
> In fact, Microsoft eliminated VXD support from Windows ME because
> VXDs were discovered to play a role in most bluescreens.

I think you are wrong here. Reading comp.os.ms-windows.programmer.vxd, I
saw a thread recently where people said that VxD programming was possible
under Windows ME. Given that VxDs are a fundamental part of Windows '9x's
design, I find it hard to believe they've totally rewritten it for ME,
even taking the new driver model (WDM) into consideration.

It would be possible to offer DPMI 1.0 features under Windows. Taking
shared memory as an example, I think you could map the same part of memory
into the memory space of any DPMI 1.0 client. VxDs have the power to do
this and more.

Bye,

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]