Hi Tom, > a) the current XMSSwap variant works anywhere.
If you mean "8086 compatible XMSSwap version": Compiling without 186 optimizations (Turbo C++ 1 does not get higher...) means that the FreeCOM binary gets bigger and that you have to disable some features to keep the size in range :-(. And you cannot XMSSwap on 8086 (which has no XMS) anyway. As far as I understand, CALL /S is only available on NON-XMSSwap FreeCOMs and XMSSwap only works with XMS, so using the XMSSwap version on 8086 would mean that you have a real memory hog FreeCOM there. On the other hand, making the XMSSwap version 8086 compatible even though 8086 has no XMS anyway will mean that you have to limit the features to keep the binary compileable at all. > conclusion: use and distribute XMSSWAP, compiled for 8086 > people who desperately want CALL /S may download and compile > there own freecom I would rather say: Use and distribute 186+ XMSSwap. People who desperately want 8086 compatibility should use a CALL /S FreeCOM. Eric ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
