High memory area

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Low_memory/hLcfWzlB">Low memory</a> (the first 64 KB of memory)</li>
<li><a href="/facts/Extended_memory/WoJJj268">Extended memory</a> (XMS)</li>
<li><a href="/facts/Expanded_memory/cYurvMxB">Expanded memory</a> (EMS)</li>
<li><a href="/facts/Unreal_mode/W2ltI5QE">Unreal mode</a></li>
<li><a href="/facts/Rebasing/mHo899gJ">Rebasing</a></li>
<li><a href="/facts/Paragraph_boundary_relocation/yKQLrrPE">Paragraph boundary relocation</a></li>
<li><a href="/facts/Intra-segment_offset_relocation/yKQLrrPE">Intra-segment offset relocation</a></li>
<li><a href="/facts/SHELLHIGH_(CONFIG.SYS_directive)/a1QSEJhj">SHELLHIGH (CONFIG.SYS directive)</a> SIZE=xxxx parameter to override default HMA pre-allocation (DR-DOS 7.02 and higher only)<a class="footnote-ref" id="fnref:36" href="#fn:36">36</a></li>
<li><a href="/facts/HMAREA_(CONFIG.SYS_directive)/a1QSEJhj">HMAREA (CONFIG.SYS directive)</a> to specify the HMA segment (PTS-DOS only), similar to the DR DOS HIDOS.SYS /BDOS=xxxx parameter</li>
<li><a href="/facts/Incomplete_address_decoding/PmLNFq01">Incomplete address decoding</a></li></ul>
<h2 id="notes">Notes</h2>

