Hi, Bernd meant "8086 FreeCOM which uses XMS". So there is NO 286 optimization. But there also is NO XMS on 8086. Actually the big problem here is that "which uses XMS" implies "swapping REQUIRES XMS" (i.e. NO call /s supported) which means "this FreeCOM can run on 8086 but will be a big bad memory hog". Such a FreeCOM is only useful for universal boot disks. Everybody who wants a FreeCOM for HARDDISK should either use the 286-optimized XMS-using version (286-optimization allows to compile all features without getting a binary which is too big for the memory model!) or the 8086-compatible CALL /S version because he will NEED CALL /S for many programs to have enough RAM free on his 8086.
Eric > When no XMS is found, CALL /S (swap freecom out to disk) should be > allowed to work. You CANNOT have both in the same binary at the moment. > This would be ok, but in most cases being optimized for 386 also means > that you have compiled for 386+ opcodes, so it is hard or impossible. See above. > 4DOS uses the same 'swap to XMS' trick, and in conventional memory is a > lot larger (220KB or so) without this trick. See advocacy against 8086-but-with-XMS-support version above. ------------------------------------------------------- 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
