I've written a hands-on book about FAT12 — reading, writing, formatting, directory creation, deletion, renaming, even porting the library into a kernel. ~1500 lines of C across 11 chapters, with all code listings in the book.
Content is complete, but I want to polish and improve it before the final release. I'm looking for beta readers — especially OSDev hobbyists who are implementing or plan to implement file systems.
If you're interested:
- Reply to this thread saying you're in
- I'll DM you a free Leanpub coupon (lifetime access)
- Read through and give me honest feedback — what's unclear, what's missing, what could be better
- No deadlines, no minimum word count
This book targets the OSDev hobbyist who knows some C and wants to understand FAT12 inside out.
Reply here if you're interested!
Beta readers wanted: FAT12 book (complete, looking for feedback)
-
thewrongchristian
- Member

- Posts: 472
- Joined: Tue Apr 03, 2018 2:44 am
Re: Beta readers wanted: FAT12 book (complete, looking for feedback)
Yeah, I'll bite.bjoerndev wrote: ↑Fri Jun 05, 2026 1:46 pm I've written a hands-on book about FAT12 — reading, writing, formatting, directory creation, deletion, renaming, even porting the library into a kernel. ~1500 lines of C across 11 chapters, with all code listings in the book.
Content is complete, but I want to polish and improve it before the final release. I'm looking for beta readers — especially OSDev hobbyists who are implementing or plan to implement file systems.
If you're interested:
- Reply to this thread saying you're in
- I'll DM you a free Leanpub coupon (lifetime access)
- Read through and give me honest feedback — what's unclear, what's missing, what could be better
- No deadlines, no minimum word count
This book targets the OSDev hobbyist who knows some C and wants to understand FAT12 inside out.
Reply here if you're interested!
My first feedback prior to even reading anything is to remark about the usefulness of FAT12. Will the book include FAT16 and/or FAT32? Long File Names?
I ask because FAT12 is useful only for devices with up to 4,084 clusters, more clusters requires FAT16. That's a limit of around 2MB with a cluster size of 512 bytes.
Re: Beta readers wanted: FAT12 book (complete, looking for feedback)
I'm in. I need to learn and research this content, and try to write it myself.
Last edited by opensky on Mon Jun 08, 2026 5:04 am, edited 1 time in total.
Re: Beta readers wanted: FAT12 book (complete, looking for feedback)
Thanks to both of you for signing up! Check your DMs — I've sent each of you a free Leanpub coupon (lifetime access, no strings attached).
@thewrongchristian — Good question about scope. LFN gets a short overview in chapter 3 (what it is, why 0x0F is the sentinel, and the basic idea of UTF-16 fragments chaining backward), but the code just skips those entries — the focus stays on core FAT12. If interest is high I may add LFN coverage before the final publish. The book also has a "FAT Family" section in every chapter explaining what changes for FAT16 and FAT32.
To both of you: Please don't hesitate to tell me if something is unclear, wrong, or missing — or if you just plain don't like something. No need to soften it. The whole point of beta readers is to catch what I can't see myself, so honest feedback (even harsh) is exactly what I need. No deadlines, no minimum word count — read at your own pace and fire away whenever something comes up.
Thanks again, and happy hacking!
@thewrongchristian — Good question about scope. LFN gets a short overview in chapter 3 (what it is, why 0x0F is the sentinel, and the basic idea of UTF-16 fragments chaining backward), but the code just skips those entries — the focus stays on core FAT12. If interest is high I may add LFN coverage before the final publish. The book also has a "FAT Family" section in every chapter explaining what changes for FAT16 and FAT32.
To both of you: Please don't hesitate to tell me if something is unclear, wrong, or missing — or if you just plain don't like something. No need to soften it. The whole point of beta readers is to catch what I can't see myself, so honest feedback (even harsh) is exactly what I need. No deadlines, no minimum word count — read at your own pace and fire away whenever something comes up.
Thanks again, and happy hacking!