Lunduke
News • Science & Tech
Quick and Dirty: The story of 86-DOS & MS-DOS
The hardware and nerdy details that led to the first release of MS-DOS.
January 19, 2024
post photo preview

MS-DOS is one of the most successful operating systems of all time — absolutely dominating the computer industry for years.

Most of us have heard the tales of how MS-DOS came into existence: How Microsoft purchased it from another company, and how Microsoft licensed it to IBM.

But what are the nerdy details? What is the background? What hardware inspired the development of that MS-DOS precursor… and what did those machines actually look like?

Let’s take a few moments to dive a little deeper into the history of how MS-DOS truly came into existence. To tell this story, we’ll need to go back to the mid 1970s…

1974 - The Altair 8800 & the S-100 BUS

Way back in 1974, the legendary Altair 8800 computer was being designed. And, as part of the system, the S-100 computer bus was designed.

The Altair 8800
 

Fun Factoids: The Altair 8800 was based on an Intel 8080 CPU clocking in at a whopping 2 MHz and sold, as a kit, starting at $439. That base model came packed with 1024 bytes of RAM. Yeah. You read that right. 1k. In order to run the new “Altair BASIC” — which was the first product of Microsoft — you first needed to upgrade to 4k of RAM… which would run another $264.

That S-100 bus — which allowed a number of peripheral cards (memory, drive controllers, etc.) to be inserted into, and used by, the computer — became the first expansion bus standardized across the computer industry.

In fact, usage of the S-100 became incredibly common among a huge number of homebrew computers built far and wide — being the defacto bus type until the IBM PC hit the scene in 1981.

Many of these computer types (using a variety of processors, including the 8080 and Z80) received ports of the CP/M operating system, developed by Gary Kildall’s Digital Research. CP/M was everywhere back then.

1979 - Seattle Computer Product’s S-100 8086 kit

Seattle Computer Products (SCP) (which, as the name would suggest, was based near Seattle, WA) produced a number of S-100 related products — including memory cards such as the 64k RAM board shown below:

Photo courtesy s100computers.com
 

Seattle Computer Products then expanded to produce boards and kits to build S-100 bus based computers using the Intel 8086 CPU (which had just been released by Intel).

SCP’s 8086 S-100 card. This is a later variant (1980 or 1981) of the original 1979 version.
 

There was just one teensy-tiny problem… there was no available operating system to ship with these S-100 based 8086 systems.

Initially these SCP S-100 8086 computers shipped with no full-fledged operating system at all.

But, instead, they worked with another local company — Microsoft — to bundle a version of their BASIC language. The result was known as “BASIC-86” and it was, essentially, a BASIC interpreter and editor, that booted from disk on the new SCP 8086 systems.

This wasn’t the only product that the two companies worked together on. Microsoft had also hired SCP to design their “Z-80 Softcard” for the Apple II platform.

 

This relationship — between Seattle Computer Products and Microsoft — would become critical to the entire computer industry.

Sales of the SCP S-100 8086 boards struggled due to the lack of operating system. Turns out most people want an OS to go with their computer. Who knew?

To remedy this problem, SCP encouraged Gary Kildall to port his wildly popular CP/M operating system to 8086 board (which Kildall had already been working towards anyway). Unfortunately the CP/M port was not shipping fast enough to meet the needs of SCP.

They needed an Operating System. And fast.

1980 - Quick and Dirty DOS

Seattle Computer Products did the only logical thing… they began building their own Operating System.

In April of 1980, Tim Paterson began working on exactly that. Armed with the manuals for CP/M, he began building his own “CP/M-like” operating system — from scratch — in assembly for their 8086 platform.

This effort was called “Quick and Dirty Disk Operating System”… or “QDOS” for short.

QDOS was incredibly similar to CP/M — as the design was done based on the CP/M manuals — and a key goal was to allow easy porting of CP/M software to QDOS. That said, it did differ in some noteworthy ways:

  • CP/M cached file system information, which could cause data loss if an update was not manually performed before a user removed a disk. QDOS changed this by doing disk updates on every write to the drive. This resulted in QDOS disk operations being slower than CP/M… but also protected against data loss.

  • Instead of CP/M’s file system, Tim used the FAT system that Microsoft created for the standalone BASIC-86 that SCP had already been shipping with their S-100 8086 machies.

Fun Factoid: The FAT (File Allocation Table) file system was developed by Marc McDonald — the first full time employee of Microsoft — and first used as the file system for “Microsoft Standalone Disk BASIC-80” (a bootable floppy for 8080 CPU’s that contained a BASIC interpreter). That was later ported to 8086 and was bundled with Seattle Computer Products 8086 systems.

