Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Mark Roddy wrote: > There is actually an interface for reading/writing "extended attribute" data > on files that is supported by both FAT32 and NTFS, although the win32 API is > not present, so you would have to dive into the actual NT api (NtQueryEaFile > and NtSetEaFile.) These apis allow you to have named attribute data > associated with a file, which would be exactly what you want here. Of course > using undocumented interfaces has issues. That only works on NTFS... FAT32 has only a single byte for storing attribute data so couldn't do anything like that. Since NTFS has streams you don't gain anything. I only need the extra bit temporarily, so it doesn't get lost in eg. diff operations... persistently storing it on the client probably isn't worth the effort - NTFS actually has a permission called 'Execute file' buried in its ACL mechanism (cygwin reads it, for example) but the Win32 subsystem doesn't honour it. Tony -- Tony Hoyle <tmh at nodomain.org> Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917