
tib files, but I wasn’t too eager to buy a copy of Workstation ($250).

VMware Workstation was apparently able to convert. Sadly, the User’s Guide contained no references to Acronis. I did that, and also downloaded their User’s Guide. But it didn’t seem to have the Recover feature that eHow found in Acronis Backup & Recovery, or that reportedly existed in the latest version of Acronis True Image.) I had previously downloaded VMware’s vCenter Converter Standalone - oddly named, if “standalone” sounds like it should mean portable: I had to install it. (My version of Acronis included the Plus Pack. tib files made with Acronis True Image Home 2011. Convert a Backup Image. I could try to convert a backup image of a physical Windows installation to a VM.But since those VMs expired after just a few months, that approach did not seem ideal for my goal of setting up VMs that I could use long-term. Preconfigured VM.I could download and run a preconfigured Windows VM from Microsoft.But I did not want to have to recreate, from scratch, a heavily tweaked Windows 7 installation of 50GB or more. Setting up new Windows installations would be relatively easy in that sort of case, where the goal was to create the simplest possible installation. I had recently done this with a copy of Windows XP, for purposes of virtualizing various Windows programs. Start from Scratch.I could install Windows from scratch inside the VM.Converting a Large Windows 7 TIB to VHD to VirtualBox VM.



I already had some Windows installations, backups, and CDs. As part of that system, I wanted to run Windows in a virtual machine (VM) in VirtualBox. As described in another post, I was transitioning to a Linux system.
