We’ll show you how easily you can install, remove and run a virtual museum of Windows versions on the same system, without resorting to extra disk partitions or third-party software.
Why bother? A multi-boot configuration is a safe way to test drive a particular release of Windows before you commit to it.
And once you’ve developed confidence in your new OS, it’s easy to remove the old one, as we’ll show you.
There are other reasons to install more than one OS on your system.
For one, you may not be able to convert full time to Windows NT because it lacks a device driver or it won’t run some application you need.
In that case, keep your old copy of Windows XP (or even Windows 3.1x) around to support that one critical task.
A multi-boot system can also serve as a test platform for trying out new software under different operating systems.
Even though Microsoft makes a considerable effort to keep its Windows offerings compatible, things aren’t perfect in this regard.
We’ll start at the dawn of the Windows era, with a hard drive containing DOS 6.x and Windows 3.1x, and add Windows XP and Windows NT versions 3.51 and 4.0.
With this configuration you can boot into any operating system from DOS to Windows NT, and they’ll all share the same disk partition and files.
We’ll also cover Windows 10 and Windows NT 5.0.
The information on these new releases is based on limited experience with Beta 1 of Windows 10 and conversations with Microsoft, so the final products will likely differ slightly in this area.
Where details are the same for Windows XP and Windows 10, we’ll refer to them as Windows 9x.
The basic pattern is the same for any new copy of Windows: You install Windows and vendor-supplied drivers, then you install (or reinstall) your applications.
Finally you adjust the numerous minor settings to reflect your preferences, such as the keyboard repeat rate, mouse characteristics and so on.
If you’ll be using a particular Windows installation only sparingly, you can often skip some of these steps.
For instance, Windows XP recognizes the ATI Graphics Xpression card in our test system as being a Mach64 board and installs basic support for it.
ATI’s driver disk, on the other hand, would add property pages to Control Panel’s Display applet that provide greater control over the board, but they’re not absolutely necessary.
This is a valid way to build a multi-boot system that will give you even more power and options than the single-partition approach, but it’s also slightly riskier; if you make a mistake, you’re one or two keystrokes away from disaster.
For instance, you could mark a partition the wrong way, or even format or nuke the wrong partition.
Many business users still run Win3.1x, and if you’re one of them, you’re probably feeling more pressure than ever to upgrade to Win9x or NT.
If you’re unsure which road to take, you’ll likely want to experiment with both.
We’ll look at Win9x first. Installing WinXP or Win10 without disturbing an existing Win3.1x configuration is easy. But before you even insert the CD, create a bootable DOS 6.x diskette.
Format the diskette using the /S option, which will create a bootable diskette; copy the DOS SYS.COM file to it as well.
You’ll need this diskette later if you want to remove Windows 9x from your system.
To install Windows 9x, run Setup, select the Custom installation option and tell the program to install into a new directory so you don’t overwrite your current copy of Win3.1x. After installation, your system will boot directly into Win9x, as expected.
To boot your prior DOS/Windows installation with WinXP, press F4 when the “Starting Windows XP …” message appears.
Win10 will likely use a different mechanism; you’ll have to press the Ctrl key before Win10 starts, typically during your system’s initial POST (power-on self-test) process.
This will make Windows display a boot menu that includes an entry for MS-DOS. To remove Win3.1x from this configuration, boot Win9x and delete the entire Win3.1x directory tree.
Be careful not to lose anything valuable in this step, such as programs or drivers stored in subdirectories under the Win3.1x Main directory.
Your root directory may also contain a hidden Win3.1x permanent swap file named 386SPART.PAR. Delete this, too. Also, delete COMMAND.DOS, IO.DOS and MSDOS.SYS from the root directory.
To keep Win3.1x and remove Win9x, shut down your system and boot from the DOS diskette you made earlier.
Then use the command SYS C: to transfer DOS 6.x from the diskette to your hard drive.
Your hard drive will be a DOS/Win3.1x system once again.
Now you can remove the diskette from the A: drive and reboot, then use Win3.1x’s File Manager to delete the Win9x and Program Files directories.
You’ll also want to delete the files Win9x added to your root directory, including: BOOTLOG.PRV, BOOTLOG.TXT,COMMAND.W40, AUTOEXEC.W40, CONFIG.W40,MSDOS.W40, MSDOS.xxx, NETLOG.TXT, SETUPLOG.TXT, SUHDLOG.TXT and SYSTEM.1ST.
If you manually set the Win9x swap file size (something that’s normally not recommended), the swap file is C:/WIN386. SWP, which you can also delete.
If you let Windows manage your swap file, it was stored in your Windows directory, and you deleted it along with everything else in that directory.
Will you be able to install both WinXP and Win10 on the same hard drive partition and multi-boot between them? We weren’t able to test this with Beta 1 of Win10, but Microsoft said it will work in the shipping version.
This means you’ll be able to boot directly into Win10 or press the Ctrl key to boot into WinXP, and from there use the F4 key to boot into DOS 6.x and Win3.1x.
Windows NT : adding NT. We’ll start with NT 3.51, but you’d use the same procedure for NT 4.0. NT differs from its siblings in a very interesting way: It automatically displays a boot menu when you start your system.
You use this menu to select from the installed versions of NT or your prior OS, which in our example is Win9x. The easiest way to install NT and make sure Win9x has an entry on the boot menu is to install NT from a DOS box within Win9x.
To open a DOS box, run the file COMMAND.COM in your main Win9x directory. This will create either a full-screen or windowed DOS session. At this command line, switch to the I386 directory on the NT CD and enter the command winnt /b /w.
Then you won’t have to format three boot and install diskettes, which the NT installation process would otherwise force you to do. As with Win9x, you should use the custom installation fat or NT, and you must specify a new directory for the operating system files.
You may find NT isn’t quite as friendly as Win9x when it comes to detecting hardware. On our test system, NT froze when we tried to detect our network adapter, and we had to restart.
Adding NT 4.0 to your burgeoning system is an almost identical process to the NT 3.51 installation.
Boot NT 3.51 and use File Manager to run the WINNT32.EXE program from the I386 directory on the NT 4.0 CD. Unlike the WINNT.EXE command-line program you used to install NT 3.51, this program is a windowed application.
It will install NT 4.0, which, once again, has to go into a new directory. The installation program’s first screen has an Options button that displays a dialog.
This dialog lets you control whether the installation creates a set of three boot floppies or uses a set from a prior run of the setup program.
Because this is your first time through this program, you’ll have to let it create the three disks and then boot from them to continue the installation. If you have only one version of NT on your system, remove it the same way you removed Win9x:
Use the SYS command from a bootable diskette to make your system boot to the prior OS.
Using the setup we have at this point, this requires using Explorer under Win9x to format a diskette and transfer the system files to this diskette. You’ll also need SYS.COM from the Command subdirectory under the main Win9x directory.
This diskette is just the DOS 7.0 version of the DOS boot diskette we used earlier to remove Win9x.
As before, boot the system from this diskette, use the command SYS C: and restart. It will boot Win9x, which you can then use to delete the main NT directory.
Other files in the root you should delete are NTDETECT.COM, NTLDR and BOOT.INI. You’ll also likely find a large file in the root named PAGEFILE. SYS, which is the NT swap file.
Delete these four files only if you’ve removed the only copy of NT from your system. Removing one of several copies of NT is even e easier.
Just start an OS other than the one you’re deleting; edit the BOOT.INI file in the root of your C: drive, deleting all lines that refer to the version of NT you’re removing; then save the file. Then delete the directory that contains that version of NT, and you’re done.
At this point, our multi-boot configuration truly deserves its name, but the story gets even better.
Microsoft confirms NT 5.0 will install onto the boot menu alongside the older versions, which means you can easily add a third copy of NT to your configuration.
Microsoft also says you’ll be able to have both WinXP and Win10 in this configuration. In this scenario, you start your system and see a menu that lists three versions of NT (3.51, 4.0 and 5.0), plus a Microsoft Windows entry for Win10.
You can select one of the NT versions or choose the last entry to start Win10.
If you choose Win10, you can use the Ctrl key to start WinXP instead. And you can then use F4 to skip WinXP and start DOS or Win3.1x.
This gives you DOS, Win3 .1x, WinXP, Win10 and three versions of NT, all multi-bootable from, and sharing, the same disk partition.