Hallo Herr Bernd Böckmann via Freedos-devel,

am Mittwoch, 19. Februar 2025 um 12:31 schrieben Sie:


>> 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.

Finally someone at the keyboard who knows what he is doing.

So the upper memory region has 69K free.

According to EXEHDR, my (somewhat older) 0.85 version needs 63K to even start 
executing.

Heap is allocated behind this, up to all available memory (here 69K).

So a maximum of 6 K is available for allocation. I know that COMMAND allocates 
a couple of 
memory for history, ALIAS, etc. 

So it is possible (and after so much failure to work probable, that COMMAND 
just starts, but can't 
allocate 40 Byte for command line, making it completely useless.

2 possibilities 

a) convert SHELLHIGH= to SHELL=
not such a big loss given that COMMAND has a resident size of ~3K

b) (better) get EXEHADR from the internet  
https://ecsoft2.org/system/files/repository/exehdr_exe-20040105.zip
(and I have not the faintest idea what they do in these 40K)

  EXEHDR /MIN:8192 command.com

requires a minimum additional load requirement of 8192 byte available for heap.
This should become part of the build process.

So this loads high if at least ~71KB are available, low if not.


While that's fine for experimenting, EXEHDR is not open source.

most likely 
        tools\patchsize command.com +6K
does the same, but should be changed to 
        tools\patchsize command.com +8K

I don't have VMWARE to reproduce the bug


Tom



_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to