Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This gives a glimpse into how much various crap could end up installed as an Int 2F handler:

Lot's of crap in INT 21 too: https://fd.lod.bz/rbil/zint/index_21.html (on the whole I like this HTMLified version of Ralf Brown's Interrupt List better)

But I suppose they invented INT 2F to discourage people from doing that to INT 21.

And then Ralf Brown also proposed an alternative multiplex interrupt, INT 2D: https://fd.lod.bz/rbil/interrup/tsr/2d.html#4258



INT 21 was for DOS what INT 80 was for Linux: the gateway to the OS kernel.

Overriding software interrupt handlers was a common mechanism, applied to BIOS interrupts as well (e.g. there was a BIOS timer interrupt that was there just for that).

The idea was that programs would take over the interrupt vector then chain-call the previous handlers. One can still see something similar at play in certain scenarios with e.g. callbacks. The system/library doesn't have to maintain a list of clients.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: