Conflict between JEMMEX and BIOS service E820h (Developers)
> First of all - I have found a bug in Japheth's utility GETI15EX. It does
> not correctly process the E820h chain and omits the last record.
> (log here )
Yes. This tool is totally outdated. The up-to-date tool is called MEMSTAT and contained in the jemmex package.
> But if I load JemmEX (from config.sys) the memory map is corrupted and the
> last entry from E820h is corrupted and is marked as memory region type 2
> (aka reserved).
That's quite correct. It's not "corrupted", however. The currect jemmex implements XMS v3.5, that is, the XMM handles memory beyond 4 GB - and it wants to handle that memory exclusively. For this reason it intercepts int 15h, ax=e820 and marks the corresponding regions as "reserved". It's documented, so all you need is to read XMS35.txt.
If you don't want this, there's another jemm version, jemmexl.exe, that leaves int 15h e820h untouched.
---
MS-DOS forever!
Complete thread:
- Wrong memory map using E820h? - Laaca, 06.01.2021, 23:30 (Developers)
- Wrong memory map using E820h? - Laaca, 07.01.2021, 10:43
- Conflict between JEMMEX and BIOS service E820h - Laaca, 07.01.2021, 22:18
- Conflict between JEMMEX and BIOS service E820h - Japheth, 08.01.2021, 04:57
- Conflict between JEMMEX and BIOS service E820h - Laaca, 08.01.2021, 13:37
- Conflict between JEMMEX and BIOS service E820h - Japheth, 08.01.2021, 04:57
- Conflict between JEMMEX and BIOS service E820h - Laaca, 07.01.2021, 22:18
- Wrong memory map using E820h? - Laaca, 07.01.2021, 10:43