win16 doesn't have the notion of stdout/stderr,
so 16 bit C compilers like watcom tend to simulate
stdout by putting up a window.
http://win16test.googlecode.com/svn/trunk/src/test.h
(a port of the 32 bit test.h) uses freopen to open
a log file to receive all the ok() and trace() output from
the
It would be sweet if you put up the executables too.
Jennifer Lai wrote:
Hi,
I've collected and fixed some win16 tests.
Since they are not going to be included in the wine tree, I've placed them
under
http://www.cs.ucla.edu/~jlai/win16test/
In order to build these tests, Open Watcom
Hi,
I've collected and fixed some win16 tests.
Since they are not going to be included in the wine tree, I've placed them under
http://www.cs.ucla.edu/~jlai/win16test/
In order to build these tests, Open Watcom was used. The tar ball also
includes the scripts of installing Open Watcom, building
Hi,
I've collected and fixed some win16 tests.
Since they are not going to be included in the wine tree, I've placed them
under
http://www.cs.ucla.edu/~jlai/win16test/
http://www.cs.ucla.edu/%7Ejlai/win16test/
In order to build these tests, Open Watcom was used. The tar ball also
includes
Dan Kegel wrote:
As Andreas Mohr pointed out a while back,
http://www.winehq.org/pipermail/wine-devel/2005-August/039602.html
we really need a win16 test suite to make sure our
win16 support doesn't rot. As far as I know, nobody's
managed to get win16 tests into the tree, presumably
because
On 7/9/07, Markus Amsler [EMAIL PROTECTED] wrote:
We have to distinguish between win16 and dos tests.
Absolutely. dos .com executables currently don't work,
but win16 .exe's with the same contents do work.
I plan to test DOS .com files using very simple pure assembly.
(That was the real way
Dan Kegel wrote:
On 7/9/07, Markus Amsler [EMAIL PROTECTED] wrote:
We have to distinguish between win16 and dos tests.
Absolutely. dos .com executables currently don't work,
but win16 .exe's with the same contents do work.
I plan to test DOS .com files using very simple pure assembly.
(That
As Andreas Mohr pointed out a while back,
http://www.winehq.org/pipermail/wine-devel/2005-August/039602.html
we really need a win16 test suite to make sure our
win16 support doesn't rot. As far as I know, nobody's
managed to get win16 tests into the tree, presumably
because the build process
