WINEPREFIX
From Wine-Wiki
Contents |
Introduction
a prefix holds a virtual windows with separate wine settings (drives, virtual desktop, special dlls 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 because the application doesn't depend upon or install junk into any of our other virtual windows, we can safely remove the whole 'wineprefix' or Windows. Also, using winetricks 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.
Vitamin [nov 09] Everything goes under [the] directory specified in WINEPREFIX, including [wine's] registry. The only exceptions are the desktop and menu links. [i.e you can even specify a link to external drive]. However DeVince cautioned: be aware that if your external drive isn't formatted as ext3, some Windows applications might not work. But I myself haven't actually ever encountered this.
when you have a specific wineprefix and want to use it by default vitamin [nov09] you can this to your ~/.bashrc:
- export WINEPREFIX=/path/to/external/drive/.wine
Forum Comments
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]
