Quick and dirty testcases for MS-DOS API?

[Dan Kegel]

Looking at http://bugs.winehq.org/show_bug.cgi?id=17181
I get a feeling that we really need some
testcases to verify we conform to the 16 bit MS-DOS
API.   Yeah, even though 16 bit is on the way out,
there's still some use for a few win16 programs, and
they use MS-DOS for file I/O.

We could merge in http://win16test.googlecode.com,
but that requires the Watcom C compiler, and
"apt-cache search watcom" still comes up empty
(unless you're on Ark Linux, see
http://www.openwatcom.org/index.php/Installing_Open_Watcom_on_Linux )
And the Linux build had problems building DOS apps
last time I tried anyway.

But "apt-get install nasm" works great, so let's
use it to run just a few crucial testcases, in
particular, the one that keeps DOS apps from
recursively deleting directories.

What I'm thinking is to add a configure check for nasm.
If it's present, and the target is 32 bit Intel,
dlls/winedos/tests would use it to assemble a few
simple assembly testcases.  The test cases
would be run from a normal test case (so no deep
integration), and only when
running on a machine capable of running 16 bit code.
I'll probably have an include file for routines to print
PASS and FAIL, but otherwise it'll be very, very bare bones.

'Course, I have no idea when I'll have time to do this,
but I imagine it won't be too complicated.  It wouldn't
bother me at all if somebody beat me to it.
- Dan