.:: HISTORY OF FAT/NTFS FILE SYSTEMS::.

The FAT system (File Allocation Table) the file system has its origin in the late seventies and in the early1980s and was the file system, which is supported by the operating system Microsoft MSDOS. As simple file system was originally developed, which is for floppy disk drive smaller than 500K in the size usable. Over time it was increased, in order to support the larger and larger means. Z.Z. gives it three FATS to kinds of file system: FAT12, FAT16 and FAT32.

The fundamental difference concerning these FATS Vorarten and the reason for the names, is the size, in the points, the entries in actual FATS the structure on the disk. There are 12 bits in GREASING an entry FAT12, 16 bits in GREASING an entry FAT16 and 32 bits in an entry of the FAT FAT32. The first important data structure on GREASING an expenditure is called the BPB (bio S-parameter block), which is in the first sector of the expenditure in the reserved region.

This sector becomes sometimes the "loading sector" or the "reserved sector" or the "0. Sector, "mentioned, but the important fact is simple that it is the first sector of the expenditure. The BPB in the loading sector, that for MSDOS 2.x left was defined only, FATS an expenditure also excluding less than 65,536 sectors too (value MT 32 of the sectors 512-byte). This restriction was because of the fact that "total sector" was the field only a 16-bit field.

This restriction was addressed by MSDOS 3.x, in which the BPB was changed, in order to cover a new 32-bit field for the total sector value. The following BPB change occurred with the operating system Microsoft Windows 95, to which the kind FAT32 was introduced. FAT16 was not limited for that by the maximum size FATS and maximum valid block size to no more than a 2-GB-Ausgabe, if the disk had sectors 512-byte.

FAT32 addressed this restriction on the quantity of storage capacity, which could occupy FATS an expenditure, so that disks must only have more largely than 2 GBS a defined subject. The FAT32 BPB brings exactly the FAT12/FAT16 together BPB up to and covering the field BPB_TotSec32. They differ, beginning at disalignment 6, dependent on whether the central kind is FAT12/FAT16 or FAT32. The relevant point here is that the BPB should always be in the loading sector GREASING of an expenditure one, which has all new BPB fields either for the FAT12-/fat16 or Fat32-bpb kind.

Doing, this way the maximum compatibility FATS of the expenditure guarantees and guarantees it that all FATS file system drivers understand and support the expenditure correctly, because them always contain all at present defined fields. The following data structure, which is important, is the FAT. Which this data structure is, defines an individually connected list of the "extent" (blocks) of a document. There are normally two identical fats. FAT No. 2 is simply a spare copy of No. 1, since FAT for the function of the disk is substantial.

Note at this point, which is not a FAT listing or document container anything, but at a regular document, which has a special attribute to indicate it is a listing. Only other special thing over a listing is that the data or contents of the "document" a number of FATS 32=byte of entries are into a listing. In all other respects a listing is like a document straight. Contents of each FAT entry consist of a complete number.

// You would tell MiniFetch: // replace with your unique start point in the source of the HTML page $start= strpos($value, "

"); // replace with the unique finish point in the source of the HTML page $finish= strpos($value, "Result Page"); $length= $finish-$start; $value=substr($value, $start, $length); $value = eregi_replace( "]*>", "", $value ); // Remove image tags. $value = eregi_replace( "]*>", "", $value ); // Remove image alt tags $value = eregi_replace( "]*>", "", $value ); // Remove all variations of tags. $value = eregi_replace( "", "", $value ); // Remove closing tags. $value = eregi_replace( "]*>", "", $value ); // Remove