exFAT notes
Posted: Mon Aug 09, 2010 4:31 am
Some small notes for a to-be-written exFAT wiki page:
- exFAT uses 32-bit FAT entries.
- When a file in exFAT has it's "no-fat-entries" bit set, assume they'd all be consecutive.
- Block allocation bitmap is leading over the FAT.
- FAT is still used for what it did before.
- There's a boot area of 24 sectors containing two large boot blocks of 12 sectors each.
- There's usually only one FAT that's mostly unfilled (because of that no-fat-entries bit).
- Using this information within a place where Microsoft holds its patents on this stuff is probably illegal. I don't live in such a place so I have no problem with using this information. The only reason I'd like to support exFAT is for interoperability with a future video camera or photocamera.
There's an awesome reverse engineering by a forensic examiner to be found at
http://www.google.com/url?sa=t&source=w ... 6q_7CRkmuQ
Also found if you google for "exfat reverse engineer".
- exFAT uses 32-bit FAT entries.
- When a file in exFAT has it's "no-fat-entries" bit set, assume they'd all be consecutive.
- Block allocation bitmap is leading over the FAT.
- FAT is still used for what it did before.
- There's a boot area of 24 sectors containing two large boot blocks of 12 sectors each.
- There's usually only one FAT that's mostly unfilled (because of that no-fat-entries bit).
- Using this information within a place where Microsoft holds its patents on this stuff is probably illegal. I don't live in such a place so I have no problem with using this information. The only reason I'd like to support exFAT is for interoperability with a future video camera or photocamera.
There's an awesome reverse engineering by a forensic examiner to be found at
http://www.google.com/url?sa=t&source=w ... 6q_7CRkmuQ
Also found if you google for "exfat reverse engineer".