16 ms·
The Life of MS-DOS
- achairapart 5y agoWell, the article misses version 5.0, which according to its rap-promo commercial[0] freed "45kb of memory at least"(!). [0]: https://www.youtube.com/watch?v=dmEvPZUdAVI https://www.youtube.com/watch?v=dmEvPZUdAVI
- 0xcde4c3db 5y agoNote that this was a big deal not because 45K was a lot of memory in general by that point, but because the first 640K ("conventional" memory) is special in DOS. If you didn't have enough of it free, many programs simply couldn't run, so having DOS itself take up significantly less of this memory was a big win.
- pdenton 5y agoThe article omits the incompatibility issues with Lotus, and the patent infringement lawsuit about DoubleSpace.
- mrlonglong 5y agoIt also omits mention about things like FreeDOS that's still being worked on today!
- paulryanrogers 5y agoIt is strange though I suppose it could be considered an independent reimplementation since there is no shared source. There's also DOSEmu and DOSBox, which while not directly bootable, are DOS environments.
- mrlonglong 5y agoI've wanted to re-implement DOS in pure assembler for years to have that lean and mean that uses less memory than MS-DOS but never had the time.
- ok123456 5y agoThe sources for MS-DOS have been floating around the net basically forever. The original first few releases are even on Microsoft's github. It largely is already in ASM. Some of the user programs are written in C. To me, it would be far more interesting to see what modern compilers and development tooling could do towards producing DOS programs and operating system extensions. The tooling from back in the day was very baroque. You had to rely on different mutually incomparable dos extenders to get around all the limitations. (Just try to find the documentation to Phar Lap 386 in 2022.)
- tored 5y agoWhat would writing DOS programs and extenders with modern tooling accomplish? Trying to understand the goal.
- ok123456 5y agoMaking easy to understand and maintain programs in C++, with compilers that can that can do aggressive optimizations and inlining that compilers of the day could not do. The STL didn't exist until the late 90s, and before C++98 it was a wild-west.
- krkixohjk 5y agoBut what is the goal in having maintainable ms-dos software? The OS is still ancient and lacks most every possible security measure. Every program can r/w any memory and so on…
- ok123456 5y agoThe fact that it gets out of your way is a feature. Why does security matter on a single user, non-multitasked environment with no networking? The netsec industrial complex has really set back computing.
- 5y ago
- Yhippa 5y agoI was a kid with not much else to do. We had a home PC and no internet connectivity. I spent so much time going through the MS-DOS manual and trying out all the commands. If only I had spent that time learning Linux commands...
- yokoprime 5y agoSame. MS-DOS was such a turd of an operating system. So much time fiddling with IRQ settings and disabling stuff to squeeze out just a little more conventional memory so I could play Warcraft II
- 13of40 5y agoI was at a conference or something one time and saw a talk by Bill Gates, where he said that they'd tried to convince IBM to use a 68000 CPU in the original PC. Imagine what DOS could have been with a 32-bit instruction set and 16MB address space from day one. A lot of the eccentricities of DOS at the API level stem from the limitations of the hardware.
- kwhitefoot 5y agoThen you have to explain why CP/M running on 8 bit hardware was so much better than DOS on 16 bit.
- 13of40 5y agoI've had pretty limited experience using CP/M - I think the last time I actually played with it was in the early 90s when some old guy I knew was still using it to run a BBS. As far as I recall it was just as atrocious as DOS and other things of that era, at least from a UX point of view. DOS's int 21h API is a close cousin of the system library in CP/M, so I'd expect the developer experience to be kind of similar. Is there something specific you think CP/M was doing better?
- lproven 5y ago
- rascul 5y agoThe article mentions MS-DOS 6.3 as the latest standalone version, but I can't find anything about it anywhere. PC-DOS had a 6.3, but as far as I know, MS-DOS only went to 6.22 before going to 7 (which was not shipped standalone).
- mobilio 5y agoI also note that. Probably typo mistake from author?
- ForOldHack 5y agoAgain, I was there. No. Microsoft stopped updating MS-DOS 6.0 at 6.2.2. I never saw DOS 6.3 ( There was a PC-DOS 6.3, which I think was unchanged except for "Disk Compression" . Next thing was the DOS 7.0 used to boot Windows 95 FE.
- jbverschoor 5y agoYeah 6.3 does not ring a bell here either
- jmclnx 5y agoIBM came out with PC-DOS 7.0 around 2000, it had fixes for the Year 2000 plus REX language. I still a copy of it somewhere.
- lproven 5y agoI saw that, too. I think it's a mistake. MS-DOS ended at 6.22. PC DOS started to significantly _diverge_ from MS-DOS thereafter, with PC DOS 6.3, then 7, then 7.01, then 7.1.
- marcodiego 5y agoThe DOS family tree lacks FreeDOS, the last remaining maintained DOS implementation.
- cout 5y agoWhere in the chart would you put FreeDOS? AFAIK it's not a direct descendant of any version of DOS on the chart but is a separate implementation.
- Fnoord 5y agoSince its 'compatible' it would sit alone, just like every other from scratch, compatible tree would. Perhaps with a notion that the source is available, FOSS licensed.
- shadowofneptune 5y agoQDOS itself was an independent implementation of CP/M. The cladogram doesn't follow cladistics as is.
- deckard1 5y agoDOSBox. Though technically an emulator. Most people that want an easy way to run old DOS apps are probably better served with DOSBox anyway.
- skissane 5y agoIn many cases better served by a fork of DOSBox, such as DOSBox-X [0] or DOSBox Staging [1]. The DOSBox development team really likes to take their time, and often rejects outside contributions. They are only interested in running games, so will even reject bug fixes, unless you can show the bug harms some game. They are still on SourceForge and Subversion, which also acts to discourage outside contributors. Overall a rather conservative and risk-averse approach. The forks are at GitHub, and have GitHub Actions for CI, and more modern build processes/etc. DOSBox-X wants to support running all applications, including non-games; DOSBox Staging has more of a games-centric focus, but still is much more open to new and improved features than the original DOSBox is. Both have a much faster development and release cycle, and are much more welcoming to new contributors. DOS itself may not be a moving target, but there is still a long way to go in supporting corner cases, features of the platform which applications rarely use, etc. [0] https://dosbox-x.com/ https://dosbox-x.com/ https://github.com/joncampbell123/dosbox-x https://github.com/joncampbell123/dosbox-x [1] https://dosbox-staging.github.io/ https://dosbox-staging.github.io/ https://github.com/dosbox-staging/dosbox-staging https://github.com/dosbox-staging/dosbox-staging
- timbit42 5y agoThere's not much about the life of MS-DOS there. It's mostly pre-history.
- edgyquant 5y agoFurther, it’s basically just a shortened version of the Wikipedia page
- malkia 5y agoWhen I discovered ProDos for Apple ][/e (Actually what I had the was the bulgarian clone called Pravetz 8C) I was so overjoyed (because at school MS-DOS is what we used on PC/AT/XT machines) and it was closer. Then I learned that there were even more options!
- ForOldHack 5y agoWOW! Pravetz! Tell us more! I have not heard that name in decades.
- malkia 5y agohttps://twitter.com/Foone/status/1300329063035232256 https://twitter.com/Foone/status/1300329063035232256
- oonerspism 5y agoAnother interesting page covering a period of MS-DOS history. Albeit incomplete and fairly editorial. https://forums.overclockers.com.au/threads/retro-faq-dos-1990-1994.1308634/ https://forums.overclockers.com.au/threads/retro-faq-dos-199...
- TazeTSchnitzel 5y agoMS-DOS did not run things behind the scenes in Windows 95, 98 or ME, no matter how convincing an appearance of this Windows gave. They are fully 32-bit operating systems that preferably use DOS only while booting, though they will fall back to DOS device drivers as a last resort when Windows drivers are missing. https://devblogs.microsoft.com/oldnewthing/20071224-00/?p=24063 https://devblogs.microsoft.com/oldnewthing/20071224-00/?p=24... (Arguably DOS was barely in the picture already by the time Windows 3.x's 386 Enhanced Mode came around. It is a hypervisor where DOS and Windows live in virtual machines!)
- ForOldHack 5y ago"Windows 95, though still being based on MS-DOS, was its own operating system, using a 16-bit DOS-based kernel and a 32-bit user space." "The Win32 API is implemented by three modules, each consisting of a 16-bit and a 32-bit component:" Fully?
- deleted 5y ago[deleted]
- TazeTSchnitzel 5y agoWell, the Windows 95 kernel is 32-bit. There are some 16-bit userland components.
- userbinator 5y ago386 Enhanced Mode actually is a hypervisor that runs DOS inside a virtual machine Windows/386 was the first version to do that, I believe. It's worth noting that it and its descendants were based around this hypervisor architecture but the fact seems to be little-known, perhaps because the virtualisation was so "transparent" (and allowing pass-through hardware access by default). Only later did things like Xen, KVM, QubesOS, etc. "rediscover" this architecture --- but with a "deny by default" model for security instead.
- WalterBright 5y agoI thought DESQview did that first.
- andai 5y ago>Because of its similarity to CP/M, it was easy to port programs originally designed for CP/M on 8080 and Z80 processors to QDOS, which targeted 8086 processors. I read somewhere[0] that a major reason for DOS's success was that it had thousands of programs "already written" for it on launch day due to backwards compatibility with CP/M software. Iirc the same article argued that backwards compatibility is Microsoft's (and Intel's) greatest strength. I can run programs compiled on Windows 95 on Windows 10 today. They go really far with this -- one version of Windows had a hack built into the kernel to work around a bug in SimCity![1] [0] Placeholder for source, if someone finds it! [1] https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost-the-api-war/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost...
- wtallis 5y agoA lot of that CP/M compatibility comes from the fact that the 8086 had a high degree of backwards compatibility with the 8080/8085 (and thus also the 8008). It wasn't actual binary compatibility, but the instruction set was either a strict superset or close enough (albeit with different encoding) that you could take an 8080 program written in assembly language and run it through an appropriate 8086 assembler to produce a valid 8086 binary. Since the processor made it possible to port software that seamlessly, it made sense for operating systems to also provide a compatible ABI.
- exidy 5y agoNot only this, but MS-DOS supported the CP/M style "Call 5" system call interface as well as the "modern" MS-DOS "int 21" system call interface, which is why to this day there is a jmp instruction at 0005h of the .com file format.
- justsomehnguy 5y ago> [0] Probably not the article you want, but has a little tidbits: https://news.ycombinator.com/item?id=27399039 https://news.ycombinator.com/item?id=27399039
- 5y ago
- curtis-paris 5y agoThis finally helps prove that I was right. I threw a test in high school when the computer teacher decided that his mainframe and cobol approach was the best. He said if I could pass his end-of-year test he would give me the permission to start coding in C++ (I already had Borland C++ at home and was WAY past all this). He was a complete dick about it. Mr. Crow. He can eat it now. I threw the test and intended to get a perfect 0%. One question that came up is what was the first operating system for the IBM computer system. It was PC-DOS because that's the contracted name. MS-DOS was the name for the generic Intel based system. I knew the answer. His answer sheet was WRONG. So I got 1 out of 40 questions right. I could have scored a 100% but I hated him as a teacher so much. His words were "You will never be anything in computers unless you can pass my class". Three letters to prove him wrong: CTO.
- alophawen 5y agoIt's probably time for you to let this one go, dude.
- dblohm7 5y ago“ Windows XP moved to the NT kernel, whose primary difference was moving away from a monolithic kernel to a hybrid kernel. With MS-DOS, the kernel and operating system exists completely within the kernel space. Windows NT uses a safer structure, where the kernel is split between the kernel space and the user space.” Yeah, that’s not what a hybrid kernel entails, and that is certainly not the primary difference between DOS and NT. I had to stop reading.