FATS RO API
You are developer and you wish to read private
data-informations on a pseudo-fat rather than native, which is to
hosted on a image file or elsewhere -> well it is here.
It is one of rare API existing in our world allowing those i.e. to read virtual
file on a file image.
Profit in good to download these API because you will not find that elsewhere.
Explanation :
It is not a question of native fat like (ext4, ntfs), but rather
a virtual fat(Fats Reever) hosted in a image file and controllable by
programming.
If it is a question of thus making visible in the explorer of Windows and all
the applications, you must download API VDXS (VDFS), there is a sample provided..
|
|
| 1)Virtual file in lambda virtual fat (eg Fats Reever), lambda fat (eg
Fats Reever) hosted in the file vfile.bin (file hosted in the native fat
windows) 2)Virtual directory in lambda virtual fat , lambda fat (eg Fats Reever) hosted in the file vfile.bin (file hosted in the native fat windows) 3)Data hosted in the virtual file , virtual file in lambda fat (eg Fats Reever) , lambda fat (eg Fats Reever) hosted in the file vfile.bin (file hosted in the native fat windows) 4)Virtual path in the lambda fat (Eg Fats Reever) , lambda fat (eg Fats Reever) hosted in the file vfile.bin (file hosted in the native fat windows)
|
Disadvantage :
| Not free |
| Source code unavailable |
| Some bugs quelques bugs but usable |
| Not portable ! |
| No visible in Windows explorer , you must download API VDXS(VDFS) and use adequat sample |
| Theoretical limit 2 tera bytes for Fat Reever |
| Fat read-only access for all licenses , it is written by API file burning api or BurnFats utility (ftpfats) |
| For storage in the physical partition (\\.\PhysicalDrive) , it's client must be write it. |
Advantage :
| Compatible Windows XP,7,..,10 |
| Easy utilisation |
| DotNet supported (Sample not available in the day 14/04/2018) |
| Encipher data and protection by password |
| Possible downloading a free license limited in the time (x86 platform only) |
| Possible storage files of the fat in the image file |
| API service work any kernel driver |
| AMD64 supported |
| Manage fat on everywhere support |
Builtin function :
| Burning |
| Encipher |
| File and directory |
Limit on evaluation version :
| One instance per user |
| Red popup showing a evaluation version |
| Size fat maximal 256 Mb |
| Usable only if processus is attacher from a debugger |
The Fat IgMa is a remade version and is an advance compared to the Fat Reever, it was developed on its own, it has a higher purchase / rental price.
Downloading FAT IgMa :
| Version | Downloading | Changelog |
| 1.0 |
Support linear access |
Downloading FAT Reever :
| Version | Downloading | Changelog |
| 1.0 |
- |
|
| 2.0 | Solved Bug ffats_readfile reading rate varying according
to file seek. Critical bug Outofmemory exception on ffats_readfile when file seek is enought large. Compatibility MapFatr v1.2 |
|
| 3.0 | Emulation Access lineair virtual disk (addr) Change version external licence |
|
Other :
| Error code of virtual fat click here |
| For information about the use of these APIs in other systems (Linux, Embedded system, Windows Driver, Kernel Code, other platform, ARM64, ARM) click here |
