Projects tagged ‘fat’

The HelenOS project is an effort to develop a complete and usable modern operating system, yet offering room for experimenting and research. HelenOS uses its own microkernel written from scratch and ... [More] supports SMP, multitasking and multithreading on both 32-bit and 64-bit, little-endian and big-endian processor architectures, among which are AMD64/EM64T (x86-64), ARM, IA-32, IA-64 (Itanium), 32-bit MIPS, 32-bit PowerPC, SPARC V9 and Xen 3.0. Thanks to the relatively high number of supported architectures and suitable design, HelenOS is extremely-well portable. [Less]

FullFAT 0.90 Download Now AvailableThis is a pre-1.0 release, and includes a snapshot of the current SVN also including the FFTerm project for the Visual Studio Demo. This release may not clean ... [More] compile, and there are a couple of performance issues I am wanting to work on regarding the opening of files. Really I just wanted to get some code out there for testing. James FullFATFullFAT is a fully featured FAT 12/16/32 library. It features optional LFN (Long File-name support) Fast and Efficient with Low Memory Footprint Scalable from Embedded Systems to Desktop OS’s Thread Safe Multiple File Open LFN Support (optional). Fully Featured Optional Caching Safe Caching behaviour Customisable Caching behaviour Multiple & Single Block Reading Platform independent, no assumptions about Endianes [Less]

fat_imgen is a minimalistic utility you can use to create or modify FAT12 floppy images with.

This is a Java library that allows to read and write FAT12, FAT16 and FAT32 file systems. It is written in pure Java (no native code involved) and has no external dependencies. FeaturesThe following ... [More] features are currently supported: creating FAT16 and FAT32 file systems r/w access to FAT12, FAT16 and FAT32 file systems r/w access to the FAT's volume label To learn more, check out the documentation Wiki. [Less]

