Hello Jose,
> Anyway, my main question was about the reason why the memory image must be
> swapped, instead of reloaded from file.
the main and real reason is that I implemented it that way - feel free
to use the swapping command.com and CALL /S
but read the documentation what won't work with CA
Tom Ehlert replied to my questions in this list:
JAS>Is this why the XMS block allocated by xmsswap is some 10 KB larger than
JAS>the FreeCOM file size ,
TE>the XMS block size allocated is fairly unrelated to the file size.
TE>freecom.com is first compressed, and some text resources are append
Hello Jose,
BO>>Freecom and C library functions use malloc() and related dynamic memory
BO>>allocation functions that allocate data higher up.
> Is this why the XMS block allocated by xmsswap is some 10 KB larger than the
> FreeCOM file size ,
the XMS block size allocated is fairly unrelated t
Bart Oldeman said:
BO>It is also very tough to reload the code portions of the executable on
BO>demand at the right place if you write your command.com in C instead of in
BO>assembly language.
BO>It is not even the C perse that makes it tough, but rather the
BO>interactions with its run-time lib
