2 ms·
You're vastly understating just how commonly people would butt head with those limits though. You're also forgetting just how painful it was setting up a worki
by hnlmorg 5y ago
You're vastly understating just how commonly people would butt head with those limits though.
You're also forgetting just how painful it was setting up a working autoexec.bat file in the first place. Never mind having dedicated chunks of code for some games and not others (eg do I need a mouse in this game? that driver is incompatible with this other bit of software, etc), just discovering what precise string of characters in your autoexec.bat was required to load the damn driver could be downright cryptic at times.
DOS wasn't that great. We remember it with rose tinted glasses because that's what humans do. But DOS wasn't a particularly good operating system, even for its era.
Gaming on DOS, now that was fun. But I'd argue it was fun in spite of DOS rather than because of it
- ghaff 5y agoOnce you get into games, especially beyond monochrome text-based or maybe CGA, you were already pushing the limits. DOS was an OS for essentially text-based office apps in the early 80s and it just got pushed well-beyond that over time. And, yes, it made getting it set up for anything that wasn't a lowest common denominator setup very challenging.
- hnlmorg 5y agoIn which case you've basically described the vast majority of DOS's common use cases. So why even argue against my point? Also there were plenty of text-based office apps that required their own dedicated autoexec.bat config too.