Originally Posted by
Phaze08
SO your saying I need to make a separate folder for WoW and just tell it to run from there?
Wow fortunately operates needing only it's installed directory and none else therefore it's not going to complain it's missing something if you move it around. So here's a useful tip for wow directory management when messing with various wine versions and prefixes.
Using symbolic linking, you can put WoW directory anywhere and just link it into the "drive_c" in a .wine prefix folder. Wine will see just like it was physically located there, and if you delete the prefix your wow directory is unaffected. I do this because I accidentally deleted the wrong prefix once and it took my wow install with it.
For example linked from another drive:
Code:
/home/<username>/.wine/drive_c/Wow --> /media/sdd1/Wow
Then the launch command is simply:
Code:
wine "C:\Wow\Wow.exe"
Or linked to prefix ".wine-wow":
Code:
/home/<username>/.wine-wow/drive_c/Wow --> /media/sdd1/Wow
Then use launch command:
Code:
env WINEPREFIX="/home/<username>/.wine-wow" wine "C:\Wow\Wow.exe"
(Search if you want to do the cmd line way)
Creating symbolic links in file manager:
- Hit F3 for 2 pane mode
- Ctrl-H to unhide . directories
- Browse to the two directories
- ctrl-shift drag directory link from one to other
I have used symlinking to run wow off a separate small solid state drive (fast loading) or usb drive (portability). You can even link to *cough* wow installed on ntfs windows partition (worked but I experience long pauses in loading/exiting).
So in conclusion; say you borked your wine install tweaking the registry or installing DX/IE9 something another. Rename or delete the prefix directory, run wine to recreate clean prefix, relink Wow to drive_c and done.
Bookmarks