• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dad got a new PC...wants to "ghost" his current setup to the new pc.

Red

Diamond Member
Dad's old PC:

HP 3500+ AMD64

Dad's new PC:

Custom 4800+ Dual core (X2) w/ MSI K8 Neo4.

He wants to ghost his data so that the new computer will boot up like his old one.

1. Are there any issues with this (going from single core to X2)

2. What is the best way to do this if it is possible? Norton Ghost?
 
Originally posted by: PurdueRy
do a Windows repair install on the same hard drive?

that will technically work, but you will still be susceptible to bsod's. the best course of action would be to sysprep the machine with the old hardware, and then boot up with the new hardware.

I will look for the thread that someone posted on here for how to do this.
 
Just take the time to do a fresh install. I don't know why people are so lazy with windows installs. Yes it takes time but if I have a new setup I want a fresh install for that specific hardware. The hard drive manufacturer should have a utility to ghost the data most likely.
 
I'm seeing two issues (don't have an X2, I'll let somebody pick up that one)

1. Did a quick google and couldn't find what mobo the HP has in it. If it uses a different chipset than the MSI you'll have problems. Diferent mobo's with different chipsets require different drivers. Prolly get a bluescreen when trying to start. HERE'S an Anandtech article on how to get around taht problem. Scroll to the bottom and check out "Misc Notes" for the solution (repair install)

2. Some HP's I've worked with have a code in the BIOS or some kinda crap to prevent using the OS on another PC. If that's the case here it ain't gonna work cuz when the OS "sees" the HP mobo missing it won't start.

Fern
 
The biggest issue will be whether or not the PC's use the same HAL. If so, an image should be relatively easy to port to the new system (with drivers being the only issue). However if you aren't running the same HAL, you're kinda screwed. There's directions out there for how to change HAL's, but it's tricky and I wouldn't trust it personally (would rather rebuild).

I'm not sure if the dual-core's use a different HAL though, we haven't experimented with those yet. Can't wait though ;-)
 
I'm not sure if the dual-core's use a different HAL
I think you're correct for bringing that up.
I'm guessing it would be a different HAL.
If he's using XPhome it won't support 2 cores anyway will it?😕
 
The easiest way to do it. On the old machine, go in to device manager, un-install the hard drive controllers, and reset the video to standard display adaptor, Uninstall things such as the sound card as well. Then go ahead and ghost the drive. You'll still likely have to do a repair install, but that method is usualy successful for me. I used Acronis True Image 8 to image my raid-0 array on my Intel system, and then restored the image to my AMD X2 system. I had to use the repair console to manualy disable the raid drivers procces, because I was getting BSOD. After that I did a repair install, and it's been running great ever since.
 
If he's using XPhome it won't support 2 cores anyway will it?😕

This still seems to be a common misunderstanding. Yes, XP HOME will support the dual core. Microsoft licenses by socket, not by cores. A dual core does work with XP home, and it will use both cores. It's just as capable of using dual cores as it is hyperthreading.
 
I reinterate what I said above-

Unless something's changed with HP, you do NOT "own" the software or OS (winXP) that came with the HP PC. You are not allowed to use it (the OS etc.) on another PC.

I think it likely "illegal" to use the HP's OS on another PC. Moreover, unless things have changed, HP has implemented security measure to prevent the cloning & use of the OS that comes with an HP PC.

If you do try to clone it over, I'd be very interested in how it worked & would appreciate if you posted back and let us know.

Fern
 
True, I didn't catch that the original system was an OEM. Some OEM OSes are "BIOS locked" and will only work on a system with the proper BIOS signature from the manufacturer.

Considering how much crap HP runs in the background on it's factory installs, he'd probbaly be better off with a clean install anyway.

 
Microsoft licenses by socket, not by cores. A dual core does work with XP home
Thanks for clearing that up for me.
I was wondering if XP would treat dual-cores like HT'ing.

Now I just need to remember who else I told that incorrect info too.😱
 
I am also interested to hear if the HP system can be ghosted to another system. Please post back on the results afterwards.

[*]Swapping a hard drive, with the system files ( C: ), from one system to another
Swapping a hard drive with the operating system files on it, from one system to another is similar to changing a motherboard in one system. The hard drive and motherboard must communicate through drivers and if either the hard drive or motherboard are changed, then the drivers must be updated. There are different ideas on how to update these drivers for the operating system and these ideas include:
 
Back
Top