INT 13H

INT 13h is shorthand for BIOS interrupt call 13hex, 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.

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 exactly 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 compatibilitydictatng 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 DHbut eventually the computer industry standardized on the interface developed in the Microid Research ("MR BIOS") in 1989.

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 TSR 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 B:" )
. . .
DL = 7Fh128th floppy disk)
DL = 80h1st hard disk
DL = 81h2nd hard disk
DL = 82h3rd hard disk
. . .
DL = E0hCD/DVD, 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 = 17hFD Set Media Type For Format (used by DOS versions <= 3.1)
AH = 18hFD Set Media Type For Format (used by DOS versions >= 3.2)
AH = 19h Park Heads
AH = 41hEXT Test 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 = 4Bh EXT Get Drive Emulation Type

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

  • FD: for floppy disk only.
  • HD: for hard disk only.
  • PS/2: for hard disk on PS/2 system only.
  • EXT: part of the INT 13h Extensions which were written in the 1990s to support hard drives with more than 8 GB.

INT 13h AH=00h: Reset Disk System

Parameters
AH 00h
DL Drive (bit 7 set means reset both hard and floppy disks)
Results
CF Set on error
AH Return Code

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

Parameters
AH 01h
DL Drive

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

Results
AH
Return Code
00h Success
01h Invalid Command
02h Cannot Find Address Mark
03h Attempted Write On Write Protected Disk
04h Sector Not Found
05h Reset Failed
06h Disk change line 'active'
07h Drive parameter activity failed
08h DMA overrun
09h Attempt to DMA over 64kb boundary
0Ah Bad sector detected
0Bh Bad cylinder (track) detected
0Ch Media type not found
0Dh Invalid number of sectors
0Eh Control data address mark detected
0Fh DMA out of range
10h CRC/ECC data error
11h ECC corrected data error
20h Controller failure
40h Seek failure
80h Drive timed out, assumed not ready
AAh Drive not ready
BBh Undefined error
CCh Write fault
E0h Status error
FFh Sense operation failed
CF Set On Error, Clear If No Error

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

Parameters
AH 02h
AL Sectors To Read Count
CH Cylinder
CL Sector
DH Head
DL Drive
ES:BX Buffer Address Pointer
Results
CF Set On Error, Clear If No Error
AH Return Code
AL Actual 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 := ( ( cylinder and 255 ) shl 8 ) or ( ( cylinder and 768 ) shr 2 ) or sector;
cylinder := ( (CX and 0xFF00) shr 8 ) or ( (CX and 0xC0) shl 2)
sector := CX and 63;

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.

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

Parameters
AH 03h
AL Sectors To Write Count
CH Track
CL Sector
DH Head
DL Drive
ES:BX Buffer Address Pointer
Results
CF Set On Error, Clear If No Error
AH Return Code
AL Actual Sectors Written Count

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

Parameters
AH 04h
AL Sectors To Verify Count
CH Track
CL Sector
DH Head
DL Drive
ES:BX Buffer Address Pointer
Results
CF Set On Error, Clear If No Error
AH Return Code
AL Actual Sectors Verified Count

INT 13h AH=05h: Format Track

Parameters
AH 05h
AL Sectors To Format Count
CH Track
CL Sector
DH Head
DL Drive
ES:BX Buffer Address Pointer
4-byte address field
(applies to PC/XT 286,AT, PS/1 and PS/2)
Byte Meaning Allowable Values
1 Track
2 Head
3 Sector
4 Bytes/Sector 0=128, 1-256, 2-512, 3-1024
Results
CF Set On Error, Clear If No Error
AH Return Code

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

Parameters
AH 06h
AL Interleave
CH Track
CL Sector
DH Head
DL Drive
Results
CF Set On Error, Clear If No Error
AH Return Code

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

Parameters
AH 07h
AL Interleave
CH Track
CL Sector
DH Head
DL Drive
Results
CF Set On Error, Clear If No Error
AH Return Code

INT 13h AH=08h: Read Drive Parameters

