BIOS interrupt call

<a href="/facts/BIOS/AYYPUogS">BIOS</a> implementations provide <a href="/facts/Interrupts/Mm6C4rpc">interrupts</a> that can be invoked by operating systems and application programs to use the facilities of the firmware on <a href="/facts/IBM_PC_compatible/zGUpl7Sh">IBM PC compatible</a> computers. Traditionally, BIOS calls are mainly used by <a href="/facts/DOS/sWwDXNmX">DOS</a> programs and some other software such as <a href="/facts/Boot_loader/6sNpcLMK">boot loaders</a> (including, mostly historically, relatively simple application software that boots directly and runs without an operating system—especially game software). BIOS runs in the <a href="/facts/Real_mode/wfU8vfjn">real address mode (Real Mode)</a> 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 <a href="/facts/Operating_system/8XTuvMh2">operating systems</a> that use the CPU in <a href="/facts/Protected_mode/y5u3Gwqq">Protected mode</a> or <a href="/facts/Long_mode/ITshSuE6">Long mode</a> 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 <a href="/facts/Booting/j6N1kRpc">booting</a>. Real mode has the 1MB memory limitation, modern <a href="/facts/Boot_loaders/j6N1kRpc">boot loaders</a> (e.g. <a href="/facts/GRUB2/pbwqDCh1">GRUB2</a>, <a href="/facts/Windows_Boot_Manager/2IQuCy3Y">Windows Boot Manager</a>) use the <a href="/facts/Unreal_mode/W2ltI5QE">unreal mode</a> or <a href="/facts/Protected_mode/y5u3Gwqq">protected mode</a> (and execute the BIOS interrupt calls in the <a href="/facts/Virtual_8086_mode/f4fjXWdU">Virtual 8086 mode</a>, but only for OS booting) to access up to 4GB memory.
In all computers, software instructions control the physical hardware (screen, disk, keyboard, etc.) from the moment the power is switched on. In a PC, the BIOS, pre-loaded in ROM on the motherboard, takes control immediately after the CPU is reset, including during power-up, when a hardware reset button is pressed, or when a critical software failure (a <a href="/facts/Triple_fault/5hYJw4Mc">triple fault</a>) causes the mainboard circuitry to automatically trigger a hardware reset. The BIOS tests the hardware and initializes its state; finds, loads, and runs the boot program (usually, an OS boot loader, and historical <a href="/facts/ROM_BASIC/aTec7AQY">ROM BASIC</a>); and provides basic hardware control to the software running on the machine, which is usually an operating system (with application programs) but may be a directly booting single software application.
For IBM's part, they provided all the information needed to use their BIOS fully or to directly utilize the hardware and avoid BIOS completely, when programming the early IBM PC models (prior to the PS/2). From the beginning, programmers had the choice of using BIOS or not, on a per-hardware-peripheral basis. IBM did strongly encourage the authorship of "well-behaved" programs that accessed hardware only through BIOS INT calls (and DOS service calls), to support compatibility of software with current and future PC models having dissimilar peripheral hardware, but IBM understood that for some software developers and hardware customers, a capability for user software to directly control the hardware was a requirement. In part, this was because a significant subset of all the hardware features and functions was not exposed by the BIOS services. For two examples (among many), the MDA and CGA adapters are capable of hardware scrolling, and the PC serial adapter is capable of interrupt-driven data transfer, but the IBM BIOS supports neither of these useful technical features.
Today, the BIOS in a new PC still supports most, if not all, of the BIOS interrupt function calls defined by IBM for the <a href="/facts/IBM_Personal_Computer/AT/YEVHpWKF">IBM AT</a> (introduced in 1984), along with many more newer ones, plus extensions to some of the originals (e.g. expanded parameter ranges) promulgated by various other organizations and collaborative industry groups. This, combined with a similar degree of hardware compatibility, means that most programs written for an IBM AT can still run correctly on a new PC today, assuming that the faster speed of execution is acceptable (which it typically is for all but games that use CPU-based timing). Despite the considerable limitations of the services accessed through the BIOS interrupts, they have proven extremely useful and durable to technological change.

BIOS interrupt call open-in-new

BIOS interrupt call