2 ms·
DOS did alright. It was never meant to be anything more than a basic CLI OS, and when everyone pushed it beyond that primary role, quirks and problems would app
by 1970-01-01 5y ago
DOS did alright. It was never meant to be anything more than a basic CLI OS, and when everyone pushed it beyond that primary role, quirks and problems would appear, just like any other complex program.
- Koshkin 5y agoThis doesn't sound right to me - there was plenty of GUI-based applications, and having DOS at the base was usually not a problem (as long as you have the right device drivers - a problem not exclusive to DOS).
- 1970-01-01 5y agoThere really weren't device drivers in DOS. Programs would include drivers for running peripheral devices, and then YOU had to configure each one to work with DOS. This was the biggest problem with DOS. These programs talked directly to the hardware. Once TSR drivers were combined with CD-ROM and sound drivers, things would be very quirky during a GUI install. I remember Peter Norton put out some very good DOS books, and he wrote a few chapters about common issues with "Multimedia PCs".
- p_l 5y agoI recall that Peter Norton was also considered responsible for why many DOS applications required pretty much error-for-error IBM compatibles - because he advocated for directly dealing with hardware and disregarding DOS APIs (which, admittedly, were bad)