Hi all I'm trying to play the game "BOH" (http://www.bohthegame.com/) on OS X using Darwine. I downloaded 1.1.19 and dragged the Darwine folder to /Applications. Then I opened the BOH installer using WineHelper and installed the game. For some reason it put the installed files inside the WineHelper application bundle. When I tried to open the game's executable using WineHelper, it appeared in the Process Window then disappeared again, with no information entered in to the Wine Log. I tried moving the game's folder to ~/.wine/drive_c/Program Files/, but I still had the same problem. The game is written using SDL and I'm wondering whether this is part of the problem. Any ideas anyone? TIA
I tried setting WINEDEBUG to +all and running the game. Without this setting, the process ran for just a few seconds before quitting. With WINEDEBUG set to +all, it ran for several hours generating loads of entries in the log. The RAM usage ran to several GB. When I came back to it after dinner WineHelper had crashed. Is there a lower level of debugging I could use which will give me the information I need without taking so long and eventually killing WineHelper? I read this page (http://www.codeweavers.com/support/docs/wine-user/x2194) but I don't know which options will give me the information I need.
motorollin <wineforum-user at winehq.org> wrote on April 23rd:> >Ok, running from the command line from the directory in which the application is installed gets me further: > >$ cd ~/.wine/drive_c/Program\ Files/BOH/ >$ /Applications/Darwine/Wine.bundle/Contents/bin/wine BOH.exe > >This causes a window to open with the title "SDL_app". The game does run in a window, but doesn't have SDL_app as the window title. The window is completely black, the keyboard has no effect, and the title music doesn't play. So the game doesn't seem to get further than opening its window. > >The game does run under Wine in Ubuntu, so I'm really confused about what's going on! >Again, and again...OpenGL is BROKEN on any Mac. This means that MOST games that rely on OpenGL 1.3 functions will not run. If you start this game in a terminal window, like you did, you should see a line about broken OpenGL functionality. You have three courses of action: 1. Get Crossover Games for Mac ($$$$) 2. Wait until XQuartz 2.3.3 is released which will ship with fixes and incorporation of OpenGL 1.3 functions (time). 3. Ping the programs author to create a Mac specific version of the game. (not likely but possible.) Your choice at this point. James McKenzie
Thanks for your reply. James Mckenzie wrote:> > Again, and again...OpenGL is BROKEN on any Mac. This means that MOST games that rely on OpenGL 1.3 functions will not run. If you start this game in a terminal window, like you did, you should see a line about broken OpenGL functionality.I don't think that's it. I don't think this game uses OpenGL, and I get no warning about it if I run from the terminal. James Mckenzie wrote:> > You have three courses of action: > 1. Get Crossover Games for Mac ($$$$)It does exactly the same thing in Crossover Games :( James Mckenzie wrote:> > 3. Ping the programs author to create a Mac specific version of the game. (not likely but possible.)Actually, the author is quite open to the possibility. I am just looking in to an alternative just in case.
austin987 wrote:> > 4. Use the XQuartz beta/rcIs that this? http://xquartz.macosforge.org/trac/wiki/X112.3.2.1 Do I just download and install that and then use Darwine as normal?
Well, I installed XQuartz, reinstalled the game using Darwine from the command line, ran the game from the command line, and it worked. The game hung when I tried to actually start a game, so I restarted the whole machine thinking perhaps the different versions of X11/Xorg and Wine were getting muddled. When I tried to launch the game again, same black screen problem :?
Thanks Ryan. Sadly no demo available. I have just installed rc5 of XQuartz but it made no difference (same black window). Just to check I'm doing it right, do I just install the XQuartz package then do this: $ cd ~/.wine/drive_c/Program\ Files/BOH/ $ /Applications/Darwine/Wine.bundle/Contents/bin/wine BOH.exe Is it worth trying the final XQuartz 2.3.3, or is it unlikely to make any difference?
@ryan I have just downloaded the wine-1.1.19. They compiled, built and installed successfully on my Leopard MacBook straight away. I ran winecfg, then ran BOH with that version of Wine. The game ran successfully and I saw the menu and heard the title music. I was able to configure the controls, but when I tried to start a game it froze. I have tried this several times with the same effect each time. There are lots of errors in the terminal window saying things like "err:font:XFONT_BuildMetrics failed to load -misc-thonburi-medium-r-normal--100-*-100-100-p-0-koi8-r", and finally "Font metrics: 100.0% done". There are no further messages after this point :?
Did you just run a "./configure" and then make and install Wine, or
did you specify any options? Wine is in your path, correct - /usr/
local/bin by default? If you could, try to start it with:
export DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib"
cd ~/.wine/drive_c/path/to/game
wine programname.exe
Does that get you any further?
ryan woodsmall
rwoodsmall at mac.com
"Be well, do good work, and keep in touch." - Garrison Keillor
On Apr 24, 2009, at 3:15 AM, motorollin wrote:
> @ryan
> I have just downloaded the wine-1.1.19. They compiled, built and
> installed successfully on my Leopard MacBook straight away. I ran
> winecfg, then ran BOH with that version of Wine. The game ran
> successfully and I saw the menu and heard the title music. I was
> able to configure the controls, but when I tried to start a game it
> froze. I have tried this several times with the same effect each time.
>
> There are lots of errors in the terminal window saying things like
> "err:font:XFONT_BuildMetrics failed to load -misc-thonburi-medium-r-
> normal--100-*-100-100-p-0-koi8-r", and finally "Font metrics:
100.0%
> done". There are no further messages after this point :?
>
>
>
>
>
I just did ./configure then make and install. I used a guide on how to compile Wine on OS X Tiger (I'm using Leopard though) and that was pretty much all it said, apart from satisfying dependencies. My path is as follows: /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Does that look ok? I have deleted the version I compiled myself to try another one, so will recompile it and try what you suggested. Also, could you confirm I'm using the correct sources? I downloaded from here: http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=77449 When that didn't work, I tried using the Darwinports version, but that just gave me the good old black screen again.
ryan woodsmall wrote:> > As far as dependencies, SDL might or might not be using some image > libraries in the background. I normally grab FreeType, jpeg, tiff, > libpng, libxml2 and libxslt, then compile those, THEN build Wine > against those libraries. This is a relatively involved process, of > course...Ok, I'll try to build those libraries first. Would you be able to tell me the correct parameters to configure Wine? I really don't get configure ;) ryan woodsmall wrote:> > If you're building from MacPorts, make sure you're using the "wine- > devel" package. And before you do anything, make sure MacPorts itself > is up-to-date: > > sudo port -v selfupdateYep, I updated before I installed it. ryan woodsmall wrote:> > Note that MacPorts places itself at the beginning of your PATH, so > binaries in /opt/local (or wherever you install it) are used before > system binaries. That behavior can be changed in ~/.bash_profile or > equivalent.I found the binaries in /opt/local/bin, but as I said it didn't work. I (perhaps stupidly) installed MacPorts 'wine' first, then when that didn't work removed it and used MacPorts 'wine-devel'. Could that be why it didn't work?
motorollin <wineforum-user at winehq.org> wrote on April 24th:> > >ryan woodsmall wrote: >> >> As far as dependencies, SDL might or might not be using some image >> libraries in the background. I normally grab FreeType, jpeg, tiff, >> libpng, libxml2 and libxslt, then compile those, THEN build Wine >> against those libraries. This is a relatively involved process, of >> course... >One suggestion: Grab the build environment from Mike Kronenberg. It includes all of these libraries and then you can build against XQuartz 2.3.3. BTW, Wine 1.1.20 was released today as well. James Mckenzie
@ryan Any chance of a quick run-through of how you compiled it? TBH anything beyond './compile', 'make' and 'make install' is beyond me. I'm willing to learn, but there comes a point where I just want it working [Wink]
James McKenzie wrote:> > As Ryan stated, you have to follow the instructions.The only instructions I can find are the README in wine-1.1.19. This basically states that you have to run tools/wineinstall, and that you need XCode >= 2.4 to compile properly on a Mac. I have done all this but it still doesn't work. Are there some more instructions I should be looking at? I'm still confused about the business of linking to XQuartz. Do I need to tell it to do that, or will it happen automatically? James McKenzie wrote:> > I use Mike > Kronenberg's build environmentIs that from http://www.kronenberg.org/darwine/ ? All I can find there is binaries. James McKenzie wrote:> > There are several fixes out > for video problems on the Mac with Wine.Again, I have no idea how these should be incorporated in to a build of Wine. James McKenzie wrote:> > One suggestion, can you try using CrossOver Office for Mac with this > game? I found that dOOm would not runn very well on CrossOver Game for > the Mac 7.1.I have tried the latest versions of Crossover Mac and Crossover Games but both have the same problem.
Ah, thanks! Is there any benefit to building that myself, or is it likely to perform the same as the binary? Also, do I have to do anything to make it build against XQuartz, or will that happen automatically?
Please see this thread: http://forum.winehq.org/viewtopic.php?p=23659#23659 as this problem appears to have extended beyond the original question to a different issue, so I have started a new thread.
motorollin wrote:> Ah, thanks! Is there any benefit to building that myself, or is it likely to perform the same as the binary? Also, do I have to do anything to make it build against XQuartz, or will that happen automatically? >Wine should build against the version of X11 that you are using. You will have to rebuild it after installing XQuartz 2.3.3 to enable any new features in that release. James McKenzie