WINEPREFIX
From Wine-Wiki
Contents |
[edit] Introduction
a prefix holds a virtual windows with separate wine settings (drives, virtual desktop and so on)
Prefixes are set with the environment variable WINEPREFIX
so, for example, we can use
# export WINEPREFIX=$HOME/.wine-wow/ # winecfg # wine "D:\Setup.exe"
or
# WINEPREFIX=$HOME/.wine-wow/ wine "C:\Program Files\WoW\WoW.exe" -opengl
the upside now is that we can rm -rf ~/.wine-wow to uninstall that application. And the application doesn't install junk into our virtual windows, since we remove the whole Windows. Also, you can set special dlloverrides and such per prefix, which can come in handy rather often
This also comes in handy when testing software. You can create a temporary wine environment to play with and then erase it when you have finished.
[edit] Forum Comments
[edit] Symlinks
jan 09 bug 16779 vitamin: WINEPREFIX [has] to be a real directory. You can put it anywhere you want to, but WINEPREFIX env var has to point to a real directory. A user then said: i also tried symlinking just the drive_c folder and not the .wine. but Vitamin said: This is not supported either. That have to be a real directory as well. The symlink [belongs] under .wine/dosdevices. However A. Julliard: Having .wine or drive_c as a symlink works just fine. The problem is most likely with JFS. This was confirmed by the user: When symlinking drive_c to a directory within the /home mount (a seperate Ext3 formatted disk) there is no problem. Only when symlinking to JFS. I had this in my /etc/fstab:
- /dev/sda1 /jfs jfs user,relatime,errors=remount-ro 0 1
i changed it to:
- /dev/sda1 /jfs jfs relatime,errors=remount-ro 0 1
After removing the 'user' mount option, the bug disappears. [appears to be not a wine bug]
