http://bugs.winehq.org/show_bug.cgi?id=17619
oiaohm oiaohm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |oiaohm@gmail.com
--- Comment #18 from oiaohm oiaohm@gmail.com 2013-11-13 20:43:45 CST --- Forest Hale and Frank Gore is wrong. C: does not report all the time as DRIVE_FIXED in all installs of Windows.
Microsoft Windows Preinstallation Environment (Windows PE) can have C: as other than DRIVE_FIXED. Yes remember Windows PE does CD forms and other forms. So fairly much everything C: can be reported as using Windows PE. Include the odd ball DRIVE_RAMDISK that we don't have the option to set in winecfg.
Forest Hale in newer versions of windows C: is always the drive where windows is installed. So if you order windows to install on D: when you boot up windows D: is now C:.
Now this brings us to the big problem here. Take Steam go read their documentation they don't recommend installing on network share and refuse to due to file locking issues. With steam you are meant to install to a local hard drive then copy installed files using steam backup to network share. This is instructions for Windows users of steam.
nfs is not without is locking issues. No one has asked the serous question is the safe to report to applications they are on a local drive when its really a network share. The answer is most likely its not safe.
One work around to this without requiring altering wine at all is http://alexeytorkhov.blogspot.com.au/2009/09/mounting-raw-and-qcow2-vm-disk-... Yes mount an image file from the nfs containing ext4. This is also coping how you are meant todo windows drive c. http://windowsdiskless.wordpress.com/
Correct way to fix this is not simple. Will require lot more test cases of disc io. Yes setting a nfs share to pretend to be local should require a set of checks to make sure the nfs share is sane to be used in this way. Like nfs can have nolock enabled and this makes nfs very much like running wine on ntfs or fat filesystems something we don't support. Yes we recommend image mounting on ntfs and fat as well to get local linux file-systems.
So I am really tempted to request this bug closed won't fix. As the fixes so far open up Pandora box of issues.
To fix properly requires alterations to winecfg to report if change is allowable by test cases checking for operational requirements. Sometimes drive c will just have to be other items other than DRIVE_FIXED because it will not be safe.
Automatically and blindly setting C: as DRIVE_FIXED has to be out. Wine refusing to create WINEPREFIX until its given somewhere that has features required for DRIVE_FIXED would be an option. This could also fix the fat and ntfs screw up issues. Since wine would also refuse to create.