There are several websites with information about Virtual PC. These include:
Robert Moir's VPC 2004 FAQ (http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html)
Virtual PC Compatibility List (http://vpc.visualwin.com/)
Microsoft's Virtual PC Website (http://www.microsoft.com/windows/virtualpc/)
The blog of Ben Armstrong, the Virtual Machine team's Program Manager (http://blogs.msdn.com/Virtual_PC_Guy/)
And for VPC 5.2 (and some VPC 2004):
Steve Jain's Virtual Machine Download Site (http://vpc.essjae.com/)
Also, never underestimate the Virtual PC help file. You can check it at anytime by clicking "Help" and then selecting "Virtual PC Help" on the Virtual PC Console window.
The Virtual Server newsgroup is microsoft.public.virtualserver. All Virtual Server questions should be posted there for the best response.
The web-based newsreader is available at http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.virtualserver
Virtual PC 2007 was released in February 2007. Information about this version (including the download, free of charge) is available at http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx.
No, there are only VPC Additions for some versions of Windows. Linux VM Additions have been released for Virtual Server 2005 and users have reported success with several Linux distributions and Virtual PC 2004/2007, though this is currently unsupported. In addition, Steve Jain's website (listed above) contains the Virtual PC 2004 Service Pack 1 Additions, which should work, but are unsupported, in some additional guest OSes running under Virtual PC 2007 (and later).
Prior to the switch to Intel processors, Mac OS ran computers that used PowerPC processors - a processor not supported by Windows, which generally use x86 or x86-64 processors, and therefore one that VPC cannot utilize. There is an effort to run these PowerPC versions of Mac OS on an x86 processor called PearPC. Info about PearPC can be found at their website (http://pearpc.sourceforge.net/).
The newer versions of Mac OS now run on Intel x86 processors. These versions still will not run in Virtual PC, however, because Apple restricts the installation of their operating system to only their computers both by means of software and licensing limitations.
The same way you would on a real PC. Most modern OSes can boot off of their CD (or ISO image), but older OSes like Windows 95 and 98 usually require a boot floppy. A good collection of boot floppies is available at www.bootdisk.com.
In the newsgroup microsoft.public.mac.virtualpc. The microsoft.public.virtualpc newsgroup is only for Virtual PC for Windows.
Virtual PC emulates a specific set of hardware regardless of your host. Your host's CPU is not emulated, and your virtual hardware is listed under "6.a.10" on http://www.robertmoir.co.uk/win/vpcfaq/VPCFAQ6-InstallingGuestOS.html#6.a.10.
Please remember to post your Virtual PC version number, host operating system & memory, CPU type, and guest operating system & memory (along with anything else that may be important to answering your question). Without information like this, it may be difficult (or impossible) to answer your question.
When you create a virtual hard drive, from that time forward it acts like a real hard drive. The same way you can't add space to a real hard drive, you can't add space to a virtual drive. You can image one virtual drive to another one that is bigger though.
There is, however, at least one third-party tool that allow for this. Information about it can be found at http://www.xtralogic.com/products_vhd_utility.shtml.
This problem is generally caused by an old version of the InCD packet CD-writing application. You can get the updated version here. (http://www.nero.com/en/nero-up.php)
Virtual PC 2007 supports Windows Vista and should have no issues installing it. For more information on Virtual PC 2007, visit http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx.
Although the emulated NIC is a 10/100 NIC, the actual speed it goes is only limited by your host hardware. Therefore, if you have a 10 mbps NIC in your host, the guest will only go up to 10mbps, and the same is true for 100 mbps and 1000 mbps host NICs.
This hotfix is included with the free download of Virtual PC 2004, available at the Microsoft Virtual PC website (http://www.microsoft.com/windows/virtualpc/), in the "Laptop Hotfix" folder of the ZIP file. Information about the update can be found in the text file within that directory. Note: This update is only intended for laptop and notebook computers.
No. To install a copy of Windows (or most other licensed programs) onto a computer you will need one license per each computer that you wish to install it on. Virtual machines are considered separate machines for this purpose, therefore you will need a separate license for the host computer (that is, the computer on which you installed Virtual PC), and each of the virtual machines you are running. There are certain exceptions to this rule - which would be clearly marked in that product's end-user licensing agreement.
The main difference between Virtual PC and Virtual Server is their target markets: Virtual PC is generally aimed towards developers, while Virtual Server is designed more for businesses doing server consolidation. Several other differences stem out from this key difference:
Supports sound in guest OSes
Runs in a window on the host
Only officially supports running a handful of consumer-level operating systems (though many unsupported OSes work as well, see http://vpc.visualwin.com)
Only officially supports running on a handful of consumer operating systems, though it can run on the business-level OSes Virtual Server supports
Does not have sound in guest OSes
Runs as a service on the host, enabling the guest machines to run without a window on the host
Has a web-based configuration which allows the remote modification of settings
Has a web-based remote control, allowing users to remotely connect to their machines
Supports the limiting of CPU resources to specific machines
Only officially supports running many business-level operating systems, including several Linux varieties. Generally, the same OSes as above work in Virtual Server
Only officially supports running on several business-level operating systems, though it can run on most of the same OSes as Virtual PC
No. Each virtual machine is like a separate computer. The same way having a standard anti-virus program on one computer wouldn't protect another computer sitting near the first computer, each guest virtual machine requires its own anti-virus installation to be protected.
The main difference in the 64-bit version of Virtual PC is that it uses a 64-bit virtualization driver. The Virtual PC application is still 32-bit, so it will show as 32-bit in Task Manager. This is normal, and you have the correct version.
In general this "may" be possible, though the same issues that can occur when migrating from one physical machine to another may be encountered. There is a series of tips, posted by Ben Armstrong of Microsoft's virtualization team, which help ease the transition: http://blogs.msdn.com/virtual_pc_guy/search.aspx?q=migrating&p=1.
There are several ways to resolve this issue. Among them:
Browse to %appdata%\Microsoft\Virtual PC\
Backup the "Options.xml" file and load the original in a text-editing application
Under the "console" section, remove the entries for "left_position" and "top_position"
After saving the changes, load Virtual PC
Several other options are posted here: http://blogs.msdn.com/virtual_pc_guy/archive/2007/05/08/recovering-a-lost-virtual-pc-console.aspx.
As per the help file, Virtual PC 2007 supports the following guest operating systems:
Windows Vista Ultimate
Windows Vista Enterprise
Windows Vista Business
Windows XP Professional
Windows XP Home Edition
Windows 2000 Professional
Windows 98 Second Edition
OS/2 Warp 4 OS/2 Fixpack 15, OS/2 Warp Convenience Pack 1, and OS/2 Warp Convenience Pack 2
Note, however, that Virtual PC can run many more operating systems, though they are not officially supported by Microsoft. To see some examples of this, visit the Virtual PC Compatibility List mentioned in question #1.
This message was automatically posted in order to help newcomers to microsoft.public.virtualpc by answering some of the most frequently asked questions from the group.
The Microsoft.Public.VirtualPC FAQ Poster