CrossOver Support - Community Forums

hey,

I was wondering if there is any low level conflict in running both crossover games and wine 1.1.34 (macports) on the same machine (apple aluminum macbook). I have still to encounter any issues, but what I have in mind is common applications, like for instance steam. I do use a separate wineprefix for every app I'm running under wine-devel, but still, should I expect by default some things going crazy?

regards,
mihai

No - they will play fine with each other.

In fact regarding Steam I can attest to the fact you can run the same exact install with both Wine & CXGames (at different times). I do this so I do not have to have 2 copies of my 80gigs of Steam games :)

~Jeff

hey Jeff,

good to know, thank you.
As a side issue, do you happen to run Oblivion under wine 1.1.34 on a mac? I'm getting a d3dx9_27.dll error, although I did use the recommended override (this is with the steam game of the year version of Oblivion). funny thing, the bugger works under crossover games 8.1.2, but performance is not something to be desired, even after changing a few things in Oblivion.ini.
I know full well that the 9400 is not exactly the best of GPU's, but I do run Fallout 3 under wine on this machine quite well, so I was hoping that Oblivion should not pose a problem.

regards,
mihai

hey,

I guess this question goes for Jeff or whomever has some knowledge of this....
is there a way to use a wineprefix (wine-devel installed with macports) as a crossover games bottle? By extension, can you archive a wine prefix such that it can be used by crossover games? I should mention the machine is a mac running 10.6.2 SL.

regards,
mihai

You can add CXBOTTLE=(path) to the command line which is the equiv of WINEPREFIX. Otherwise you could copy your ~/.wine to ~/Library/Application Support/Crossover/Bottles and change the name to something without the . in it and Crossover may see it as a bottle you can run against. From what I understand Crossover will recreate its own .conf files, but it should use the same .reg files and the drive_c path.