DarWine & OpenGL

pinchies · Post by **pinchies** » Wed May 20, 2009 6:22 am

Hi,
For the past 3 months I have been trying to get wine working well, but have hit several obstacles.
I am on a Mac 10.5.7, using X11 2.3.3.2 from Xquartz, and using Kroneberg's Darwine builds.
The issues:
I can't seem to get OpenGL working or DirectX.
I sometimes have problems where I launch an exe, and the program runs as if it cannot "see" any other files in the same folder. This means some programs seem to not launch correctly.

Does anybody have a setup/config that they have tried on OS X where everything is working, and could they describe this to me?

Thanks.

pinchies

James Mckenzie · Post by **James Mckenzie** » Wed May 20, 2009 8:39 am

pinchies wrote about {Wine] DarWine & OpenGL

Hi,
For the past 3 months I have been trying to get wine working well, but have hit several obstacles.
I am on a Mac 10.5.7, using X11 2.3.3.2 from Xquartz, and using Kroneberg's Darwine builds.

One item, Mike builds for Tiger, not Leopard. I have built on Leopard and will, again, attempt to get the file uploaded to the same site that hosts Mike's builds.

The issues:
I can't seem to get OpenGL working or DirectX.

This is a shortcoming of OpenGL on Tiger (you cannot install XQuartz builds on Tiger from what I gather on the XQuartz site that has the OpenGL fixes and server updates.)

I sometimes have problems where I launch an exe, and the program runs as if it cannot "see" any other
files in the same folder. This means some programs seem to not launch correctly.

How are you launching the programs? Through a link or by changing to the install directory and then launching through Finder? The suggested method is to use terminal and then lauch using the wine <program.exe> command and this is outlined in the Wine FAQs as well.

Does anybody have a setup/config that they have tried on OS X where everything is working, and could
they describe this to me?

