Steps for proper cloning

Discussion in 'Acronis True Image Product Line' started by CrazyBishop, Jan 1, 2006.

Thread Status:
Not open for further replies.
  1. CrazyBishop

    CrazyBishop Registered Member

    Joined:
    Nov 19, 2005
    Posts:
    5
    Hi, The last time I tried TrueImage (v9 build 2302) for cloning a harddrive, I got a cloned harddrive and operating system that didn't recognize the old drive. This time I'm going to use TrueImage v8 build 937 for the job. This is my current config: Primary IDE Master 40gb(original harddrive), Windows XP SP2, NTFS file system. Here are the steps I'm planning to follow:

    1) Install TrueImage 8, then shutdown PC
    2) Connect new 80gb harddrive as Primary Slave
    3) Turn on computer, start TrueImage 8 and begin cloning process.
    3) Turn off computer after cloning process, then reverse drives (i.e reverse harddrive positions on the cable and reverse jumper settings.)
    4) Disconnect old harddrive
    5) Turn on computer, i.e - boot into the new cloned OS.
    6) Shut down PC, reconnect old harddrive as Primary Slave, and then turn the computer back on.

    Is this the proper way to clone the harddrive?; will it allow the cloned OS to recognize the old harddrive and use it as extra space? If not, please advise on the correct steps to follow and in the correct order. Thanks.
     
  2. noonie

    noonie Registered Member

    Joined:
    Jun 7, 2004
    Posts:
    299
    The method you describe will leave you with 2 winxp installs on active partitions on 2 separate drives. Winxp does not like this.
    In my experience, this was only possible with the original winxp with no service packs. I never bothered to persue why, but if the original drive has no operative winxp it will work.
     
  3. RetiredBri

    RetiredBri Registered Member

    Joined:
    Dec 11, 2005
    Posts:
    23
    Location:
    Saffron Walden, Essex, UK
    Hi CrazyBishop
    Do you mean that your new cloned drive worked in all respects and only had one problem in that it Windows didn't recognize the old drive
    OR
    That it your new cloned drive did not work/would not boot?

    Just like you, I'm trying to understand the steps to proper cloning and to include in these steps the things you must do (and the reasons why) together with the things you must not do because of the problems they cause.

    I think that even Acronis Support confuses things by using the word "moves" in their responses rather than "copies" :
    RetiredBri
     
  4. CrazyBishop

    CrazyBishop Registered Member

    Joined:
    Nov 19, 2005
    Posts:
    5
    The first one: the new cloned drive worked in all respects and only had one problem in that it Windows didn't recognize the old drive..

    Is there any solution to this other than formatting the old harddrive completely ?...
     
  5. shieber

    shieber Registered Member

    Joined:
    Oct 27, 2004
    Posts:
    3,710
    If you clone, shut down, disconnect the original internal sys-drive, connecdt new drive where the old one was connected, boot on new drive, then windows locks on the new drive as the sys drive. Then you can shut down and reconnect the old drive and the new one will remain recognized by windows as the sys drive. You can go ahead and reformat the old drive then.

    Windows Drive Manager might show the old drive as an active, which doesn't seem to hurt anything but you can reformat to change that or just ignore it.


    This has worked for me many times.
    sh
     
  6. Menorcaman

    Menorcaman Retired Moderator

    Joined:
    Aug 19, 2004
    Posts:
    4,661
    Location:
    Menorca (Balearic Islands) Spain
    The reason you need to remove the old drive before booting into Windows XP (or 2K) for the first time is beautifully explained in this Dan Goodell article titled <Fixing Windows 2000/XP Drive Letters>. In fact, IMHO, the technical areas of <Dan Goodell's Web Site> contain so many golden nuggets of information that it should be in every computer enthusiast's Favorites folder.

    Regards
     
Thread Status:
Not open for further replies.