I was just looking some information about this and I'm glad I found
this thread. I hope you don't mind me "reviving" an old thread.
I have the following question related to this:
-Can I use CrossOver Bottles directly under Wine? If not directly,
is it just a matter of changing a config file?
-The other way around: can I use Wine bottles directly under
Crossover?
Thanks in advance!
Hi there,
No problem with digging up an old thread -- always happy to go over things
again to add more detail 8)
To answer your first/2nd question, yes, however you should be careful to back
things up just incase something goes wrong, plus there's always the chance
that a different wine build may compromise the integrity of your crossover
bottle, particularly around the registry. For this reason I advise you clone
(Add duplicate) of your working bottle, and experiment with this first, before
committing any 'live' bottle to this process...
When using wine in linux, everything is typically installed into your homedir
.wine directory (~/.wine) -- you can influence this behavior by setting the
WINEPREFIX environment variable, so wine itself uses other locations. On the
other hand, with crossover every 'bottle' is equivalent to being it's own self
contained ~/.wine directory with a unique name, and we can install win32 apps
on a per bottle basis - not just into the same ~/,wine directory like wine does
by default. The obvious extension of all this, gives you a wine command of...;
WINEPREFIX="~/.cxgames/$bottlename/ wine "c:/Program Files/somedir/somefile.exe"
Replace the $bottlename variable with the actual name of the bottle you're working
with (without the $ symbol), but remember what I say - different wine builds -may-
change something in the bottle that crossover doesn't like. Experimentation and
checking is the only real way to work out if this is the case, and obviously will
not apply if you never launch the bottle with crossover-wine again 8)
As for you third question...and as somewhat explained above, wine pure doesn't
have bottles -- it typically just uses the single ~/.wine directory. I've had
limited/varying success with just copying the contents of ~/.wine into a freshly
prepared crossover bottle of the same windows version type -- other times I've
had better success doing that but not copying the wine equivalents of the windows
registry across (crossover will already have made it's own versions). Instead, check
with regedit (in wine pure) if the app installation itself added any keys to the
registry -- if it did, export those keys from regedit. Then you can start regedit
using the crossover 'Run command' option for that bottle, and import the required
registry keys into the crossover windows registry ... this avoids any mishmash should
there be any major differences in the registry layouts themselves.
Any win32 games that don't use the registry at all, it's just a matter of copying
the needed files into the crossover bottle - do not copy the ~/.wine registry files
across. Regardless of which method you use, you will need to create menu entries/short
cut for the app exe you copied from wine - again, use the 'Run command' option on
the bottle in question, and use the 'Create launcher' button to do this after you
navigate to the app exe itself.
Also...you might be interested in this - one of our advocates has written a utility
that allows linux users to switch between crossover releases and wine pure versions.
It is a handy little idea and more or less encompasses some of your goals perhaps?
Although I haven't tried it myself, you might want to give it a go...see;
http://random.zerodogg.org/wwine
Cheers!