Boot Camp: Why Your Dusty Pentium II Laughs at Your Brand-New Windows 11 Machine

Let's set the scene. It's a lazy Sunday afternoon. You crack open your sleek, impossibly thin modern laptop — the one that cost you twelve hundred bucks and has a processor that could theoretically simulate a small galaxy — and you hit the power button. Then you wait. Then you wait some more. A spinning circle. An update prompt. A login screen that loads in three stages for absolutely no reason. Maybe a little notification asking if you'd like to set up OneDrive. Again.

Meanwhile, in a garage in Tucson, Arizona, a guy named Dave has just powered on his 1998 Compaq Deskpro with a 300MHz Pentium II and 64 megabytes of RAM. It's running Windows 98 SE. It is fully at the desktop, mouse responsive, Minesweeper open, in approximately twenty-two seconds.

Dave is grinning. Dave has a point.

The Bloat Is Real, and It Has a Name

This isn't just nostalgia talking. The phenomenon is real enough that it has a name in developer circles: software bloat. Every layer of abstraction, every background service, every telemetry daemon phoning home to a corporate server farm, every auto-updater for an app you installed once in 2019 and forgot about — it all stacks up. Modern operating systems are, by almost any honest metric, enormous. Windows 11 requires a minimum of 64 gigabytes of storage just to install. Windows 98 fit comfortably on a single CD-ROM and still had room to spare.

That's not inherently evil. Modern operating systems do vastly more. They manage Wi-Fi, Bluetooth, touchscreens, virtual machines, cloud sync, accessibility services, and security layers that would have seemed like science fiction to the average 1998 user. But here's the uncomfortable question nobody in Redmond wants you to ask: how much of what launches at startup do you actually need?

Mark, a systems administrator from Columbus, Ohio, decided to find out. He spent three weekends last year running informal benchmarks between a restored Pentium III machine running Windows 2000 and a mid-range modern desktop running Windows 11. "The old box hit a usable desktop in under thirty seconds, consistently," he told us. "The modern machine — and this is a machine with an NVMe SSD, mind you — took between ninety seconds and two and a half minutes before it stopped thrashing the drive and let me actually do anything without lag."

He clarifies, generously, that the modern machine was doing more. But doing more that you didn't ask it to do, at startup, without your permission, is its own kind of problem.

The Philosophy of Doing Less, Better

There's a design philosophy baked into 90s computing that modern OS architects have largely abandoned: the idea that the machine exists to serve the user's immediate task, not the software vendor's ecosystem goals. Windows 95 and 98 were not exactly paragons of stability — the Blue Screen of Death earned its nickname honestly — but they were lean in ways that mattered. They started fast because they started small. The OS loaded, handed control to the user, and got out of the way.

This is partly why retrocomputing enthusiasts like to point out that a Pentium II running a period-appropriate OS feels, in a very specific sense, snappier than a modern machine. Not more powerful. Not more capable. But more immediately responsive to input in a way that registers in your fingers and your brain before your brain can explain why.

Susan, a software developer based in Portland who maintains a small collection of vintage machines including a gorgeous IBM ThinkPad 600 running Windows 98, describes it as "the absence of friction." "There's no moment where the machine is doing something I didn't ask it to do," she says. "I click a thing, the thing opens. That relationship feels almost radical now."

What Modern Designers Could Actually Learn

To be fair — and RetroBits is nothing if not occasionally fair — the retrocomputing community isn't entirely right that old equals better. Security alone is a reason modern systems run background processes constantly. A Windows 98 machine connected to the modern internet is essentially a welcome mat for malware. The complexity of contemporary software environments is not purely corporate greed; some of it is genuinely necessary infrastructure.

But the retrocomputing critique lands hardest not on features but on defaults. The argument isn't that modern operating systems shouldn't be capable of doing everything they do. It's that they shouldn't be doing all of it at boot, automatically, without asking. The 90s approach — where you largely got what you installed and nothing else — was a kind of accidental minimalism that produced machines that felt fast because they largely were.

Some developers are listening. The rise of lightweight Linux distributions like antiX and Puppy Linux — which can run on hardware so old it makes a Pentium II look cutting-edge — points to an audience that still values the lean-and-mean philosophy. Even within mainstream Linux, there's growing conversation about startup service management and reducing the default footprint of modern desktop environments.

The Benchmark That Broke Dave's Brain

Back to Dave in Tucson. He went further than just booting. He timed how long it took each machine — the Pentium II and a current-generation mid-range laptop — to open a text document, perform a find-and-replace operation, and save the file. The vintage machine, running a copy of Microsoft Word 97, completed the task in four seconds. The modern machine, running Microsoft Word 365 and needing to first finish syncing with OneDrive, took forty-one seconds before the document was fully editable.

"I'm not saying the old computer is better," Dave says, with the measured tone of a man who has had this argument many times. "I'm saying something has gone wrong when the old computer is faster at the thing you're trying to do right now." He pauses. "Also, Word 97 never once asked me if I wanted to try Copilot."

He has a point. Twenty-two seconds to a usable desktop. No telemetry. No update nag. No cloud sync spinning in the background like an anxious intern.

Maybe progress isn't always a straight line. Maybe sometimes it loops back around, taps you on the shoulder, and hands you a floppy disk with a knowing look.