Re:What's the difference between the com and exe extensions?...
by vram22 on Tuesday June 06, 2017 @12:11PM
(#14498333)
Interesting, didn't know that there were 4 groups. I do remember INT 21H and setting a value in a register to specify what syscall you want run. Turbo Pascal had some support for assembly and even register handling, IIRC, so you could write such low-level programs in it. Also had absolute memory addressing which could be used for anything where you need to manipulate fixed, known memory addresses, such as video RAM.
CPU interrupts - handlers for CPU errors like division by zero (0h) or overflow (4h).
IRQ interrupts - handlers for hardware events; e.g. hardware timer (8h) or keyboard (9h).
BIOS interrupts - for BIOS-implemented syscalls; e.g. video output (10h) or sector-oriented disk I/O (13h). Also callbacks to be invoked by BIOS, like the aforementioned 1Ch for configurable timer.
DOS interrupts - for DOS-implemented syscalls; mostly this was 21h with actual syscall ID in the register. This is where you got things like file-oriented I/O, and some basic memory management.
And then there was "everything else", meaning things installed by third party TSRs and drivers. For example, 33h for the Microsoft mouse driver (which all other mouse drivers promptly copied, so it became the de facto standard mouse API in DOS), or 3Eh for Borland's software floating point emulator.
Of these, only the first two are actually "special" as far as hardware is concerned - the rest is just convention.