Now you can reboot your virtual install and use your Windows 95 disc to install the OS. Add the cdrom.img files to the completed install. If you have a full Windows 95 install disk (OEM disks or full commercial release), load DOS 6.22 just as you did for Windows 3.1x. Remember to disable VT-x/AMD-V and Nested Paging. vdi file) to a fixed size of no more than 2GB. Even in VB, it may still give you fits.Ĭreate a new VB install. Historically significant, Windows 95 set the standard for the desktop GUI. ![]() Or you’re like me and you have a bunch of old Windows install discs collecting dust that are just begging for new life. Or you just want to rekindle old skills you’ve forgotten. Or maybe you just want to see the Berkeley Systems After Dark Loony Tunes screensaver you bought years ago run just one last time: Why would anyone want a working virtual copy of Windows 3.1x? Well, perhaps you have a bunch of old software programs lying around and just need to open a document in Microsoft Works 3.0: I have all of the images files for DOS 6.22 and Windows 3.11 that were included with my first Windows computer: a Packard Bell Legend series system with a 50MHz Intel CPU, 4MB of RAM built onto the motherboard (upgraded to 36MB by adding two 16MB RAM chips), and a 512MB hard drive. You swap image files under the Devices menu at the top of the screen while VB is running.īefore attempting to load Windows 3.1x or Windows 95 in VB, you must disable VT-x/AMD-V and Nested Paging under the System > Accelerations settings tab.Ī full tutorial has been created by Glijnos to walk you through the process. ima) can be used as a substitute for physical floppy disks in VB. If you know nothing about VirtualBox, now would be a good time to learn. Thanks to VirtualBox, you can relive that nightmare all over again! Windows 3.1x was nothing more than a graphical shell around which DOS operated. ![]() For many of us, this was our first experience with the Microsoft Windows graphical user interface (GUI).
0 Comments
Leave a Reply. |