Aller au contenu principal

DDD does not truly clone

Thread needs solution

When I clone the C drive to another HDD, the swap drives, I have to go through the procedure of re-registering many of the programs. If the disk is truly a clone, then why is this needed?

0 Users found this helpful

Typo in original. Should read as follows: When I clone the C drive to another hard drive, then swap drives, I have to go through the procedure of re-registering many of the programs. If the disk is truly a clone, then why is this needed?

Lots of unsupplied data but try this.

If you have a full disk image backup of our system, you could try restoring the Disk Signature from within the backup

1. If both disks inside one computer, place the target on same MB connector as the original.
2. Move the original onto a new set of connectors.
3. Boot using the TI Recovery CD to perform the clone.

If both disk not inside one computer, place the target inside computer on same MB connector as the original.
2. Move the original onto a new set connection such as an usb enclosure or usb utility connector.
3. Boot using the TI Recovery CD to perform the clone.

.

The first boot following the clone should be with only the clone attached. If both clone and source attached during first boot,Windows can and often does get confused causing the issues you are describing.

Thank you. Both disks are in same computer. When doing clone do I have to re-register all software again? QuickBooks seems to require this and it is a real pain. Other software is much easier to re-register, but it would be nice not to have to do so and I was thinking if the clone is truly a clone, the it should not need to re-register. I guess there are some differences even when cloned.

Richard Morris wrote:
Both disks are in same computer.

This may be the problem. Possibly Windows won't allow two disks with the same disk signature to be seen concurrently.

If you did a full disk mode Backup and restored that to the second disk, including restoring the disk signature, that should work. I've never had to re-register software after doing that. But, you should not allow Windows to boot with both those now-identical disks in the PC at the same time.

I never had both disks plugged in at the same time, except when doing the cloning, and always disconnected one before rebooting. Is there a way to boot from the CD ( to keep the HD from working) and then do a real bit-for-bit clone?

One thing I forgot to mention, the disks are not identical. One is 500GB and the other is 1TB. Could this have made a difference? Perhaps both must be the same size or even the same brand.

The disk serial numbers will be different, this along with many other things, could be enough to trigger the software re-registration problem