First of all, your software rules. Its easy to use, and it does what its supposed to well. There is, however, one function missing... and including it just seems so blatently obvious to me. From the Parallels Image Tool, why can't I convert a real, physical HD to a virtual .hdd file? I would guess that there's many Win users out there, that when they bought a new computer, just kept the HD from their previous machine. Why, when migrating, do I have to mess around with the old computer? This functionality would be incredibly useful for Parallels Desktop for Mac, because Macs can read FAT16, FAT32, & NTFS. This is how it should work: I've pulled my hard drive from my old WinDell machine (and thrown the Dell off the roof or into a swift flowing river) and I've put the HD in a usb/firewire enclosure, or I'm using a bridge. OS X mounts this like a champ, regardless of the native fs. I launch the Parallels Image Tool, and it gives me an option to image from an actual hard drive as the source (or a folder on the Mac HD). I choose my old windows bootable hard drive, and pick a destination to create the new virtual.hdd image. Now I launch Parallels Desktop, and I create a new machine, but choose the new virtual.hdd image instead of creating a new blank one. No installation necessary. Why all this connecting old computer to new computer over a network? Running some migration utility from the legacy machine is counter-productive and counter-intuitive. Just seems so unnecessary to me. Plz add this ability! Thanks.