I've installed Fink and loaded the dependencies needed to build Wine. I then used Mike's build environment to build Wine on Leopard. I then installed it and ran Final Doom (which crashed with Mike's builds.) The program ran well once I set it up to use Windowed mode (it ran but was real ugly in full screen mode.)

Hope this helps solve your Wine on MacOSX difficulties.

James McKenzie

James McKenzie · Post by **James McKenzie** » Fri May 22, 2009 10:02 pm

pinchies wrote:

Hi,
For the past 3 months I have been trying to get wine working well, but have hit several obstacles.
I am on a Mac 10.5.7, using X11 2.3.3.2 from Xquartz, and using Kroneberg's Darwine builds.
The issues:
I can't seem to get OpenGL working or DirectX.
I sometimes have problems where I launch an exe, and the program runs as if it cannot "see" any other files in the same folder. This means some programs seem to not launch correctly.

You are going to have to 'roll your own' as Mike is still building for
Tiger (10.4.11) and I don't think that XQuartz 2.3.3 will install on
this platform. This would eliminate the need for his OpenGL 'hack' and
allow the full use of OpenGL functions currently supported by Wine.

Does anybody have a setup/config that they have tried on OS X where everything is working, and could they describe this to me?

I do. I have installed Fink to grab the Required Dependencies, I am
using the build env that Mike has so graciously supplied and I installed
and upgraded XCode from the Leopard DVD. You will also have to get the
X11 Software Development Kit (X11SDK) from the DVD and install it.
Mike's builds may not require the use of Fink or MacPorts to build, but
I had already installed Fink for OpenOffice.org X11 (I go WAY back on
that project.)

Please read through the Wine on MacOSX Wiki page for more information.

James McKenzie

pinchies · Post by **pinchies** » Sat May 23, 2009 5:10 pm

Thanks James, this helped a lot! I have more to try (I made a test 10.5.7 enviroment to play in), but first I have three questions:
1. is there any difference between the fink and macports builds?
2. can fink and macports be installed at the same time?
3. are you using leopard or tiger?

I also think that there is a bug in Xquartz somewhere, as with the latest build 2.3.3.2 sometimes the $Display variable changes randomly, resulting in wine complaining of errors that it cant find the screen.

***I also have one final problem - and I have checked the FAQ.

***
Some programs complain that their resources are missing, and seem to be looking in "winehelper.app/contents/resources/" instead.
This error is mentioned here:
http://forum.winehq.org/viewtopic.php?t=4614
Is there a solution you know of?

pinchies · Post by **pinchies** » Tue May 26, 2009 8:26 am

Thanks Felix.

I won't do it again!

felix · Post by **felix** » Tue May 26, 2009 10:29 am

On Tue, May 26, 2009 at 08:26:12AM -0500, pinchies wrote:

I have edited my last post with further Darwine/wine questions.
Thanks,
pinchies

Since the forum is tied to the mailing list this is the wrong thing to
do. It will not resend edited posts to the mailing list so anyone that
just uses the ML and not the forum will not see your additional
questions.

Recommend you add them in a separate reply to your original question.

--
Darragh

"Nothing is foolproof to a sufficiently talented fool."

pinchies · Post by **pinchies** » Wed May 27, 2009 2:56 am

*reposting my current unsolved problems:

I think that there is a bug in Xquartz or winehelper somewhere, as with the latest build 2.3.3.2 sometimes the $Display variable changes randomly, resulting in wine complaining of errors that it cant find the screen. Wine used to crash occasionally, but it would never give this error, and would normally reconnect back to X11 easily.

"Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly."

I can bypass this error by using "$ var" and putting the $display manually into winehelper.

***I also have one final problem - and I have checked the FAQ. ***
Some programs complain that their resources are missing, and seem to be looking in "winehelper.app/contents/resources/" instead.
This error is mentioned here:
http://forum.winehq.org/viewtopic.php?t=4614
Is there a solution anyone knows of?

ryan woodsmall · Post by **ryan woodsmall** » Wed May 27, 2009 6:33 pm

The DISPLAY changing is not a bug. When Xquartz restarts (or starts
as a different user), a new socket is created in /tmp/launch-XXXX/:0,
where XXXX is random.

**
rbwmb:~ ryan$ echo $DISPLAY
/tmp/launch-cPFfik/:0
**

Are you setting DISPLAY manually somewhere? If you are, don't.
launchd should take care of all that for you.

Regarding the other error: roll your own, compile Wine from source and
circumvent the Darwine setup. Not nearly as nice (no winehelper.app),
but you'll get more help from the forums.

ryan woodsmall
[email protected]

"Be well, do good work, and keep in touch." - Garrison Keillor

On May 27, 2009, at 2:56 AM, pinchies wrote:

*reposting my current unsolved problems:

I think that there is a bug in Xquartz or winehelper somewhere, as
with the latest build 2.3.3.2 sometimes the $Display variable
changes randomly, resulting in wine complaining of errors that it
cant find the screen. Wine used to crash occasionally, but it would
never give this error, and would normally reconnect back to X11
easily.

"Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set
correctly."

I can bypass this error by using "$ var" and putting the $display
manually into winehelper.

***I also have one final problem - and I have checked the FAQ. ***
Some programs complain that their resources are missing, and seem to
be looking in "winehelper.app/contents/resources/" instead.
This error is mentioned here:
http://forum.winehq.org/viewtopic.php?t=4614
Is there a solution anyone knows of?

James McKenzie · Post by **James McKenzie** » Wed May 27, 2009 10:26 pm

ryan woodsmall wrote:

On May 27, 2009, at 2:56 AM, pinchies wrote:

*reposting my current unsolved problems:

I think that there is a bug in Xquartz or winehelper somewhere, as
with the latest build 2.3.3.2 sometimes the $Display variable changes
randomly, resulting in wine complaining of errors that it cant find
the screen. Wine used to crash occasionally, but it would never give
this error, and would normally reconnect back to X11 easily.

"Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set
correctly."

I can bypass this error by using "$ var" and putting the $display
manually into winehelper.

Don't do this. This causes all sorts of problems as the display will
change, for security, on Leopard whenever X is restarted.

The problem appears to be that you are starting the program outside of
its directory. You stated that you are using the Winehelper application
to start your programs or are you using terminal and starting them from it?

Regarding the other error: roll your own, compile Wine from source and
circumvent the Darwine setup.

Depends. I do use Winehelper and I have several problems, but they are
not related to the use of this program as the programs also do not run
from terminal. I'm working on them to see what is wrong, but I suspect
one program still has Win16 code somewhere and that will cause all sorts
of problems, including the inability to run on a 64 bit system with Vista.

Not nearly as nice (no winehelper.app), but you'll get more help from
the forums.

Hmm. I'm still here, and I help. However, Winehelper is a dead product
(at least as far as I can tell) and Mike is working on a replacement due
to his furstration with it.

ryan woodsmall
[email protected]

pinchies · Post by **pinchies** » Fri May 29, 2009 10:03 am

The error is not so much the $display changing, it was winehelper not being able to reconnect. The workaround was also only a temporary one, to avoid a reboot, which seems to fix the problem.

I will have a go at compiling from source when I have time, it sounds like it fixes quite a few common problems.
Thanks for your help guys.
I will keep trying.

Thunderbird · Post by **Thunderbird** » Fri May 29, 2009 11:43 am

I'm seeing the same issue with the Display variable. In my case I'm just launching Wine from the menu and let e.g. winehelper launch programs. The app I'm working on still crashes frequently on the Mac and when I try to restart the (it shows a nice backtrace in the error) I get the mentioned error. Quitting winehelper and restarting the Xserver fixes the issues.

Roderick

James Mckenzie · Post by **James Mckenzie** » Fri May 29, 2009 11:55 am

Thunderbird <[email protected]> wrote about [Wine] Re: DarWine & OpenGL

I'm seeing the same issue with the Display variable. In my case I'm just launching Wine from the menu and let e.g. winehelper launch programs. The app I'm working on still crashes frequently on the Mac and when I try to restart the (it shows a nice backtrace in the error) I get the mentioned error. Quitting winehelper and restarting the Xserver fixes the issues.

Does the X server crash as well? This may be why wineserver cannot start the program a second time. Thus you have to restart wineserver to pick up the new DISPLAY location. Again, the change in location is a security feature.

James McKenzie

Thunderbird · Post by **Thunderbird** » Fri May 29, 2009 1:19 pm

The Xserver stays around I think (I had to kill it explicitly by tabbing to it and then closing it). I can check again next week when I'm back behind the mac.

James Mckenzie · Post by **James Mckenzie** » Fri May 29, 2009 1:39 pm

Thunderbird wrote about [Wine] Re: DarWine & OpenGL

The Xserver stays around I think (I had to kill it explicitly by tabbing to it and then closing it). I can check again next week when I'm back behind the mac.

Then the DISPLAY variable should stay the same. While you are back behind the Mac, open a second terminal session and cd to the /tmp directory. When the program crashes, refresh the directory. See if the directory created by X disappears or changes. This should not happen and needs to be reported as a bug to both Apple and the XQuartz folks for resolution.

James McKenzie

Thunderbird · Post by **Thunderbird** » Wed Jun 03, 2009 1:42 pm

I have been doing some experimenting and at this point I can't reproduce the issue. How is wine receiving the DISPLAY variable? I tried launching apps using Finder (it uses winehelper). I guess this tool is somehow providing wine 'sessions' with the DISPLAY variable?

Is anyone using wine from source on osx? I would like to just use the darwine build scripts and then use my own wine dev tree and launch apps from the console or so. By default a lot of libraries can't be found that way. I guess I should install the needed libs in a directory which is in the library path and then run wine.. Not sure what the best way on OSX is yet (I'm a Linux user and have to use OSX for some app now).

Roderick