http://bugs.winehq.org/show_bug.cgi?id=23095
--- Comment #3 from Alexander Scott-Johns alexander.scott.johns+winebug@googlemail.com 2010-06-10 14:01:44 --- (In reply to comment #1)
Did you try running "winetest.exe mscvrt:file" on a Windows box and see what the results are (default output is somewhere in your %TMP% directory) ?
I have Windows 95 installed in a VM, but for some reason it doesn't recognise mounted floppy disk images (it did before; not sure what broke). Is there another way to get data into a VM image in VirtualBox? I don't want to reinstall it as stock Win95 doesn't even come with msvcrt.dll.
Also, how do you build winetest.exe or msvcrt_test.exe? In programs/winetest, "make winetest.exe" produces a shell script. In dlls/msvcrt/tests, "make crosstest" fails to link ("cannot find -lwinecrt0").
(In reply to comment #2)
Let me answer my own question:
C:\wct>msvcrt_test.exe printf printf.c:844: Tests skipped: _vscprintf not available printf.c:871: Tests skipped: _vscwprintf not available printf.c:902: Tests skipped: _vsnwprintf_s not available printf: 354 tests executed (0 marked as todo, 0 failures), 3 skipped.
C:\wct>d:\winetest.exe msvcrt:printf -o res C:\wct>type res .... .... Test output: msvcrt:printf start dlls/msvcrt/tests/printf.c - printf.c:844: Test failed: _vscprintf not available printf.c:871: Test failed: _vscwprintf not available printf.c:902: Test failed: _vsnwprintf_s not available printf: 357 tests executed (0 marked as todo, 3 failures), 0 skipped. msvcrt:printf done (3)
Why do these behave differently? Doesn't the latter just extract msvcrt_test.exe and run the former?