Re:CP/NC – a CP/M-compatible operating system
by kjs3 on Tuesday December 17, 2019 @07:38PM
(#21820675)
It was also about speed. For example, going through BIOS for video was slooooow, so most everyone went straight to the hardware, which buggered up anything that wasn't an MDA/CGA/EGA/VGA video adapter or near identical (like those with a NEC 7220...there were one or two). It meant things like the Wyse 700 (high-res mono video adapter) had to have application specific drivers.
Re:CP/NC – a CP/M-compatible operating system
by skissane on Tuesday December 17, 2019 @08:35PM
(#21820952)
In theory, they should have written to MS-DOS API, and then if BIOS video is slow, Microsoft (or OEMs) could have changed the MS-DOS console device driver to use direct hardware access. The problem was, everyone just went straight to the hardware so there was little impetus on anyone to write a faster console device driver for MS-DOS.
Re:CP/NC – a CP/M-compatible operating system
by abecedarius on Tuesday December 17, 2019 @09:35PM
(#21821240)
Iirc the bios interface was inherently slow: output was a character at a time, one bios call each. It’s been a long time, though.
That wasn't anything to do with the technical characteristics of MS-DOS versus CP/M. It was about the market conditions – for MS-DOS, the vast majority of users were running it on the IBM PC (and later compatible clones), so developers coded to the IBM PC BIOS and direct hardware access. With CP/M, hardware was far more diverse so developers had an incentive not to do that sort of thing.