INT 13H

Last updated

INT 13h is shorthand for BIOS interrupt call 13 hex , the 20th interrupt vector in an x86-based (IBM PC-descended) computer system. The BIOS typically sets up a real mode interrupt handler at this vector that provides sector-based hard disk and floppy disk read and write services using cylinder-head-sector (CHS) addressing. Modern PC BIOSes also include INT 13h extension functions, originated by IBM and Microsoft in 1992, that provide those same disk access services using 64-bit LBA addressing; with minor additions, these were quasi-standardized by Phoenix Technologies and others as the EDD (Enhanced Disk Drive) BIOS extensions.

Contents

INT is an x86 instruction that triggers a software interrupt, and 13hex is the interrupt number (as a hexadecimal value) being called.

Modern computers come with both BIOS INT 13h and UEFI functionality that provides the same services and more, with the exception of UEFI Class 3 that completely removes CSM thus lacks INT 13h and other interrupts. Typically, UEFI drivers use LBA-addressing instead of CHS-addressing.

Overview

Under real mode operating systems, such as DOS, calling INT 13h would jump into the computer's ROM-BIOS code for low-level disk services, which would carry out physical sector-based disk read or write operations for the program. In DOS, it serves as the low-level interface for the built-in block device drivers for hard disks and floppy disks. This allows INT 25h and INT 26h to provide absolute disk read/write functions for logical sectors to the FAT file system driver in the DOS kernel, which handles file-related requests through DOS API (INT 21h) functions.

Under protected mode operating systems, such as Microsoft Windows NT derivatives (e.g. NT4, 2000, XP, and Server 2003) and Linux with dosemu, the OS intercepts the call and passes it to the operating system's native disk I/O mechanism. Windows 9x and Windows for Workgroups 3.11 also bypass BIOS routines when using 32-bit Disk Access. Besides performing low-level disk access, INT 13h calls and related BIOS data structures also provide information about the types and capacities of disks (or other DASD devices) attached to the system; when a protected-mode OS boots, it may use that information from the BIOS to enumerate disk hardware so that it (the OS) can load and configure appropriate disk I/O drivers.

The original BIOS real-mode INT 13h interface supports drives of sizes up to about 8 GB using what is commonly referred to as physical CHS addressing. This limit originates from the hardware interface of the IBM PC/XT disk hardware. The BIOS used the cylinder-head-sector (CHS) address given in the INT 13h call, and transferred it directly to the hardware interface. A lesser limit, about 504 MB, was imposed by the combination of CHS addressing limits used by the BIOS and those used by ATA hard disks, which are dissimilar. When the CHS addressing limits of both the BIOS and ATA are combined (i.e. when they are applied simultaneously), the number of 512-byte sectors that can be addressed represent a total of about 504 MB.

The 504 MB limit was overcome using CHS translation, a technique by which the BIOS would simulate a fictitious CHS geometry at the INT 13h interface, while communicating with the ATA drive using its native logical CHS geometry. (By the time the 504 MB barrier was being approached, ATA disks had long before ceased to present their real physical geometry parameters at the external ATA interface.) Translation allows the BIOS, still using CHS addressing, to effectively address ATA disks with sizes up to 8064 MB, the native capacity of the BIOS CHS interface alone. (The ATA interface has a much larger native CHS addressing capacity, so once the "interference" of the CHS limits of BIOS and ATA was resolved by addressing, only the smaller limitation of the BIOS was significant.) CHS translation is sometimes referred to as logical CHS addressing, but that is actually a misnomer since by the time of this BIOS development, ATA CHS addresses were already logical, not physical. The 8064 MB limit originates from a combination of the register value based calling convention used in the INT 13h interface and the goal of maintaining backward compatibilitydictating that the format or size of CHS addresses passed to INT 13h could not be changed to add more bits to one of the fields, e.g. the Cylinder-number field. This limit uses 1024 cylinders, 256 heads, 63 sectors, and 512 byte blocks, allowing exactly 7.875 GiB of addressing (1024 × 256 × 63 × 512 bytes). There were briefly a number of BIOSes that offered incompatible versions of this interfacefor example, AWARD AT BIOS and AMI 386sx BIOS have been extended to handle up to 4096 cylinders by placing bits 10 and 11 of the cylinder number into bits 6 and 7 of register DH.

