If you are looking for a text-mode editor which is simple to use but has much more functionality than edit, or if you are allergic to Microsoft, check out (figuratively, or literally, if you want to compile it yourself!) fresh, blazing fast, written in rust, available for all major platforms.The open-source remake of the old MS-DOS Editor isn’t actually the same app as the old EDIT.COM, but its heart is in the right place.
I always thought it stood for Disk Operating System. I was fucking around with it back in the early 80's after I got out of the Navy, and had taken some BASIC courses. I wrote a program to find out how what kind of acceleration was needed to get from Triton to Earth in 10 days as part of a book I was writing then.I just knew the acronym QDOS (Quick and Dirty Operating System), when I read 86-DOS I thought it was something different I did not know about… good to know we got the story right
https://en.wikipedia.org/wiki/86-DOS
Remember piggybacking DIP packages one on top of another and running fly wires for an address line?Having grown up in the 80s and 90s as a huge need, seeing things that are for me a lived experience (ok this particular case is a bit old even for me) being pulled from old documents, diskettes, and roms is an odd experience.
I was watching a video of someone restoring an old 286 and they discussed how the SIPP modules were short-lived and hard to come by - triggering memories of wanting to upgrade my first computer (amd 286) with a little more RAM, and getting 2MB of free simms and trying to solder pins on to fit the motherboard. I ended up not successful but was able to trade someone simms for sipps and get a whopping 4MB running.
Looking it up, people have compiled the previous open-sourced DOS releases from source.Of course, the value is only historical - has anyone tried to compile/assemble one of the MS-DOS sources? are the tools still available/usable?
I find it ironic that OCR should have that much trouble with a print out of that era, given that the two main modes of printing back then was either typographical, like a daisy wheel printer or dot matrix. No fancy fonts, very regular character size and spacing, still quite mechanically generated, every character and symbol was discreetly different, and the total set size of characters was quite finite. I would have thought that it would have been "Easy Mode" for an OCR.This source code is old enough that it hadn’t been stored digitally. “A dedicated team of historians and preservationists led by Yufeng Gao and Rich Cini,” calling itself the “DOS Disassembly Group,” painstakingly transcribed and scanned in code from paper printouts provided by Paterson. This process was made even more difficult because modern OCR software struggled with the quality of the decades-old printout.
Yeah. The ink wasn't evenly distributed across the lines, since the thing holding the ink was a ribbon flying back and forth that may well have dried out.I find it ironic that OCR should have that much trouble with a print out of that era, given that the two main modes of printing back then was either typographical, like a daisy wheel printer or dot matrix. No fancy fonts, very regular character size and spacing, still quite mechanically generated, every character and symbol was discreetly different, and the total set size of characters was quite finite. I would have thought that it would have been "Easy Mode" for an OCR.
It's an interesting read, although it was mildly amusing that they were OCRing text from ruled paper, removed the rule lines during the early processing, and then put in significant effort to apply a grid to help localize the characters. There were some other techniques they could have used for other challenges they ran into. But there's more than one way to OCR a cat, as they say...I find it ironic that OCR should have that much trouble with a print out of that era, given that the two main modes of printing back then was either typographical, like a daisy wheel printer or dot matrix. No fancy fonts, very regular character size and spacing, still quite mechanically generated, every character and symbol was discreetly different, and the total set size of characters was quite finite. I would have thought that it would have been "Easy Mode" for an OCR.
Having grown up in the 80s and 90s as a huge need, seeing things that are for me a lived experience (ok this particular case is a bit old even for me) being pulled from old documents, diskettes, and roms is an odd experience.
Also, they've been sitting (somewhere) for a long time- fading wasn't likely regular, there may be folds, creases, ink wiped off or stained.
That's the most common full-word meaning for DOS, and one IBM and MS used on official releases:I always thought it stood for Disk Operating System.
Well, no. He was paid to maintain it:So even from the beginning of time the entirety of what we know to be "secure operating system" was just being thanklessly maintained by some dude.
https://xkcd.com/2347/
Microsoft, on the hook to provide an operating system for the still-in-development IBM PC 5150, licensed 86-DOS and hired Paterson to continue developing it
DOS is actually a pretty generic acronym for Disk Operating System, "QDOS" was an internal joke name.To find out that it (at least originally) stood for "Dirty Operating System" is kind of an eye-opener.
Its college, 1983 flashback for me. OG PC, dual floppies, pre-XT release with 5MB HDD.The lede image is giving me serious flashbacks. Just not sure if it's nostalgia or PTSD...
That's the most common full-word meaning for DOS, and one IBM and MS used on official releases:
View attachment 134117
Also, keep in mind that PC-DOS/MS-DOS wasn't the first to use the name "DOS". Apple DOS predated it by a few years, for example.
https://en.wikipedia.org/wiki/Apple_DOS
https://en.wikipedia.org/wiki/List_of_disk_operating_systems_called_DOS
This video goes into the first commercially released DOS for a microcomputer, FDOS (Floppy Disk Operating System) by iCOM for the Intellec 8, released in 1975.
View: https://www.youtube.com/watch?v=TpHKygZ7OHY
If it was printed out on thermal paper, expect lots and lots of fading. I remember seeing all the saved "preorder slips" for Duke Nuke Them Forever. They were barely legible.A bit like watching archeologists carefully brushing the soil away from a skeleton in the ground and realizing, "Hey, that's granny."
...not to mention scruff marks from shoes on desks during photoshoots...
![]()
86?! THEY MEAN TO KILL DOS!I just knew the acronym QDOS (Quick and Dirty Operating System), when I read 86-DOS I thought it was something different I did not know about… good to know we got the story right![]()
Little bit of both for sure. Learning to program on a system not too different than that was... simpler times. I still remember the super satisfying clack that those power switches made, and the sound of sliding the steel shell off because the damn thing wouldn't boot. Also slicing my knuckles up on the solder joints on the back of the expansion cards. Spending a day with a multimeter and scope trying to find a bad trace on a card, finding it, and then soldering a jumper between the pins and getting the thing to work was so satisfying in a way that today's tech just doesn't allow for.The lede image is giving me serious flashbacks. Just not sure if it's nostalgia or PTSD...
Around 2013, I required an IBM-compatible PC with at least DOS2.0 or higher with a parallel port...needed to reprogram n 80s vintage digital lighting dimmer-brain because my boss wiped the settings dusting it out. The support manual for that system fortunately had the original 5.25" floppy.The oldest version that I have used is MS-DOS 2.0 in several 286 computers. The last time I say it being used for actual work was in 2007, a reminder that thing is not Y2K proof.
That would be windows NT, the close cousin to os/2...., but it would have been interesting to see what a PC-DOS (and OS/2 Warp) timeline would have been like. The DOS games would have been fine at least.
the picture is missing a mountain dew.
With that as the basis for 2000 and then XP, we effectively got that then.That would be windows NT, the close cousin to o/2.
That fork came pretty late, only diverging in MS/PC DOS 6, DOS 5 was the last one with shared code. Funnily enough 5 was still the target for NTVDM even after all these yearsSo far they've released code from back when PC-DOS and MS-DOS were just branding on top of the same program, since MS was doing work for IBM at the time and that's the arrangement they had, where IBM would just rebrand and sell the OS after MS had been paid, but they both could sell it under their own branding.
Then, MS left that comfy arrangement, forcing PC-DOS to fork away from MS-DOS into it's own thing, a thing which was actually pretty capable. My dad was the primary computer guy in the house when I was growing up, so I saw the PC bounce back and forth between PC and MS DOS a few times, and once even dabble in DR-DOS. Ultimately, when it became clear that MS-DOS was the only stable way to get newer versions of Windows (95 on up) working, that became the standard I stuck with, but it would have been interesting to see what a PC-DOS (and OS/2 Warp) timeline would have been like. The DOS games would have been fine at least.
If I recall correctly win95 didn't require DOS installed, it had its own version it installed.Ultimately, when it became clear that MS-DOS was the only stable way to get newer versions of Windows (95 on up) working
I did some work on a non-PC 8088 board in the 1980s. I used a cross assembler on a VAX to build the code. There was a monitor ROM that would load code into RAM from a serial port. Final code would be burned into an EPROM.How were the earliest versions of DOS created? What I mean is, presumably either Paterson used some other OS, or maybe no OS at all? I recall reading somewhere that for early development work, Microsoft used to use a PDP/11, I think running Unix, to do development of some of their software like early versions of MS-BASIC.
So, was Paterson working on some other computer platform, such as a PDP/11 or other mini computer, writing, I presume assembly language for Intel 8086, and using a foreign-cpu assembler to create binaries of DOS on that mini-computer, write the binary object code to a floppy disk, then boot that on his PC to test it?
Or, alternatively, I think one didn't actually HAVE to use any OS at all - I recall some software for the early PCs came on boot floppies and you could boot up the software straight into the app - I guess it probably used BIOS calls for a lot of lower level stuff like disk access, and probably used their own sort of proprietary "filesystem", or no filesystem at all - just writing data straight to disk without using a concept of files - treating it more like non-volatile memory?
So, maybe there was an 8086 editor/assembler on a boot floppy, and he could boot into that, write assembly code, save it to a second floppy disk, assemble it, write the built kernel and utils it to a third floppy disk (presumably formatted with some early flavor of FAT filesystem), then reboot into his DOS to test it?
Catchphrase was 'Up and at them!' I'm guessing.If it was printed out on thermal paper, expect lots and lots of fading. I remember seeing all the saved "preorder slips" for Duke Nuke Them Forever. They were barely legible.
Yep, in a game where you play as a Captain Planet villain.Catchphrase was 'Up and at them!' I'm guessing.