Hello Rugxulo, hello Mercury 13,
Of course, you could just always rather test the "big dogs" of the DOS world: Turbo C, Lotus 1-2-3, Doom, QBASIC, etc .... I don't know of a good list of tools off-hand, but obviously things like DJGPP or OpenWatcom or FASM (or maybe small *nix utils like sed) might make for good tests.
I think Spinellis's system call tracer (https://www.spinellis.gr/sw/ports/trace/) might be a good adjunct to such test programs. It can help give an idea of the DOS system calls which are covered by a particular run of a program. However, the tracer does not handle calls to the BIOS, even though the BIOS is also quite an important part of the ABI for DOS programs. Thank you! -- https://github.com/tkchia _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
