I work for a very large computer company that distributes demonstrations as VMware images that I need to run under Parallels (otherwise I will be forced to purchase VMware Fusion when it's released). In VMware, each virtual machine receives a generated BIOS UUID in the .VMX file. Because Transporter does not propagate this UUID over to the Parallels VM, any Windows VMware image that I convert/boot in that is running Windows forces Windows to want to re-activate because it thinks that the machine has had a major hardware change. Is there any way to propagate the .VMX 'uuid.bios' parameter from the VMware .VMX file to the new Parallels virtual machine to prevent Windows wanting to re-activate? Thanks, Tim Henrion
