Running 16 bit builtin exes fails?

[Dan Kegel]

With Friday's git, I can't run the new winhelp.exe16.

$ cd programs/winhelp.exe16
$ wine winhelp.exe16.so
fails with
err:process:start_process
L"Z:\home\dank\wine32\programs\winhelp.exe16\winhelp.exe16"
doesn't have an entry point, it cannot be executed

Did I miss some memo?

This is on a 64 bit intel ubuntu 8.10 box, but wine was built as 32 bits.
- Dan

[Alexandre Julliard]

Dan Kegel  writes:
> With Friday's git, I can't run the new winhelp.exe16.
>
> $ cd programs/winhelp.exe16
> $ wine winhelp.exe16.so
> fails with
> err:process:start_process
> L"Z:\home\dank\wine32\programs\winhelp.exe16\winhelp.exe16"
> doesn't have an entry point, it cannot be executed
>
> Did I miss some memo?

Running those directly is not supported. Not that it would be of any use
anyway, but if you really want to, you can start it with 'wine winevdm
winhelp.exe'.

[Dan Kegel]

On Sun, Mar 8, 2009 at 10:13 AM, Alexandre Julliard  wrote:
> > $ cd programs/winhelp.exe16
> > $ wine winhelp.exe16.so
> > fails with
> > err:process:start_process
> > L"Z:\home\dank\wine32\programs\winhelp.exe16\winhelp.exe16"
> > doesn't have an entry point, it cannot be executed
>
> Running those directly is not supported. Not that it would be of any use
> anyway,

My goal is to integrate the win16 test suite; I was just trying
to run programs/winhelp.exe16 since that's the only "16 bit"
program we have so far.
> 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

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)?
- Dan

[Alexandre Julliard]

Dan Kegel  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.

[Saulius Krasuckas]

As many developers (Dan, Steven) already have mentioned this feature since 
2005..:

* On Sun, 8 Mar 2009, Alexandre Julliard wrote:
> - Dan Kegel  writes:
> > 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.

Would it be acceptable to use Open Watcom C compiler to crosscompile the 
16-bit part?  (v1.8 released two weaks ago)

[Dan Kegel]

On Sun, Mar 8, 2009 at 8:18 PM, Saulius Krasuckas  wrote:
> Would it be acceptable to use Open Watcom C compiler to crosscompile the
> 16-bit part?  (v1.8 released two weaks ago)

That's what win16test.googlecode.com already uses, though it uses
the windows version (as we had some problems using the linux
version as a crosscompiler; it's supposed to work, but didn't quite).

The other annoyance is that one still can't do "apt-get install watcom-c"
in ubuntu.  This is unlikely ever to be fixed in Ubuntu proper
because of licensing problems, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376431

Alexandre didn't like using the Windows version, see
http://wiki.jswindle.com/index.php/Coding_Hints:Test_Cases#Win16_test_and_th...
so if somebody wants to have another shot at using the Linux version
to cross-compile win16 problems, please do.   Then our configure
script can detect whether watcom is installed, and generate the
win16 tests if it is.

Alternately we could just use assembly to test win16 and dos, but that
would make it awful hard to port the existing win16 test suite.
- Dan