Hello Rugxulo, hello Mercury 13, hello TK Chia,
>> 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. of course obviously not. Turbo C *compiler*, OpenWatcom, FASM, sed all just call mostly trivial file I/O routines (open, read sequential, write sequential, close), which even the most trivial implementation should support. no interesting functions are used (or needed) by a compiler. Turbo C *IDE*, QBASIC : some video I/O. a bit more interesting, but not too much. Doom: requires DOS-32. many years ahead for NightDOS. FreeCOM itself is a *much* better test as you can exercise a good part of DOS functions with it. just make it run, and I will provide some batch files that will tell you that night is not just compatible yet. in addition, there are a lot of 'undocumented DOS' utilities floating around that test some aspects of DOS. MSD.EXE will also help. > 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. I wasn't aware of this, and this would have been a really useful tool in debugging FreeDOS. Too late, but still useful (going by the description only). > 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. Of course. and doing interesting things with the LOL. (List Of List, not Laughing Out Loud ;) This being said, Night 'DOS' is still *very* much in development. So far they have a keyboard interrupt handler, a routine to read sectors in PIO mode, a function to print primary partitions, and a timer interrupt that switches the (integer) registers of some 'tasks'. the need for compatibility testing software is some years ahead. Tom _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
