delorie.com/archives/browse.cgi | search |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Generate real-mode 386 DOS executables? |
Date: | Mon, 06 Jan 2003 14:32:26 CST |
Organization: | Rice University, Houston TX |
Lines: | 11 |
Message-ID: | <3e19e7da.sandmann@clio.rice.edu> |
References: | <20030106182332 DOT GA11839 AT kendall DOT sfbr DOT org> |
NNTP-Posting-Host: | clio.rice.edu |
X-Trace: | joe.rice.edu 1041887298 15302 128.42.105.3 (6 Jan 2003 21:08:18 GMT) |
X-Complaints-To: | abuse AT rice DOT edu |
NNTP-Posting-Date: | 6 Jan 2003 21:08:18 GMT |
X-NewsEditor: | ED-1.5.9 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> My only use for HIMEM.SYS has been to load DOS into the HMA. Does this > capability (i.e., DOS=HIGH) have any advantage in protected mode, other > than to free up some conventional memory below the 640K mark? HIMEM.SYS handles weird chipset A20 configurations that CWSDPMI doesn't talk to. It allows modern disk caches and ramdisks to work (VDISK.SYS does work with CWSDPMI without HIMEM). It handles systems with memory "holes" and memory bios calls which don't support the full physically installed memory better (they are rare). But there are no advantages (and some memory/speed disadvantages) in using HIMEM only for Prot Mode memory management.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |