Here's how I do my "Restore to any hardware VMware images": 1. First I create a bootable CD with "Bootable CD Wizard" (freeware). You can use the 1.50z version, but then you need to extract the bootable information from the Acronis CD/CD's with "Winiso" as an "WBT file". If you use the 2.01a version, then that's not neccessary, that bootloader can run the Acronis iso's directly without extracting anything. Where to get:http://www.bcdwb.de/bcdw_e.html Put TI + Universal Restore onto this CD, as it's a multiboot CD loader, you can put several versions on it if you like. Onto this CD I also put "Bâshrat the Sneaky" Massstorage driverpack.(17 mb) It has massstorage and scsi drivers for like 95% of the hardware out there. Where to get:http://www.driverpacks.net/ (freeware) As Universal Restore searches "removable media", the CD is a very good place to put these drivers. With the massstorage drivers on the CD, and the Hal drivers in Universal Restore, you can now restore an image onto almost any hardware. This is the first part, the second part is to create the image in VMware. 1. Do a fresh install with the apps and windows updates of your choice in VMware. 2. Do not install VMware tools. 3. Download the additional driverpacks, such as sound graphics etc from http://www.driverpacks.net/ Expand these drivers into a folder named "D" in your windows folder. We don't wanna use long folder names here because of limitations in the length of the filepath. 4. Download "SetDevicePath.exe" from here: http://www.flachestirn.de/msfn/SetDevicePath.exe This tool will help you add the driverpaths to the "DevicePath" in your registry. It adds it to this key: hkey_local_machine\software\Microsoft\Windows\CurrentVersion This way, when windows first bootup, it will search this location additionaly to the "inf folder" for drivers. Run the tool from command prompt like this: SetDevicePath.exe %SystemRoot%\D Additionaly to doing this I like to delete all ".pnf" files + "INFCACHE.1" files from the inf folder in the windows directory. If you did a fresh install there shouldn't be any oem0.inf,oem1.inf etc in the inf folder, if there is ,(as when you install oem drivers which you shouldn't do) delete those as well. (only the oem one's). Lastly, go into device manager and delete all the devices. If it asks you to restart, click no, and continue to delete until all the devices has been un-installed. Deleting pnf and infcache files + deleting devices in device manager, should be done as the last thing before you shut the computer down for imaging ! The reason we don't want these .pnf and infcache files, is because they are "cached pointers", telling the system where installed drivers are located. Keeping these could potentially give you a "blue screen". Deleting this stuff is alot like running microsofts "Sysprep". It makes Windows start looking for new drivers, instead of "blindly following" the pre-cached .pnf files. When you first bootup, all these files will be re-created, making a new layout for windows to follow for your new hardware, ( first boot takes some time). In VMware I like to create a "Snapshot" just before deleting this stuff. so I can return to where I were if something goes wrong. Now shutdown your comp and make an image with TI. Voil'a ! now you have an image that should restore onto almost any hardware without the need to go hunting for drivers ! I do not recommend to Image to CD. Imaging to DVD or a usb drive is better. As a thumb rule, don't image onto any CD/DVD where the media is split. You will be shuffling CD's back and fourth until you go insane ! After you have installed the image to your new hardware using TI + UR, you can delete the "D" folder from the Windows folder if you like, after it has installed all the drivers completely. The whole driverpack complete takes up well over 1 gig in space. Unneccessary to have on a working machine. If you're really smart you create a small regfile to, that restores the "DevicePath" back to it's default, which is: %SystemRoot%\inf You can offcourse keep the drivers to if you want, it's up to you. If you keep them, and don't remove the registry entries in the device path, these drivers will be avaliable if you install any new device in the future, as "plug and play" If you wonder, why not add the massstorage drivers to, to the "D" folder ?, the answer is: Universal Restore has problems finding them if you add them to the image, instead of onto the bootCD. (I've learned by experience) Remember, Universal Restore Only restores massstorage and Hal drivers, the rest is done by windows itself, as the remaining drivers are not critical for a successful boot. Ho ho ha ha, my little tutorial (This was first a reply in another post, but I think it merits it's own topic) PS. I really hope Acronis one day makes Universal Restore "standalone", as it can then be used on other imaging software as well.