<h2 id="further-reading">Further reading</h2>
<ul><li>Necasek, Michal (2011-09-13). <a href="http://www.os2museum.com/wp/who-needs-the-address-wraparound-anyway/">"Who needs the address wraparound, anyway?"</a>. OS/2 Museum. <a href="https://web.archive.org/web/20200219004644/http://www.os2museum.com/wp/who-needs-the-address-wraparound-anyway/">Archived</a> from the original on 2020-02-19. Retrieved 2020-02-19. […] <a href="/facts/86-DOS/u0Hm0Ijv">86-DOS</a>, and hence <a href="/facts/PC_DOS/ScsfqAwQ">PC DOS</a>/<a href="/facts/MS-DOS/fVrrz1uN">MS-DOS</a>, used a clever trick. The byte at offset 5 of the <a href="/facts/Program_Segment_Prefix/ljzJrWyd">PSP</a> contained a far call opcode (9Ah); the word at offset 6 of the PSP contained the appropriate value to indicate program segment size, and also the offset part of the far call. The word at offset 8, which served as the segment part of the far call, was crafted such that when combined with the offset, it would wrap around (a well understood feature of the <a href="/facts/8086/sS9dlSdK">8086</a> CPU) and point to address 0:C0h, which contains interrupt vector 30h. […] the <a href="/facts/CALL_5_(DOS)/K8NV4Gg5">CALL 5</a> interface works even in DOS emulation under Windows NT and OS/2, and those systems most certainly cannot run with the <a href="/facts/A20_line/K8NV4Gg5">A20 line</a> disabled. How does that work then? […] Rather than chopping off address bits, the system mirrors the five bytes at 0:C0h at 1000C0h. The same technique had been in fact used in DOS 5 and above running with <a href="/facts/DOS_(CONFIG.SYS_directive)/a1QSEJhj">DOS</a>=HIGH. In that case, DOS makes sure that linear address 1000C0h contains the appropriate far call. […]</li>
<li>Kozierok, Charles M. (2001-04-17) [1997]. <a href="https://web.archive.org/web/20061016143339/http://www.pcguide.com/ref/ram/logicHMA-c.html">"High Memory Area (HMA)"</a>. The PC Guide. 2.2.0. Archived from <a href="http://www.pcguide.com/ref/ram/logicHMA-c.html">the original</a> on 2006-10-16. Retrieved 2006-10-15.</li>
<li>Paul, Matthias R. (2002-04-11). <a href="https://marc.info/?l=freedos-dev&m=101853130816682&w=2">"Re: [fd-dev] ANNOUNCE: CuteMouse 2.0 alpha 1"</a>. freedos-dev. <a href="https://web.archive.org/web/20200221130238/https://marc.info/?l=freedos-dev&m=101853130816682&w=2">Archived</a> from the original on 2020-02-21. Retrieved 2020-02-21. […] in case of such <a href="/facts/Fat_pointer/211NC5eu">mangled pointers</a> […] many years ago Axel and I were thinking about a way how to use *one* entry point into a driver for multiple interrupt vectors (as this would save us a lot of space for the multiple entry points and the more or less identical startup/exit framing code in all of them), and then switch to the different interrupt handlers internally. For example: 1234h:0000h […] 1233h:0010h […] 1232h:0020h […] 1231h:0030h […] 1230h:0040h […] all point to exactly the same entry point. If you hook INT 21h onto 1234h:0000h and INT 2Fh onto 1233h:0010h, and so on, they would all go through the same "loophole", but you would still be able to distinguish between them and branch into the different handlers internally. Think of a "compressed" entry point into a <a href="/facts/A20_line/K8NV4Gg5">A20</a> stub for HMA loading. This works as long as no program starts doing segment:offset magics. […] Contrast this with the opposite approach to have multiple entry points (maybe even supporting <a href="/facts/IBM/QszA7nwd">IBM</a>'s <a href="/facts/IBM_Interrupt_Sharing_Protocol/6croHFxf">Interrupt Sharing Protocol</a>), which consumes much more memory if you hook many interrupts. […] We came to the result that this would most probably not be save in practise because you never know if other drivers normalize or denormalize pointers, for what reasons ever. […]</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Ingenoso, Tony (1998-12-20). "Chapter 13 - The A20 gate and the HMA". Making Code Work Better - How to minimize the size of 80x86 code and sometimes make it faster (e-book). Archived from the original on 2019-11-18. Retrieved 2019-11-18. <a href="http://www.bobeager.uk/tonyingenoso/chap13.htm" target="_blank">http://www.bobeager.uk/tonyingenoso/chap13.htm</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Ingenoso, Tony (1998-12-20). "Chapter 13 - The A20 gate and the HMA". Making Code Work Better - How to minimize the size of 80x86 code and sometimes make it faster (e-book). Archived from the original on 2019-11-18. Retrieved 2019-11-18. <a href="http://www.bobeager.uk/tonyingenoso/chap13.htm" target="_blank">http://www.bobeager.uk/tonyingenoso/chap13.htm</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">Ingenoso, Tony (1998-12-20). "Chapter 13 - The A20 gate and the HMA". Making Code Work Better - How to minimize the size of 80x86 code and sometimes make it faster (e-book). Archived from the original on 2019-11-18. Retrieved 2019-11-18. <a href="http://www.bobeager.uk/tonyingenoso/chap13.htm" target="_blank">http://www.bobeager.uk/tonyingenoso/chap13.htm</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">A stub is not necessary for the resident system extensions SHARE and NLSFUNC under DR DOS 6.0 and higher, because they only hook the multiplex interrupt INT 2Fh and can therefore utilize a backdoor interface to hook into the interrupt chain in kernel space so that the kernel's gate A20 handler will provide the functionality of the stub. <a href="/wiki/SHARE_(DOS_command)" target="_blank">/wiki/SHARE_(DOS_command)</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Dryfoos, Mike, ed. (1991-09-18) [1991-07-19]. "MS-DOS 5.0 Development Post-Mortem Report" (PDF) (mail as court document). Microsoft. p. 10. MS-PCA1179169 (MS-PCA1179159-MS-PCA1179191). MS7020988 (MS7020978-MS7021010). Depo. Ex. 1109. Comes v Microsoft Plaintiff's Exhibit 3473. CA.No.2:96CV645B Plaintiff's Exhibit 477. Archived (PDF) from the original on 2019-04-02. Retrieved 2019-07-22. […] One of the most important stimulanta for adding features was competitive pressure from DRDOS 5.0, which we first learnt of in the spring of 1990. The DRDOS feature set led us to add UMB support, task swapping, and Undelete. […] Considerable amounts of the team's management attention was diverted to new features such as file transfer software, undelete and network installation […] Eventually this situation reached a crisis point at the end of July 1990, and, led by BradS, the team's management spent an arduous series of meetings nailing down a schedule and process for closing the project down […] (1+32 pages) <a href="http://www.windowswiki.info/wp-content/uploads/codenames/PX03473.pdf" target="_blank">http://www.windowswiki.info/wp-content/uploads/codenames/PX03473.pdf</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">Banta, K.; Partridge, D. (1994-08-18). "Third Party Memory Managers". DR DOS 6.0 (Technical information document). Revision A. Novell. TID800074 (replaces FYI-M-1303). Archived from the original on 2021-12-15. Retrieved 2021-12-15. <a href="https://ftp.zx.net.nz/pub/archive/novell/drdos/6/DR6TID/800074.TXT" target="_blank">https://ftp.zx.net.nz/pub/archive/novell/drdos/6/DR6TID/800074.TXT</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">Dryfoos, Mike, ed. (1991-09-18) [1991-07-19]. "MS-DOS 5.0 Development Post-Mortem Report" (PDF) (mail as court document). Microsoft. p. 10. MS-PCA1179169 (MS-PCA1179159-MS-PCA1179191). MS7020988 (MS7020978-MS7021010). Depo. Ex. 1109. Comes v Microsoft Plaintiff's Exhibit 3473. CA.No.2:96CV645B Plaintiff's Exhibit 477. Archived (PDF) from the original on 2019-04-02. Retrieved 2019-07-22. […] One of the most important stimulanta for adding features was competitive pressure from DRDOS 5.0, which we first learnt of in the spring of 1990. The DRDOS feature set led us to add UMB support, task swapping, and Undelete. […] Considerable amounts of the team's management attention was diverted to new features such as file transfer software, undelete and network installation […] Eventually this situation reached a crisis point at the end of July 1990, and, led by BradS, the team's management spent an arduous series of meetings nailing down a schedule and process for closing the project down […] (1+32 pages) <a href="http://www.windowswiki.info/wp-content/uploads/codenames/PX03473.pdf" target="_blank">http://www.windowswiki.info/wp-content/uploads/codenames/PX03473.pdf</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">Dryfoos, Mike, ed. (1991-09-18) [1991-07-19]. "MS-DOS 5.0 Development Post-Mortem Report" (PDF) (mail as court document). Microsoft. p. 10. MS-PCA1179169 (MS-PCA1179159-MS-PCA1179191). MS7020988 (MS7020978-MS7021010). Depo. Ex. 1109. Comes v Microsoft Plaintiff's Exhibit 3473. CA.No.2:96CV645B Plaintiff's Exhibit 477. Archived (PDF) from the original on 2019-04-02. Retrieved 2019-07-22. […] One of the most important stimulanta for adding features was competitive pressure from DRDOS 5.0, which we first learnt of in the spring of 1990. The DRDOS feature set led us to add UMB support, task swapping, and Undelete. […] Considerable amounts of the team's management attention was diverted to new features such as file transfer software, undelete and network installation […] Eventually this situation reached a crisis point at the end of July 1990, and, led by BradS, the team's management spent an arduous series of meetings nailing down a schedule and process for closing the project down […] (1+32 pages) <a href="http://www.windowswiki.info/wp-content/uploads/codenames/PX03473.pdf" target="_blank">http://www.windowswiki.info/wp-content/uploads/codenames/PX03473.pdf</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">Schulman, Andrew; Brown, Ralf D.; Maxey, David; Michels, Raymond J.; Kyle, Jim (1994) [November 1993]. Williams, Andrew (ed.). Undocumented DOS: A programmer's guide to reserved MS-DOS functions and data structures - expanded to include MS-DOS 6, Novell DOS and Windows 3.1. The Andrew Schulman Programming Series (1st printing, 2nd ed.). Reading, Massachusetts, USA: Addison Wesley Publishing Company. pp. 42, 349–350, 437–438. ISBN 0-201-63287-X. ISBN 978-0-201-63287-3. (xviii+856+vi pages, 3.5"-floppy [1]) Errata: [2][3] <a href="0-201-63287-X" target="_blank">0-201-63287-X</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Schulman, Andrew; Brown, Ralf D.; Maxey, David; Michels, Raymond J.; Kyle, Jim (1994) [November 1993]. Williams, Andrew (ed.). Undocumented DOS: A programmer's guide to reserved MS-DOS functions and data structures - expanded to include MS-DOS 6, Novell DOS and Windows 3.1. The Andrew Schulman Programming Series (1st printing, 2nd ed.). Reading, Massachusetts, USA: Addison Wesley Publishing Company. pp. 42, 349–350, 437–438. ISBN 0-201-63287-X. ISBN 978-0-201-63287-3. (xviii+856+vi pages, 3.5"-floppy [1]) Errata: [2][3] <a href="0-201-63287-X" target="_blank">0-201-63287-X</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">Paul, Matthias R. (2002-02-02). "Treiber dynamisch nachladen (Intra-Segment-Offset-Relokation zum Laden von TSRs in die HMA)" [Loading drivers dynamically (Intra-segment offset relocation to load TSRs into the HMA)] (in German). Newsgroup: de.comp.os.msdos. Archived from the original on 2017-09-09. Retrieved 2017-07-02. (NB. Gives a comprehensive overview on the history and "nature" of the HMA and the non-obvious design constraints to be observed when developing resident system extensions to be loaded into the HMA. It also describes how to address these issues using stubs, backdoors, and intra-segment offset relocation, a method used by DR-DOS drivers capable of relocating into the HMA and similar to a (more sophisticated) method used as the basis for the dynamic dead code elimination in the author's FreeKEYB driver.) <a href="https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ" target="_blank">https://groups.google.com/d/msg/de.comp.os.msdos/tdvpBoMVN6A/a_zqDxGk22IJ</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">"Format of HMA Memory Block (DR DOS 6.0 kernel loaded in HMA)". RBIL. 2000. Archived from the original on 2020-02-18. Retrieved 2020-02-18. <a href="http://faydoc.tripod.com/structures/15/1588.htm" target="_blank">http://faydoc.tripod.com/structures/15/1588.htm</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">Paul, Matthias R. (2002-04-10). "[fd-dev] HMA access from TSR". freedos-dev. Archived from the original on 2017-09-09. Retrieved 2017-09-09. […] MS-DOS 7.0+ adds INT 21h/AX=4A03h and INT 21h/AX=4A04h. RBIL61 INT 21h/AH=52h has some info on the MS-DOS 7.0+ HMA MCB chain […] HMA relocation for TSRs makes much sense for DR-DOS: Although you can load large parts of the BIOS and BDOS, the resident part of the shell, the BUFFERS, and DR-DOS TSRs like SHARE, KEYB, and NLSFUNC (and in some issues parts of TASKMGR and NWCACHE) into the HMA, there is usually still free space available, typically around 10 Kb (up to ca. 20 Kb when you use a 3rd party shell). It also makes sense for MS-DOS 5.0 - 6.22 and PC DOS up to 2000, which typically leave 4 - 7 Kb of the HMA memory unused (SHARE, KEYB, and NLSFUNC cannot load into the HMA, but DBLSPACE and HIMEM can to some extent). Available HMA space can be rather tight with MS-DOS 7.0+, since this issue introduced a new and for the most part undocumented RMD data structure usually located in the HMA. The kernel collects and records configuration and Real Mode Driver data during boot (type of driver, interrupts hooked by driver, CONFIG.SYS line of invocation, etc.) and stores this information in an […] complicated […] and […] growing data structure. Presumably this info is meant to be used by the Windows core to get a better picture of the loaded Real Mode drivers instead of treating DOS as a monolithic block, or even […] attempt to unhook or unload some of them, however, it is only used to a very limited extent (for example you can see some of the info reflected in the log files created on Windows 9x startup, and some parts of the Windows configuration manager also make use of it), leaving room for speculation much beyond the technical side - in particular because nothing of the interesting stuff is documented… […] <a href="https://marc.info/?l=freedos-dev&m=101846072627263&w=4" target="_blank">https://marc.info/?l=freedos-dev&m=101846072627263&w=4</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">Paul, Matthias R. (1997-07-30) [1994-05-01]. "II.4. Undokumentierte Eigenschaften externer Kommandos". NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. MPDOSTIP (in German) (3 ed.). Archived from the original on 2016-11-05. Retrieved 2012-01-11. (NB. NWDOSTIP.TXT is a comprehensive work on Novell DOS 7 and OpenDOS 7.01, including the description of many undocumented features and internals. It is part of the author's yet larger MPDOSTIP.ZIP collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the file.) [4] <a href="http://www.antonis.de/dos/dos-tuts/mpdostip/html/nwdostip.htm" target="_blank">http://www.antonis.de/dos/dos-tuts/mpdostip/html/nwdostip.htm</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">Paul, Matthias R. (2001-04-09). "II.4. Undokumentierte Eigenschaften externer Kommandos". NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. MPDOSTIP (in German) (3 ed.). <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">Paul, Matthias R. (2002-04-10). "[fd-dev] HMA access from TSR". freedos-dev. Archived from the original on 2017-09-09. Retrieved 2017-09-09. […] MS-DOS 7.0+ adds INT 21h/AX=4A03h and INT 21h/AX=4A04h. RBIL61 INT 21h/AH=52h has some info on the MS-DOS 7.0+ HMA MCB chain […] HMA relocation for TSRs makes much sense for DR-DOS: Although you can load large parts of the BIOS and BDOS, the resident part of the shell, the BUFFERS, and DR-DOS TSRs like SHARE, KEYB, and NLSFUNC (and in some issues parts of TASKMGR and NWCACHE) into the HMA, there is usually still free space available, typically around 10 Kb (up to ca. 20 Kb when you use a 3rd party shell). It also makes sense for MS-DOS 5.0 - 6.22 and PC DOS up to 2000, which typically leave 4 - 7 Kb of the HMA memory unused (SHARE, KEYB, and NLSFUNC cannot load into the HMA, but DBLSPACE and HIMEM can to some extent). Available HMA space can be rather tight with MS-DOS 7.0+, since this issue introduced a new and for the most part undocumented RMD data structure usually located in the HMA. The kernel collects and records configuration and Real Mode Driver data during boot (type of driver, interrupts hooked by driver, CONFIG.SYS line of invocation, etc.) and stores this information in an […] complicated […] and […] growing data structure. Presumably this info is meant to be used by the Windows core to get a better picture of the loaded Real Mode drivers instead of treating DOS as a monolithic block, or even […] attempt to unhook or unload some of them, however, it is only used to a very limited extent (for example you can see some of the info reflected in the log files created on Windows 9x startup, and some parts of the Windows configuration manager also make use of it), leaving room for speculation much beyond the technical side - in particular because nothing of the interesting stuff is documented… […] <a href="https://marc.info/?l=freedos-dev&m=101846072627263&w=4" target="_blank">https://marc.info/?l=freedos-dev&m=101846072627263&w=4</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Chappell, Geoff (January 1994). Schulman, Andrew; Pedersen, Amorette (eds.). DOS Internals. The Andrew Schulman Programming Series (1st printing, 1st ed.). Addison Wesley Publishing Company. pp. 4, 21, 100–106, 127–129. ISBN 978-0-201-60835-9. ISBN 0-201-60835-9. (xxvi+738+iv pages, 3.5"-floppy [5][6]) Errata: [7][8][9] <a href="978-0-201-60835-9" target="_blank">978-0-201-60835-9</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">Chappell, Geoff (January 1994). Schulman, Andrew; Pedersen, Amorette (eds.). DOS Internals. The Andrew Schulman Programming Series (1st printing, 1st ed.). Addison Wesley Publishing Company. pp. 4, 21, 100–106, 127–129. ISBN 978-0-201-60835-9. ISBN 0-201-60835-9. (xxvi+738+iv pages, 3.5"-floppy [5][6]) Errata: [7][8][9] <a href="978-0-201-60835-9" target="_blank">978-0-201-60835-9</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">Paul, Matthias R. (2002-12-04). "[fd-dev] DISPLAY CON?". freedos-dev. Archived from the original on 2021-12-08. […] some issues of DISPLAY.SYS (of PC DOS 7/2000, for example) store the currently unused fonts in XMS memory. Some earlier issues of MS-DOS/PC DOS DISPLAY.SYS seem to have had a facility to store them in the HMA […] <a href="https://marc.info/?l=freedos-dev&m=103902610816421&w=2" target="_blank">https://marc.info/?l=freedos-dev&m=103902610816421&w=2</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">Schulman, Andrew; Brown, Ralf D.; Maxey, David; Michels, Raymond J.; Kyle, Jim (1994) [November 1993]. Williams, Andrew (ed.). Undocumented DOS: A programmer's guide to reserved MS-DOS functions and data structures - expanded to include MS-DOS 6, Novell DOS and Windows 3.1. The Andrew Schulman Programming Series (1st printing, 2nd ed.). Reading, Massachusetts, USA: Addison Wesley Publishing Company. pp. 42, 349–350, 437–438. ISBN 0-201-63287-X. ISBN 978-0-201-63287-3. (xviii+856+vi pages, 3.5"-floppy [1]) Errata: [2][3] <a href="0-201-63287-X" target="_blank">0-201-63287-X</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
<li id="fn:30">Cooper, Jim (2002). Using MS-DOS 6.22 (special 3rd ed.). Que Publishing. p. 669. ISBN 0-78972573-8. ISBN 978-0-78972573-8. Archived from the original on 2020-02-18. Retrieved 2020-02-18. <a href="0-78972573-8" target="_blank">0-78972573-8</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></li>
<li id="fn:31">Brooks, Vernon C. (2014). "This is a detailed list of the changes I made in PC DOS 7.0". PC DOS Retro. Archived from the original on 2020-02-18. Retrieved 2020-02-18. […] DOSKEY.COM […] Move code to HMA if available. […] SHARE.EXE […] Move code to HMA if available and added /NOHMA option force loading low. […] <a href="https://sites.google.com/site/pcdosretro/dosmods" target="_blank">https://sites.google.com/site/pcdosretro/dosmods</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></li>
<li id="fn:32">Brooks, Vernon C. (2014). "This is a detailed list of the changes I made in PC DOS 7.0". PC DOS Retro. Archived from the original on 2020-02-18. Retrieved 2020-02-18. […] DOSKEY.COM […] Move code to HMA if available. […] SHARE.EXE […] Move code to HMA if available and added /NOHMA option force loading low. […] <a href="https://sites.google.com/site/pcdosretro/dosmods" target="_blank">https://sites.google.com/site/pcdosretro/dosmods</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></li>
<li id="fn:33">Paul, Matthias R. (2002-04-10). "[fd-dev] HMA access from TSR". freedos-dev. Archived from the original on 2017-09-09. Retrieved 2017-09-09. […] MS-DOS 7.0+ adds INT 21h/AX=4A03h and INT 21h/AX=4A04h. RBIL61 INT 21h/AH=52h has some info on the MS-DOS 7.0+ HMA MCB chain […] HMA relocation for TSRs makes much sense for DR-DOS: Although you can load large parts of the BIOS and BDOS, the resident part of the shell, the BUFFERS, and DR-DOS TSRs like SHARE, KEYB, and NLSFUNC (and in some issues parts of TASKMGR and NWCACHE) into the HMA, there is usually still free space available, typically around 10 Kb (up to ca. 20 Kb when you use a 3rd party shell). It also makes sense for MS-DOS 5.0 - 6.22 and PC DOS up to 2000, which typically leave 4 - 7 Kb of the HMA memory unused (SHARE, KEYB, and NLSFUNC cannot load into the HMA, but DBLSPACE and HIMEM can to some extent). Available HMA space can be rather tight with MS-DOS 7.0+, since this issue introduced a new and for the most part undocumented RMD data structure usually located in the HMA. The kernel collects and records configuration and Real Mode Driver data during boot (type of driver, interrupts hooked by driver, CONFIG.SYS line of invocation, etc.) and stores this information in an […] complicated […] and […] growing data structure. Presumably this info is meant to be used by the Windows core to get a better picture of the loaded Real Mode drivers instead of treating DOS as a monolithic block, or even […] attempt to unhook or unload some of them, however, it is only used to a very limited extent (for example you can see some of the info reflected in the log files created on Windows 9x startup, and some parts of the Windows configuration manager also make use of it), leaving room for speculation much beyond the technical side - in particular because nothing of the interesting stuff is documented… […] <a href="https://marc.info/?l=freedos-dev&m=101846072627263&w=4" target="_blank">https://marc.info/?l=freedos-dev&m=101846072627263&w=4</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></li>
<li id="fn:34">Sweger, Kristofer (2007) [2002-07-15]. "ANSIPLUS and Windows". Archived from the original on 2021-11-28. Retrieved 2021-11-28. […] ANSIPLUS's code cannot be loaded to the HMA under MS-DOS 7 (Windows 9x only) because there apparently is not enough unused HMA memory available. […] <a href="http://www.sweger.com/ansiplus/TechNotesWindows.html" target="_blank">http://www.sweger.com/ansiplus/TechNotesWindows.html</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></li>
<li id="fn:35">Paul, Matthias R. (2002-08-13). "Suche freien Speicherbereich unterhalb von 1 MB, der nicht von OS überschrieben wird" (in German). Newsgroup: de.comp.lang.assembler.x86. Archived from the original on 2017-09-04. Retrieved 2017-09-03. <a href="https://groups.google.com/d/msg/de.comp.lang.assembler.x86/boKnIpqPl-Q/ZLDFDX9E1e0J" target="_blank">https://groups.google.com/d/msg/de.comp.lang.assembler.x86/boKnIpqPl-Q/ZLDFDX9E1e0J</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></li>
<li id="fn:36">Paul, Matthias R. (1997-10-02) [1997-09-29]. "Caldera OpenDOS 7.01/7.02 Update Alpha 3 IBMBIO.COM - README.TXT and BOOT.TXT - A short description of how OpenDOS is booted". Archived from the original on 2003-10-04. Retrieved 2009-03-29. [10] <a href="https://web.archive.org/web/20031004074600/http://www-student.informatik.uni-bonn.de/~frinke/ibmbioa3.zip" target="_blank">https://web.archive.org/web/20031004074600/http://www-student.informatik.uni-bonn.de/~frinke/ibmbioa3.zip</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></li>
</ol>

High memory area open-in-new

High memory area