Date: Tue, 14 Dec 1999 09:21:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Peter Johnson <locke AT mcs DOT net>
cc: Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>, djgpp AT delorie DOT com
Subject: Re: NT4 DPMI BUG (303h, Allocate Real-Mode Callback)
In-Reply-To: <4.2.1.19991213113354.00af5f00@popmail.mcs.net>
Message-ID: <Pine.SUN.3.91.991214092127.9300E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 13 Dec 1999, Peter Johnson wrote:

> So perhaps I need to be the one to "fix it someday" by copying the RMCB 
> structure?  It might be nice to do this even if the separate NT workaround 
> (as originally planned or as you envisioned) is still included, while we're 
> changing the code in that module.  Thoughts, Eli?

Given that nobody complained about this (except myself, more than two
years ago ;-), I would consider this low priority.  A user who needs
RMCBs in some industry-strength application, like a program that hooks
DOS interrupt 21h, will need to toss the RMCB wrapper anyhow, because
it has several additional limitations, like leaving interrupts
disabled.  While at that, it is easy for such a user to copy the RMCB
structure before reenabling interrupts.