FAT16 Package

FAT16 Package

class FATpy.FAT16.FAT16Partition(partition)

Bases: FATpy.Partition.Partition

getCluster(key)
getClusterChain(key)
getDirectory(key)
readBootSector()
readFAT()
readFAT16TableSector(where=None)
readROOT()

FAT16BootSector Module

class FATpy.FAT16.FAT16BootSector.FAT16BootSector(data)[source]

Bases: FATpy.Sector.Sector

ID[source]

ID: The ID is a random serial number assigned at format time in order to aid in distinguishing one disk from another.

OEM_ID[source]

OEM ID: Following the jump instruction is an 8 byte “OEM ID”. This is typically a string of characters that identifies the operating system that formatted the volume.

bps[source]

Bytes Per Sector: This is the size of a hardware sector and for most disks in use in the United States, the value of this field will be 512.

current_head[source]

Current Head: This is another field typically used when doing INT13 BIOS calls. The value would originally have been used to store the track on which the boot record was located, but the value stored on disk is not currently used as such. Therefore, Windows NT uses this field to store two flags:

  • The low order bit is a “dirty” flag, used to indicate that autochk should run chkdsk against the volume at boot time.
  • The second lowest bit is a flag indicating that a surface scan should also be run.
drive_number[source]

Physical Drive Number: This is related to the BIOS physical drive number. Floppy drives are numbered starting with 0x00 for the A: drive, while physical hard disks are numbered starting with 0x80. Typically, you would set this value prior to issuing an INT 13 BIOS call in order to specify the device to access. The on-disk value stored in this field is typically 0x00 for floppies and 0x80 for hard disks, regardless of how many physical disk drives exist, because the value is only relevant if the device is a boot device.

executable_code[source]

On a bootable volume, the area following the Extended BIOS Parameter Block is typically executable boot code. This code is responsible for performing whatever actions are necessary to continue the boot-strap process. On Windows NT systems, this boot code will identify the location of the NTLDR file, load it into memory, and transfer execution to that file. Even on a non-bootable floppy disk, there is executable code in this area. The code necessary to print the familiar message, “Non-system disk or disk error” is found on most standard, MS-DOS formatted floppy disks that were not formatted with the “system” option.

executable_marker[source]

Finally, the last two bytes in any boot sector always have the hexidecimal values: 0x55 0xAA.

extended_signature[source]

Signature: The extended boot record signature must be either 0x28 or 0x29 in order to be recognized by Windows NT.

fat_copies[source]

FATs: This is the number of copies of the FAT table stored on the disk. Typically, the value of this field is 2.

jumpcode[source]

jumpcode: Because the MBR transfers CPU execution to the boot sector, the first few bytes of the FAT boot sector must be valid executable instructions for an 80x86 CPU. In practice these first instructions constitute a “jump” instruction and occupy the first 3 bytes of the boot sector. This jump serves to skip over the next several bytes which are not “executable.”

large_sectors[source]

Large Sectors: If the Small Sectors field is zero, this field contains the total number of sectors used by the FAT volume.

media_descriptor[source]

Media Descriptor: This byte provides information about the media being used. The following table lists some of the recognized media descriptor values and their associated media. Note that the media descriptor byte may be associated with more than one disk capacity.

Byte Capacity Media Size and Type F0 2.88 MB 3.5-inch, 2-sided, 36-sector F0 1.44 MB 3.5-inch, 2-sided, 18-sector F9 720 KB 3.5-inch, 2-sided, 9-sector F9 1.2 MB 5.25-inch, 2-sided, 15-sector FD 360 KB 5.25-inch, 2-sided, 9-sector FF 320 KB 5.25-inch, 2-sided, 8-sector FC 180 KB 5.25-inch, 1-sided, 9-sector FE 160 KB 5.25-inch, 1-sided, 8-sector F8 —– Fixed disk
num_heads[source]

Heads: Part of the apparent disk geometry in use when the disk was formatted.

num_hidden_sectors[source]

Hidden Sectors: This is the number of sectors on the physical disk preceding the start of the volume. (that is, before the boot sector itself) It is used during the boot sequence in order to calculate the absolute offset to the root directory and data areas.

reserved_sectors[source]

Reserved Sectors: This represents the number of sectors preceding the start of the first FAT, including the boot sector itself. It should always have a value of at least 1.

root_entries[source]

Root Entries: This is the total number of file name entries that can be stored in the root directory of the volume. On a typical hard drive, the value of this field is 512. Note, however, that one entry is always used as a Volume Label, and that files with long file names will use up multiple entries per file. This means the largest number of files in the root directory is typically 511, but that you will run out of entries before that if long file names are used.

sectors_per_fat[source]

Sectors Per FAT: This is the number of sectors occupied by each of the FATs on the volume. Given this information, together with the number of FATs and reserved sectors listed above, we can compute where the root directory begins. Given the number of entries in the root directory, we can also compute where the user data area of the disk begins.

sectors_per_track[source]

Sectors Per Track: Part of the apparent disk geometry in use when the disk was formatted.

small_sectors[source]

Small Sectors: This field is used to store the number of sectors on the disk if the size of the volume is small enough. For larger volumes, this field has a value of 0, and we refer instead to the “Large Sectors” value which comes later.

spc[source]

Sectors Per Cluster: Because FAT is limited in the number of clusters (or “allocation units”) that it can track, large volumes are supported by increasing the number of sectors per cluster. The cluster factor for a FAT volume is entirely dependent on the size of the volume. Valid values for this field are 1, 2, 4, 8, 16, 32, 64, and 128.

system_id[source]

System ID: This field is either “FAT12” or “FAT16,” depending on the format of the disk.

volume_label[source]

Volume Label: This field was used to store the volume label, but the volume label is now stored as a special file in the root directory.

FAT16Directory Module

class FATpy.FAT16.FAT16Directory.FAT16Directory(*args, **kwargs)[source]

Bases: FATpy.MultiBlockDataUnpacker.MultiBlockDataUnpacker

next()[source]

FAT16DirectoryEntry Module

class FATpy.FAT16.FAT16DirectoryEntry.FAT16DirectoryEntry(data)[source]

Bases: FATpy.DataUnpacker.DataUnpacker

archive[source]
attributes[source]
Attributes: a bitvector.
Bit 0: read only. Bit 1: hidden. Bit 2: system file. Bit 3: volume label. Bit 4: subdirectory. Bit 5: archive. Bits 6-7: unused.
date[source]

Date (7/4/5 bits, for year-since-1980/month/day)

file_name[source]
filesize[source]

Filesize in bytes

hidden[source]
readonly[source]
starting_cluster[source]

Starting Cluster (or 0 for an empty file)

subdirectory[source]
system[source]
time[source]

Time (5/6/5 bits, for hour/minutes/doubleseconds)

volume_label[source]

FAT16Partition Module

class FATpy.FAT16.FAT16Partition.FAT16Partition(partition)[source]

Bases: FATpy.Partition.Partition

getCluster(key)[source]
getClusterChain(key)[source]
getDirectory(key)[source]
readBootSector()[source]
readFAT()[source]
readFAT16TableSector(where=None)[source]
readROOT()[source]

FAT16Table Module

class FATpy.FAT16.FAT16Table.FAT16Table[source]
appendSector(sector)[source]
end_of_cluster_chain[source]
media_descriptor[source]
next()[source]

FAT16TableSector Module

class FATpy.FAT16.FAT16TableSector.FAT16TableSector(*args, **kwargs)[source]

Bases: FATpy.Sector.Sector

next()[source]