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 appended TE>to it. Strange. I viewed the command.com file I am using (95666 bytes) and it does not look compressed at all (code too smooth, no traces of a self-decompression stub). There is, of course, the command.com available from sourceforge which is supplied in a self-linking to the "strings" file form, but even it is not necessarily compressed. TE>these 25 KB are the text resources which are thrown away if not TE>swapping to XMS But the transient size I mentioned (81744 bytes) is the memory image size of the transient part of COMMAND.COM, so,even if the file was compressed, it should have been already re-expanded at this time. Nevertheless,the XMS swap handle size is 106496 bytes. Anyway, my main question was about the reason why the memory image must be swapped, instead of reloaded from file. I advanced two guesses: 1) there are runtime variables in the transient part. 2)the runtime memory allocation loads the several file parts in an order unpredictably different from the order they are in the file. Is either of these correct or there is another reason ? Regards JAS ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
