X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Thu, 19 Mar 2009 02:03:14 -0400
Message-Id: <200903190603.n2J63ELG026454@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: 
	<419a56e7-9d0d-4835-8ff8-159efe59d96e AT e18g2000yqo DOT googlegroups DOT com>
	(message from Rugxulo on Wed, 18 Mar 2009 22:42:28 -0700 (PDT))
Subject: Re: demand loaded?
References: <0211e58d-1d17-494d-9411-28dc3b6d6571 AT c36g2000yqn DOT googlegroups DOT com> 
	<200903171651 DOT n2HGp9Cr021772 AT envy DOT delorie DOT com> <419a56e7-9d0d-4835-8ff8-159efe59d96e AT e18g2000yqo DOT googlegroups DOT com>
Errors-To: nobody AT delorie DOT com


> Was this due to XMS and VCPI used in v1 being less stringent or just
> that DPMI 0.9 lacks some things that DPMI 1.0 has (which you avoided
> requiring for compatibility)?

DPMI 0.9 is the basis for 286-based CPUs.  Yes, it's old, but that's
what most providers implement.  There just isn't any support in 0.9
for demand paged loading; the callbacks are all missing.

With djgpp 1.x we had access to the exception handling so we could
manage the paging ourselves.  DPMI 1.0 offers that, but we can't rely
on it.