QDOS required the SCP S-100 8086 systems, naturally, with a specific floppy drive controller: the Cromemco 4FDC, as pictured below.

Photo courtesy s100computers.com
 

By July of 1980, QDOS was functional — with roughly half of the outlined feature set. Then, by August, the famous EDLIN command was added.

Factoid time! The EDLIN program, a simple line editor, is the most enduring portion of this original version of QDOS. Lasting until this day, in various forms and ports, and being the primary text editor for MS-DOS up until the early 1990s. It was inspired by the ED commands of both CP/M and UNIX.

During the summer of 1980, the name QDOS was dropped (as “Quick and Dirty” isn’t the best product name) in favor of the, rather on-the-nose, “86-DOS”. A DOS. On the 8086 platform.

Bellow are a few screenshots of 86-DOS from the 1.0 version, which didn’t ship until 1981 (but still gives a good view of what it looked like back then):

COMMAND.COM and EDLIN
 
A DIR of an 86-DOS system

And, for the sake of posterity, here is the first part of the 86-DOS user manual for version 0.3. This is the very first published description — ever — of the OS that would later become MS-DOS.

At this point, Seattle Computer Products could begin bundling their S-100 8086 systems with the, now functional, 86-DOS.

Below you can see an advertisement of exactly that. A complete computer with an 8086 @ 8 MHz, 128k of RAM, the disk controller mentioned above… and shipping with both 86-DOS and Microsoft’s 86-BASIC. For a mere $3,349.

Ad for the SCP S-100 in the November, 1981 issue of Kilobaud Microcomputing magazine.
 

1981 - The Microsoft Agreement

Remember how Microsoft and Seattle Computer Products had worked together a few times already? Well, they were about to make an agreement that would change all of computing for decades to come.

Starting in November/December of 1980, Microsoft licensed a version of 86-DOS (version 0.3 to be exact) from SCP. This was a non-exclusive deal, meaning SCP could still sell 86-DOS and license to other OEMs.

Amazingly enough, a copy of one of that license — dated January 6th, 1981 — is now available so we can know the exact terms of the deal:

Document copy, courtesy Archive.org
 

That’s when things really took off. At an almost lightning speed.

Just a few short months later — in May — Tim Paterson left SCP and started working directly for Microsoft. His job: to port 86-DOS to the new IBM PC, which had an 8088 processor.

Then, in July of 1981 (just two months later), Microsoft purchased 86-DOS — in entirety — for an additional $50,000 (over the $25,000 MS had previously paid for a non-exclusive license). It was now Microsoft’s to do with as they please… and the original developer now worked for them.

That very next month, in August, Microsoft officially licensed MS-DOS to IBM… who then bundled it with their new IBM Personal Computer (the famous model 5150)… renamed “PC-DOS”.

Something wild to think about: Consider the timeline here.

  • The IBM 5150 PC was announced on August 12th, 1981.

  • The deal between Microsoft and IBM — for MS-DOS, renamed to PC-DOS — was finalized… that same month.

  • Microsoft didn’t actually own MS-DOS… until a few weeks before that.

  • … and Microsoft didn’t even have the developer (Tim Paterson) working for them until two months before that.

That’s right. One of the most important business deals in computer history… came together in a matter of just a few short months… with only days to spare.

Epilogue

There is oh-so-much more to this story. Too much to tell in one sitting.

  • MS-DOS would go on to absolutely dominate the computer industry and set the course of Microsoft for decades to come.

  • That version of CP/M that Seattle Computer Products wanted (before they gave up waiting and built QDOS)? It eventually shipped in November of 1981. CP/M was this close to being shipped with the first IBM PCs. You can mark that moment as the point when CP/M lost its position of market dominance.

  • The relationship with IBM and Microsoft would be a wild and rocky one — involving PC-DOS, OS/2 and many other products over the years.

  • Tim Paterson would end up working at Microsoft, multiple times, on several versions of DOS as well as Visual BASIC.

Fun personal anecdote: As a young man in the 1990s, I started working at Microsoft. One day, it occurred to me: “I wonder if Tim Paterson still works here?”

 

So I looked him up and, turns out, he did. In a building just around the corner from the one I was working in. So I did what any presumptuous, nerdy 19 year old would do… I sent him an email. One where I sounded like a giddy fanboy. Because that’s what I was.

 

