Restoring Ghost 15 Backup to new / dissimilar hardware

I had a 6 year old Acer Pentium Dual Core XPsp3 machine that I was backing up with Ghost 15.0.

Unfortunately this machine died this morning, but fortunately after the nightly Ghost 15.0 backups had run. 

 

I am now trying to restore the Ghost 15.0 backup to a new Gateway Intel Core 2 Quad desktop, but for some reason I am not having success.  The "restore anywhere" option is grayed out, and when the restored partition boots, I get a half second of the Windows splash screen and then the machine reboots.

 

Any help, suggestions or other would be greatly appreciated.

 

I have another spare desktop I could try to use, but I would prefer to use this one if possible.

 

Thank you!

Thanks for the quick reply.

 

Both computers have SATA drives with NO floppy.

I will check the BIOS settings.

 

My next steps was to do a repair install, and will try that tomorrow. 

 

 I suspect there are some driver issues and have ones on a thumb drive, but I was hoping to at least get the machine to boot with the default drivers.

 

Any other advise is appreciated.

 

 

If you have to do a repair, make sure you have a XP disk that has SP3 integrated into it.  Otherwise you can end up with a mis-match of system file versions.

 

But I would try different BIOS settings first, try SATA, AHCI, and even IDE mode if you have it.  Whatever gets you into windows so you can install the right chipset and SATA drivers.

If your getting a blue screen and it reboots to quick to read it, hit the "pause" button on the keyboard and the system will stop until you press the "enter" key.

 

You also might want to try booting into safe mode in case it's something else causing the problem.

Best of luck

Dave

He could also use Ghost 15 to convert to VHD and run mini setup (this strips the HAL). Then use Ghost 15 to restore the .vhd file instead of the .v2i file.

Red, you are probabably more familiar with this but I haven't found a wrong HAL to cause a reboot. It just causes a black screen. I put reboots down to wrong storage drivers.

 

I just installed a wrong HAL on a WinXP machine. A few seconds after power on the Win XP scrolling white dots started and then froze on a black screen with a white bar across the bottom.

I'm not any more familiar with it than you. I just played around with it in Virtual PC. I just wanted to remind you that there is more than one way to skin a cat. Running Mini setup seems like it might be good idea since he is restoring to different hardware. 

Red,

 

I've never run mini setup. Do you have any instructions? I'd like to try it sometime.

I had a 6 year old Acer Pentium Dual Core XPsp3 machine that I was backing up with Ghost 15.0.

Unfortunately this machine died this morning, but fortunately after the nightly Ghost 15.0 backups had run. 

 

I am now trying to restore the Ghost 15.0 backup to a new Gateway Intel Core 2 Quad desktop, but for some reason I am not having success.  The "restore anywhere" option is grayed out, and when the restored partition boots, I get a half second of the Windows splash screen and then the machine reboots.

 

Any help, suggestions or other would be greatly appreciated.

 

I have another spare desktop I could try to use, but I would prefer to use this one if possible.

 

Thank you!

The mini-setup runs automatically as a function of sysprep.

 

You got Virtual PC already installed, try taking a small image and use ghost to convert it to a .vhd

If you boot that in virtual pc, you'll see that it's been sysprepped and on first boot it will run a mini-setup and reconfigure the hal, SATA drivers, and for some reason re-install USB and network drivers.  It basically does a "restore anywhere".

 

What Red's getting at is that you can restore a physical drive from a vhd with Ghost, it doesn't have to be a .v2i file.

So if you do the same thing onto a real hard drive rather than boot it in VPC you have performed a restore anywhere onto dissimilar hardware. It's the same thing BESR does.

 

Downside is that windows will go into a 3 day grace period and prompt for activation.

Dave

Yeah, it bacically runs sysprep offline. There is an option to check when you convert .v2i to .vhd to run Mini-Setup.

 

 

Untitled.png

Thanks for the instructions. I restored the .vhd to the same computer but I have the idea.

 

One thing I missed. If you were going to restore the .vhd to different hardware, how do you install storage controller drivers? If they are needed. They are the main issue as far as I can see. Once the OS has booted you can then deal with installing other hardware drivers at your leisure.

Good question, I never checked that with restoring a VHD.

 

When I tried BESR, it took the drivers from the recovery disk.  I also tried another product that called it "Machine Independant Restore" or something like that and by default it would take the ones in use or it would let you choose another one if you wanted to.  But it made sense to me because if the recovery disk had the right drivers to do the image and restore then those drivers must work good enough to boot into windows and you could re-install the correct ones later.

 

In BESR, when your restoring the image and get close to the very end (I think at that point the image has been restored) If you look at the progress indicator it says " Re-targeting system for new hardware" then it says "updating storage drivers", "checking hal", adding necessary devices, etc

 

However, I don't remember watching for that when restoring a sysprepped vhd, so I'm not positive that will happen.

It would however, have to be able to go the other way, to a  ATA driver because thats what VPC uses.

Dave

Wouldn't Windows supply the driver? Maybe not if it is an OEM install, huh?

 


redk9258 wrote:

Wouldn't Windows supply the driver? Maybe not if it is an OEM install, huh?


 

I guess the main problem with drivers is doing it with XP, it's always been tough to switch between ATA and SATA, AHCI and that needs to be done before the system boots.

Heck, you used to have to put in a floppy disk and load the drivers before the setup

 

But maybe it does look there too, I just assumed they came off the recovery disk because thats what another product does.

 

Edit- I also assumed it came off the disk because of that long thread here about "please insert the recovery disk at 99%"

I thought for sure that was really a bug in restore anywhere and not a bug in windows pe.

some of the people mentioned something about it looking for drivers and it looked to me some of those restores were trying to do a restore anywhere even though it's supposed to be disabled in Ghost.

 

At long last I have resolved the issue.

 

0) boot a Windows XP sp3 CD on the target computer to make sure XP works on this machine

1) I had to first delete all partitions on the hard disk being restored to

2) restored the ghost backup to the new drive

3) booted to safe mode and installed the necessary drivers for the chipset of the new computer

4) removed an Intel specific registry key, as the new computer was an AMD (see: http://www.0x0000007e.com/)

5) booted to safe mode with networking - test

6) booted normal - test

7) bootee normal - rejoin to domain - test

 

ALL OK - i hope this helps someone else!!

 

 

That is great news.

 

The restore gave a different result this time as you could boot into Safe Mode. You couldn't do that the first time. Any idea why?

I'm not 100% sure, but I suspect that step 1, deleting all old partitions and having ghost re-create what it needed helped.

 

i am very pleased that the new computer is an exact  clone of the original with NO data loss.