On the new system, attach the boot drive to this same add-in controller and perform the restore. What I’ve always had to do when migrating working systems to new hardware is to use an add-in controller on the old system, load the drivers for the add-in controller, then take the system image. What I have seen in other universal restore products is the ability to inject the correct driver during the restore process. The biggest problem I have encountered restoring to different hardware, (using other products), is if the new system uses a different hard drive controller or different raid controller then you will get the dreaded “Inaccessible boot device” error when starting up because the system image doesn’t contain the driver for the new controller. The option will appear on the last screen, after the volume is restored. It would be nice if we could investigate in which constellations (of hardware backed up and hardware restored to) this already works and which constellations still need work. The restore cd here includes a first release of the method to make the restored Windows bootable on different hardware. Problem 2 remains unsolved for now, but I would like some feedback of how much of a problem this is. For example Windows XP does not have any AHCI driver per default.įor problem 1 the restore cd now has a method to modifiy the restored Windows installation to reenable the relevant drivers. Problem 2: Windows sometimes does not have the correct driver to boot on different hardware at all. If one restores it to different hardware it then won’t be able to boot because the correct drivers are not loaded. Problem 1: Windows optimizes itself for a short boot time by disabling drivers which it does not need on the current harware.
0 Comments
Leave a Reply. |