Tim was gracious and kind. Taking time out of his schedule to chat with a fan of his work. While we only spoke on a few occasions, those moments meant a great deal to this young nerd.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
6
What else you may like…
Videos
Podcasts
Posts
Articles
4Chan Lawyer Says UK Demands Make Good "Bedding for My Pet Hamster"

UK is threatening to block 4Chan in 60 days if it does not comply with OfCom demands. In other news: 4Chan is censoring Lunduke Journal stories & suspending users who post them.

More from The Lunduke Journal:
https://lunduke.com/

00:17:10
October 14, 2025
The UK Begins Process of Blocking 4Chan in 60 Days

The United Kingdom Office of Communications (Ofcom) has issued a fine to 4Chan. If 4Chan does not pay the fine in 60 days, it can be blocked in the UK.

More from The Lunduke Journal:
https://lunduke.com/

00:10:08
October 13, 2025
Framework's Discord Moderators Go on Strike over "Fash" Software Support

Volunteer moderators have "taken a hiatus" in response to Framework supporting Omarchy Linux and Hyperland - which Leftists say have "Hitler Particles".

More from The Lunduke Journal:
https://lunduke.com/

00:24:12
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Now, let’s take a second to think about this. How can they access your BIOS remotely? Tell me again it isn’t just a back door with a marketing team behind it…

October 14, 2025

Heads up: The “Linux Sucks 2025” livestream planned for October 14 is being bumped out a couple days due to technical hiccups in the streaming setup.

Had streaming issues for the last several days, so makes sense to sort that out before doing a big show.

Updated schedule asap.

18 hours ago

In summary, although tech companies have money. When the AI boom goes bust. Data centers will lose. Like big fiber optic rollouts during the .com bust. Underutilized, sold and used to capacity far later than expected.

