Words that describe my experience in key areas in getting VPC 2007 to create a Windows 95 VM: Drag and drop is enabled through guest additions making it easy to install IE VPC 2004 VM Additions installed just fine. This was expected based on the initial research. VPC 2007 does an excellent job of virtualising hardware for Windows 95.Īttempting to install the VPC 2007 version of VM Additions threw up the following error: The view of Device Manager below provides clues as to why display, sound and network work out of the box. The display could also be adjusted and there was network visibility, all this without the addition of guest services (Microsoft use the term VM Additions). Once I applied the specified patch, Windows booted cleanly.Īfter finalising setup and booting into Windows, the first thing that I noticed was sound. Unlike WP, which handled this intrinsically and VirtualBox, which had a workaround, VPC 2007 doesn’t have an elegant way of dealing with the issue. When booting Windows 95 after initial setup, I got the dreaded Windows protection error I observed under VirtualBox. Like VirtualBox, I found this took a little getting use to.ĭuring installation, I allowed Windows 95 to detect hardware. Right-Alt is used to switch back from the guest system to the host system. The floppy was A: and the target drive for the system was C: as expected. This must be some sort of defacto standard amongst virtualisation vendors. Interesting that VPC 2007 also assigned the letter R: to the optical drive. When setting up the VM, I chose Windows 98 as a comparable guest OS.Īs with VirtualBox, VPC 2007 handles both optical and floppy devices well. It is able to run guest additions designed for VPC 2004.īased on this, I decided to work with VPC 2007, the highest version of VPC able to support Windows 95.
0 Comments
Leave a Reply. |