Wine automatically creates a C: drive for you on first startup. This is usually located in ~/.wine (although if you're using a commercial application bundled with Wine, it may have a different name).

When your home directory is located on a network (e.g. on an NFS server), performance can suffer if you run an application that makes large numbers of file accesses to the C: drive.

There are two ways to force the C: drive to really be located on a local drive. This will solve the performance problem. It has the disadvantage that you can only run Wine on the computer where the C: drive is stored.

One way to do this is to move ~/.wine to a directory on your local drive, and replace it with a symlink to the new directory. You can even do this before .wine is created.

Another way to do this is to move ~/.wine to a directory on your local hard drive, then set WINEPREFIX to point to the new directory.

• See "man wine" for more info about WINEPREFIX.

Apart from performance problems, you might encounter problems with .NET2.0 if your C: drive lives on a network, e.g. a "NFS System.IO.FileLoadException: Failed to grant minimum permission requests." failure.

The reason is that .NET2.0 by default considers everything coming from the network as possibly tainted. Usually you can issue something like "CasPol.exe -m -ag 1.2 -url file://... FullTrust" command to make e.g. your intranet trusted.

Unfortunately CasPol.exe is a .NET application and is living on C:, and hence is not trusted if that is served via NFS ... If you still want C: to be on NFS (despite the above mentioned performance penalty), the fix is to copy your CasPol.exe to a local directory (e.g. /tmp/), and use wine /tmp/CasPol.exe -m -ag 1.2 -url "file:///c:\\*" FullTrust