Virtual PC 2007

Virtual PC 2007 is a x86-based hypervisor that was originally created by Connectix as a Macintosh program, and it was later ported to Windows 95/NT 4.0. Shortly afterwards, Microsoft bought the program and released Virtual PC 2004, Virtual PC 2007, and Windows Virtual PC, the latter only working on Windows 7. Eventually it was replaced by Hyper-V. There's also a server variant of Virtual PC known as Virtual Server 2005 which added an Adaptec SCSI adapter.

This page mainly focuses on Virtual PC 2007.

Virtual PC 2007 is mostly intended for using 9x and XP-based operating systems, the absolute latest OS it can run without modifications is Windows 7 (very sluggishly), though it can run pure DOS, OS/2 Warp/NetWare or almost any x86 based OS. It is incapable of running x64 based OSes unlike most modern hypervisors though.

The only latest officially supported host operating system for Virtual PC 2004/2007 is Windows 7, but you can get it to run on newer versions with a hack, but you should only use 32-bit versions of them for best compatibility. You cannot run Virtual PC on 64-bit Windows 8 and higher.

Emulated hardware

• BIOS: Generic AMI BIOS
• Chipset: Intel 440BX
• Sound card: Creative Labs Sound Blaster 16
• Network card: DEC 21140A 10/100
• Video card: S3 Trio64V+

Running on CollabVM

CollabVM Server 1.x does not support running Virtual PC 2007 VMs at all.

CollabVM Server 2.0 can technically run Virtual PC 2007 VMs, but it is advised that you do not use it as it is very outdated and lacks many common features found in modern virtualization softwares. It also cannot run most modern Linux distros nor can it run any modern Windows OS. In addition, Virtual PC 2007 cannot be installed on 64-bit versions of Windows 10.

Hosting on CollabVM 2.0 (not recommended)

1. Create a VM and install an OS.
2. Install a VNC server, like TightVNC Server.
3. Add "C:\Program Files\Microsoft Virtual PC" to your PATH on your host machine.
4. Open the CollabVM Admin Panel.
5. Click on "New VM".
6. Fill in the following information:
   • The VM name, description, OS, RAM and Disk Space, etc.
   • Set the Start Command to: Virtual PC.exe -pc "(name of your VM here)" -launch -singlepc
   • Set the Stop Command to: taskkill /f /im "Virtual PC.exe"
   • Make sure the Protocol is set to "VNC".
   1. Add the following Guacamole Connection Parameters:
      • Add "hostname", and set the value to the IP or domain the VM is being hosted on - localhost should work fine.
      • Add "port", use 5900 if you didn't change the port.
      • If you set a password on the TightVNC server, add another parameter called "password" with the password you used.
7. Verify the information is correct, then start the VM.