Follow-up: success - VPC to Parallels XP image
I'll post to the how-to board as well, but I wanted to quote antblog, since the specifics mentioned here were the keys to my success, both in using the Windows Transfer tool, as well as to getting the Mac Transfer tool and Windows Transfer Agent combo to work.
Initially, I just used the Windows Parallels Transporter to create a Parallels disk image that I then coped to the target Intel iMac, and I was able to boot the virtual machine, though Mouse Synchronization was clearly not working. I was able to log in to the XP environment, though networking was not working, and drivers could not be installed (the only discs available in this installation case are the original Virtual PC install discs, which do NOT include a standard XP installation disc, which leaves a re-installation near impossible, without transfer tools). I was able to run the Parallels Tools installation, but once complete, the mouse and keyboard input to the virtual environment did not work at all.
The key, in reviewing the post quoted here, is the section that details that the "Virtual PC Additions" need to be uninstalled. If they are not uninstalled, there are clearly conflicts between the Virtual PC additions, and the "Parallels Tools" that offer similar benefits and the actual drivers for the virtualization environment. After restarting the Virtual PC machine after the uninstallation, the mouse synchronization in the VPC environment was off, but I was still able to run the Windows Parallels Transporter to create a new Transporter1.hdd and accompanying winxp.pvs file set, which I copied to the Intel iMac, and was able to successfully boot, run the "Install Parallels Tools..." installer, and get working keyboard & mouse input, working video drivers, and working networking.
HUZZAH!!! Success, especially in this case, before the actual deadline, is very sweet.
The other important detail in the original post is that to get the Mac Parallels Transporter to recognize a Virtual PC "machine" running the Parallels Transfer Agent (Windows) is to make sure that the VPC machine is set to use Virtual Switch networking instead of Shared networking. Once I shut down the VPC VM, set the networking to Virtual Switch, started the VPC VM, and started the Parallels Transfer Agent, the Intel iMac running the Mac Parallels Transfer app was able to "see" and start an import of the VPC VM.
I made a backup of the original, working, bootable file set I got from the Windows Parallels Transfer app, but hopefully the Mac Transfer app will be smart about asking where to save the file it creates, rather than overwriting the "working" VM I have in place.
Currently, I'm very happy I can get this machine in place without having to find or purchase a new XP install disc, since the original license with Virtual PC is valid.
Happy Transferring,
G
antblog701 said:
I successfully imported the Virtual PC disk image (Windows 2000) to Parallels. Let me add a few detail...
It's Windows 2000 Pro under Virtual PC 7
for Mac, and migrated to
Parallels Desktop for Mac.
Just to provide some basic steps on what I did...
- Install Parallels Transporter and Parallels Transporter Agent on your source PC (under Virtual PC for Mac).
- Uninstall Virtual PC Additions, then reboot. (this is very important, otherwise you won't be able to boot up the imported virtual machine.)
- I also changed the Network Setting to "Virtual Switch" (I am not 100% certain if this is necessary, but it works better in a number of situations with this setting.)
- In your Windows PC, launch Parallels Transporter Agent, make sure the Virtual PC is connected to the local network.
- In your Intel-based Mac, launch Parallels Transpoter, and follow the on-screen instruction.
Hope this helps.