All versions of MS-DOS, (including MS-DOS 7 and Windows 95) have a bug which prevents booting disk drives with 256 heads (register value 0xFF), so many modern BIOSes provide CHS translation mappings with at most 255 (0xFE) heads, [1] [2] thus reducing the total addressable space to exactly 8032.5 MiB (approx 7.844 GiB). [3]

To support addressing of even larger disks, an interface known as INT 13h Extensions was introduced by IBM and Microsoft, then later re-published and slightly extended by Phoenix Technologies as part of BIOS Enhanced Disk Drive Services (EDD). [4] [5] It defines new functions within the INT 13h service, all having function numbers greater than 40h, that use 64-bit logical block addressing (LBA), which allows addressing up to 8 ZiB. (An ATA drive can also support 28-bit or 48-bit LBA which allows up to 128 GiB or 128 PiB respectively, assuming a 512-byte sector/block size). This is a "packet" interface, because it uses a pointer to a packet of information rather than the register based calling convention of the original INT 13h interface. This packet is a very simple data structure that contains an interface version, data size, and LBAs. For software backward-compatibility, the extended functions are implemented alongside the original CHS functions, and calls to functions from both sets can be intermixed, even for the same drive, with the caveat that the CHS functions cannot reach past the first 8064 MB of the disk.

Some cache drivers flush their buffers when detecting that DOS is bypassed by directly issuing INT 13h from applications. A dummy read via INT 13h can be used as one of several methods to force cache flushing for unknown caches (e.g. before rebooting). [1] [2]

AMI BIOSes from around 1990–1991 trash word unaligned buffers. Some DOS and terminate-and-stay-resident programs clobber interrupt enabling and registers so PC DOS and MS-DOS install their own filters to prevent this. [6]

List of INT 13h services

Drive Table
DL = 00h1st floppy disk ( "drive A:" )
DL = 01h2nd floppy disk ( "drive B:" )
DL = 02h3rd floppy disk ( "drive C:" )
. . .
DL = 7Fh128th floppy disk
DL = 80h1st hard disk
DL = 81h2nd hard disk
DL = 82h3rd hard disk
. . .
DL = E0hCD/DVD[ citation needed ], or 97th hard disk
. . .
DL = FFh128th hard disk
Function Table
AH = 00h Reset Disk System
AH = 01h Get Status of Last Drive Operation
AH = 02h Read Sectors From Drive
AH = 03h Write Sectors To Drive
AH = 04h Verify Sectors
AH = 05h Format Track
AH = 06h Format Track Set Bad Sector Flags
AH = 07h Format Drive starting at Track
AH = 08h Read Drive Parameters
AH = 09hHDInitialize Disk Controller
AH = 0AhHDRead Long Sectors From Drive
AH = 0BhHDWrite Long Sectors To Drive
AH = 0ChHDMove Drive Head To Cylinder
AH = 0DhHDReset Disk Drives
AH = 0EhPS/2Controller Read Test
AH = 0FhPS/2Controller Write Test
AH = 10hHDTest Whether Drive Is Ready
AH = 11hHDRecalibrate Drive
AH = 12hPS/2Controller RAM Test
AH = 13hPS/2Drive Test
AH = 14hHDController Diagnostic
AH = 15h Read Drive Type
AH = 16hFDDetect Media Change
AH = 17hFDSet Media Type For Format (used by DOS versions <= 3.1)
AH = 18hFDSet Media Type For Format (used by DOS versions >= 3.2)
AH = 19h Park Heads
AH = 41hEXTTest Whether Extensions Are Available
AH = 42hEXTRead Sectors From Drive
AH = 43hEXTWrite Sectors To Drive
AH = 44hEXTVerify Sectors
AH = 45hEXTLock/Unlock Drive
AH = 46hEXTEject Drive
AH = 47hEXTMove Drive Head To Sector
AH = 48hEXTRead Drive Parameters
AH = 49hEXTDetect Media Change
AH = 4BhEXTGet Drive Emulation Type

If the second column is empty then the function may be used both for floppy and hard disk.

INT 13h AH=00h: Reset Disk System

