The Multi-Boot Odyssey: Breaking the Installation Mold with Windows NT 3.5.1

Breaking the Installation Mold

with Windows NT 3.5.1

Today's leg of the multi-boot odyssey ventured into uncharted territory: Windows NT 3.5.1. This early iteration of NT piqued my curiosity – could it, like Windows 95, handle FAT32 partitions? Little did I know, this foray would challenge my preconceived notions of multi-booting.

With DOS 6.22 and Windows 3.11 already residing on the system, I prepped for a standard multi-boot installation. But Windows NT had other plans. During the setup process, a message popped up, unlike anything I'd encountered before:

"Setup has found a previous version of Microsoft Windows on your hard disk in the directory shown below

D:\Win311

Setup recommends installing Microsoft Windows NT in the same directory. This will WIndows NT interoperate with the previous version of windows"

It then suggested installing NT in the same directory as Windows 3.11, promising "interoperability" between the two.

Rethinking Multi-Boot Rules

Conventional wisdom dictates that each operating system in a multi-boot setup needs its own dedicated directory, with the earliest version installed first. However, this encounter with NT threw a wrench into those assumptions. Here was a clear exception to the "rule," and it piqued my adventurous spirit.

Embracing the spirit of experimentation, I opted to follow the installer's suggestion. After all, "interoperability" sounded fantastic! And indeed, it turned out that Windows NT wasn't just playing nice with its older sibling; it offered the option to import elements from Windows 3.11, much like how Firefox might import settings from Internet Explorer.

This unexpected twist highlights the beauty of diving deeper into the world of legacy software. It's a constant reminder that there's often more than meets the eye, and sometimes, breaking the established "rules" can lead to fascinating discoveries.

 The Blue Screen of Despair (and the Joy of Obscure Knowledge)

Our multi-boot adventure continues, and this time, we encountered a formidable foe – the dreaded Blue Screen of Death (BSOD). Just as the setup for Windows NT 3.5.1 seemed to be progressing smoothly, the reboot delivered a chilling message: "INACCESSIBLE_BOOT_DEVICE." Panic threatened to set in, but then, a glimmer of hope emerged.

Thankfully, Microsoft's knowledge base articles, even for discontinued operating systems like NT 3.5.1, haven't vanished into the digital abyss. Through the power of internet research, we unearthed the culprit – the pesky optical drive! Disconnecting it proved to be the magic bullet, banishing the blue screen and allowing the installation to proceed.

Beyond the "Next" Button: The Nuances of NT Installation

Now, for those who favor a more streamlined approach to installation (think clicking "Next" repeatedly), this might seem like an unnecessary hurdle. However, the charm of this multi-boot odyssey lies in the journey itself, in delving deeper than the surface-level experience of modern installers.

Unlike its user-friendly successors, Windows NT 3.5.1 lacks the luxury of a convenient "SETUP.EXE" or an "INSTALL.BAT" file. It demands a more hands-on approach, requiring users to directly execute "WINNT.EXE" from the root of the installation disc.

Floppy Fiasco and the Allure of the Switch

Adding another layer of complexity, the default installation process relies on a staggering number of floppy disks – over 30 by some estimates! Thankfully, we have the "/b" switch on our side. This magic command enables a floppy-less installation, a godsend in an age where floppy drives are becoming relics of the past.

However, a minor quirk emerged. The installer, seemingly programmed for a world dominated by CDs, appears to struggle with the concept of running from the local hard drive or a network drive. While this might seem like a minor technicality, it serves as a reminder of the evolving landscape of software installation over the years.

Workstation Dreams and Domain-Free Destinations

It's important to note that this particular adventure focuses on the Workstation version of Windows NT 3.5.1. Domain functionalities aren't on the agenda for this rig. Our goal is to create a diverse multi-boot environment, not a miniature network empire.

Detours and Discoveries on the Road to Nostalgia

The quest for multi-boot mastery continues, and this week's episode is a testament to the unexpected twists and turns that lie in wait for the intrepid explorer. Buckle up, fellow retrocomputing enthusiasts, for a tale of near triumphs, roadblocks, and a glimmer of a new path forward!

NT 3.5.1: A Glimpse into the Windows Past

First up, we delved into the intriguing world of Windows NT 3.5.1. A cursory glance revealed applets with a familiar layout, reminiscent of Windows 95, yet nestled within a 3.11 environment. The allure of experiencing this relatively obscure operating system was palpable – a chance to witness a bygone era of Windows firsthand. Installation excitement coursed through our veins!

The Impasse of Windows 98

Alas, fate had other plans. When we attempted to install Windows 98, the stubborn beast refused to acknowledge the presence of its older siblings, even when armed with the fabled /NTLDR switch. A quick revisit of the multi-boot project resources confirmed our suspicions: the provided instructions assumed a pristine environment, starting with DOS and then progressing to Windows 98. Only the "advanced course," shrouded in mystery, hinted at the inclusion of Windows 2000 and Linux.

A New Dawn: Reversing the Order of Operations

This revelation sparked a new line of thinking. Perhaps, just perhaps, the key lay in installing Windows 98 first, then backtracking to incorporate Windows 3.11 and NT 3.5.1. This unorthodox approach offered a flicker of hope. Could trusty DOS 7.1, with its FAT32 partition capabilities, hold the answer to this multi-boot conundrum?

The journey continues! Armed with this newfound strategy, we press onward, determined to conquer the multi-boot mountain. Stay tuned for the next chapter, where we'll attempt this installation reversal and see if it unlocks the secrets of a harmonious coexistence for our vintage operating systems. Who knows, we might even stumble upon some unexpected treasures along the way!