3 ms·
No, there were MS-DOS interrupts for those as well. BIOS became more relevant for graphics programming as MS-DOS did not do graphics, only text mode. These be
by pjmlp 2y ago
No, there were MS-DOS interrupts for those as well.
BIOS became more relevant for graphics programming as MS-DOS did not do graphics, only text mode.
These became my bibles of the time,
"PC assembly language step-by-step"
https://archive.org/details/pcassemblylangua0000hoff https://archive.org/details/pcassemblylangua0000hoff
"Advanced assembly language on the IBM PC"
https://archive.org/details/advancedassembly0000holz https://archive.org/details/advancedassembly0000holz
"PC intern system programming : the encyclopedia of DOS programming know how"
https://archive.org/details/pcinternsystempr0000tisc https://archive.org/details/pcinternsystempr0000tisc
Last one is great, it has examples on Quick Basic, Turbo Pascal, Turbo C and C++, Microsoft C and C++, TASM and NASM.
- jbverschoor 2y agoThe interrupts were used to call bios commands. The whole DOS was only a tiiiny line between the bios. In fact, I think it really was only “DISK” os. Edit: https://mrszeto.net/CIT/interrupts.htm https://mrszeto.net/CIT/interrupts.htm DOS only did file system operations and a few date/time calls
- pjmlp 2y agoAnd since I listed all the books I used routinely I didn't know that. Parent, > I should know the answer to this, but was using the BIOS the only way to interact with hardware like disks, mice, and keyboard? First link from your URL > READ CHARACTER FROM STANDARD INPUT, WITH ECHO Also drivers loaded via config.sys would extend MS-DOS, and be exposed via additional interrupts, e.g 0x33h for mices. Now is interrupt 0x33h populated by MS-DOS, after loading a mouse driver configured in config.sys, still MS-DOS API or not?
- _mlbt 2y agoAnother great resource for DOS and BIOS programming is Ralph Brown’s interrupt list… http://www.cs.cmu.edu/~ralf/files.html http://www.cs.cmu.edu/~ralf/files.html