8 ms·
PC DOS Reimagined
- Crontab 6y agoAs an OS nerd, I find this very interesting. Thanks for posting it.
- curlypaul924 6y agoI remember when I first learned about multitasking. I think I read an article in Compute! or PC Magazine about Desqview or Concurrent DOS, and I remember wondering "Who would ever want to run two programs at the same time? Nobody has a multitasking brain!"
- loloquwowndueo 6y agoDesqview was acceptable to run a two-line Dial-up BBS on the same machine. It had stability issues beyond that so when the need arose for a third line we moved to OS/2 which was wonderful to multitask DOS applications in. The internet killed our little BBS before we had a need for four lines and beyond :)
- ghaff 6y agoThere was a cottage industry of software to get around DOS' single-tasking limitations. DoubleDOS was another program that let you have multiple sessions. There were terminate and stay resident (TSR) program like Sidekick.
- rbanffy 6y agoI always thought that TSR stood for "trash system randomly". I'll show myself out.
- myself248 6y agoMeanwhile I was clamoring to find a copy of DesqView as fast as I could, because my favorite MOD player had a DOS shell, but you had to exit your shelled-out program to return to the player and pick another song. That was acceptable for a quick dial-up-and-toss-a-mail-packet session, but not for door games or chat, so the prospect of being able to run something in an _alternate_ task, not a _parent_ task, was incredibly attractive.
- ta988 6y agoYep and then you get the 2000's brain that can't focus on a thing for more than a few minutes at a time.
- raphlinus 6y agoIf you want to match the font of the IBM PC technical documentation, it's ITC Garamond, not Times. Very characteristic of the era, Apple also adopted it (in it condensed variant).
- eqvinox 6y agoThis kinda happened in the UNIX world: https://en.wikipedia.org/wiki/C_shell https://en.wikipedia.org/wiki/C_shell
- icedchai 6y agoKinda, except that C shell syntax isn't very C language like. I think 8 bit micros (Apple II, Commodore 64) are closer. They booted up into BASIC and their DOS was an extension to BASIC.
- rbanffy 6y agoI like to say their OS shell was also an IDE.
- tssva 6y agoThe DOS for the Commodore computers including the above mentioned Commodore 64 was not an extension to BASIC. The DOS for Commodore computers instead ran on the floppy drive units themselves which included their own RAM and 6502 family CPUs to do so. The other 8-bit micro I used personally was the TRS-80 Model 1. It would boot directly to BASIC but their was no DOS as part of this basic. To use a floppy drive a DOS boot disk was required. There were a few different DOS's available for the machine. The official DOS available from Tandy was TRS-DOS.
- icedchai 6y agoRegardless of where it ran, to the C64 user, at a command level, it looked and acted like an extension to BASIC. You can see some examples of the basic code here: https://en.wikipedia.org/wiki/Commodore_DOS https://en.wikipedia.org/wiki/Commodore_DOS Apple ProDOS had similar stuff...
- skissane 6y agoTempleOS is written in a custom language inspired by C and C++ called HolyC. And HolyC is used as the shell. So that's actually much closer to what you are talking about than any Unix shell is (C shell included)
- kiwidrew 6y agoThis is very cool! The IBM PC (and clone) hardware was progressing rapidly at the time: from an 8-bit 8088 @ 4.77Mhz with 64-256K RAM to much much faster 16-bit 80286/80386 systems @ 16Mhz+ with 2-4MB RAM in just a few short years. As a consequence of this rapid progress, the software of the era didn't really exist for long enough to get heavily optimized and [with the exception of certain games] never pushed the PC/XT hardware to anywhere near its full capabilities.
- hakfoo 6y agoWhile the state of the art advanced fast, there was also a great deal of market spread. An early 386 would be several grand, but at the same time there were also floppy-only 8088 machines from about USD500 on up, and a significant installed base of XTs and clones. The software evolved far more slowly because of this-- you still had a lot of "It supports an 8088" or "it supports CGA" until the early 1990s.
- dragonwriter 6y agoSome nitpicks. (Mostly, “bitpicks”, I guess.) > from an 8-bit 8088 the 8088 was a 16-bit processor choked by pushing data through an 8-bit data bus. > 16-bit 80286/80386 systems Depending on exactly what period and systems you mean, this should probably be: 16-bit 8086/80286 (8086, of which the 8088 was the 8-bit-bus copy, was obviously earlier than 8088, but used later in PC clones) Or 16-/32-bit 80286/80386 (the 386 was a 32-bit processor.)
- ghaff 6y agoThe 286 was really a weird beast. It was a nice speed uptick from the 8088 but was still a 16-bit system in most respects. (As, truth be told, as was the 386 so long as it was still running DOS.)
- Koshkin 6y agoRe. i386, not exactly - there were numerous "DOS extenders" available, and some programs and games required it or included one on the install disk. DOOM, for example, used DOS/4G.
- indymike 6y agoMany other microcomputers of the era used BASIC as their shell Apple II, TI 99-4a, and the Commodore 64 are all examples of this. So the machine would boot to BASIC, and then you would call something like this (Commodore 64) from the BASIC prompt: LOAD "FILE",8 Computers with MS-DOS and CPM were different in that you would load a proper shell and launch basic from there. I seem to recall (I was 9 years old at the time) the original IBM PC having a less capable BASIC that could use a cassette tape for storage built in that would boot if you did not have a floppy drive or disk in the boot drive when the machine started.
- imoverclocked 6y agoUnless you inserted a cartridge into the C64 ... in which case there was no typing required!
- dvfjsdhgfv 6y agoSome, like the Commodore 128, had both: a "legacy" C64 style BASIC-enabled frontend, and another one: CP/M, the predecessor of DOS, quite popular in the 70s. I loved this combination of two very different worlds.
- anyfoo 6y agoIts BASIC frontend was not really legacy, instead the CP/M environment was basically tacked on. It had an entire separate CPU, an actual Z80, for that purpose, but unfortunately running CP/M was almost unbearably slow (which was not really the fault of the Z80). BASIC, in its upgraded version "BASIC 7.0" (compared to the C64's "BASIC 2.0") was quite obviously still the "main mode" and the one that supported all the C128's features. However, there was also a third mode, a "C64 compatibility mode", which removed (almost) all of the new features and presented itself exactly like a C64 would, same ROM and all.
- glhaynes 6y agoWhy was running CP/M so slow? I never got to run it but I don't think of CP/M as being a particularly bloated/slow OS; but you say it wasn't the fault of the Z80. Something particular to the C128?
- rbanffy 6y agoBefore OS/2, Microsoft had Xenix. It was the last good OS they ever shipped.
- cable2600 6y agohttps://en.wikipedia.org/wiki/Xenix https://en.wikipedia.org/wiki/Xenix But Xenix does not run DOS or Windows programs like OS/2 does. Microsoft needed the backwards compatibility to be able to sell the next DOS. When Microsoft split from IBM for OS/2 Microsoft's OS/2 NT 3.0 became Microsoft Windows NT 3.1
- oso2k 6y agoThere was also that XEDOS, that never officially saw the light of day. But some of those feature apparently made it into MS-DOS 2.x and appear as those *nix-like features that DOS had from 2.0+. https://youtu.be/Vo8NG8T4rWs https://youtu.be/Vo8NG8T4rWs
- skissane 6y ago> There was also that XEDOS, that never officially saw the light of day I wonder if XEDOS ever existed as actual code, as opposed to simply an item in a roadmap.
- rbanffy 6y agoWhen Microsoft first released Xenix, DOS wasn't a thing and GUIs were only available in rich research labs. Not being compatible with PC-DOS was not really an issue. As the IBM PC became Microsoft's passport to success, they ditched the Unixness of Xenix and embraced the CP/M-ness of PC-DOS. That's why people do dir in Windows instead of ls.
- marcodiego 6y agoThat could still be useful as a package for freedos I think.
- WalterBright 6y agoI remember being on a "compiler panel" AMA at a conference in the late 1980s. There were 5 of us on the panel, each representing a different C compiler. I was in the middle. We got asked "does your compiler system work on a floppy only machine?" Vendor1: "Yes. We have a special install for it, carefully distribute the files among floppies, and you can do it." Vendor2: "Yes, we can do it. It has a special install, blah blah blah." Me: "Yes. It costs $200 extra and comes with a hard disk." The question never progressed to Vendors 4 and 5, the question never came up again from anybody. That marked the end of the floppy-only era as far as I was concerned :-) It still took some more years before we could stop distributing the compiler on a stack of floppies and go with a CD. P.S. The price of a "hard card" (a hard disk on an expansion plug-in card) was $200 at the time.
- aidenn0 6y agoThat's a brilliant answer. As someone who has worked supporting a commercial compiler, it never ceases to amaze me how companies will pay 6 figures per seat for development tools, and then install them on a 5 year old machine that wasn't fit for the title "workstation" when it was brand new.
- WalterBright 6y agoTrue, that does happen, but at Zortech we discovered that the professional segment of the market was not price sensitive for just that reason - the price of the dev tools was noise compared to the cost of developer time.
- dragonwriter 6y ago> As someone who has worked supporting a commercial compiler, it never ceases to amaze me how companies will pay 6 figures per seat for development tools, and then install them on a 5 year old machine that wasn't fit for the title "workstation" when it was brand new. Well, because the dev shop buys the dev tools, but general desktop IT buys the computers, with policies around limiting number of different builds in the organization for IT convenience, and distribution policies for new machines based on internal politics (if you are in th chain of command above the head of the unit in charge of the hardware, or politically connected to someone in that position, you and your staff can get newer, better machines, whether or not you have a real business need, and even if that means denying someone else with a real business need.) Or, at least, I've seen enterprise shops like that.
- 29athrowaway 6y agoIn the DOS era, my favorite DOS was DR-DOS, which was much better than MS DOS in my opinion. Although I cannot remember exactly why, since this was decades ago. Unfortunately Microsoft did everything in its power to kill it. > "If you're going to kill someone there isn't much reason to get all worked up about it and angry. Any discussions beforehand are a waste of time. We need to smile at Novell while we pull the trigger." - Jim Allchin, Microsoft Co-President, on a memo about DR-DOS.
- throwaway_dcnt 6y agoSpeaking of multi-tasking, I remember writing code that hijacked timer interrupt to surreptitiously perform background tasks. I would also hijack interrupt 9 (I think) to capture keyboard so that I would pop up a small text mode window to display the current state/status when you clicked the magic key combo (ctrl+shift+9 for example). The dialog would vanish and background restored as soon as the keys were let go. Miss that time. The size of my binary was a little over 1K (written in assembler).
- unnouinceput 6y agoTSR days, heh? Good times
- Threeve303 6y agoDesqview is a name I have not heard in some time. Pretty revolutionary at the time, for someone who only knew traditional DOS, and was a sign of other multitasking window managers to come.