Parameters
AH00h
DLDrive (bit 7 set means reset both hard and floppy disks)
Results
CFSet on error
AHReturn Code

INT 13h AH=01h: Get Status of Last Drive Operation

Parameters
AH01h
DLDrive

Bit 7=0 for floppy drive, bit 7=1 for fixed drive

Results
AH
Return Code
00hSuccess
01hInvalid Command
02hCannot Find Address Mark
03hAttempted Write On Write Protected Disk
04hSector Not Found
05hReset Failed
06hDisk change line 'active'
07hDrive parameter activity failed
08hDMA overrun
09hAttempt to DMA over 64kb boundary
0AhBad sector detected
0BhBad cylinder (track) detected
0ChMedia type not found
0DhInvalid number of sectors
0EhControl data address mark detected
0FhDMA out of range
10hCRC/ECC data error
11hECC corrected data error
20hController failure
40hSeek failure
80hDrive timed out, assumed not ready
AAhDrive not ready
BBhUndefined error
CChWrite fault
E0hStatus error
FFhSense operation failed
CFSet On Error, Clear If No Error

INT 13h AH=02h: Read Sectors From Drive

Parameters
AH02h
ALSectors To Read Count
CHCylinder
CLSector
DHHead
DLDrive
ES:BXBuffer Address Pointer
Results
CFSet On Error, Clear If No Error
AHReturn Code
ALActual Sectors Read Count

Remarks

Register CX contains both the cylinder number (10 bits, possible values are 0 to 1023) and the sector number (6 bits, possible values are 1 to 63). Cylinder and Sector bits are numbered below:

CX =       ---CH--- ---CL--- cylinder : 76543210 98 sector   :            543210

Examples of translation:

CX:=((cylinderand255)shl8)or((cylinderand768)shr2)orsector;cylinder:=((CXand$FF00)shr8)or((CXand$C0)shl2)sector:=CXand63;

Addressing of Buffer should guarantee that the complete buffer is inside the given segment, i.e. ( BX + size_of_buffer ) <= 10000h. Otherwise the interrupt may fail with some BIOS or hardware versions.

Example

Assume you want to read 16 sectors (= 2000h bytes) and your buffer starts at memory address 4FF00h. Utilizing memory segmentation, there are different ways to calculate the register values, e.g.:

ES = segment         = 4F00h BX = offset          =  0F00h sum = memory address = 4FF00h would be a good choice because 0F00h + 2000h = 2F00h <= 10000h ES = segment         = 4000h BX = offset          =  FF00h sum = memory address = 4FF00h would not be a good choice because FF00h + 2000h = 11F00h > 10000h

Function 02h of interrupt 13h may only read sectors of the first 16,450,560 sectors of your hard drive, to read sectors beyond the 8 GB limit you should use function 42h of INT 13h Extensions. Another alternate may be DOS interrupt 25h which reads sectors within a partition.

Code Example

[ORG7c00h]; code starts at 7c00hxorax,ax; make sure ds is set to 0movds,axcld; start putting in values:movah,2h; int13h function 2moval,63; we want to read 63 sectorsmovch,0; from cylinder number 0movcl,2; the sector number 2 - second sector (starts from 1, not 0)movdh,0; head number 0xorbx,bxmoves,bx; es should be 0movbx,7e00h; 512bytes from origin address 7c00hint13hjmp7e00h; jump to the next sector; to fill this sector and make it bootable:times510-($-$$)db0dw0AA55h

After this code section (which the asm file should start with), you may write code and it will be loaded to memory and executed.

Notice how we didn't change dl (the drive). That is because when the computer first loads up, dl is set to the number of the drive that was booted, so assuming we want to read from the drive we booted from, there is no need to change dl.

INT 13h AH=03h: Write Sectors To Drive

Parameters
AH03h
ALSectors To Write Count
CHTrack
CLSector
DHHead
DLDrive
ES:BXBuffer Address Pointer
Results
CFSet On Error, Clear If No Error
AHReturn Code
ALActual Sectors Written Count

INT 13h AH=04h: Verify Sectors From Drive

Parameters
AH04h
ALSectors To Verify Count
CHTrack
CLSector
DHHead
DLDrive
ES:BXBuffer Address Pointer
Results
CFSet On Error, Clear If No Error
AHReturn Code
ALActual Sectors Verified Count