Some MP3 mobile players only show a very limited number of directories when using the FAT16 file system. This behavior sometimes can be improved by not using file- and directory-names longer than 12 ... [More] characters. (8.3 format, see http://en.wikipedia.org/wiki/File_Allocation_Table for more information). fnshortener (file name shortener) will do this job automatically for you. BIG FAT WARNING: Always double check which path you give as an argument to fnshortener. Every file and directory will be renamed. Even if there is no MP3-file in it at all. This can destroy your file-system (Windows) destroy the names of your wonderful arranged home-directory (Linux) destroy the wonderful names of your MP3 files in your original MP3 collection. So only rename copies of your MP3 collection. System Requirementsfnshortener is programmed in Java, so be sure you have a recent Java VM (at least 6). You aren't sure? Go to http://www.java.com It is also a commandline/shell program. No nice graphical interface (GUI) yet. MP3 playersA (veeery short) list of MP3-players is in the WIKI. [Less]

The TFFS project aims to create a FAT file system module for embedded system. All of code is writen by ANSI C, so it is easy to port for your architecture. You can support your own specific hardware ... [More] by implimentating your own Hardware Abstraction Interface. Feature of Tiny-FAT file systemSupports FAT12, FAT16 and FAT32. Supports both 8.3 format file name and Long File Name(LFN). Supports cache system to improve access speed. Hardware independent design, easy to port to specific hardware platform. Works under Linux, iTRION and None-OS environment(currently only works under Linux). Get latest versionYou can get the latest version of TFFS-lib by checking out from google code. svn checkout http://tffs-lib.googlecode.com/svn/trunk/ tffs-lib-read-onlyBuild tffs-lib1. Enter into the tffs-lib directory and make the library. make2. tshell is a test tool and a demo application to show how to use the tffs-lib. You can build it by the following command. make tsh3. tffs is a test application including some test cases. You can build it by using the following command. make tffsTest under linux1. First of all, you have to create a FAT file system image used by tsh. It can be done by the script "mkfs.sh". The following command create a FAT file system image file with the size of 32M. mkfs.sh fat32.img 327682. Now, you can use the tsh to test the function of tffs-lib. [zhangck@subnode1 tffs-lib-read-only]$ ./tsh fat32.img =================Boot sector==================== oem_name: mkdosfs byts_per_sec: 512 resvd_sec_cnt: 32 sec_per_clus: 1 ================================================ count_of_clusters = 64496 tffs->fat_type:3 tffs->sec_fat:32 tffs->sec_root_dir:1040 tffs->sec_first_data:1040 tiny fat file system mount OK. /:>ls Total 0 files. /:>help tsh commands: ls: Lists the contents of a directory. pwd: Print current directory. cd: Change the current directory to dir. mkdir: Make directories. rm: Remove directories or files. cat: Show the file contents. write: Write contents to the file. help: Show help. quit: Quit tiny shell. /:>mkdir tdir1 /:>ls 0 byte 2009/01/20 - 16:24 tdir1 Total 1 files. /:>mkdir tdir2 /:>ls 0 byte 2009/01/20 - 16:24 tdir1 0 byte 2009/01/20 - 16:24 tdir2 Total 2 files. /:>write test1.txt this is a test line. this is a test line2. ============================================================ wrote 44 bytes to file test1.txt ok. /:>ls 0 byte 2009/01/20 - 16:24 tdir1 0 byte 2009/01/20 - 16:24 tdir2 44 byte 2009/01/20 - 16:24 test1.txt Total 3 files. /:>cat test1.txt this is a test line. this is a test line2. ============================================================ [test1.txt] total size 44 bytes /:>write testlongfilenamefile.fileextion this is a test line 01. this is a test line 02. this is a test line 03. this is a test line 04. ============================================================ wrote 96 bytes to file testlongfilenamefile.fileextion ok. /:>ls 0 byte 2009/01/20 - 16:24 tdir1 0 byte 2009/01/20 - 16:24 tdir2 44 byte 2009/01/20 - 16:24 test1.txt 96 byte 2009/01/20 - 16:25 testlongfilenamefile.fileextion Total 4 files. /:>cd tdir1 /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. Total 2 files. /tdir1/:>mkdir dir1 /tdir1/:>mkdir dir2 /tdir1/:>mkdir dir3 /tdir1/:>mkdir dir4 /tdir1/:>mkdir dir5 /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. 0 byte 2009/01/20 - 16:26 dir1 0 byte 2009/01/20 - 16:26 dir2 0 byte 2009/01/20 - 16:26 dir3 0 byte 2009/01/20 - 16:26 dir4 0 byte 2009/01/20 - 16:26 dir5 Total 7 files. /tdir1/:>write t.txt this is a test line 01. this is a test line 02. ============================================================ wrote 52 bytes to file t.txt ok. /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. 0 byte 2009/01/20 - 16:26 dir1 0 byte 2009/01/20 - 16:26 dir2 0 byte 2009/01/20 - 16:26 dir3 0 byte 2009/01/20 - 16:26 dir4 0 byte 2009/01/20 - 16:26 dir5 52 byte 2009/01/20 - 16:26 t.txt Total 8 files. /tdir1/:>rm t.txt /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. 0 byte 2009/01/20 - 16:26 dir1 0 byte 2009/01/20 - 16:26 dir2 0 byte 2009/01/20 - 16:26 dir3 0 byte 2009/01/20 - 16:26 dir4 0 byte 2009/01/20 - 16:26 dir5 Total 7 files. /tdir1/:>rm -r dir1 /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. 0 byte 2009/01/20 - 16:26 dir2 0 byte 2009/01/20 - 16:26 dir3 0 byte 2009/01/20 - 16:26 dir4 0 byte 2009/01/20 - 16:26 dir5 Total 6 files. /tdir1/:>mkdir dir6 /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. 0 byte 2009/01/20 - 16:27 dir6 0 byte 2009/01/20 - 16:26 dir2 0 byte 2009/01/20 - 16:26 dir3 0 byte 2009/01/20 - 16:26 dir4 0 byte 2009/01/20 - 16:26 dir5 Total 7 files. /tdir1/:>mkdir dir7 /tdir1/:>ls 0 byte 2009/01/20 - 16:24 . 0 byte 2009/01/20 - 16:24 .. 0 byte 2009/01/20 - 16:27 dir6 0 byte 2009/01/20 - 16:26 dir2 0 byte 2009/01/20 - 16:26 dir3 0 byte 2009/01/20 - 16:26 dir4 0 byte 2009/01/20 - 16:26 dir5 0 byte 2009/01/20 - 16:27 dir7 Total 8 files. /tdir1/:>cd dir2 /tdir1/dir2/:>ls 0 byte 2009/01/20 - 16:26 . 0 byte 2009/01/20 - 16:26 .. Total 2 files. /tdir1/dir2/:>mkdir dir3 /tdir1/dir2/:>cd dir3 /tdir1/dir2/dir3/:>mkdir dir4 /tdir1/dir2/dir3/:>cd dir4 /tdir1/dir2/dir3/dir4/:>mkdir dir5 /tdir1/dir2/dir3/dir4/:>cd dir5 /tdir1/dir2/dir3/dir4/dir5/:>mkdir dir6 /tdir1/dir2/dir3/dir4/dir5/:>cd dir6 /tdir1/dir2/dir3/dir4/dir5/dir6/:>pwd /tdir1/dir2/dir3/dir4/dir5/dir6/ /tdir1/dir2/dir3/dir4/dir5/dir6/:>quit [zhangck@subnode1 tffs-lib-read-only]$3. You can also use the fat system module of linux to validate the result of tffs-lib by using the following command. [root@subnode1 tffs-lib-read-only]# mkdir /mnt/fatimg [root@subnode1 tffs-lib-read-only]# ./mountfs.sh fat32.img /mnt/fatimg/ /dev/loop1 installed... /mnt/fatimg/ mount ok... [root@subnode1 tffs-lib-read-only]# cd /mnt/fatimg/ [root@subnode1 fatimg]# ls tdir1 tdir2 test1.txt testlongfilenamefile.fileextion [root@subnode1 fatimg]# ll drwxr-xr-x 8 root root 512 1月 20 16:24 tdir1 drwxr-xr-x 2 root root 512 1月 20 16:24 tdir2 -rwxr-xr-x 1 root root 44 1月 20 16:24 test1.txt -rwxr-xr-x 1 root root 96 1月 20 16:25 testlongfilenamefile.fileextionEnjoy it [Less]

ThinFAT32ThinFAT32 is an implementation of the FAT32 filesystem specification specifically targeted at embedded systems. It is designed to have a low memory footprint, use very little RAM, but be as ... [More] robust and feature-complete as more sophisticated or expensive implementations of the same spec. FeaturesSmall Easy to setup and use (you need only supply functions to read and write blocks from your hardware) Written in ANSI-compliant C Supports both 8.3 and LFN (Long Filenames) Almost no dependency on any external C library. (Requires only string.h, which can be factored out very easily) Low RAM footprint (Works mostly like the C standard libs fopen() fread() fwrite() etc... Does not conflict with the standard C libs, if you happen to be using them Is ThinFAT32 Ready for My Application?Yes! ... er... well actually no. There are still some bugs, and a few features left, but all in all, it works pretty well. It's certainly ready to be tested, and for use in prototypes. Getting Started - Testing on NIXGet the source from subversion. Make sure you've got gcc. The default make target builds main.c which is a simple test program. (Typically the last test I felt like doing) $: makeThe default build of ThinFAT32 depends on a filesystem for testing. The make targets make create make mount and make unmount create, mount and unmount this filesystem respectively. The filesystem will be stored in the regular file test.fat32, and will be available through the directory fs when mounted. Have a look at main.c to see how ThinFAT32 is used. [Less]

Grupo formado por alunos de diversos anos do curso de engenharia de computação da PUC-Campinas

FAT filesystem(12/16/32) implementation on Python, allowing reading/writing of FAT images. Project INACTIVE - Any help?

follows