Loading AI tools
PowerPC Macs and Windows x86 emulator From Wikipedia, the free encyclopedia
Virtual PC is a discontinued x86 emulator for PowerPC Mac hosts and a hypervisor for Microsoft Windows hosts. It was created by Connectix in 1997 and acquired by Microsoft in 2003. The Mac version was discontinued in 2006 following the Mac transition to Intel, while the Windows version was discontinued in 2011 in favour of Hyper-V.[1]
Up until version 4, Virtual PC only supported Classic Mac OS hosts. In 2000, version 4 was released for both Mac OS and Windows, and version 5 (2001) added support for Mac OS X hosts. After Microsoft acquired Virtual PC from Connectix in 2003, the program was renamed Microsoft Virtual PC. In July 2006, Microsoft released the Windows version free of charge.[2] In August 2006, Microsoft announced the Mac version would not be ported to Intel-based Macs, effectively discontinuing the product as PowerPC-based Macs would no longer be manufactured.
In 2009, Microsoft released Windows Virtual PC, which is only compatible with Windows 7 hosts, and is the technical foundation for the latter's Windows XP Mode. Windows Virtual PC does not officially support MS-DOS or operating systems older than Windows XP Professional SP3 as guests.[3]
Connectix Virtual PC, Microsoft Virtual PC 2004, Microsoft Virtual PC 2007, and Windows Virtual PC are successive versions of the same software. Windows Virtual PC only runs on Windows 7. The earlier Microsoft versions which run on older versions of Windows were still available and support operating systems older than Windows XP. Starting in Windows 8, Microsoft replaced Virtual PC with Hyper-V.
Virtual PC was originally developed as a Macintosh application for System 7.5 and released by Connectix in June 1997.[4] The first version of Virtual PC designed for Windows-based systems, version 4.0, was released in June 2001. Virtual PC 4 was the first version with expandable drive images.
Connectix sold versions of Virtual PC bundled with a variety of guest operating systems, including Windows, OS/2, and Red Hat Linux. As virtualization's importance to enterprise users became clear, Microsoft took interest in the sector and acquired Virtual PC and Virtual Server (unreleased at the time) from Connectix in February 2003.
Under agreement with Connectix, Innotek GmbH (makers of VirtualBox, now part of Oracle) ported version 5.0 to run on an OS/2 host.[5] This version also included guest extensions (VM additions) for OS/2 guests, which could run on Windows, OS/2 or Mac OS X hosts using Virtual PC versions 5, 6 or 7. A new version of the guest extensions was later included with Microsoft's Virtual PC 2004.
This section needs additional citations for verification. (March 2011) |
On July 12, 2006, Microsoft released Virtual PC 2004 SP1 for Windows free of charge, however the Mac version remained a paid software. The equivalent version for Mac, version 7, was the final version of Virtual PC for Mac. It ran on Mac OS X 10.2.8 or later for PowerPC and was a proprietary commercial software product.[6]
Virtual PC 2007 was released only for the Windows platform, with public beta testing beginning October 11, 2006, and production release on February 19, 2007. It added support for hardware virtualization, "undo disks", transfer statistic monitor for disk and network, and viewing virtual machines on multiple monitors and support for Windows Vista as both host and guest. The Windows Aero interface is disabled on Windows Vista guests due to limitations of the emulated video hardware; however, Aero effects can be rendered by connecting to the guest via Remote Desktop Services from an Aero-enabled Windows Vista host, provided that the guest is running Windows Vista Business or a higher edition.[7][8][9] Windows XP Home Edition is officially not supported as a host OS, but it will work.[10] This was rectified in a February 20, 2009 hotfix update for Virtual PC 2007 SP1. Windows XP Starter and Windows XP Media Center Edition is not supported on Virtual PC 2007. Support for Windows 2000 Professional as a host OS was dropped in Virtual PC 2007 and will not work at all on Windows 2000 hosts, but is still supported as a guest OS.
"Undo disks" make it possible to revert virtual machines' state to an earlier point by storing changes into a separate .vud
file since the last save to the main .vhd
file, which can be used for experimenting. The VHD file acts as a snapshot. The undo disk file (.vud
) incrementally stores changes made by the virtual machine compared to the main Virtual hard disk drive (VHD) image, which can be applied or discarded by the user. If deactivated, changes are directly written to the VHD file.[11]
On May 15, 2008, Microsoft released Virtual PC 2007 Service Pack 1, which added support for both Windows XP SP3, Windows Vista SP1 and Windows 7 as guest and host OSes, as well as Windows Server 2008 Standard as a guest OS.[12][13] A hotfix rollup for Virtual PC 2007 SP1, released February 20, 2009, solved networking issues and enhanced the maximum screen resolution to 2048×1920 (32-bit),[14] enabling 16:9 resolutions such as 1920×1080. It also added official support for Windows XP Home Edition as both guest and host OSes. A security update was released on July 14, 2009 to address an elevation of privilege vulnerability in guest operating systems.[15]
Microsoft Virtual PC (2004 and 2007) does not work at all on Windows 10 64-bit,[16] and even on 32-bit platforms lack internet connectivity due to the lack of the VPC driver. This also impacts Windows Mobile emulators.
Date | Version | Description |
---|---|---|
2006-10-11 | 6.0.122 | Beta |
2007-01-02 | 6.0.142 | Release Candidate 1 |
2007-02-22 | 6.0.156 | Release to Manufacturing |
2008-05-15 | 6.0.192 | Service Pack 1[17] |
2009-02-20 | 6.0.210 | Update[18] |
2009-07-14 | — | Security Update MS09-33[19] |
![]() | |
![]() Windows Virtual PC running Windows XP on a Windows 7 host | |
Developer(s) | Microsoft |
---|---|
Initial release | September 19, 2009[20] |
Final release | 6.1.7600.16393
/ February 14, 2011[20] |
Operating system | Windows 7 (all editions except Starter)[3] |
Successor | Hyper-V |
Size | 32-bit: 9.1 MB 64-bit: 16.3 MB[20] |
Type | Virtual machine |
License | Freeware[20] |
Website | www |
Windows Virtual PC entered public beta testing on April 30, 2009,[21] and was released alongside Windows 7.[22] Unlike its predecessors, this version supports only Windows 7 host operating systems.[3] It originally required hardware virtualization support but on March 19, 2010, Microsoft released an update to Microsoft Virtual PC which allows it to run on PCs without hardware support.[20]
Windows Virtual PC is available free of charge for certain editions of Windows 7,[3] either pre-installed by OEMs or via download from the Microsoft website.[20]
New features include:[23]
Windows XP Mode (XPM)[36][37] is a virtual machine package for Windows Virtual PC containing a pre-installed, licensed copy of Windows XP Professional with Service Pack 3 as its guest OS. Previously, both the CPU and motherboard of the host had to support hardware virtualization,[38] but an update in early 2010 eliminated this requirement.[39] Pre-installed integration components allow applications running within the virtualized environment to appear as if running directly on the host,[22][40] sharing the native desktop and start menu of Windows 7 as well as participating in file type associations. Windows XP Mode applications run in a Terminal Services session in the virtualized Windows XP, and are accessed via Remote Desktop Protocol by a client running on the Windows 7 host.[41]
Applications running in Windows XP Mode do not have compatibility issues, as they are actually running inside a Windows XP virtual machine and redirected using RDP to the Windows 7 host. Windows XP Mode may be used to run 16-bit applications; it includes NTVDM, however it is impossible to run 16-bit applications that require hardware acceleration, as Windows Virtual PC does not have hardware acceleration for such applications.
Windows XP Mode is available free of charge to users of Windows 7 Professional, Enterprise, and Ultimate.[35] Users of other editions of Windows 7 are not eligible to download and use it.[39][42] This restriction does not apply to Windows Virtual PC itself.
Windows XP Mode can also be run with VMware Player and VMware Workstation. However, like with Windows Virtual PC itself, VMware products only import Windows XP Mode on Windows 7 Professional, Enterprise, or Ultimate versions in order to adhere with Microsoft licensing requirements.[43]
Virtual PC emulates the following environments:[44]
Implementation:
Virtual PC 4 requires Mac OS 8.5 or later on a G3 or G4 processor, but running Windows Me, Windows 2000 or Red Hat Linux requires Mac OS 9.0 or later. Virtual PC 5 requires Mac OS 9.1 or newer or Mac OS X 10.1 or later. For USB support, Mac OS X is recommended. To run Virtual PC 5 in Mac OS X, a 400 MHz or faster processor is required.
Earlier versions of Virtual PC supported the following features: (now removed in Microsoft Virtual PC 2004, 2007, and Windows Virtual PC):
Windows Virtual PC may enable guest operating systems running inside virtual machines to interact with their host operating system beyond what is feasible between two physical computers, such as sharing physical hardware components or exchanging data. To do so however, integration components must be installed on the guest operating systems. When no integration component is installed, the only mean of communicating between two machines (either virtual or physical) is through a virtual network interface. Even the mouse cursor can only be controlled by one operating system (either real or virtual) at any given time. However, once the Integration Components are installed on the guest operating systems, the following features are automatically activated:[45]
In addition to features described above, guest operating systems may also take advantage of the following integration features but only when the administrator activates them:[45]
In Windows Virtual PC, enabling integration features automatically makes the virtual machine user account accessible using Remote Desktop Connection.[45]
Virtual PC allows multiple guest operating systems to run virtualized on a single physical host. Although a number of popular host and guest operating systems lack official Microsoft support, there are sometimes few, if any, technical obstacles impeding installation. Instead, a configuration may be unsupported due to Microsoft's own licensing restrictions,[47][48] or a decision to focus testing and support resources elsewhere, especially when production use of a legacy product fades.[49][50]
A program manager on Microsoft's core virtualization team explains what official support entails:
With each release of Virtual PC we spend a significant amount of time trying to decide which (guest) operating system should be officially supported. While Virtual PC is capable of running many operating systems, official support for an operating system means that we will test it thoroughly, not ship Virtual PC if an issue exists with that operating system, and provide full support for customers who encounter problems while running these operating systems under Virtual PC.[49]
— Ben Armstrong, "Virtual PC Guy"
As a product positioned for desktop use, Virtual PC provides official support for a different set of operating systems than its server-oriented counterpart, Microsoft Virtual Server and the more advanced Hyper-V.[51][52] While the latter products support a range of server operating systems,[53][54] Virtual PC 2007 supports only one variety as host and another as guest;[55] its successor, Windows Virtual PC, supports none.[56] And, whereas Virtual Server and Hyper-V have officially supported select Linux guests since 2006[57] and 2008,[58] respectively, as of 2009[update], no Microsoft release of Virtual PC has officially supported Linux. Nonetheless, a number of Linux distributions[58] do run successfully in Virtual PC 2007, and can be used with the Virtual Machine Additions from Virtual Server (see below).[59][60] Lastly, while 64-bit host support was introduced with Virtual PC 2007, no[update] release has been able to virtualize a 64-bit guest;[61][62][63] Microsoft has thus far reserved this functionality for Hyper-V, which runs only on 64-bit (x64) editions of Windows Server 2008, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows 8/8.1 Pro and Enterprise, and Windows 10 Pro, Enterprise, and Education.
In the following table and notes, "support" refers to official Microsoft support, as described above.
Notes – details of Microsoft support
Notes – not supported installations
Installing a Linux-based guest environment in Virtual PC is possible. RedHat and SuSe Linux guests are supported. Linux additions are supported in Microsoft Virtual Server, and these additions should also work in Virtual PC.[59]
Some Linux distributions must be installed in text mode, as they do not support Microsoft Virtual PC's emulated graphics chip. Ubuntu 8.10 "Intrepid Ibex" must be installed in SafeMode, but does not require other changes.
Some websites specialize in listing operating systems that run successfully as Virtual PC guests, to help users avoid issues when installing Linux distributions or other operating systems lacking official Microsoft support.[93][unreliable source?]
Microsoft announced on August 7, 2006, that Virtual PC for Mac would not be ported to the Intel Mac platform. Microsoft stated, "Alternative solutions offered by Apple and other vendors, combined with a fully packaged retail copy of Windows, will satisfy this need."[94] Similar products available or announced at the time were Parallels Desktop and VMware Fusion.