From: Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id: <199912071113.MAA00290@spica-144.lu.erisoft.se>
Subject: Re: NT4 DPMI BUG (303h, Allocate Real-Mode Callback)
To: djgpp-workers AT delorie DOT com
Date: Tue, 7 Dec 1999 12:13:30 +0100 (MET)
In-Reply-To: <Pine.SUN.3.91.991207121512.29709K-100000@is> from "Eli Zaretskii" at Dec 7, 99 12:16:15 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> One other issue about the solution proposed by Peter: it sets the
> limit of the additional selector to 32h (since it only spans the
> real-mode registers' data structure.  This makes the segment be
> byte-granular (as opposed to page granularity used by DJGPP for all
> other selectors).  Can this cause any problems?  Is it safer to define
> a page-granular segment?

Isn't it possible to have page granularity with the limit 0x32? Or is
it in steps of 0x10? Use 0x40 if so.


Nico, The End,

							MartinS