Parameters
Registers
AH 08h = function number for read_drive_parameters
DL drive index (e.g. 1st HDD = 80h)
ES:DI[7] set to 0000h:0000h to work around some buggy BIOS
Results
CF Set On Error, Clear If No Error
AHReturn Code
DL number 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
AH 09h
DL Drive
Results
CF Set On Error, Clear If No Error
AH Return 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
Registers Description
AH 41h = function number for extensions check[8]
DL drive index (e.g. 1st HDD = 80h)
BX55AAh
Results
Registers Description
CF Set On Not Present, Clear If Present
AH Error Code or Major Version Number
BXAA55h
CX Interface 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
Registers Description
AH 42h = function number for extended read
DL drive index (e.g. 1st HDD = 80h)
DS:SI segment:offset pointer to the DAP, see below
DAP : Disk Address Packet
offset rangesize description
00h1 bytesize of DAP (set this to 10h)
01h1 byteunused, should be zero
02h..03h2 bytes number of sectors to be read, (some Phoenix BIOSes are limited to a maximum of 127 sectors)
04h..07h4 bytes segment: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 bytes absolute 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
Registers Description
CF Set 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
Registers Description
AH 43h = 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
DL drive index (e.g. 1st HDD = 80h)
DS:SI segment:offset pointer to the DAP
Results
Registers Description
CF Set On Error, Clear If No Error
AHReturn Code

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

Parameters
Registers Description
AH 48h = function number for extended_read_drive_parameters
DL drive index (e.g. 1st HDD = 80h)
DS:SI segment:offset pointer to Result Buffer, see below
Result Buffer
offset rangesize description
00h..01h2 bytessize of Result Buffer (set this to 1Eh)
02h..03h2 bytesinformation flags
04h..07h4 bytes physical number of cylinders = last index + 1
(because index starts with 0)
08h..0Bh4 bytes physical number of heads = last index + 1
(because index starts with 0)
0Ch..0Fh4 bytes physical number of sectors per track = last index
(because index starts with 1)
10h..17h8 bytes absolute number of sectors = last index + 1
(because index starts with 0)
18h..19h2 bytesbytes per sector
1Ah..1Dh4 bytes optional pointer to Enhanced Disk Drive (EDD) configuration parameters which may be used for subsequent interrupt 13h Extension calls (if supported)
Results
Registers Description
CF Set 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
Regsiters Description
AH 4Bh = get drive emulation type
AL 01
DL drive index (e.g. 1st HDD = 80h)
DS:SI points to an empty structure for result . must be 13h in size
Results
Registers Description
CF Set On Error, Clear if No Error
AX Return Code
DS:SI Points to a specification structure
Specification Structure
Offset Size (byte) Description
00h 1 Size of packets in byte (13h)
01h 1 Boot Media Type :
Bits
0 - 3 0000b: No Emulation

0001b: 1.2M Floppy Disk

0010b: 1.44M Floppy Disk

0011b: 2.88M Floppy Disk

0100b: Hard Disk

4-5 Reserved
6 Image Contain ATAPI Driver
7 Image Contain SCSI Driver
02h 1 Drive Number (Drive Index)
03h 1 CD-ROM Controller Number
04h 4 Logical Block Address (LBA) of disk image to emulate
08h 2 Device Specification:

bit 0: Drive is slave instead of master

bits 7-0: LUN and PUN

0Ah 2 Segment Of 3K Buffer For Caching CD-ROMs Reads
0Ch 2 Initial Boot Image Segment Starting From 7c0h Segment
0Eh 2 Number Of Sectors (512 bytes long) To Load
10h 1 Cylinder Count Low Byte (From int 8h)
11h 1 Sector Count (From int 8h)
12h 1 Head Count (From int 8h)
gollark: That too.
gollark: Crime could probably be reduced a lot with mandatory cameras in every home and every room, and we don't do that (yet...) because people care about their privacy a decent amount in at least that visceral way.
gollark: There is, however, a safety/privacy tradeoff.
gollark: Yes, that is true.
gollark: I am composing an email to my local MP, who will probably come up with some meaningless response and ignore it.

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.