hd cloning

Hi all,


new to this HD cloning thing.....If i clone a drive from a CF-M34 (mk5) will it work in any cf-m34 regardless of mark...or do they have to be the same????....


cheers

Mick T

 

You should clone for the same MK#... Some may work between models but if you go from MK1 to MK5... You will most likely have issues... if you don't get the BSOD first...

 

One of the problems you face when you try to use the same carrier and HD among even the same models is that when you install the OS and put in the key for activation, it takes info from several points on the mobo including the processor. When you put the HD in another model with a different processor, the OS will recognize the difference and you will probably get the BSOD.

 

Unless you clone with something like shadowprotect or Acronis with the Universal Restore...

 

If you are imaging XP from computer to computer (ie. CF-M34mk1 to mk5), then the BSOD will be caused by incorrect chipset drivers for the machine it is now trying to boot.

Only Vista/Win7 looks at hardware differences with regards to activation status (and if it just an activation problem, it won't BSOD).

 

Hi,

just wondering which acronis do i use...went to the site and there's a few different versions....

 

Not necessarily, I have taken a Ghost Image of XP off an AMD Chipset and moved it over to a Intel Chipset. The machine hiccuped a few times and demanded to be restarted but ultimately ran just fine.

Chipset whose drivers are not native to the OS will most likely be less lucky.

 

Completely untrue. I've seen XP BSOD code 0x0 on a completely stock machine for a change in RAM and HDD at the same time. I've also seen it completely ignore a change from AMD to Intel processor (which means different motherboard as well)... don't imagine that XP doesn't monitor hardware every time you boot it - it does. It's just not always that smart at figuring out when something it SHOULD be upset about changes.

mnem
Boop.

 

I have never seen a machine blue screen from activation status problem in years...and I've done a lot of different builds for customers (including migrating an image from one unit to another). I'll conceed a assumption issue with what Azrial said (I made the sweeping assumption that XP never has the chipset drivers, which is only true for post XP-release chipset drivers, and that when I said chipset I meant the HDD chipset, ie. SATA). It's just occurred to me that more often then I'm not I'm using enterprise/vlk/other non-consumer product, which makes a difference for activation status - oooops!

And if what you say is true, that it only notices hardware changes and messes with activation very rarely, then what I said is hardly "completely untrue"

 

You said it doesn't monitor - it does, at least on any product available to the general public. Site license versions are a completely different animal; heck, you don't even have to validate them; that's like comparing Windoze to... decr@pified Windoze.

mnem
uncr@p.

 

Well yes, in my case we are discussing a legit copy of VLK...