Quick and dirty testcases for MS-DOS API?
dmitry at codeweavers.com
Thu Jan 29 23:20:19 CST 2009
"Dan Kegel" <dank at kegel.com> wrote:
> 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.
Compiling DOS code to a .com file will produce a very small
executable, then embedding it into the test, put it in %TEMP%,
and exec should be trivial. No need for external tools IMO.
More information about the wine-devel