"It just works!"

Developers are often surprised that FullFAT just works!

Ubiquitous. Almost every user OS includes FAT support.

Transparent to your end user, everyone can use FAT.

Portable from the Ground-up

FullFAT was always intended to be 100% portable. You won't have to hack routines for it to work on your system. FullFAT will simply compile (usually cleanly) and just work!

Endian Independent Architecture (no assumptions made).
No assumptions made about memory alignment, or access restraints.
Makes no assumptions about the underlying OS services, or their availability.
No critical regions.
Object based code design.
100% ANSI C code.

Tested Architectures

FullFAT is known have been tested and work on projects using the following architectures:

ARM
Atmega
Atmel
AVR
Blackfin
Fujitsu
Renasas (Hitachi Micro-controllers)
Intel x86 / x64

It has also been ported sucessfully to a custom designed CPU for a gaming platform.

Easily Integrated

FullFAT can be easily integrated in almost any platform or framework. Here's a list of projects or OS's that are currently using FullFAT, or integrating it.

BlackSHEEP from Bluetechnix
ReactOS - The open-source Windows clone.
Renesas Developer Libraries

Aleksey Bragin, one of the lead developers of ReactOS claims to have developed a working proto-type Windows Filesystem driver based on FullFAT in 2 days. (See their newsletter).

Take the Stress Away

Because of FullFAT's layered architecture, including it in your project is simple and stress-free. FullFAT exposes a standard-IO (STDIO.H) like API that you're development team are already familiar with. FullFAT lends itself to be integrated into other frameworks and OS's. As such it can easily be integrated into the stdio interface.

We are often told by developers that they we're completely surprised that FullFAT just works first time. Feedback has shown that integration is straight-forward, and few issues occur. Many issues tend to come from layers below or above FullFAT and are often easy to resolve.