<P> Due to the restricted size of the MBR's code section, it typically contains only a small program that copies additional code (such as a boot loader) from the storage device into memory . Control is then passed to this code, which is responsible for loading the actual operating system . This process is known as chain loading . </P> <P> Popular MBR code programs were created for booting PC DOS and MS - DOS, and similar boot code remains in wide use . These boot sectors expect the fdisk partition table scheme to be in use and scans the list of partitions in the MBR's embedded partition table to find the only one that is marked with the active flag . It then loads and runs the volume boot record (VBR) of the active partition . </P> <P> There are alternative boot code implementations, some of which are installed by boot managers, which operate in a variety of ways . Some MBR code loads additional code for a boot manager from the first track of the disk, which it assumes to be "free" space that is not allocated to any disk partition, and executes it . A MBR program may interact with the user to determine which partition on which drive should boot, and may transfer control to the MBR of a different drive . Other MBR code contains a list of disk locations (often corresponding to the contents of files in a filesystem) of the remainder of the boot manager code to load and to execute . (The first relies on behavior that is not universal across all disk partitioning utilities, most notably those that read and write GPTs . The last requires that the embedded list of disk locations be updated when changes are made that would relocate the remainder of the code .) </P> <P> On machines that do not use x86 processors, or on x86 machines with non-BIOS firmware such as Open Firmware or Extensible Firmware Interface (EFI) firmware, this design is unsuitable, and the MBR is not used as part of the system bootstrap . EFI firmware is instead capable of directly understanding the GPT partitioning scheme and the FAT filesystem format, and loads and runs programs held as files in the EFI System partition . The MBR will be involved only insofar as it might contain a partition table for compatibility purposes if the GPT partition table scheme has been used . </P>

Under an mbr based system how are drive letters allocated