
Once the CD-ROM is enabled in the VM, we’ll use the second image, a CD-ROM image, to deliver patches and software to WfW via the VirtualBox CD-ROM drive. This will enable us to transfer the driver from the host system to the target VM via the VirtualBox floppy drive.

The first is a floppy disk image of the CD-ROM driver for MS-DOS. In this step, we’re going to build two images. I’ve outlined nine steps to follow to construct a WfW VM with sound, super VGA display, local network and browser support. As I already had access to later versions of Windows in VMs, I used the technique described here to create floppy images. I thought ImgBurn would do the trick for me, but I couldn’t create a readable floppy image with it.

However, WfW is where my love affair with Windows first began. I intended to stop the Windows virtual machine (VM) challenge at Windows 95 and wasn’t planning on going back as far as WfW. Some familiarity with DOS is also assumed.Įdit (): According to this thread, the highest version of VirtualBox to still support WfW is VirtualBox 6.0.18. A working knowledge of VirtualBox is assumed.

This post will be of interest if you are considering revisiting MS-DOS 6.22, the last standalone version of Microsoft DOS, and Windows for Workgroups 3.11 (WfW), the first commercial version of Windows to gain any real traction.įor this post, I’m working with VirtualBox 5.2.12 under Windows 10 Home (build 1803).
