http://bugs.winehq.org/show_bug.cgi?id=17619
--- Comment #13 from Forest Hale lordhavoc@ghdigital.com 2009-12-10 22:57:15 --- (In reply to comment #12)
(In reply to comment #11)
Since C:\ cannot ever be a network share in Windows
Is this still the case for XP/Vista/7 which allow drive remapping? (I've seen XP systems that have L: %SYSTEMDRIVE% or whatever it's called.)
The perspective I take on this is: the default wine install should never cause users unnecessary pain - it should enforce that the C: reports as DRIVE_FIXED, how this is done is less important.
The underlying problems cause the user's settings in winecfg to be ignored, causing problems for any user attempting to force the type of additional drive mounts, but the common manifestation of this for users is C: not being DRIVE_FIXED.
It is important to note that winecfg does not allow the user to modify the type of the C: drive, and registry modification in its place is not a compelling argument, at least to me.
For this reason I assert that C: is always DRIVE_FIXED, unless the user tirelessly pursues an unnecessary approach.
But pursuing this line of thinking, I think we can break this down to a few questions that could be answered on a test system: 1. When the OS is installed to D: on a partition setup with two NTFS partitions (respectively C: and D:), is it possible to delete the C: partition? 2. If the C: partition is deleted, can a new network mount be made as C: ? 3. If the C: partition is deleted and a network mount made as C:, what drive type does it report as?
Then the question is whether the discovered behavior would be appropriate for Wine, considering that it creates its own install under much more ideal conditions than a real OS has to contend with.