How do you "ghost" to different mobo?

[Technican]

hi:

ok i have windows XP pro (corporate) up and running and I want to clone it to new hard drive in different mobo. I'm using Norton Ghost 2002 which is compatible with Win XP. The 2 mobo's are entirely different. The source is the Epox 8kta3 and the destination mobo is the K7s5a. after ghosting and hooking up the hard drive to the k7s5a I get a blue screen which prevents me from proceding. Can't get into safe mode or any mode. I also ran the sysprep utility on the source hard drive before ghosting. Does anyone know how to get around this problem? Thanks!

 

[MentalAtrophy]

Are any of the other components in the system different? Pretty much with all the driver conflicts you'll get trying to do it that way, you'd be better off just installing the OS and programs fresh and copying any data you need over.... be much much cleaner that way.

-mA

 

[JustStarting]

you should have manually removed the drivers first. ghosting is mainly used for backing up a hdd to reinstall in the SAME system if the original hdd fails.

 

[desy]

Yep same system. . .
Which is why when I buy for work I make em identical as much as possible simplifies life

 

[Technican]

hi:

Thanks to all for their replies. The main purpose of "my" ghosting is to be able to take a hard drive all setup and clone it to a clients hard drive so I dont have to do all the installs of the OS and programs like office, norton's etc. When doing this with win 95/98/me it was a snap. after the ghost you would boot the new hard drive in a completely different hardware environment and delete the ENUM in the registry. windows would then do a new hardware detection and you're all set...however in windows XP there is the SID and probably other obstacles to tackle. It doesn't work because of the difference in the hard drive controllers. again assistance would be appreciated. Thanks..

 

[Drakkhen]

Well, I just went from a VIA based board to an Intel 845D board, and all I did was swap the cards and the hard drives.

Windows XP picked up everything and kept on trucking.

One caveat, though, was that I was using a SCSI setup and the SCSI controller was the same (since I moved them). Now, what I would do in your situation, though, is to make sure you had a machine specific image for each machine. This will lead to fewer problems out in the field.

I do believe that the ghost product has "ghostwalk" which will change the SID on the machine. Although, I don't know if that will work with XP or not.