Running Windows 3.1 as a program inside Windows 95 served as a convincing technology demonstration, but the feature was cut shortly after it came together. And you wanted keyboard hotkeys like Alt+ Tab to switch among your Windows 3.1 windows, rather than treating Windows 3.1 as one giant program to be switched into or out of.
Computer systems of that era simply didn’t have the computing horsepower to render the video fast enough. There were some other preparatory steps that had to be done, but eventually you got to the point where you could double-click the Windows 3.1 icon, and up came Windows 3.1 in an MS-DOS virtual machine.Īlthough you could in theory run Windows 3.1 in a window, the experience was pretty bad in practice for a variety of reasons.
#Dosbox windows 3.1 video driver unable to set desired mode serial
To use it, you installed Windows 3.1 and Windows 95 into separate directories, and then made a few edits to the Windows 3.1 SYSTEM.INI file to replace the mouse and serial drivers with special versions. If you had a program that simply wouldn’t work with Windows 95 for whatever reason, you could fire up a copy of Windows 3.1 in a virtual machine and run the program there. Second, it was the ultimate backward compatibility ripcord. This was the ultimate in backward compatibility, along multiple axes.įirst of all, it was a demonstration of Windows 95’s backward compatibility by showing that it could even use an emulated MS-DOS virtual machine to run the operating system it was designed to replace. As the Windows 95 project started to come together, I was approached to undertake a special project: Run Windows 3.1 in an MS-DOS virtual machine inside Windows 95.
0 kommentar(er)