INT 13h AH=05h: Format Track

Parameters
AH05h
ALSectors To Format Count
CHTrack
CLSector
DHHead
DLDrive
ES:BXBuffer Address Pointer
4-byte address field
(applies to PC/XT 286,AT, PS/1 and PS/2)
ByteMeaningAllowable Values
1Track
2Head
3Sector
4Bytes/Sector0=128, 1-256, 2-512, 3-1024
Results
CFSet On Error, Clear If No Error
AHReturn Code

INT 13h AH=06h: Format Track Set Bad Sector Flags

Parameters
AH06h
ALInterleave
CHTrack
CLSector
DHHead
DLDrive
Results
CFSet On Error, Clear If No Error
AHReturn Code

INT 13h AH=07h: Format Drive Starting at Track

Parameters
AH07h
ALInterleave
CHTrack
CLSector
DHHead
DLDrive
Results
CFSet On Error, Clear If No Error
AHReturn Code

INT 13h AH=08h: Read Drive Parameters

Parameters
Registers
AH08h = function number for read_drive_parameters
DLdrive index (e.g. 1st HDD = 80h)
ES:DI [7] set to 0000h:0000h to work around some buggy BIOS
Results
CFSet On Error, Clear If No Error
AHReturn Code
DLnumber of hard disk drives
DH [7] logical last index of heads = number_of - 1 (because index starts with 0)
CX[7:6] [15:8] [7] logical last index of cylinders = number_of - 1 (because index starts with 0)

[5:0] [7] logical last index of sectors per track = number_of (because index starts with 1)

BL [7] drive type (only AT/PS2 floppies)
ES:DI [7] pointer to drive parameter table (only for floppies)

Remarks

  • Logical values of function 08h may/should differ from physical CHS values of function 48h.
  • Result register CX contains both cylinders and sector/track values, see remark of function 02h.

INT 13h AH=09h: Init Drive Pair Characteristics

Parameters
AH09h
DLDrive
Results
CFSet On Error, Clear If No Error
AHReturn Code

INT 13h AH=0Ah: Read Long Sectors From Drive

The only difference between this function and function 02h (see above) is that function 0Ah reads 516 bytes per sector instead of only 512. The last 4 bytes contains the Error Correction Code (ECC), a checksum of sector data.

INT 13h AH=41h: Check Extensions Present

Parameters
RegistersDescription
AH41h = function number for extensions check [8]
DLdrive index (e.g. 1st HDD = 80h)
BX55AAh
Results
RegistersDescription
CFSet On Not Present, Clear If Present
AHError Code or Major Version Number
BXAA55h
CXInterface support bitmask:
  • 1 – Device Access using the packet structure
  • 2 – Drive Locking and Ejecting
  • 4 – Enhanced Disk Drive Support (EDD)

INT 13h AH=42h: Extended Read Sectors From Drive

Parameters
RegistersDescription
AH42h = function number for extended read
DLdrive index (e.g. 1st HDD = 80h)
DS:SIsegment:offset pointer to the DAP, see below
DAP : Disk Address Packet
offset rangesizedescription
00h1 bytesize of DAP (set this to 10h)
01h1 byteunused, should be zero
02h..03h2 bytesnumber of sectors to be read, (some Phoenix BIOSes are limited to a maximum of 127 sectors)
04h..07h4 bytessegment:offset pointer to the memory buffer to which sectors will be transferred (note that x86 is little-endian: if declaring the segment and offset separately, the offset must be declared before the segment)
08h..0Fh8 bytesabsolute number of the start of the sectors to be read (1st sector of drive has number 0) using logical block addressing (note that the lower half comes before the upper half) [9]
Results
RegistersDescription
CFSet On Error, Clear If No Error
AHReturn Code

As already stated with int 13h AH=02h, care must be taken to ensure that the complete buffer is inside the given segment, i.e. ( BX + size_of_buffer ) <= 10000h

INT 13h AH=43h: Extended Write Sectors to Drive

Parameters
RegistersDescription
AH43h = function number for extended write
AL
  • bit 0 = 0: close write check,
  • bit 0 = 1: open write check,
  • bit 1-7:reserved, set to 0
