d'Oh! 3650132. If FCP were testing the bSupports2TBFiles bit, which VOP/VFS interface would the Carbon File Manager be using to ask us the answer? I'd like to put the code in now so that it will all just work when FCP/CFM are fixed. Thanks Quinn, Sam On 11/05/2004, at 3:00 PM, darwin-kernel-request@lists.apple.com wrote: Hmmm, I think that there are least two issues here. For a start, FCP (or whatever underlies it) should determine whether a volume supports large files by testing the bSupports2TBFiles bit in the vMExtendedAttributes field of the GetVolParmsInfoBuffer returned by the Carbon File Manager routine PBHGetVolParmsSync. However, it doesn't look like it's doing this (because of the next point). I'd consider that a bug. Second, it seems that the Carbon File Manager sets this flag based on a simple volume identifier check. If the volume is original HFS, it clears the flag, otherwise it sets it. This is a bug IMHO. The Carbon File Manager should not contain hard-wired special cases for particular file systems. You know the drill... <http://developer.apple.com/bugreporter/> Please send me the bug numbers. _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.