Forcing JEMMEX to use the memory region C900-DFFF results in 87K free in the UMA, and that is sufficient to make FreeCOM work when loaded via SHELLHIGH, meaning not terminating with an out of memory error.
DEVICE=C:\FREEDOS\BIN\JEMMEX.EXE NOEMS I=C900-DFFF But this line is likely to have unintended side effects depending on what this region actually is for. Does anyone know this? > Am 19.02.2025 um 12:31 schrieb Bernd Böckmann <bernd-free...@boeckmann.io>: > > >> Am 19.02.2025 um 09:51 schrieb Bernd Böckmann via Freedos-devel >> <freedos-devel@lists.sourceforge.net>: >> >> As previously stated, a significant portion of upper memory is not available >> under VMware. So we should further try to figure out why this is the case. >> >> Screenshots are at: >> https://nextcloud.iww.rwth-aachen.de/index.php/s/WrPTqCpbGMAXZKN > > I did a scan for option ROMS and uploaded the result as screenshot to the > link above. There is a ROM signature for the memory at DC00-DFFF. I cannot > identify what this region is for. It simply contains a FAR RET as first byte > and otherwise does not contain any meaningful string in the first 0x50 bytes > to make it easily identifiable, and it consists mostly of zeroes. But it > explains why JEMMEX excluded its memory region. > > Further, I am not sure what happens to the memory segments E800-EFFF. There > seems to be some code in it, but it is lacking a signature. Maybe this is for > JEMMEX itself? > > Bernd > _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
