X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Fri, 20 Jul 2001 09:41:56 -0500
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: djgpp AT delorie DOT com
Subject: Re: memory under DOS
Message-ID: <20010720094156.A18035@kendall.sfbr.org>
Mail-Followup-To: djgpp AT delorie DOT com
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010717130411 DOT 29833A AT is> <20010717160543 DOT 05952 DOT 00000668 AT ng-ba1 DOT aol DOT com> <200107172028 DOT QAA32600 AT envy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200107172028.QAA32600@envy.delorie.com>; from dj@delorie.com on Tue, Jul 17, 2001 at 04:28:10PM -0400
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

-: Try taking himem.sys out completely and see if cwsdpmi does the right
-: thing.  Or, you may have to load some alternate xms driver, like qemm
-: or 386max.

Are there *any* advantages to loading HIMEM.SYS in protected mode?
Loading DOS `high' or `low' may be irrelevant in PM, but what about
shadow RAM, EMB handles, or a20 control?