  a boot sector or boot block is a region of a hard disk, floppy disk, optical disc, or other data storage device that contains machine code to be loaded into random-access memory (ram) by a computer system's built-in firmware. the purpose of a boot sector is to allow the boot process of a computer to load a program (usually, but not necessarily, an operating system) stored on the same storage device. the location and size of the boot sector (perhaps corresponding to a logical disk sector) is specified by the design of the computing platform. on an ibm pc compatible machine, the bios selects a boot device, then copies the first sector from the device (which may be a mbr, vbr or any executable code), into physical memory at memory address 0x7c00. on other systems, the process may be quite different. == kinds of boot sectors == several major kinds of boot sectors could be encountered on ibm pc compatible hard disks, floppy disks and similar storage devices: * a master boot record (mbr) is the first sector of a data storage device that has been partitioned. the mbr sector may contain code to locate the active partition and invoke its volume boot record. * a volume boot record (vbr) is the first sector of a data storage device that has not been partitioned, or the first sector of an individual partition on a data storage device that has been partitioned. it may contain code to load and invoke an operating system (or other standalone program) installed on that device or within that partition. the presence of an ibm pc compatible boot loader for x86-cpus in the boot sector is by convention indicated by a two-byte hexadecimal sequence 0x55, 0xaa (called the boot sector signature) at the end of the boot sector (offsets 0x1fe and 0x1ff). this signature indicates the presence of at least a dummy boot loader which is safe to be executed, even if it may not be able to actually load an operating system. it does not indicate the presence of a (or even a particular) file system or operating system, although some old versions of dos 3 relied on it in their process to detect fat-formatted media (newer versions do not). boot code for other platforms or cpus should not use this signature, since this may lead to a crash when the bios passes execution to the boot sector assuming that it contains valid executable code. nevertheless, some media for other platforms erroneously contain the signature, anyway, rendering this check not 100% reliable in practice. the signature is checked for by most system bioses since (at least) the ib
BIOS Booting Computer_file_systems