Jeremy White wrote:
> Actually, it's a fascinating problem - I've been bit by it, badly.
>
> Wine works fine with a Win4lin kernel, so long as you build
> it from source. If you try to take a binary built on a non
> Win4lin kernel, you get an unhandled exception when your
> app starts to run, with a problem in the ThunkConnect32 area.
>
> Similarly, if you take a binary that you built on your Win4lin
> kernel, and give that binary to someone on a non Win4lin kernel,
> they see the exact same problem.
>
> So, it works with Win4lin, sorta.
>
> Jer
>
Ah, so that explains why I haven't seen this problem then, because I always
build from source. Hmm, come to think of it, that'd make it kind of hard
for me to make a wine package usable by anyone else.
Do you happen to know WHY this problem shows up??? I don't believe it has
anything to do with kernel headers, since I am using kernel headers from
2.4.0testXX (ala RedHat 7.0) even though I am running a customized version
of 2.2.18pre17 (http://www.thecomputerbuilder.com/~dfe/linux/kernel_RPM/).
So theoretically I should be hit really hard by the problem if it was the
headers.
In any case, a message by Richard Bass ([EMAIL PROTECTED]) says that they
are fixing the problem. I just wish they'd go ahead and release a fixed
kernel patch right now rather than wait for all the different kernels to
build. I could have it in my kernel RPM in about 5 minutes then go worrk on
Wine while I'm waiting for it to build. ;-)
-Dave
P.S. cced this back to the win4lin-beta list as this could be informative
for people on that list.
