Hi Robert,
>>> During some recent development work, I noticed that the FreeDOS MEM
>>> command reports the TSR I'm writing is using one less paragraph than
>>> its MS-DOS counterpart - it seems it does not account for space
>>> occupied by the MCB at the start of the TSR's heap, while the MS-DOS
Hi tom,
>> During some recent development work, I noticed that the FreeDOS MEM
>> command reports the TSR I'm writing is using one less paragraph than
>> its MS-DOS counterpart - it seems it does not account for space
>> occupied by the MCB at the start of the TSR's heap, while the MS-DOS MEM
>>
> During some recent development work, I noticed that the FreeDOS MEM
> command reports the TSR I'm writing is using one less paragraph than
> its MS-DOS counterpart - it seems it does not account for space
> occupied by the MCB at the start of the TSR's heap, while the MS-DOS MEM
> command doe
I personally use MAPMEM (from the old TSRCOM35 utilities) instead of MEM from
either MS or FD. I find its output much more useful and informative, at least
for my purposes. Here's an example of the output from my current VMWare
virtual machine (running MS-DOS rather than FreeDOS, and loading s
During some recent development work, I noticed that the FreeDOS MEM command
reports the TSR I'm writing is using one less paragraph than its MS-DOS
counterpart - it seems it does not account for space occupied by the MCB at the
start of the TSR's heap, while the MS-DOS MEM command does.
I'm uns