Another thought not mentioned in the article. Which I heard in a WSJ podcast and sounds about right. (Linked below the article. And let's just say the commentaror sounds less than manly...) Fiber optics doesn't need line upgrades once laid. It's a one time major capital expense. But data center CPUs will continue going obsolete, with a need for expensive upgrades. Else, they'll be slower than other options later. Which makes for a continual cost, once that time comes when they are being used to capacity.

Also, ordinary consumers do not want to "pay" for AI. That prevents ROI from looking good.

Big tech spending on AI data centers and infrastructure vs the fiber optic buildout during the dot-com boom (& bust) – IEEE ComSoc Technology Blog
...

post photo preview
The Unpublished Anti-Lunduke Hit-Piece
A Tech Journalist interviewed me for a hit-piece article. But the questions made them look bad, and they shelved the story. So I'm publishing their hit-piece for them.

Back in September, shortly after the assassination of Charlie Kirk, I was contacted by a Tech Journalist writing for FossForce.com (a smaller, Open Source focused publication) who was working on an article around Open Source, Antifa, and the Lunduke Journal’s coverage of those topics.

This particular outlet had, several months prior, run an “anti-Lunduke” hit piece without first reaching out for comment — which resulted in their most popular article (at least on social media) in quite some time.

With that in mind, it seemed reasonable that they’d want to repeat that success with another “anti-Lunduke” story.

This time they were doing the responsible thing. They reached out to the subject of the hit-piece article with questions. I like encouraging Tech Journalists when they do actual journalism, so I answered each and every query with easy-to-quote responses.

But, it would appear that the answers they received were not conducive to creating the hit-piece they were hoping for — my guess is they realized their questions made them look like the villain in the story. The villain they, clearly, hoped to portray me as.

They opted to not publish the piece.

So I’m publishing their hit-piece for them.

Below is every question — and every answer (with no edits) — which I was asked, on September 19th, by a Tech Journalist by the name of Christine Hall, writing for FossForce.

Fair warning: This is very, very politically charged.

Enjoy.


September 19th

Hall:

The last time I mentioned you in an article, you castigated me for not reaching out to you beforehand. Well, I’m reaching out now. We’ll see what comes of this.

You do recognize that the vast majority of organizations using the term antifa as a descriptor are not in the least bit terrorist and pose no threat to society -- and indeed, the only threats they might pose to fascist groups are not physical or life-harming?

Lunduke:

Hello Christine! Nice to hear from you!

Many, if not most, of those proclaiming support for Antifa (within Open Source) have also made statements encouraging or supporting violence and discrimination.

Regardless of that fact -- which I have documented extensively in Lunduke Journal coverage -- when violent acts are committed (such as murder, riots, and lynchings) in the name of “Antifa”, to turn around and immediately declare yourself to be “Antifa” is a clear declaration of support of that violence.

Hall:

And why did you feel it necessary to call out Danielle Foré’s [the founder of the elementary OS Linux Distribution] trans status in such an ugly manner?

Lunduke:

There is a noteworthy overlap between “Trans activism” and support for political violence -- including in the recent murder of Charlie Kirk (the murderer’s boyfriend was “Trans”).

In the case of Daniel Fore, he, a leader of an Open Source project, regularly calls for discrimination (and violence) against people he disagrees with -- often in conjunction with his self-declaration as “Trans”.

Thus, his declaration of being “Trans” becomes a part of the overall story.

It is worth noting here that The Lunduke Journal has never -- and would never -- call for discrimination or violence against someone because of how they identify or who they may (or may not) vote for.

This is in stark contrast those, such as Mr. Fore, who consider themselves “Trans” or “Antifa” -- who actively advocate for both discrimination and violence.

Hall:

Mentioning a person’s trans status in ways that are pertinent to your argument necessates rudeness such as calling her a “dude who likes to wear dresses”?

Lunduke:

Dan Fore is, in fact, a dude who likes to wear dresses.

The only reason to view that as a negative is if you view dudes wearing dresses as a negative.

Hall:

I’ll quote you on that, which I’m pretty sure won’t bother you in the least.

Lunduke:

Absolutely! Quote anything I say here. In fact, I suggest quoting absolutely everything I’ve written to you here, today.

Hall:

You also understand, don’t you, that voicing disagreement with an assessment made by POTUS is not only legal but a healthy part of the national dialog.

Lunduke:

Absolutely! Did I say somewhere that it was illegal to disagree with a politician? It seems unlikely that I have ever said that.

Hall:

Also, how would you reply to this:

There have been very few murders linked to individuals associated with Antifa, some incidents of rioting attributed to Antifa supporters, and no credible evidence of lynchings conducted in the name of Antifa. Compared to far-right groups, violence attributed to Antifa is much less frequent and lethal, with only one suspected kill—Aaron Danielson in Portland, by an anti-fascist activist—officially confirmed in recent U.S. history.

Lunduke:

Murder is bad. I am opposed to all murder.

In the context of these discussions, bearing in mind the Kirk murder is important (as many statements were made in response to it). The murderer of Kirk appears to have been pro-Trans and pro-Antifa (based on all available information).

Hall:

Is there any evidence that the suspect was part of an antifa group? I haven’t seen any.

Lunduke:

I have seen some reporting to this effect (including statements from family and messages he wrote).

But, far more important to this story, is the response to the murder among Antifa supporters (including those within Open Source). A large portion of Antifa supporters have celebrated the murder as justified because it killed someone they considered to be a “fascist”.

Hall:

Also, no group should be held responsible for what some deranged person who identifies with the group has done.

Lunduke:

I agree that a broader group should not be held responsible for the actions of a small number of individuals.

However, and this is critically important, it is entirely appropriate to hold people responsible for their own statements and actions.

With that in mind: The overall messaging of Antifa (and Antifa supporters) tends heavily towards violence. Punching, killing, molotov cocktails, etc. are all common messaging used by Antifa (including by those I quote within the Open Source world -- many of whom have advocated violence against myself).

Advocating for violence, then celebrating when violence is committed, are not good things.

Yet we see a great deal of that among Open Source supporters of Antifa.

Read full Article
October 13, 2025
Sale ends in a few hours, Lifetime Subs set up.

Holy moly, you guys are amazing.

A few days ago I published a “50% off” sale for Lunduke Journal subscriptions… and all of you showed up. In a big way.

To everyone who grabbed a Lifetime Subscription over the last few days: All of you are set to full Lifetime access. You should have a confirmation email in your inbox. If not, email me and I’ll make sure you’re setup properly.

That “50% off” sale ends tonight at midnight. So you have a few hours to snag a discounted subscription, if you haven’t already.

A huge thank you to everyone who supports this work. Couldn’t do it without you.

-Lunduke

Read full Article
October 12, 2025
50% Off Lunduke Journal Extended Through Monday (Oct 13th)

Just a quick heads up:

The “50% off every kind of Subscription to The Lunduke Journal” sale has been extended through Monday (October 13th).

So. You know. Grab one at 50% off between now and end of the day on Monday.

To all of you amazing nerds who have picked up a Lifetime Subscription already this weekend: You are awesome. You’ll be receiving a confirmation email, with all of the Lifetime Subscription details, by tomorrow (if you haven’t already).

Oh, and remember how we hit 11 Million views last month? Yeah. We’re well on our way to blowing past those numbers in October.

Wild.

See you all on Monday!

-Lunduke

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals