2009/4/6 Austin English austinenglish@gmail.com:
On Sun, Apr 5, 2009 at 4:51 PM, James McKenzie jjmckenzie51@earthlink.net wrote:
Austin English wrote:
See http://bugs.winehq.org/show_bug.cgi?id=17938 for background.
Sent reply direct to Austin. This may be outside of Wine's control due to flaky NTFS support by some Linux distributions.
No, it's unrelated.
Previously, we reported the file system type to be NTFS for hard disk mounts. Now we report the file system to be UNIXFS, because, e.g., the .Net 2.0 installer tries to do NTFS specific stuff on the disk, and with UNIXFS (which it doesn't recognize), it doesn't. The problem is some other apps DEPEND on seeing NTFS to work, e.g., Total War (downloading the demo now to test), and in the case of this bug, DVD Shrink. It's not using any NTFS specific features, and it's not using a 'real' NTFS mount through NTFS-3G.
If I interpret it correctly, the user reporting bug 17938 is trying to use a native NTFS filesystem with Wine, which we already know is a bad idea :)
But his bug raises an interesting issue. If an application has sanity checks on FAT32 vs NTFS (e.g., I need a 4GB file ... I've detected no NTFS therefore it's FAT32 which doesn't support more than 2GB files), then we might just have to make this configurable, possible on a per-app basis.
My suggestion is a drop-down box in the "Advanced" tab of "Drives" to control filesystem type (separate from disk type, as is suggested in Comment #7 on 17938). It shouldn't be important for floppies or even CD-ROMs, but the options could be: - Default (autodetect, fall-back to unixfs) - FAT12 (floppies) - FAT16 - FAT32 - NTFS (probably don't need different versions on NTFS) Possibly restrict these to CDROM type: - ISO9660 - UDF
Unless someone can come up with a better default than unixfs :)