Dan Kegel dank@kegel.com writes:
but if you really want to, you can start it with 'wine winevdm winhelp.exe'.
Tried that just now:
~/wine32/programs/winhelp.exe16$ ~/wine32/wine winevdm winhelp.exe16.so winevdm: can't exec 'Z:\home\dank\wine32\programs\winhelp.exe16\winhelp.exe16.so': invalid program file
Use winhelp.exe, not winhelp.exe16.so.
Also, I was hoping we really had a solution for building 16 bit executables, but objdump reports that it's all 32 bit code. Should it still be possible to write win16 tests with this infrastructure (lightly extended, if needed)?
No, it's not possible. We don't have any way of building 16-bit code with gcc. All 16-bit stuff in Wine is actually 32-bit code, with functions explicitly suffixed with '16' etc. You can't possibly build real 16-bit apps this way.