Skip to main content

The Rise of Microsoft, Part 8: 3.0

3.0

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

💻 The Rise of Microsoft — a 20-part series. See all parts »  |  « Part 7: The Youngest Billionaire

By the late 1980s, Microsoft owned the plumbing of the personal computer. MS-DOS ran on tens of millions of machines, and the money was rolling in. But DOS was a stubborn thing — a blinking C:\> prompt that demanded you memorize commands and type them exactly right. Across the industry, everyone agreed the future was graphical, with windows and icons and a mouse. The only question was whose graphical future would win.

Apple's Macintosh had shown what was possible back in 1984. Microsoft's own first two attempts at Windows, in 1985 and 1987, had landed with a thud — clunky, slow, and largely ignored. And Microsoft's official plan for the graphical future wasn't even Windows. It was OS/2, the operating system it was building hand-in-hand with IBM. Windows, as far as the partnership was concerned, was a dead end.

The skunkworks that shouldn't have existed

The third version of Windows very nearly didn't happen. While most of Microsoft's talent was pouring into OS/2, a programmer named David Weise became convinced the Windows project could be resurrected — if only it could break free of DOS's crippling memory limits. He teamed up with Murray Sargent, a physics professor Microsoft had recruited from the University of Arizona, who had written a tool called a DOS extender that let programs reach past the old barriers.

Starting in 1988, the two of them worked what amounted to a side project, rebuilding Windows' memory manager so that applications could run in the "protected mode" that newer Intel chips supported. In a matter of months they had a rough prototype running Word, Excel, and PowerPoint side by side. They showed it to Microsoft's executives, who were impressed enough to bless it as a real product. IBM was not amused: the company had bet on OS/2, and here was its partner quietly reviving the very thing it had written off. The relationship never fully recovered.

What made Windows 3.0 special under the hood was that it refused to choose a single kind of computer. It shipped with three operating modes and picked the right one for whatever machine it found itself on.

That flexibility was the quiet genius of it. The exact same box you bought at the store would run on a creaky 1984 machine and on a top-of-the-line 386 — and it got dramatically better as your hardware improved. For the first time, Windows could reach the memory above the ancient 640 KB ceiling that had haunted DOS users for a decade, and on a 386 it could juggle several DOS programs at once. The system finally felt like it had room to breathe.

The most expensive software launch ever

Microsoft knew it had something, and it spent accordingly. On May 22, 1990, the company unveiled Windows 3.0 at the New York City Center theater in front of roughly 6,000 people, with the event beamed live to seven other North American cities and a dozen more around the world. Microsoft poured about $3 million into the festivities — a staggering sum for launching a piece of software. Bill Gates called it "the most extravagant, extensive, and expensive software introduction ever."

The pitch was aggressive on price, too. A full copy carried a suggested retail price of $149, but existing Windows and runtime users could upgrade for just $50. And crucially, Windows now came bundled on new PCs from a growing list of hardware makers. Zenith Data Systems, Austin Computer Systems, and CompuAdd were first out of the gate, followed by more than 25 other manufacturers — conspicuously, everyone but IBM, which was still nursing its OS/2 grudge.

The version that made Windows unavoidable

This time it worked. Windows 3.0 was the first version to succeed both with critics and in the market, and it went on to sell around 10 million copies. Reviewers who had mocked earlier releases now praised its multitasking, its customizability, and above all its memory management — the very thing that had tortured users of Windows 1 and 2.

The look was a genuine leap. In place of DOS's wall of file names, the new Program Manager greeted you with tidy, clickable icons, and the File Manager let you drag your way through folders. Microsoft threw in a suite of little accessories — Paintbrush, Write, Notepad, a calculator, a clock — and a card game called Solitaire that, almost by accident, became one of the most effective pieces of software ever written. Millions of office workers learned to use a mouse by dragging virtual playing cards, one click at a time.

There was grumbling, too. Rival software makers complained that Microsoft was bundling its own applications with the operating environment, an early note in a chorus of antitrust complaints that would grow much louder over the coming decade. But in 1990 the message was unmistakable: the graphical PC belonged to Microsoft now, not to IBM's OS/2 and not to Apple. Windows 3.0 sold ten million reasons to believe it.

Next time: with Windows ascendant and OS/2 fading, the Microsoft–IBM marriage finally collapses — and the two giants go to war.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...