DLdrive index (e.g. 1st HDD = 80h)
DS:SIsegment:offset pointer to the DAP
Results
RegistersDescription
CFSet On Error, Clear If No Error
AHReturn Code

INT 13h AH=48h: Extended Read Drive Parameters

Parameters
RegistersDescription
AH48h = function number for extended_read_drive_parameters
DLdrive index (e.g. 1st HDD = 80h)
DS:SIsegment:offset pointer to Result Buffer, see below
Result Buffer
offset rangesizedescription
00h..01h2 bytessize of Result Buffer (set this to 1Eh)
02h..03h2 bytesinformation flags
04h..07h4 bytesphysical number of cylinders = last index + 1
(because index starts with 0)
08h..0Bh4 bytesphysical number of heads = last index + 1
(because index starts with 0)
0Ch..0Fh4 bytesphysical number of sectors per track = last index
(because index starts with 1)
10h..17h8 bytesabsolute number of sectors = last index + 1
(because index starts with 0)
18h..19h2 bytesbytes per sector
1Ah..1Dh4 bytesoptional pointer to Enhanced Disk Drive (EDD) configuration parameters which may be used for subsequent interrupt 13h Extension calls (if supported)
Results
RegistersDescription
CFSet On Error, Clear If No Error
AHReturn Code

Remark

Physical CHS values of function 48h may/should differ from logical values of function 08h.

INT 13h AH=4Bh: Get Drive Emulation Type

Parameters
RegsitersDescription
AH4Bh = get drive emulation type
AL01
DLdrive index (e.g. 1st HDD = 80h)
DS:SIpoints to an empty structure for result . must be 13h in size
Results
RegistersDescription
CFSet On Error, Clear if No Error
AXReturn Code
DS:SIPoints to a specification structure
Specification Structure
OffsetSize (byte)Description
00h1Size of packets in byte (13h)
01h1Boot Media Type :
Bits
0 - 30000b: No Emulation

0001b: 1.2M Floppy Disk

0010b: 1.44M Floppy Disk

0011b: 2.88M Floppy Disk

0100b: Hard Disk

4-5Reserved
6Image Contain ATAPI Driver
7Image Contain SCSI Driver
02h1Drive Number (Drive Index)
03h1CD-ROM Controller Number
04h4Logical Block Address (LBA) of disk image to emulate
08h2Device Specification:

bit 0: Drive is slave instead of master

bits 7-0: LUN and PUN

0Ah2Segment Of 3K Buffer For Caching CD-ROMs Reads
0Ch2Initial Boot Image Segment Starting From 7c0h Segment
0Eh2Number Of Sectors (512 bytes long) To Load
10h1Cylinder Count Low Byte (From int 8h)
11h1Sector Count (From int 8h)
12h1Head Count (From int 8h)

See also

Related Research Articles

<span class="mw-page-title-main">Parallel ATA</span> Interface standard for the connection of storage devices

Parallel ATA (PATA), originally AT Attachment, also known as IDE, is a standard interface designed for IBM PC-compatible computers. It was first developed by Western Digital and Compaq in 1986 for compatible hard drives and CD or DVD drives. The connection is used for storage devices such as hard disk drives, floppy disk drives, and optical disc drives in computers.

<span class="mw-page-title-main">BIOS</span> Firmware for hardware initialization and OS runtime services

In computing, BIOS is firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process. The BIOS firmware comes pre-installed on an IBM PC or IBM PC compatible's system board and exists in some UEFI-based systems to maintain compatibility with operating systems that do not support UEFI native operation. The name originates from the Basic Input/Output System used in the CP/M operating system in 1975. The BIOS originally proprietary to the IBM PC has been reverse engineered by some companies looking to create compatible systems. The interface of that original system serves as a de facto standard.

<span class="mw-page-title-main">Booting</span> Process of starting a computer

In computing, booting is the process of starting a computer as initiated via hardware such as a button or by a software command. After it is switched on, a computer's central processing unit (CPU) has no software in its main memory, so some process must load software into memory before it can be executed. This may be done by hardware or firmware in the CPU, or by a separate processor in the computer system.

File Allocation Table (FAT) is a file system developed for personal computers and was the default filesystem for MS-DOS and Windows 9x operating systems. Originally developed in 1977 for use on floppy disks, it was adapted for use on hard disks and other devices. The increase in disk drives capacity required three major variants: FAT12, FAT16 and FAT32. FAT was replaced with NTFS as the default file system on Microsoft operating systems starting with Windows XP. Nevertheless, FAT continues to be used on flash and other solid-state memory cards and modules, many portable and embedded devices because of its compatibility and ease of implementation.

<span class="mw-page-title-main">Netwide Assembler</span> Assembler for the Intel x86 architecture

The Netwide Assembler (NASM) is an assembler and disassembler for the Intel x86 architecture. It can be used to write 16-bit, 32-bit (IA-32) and 64-bit (x86-64) programs. It is considered one of the most popular assemblers for Linux & x86 chips.

x86 assembly language is the name for the family of assembly languages which provide some level of backward compatibility with CPUs back to the Intel 8008 microprocessor, which was launched in April 1972. It is used to produce object code for the x86 class of processors.

<span class="mw-page-title-main">A20 line</span> Signal in the system bus of an x86-based computer system

The A20, or address line 20, is one of the electrical lines that make up the system bus of an x86-based computer system. The A20 line in particular is used to transmit the 21st bit on the address bus.

Disk formatting is the process of preparing a data storage device such as a hard disk drive, solid-state drive, floppy disk, memory card or USB flash drive for initial use. In some cases, the formatting operation may also create one or more new file systems. The first part of the formatting process that performs basic medium preparation is often referred to as "low-level formatting". Partitioning is the common term for the second part of the process, dividing the device into several sub-devices and, in some cases, writing information to the device allowing an operating system to be booted from it. The third part of the process, usually termed "high-level formatting" most often refers to the process of generating a new file system. In some operating systems all or parts of these three processes can be combined or repeated at different levels and the term "format" is understood to mean an operation in which a new disk medium is fully prepared to store files. Some formatting utilities allow distinguishing between a quick format, which does not erase all existing data and a long option that does erase all existing data.

Logical block addressing (LBA) is a common scheme used for specifying the location of blocks of data stored on computer storage devices, generally secondary storage systems such as hard disk drives. LBA is a particularly simple linear addressing scheme; blocks are located by an integer index, with the first block being LBA 0, the second LBA 1, and so on.

The Program Segment Prefix (PSP) is a data structure used in DOS systems to store the state of a program. It resembles the Zero Page in the CP/M operating system. The PSP has the following structure:

<span class="mw-page-title-main">SpinRite</span>

SpinRite is a computer program for scanning RAS Random Access Storage devices such as hard disks, reading and rewriting data using proprietary programming methods to resolve and retrieve data that is unreadable by DOS or Windows. The first version was released in 1987 by Steve Gibson. The current version, 6.0, was released in 2004., with ongoing development open to the public at https://www.grc.com/dev/spinrite/

BIOS implementations provide interrupts that can be invoked by operating systems and application programs to use the facilities of the firmware on IBM PC compatible computers. Traditionally, BIOS calls are mainly used by DOS programs and some other software such as boot loaders. BIOS runs in the real address mode of the x86 CPU, so programs that call BIOS either must also run in real mode or must switch from protected mode to real mode before calling BIOS and then switching back again. For this reason, modern operating systems that use the CPU in Protected mode or Long mode generally do not use the BIOS interrupt calls to support system functions, although they use the BIOS interrupt calls to probe and initialize hardware during booting. Real mode has the 1MB memory limitation, modern boot loaders use the unreal mode or protected mode to access up to 4GB memory.

<span class="mw-page-title-main">Cylinder-head-sector</span> Historical method for giving addresses to physical data blocks on hard disk drives

Cylinder-head-sector (CHS) is an early method for giving addresses to each physical block of data on a hard disk drive.

An Option ROM for the PC platform is a piece of firmware that resides in ROM on an expansion card, which gets executed to initialize the device and (optionally) add support for the device to the BIOS. In its usual use, it is essentially a driver that interfaces between the BIOS API and hardware. Technically, an option ROM is firmware that is executed by the BIOS after POST and before the BIOS boot process, gaining complete control of the system and being generally unrestricted in what it can do. The BIOS relies on each option ROM to return control to the BIOS so that it can either call the next option ROM or commence the boot process. For this reason, it is possible for an option ROM to keep control and preempt the BIOS boot process. The BIOS generally scans for and initializes option ROMs in ascending address order at 2 KB address intervals within two different address ranges above address C0000h in the conventional (20-bit) memory address space; later systems may also scan additional address ranges in the 24-bit or 32-bit extended address space.

<span class="mw-page-title-main">GUID Partition Table</span> Computer disk partitioning standard

The GUID Partition Table (GPT) is a standard for the layout of partition tables of a physical computer storage device, such as a hard disk drive or solid-state drive, using universally unique identifiers, which are also known as globally unique identifiers (GUIDs). Forming a part of the Unified Extensible Firmware Interface (UEFI) standard, it is nevertheless also used for some BIOS systems, because of the limitations of master boot record (MBR) partition tables, which use 32 bits for logical block addressing (LBA) of traditional 512-byte disk sectors.

An extended boot record (EBR), or extended partition boot record (EPBR), is a descriptor for a logical partition under the common DOS disk drive partitioning system. In that system, when one partition record entry in the master boot record (MBR) is designated an extended partition, then that partition can be subdivided into a number of logical partitions. The actual structure of that extended partition is described by one or more EBRs, which are located inside the extended partition. The first EBR will always be located on the very first sector of the extended partition.

A volume boot record (VBR) is a type of boot sector introduced by the IBM Personal Computer. It may be found on a partitioned data storage device, such as a hard disk, or an unpartitioned device, such as a floppy disk, and contains machine code for bootstrapping programs stored in other parts of the device. On non-partitioned storage devices, it is the first sector of the device. On partitioned devices, it is the first sector of an individual partition on the device, with the first sector of the entire device being a Master Boot Record (MBR) containing the partition table.

<span class="mw-page-title-main">Cosmos (operating system)</span> Toolkit for building GUI and command-line based operating systems

C# Open Source Managed Operating System (Cosmos) is a toolkit for building GUI and command-line based operating systems, written mostly in the programming language C# and small amounts of a high level assembly language named X#. Cosmos is a backronym, in that the acronym was chosen before the meaning. It is open-source software released under a BSD license.

A master boot record (MBR) is a special type of boot sector at the very beginning of partitioned computer mass storage devices like fixed disks or removable drives intended for use with IBM PC-compatible systems and beyond. The concept of MBRs was publicly introduced in 1983 with PC DOS 2.0.

The FAT file system is a file system used on MS-DOS and Windows 9x family of operating systems. It continues to be used on mobile devices and embedded systems, and thus is a well suited file system for data exchange between computers and devices of almost any type and age from 1981 through the present.

References

  1. 1 2 Brown, Ralf D. (2000-07-16). "Ralf Browns Interrupt List (v61 html)" . Retrieved 2016-11-03.
  2. 1 2 Brown, Ralf D. (2000-07-16). "The x86 Interrupt List (v61 original text) archive: "inter61a.zip", subfile: "INTERRUP.B", heading: "B-1302" (INT13, 02 Read), Notes" . Retrieved 2016-11-03.
  3. Disk size limitations, The 8.4 GB limit (and others)
  4. Stevens, Curtis (1995-01-26). "Enhanced Disk Drive Specification 1.1 -DRAFT- Phoenix Technologies, see 3.0 BIOS Extensions (registration required)" (PDF). Retrieved 2016-11-03.
  5. Landis, Hale (1995-02-11). "BIOS Types, CHS Translation, LBA and Other Good Stuff, See BIOS Type 6 The Phoenix Enhanced Disk Drive Specification. (registration required)" (PDF). Retrieved 2016-11-03.
  6. ctyme.com - Ralf Browns Interrupt List, Indexed html, DISK - READ SECTOR(S) INTO MEMORY
  7. 1 2 3 4 5 6 ctyme.com - DISK - GET DRIVE PARAMETERS (PC,XT286,CONV,PS,ESDI,SCSI)
  8. ctyme.com - IBM/MS INT 13 Extensions - INSTALLATION CHECK
  9. - LBA in Extended Mode