error loading os

Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

Hi,
I have 2 SATA drives, and I've been struggling to do a simple clone of my
Seagate C: partiton to a Maxtor F: partition.
I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
most cases I got as far as a login screen and it reverted to a plain blue
screen with cursor. I always remove Seagate before trying to boot with the
cloned Maxtor. The only thing that did consistently work was Acronis Migrate
Easy, but the problem is that you need to copy the entire disk. That means
overwriting the other Maxtor partitions. But it proves that it did work. Now
why did it, and not the others?

Now whilst playing around with all this I noticed that I was getting 'error
loading os' when trying to boot. When I went back to Acronis, that was also
giving this message, and not even attempting to boot as it had previosly
done. I tried using sysprep with the same result.

Then I tried removing partitions completely from the Maxtor, using fdisk and
dos to format, using Max Blast to format, using the
XP repair tool, fixmbr, fixboot. You name it I tried it I think.

So I then thought I'd see if I could install XP on this drive. No, I get the
same message when it gets to the booting from disk stage.

Firstly, any ideas what could have caused this, and secondly do I need to do
a low level format to get this drive back to normal shipping condition. If
so, could someone tell me how, and what software to use, as I've done this
before.

I've now done a fair bit of reading about cloning. For a lot of people it
seems to be a completely painless process using Ghost or Acronis. For many
others including me, it just doesn't seem to work, and I've seen the same
issues reported over and over with no workable solutions.

Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,

Dave Cockram
38 answers Last reply
More about error loading
  1. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    On your Seagate drive, did you add the SATA drivers?? The SATA drivers may
    need to be installed before you clone the drive??

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    > Hi,
    > I have 2 SATA drives, and I've been struggling to do a simple clone of my
    > Seagate C: partiton to a Maxtor F: partition.
    > I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    > most cases I got as far as a login screen and it reverted to a plain blue
    > screen with cursor. I always remove Seagate before trying to boot with the
    > cloned Maxtor. The only thing that did consistently work was Acronis
    > Migrate Easy, but the problem is that you need to copy the entire disk.
    > That means overwriting the other Maxtor partitions. But it proves that it
    > did work. Now why did it, and not the others?
    >
    > Now whilst playing around with all this I noticed that I was getting
    > 'error loading os' when trying to boot. When I went back to Acronis, that
    > was also giving this message, and not even attempting to boot as it had
    > previosly done. I tried using sysprep with the same result.
    >
    > Then I tried removing partitions completely from the Maxtor, using fdisk
    > and dos to format, using Max Blast to format, using the
    > XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >
    > So I then thought I'd see if I could install XP on this drive. No, I get
    > the same message when it gets to the booting from disk stage.
    >
    > Firstly, any ideas what could have caused this, and secondly do I need to
    > do a low level format to get this drive back to normal shipping condition.
    > If so, could someone tell me how, and what software to use, as I've done
    > this before.
    >
    > I've now done a fair bit of reading about cloning. For a lot of people it
    > seems to be a completely painless process using Ghost or Acronis. For many
    > others including me, it just doesn't seem to work, and I've seen the same
    > issues reported over and over with no workable solutions.
    >
    > Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >
    > Dave Cockram
    >
  2. Archived from groups: microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    David,

    Try using the Maxtor as a SLAVE, first. Install the Maxtor software, from
    CD to the Master HD. ONce done you have XP on the master with the necessary
    files to enable reading of the Maxtor HD. Format the Maxtor to a single
    Partition and then when complete use the ghost to copy from Master to SLave.
    Now remove the Master, set the jumpers on the slave for Master and reboot. If
    this doesn't work, ignore what I said, have a couple of shots of J.D. and
    start over. Good Luck.


    "David Cockram" wrote:

    > Hi,
    > I have 2 SATA drives, and I've been struggling to do a simple clone of my
    > Seagate C: partiton to a Maxtor F: partition.
    > I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    > most cases I got as far as a login screen and it reverted to a plain blue
    > screen with cursor. I always remove Seagate before trying to boot with the
    > cloned Maxtor. The only thing that did consistently work was Acronis Migrate
    > Easy, but the problem is that you need to copy the entire disk. That means
    > overwriting the other Maxtor partitions. But it proves that it did work. Now
    > why did it, and not the others?
    >
    > Now whilst playing around with all this I noticed that I was getting 'error
    > loading os' when trying to boot. When I went back to Acronis, that was also
    > giving this message, and not even attempting to boot as it had previosly
    > done. I tried using sysprep with the same result.
    >
    > Then I tried removing partitions completely from the Maxtor, using fdisk and
    > dos to format, using Max Blast to format, using the
    > XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >
    > So I then thought I'd see if I could install XP on this drive. No, I get the
    > same message when it gets to the booting from disk stage.
    >
    > Firstly, any ideas what could have caused this, and secondly do I need to do
    > a low level format to get this drive back to normal shipping condition. If
    > so, could someone tell me how, and what software to use, as I've done this
    > before.
    >
    > I've now done a fair bit of reading about cloning. For a lot of people it
    > seems to be a completely painless process using Ghost or Acronis. For many
    > others including me, it just doesn't seem to work, and I've seen the same
    > issues reported over and over with no workable solutions.
    >
    > Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >
    > Dave Cockram
    >
    >
    >
  3. Archived from groups: microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Another thing that you might check is in your Bios to make sure that the
    SATA drive is still set as the boot drive. My system will periodically drop
    the Sata drive as the boot drive and I have to go into the Bios and reset it
    as the boot drive. I have not found an answer as to why that happens but so
    far everytime that I have recieved the error loading os that has been the
    problem. Just a thought.

    Jeff

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    > Hi,
    > I have 2 SATA drives, and I've been struggling to do a simple clone of my
    > Seagate C: partiton to a Maxtor F: partition.
    > I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    > most cases I got as far as a login screen and it reverted to a plain blue
    > screen with cursor. I always remove Seagate before trying to boot with the
    > cloned Maxtor. The only thing that did consistently work was Acronis
    Migrate
    > Easy, but the problem is that you need to copy the entire disk. That means
    > overwriting the other Maxtor partitions. But it proves that it did work.
    Now
    > why did it, and not the others?
    >
    > Now whilst playing around with all this I noticed that I was getting
    'error
    > loading os' when trying to boot. When I went back to Acronis, that was
    also
    > giving this message, and not even attempting to boot as it had previosly
    > done. I tried using sysprep with the same result.
    >
    > Then I tried removing partitions completely from the Maxtor, using fdisk
    and
    > dos to format, using Max Blast to format, using the
    > XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >
    > So I then thought I'd see if I could install XP on this drive. No, I get
    the
    > same message when it gets to the booting from disk stage.
    >
    > Firstly, any ideas what could have caused this, and secondly do I need to
    do
    > a low level format to get this drive back to normal shipping condition. If
    > so, could someone tell me how, and what software to use, as I've done this
    > before.
    >
    > I've now done a fair bit of reading about cloning. For a lot of people it
    > seems to be a completely painless process using Ghost or Acronis. For many
    > others including me, it just doesn't seem to work, and I've seen the same
    > issues reported over and over with no workable solutions.
    >
    > Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >
    > Dave Cockram
    >
    >
  4. Archived from groups: microsoft.public.windowsxp.general (More info?)

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    > Hi,
    > I have 2 SATA drives, and I've been struggling to do a simple clone of my
    > Seagate C: partiton to a Maxtor F: partition.
    > I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    > most cases I got as far as a login screen and it reverted to a plain blue
    > screen with cursor. I always remove Seagate before trying to boot with the
    > cloned Maxtor. The only thing that did consistently work was Acronis
    > Migrate Easy, but the problem is that you need to copy the entire disk.
    > That means overwriting the other Maxtor partitions. But it proves that it
    > did work. Now why did it, and not the others?
    >
    > Now whilst playing around with all this I noticed that I was getting
    > 'error loading os' when trying to boot. When I went back to Acronis, that
    > was also giving this message, and not even attempting to boot as it had
    > previosly done. I tried using sysprep with the same result.
    >
    > Then I tried removing partitions completely from the Maxtor, using fdisk
    > and dos to format, using Max Blast to format, using the
    > XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >
    > So I then thought I'd see if I could install XP on this drive. No, I get
    > the same message when it gets to the booting from disk stage.
    >
    > Firstly, any ideas what could have caused this, and secondly do I need to
    > do a low level format to get this drive back to normal shipping condition.
    > If so, could someone tell me how, and what software to use, as I've done
    > this before.
    >
    > I've now done a fair bit of reading about cloning. For a lot of people it
    > seems to be a completely painless process using Ghost or Acronis. For many
    > others including me, it just doesn't seem to work, and I've seen the same
    > issues reported over and over with no workable solutions.
    >
    > Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >
    > Dave Cockram


    Dave:
    Let's take it step-by-step...
    1. We're dealing with two internal HDs here, right? The Seagate is your
    day-to-day bootable drive containing the XP OS and it's connected as Primary
    Master while the Maxtor is a second internal HD (presumably a data drive -
    non-bootable) either connected as Primary Slave or connected as Master or
    Slave on your secondary IDE channel. Do I have this right?

    2. You're certain that both drives are sound and that your source disk (the
    Seagate) is free of any system files corruption that prevent it making a
    normal boot, correct?

    3. You're also certain that both drives are connected/configured properly,
    i.e., correctly jumpered and securely connected with their IDE cables,
    right?

    4. When you say your objective is "to do a simple clone of my Seagate C:
    partiton to a Maxtor F: partition.", are you talking about a disk-to-disk
    clone of the entire contents of your Seagate drive to the Maxtor drive,
    yes?. Or are you really dealing with cloning multi-partitioned drives here?

    Please answer the above and then we can take you through the cloning process
    step-by-step using Ghost 2003 (I prefer to work with that version using the
    Ghost bootable floppy disk), it's included as a separate CD in the Ghost 9
    package) or Acronis True Image (I prefer to work with the ATI bootable CD).
    Anna
  5. Archived from groups: microsoft.public.windowsxp.general (More info?)

    The guys above have covered all software backups pretty well, so could i
    suggest another option?

    Have you considered a RAID config? That may help in this...

    http://msdn.microsoft.com/archive/en-us/dnarntpro00/html/RAID.asp

    heres all MS's infro on it
    http://www.google.com.au/search?q=raid+how+site%3Amicrosoft.com&btnG=Search&hl=en

    Good luck

    Cheers

    Quintin
    MVP wannabe

    "David Cockram" wrote:

    > Hi,
    > I have 2 SATA drives, and I've been struggling to do a simple clone of my
    > Seagate C: partiton to a Maxtor F: partition.
    > I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    > most cases I got as far as a login screen and it reverted to a plain blue
    > screen with cursor. I always remove Seagate before trying to boot with the
    > cloned Maxtor. The only thing that did consistently work was Acronis Migrate
    > Easy, but the problem is that you need to copy the entire disk. That means
    > overwriting the other Maxtor partitions. But it proves that it did work. Now
    > why did it, and not the others?
    >
    > Now whilst playing around with all this I noticed that I was getting 'error
    > loading os' when trying to boot. When I went back to Acronis, that was also
    > giving this message, and not even attempting to boot as it had previosly
    > done. I tried using sysprep with the same result.
    >
    > Then I tried removing partitions completely from the Maxtor, using fdisk and
    > dos to format, using Max Blast to format, using the
    > XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >
    > So I then thought I'd see if I could install XP on this drive. No, I get the
    > same message when it gets to the booting from disk stage.
    >
    > Firstly, any ideas what could have caused this, and secondly do I need to do
    > a low level format to get this drive back to normal shipping condition. If
    > so, could someone tell me how, and what software to use, as I've done this
    > before.
    >
    > I've now done a fair bit of reading about cloning. For a lot of people it
    > seems to be a completely painless process using Ghost or Acronis. For many
    > others including me, it just doesn't seem to work, and I've seen the same
    > issues reported over and over with no workable solutions.
    >
    > Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >
    > Dave Cockram
    >
    >
    >
  6. Archived from groups: microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    "Jeff" <jefffby@yahoo.com> wrote in message
    news:42681fd0$2_3@newspeer2.tds.net...
    > Another thing that you might check is in your Bios to make sure that the
    > SATA drive is still set as the boot drive. My system will periodically
    > drop
    > the Sata drive as the boot drive and I have to go into the Bios and reset
    > it
    > as the boot drive. I have not found an answer as to why that happens but
    > so
    > far everytime that I have recieved the error loading os that has been the
    > problem. Just a thought.
    >
    > Jeff
    >

    I seem to have found a cure for my particular “Error loading OS” problem.


    I have two Maxtor SATA hard disc drives. These show up in my BIOS as
    PM-Maxtor, and underneath SM-Maxtor (i.e. Primary and Secondary). The first
    drive in this list, PM-Maxtor, is the boot drive containing the operating
    system.


    On boot-up, the BIOS looks for an operating system on the first drive in the
    list only. Thus it looks on PM-Maxtor, finds the operating system, and boots
    up.


    However, about once a week on boot-up I got the “Error loading OS” message.
    I noticed that in the BIOS, PM-Maxtor and SM-Maxtor had changed places. So
    SM-Maxtor was being searched for the operating system – and it did not have
    one of course.


    I think I may have found out why this changeover was happening. The SATA
    lead connecting the PM-Maxtor drive to the motherboard fitted very loosely
    on the pins on the drive. At boot-up, with the metal cold, it was as though
    the PM drive was not making good enough contact with the motherboard and was
    not being properly detected by the BIOS.


    I replaced the SATA connecting lead with one of a better quality that
    gripped the connecting pins on the drive more firmly, and have not had the
    “Error loading OS” message in four months. As it was happening weekly in the
    two months prior to changing the lead, I think there is a strong possibility
    that the problem, in my case at least, was caused by poor electrical
    connections. (Once I suspected what was happening, I pushed the original
    lead onto the drive tightly, where it lasted about a week before giving
    trouble again.)


    I should be interested to know what make of drive and SATA lead is being
    used by anyone else with this problem.


    Cycle.
  7. Archived from groups: microsoft.public.windowsxp.general (More info?)

    That's a very interesting idea. I hadn't realised you could just mirror a
    particular partition with raid. However it wouldn't help me here as my main
    reason is to have a clean installation of xp & programs which takes many
    hours to reinstall. I had a problem prompted by all this whereby one of my
    programs just stopped working, and it wouldn't reinstall. The mirror would
    have an identical problem.


    "Quintin" <Quintin@discussions.microsoft.com> wrote in message
    news:6428B0FA-F283-4CC6-BB41-085CD34CA768@microsoft.com...
    > The guys above have covered all software backups pretty well, so could i
    > suggest another option?
    >
    > Have you considered a RAID config? That may help in this...
    >
    > http://msdn.microsoft.com/archive/en-us/dnarntpro00/html/RAID.asp
    >
    > heres all MS's infro on it
    > http://www.google.com.au/search?q=raid+how+site%3Amicrosoft.com&btnG=Search&hl=en
    >
    > Good luck
    >
    > Cheers
    >
    > Quintin
    > MVP wannabe
    >
    > "David Cockram" wrote:
    >
    >> Hi,
    >> I have 2 SATA drives, and I've been struggling to do a simple clone of my
    >> Seagate C: partiton to a Maxtor F: partition.
    >> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    >> most cases I got as far as a login screen and it reverted to a plain blue
    >> screen with cursor. I always remove Seagate before trying to boot with
    >> the
    >> cloned Maxtor. The only thing that did consistently work was Acronis
    >> Migrate
    >> Easy, but the problem is that you need to copy the entire disk. That
    >> means
    >> overwriting the other Maxtor partitions. But it proves that it did work.
    >> Now
    >> why did it, and not the others?
    >>
    >> Now whilst playing around with all this I noticed that I was getting
    >> 'error
    >> loading os' when trying to boot. When I went back to Acronis, that was
    >> also
    >> giving this message, and not even attempting to boot as it had previosly
    >> done. I tried using sysprep with the same result.
    >>
    >> Then I tried removing partitions completely from the Maxtor, using fdisk
    >> and
    >> dos to format, using Max Blast to format, using the
    >> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>
    >> So I then thought I'd see if I could install XP on this drive. No, I get
    >> the
    >> same message when it gets to the booting from disk stage.
    >>
    >> Firstly, any ideas what could have caused this, and secondly do I need to
    >> do
    >> a low level format to get this drive back to normal shipping condition.
    >> If
    >> so, could someone tell me how, and what software to use, as I've done
    >> this
    >> before.
    >>
    >> I've now done a fair bit of reading about cloning. For a lot of people it
    >> seems to be a completely painless process using Ghost or Acronis. For
    >> many
    >> others including me, it just doesn't seem to work, and I've seen the same
    >> issues reported over and over with no workable solutions.
    >>
    >> Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >>
    >> Dave Cockram
    >>
    >>
    >>
  8. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    OK, we're making some progress here. I can now make and restore a clone copy
    in Acronis 8.0.

    I need to follow these steps EXACTLY.

    1. Don't format or give a drive letter to the recipient drive (Maxtor first
    partition here)
    2. Use Acronis from boot CD not XP
    3. Swap SATA cables before rebooting so Maxtor drive is now on same cable as
    original Seagate

    And this is the killer - if I don't do one of these and the cloning process
    fails, than it will ALWAYS fail UNTIL I do a disk copy with Acronis. This
    overwrites my entire drive and it's not entirely convenient to ship out
    100GB of data to somewhere else. (Andrew mentions earlier in the thread a
    method using recovery console which I'll try if I need to in future.) And
    bizarrely this not only clones the drive correctly, but it puts it back to
    normal such that I can now successfully clone a partition.

    So, what on earth is going on here? Why did the boot sector get screwed up
    ( I assume that's what it was) and why did none of the standard fixes for
    this type of problem not work - fixboot /fixmbr?

    I gather at least some of this is caused by me using SATA drives. Perhaps
    there will be no such problems with Ghost 10.0 and Acronis 9.0?

    Dave


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    > Hi,
    > I have 2 SATA drives, and I've been struggling to do a simple clone of my
    > Seagate C: partiton to a Maxtor F: partition.
    > I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    > most cases I got as far as a login screen and it reverted to a plain blue
    > screen with cursor. I always remove Seagate before trying to boot with the
    > cloned Maxtor. The only thing that did consistently work was Acronis
    > Migrate Easy, but the problem is that you need to copy the entire disk.
    > That means overwriting the other Maxtor partitions. But it proves that it
    > did work. Now why did it, and not the others?
    >
    > Now whilst playing around with all this I noticed that I was getting
    > 'error loading os' when trying to boot. When I went back to Acronis, that
    > was also giving this message, and not even attempting to boot as it had
    > previosly done. I tried using sysprep with the same result.
    >
    > Then I tried removing partitions completely from the Maxtor, using fdisk
    > and dos to format, using Max Blast to format, using the
    > XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >
    > So I then thought I'd see if I could install XP on this drive. No, I get
    > the same message when it gets to the booting from disk stage.
    >
    > Firstly, any ideas what could have caused this, and secondly do I need to
    > do a low level format to get this drive back to normal shipping condition.
    > If so, could someone tell me how, and what software to use, as I've done
    > this before.
    >
    > I've now done a fair bit of reading about cloning. For a lot of people it
    > seems to be a completely painless process using Ghost or Acronis. For many
    > others including me, it just doesn't seem to work, and I've seen the same
    > issues reported over and over with no workable solutions.
    >
    > Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >
    > Dave Cockram
    >
  9. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Prior to the clone, delete all but the default value from
    HKLM\system\mounteddevices.

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    > OK, we're making some progress here. I can now make and restore a clone
    > copy in Acronis 8.0.
    >
    > I need to follow these steps EXACTLY.
    >
    > 1. Don't format or give a drive letter to the recipient drive (Maxtor
    > first partition here)
    > 2. Use Acronis from boot CD not XP
    > 3. Swap SATA cables before rebooting so Maxtor drive is now on same cable
    > as original Seagate
    >
    > And this is the killer - if I don't do one of these and the cloning
    > process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    > Acronis. This overwrites my entire drive and it's not entirely convenient
    > to ship out 100GB of data to somewhere else. (Andrew mentions earlier in
    > the thread a method using recovery console which I'll try if I need to in
    > future.) And bizarrely this not only clones the drive correctly, but it
    > puts it back to normal such that I can now successfully clone a partition.
    >
    > So, what on earth is going on here? Why did the boot sector get screwed
    > up ( I assume that's what it was) and why did none of the standard fixes
    > for this type of problem not work - fixboot /fixmbr?
    >
    > I gather at least some of this is caused by me using SATA drives. Perhaps
    > there will be no such problems with Ghost 10.0 and Acronis 9.0?
    >
    > Dave
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >> Hi,
    >> I have 2 SATA drives, and I've been struggling to do a simple clone of my
    >> Seagate C: partiton to a Maxtor F: partition.
    >> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
    >> most cases I got as far as a login screen and it reverted to a plain blue
    >> screen with cursor. I always remove Seagate before trying to boot with
    >> the cloned Maxtor. The only thing that did consistently work was Acronis
    >> Migrate Easy, but the problem is that you need to copy the entire disk.
    >> That means overwriting the other Maxtor partitions. But it proves that it
    >> did work. Now why did it, and not the others?
    >>
    >> Now whilst playing around with all this I noticed that I was getting
    >> 'error loading os' when trying to boot. When I went back to Acronis, that
    >> was also giving this message, and not even attempting to boot as it had
    >> previosly done. I tried using sysprep with the same result.
    >>
    >> Then I tried removing partitions completely from the Maxtor, using fdisk
    >> and dos to format, using Max Blast to format, using the
    >> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>
    >> So I then thought I'd see if I could install XP on this drive. No, I get
    >> the same message when it gets to the booting from disk stage.
    >>
    >> Firstly, any ideas what could have caused this, and secondly do I need to
    >> do a low level format to get this drive back to normal shipping
    >> condition. If so, could someone tell me how, and what software to use, as
    >> I've done this before.
    >>
    >> I've now done a fair bit of reading about cloning. For a lot of people it
    >> seems to be a completely painless process using Ghost or Acronis. For
    >> many others including me, it just doesn't seem to work, and I've seen the
    >> same issues reported over and over with no workable solutions.
    >>
    >> Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >>
    >> Dave Cockram
    >>
    >
    >
  10. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Presumably XP will just rebuild this from scratch again? Do you think that
    is what stopped the clone booting when it almost got to the login screen and
    then reverted to a plain blue screen with cursor?

    Dave
    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    > Prior to the clone, delete all but the default value from
    > HKLM\system\mounteddevices.
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >> OK, we're making some progress here. I can now make and restore a clone
    >> copy in Acronis 8.0.
    >>
    >> I need to follow these steps EXACTLY.
    >>
    >> 1. Don't format or give a drive letter to the recipient drive (Maxtor
    >> first partition here)
    >> 2. Use Acronis from boot CD not XP
    >> 3. Swap SATA cables before rebooting so Maxtor drive is now on same cable
    >> as original Seagate
    >>
    >> And this is the killer - if I don't do one of these and the cloning
    >> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >> Acronis. This overwrites my entire drive and it's not entirely convenient
    >> to ship out 100GB of data to somewhere else. (Andrew mentions earlier in
    >> the thread a method using recovery console which I'll try if I need to in
    >> future.) And bizarrely this not only clones the drive correctly, but it
    >> puts it back to normal such that I can now successfully clone a
    >> partition.
    >>
    >> So, what on earth is going on here? Why did the boot sector get screwed
    >> up ( I assume that's what it was) and why did none of the standard fixes
    >> for this type of problem not work - fixboot /fixmbr?
    >>
    >> I gather at least some of this is caused by me using SATA drives. Perhaps
    >> there will be no such problems with Ghost 10.0 and Acronis 9.0?
    >>
    >> Dave
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>> Hi,
    >>> I have 2 SATA drives, and I've been struggling to do a simple clone of
    >>> my Seagate C: partiton to a Maxtor F: partition.
    >>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software.
    >>> In most cases I got as far as a login screen and it reverted to a plain
    >>> blue screen with cursor. I always remove Seagate before trying to boot
    >>> with the cloned Maxtor. The only thing that did consistently work was
    >>> Acronis Migrate Easy, but the problem is that you need to copy the
    >>> entire disk. That means overwriting the other Maxtor partitions. But it
    >>> proves that it did work. Now why did it, and not the others?
    >>>
    >>> Now whilst playing around with all this I noticed that I was getting
    >>> 'error loading os' when trying to boot. When I went back to Acronis,
    >>> that was also giving this message, and not even attempting to boot as it
    >>> had previosly done. I tried using sysprep with the same result.
    >>>
    >>> Then I tried removing partitions completely from the Maxtor, using fdisk
    >>> and dos to format, using Max Blast to format, using the
    >>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>
    >>> So I then thought I'd see if I could install XP on this drive. No, I get
    >>> the same message when it gets to the booting from disk stage.
    >>>
    >>> Firstly, any ideas what could have caused this, and secondly do I need
    >>> to do a low level format to get this drive back to normal shipping
    >>> condition. If so, could someone tell me how, and what software to use,
    >>> as I've done this before.
    >>>
    >>> I've now done a fair bit of reading about cloning. For a lot of people
    >>> it seems to be a completely painless process using Ghost or Acronis. For
    >>> many others including me, it just doesn't seem to work, and I've seen
    >>> the same issues reported over and over with no workable solutions.
    >>>
    >>> Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,
    >>>
    >>> Dave Cockram
    >>>
    >>
    >>
    >
  11. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Yes it will get rebuilt and yes, if that's not deleted then cloning just the
    partition image itself can cause some less than desirable results. In fact
    if you check
    HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore MS back
    up / restore tools don't restore that key.

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    > Presumably XP will just rebuild this from scratch again? Do you think that
    > is what stopped the clone booting when it almost got to the login screen
    > and then reverted to a plain blue screen with cursor?
    >
    > Dave
    > "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    > news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >> Prior to the clone, delete all but the default value from
    >> HKLM\system\mounteddevices.
    >>
    >> --
    >> Walter Clayton
    >> Any technology distinguishable from magic is insufficiently advanced.
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>> OK, we're making some progress here. I can now make and restore a clone
    >>> copy in Acronis 8.0.
    >>>
    >>> I need to follow these steps EXACTLY.
    >>>
    >>> 1. Don't format or give a drive letter to the recipient drive (Maxtor
    >>> first partition here)
    >>> 2. Use Acronis from boot CD not XP
    >>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>> cable as original Seagate
    >>>
    >>> And this is the killer - if I don't do one of these and the cloning
    >>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>> Acronis. This overwrites my entire drive and it's not entirely
    >>> convenient to ship out 100GB of data to somewhere else. (Andrew mentions
    >>> earlier in the thread a method using recovery console which I'll try if
    >>> I need to in future.) And bizarrely this not only clones the drive
    >>> correctly, but it puts it back to normal such that I can now
    >>> successfully clone a partition.
    >>>
    >>> So, what on earth is going on here? Why did the boot sector get screwed
    >>> up ( I assume that's what it was) and why did none of the standard fixes
    >>> for this type of problem not work - fixboot /fixmbr?
    >>>
    >>> I gather at least some of this is caused by me using SATA drives.
    >>> Perhaps there will be no such problems with Ghost 10.0 and Acronis 9.0?
    >>>
    >>> Dave
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>> Hi,
    >>>> I have 2 SATA drives, and I've been struggling to do a simple clone of
    >>>> my Seagate C: partiton to a Maxtor F: partition.
    >>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software.
    >>>> In most cases I got as far as a login screen and it reverted to a plain
    >>>> blue screen with cursor. I always remove Seagate before trying to boot
    >>>> with the cloned Maxtor. The only thing that did consistently work was
    >>>> Acronis Migrate Easy, but the problem is that you need to copy the
    >>>> entire disk. That means overwriting the other Maxtor partitions. But it
    >>>> proves that it did work. Now why did it, and not the others?
    >>>>
    >>>> Now whilst playing around with all this I noticed that I was getting
    >>>> 'error loading os' when trying to boot. When I went back to Acronis,
    >>>> that was also giving this message, and not even attempting to boot as
    >>>> it had previosly done. I tried using sysprep with the same result.
    >>>>
    >>>> Then I tried removing partitions completely from the Maxtor, using
    >>>> fdisk and dos to format, using Max Blast to format, using the
    >>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>
    >>>> So I then thought I'd see if I could install XP on this drive. No, I
    >>>> get the same message when it gets to the booting from disk stage.
    >>>>
    >>>> Firstly, any ideas what could have caused this, and secondly do I need
    >>>> to do a low level format to get this drive back to normal shipping
    >>>> condition. If so, could someone tell me how, and what software to use,
    >>>> as I've done this before.
    >>>>
    >>>> I've now done a fair bit of reading about cloning. For a lot of people
    >>>> it seems to be a completely painless process using Ghost or Acronis.
    >>>> For many others including me, it just doesn't seem to work, and I've
    >>>> seen the same issues reported over and over with no workable solutions.
    >>>>
    >>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>> Thanks,
    >>>>
    >>>> Dave Cockram
    >>>>
    >>>
    >>>
    >>
    >
    >
  12. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter, HELP! ! !

    I deleted that key as suggested, HKLM\system\mounteddevices (except default
    value).
    Before restoring the clone onto the other drive I decided to just check the
    values in the key after rebooting and supposedly rebuilding.

    After entering my password at the log in screen, it immediately reverts to
    logging off . . .
    I have tried everything I can think of, safe mode, boot disk but can't log
    on any more.

    I then tried restoring the saved cloned partition to the other drive and got
    NTLDR is missing. So now I don't have any bootable drives.Back to Acronis
    boot CD to restore an earlier clone that worked and restored. The first
    partition, E: on the Maxtor was greyed out so I couldn't access it. I
    eventually used MaxBlast to repartition and then Acronis restore worked, and
    I'm now back to using an earlier saved clone that I've restored on the
    Maxtor. I haven't touched the Seagate C: so if there's a way of accessing
    and putting back this registry key (which I stupidly didn't feel the need to
    save) maybe I can get back to normal.

    I swear once this is over, I won't touch any of this software for a long,
    long time. There are just too many issues and problems here. Restoring all
    my programs in an emergency pales to insignificance compared with the time
    and hassle spent so far.

    Thanks in anticipation,

    Dave


    ----- Original Message -----
    From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    Newsgroups:
    microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    Sent: Sunday, April 24, 2005 1:28 AM
    Subject: Re: error loading os


    > Yes it will get rebuilt and yes, if that's not deleted then cloning just
    > the partition image itself can cause some less than desirable results. In
    > fact if you check
    > HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore MS
    > back up / restore tools don't restore that key.
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >> Presumably XP will just rebuild this from scratch again? Do you think
    >> that is what stopped the clone booting when it almost got to the login
    >> screen and then reverted to a plain blue screen with cursor?
    >>
    >> Dave
    >> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>> Prior to the clone, delete all but the default value from
    >>> HKLM\system\mounteddevices.
    >>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>> OK, we're making some progress here. I can now make and restore a clone
    >>>> copy in Acronis 8.0.
    >>>>
    >>>> I need to follow these steps EXACTLY.
    >>>>
    >>>> 1. Don't format or give a drive letter to the recipient drive (Maxtor
    >>>> first partition here)
    >>>> 2. Use Acronis from boot CD not XP
    >>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>>> cable as original Seagate
    >>>>
    >>>> And this is the killer - if I don't do one of these and the cloning
    >>>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>>> Acronis. This overwrites my entire drive and it's not entirely
    >>>> convenient to ship out 100GB of data to somewhere else. (Andrew
    >>>> mentions earlier in the thread a method using recovery console which
    >>>> I'll try if I need to in future.) And bizarrely this not only clones
    >>>> the drive correctly, but it puts it back to normal such that I can now
    >>>> successfully clone a partition.
    >>>>
    >>>> So, what on earth is going on here? Why did the boot sector get
    >>>> screwed up ( I assume that's what it was) and why did none of the
    >>>> standard fixes for this type of problem not work - fixboot /fixmbr?
    >>>>
    >>>> I gather at least some of this is caused by me using SATA drives.
    >>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis 9.0?
    >>>>
    >>>> Dave
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>> Hi,
    >>>>> I have 2 SATA drives, and I've been struggling to do a simple clone of
    >>>>> my Seagate C: partiton to a Maxtor F: partition.
    >>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software.
    >>>>> In most cases I got as far as a login screen and it reverted to a
    >>>>> plain blue screen with cursor. I always remove Seagate before trying
    >>>>> to boot with the cloned Maxtor. The only thing that did consistently
    >>>>> work was Acronis Migrate Easy, but the problem is that you need to
    >>>>> copy the entire disk. That means overwriting the other Maxtor
    >>>>> partitions. But it proves that it did work. Now why did it, and not
    >>>>> the others?
    >>>>>
    >>>>> Now whilst playing around with all this I noticed that I was getting
    >>>>> 'error loading os' when trying to boot. When I went back to Acronis,
    >>>>> that was also giving this message, and not even attempting to boot as
    >>>>> it had previosly done. I tried using sysprep with the same result.
    >>>>>
    >>>>> Then I tried removing partitions completely from the Maxtor, using
    >>>>> fdisk and dos to format, using Max Blast to format, using the
    >>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>
    >>>>> So I then thought I'd see if I could install XP on this drive. No, I
    >>>>> get the same message when it gets to the booting from disk stage.
    >>>>>
    >>>>> Firstly, any ideas what could have caused this, and secondly do I need
    >>>>> to do a low level format to get this drive back to normal shipping
    >>>>> condition. If so, could someone tell me how, and what software to use,
    >>>>> as I've done this before.
    >>>>>
    >>>>> I've now done a fair bit of reading about cloning. For a lot of people
    >>>>> it seems to be a completely painless process using Ghost or Acronis.
    >>>>> For many others including me, it just doesn't seem to work, and I've
    >>>>> seen the same issues reported over and over with no workable
    >>>>> solutions.
    >>>>>
    >>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>> Thanks,
    >>>>>
    >>>>> Dave Cockram
    >>>>>
    >>>>
    >>>>
    >>>
    >>
    >>
    >
  13. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    I assume you're up and running on the problematic platform? If so, go to
    http://www.bootitng.com/utilities.html and download Partinfo. Unzip it and
    run partinfW (yes, that W not O) from a command prompt as follows:

    partinfw >partinfo.txt
    start notepad partinfo.txt

    Then copy and paste the contents back here. Also, do start->run->c:\boot.ini
    and copy and paste the contents of boot.ini back here as well.


    I think I know what your issue is now and it's going to revolve around
    boot.ini and the mbr code and now that I've taken a really fast look at
    Acronis, it may be the tool isn't the right tool for what you're attempting.
    Or you may be using it wrong.

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    > Walter, HELP! ! !
    >
    > I deleted that key as suggested, HKLM\system\mounteddevices (except
    > default
    > value).
    > Before restoring the clone onto the other drive I decided to just check
    > the
    > values in the key after rebooting and supposedly rebuilding.
    >
    > After entering my password at the log in screen, it immediately reverts to
    > logging off . . .
    > I have tried everything I can think of, safe mode, boot disk but can't log
    > on any more.
    >
    > I then tried restoring the saved cloned partition to the other drive and
    > got
    > NTLDR is missing. So now I don't have any bootable drives.Back to Acronis
    > boot CD to restore an earlier clone that worked and restored. The first
    > partition, E: on the Maxtor was greyed out so I couldn't access it. I
    > eventually used MaxBlast to repartition and then Acronis restore worked,
    > and
    > I'm now back to using an earlier saved clone that I've restored on the
    > Maxtor. I haven't touched the Seagate C: so if there's a way of accessing
    > and putting back this registry key (which I stupidly didn't feel the need
    > to
    > save) maybe I can get back to normal.
    >
    > I swear once this is over, I won't touch any of this software for a long,
    > long time. There are just too many issues and problems here. Restoring all
    > my programs in an emergency pales to insignificance compared with the time
    > and hassle spent so far.
    >
    > Thanks in anticipation,
    >
    > Dave
    >
    >
    > ----- Original Message -----
    > From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    > Newsgroups:
    > microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    > Sent: Sunday, April 24, 2005 1:28 AM
    > Subject: Re: error loading os
    >
    >
    >> Yes it will get rebuilt and yes, if that's not deleted then cloning just
    >> the partition image itself can cause some less than desirable results. In
    >> fact if you check
    >> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore MS
    >> back up / restore tools don't restore that key.
    >>
    >> --
    >> Walter Clayton
    >> Any technology distinguishable from magic is insufficiently advanced.
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>> Presumably XP will just rebuild this from scratch again? Do you think
    >>> that is what stopped the clone booting when it almost got to the login
    >>> screen and then reverted to a plain blue screen with cursor?
    >>>
    >>> Dave
    >>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>> Prior to the clone, delete all but the default value from
    >>>> HKLM\system\mounteddevices.
    >>>>
    >>>> --
    >>>> Walter Clayton
    >>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>> OK, we're making some progress here. I can now make and restore a
    >>>>> clone copy in Acronis 8.0.
    >>>>>
    >>>>> I need to follow these steps EXACTLY.
    >>>>>
    >>>>> 1. Don't format or give a drive letter to the recipient drive (Maxtor
    >>>>> first partition here)
    >>>>> 2. Use Acronis from boot CD not XP
    >>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>>>> cable as original Seagate
    >>>>>
    >>>>> And this is the killer - if I don't do one of these and the cloning
    >>>>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>>>> Acronis. This overwrites my entire drive and it's not entirely
    >>>>> convenient to ship out 100GB of data to somewhere else. (Andrew
    >>>>> mentions earlier in the thread a method using recovery console which
    >>>>> I'll try if I need to in future.) And bizarrely this not only clones
    >>>>> the drive correctly, but it puts it back to normal such that I can now
    >>>>> successfully clone a partition.
    >>>>>
    >>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>> standard fixes for this type of problem not work - fixboot /fixmbr?
    >>>>>
    >>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>> 9.0?
    >>>>>
    >>>>> Dave
    >>>>>
    >>>>>
    >>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>> Hi,
    >>>>>> I have 2 SATA drives, and I've been struggling to do a simple clone
    >>>>>> of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>> software. In most cases I got as far as a login screen and it
    >>>>>> reverted to a plain blue screen with cursor. I always remove Seagate
    >>>>>> before trying to boot with the cloned Maxtor. The only thing that did
    >>>>>> consistently work was Acronis Migrate Easy, but the problem is that
    >>>>>> you need to copy the entire disk. That means overwriting the other
    >>>>>> Maxtor partitions. But it proves that it did work. Now why did it,
    >>>>>> and not the others?
    >>>>>>
    >>>>>> Now whilst playing around with all this I noticed that I was getting
    >>>>>> 'error loading os' when trying to boot. When I went back to Acronis,
    >>>>>> that was also giving this message, and not even attempting to boot as
    >>>>>> it had previosly done. I tried using sysprep with the same result.
    >>>>>>
    >>>>>> Then I tried removing partitions completely from the Maxtor, using
    >>>>>> fdisk and dos to format, using Max Blast to format, using the
    >>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>
    >>>>>> So I then thought I'd see if I could install XP on this drive. No, I
    >>>>>> get the same message when it gets to the booting from disk stage.
    >>>>>>
    >>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>> need to do a low level format to get this drive back to normal
    >>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>> software to use, as I've done this before.
    >>>>>>
    >>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>> people it seems to be a completely painless process using Ghost or
    >>>>>> Acronis. For many others including me, it just doesn't seem to work,
    >>>>>> and I've seen the same issues reported over and over with no workable
    >>>>>> solutions.
    >>>>>>
    >>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>> Thanks,
    >>>>>>
    >>>>>> Dave Cockram
    >>>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >
    >
  14. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Thanks Walter,

    I'll do it now, but in the meantime, I'm only up and running on my second
    hard drive, the Maxtor. The Seagate which has the problem is inaccessable. I
    don't know if that affects things. Let me know if it does.

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >I assume you're up and running on the problematic platform? If so, go to
    >http://www.bootitng.com/utilities.html and download Partinfo. Unzip it and
    >run partinfW (yes, that W not O) from a command prompt as follows:
    >
    > partinfw >partinfo.txt
    > start notepad partinfo.txt
    >
    > Then copy and paste the contents back here. Also, do
    > start->run->c:\boot.ini and copy and paste the contents of boot.ini back
    > here as well.
    >
    >
    > I think I know what your issue is now and it's going to revolve around
    > boot.ini and the mbr code and now that I've taken a really fast look at
    > Acronis, it may be the tool isn't the right tool for what you're
    > attempting. Or you may be using it wrong.
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >> Walter, HELP! ! !
    >>
    >> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >> default
    >> value).
    >> Before restoring the clone onto the other drive I decided to just check
    >> the
    >> values in the key after rebooting and supposedly rebuilding.
    >>
    >> After entering my password at the log in screen, it immediately reverts
    >> to
    >> logging off . . .
    >> I have tried everything I can think of, safe mode, boot disk but can't
    >> log
    >> on any more.
    >>
    >> I then tried restoring the saved cloned partition to the other drive and
    >> got
    >> NTLDR is missing. So now I don't have any bootable drives.Back to Acronis
    >> boot CD to restore an earlier clone that worked and restored. The first
    >> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >> eventually used MaxBlast to repartition and then Acronis restore worked,
    >> and
    >> I'm now back to using an earlier saved clone that I've restored on the
    >> Maxtor. I haven't touched the Seagate C: so if there's a way of accessing
    >> and putting back this registry key (which I stupidly didn't feel the need
    >> to
    >> save) maybe I can get back to normal.
    >>
    >> I swear once this is over, I won't touch any of this software for a long,
    >> long time. There are just too many issues and problems here. Restoring
    >> all
    >> my programs in an emergency pales to insignificance compared with the
    >> time
    >> and hassle spent so far.
    >>
    >> Thanks in anticipation,
    >>
    >> Dave
    >>
    >>
    >> ----- Original Message -----
    >> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >> Newsgroups:
    >> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >> Sent: Sunday, April 24, 2005 1:28 AM
    >> Subject: Re: error loading os
    >>
    >>
    >>> Yes it will get rebuilt and yes, if that's not deleted then cloning just
    >>> the partition image itself can cause some less than desirable results.
    >>> In fact if you check
    >>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore MS
    >>> back up / restore tools don't restore that key.
    >>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>> Presumably XP will just rebuild this from scratch again? Do you think
    >>>> that is what stopped the clone booting when it almost got to the login
    >>>> screen and then reverted to a plain blue screen with cursor?
    >>>>
    >>>> Dave
    >>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>> Prior to the clone, delete all but the default value from
    >>>>> HKLM\system\mounteddevices.
    >>>>>
    >>>>> --
    >>>>> Walter Clayton
    >>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>
    >>>>>
    >>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>> clone copy in Acronis 8.0.
    >>>>>>
    >>>>>> I need to follow these steps EXACTLY.
    >>>>>>
    >>>>>> 1. Don't format or give a drive letter to the recipient drive (Maxtor
    >>>>>> first partition here)
    >>>>>> 2. Use Acronis from boot CD not XP
    >>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>>>>> cable as original Seagate
    >>>>>>
    >>>>>> And this is the killer - if I don't do one of these and the cloning
    >>>>>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>>>>> Acronis. This overwrites my entire drive and it's not entirely
    >>>>>> convenient to ship out 100GB of data to somewhere else. (Andrew
    >>>>>> mentions earlier in the thread a method using recovery console which
    >>>>>> I'll try if I need to in future.) And bizarrely this not only clones
    >>>>>> the drive correctly, but it puts it back to normal such that I can
    >>>>>> now successfully clone a partition.
    >>>>>>
    >>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>> standard fixes for this type of problem not work - fixboot /fixmbr?
    >>>>>>
    >>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>> 9.0?
    >>>>>>
    >>>>>> Dave
    >>>>>>
    >>>>>>
    >>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>> Hi,
    >>>>>>> I have 2 SATA drives, and I've been struggling to do a simple clone
    >>>>>>> of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>> reverted to a plain blue screen with cursor. I always remove Seagate
    >>>>>>> before trying to boot with the cloned Maxtor. The only thing that
    >>>>>>> did consistently work was Acronis Migrate Easy, but the problem is
    >>>>>>> that you need to copy the entire disk. That means overwriting the
    >>>>>>> other Maxtor partitions. But it proves that it did work. Now why did
    >>>>>>> it, and not the others?
    >>>>>>>
    >>>>>>> Now whilst playing around with all this I noticed that I was getting
    >>>>>>> 'error loading os' when trying to boot. When I went back to Acronis,
    >>>>>>> that was also giving this message, and not even attempting to boot
    >>>>>>> as it had previosly done. I tried using sysprep with the same
    >>>>>>> result.
    >>>>>>>
    >>>>>>> Then I tried removing partitions completely from the Maxtor, using
    >>>>>>> fdisk and dos to format, using Max Blast to format, using the
    >>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>
    >>>>>>> So I then thought I'd see if I could install XP on this drive. No, I
    >>>>>>> get the same message when it gets to the booting from disk stage.
    >>>>>>>
    >>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>> software to use, as I've done this before.
    >>>>>>>
    >>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>> people it seems to be a completely painless process using Ghost or
    >>>>>>> Acronis. For many others including me, it just doesn't seem to work,
    >>>>>>> and I've seen the same issues reported over and over with no
    >>>>>>> workable solutions.
    >>>>>>>
    >>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>> Thanks,
    >>>>>>>
    >>>>>>> Dave Cockram
    >>>>>>>
    >>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>>
    >>>
    >>
    >>
    >
  15. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
    missing. I don't know if that's because I'm now bootiing from the other
    drive.

    boot.ini from the Maxtor drive I'm now using - SATA 2

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    Edition" /fastdetect /NoExecute=OptOut


    PARTINFO 1.09
    Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

    Run date: 04/24/2005 16:06

    ====================================================================
    MBR Partition Information (HD0):
    +====+====+=============+====+=============+===========+===========+
    | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    +====+====+=============+====+=============+===========+===========+
    Volume Information
    +----+----+-------------+----+-------------+-----------+-----------+
    | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
    | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    MBR Partition Information (HD0) Continued:
    +====+====+=============+====+=============+===========+===========+
    | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    +====+====+=============+====+=============+===========+===========+
    BOOT SECTOR INFORMATION
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 63
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x04E1AF2A
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x04E1AF2
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0x22F802A6F8027875
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 81915435
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x0F065F8A
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x0F065F8
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0xD400C167C150E2
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 333991350
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x0F065F8A
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x0F065F8
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0xA478DD6678DD382E
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    ====================================================================
    MBR Partition Information (HD1):
    +====+====+=============+====+=============+===========+===========+
    | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    +====+====+=============+====+=============+===========+===========+
    BOOT SECTOR INFORMATION
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 63
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x024C1258
    MFT LCN: 0x0B42FF
    MFT Mirr LCN: 0x03D54EA
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0x4228D79E28D78EF3
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
    > Thanks Walter,
    >
    > I'll do it now, but in the meantime, I'm only up and running on my second
    > hard drive, the Maxtor. The Seagate which has the problem is inaccessable.
    > I don't know if that affects things. Let me know if it does.
    >
    > Dave
    >
    >
    > "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    > news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >>I assume you're up and running on the problematic platform? If so, go to
    >>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it and
    >>run partinfW (yes, that W not O) from a command prompt as follows:
    >>
    >> partinfw >partinfo.txt
    >> start notepad partinfo.txt
    >>
    >> Then copy and paste the contents back here. Also, do
    >> start->run->c:\boot.ini and copy and paste the contents of boot.ini back
    >> here as well.
    >>
    >>
    >> I think I know what your issue is now and it's going to revolve around
    >> boot.ini and the mbr code and now that I've taken a really fast look at
    >> Acronis, it may be the tool isn't the right tool for what you're
    >> attempting. Or you may be using it wrong.
    >>
    >> --
    >> Walter Clayton
    >> Any technology distinguishable from magic is insufficiently advanced.
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >>> Walter, HELP! ! !
    >>>
    >>> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >>> default
    >>> value).
    >>> Before restoring the clone onto the other drive I decided to just check
    >>> the
    >>> values in the key after rebooting and supposedly rebuilding.
    >>>
    >>> After entering my password at the log in screen, it immediately reverts
    >>> to
    >>> logging off . . .
    >>> I have tried everything I can think of, safe mode, boot disk but can't
    >>> log
    >>> on any more.
    >>>
    >>> I then tried restoring the saved cloned partition to the other drive and
    >>> got
    >>> NTLDR is missing. So now I don't have any bootable drives.Back to
    >>> Acronis
    >>> boot CD to restore an earlier clone that worked and restored. The first
    >>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >>> eventually used MaxBlast to repartition and then Acronis restore worked,
    >>> and
    >>> I'm now back to using an earlier saved clone that I've restored on the
    >>> Maxtor. I haven't touched the Seagate C: so if there's a way of
    >>> accessing
    >>> and putting back this registry key (which I stupidly didn't feel the
    >>> need to
    >>> save) maybe I can get back to normal.
    >>>
    >>> I swear once this is over, I won't touch any of this software for a
    >>> long,
    >>> long time. There are just too many issues and problems here. Restoring
    >>> all
    >>> my programs in an emergency pales to insignificance compared with the
    >>> time
    >>> and hassle spent so far.
    >>>
    >>> Thanks in anticipation,
    >>>
    >>> Dave
    >>>
    >>>
    >>> ----- Original Message -----
    >>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >>> Newsgroups:
    >>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >>> Sent: Sunday, April 24, 2005 1:28 AM
    >>> Subject: Re: error loading os
    >>>
    >>>
    >>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
    >>>> just the partition image itself can cause some less than desirable
    >>>> results. In fact if you check
    >>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore MS
    >>>> back up / restore tools don't restore that key.
    >>>>
    >>>> --
    >>>> Walter Clayton
    >>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>>> Presumably XP will just rebuild this from scratch again? Do you think
    >>>>> that is what stopped the clone booting when it almost got to the login
    >>>>> screen and then reverted to a plain blue screen with cursor?
    >>>>>
    >>>>> Dave
    >>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>>> Prior to the clone, delete all but the default value from
    >>>>>> HKLM\system\mounteddevices.
    >>>>>>
    >>>>>> --
    >>>>>> Walter Clayton
    >>>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>>
    >>>>>>
    >>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>>> clone copy in Acronis 8.0.
    >>>>>>>
    >>>>>>> I need to follow these steps EXACTLY.
    >>>>>>>
    >>>>>>> 1. Don't format or give a drive letter to the recipient drive
    >>>>>>> (Maxtor first partition here)
    >>>>>>> 2. Use Acronis from boot CD not XP
    >>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>>>>>> cable as original Seagate
    >>>>>>>
    >>>>>>> And this is the killer - if I don't do one of these and the cloning
    >>>>>>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>>>>>> Acronis. This overwrites my entire drive and it's not entirely
    >>>>>>> convenient to ship out 100GB of data to somewhere else. (Andrew
    >>>>>>> mentions earlier in the thread a method using recovery console which
    >>>>>>> I'll try if I need to in future.) And bizarrely this not only clones
    >>>>>>> the drive correctly, but it puts it back to normal such that I can
    >>>>>>> now successfully clone a partition.
    >>>>>>>
    >>>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>>> standard fixes for this type of problem not work - fixboot /fixmbr?
    >>>>>>>
    >>>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>>> 9.0?
    >>>>>>>
    >>>>>>> Dave
    >>>>>>>
    >>>>>>>
    >>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>> Hi,
    >>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple clone
    >>>>>>>> of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>>> reverted to a plain blue screen with cursor. I always remove
    >>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
    >>>>>>>> thing that did consistently work was Acronis Migrate Easy, but the
    >>>>>>>> problem is that you need to copy the entire disk. That means
    >>>>>>>> overwriting the other Maxtor partitions. But it proves that it did
    >>>>>>>> work. Now why did it, and not the others?
    >>>>>>>>
    >>>>>>>> Now whilst playing around with all this I noticed that I was
    >>>>>>>> getting 'error loading os' when trying to boot. When I went back to
    >>>>>>>> Acronis, that was also giving this message, and not even attempting
    >>>>>>>> to boot as it had previosly done. I tried using sysprep with the
    >>>>>>>> same result.
    >>>>>>>>
    >>>>>>>> Then I tried removing partitions completely from the Maxtor, using
    >>>>>>>> fdisk and dos to format, using Max Blast to format, using the
    >>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>>
    >>>>>>>> So I then thought I'd see if I could install XP on this drive. No,
    >>>>>>>> I get the same message when it gets to the booting from disk stage.
    >>>>>>>>
    >>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>>> software to use, as I've done this before.
    >>>>>>>>
    >>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>>> people it seems to be a completely painless process using Ghost or
    >>>>>>>> Acronis. For many others including me, it just doesn't seem to
    >>>>>>>> work, and I've seen the same issues reported over and over with no
    >>>>>>>> workable solutions.
    >>>>>>>>
    >>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>>> Thanks,
    >>>>>>>>
    >>>>>>>> Dave Cockram
    >>>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >
    >
  16. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    The partition structure is a bit weird. You have a logical with what appears
    to be a single volume followed by a couple of standard bootable primaries.
    In fact, the second partition is currently flagged as active.
    > MBR Partition Information (HD0):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    > MBR Partition Information (HD0) Continued:
    > +====+====+=============+====+=============+===========+===========+
    > | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    > | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |

    The boot strap code would have to be in the second partition. That includes
    boot.ini, ntldr, ntdetect.com. The arc statement for that partition will be
    tricky, that depends on from where you're loading the OS. If you're loading
    the OS from the same partition, using the current partition and volume
    tables, the arc statement should read

    > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

    although the partition number might need be three depending on how things
    are counted (and I get really fuzzy on how the boot strap code counts
    logical partitions and volumes; I avoid placing logicals in front of
    non-logical volumes like the plague).

    Exactly what are you attempting to accomplish? One thing that sticks out is
    to move the logical higher in the partition table and drop the bootable
    primary in front of that.

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426bb863$0$337$cc9e4d1f@news.dial.pipex.com...
    > The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
    > missing. I don't know if that's because I'm now bootiing from the other
    > drive.
    >
    > boot.ini from the Maxtor drive I'm now using - SATA 2
    >
    > [boot loader]
    > timeout=30
    > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    > [operating systems]
    > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    > Edition" /fastdetect /NoExecute=OptOut
    >
    >
    > PARTINFO 1.09
    > Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >
    > Run date: 04/24/2005 16:06
    >
    > ====================================================================
    > MBR Partition Information (HD0):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    > +====+====+=============+====+=============+===========+===========+
    > Volume Information
    > +----+----+-------------+----+-------------+-----------+-----------+
    > | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
    > | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > MBR Partition Information (HD0) Continued:
    > +====+====+=============+====+=============+===========+===========+
    > | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    > | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > +====+====+=============+====+=============+===========+===========+
    > BOOT SECTOR INFORMATION
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 63
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x04E1AF2A
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x04E1AF2
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x22F802A6F8027875
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 81915435
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x0F065F8A
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x0F065F8
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0xD400C167C150E2
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 333991350
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x0F065F8A
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x0F065F8
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0xA478DD6678DD382E
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > ====================================================================
    > MBR Partition Information (HD1):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    > | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > +====+====+=============+====+=============+===========+===========+
    > BOOT SECTOR INFORMATION
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 63
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x024C1258
    > MFT LCN: 0x0B42FF
    > MFT Mirr LCN: 0x03D54EA
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x4228D79E28D78EF3
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
    >> Thanks Walter,
    >>
    >> I'll do it now, but in the meantime, I'm only up and running on my second
    >> hard drive, the Maxtor. The Seagate which has the problem is
    >> inaccessable. I don't know if that affects things. Let me know if it
    >> does.
    >>
    >> Dave
    >>
    >>
    >> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >> news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >>>I assume you're up and running on the problematic platform? If so, go to
    >>>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
    >>>and run partinfW (yes, that W not O) from a command prompt as follows:
    >>>
    >>> partinfw >partinfo.txt
    >>> start notepad partinfo.txt
    >>>
    >>> Then copy and paste the contents back here. Also, do
    >>> start->run->c:\boot.ini and copy and paste the contents of boot.ini back
    >>> here as well.
    >>>
    >>>
    >>> I think I know what your issue is now and it's going to revolve around
    >>> boot.ini and the mbr code and now that I've taken a really fast look at
    >>> Acronis, it may be the tool isn't the right tool for what you're
    >>> attempting. Or you may be using it wrong.
    >>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >>>> Walter, HELP! ! !
    >>>>
    >>>> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >>>> default
    >>>> value).
    >>>> Before restoring the clone onto the other drive I decided to just check
    >>>> the
    >>>> values in the key after rebooting and supposedly rebuilding.
    >>>>
    >>>> After entering my password at the log in screen, it immediately reverts
    >>>> to
    >>>> logging off . . .
    >>>> I have tried everything I can think of, safe mode, boot disk but can't
    >>>> log
    >>>> on any more.
    >>>>
    >>>> I then tried restoring the saved cloned partition to the other drive
    >>>> and got
    >>>> NTLDR is missing. So now I don't have any bootable drives.Back to
    >>>> Acronis
    >>>> boot CD to restore an earlier clone that worked and restored. The first
    >>>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >>>> eventually used MaxBlast to repartition and then Acronis restore
    >>>> worked, and
    >>>> I'm now back to using an earlier saved clone that I've restored on the
    >>>> Maxtor. I haven't touched the Seagate C: so if there's a way of
    >>>> accessing
    >>>> and putting back this registry key (which I stupidly didn't feel the
    >>>> need to
    >>>> save) maybe I can get back to normal.
    >>>>
    >>>> I swear once this is over, I won't touch any of this software for a
    >>>> long,
    >>>> long time. There are just too many issues and problems here. Restoring
    >>>> all
    >>>> my programs in an emergency pales to insignificance compared with the
    >>>> time
    >>>> and hassle spent so far.
    >>>>
    >>>> Thanks in anticipation,
    >>>>
    >>>> Dave
    >>>>
    >>>>
    >>>> ----- Original Message -----
    >>>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >>>> Newsgroups:
    >>>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >>>> Sent: Sunday, April 24, 2005 1:28 AM
    >>>> Subject: Re: error loading os
    >>>>
    >>>>
    >>>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
    >>>>> just the partition image itself can cause some less than desirable
    >>>>> results. In fact if you check
    >>>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
    >>>>> MS back up / restore tools don't restore that key.
    >>>>>
    >>>>> --
    >>>>> Walter Clayton
    >>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>
    >>>>>
    >>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>>>> Presumably XP will just rebuild this from scratch again? Do you think
    >>>>>> that is what stopped the clone booting when it almost got to the
    >>>>>> login screen and then reverted to a plain blue screen with cursor?
    >>>>>>
    >>>>>> Dave
    >>>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>>>> Prior to the clone, delete all but the default value from
    >>>>>>> HKLM\system\mounteddevices.
    >>>>>>>
    >>>>>>> --
    >>>>>>> Walter Clayton
    >>>>>>> Any technology distinguishable from magic is insufficiently
    >>>>>>> advanced.
    >>>>>>>
    >>>>>>>
    >>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>>>> clone copy in Acronis 8.0.
    >>>>>>>>
    >>>>>>>> I need to follow these steps EXACTLY.
    >>>>>>>>
    >>>>>>>> 1. Don't format or give a drive letter to the recipient drive
    >>>>>>>> (Maxtor first partition here)
    >>>>>>>> 2. Use Acronis from boot CD not XP
    >>>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>>>>>>> cable as original Seagate
    >>>>>>>>
    >>>>>>>> And this is the killer - if I don't do one of these and the cloning
    >>>>>>>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>>>>>>> Acronis. This overwrites my entire drive and it's not entirely
    >>>>>>>> convenient to ship out 100GB of data to somewhere else. (Andrew
    >>>>>>>> mentions earlier in the thread a method using recovery console
    >>>>>>>> which I'll try if I need to in future.) And bizarrely this not only
    >>>>>>>> clones the drive correctly, but it puts it back to normal such that
    >>>>>>>> I can now successfully clone a partition.
    >>>>>>>>
    >>>>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>>>> standard fixes for this type of problem not work - fixboot /fixmbr?
    >>>>>>>>
    >>>>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>>>> 9.0?
    >>>>>>>>
    >>>>>>>> Dave
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>> Hi,
    >>>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple
    >>>>>>>>> clone of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>>>> reverted to a plain blue screen with cursor. I always remove
    >>>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
    >>>>>>>>> thing that did consistently work was Acronis Migrate Easy, but the
    >>>>>>>>> problem is that you need to copy the entire disk. That means
    >>>>>>>>> overwriting the other Maxtor partitions. But it proves that it did
    >>>>>>>>> work. Now why did it, and not the others?
    >>>>>>>>>
    >>>>>>>>> Now whilst playing around with all this I noticed that I was
    >>>>>>>>> getting 'error loading os' when trying to boot. When I went back
    >>>>>>>>> to Acronis, that was also giving this message, and not even
    >>>>>>>>> attempting to boot as it had previosly done. I tried using sysprep
    >>>>>>>>> with the same result.
    >>>>>>>>>
    >>>>>>>>> Then I tried removing partitions completely from the Maxtor, using
    >>>>>>>>> fdisk and dos to format, using Max Blast to format, using the
    >>>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>>>
    >>>>>>>>> So I then thought I'd see if I could install XP on this drive. No,
    >>>>>>>>> I get the same message when it gets to the booting from disk
    >>>>>>>>> stage.
    >>>>>>>>>
    >>>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>>>> software to use, as I've done this before.
    >>>>>>>>>
    >>>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>>>> people it seems to be a completely painless process using Ghost or
    >>>>>>>>> Acronis. For many others including me, it just doesn't seem to
    >>>>>>>>> work, and I've seen the same issues reported over and over with no
    >>>>>>>>> workable solutions.
    >>>>>>>>>
    >>>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>>>> Thanks,
    >>>>>>>>>
    >>>>>>>>> Dave Cockram
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>>
    >>>
    >>
    >>
    >
    >
  17. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    I also just noticed that my drive letter asignments are all screwed up.

    The Seagate (SATA 1) should be C,D,E with C being active. It is now F,D,E
    with D being active (OS is on F).
    The Maxtor (SATA 2) should be F, active. It is now C, active.

    Dave

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426bb863$0$337$cc9e4d1f@news.dial.pipex.com...
    > The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
    > missing. I don't know if that's because I'm now bootiing from the other
    > drive.
    >
    > boot.ini from the Maxtor drive I'm now using - SATA 2
    >
    > [boot loader]
    > timeout=30
    > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    > [operating systems]
    > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    > Edition" /fastdetect /NoExecute=OptOut
    >
    >
    > PARTINFO 1.09
    > Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >
    > Run date: 04/24/2005 16:06
    >
    > ====================================================================
    > MBR Partition Information (HD0):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    > +====+====+=============+====+=============+===========+===========+
    > Volume Information
    > +----+----+-------------+----+-------------+-----------+-----------+
    > | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
    > | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > MBR Partition Information (HD0) Continued:
    > +====+====+=============+====+=============+===========+===========+
    > | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    > | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > +====+====+=============+====+=============+===========+===========+
    > BOOT SECTOR INFORMATION
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 63
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x04E1AF2A
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x04E1AF2
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x22F802A6F8027875
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 81915435
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x0F065F8A
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x0F065F8
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0xD400C167C150E2
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 333991350
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x0F065F8A
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x0F065F8
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0xA478DD6678DD382E
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > ====================================================================
    > MBR Partition Information (HD1):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    > | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > +====+====+=============+====+=============+===========+===========+
    > BOOT SECTOR INFORMATION
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 63
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x024C1258
    > MFT LCN: 0x0B42FF
    > MFT Mirr LCN: 0x03D54EA
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x4228D79E28D78EF3
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
    >> Thanks Walter,
    >>
    >> I'll do it now, but in the meantime, I'm only up and running on my second
    >> hard drive, the Maxtor. The Seagate which has the problem is
    >> inaccessable. I don't know if that affects things. Let me know if it
    >> does.
    >>
    >> Dave
    >>
    >>
    >> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >> news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >>>I assume you're up and running on the problematic platform? If so, go to
    >>>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
    >>>and run partinfW (yes, that W not O) from a command prompt as follows:
    >>>
    >>> partinfw >partinfo.txt
    >>> start notepad partinfo.txt
    >>>
    >>> Then copy and paste the contents back here. Also, do
    >>> start->run->c:\boot.ini and copy and paste the contents of boot.ini back
    >>> here as well.
    >>>
    >>>
    >>> I think I know what your issue is now and it's going to revolve around
    >>> boot.ini and the mbr code and now that I've taken a really fast look at
    >>> Acronis, it may be the tool isn't the right tool for what you're
    >>> attempting. Or you may be using it wrong.
    >>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >>>> Walter, HELP! ! !
    >>>>
    >>>> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >>>> default
    >>>> value).
    >>>> Before restoring the clone onto the other drive I decided to just check
    >>>> the
    >>>> values in the key after rebooting and supposedly rebuilding.
    >>>>
    >>>> After entering my password at the log in screen, it immediately reverts
    >>>> to
    >>>> logging off . . .
    >>>> I have tried everything I can think of, safe mode, boot disk but can't
    >>>> log
    >>>> on any more.
    >>>>
    >>>> I then tried restoring the saved cloned partition to the other drive
    >>>> and got
    >>>> NTLDR is missing. So now I don't have any bootable drives.Back to
    >>>> Acronis
    >>>> boot CD to restore an earlier clone that worked and restored. The first
    >>>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >>>> eventually used MaxBlast to repartition and then Acronis restore
    >>>> worked, and
    >>>> I'm now back to using an earlier saved clone that I've restored on the
    >>>> Maxtor. I haven't touched the Seagate C: so if there's a way of
    >>>> accessing
    >>>> and putting back this registry key (which I stupidly didn't feel the
    >>>> need to
    >>>> save) maybe I can get back to normal.
    >>>>
    >>>> I swear once this is over, I won't touch any of this software for a
    >>>> long,
    >>>> long time. There are just too many issues and problems here. Restoring
    >>>> all
    >>>> my programs in an emergency pales to insignificance compared with the
    >>>> time
    >>>> and hassle spent so far.
    >>>>
    >>>> Thanks in anticipation,
    >>>>
    >>>> Dave
    >>>>
    >>>>
    >>>> ----- Original Message -----
    >>>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >>>> Newsgroups:
    >>>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >>>> Sent: Sunday, April 24, 2005 1:28 AM
    >>>> Subject: Re: error loading os
    >>>>
    >>>>
    >>>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
    >>>>> just the partition image itself can cause some less than desirable
    >>>>> results. In fact if you check
    >>>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
    >>>>> MS back up / restore tools don't restore that key.
    >>>>>
    >>>>> --
    >>>>> Walter Clayton
    >>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>
    >>>>>
    >>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>>>> Presumably XP will just rebuild this from scratch again? Do you think
    >>>>>> that is what stopped the clone booting when it almost got to the
    >>>>>> login screen and then reverted to a plain blue screen with cursor?
    >>>>>>
    >>>>>> Dave
    >>>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>>>> Prior to the clone, delete all but the default value from
    >>>>>>> HKLM\system\mounteddevices.
    >>>>>>>
    >>>>>>> --
    >>>>>>> Walter Clayton
    >>>>>>> Any technology distinguishable from magic is insufficiently
    >>>>>>> advanced.
    >>>>>>>
    >>>>>>>
    >>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>>>> clone copy in Acronis 8.0.
    >>>>>>>>
    >>>>>>>> I need to follow these steps EXACTLY.
    >>>>>>>>
    >>>>>>>> 1. Don't format or give a drive letter to the recipient drive
    >>>>>>>> (Maxtor first partition here)
    >>>>>>>> 2. Use Acronis from boot CD not XP
    >>>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on same
    >>>>>>>> cable as original Seagate
    >>>>>>>>
    >>>>>>>> And this is the killer - if I don't do one of these and the cloning
    >>>>>>>> process fails, than it will ALWAYS fail UNTIL I do a disk copy with
    >>>>>>>> Acronis. This overwrites my entire drive and it's not entirely
    >>>>>>>> convenient to ship out 100GB of data to somewhere else. (Andrew
    >>>>>>>> mentions earlier in the thread a method using recovery console
    >>>>>>>> which I'll try if I need to in future.) And bizarrely this not only
    >>>>>>>> clones the drive correctly, but it puts it back to normal such that
    >>>>>>>> I can now successfully clone a partition.
    >>>>>>>>
    >>>>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>>>> standard fixes for this type of problem not work - fixboot /fixmbr?
    >>>>>>>>
    >>>>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>>>> 9.0?
    >>>>>>>>
    >>>>>>>> Dave
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>> Hi,
    >>>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple
    >>>>>>>>> clone of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>>>> reverted to a plain blue screen with cursor. I always remove
    >>>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
    >>>>>>>>> thing that did consistently work was Acronis Migrate Easy, but the
    >>>>>>>>> problem is that you need to copy the entire disk. That means
    >>>>>>>>> overwriting the other Maxtor partitions. But it proves that it did
    >>>>>>>>> work. Now why did it, and not the others?
    >>>>>>>>>
    >>>>>>>>> Now whilst playing around with all this I noticed that I was
    >>>>>>>>> getting 'error loading os' when trying to boot. When I went back
    >>>>>>>>> to Acronis, that was also giving this message, and not even
    >>>>>>>>> attempting to boot as it had previosly done. I tried using sysprep
    >>>>>>>>> with the same result.
    >>>>>>>>>
    >>>>>>>>> Then I tried removing partitions completely from the Maxtor, using
    >>>>>>>>> fdisk and dos to format, using Max Blast to format, using the
    >>>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>>>
    >>>>>>>>> So I then thought I'd see if I could install XP on this drive. No,
    >>>>>>>>> I get the same message when it gets to the booting from disk
    >>>>>>>>> stage.
    >>>>>>>>>
    >>>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>>>> software to use, as I've done this before.
    >>>>>>>>>
    >>>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>>>> people it seems to be a completely painless process using Ghost or
    >>>>>>>>> Acronis. For many others including me, it just doesn't seem to
    >>>>>>>>> work, and I've seen the same issues reported over and over with no
    >>>>>>>>> workable solutions.
    >>>>>>>>>
    >>>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>>>> Thanks,
    >>>>>>>>>
    >>>>>>>>> Dave Cockram
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>>
    >>>
    >>
    >>
    >
    >
  18. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    First rule when dealing with multiple partitions is that drive lettering is
    fluid and meaningless. :-)

    See other post since it's time to figure out exactly where you think you are
    and where you're going.

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426be1d1$0$302$cc9e4d1f@news.dial.pipex.com...
    >I also just noticed that my drive letter asignments are all screwed up.
    >
    > The Seagate (SATA 1) should be C,D,E with C being active. It is now F,D,E
    > with D being active (OS is on F).
    > The Maxtor (SATA 2) should be F, active. It is now C, active.
    >
    > Dave
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426bb863$0$337$cc9e4d1f@news.dial.pipex.com...
    >> The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
    >> missing. I don't know if that's because I'm now bootiing from the other
    >> drive.
    >>
    >> boot.ini from the Maxtor drive I'm now using - SATA 2
    >>
    >> [boot loader]
    >> timeout=30
    >> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >> [operating systems]
    >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >> Edition" /fastdetect /NoExecute=OptOut
    >>
    >>
    >> PARTINFO 1.09
    >> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>
    >> Run date: 04/24/2005 16:06
    >>
    >> ====================================================================
    >> MBR Partition Information (HD0):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    >> +====+====+=============+====+=============+===========+===========+
    >> Volume Information
    >> +----+----+-------------+----+-------------+-----------+-----------+
    >> | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
    >> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> MBR Partition Information (HD0) Continued:
    >> +====+====+=============+====+=============+===========+===========+
    >> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    >> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x04E1AF2A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x04E1AF2
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x22F802A6F8027875
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 81915435
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0F065F8A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0F065F8
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xD400C167C150E2
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 333991350
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0F065F8A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0F065F8
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xA478DD6678DD382E
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> ====================================================================
    >> MBR Partition Information (HD1):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x024C1258
    >> MFT LCN: 0x0B42FF
    >> MFT Mirr LCN: 0x03D54EA
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x4228D79E28D78EF3
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
    >>> Thanks Walter,
    >>>
    >>> I'll do it now, but in the meantime, I'm only up and running on my
    >>> second hard drive, the Maxtor. The Seagate which has the problem is
    >>> inaccessable. I don't know if that affects things. Let me know if it
    >>> does.
    >>>
    >>> Dave
    >>>
    >>>
    >>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>> news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >>>>I assume you're up and running on the problematic platform? If so, go to
    >>>>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
    >>>>and run partinfW (yes, that W not O) from a command prompt as follows:
    >>>>
    >>>> partinfw >partinfo.txt
    >>>> start notepad partinfo.txt
    >>>>
    >>>> Then copy and paste the contents back here. Also, do
    >>>> start->run->c:\boot.ini and copy and paste the contents of boot.ini
    >>>> back here as well.
    >>>>
    >>>>
    >>>> I think I know what your issue is now and it's going to revolve around
    >>>> boot.ini and the mbr code and now that I've taken a really fast look at
    >>>> Acronis, it may be the tool isn't the right tool for what you're
    >>>> attempting. Or you may be using it wrong.
    >>>>
    >>>> --
    >>>> Walter Clayton
    >>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >>>>> Walter, HELP! ! !
    >>>>>
    >>>>> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >>>>> default
    >>>>> value).
    >>>>> Before restoring the clone onto the other drive I decided to just
    >>>>> check the
    >>>>> values in the key after rebooting and supposedly rebuilding.
    >>>>>
    >>>>> After entering my password at the log in screen, it immediately
    >>>>> reverts to
    >>>>> logging off . . .
    >>>>> I have tried everything I can think of, safe mode, boot disk but can't
    >>>>> log
    >>>>> on any more.
    >>>>>
    >>>>> I then tried restoring the saved cloned partition to the other drive
    >>>>> and got
    >>>>> NTLDR is missing. So now I don't have any bootable drives.Back to
    >>>>> Acronis
    >>>>> boot CD to restore an earlier clone that worked and restored. The
    >>>>> first
    >>>>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >>>>> eventually used MaxBlast to repartition and then Acronis restore
    >>>>> worked, and
    >>>>> I'm now back to using an earlier saved clone that I've restored on the
    >>>>> Maxtor. I haven't touched the Seagate C: so if there's a way of
    >>>>> accessing
    >>>>> and putting back this registry key (which I stupidly didn't feel the
    >>>>> need to
    >>>>> save) maybe I can get back to normal.
    >>>>>
    >>>>> I swear once this is over, I won't touch any of this software for a
    >>>>> long,
    >>>>> long time. There are just too many issues and problems here. Restoring
    >>>>> all
    >>>>> my programs in an emergency pales to insignificance compared with the
    >>>>> time
    >>>>> and hassle spent so far.
    >>>>>
    >>>>> Thanks in anticipation,
    >>>>>
    >>>>> Dave
    >>>>>
    >>>>>
    >>>>> ----- Original Message -----
    >>>>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >>>>> Newsgroups:
    >>>>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >>>>> Sent: Sunday, April 24, 2005 1:28 AM
    >>>>> Subject: Re: error loading os
    >>>>>
    >>>>>
    >>>>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
    >>>>>> just the partition image itself can cause some less than desirable
    >>>>>> results. In fact if you check
    >>>>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
    >>>>>> MS back up / restore tools don't restore that key.
    >>>>>>
    >>>>>> --
    >>>>>> Walter Clayton
    >>>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>>
    >>>>>>
    >>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>>>>> Presumably XP will just rebuild this from scratch again? Do you
    >>>>>>> think that is what stopped the clone booting when it almost got to
    >>>>>>> the login screen and then reverted to a plain blue screen with
    >>>>>>> cursor?
    >>>>>>>
    >>>>>>> Dave
    >>>>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>>>>> Prior to the clone, delete all but the default value from
    >>>>>>>> HKLM\system\mounteddevices.
    >>>>>>>>
    >>>>>>>> --
    >>>>>>>> Walter Clayton
    >>>>>>>> Any technology distinguishable from magic is insufficiently
    >>>>>>>> advanced.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>>>>> clone copy in Acronis 8.0.
    >>>>>>>>>
    >>>>>>>>> I need to follow these steps EXACTLY.
    >>>>>>>>>
    >>>>>>>>> 1. Don't format or give a drive letter to the recipient drive
    >>>>>>>>> (Maxtor first partition here)
    >>>>>>>>> 2. Use Acronis from boot CD not XP
    >>>>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on
    >>>>>>>>> same cable as original Seagate
    >>>>>>>>>
    >>>>>>>>> And this is the killer - if I don't do one of these and the
    >>>>>>>>> cloning process fails, than it will ALWAYS fail UNTIL I do a disk
    >>>>>>>>> copy with Acronis. This overwrites my entire drive and it's not
    >>>>>>>>> entirely convenient to ship out 100GB of data to somewhere else.
    >>>>>>>>> (Andrew mentions earlier in the thread a method using recovery
    >>>>>>>>> console which I'll try if I need to in future.) And bizarrely this
    >>>>>>>>> not only clones the drive correctly, but it puts it back to normal
    >>>>>>>>> such that I can now successfully clone a partition.
    >>>>>>>>>
    >>>>>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>>>>> standard fixes for this type of problem not work - fixboot
    >>>>>>>>> /fixmbr?
    >>>>>>>>>
    >>>>>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>>>>> 9.0?
    >>>>>>>>>
    >>>>>>>>> Dave
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>>> Hi,
    >>>>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple
    >>>>>>>>>> clone of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>>>>> reverted to a plain blue screen with cursor. I always remove
    >>>>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
    >>>>>>>>>> thing that did consistently work was Acronis Migrate Easy, but
    >>>>>>>>>> the problem is that you need to copy the entire disk. That means
    >>>>>>>>>> overwriting the other Maxtor partitions. But it proves that it
    >>>>>>>>>> did work. Now why did it, and not the others?
    >>>>>>>>>>
    >>>>>>>>>> Now whilst playing around with all this I noticed that I was
    >>>>>>>>>> getting 'error loading os' when trying to boot. When I went back
    >>>>>>>>>> to Acronis, that was also giving this message, and not even
    >>>>>>>>>> attempting to boot as it had previosly done. I tried using
    >>>>>>>>>> sysprep with the same result.
    >>>>>>>>>>
    >>>>>>>>>> Then I tried removing partitions completely from the Maxtor,
    >>>>>>>>>> using fdisk and dos to format, using Max Blast to format, using
    >>>>>>>>>> the
    >>>>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>>>>
    >>>>>>>>>> So I then thought I'd see if I could install XP on this drive.
    >>>>>>>>>> No, I get the same message when it gets to the booting from disk
    >>>>>>>>>> stage.
    >>>>>>>>>>
    >>>>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>>>>> software to use, as I've done this before.
    >>>>>>>>>>
    >>>>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>>>>> people it seems to be a completely painless process using Ghost
    >>>>>>>>>> or Acronis. For many others including me, it just doesn't seem to
    >>>>>>>>>> work, and I've seen the same issues reported over and over with
    >>>>>>>>>> no workable solutions.
    >>>>>>>>>>
    >>>>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>>>>> Thanks,
    >>>>>>>>>>
    >>>>>>>>>> Dave Cockram
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >>
    >
    >
  19. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter,

    Very simply, I'm just trying to undo the problems caused by deleting that
    key.

    Perhaps under most circumstances it can be deleted and it will rebuild, but
    this is not what has happened here.

    So I would like to get back to being able to boot from the first partition
    (where the OS is) on the Seagate. The second partition is marked active at
    the moment.

    As for the wider picture, I had sorted out a method of cloning that worked
    as long as I rigidly followed the steps I mentioned earlier. Otherwise I
    never managed to boot the clone. I assumed that deleting that key would
    answer that particular issue

    Thanks,

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uVL6CuPSFHA.3788@tk2msftngp13.phx.gbl...
    > The partition structure is a bit weird. You have a logical with what
    > appears to be a single volume followed by a couple of standard bootable
    > primaries. In fact, the second partition is currently flagged as active.
    >> MBR Partition Information (HD0):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    >> MBR Partition Information (HD0) Continued:
    >> +====+====+=============+====+=============+===========+===========+
    >> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    >> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >
    > The boot strap code would have to be in the second partition. That
    > includes boot.ini, ntldr, ntdetect.com. The arc statement for that
    > partition will be tricky, that depends on from where you're loading the
    > OS. If you're loading the OS from the same partition, using the current
    > partition and volume tables, the arc statement should read
    >
    >> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    >
    > although the partition number might need be three depending on how things
    > are counted (and I get really fuzzy on how the boot strap code counts
    > logical partitions and volumes; I avoid placing logicals in front of
    > non-logical volumes like the plague).
    >
    > Exactly what are you attempting to accomplish? One thing that sticks out
    > is to move the logical higher in the partition table and drop the bootable
    > primary in front of that.
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426bb863$0$337$cc9e4d1f@news.dial.pipex.com...
    >> The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
    >> missing. I don't know if that's because I'm now bootiing from the other
    >> drive.
    >>
    >> boot.ini from the Maxtor drive I'm now using - SATA 2
    >>
    >> [boot loader]
    >> timeout=30
    >> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >> [operating systems]
    >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >> Edition" /fastdetect /NoExecute=OptOut
    >>
    >>
    >> PARTINFO 1.09
    >> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>
    >> Run date: 04/24/2005 16:06
    >>
    >> ====================================================================
    >> MBR Partition Information (HD0):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    >> +====+====+=============+====+=============+===========+===========+
    >> Volume Information
    >> +----+----+-------------+----+-------------+-----------+-----------+
    >> | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
    >> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> MBR Partition Information (HD0) Continued:
    >> +====+====+=============+====+=============+===========+===========+
    >> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    >> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x04E1AF2A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x04E1AF2
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x22F802A6F8027875
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 81915435
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0F065F8A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0F065F8
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xD400C167C150E2
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 333991350
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0F065F8A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0F065F8
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xA478DD6678DD382E
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> ====================================================================
    >> MBR Partition Information (HD1):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x024C1258
    >> MFT LCN: 0x0B42FF
    >> MFT Mirr LCN: 0x03D54EA
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x4228D79E28D78EF3
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
    >>> Thanks Walter,
    >>>
    >>> I'll do it now, but in the meantime, I'm only up and running on my
    >>> second hard drive, the Maxtor. The Seagate which has the problem is
    >>> inaccessable. I don't know if that affects things. Let me know if it
    >>> does.
    >>>
    >>> Dave
    >>>
    >>>
    >>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>> news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >>>>I assume you're up and running on the problematic platform? If so, go to
    >>>>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
    >>>>and run partinfW (yes, that W not O) from a command prompt as follows:
    >>>>
    >>>> partinfw >partinfo.txt
    >>>> start notepad partinfo.txt
    >>>>
    >>>> Then copy and paste the contents back here. Also, do
    >>>> start->run->c:\boot.ini and copy and paste the contents of boot.ini
    >>>> back here as well.
    >>>>
    >>>>
    >>>> I think I know what your issue is now and it's going to revolve around
    >>>> boot.ini and the mbr code and now that I've taken a really fast look at
    >>>> Acronis, it may be the tool isn't the right tool for what you're
    >>>> attempting. Or you may be using it wrong.
    >>>>
    >>>> --
    >>>> Walter Clayton
    >>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >>>>> Walter, HELP! ! !
    >>>>>
    >>>>> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >>>>> default
    >>>>> value).
    >>>>> Before restoring the clone onto the other drive I decided to just
    >>>>> check the
    >>>>> values in the key after rebooting and supposedly rebuilding.
    >>>>>
    >>>>> After entering my password at the log in screen, it immediately
    >>>>> reverts to
    >>>>> logging off . . .
    >>>>> I have tried everything I can think of, safe mode, boot disk but can't
    >>>>> log
    >>>>> on any more.
    >>>>>
    >>>>> I then tried restoring the saved cloned partition to the other drive
    >>>>> and got
    >>>>> NTLDR is missing. So now I don't have any bootable drives.Back to
    >>>>> Acronis
    >>>>> boot CD to restore an earlier clone that worked and restored. The
    >>>>> first
    >>>>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >>>>> eventually used MaxBlast to repartition and then Acronis restore
    >>>>> worked, and
    >>>>> I'm now back to using an earlier saved clone that I've restored on the
    >>>>> Maxtor. I haven't touched the Seagate C: so if there's a way of
    >>>>> accessing
    >>>>> and putting back this registry key (which I stupidly didn't feel the
    >>>>> need to
    >>>>> save) maybe I can get back to normal.
    >>>>>
    >>>>> I swear once this is over, I won't touch any of this software for a
    >>>>> long,
    >>>>> long time. There are just too many issues and problems here. Restoring
    >>>>> all
    >>>>> my programs in an emergency pales to insignificance compared with the
    >>>>> time
    >>>>> and hassle spent so far.
    >>>>>
    >>>>> Thanks in anticipation,
    >>>>>
    >>>>> Dave
    >>>>>
    >>>>>
    >>>>> ----- Original Message -----
    >>>>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >>>>> Newsgroups:
    >>>>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >>>>> Sent: Sunday, April 24, 2005 1:28 AM
    >>>>> Subject: Re: error loading os
    >>>>>
    >>>>>
    >>>>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
    >>>>>> just the partition image itself can cause some less than desirable
    >>>>>> results. In fact if you check
    >>>>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
    >>>>>> MS back up / restore tools don't restore that key.
    >>>>>>
    >>>>>> --
    >>>>>> Walter Clayton
    >>>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>>
    >>>>>>
    >>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>>>>> Presumably XP will just rebuild this from scratch again? Do you
    >>>>>>> think that is what stopped the clone booting when it almost got to
    >>>>>>> the login screen and then reverted to a plain blue screen with
    >>>>>>> cursor?
    >>>>>>>
    >>>>>>> Dave
    >>>>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>>>>> Prior to the clone, delete all but the default value from
    >>>>>>>> HKLM\system\mounteddevices.
    >>>>>>>>
    >>>>>>>> --
    >>>>>>>> Walter Clayton
    >>>>>>>> Any technology distinguishable from magic is insufficiently
    >>>>>>>> advanced.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>>>>> clone copy in Acronis 8.0.
    >>>>>>>>>
    >>>>>>>>> I need to follow these steps EXACTLY.
    >>>>>>>>>
    >>>>>>>>> 1. Don't format or give a drive letter to the recipient drive
    >>>>>>>>> (Maxtor first partition here)
    >>>>>>>>> 2. Use Acronis from boot CD not XP
    >>>>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on
    >>>>>>>>> same cable as original Seagate
    >>>>>>>>>
    >>>>>>>>> And this is the killer - if I don't do one of these and the
    >>>>>>>>> cloning process fails, than it will ALWAYS fail UNTIL I do a disk
    >>>>>>>>> copy with Acronis. This overwrites my entire drive and it's not
    >>>>>>>>> entirely convenient to ship out 100GB of data to somewhere else.
    >>>>>>>>> (Andrew mentions earlier in the thread a method using recovery
    >>>>>>>>> console which I'll try if I need to in future.) And bizarrely this
    >>>>>>>>> not only clones the drive correctly, but it puts it back to normal
    >>>>>>>>> such that I can now successfully clone a partition.
    >>>>>>>>>
    >>>>>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>>>>> standard fixes for this type of problem not work - fixboot
    >>>>>>>>> /fixmbr?
    >>>>>>>>>
    >>>>>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>>>>> 9.0?
    >>>>>>>>>
    >>>>>>>>> Dave
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>>> Hi,
    >>>>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple
    >>>>>>>>>> clone of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>>>>> reverted to a plain blue screen with cursor. I always remove
    >>>>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
    >>>>>>>>>> thing that did consistently work was Acronis Migrate Easy, but
    >>>>>>>>>> the problem is that you need to copy the entire disk. That means
    >>>>>>>>>> overwriting the other Maxtor partitions. But it proves that it
    >>>>>>>>>> did work. Now why did it, and not the others?
    >>>>>>>>>>
    >>>>>>>>>> Now whilst playing around with all this I noticed that I was
    >>>>>>>>>> getting 'error loading os' when trying to boot. When I went back
    >>>>>>>>>> to Acronis, that was also giving this message, and not even
    >>>>>>>>>> attempting to boot as it had previosly done. I tried using
    >>>>>>>>>> sysprep with the same result.
    >>>>>>>>>>
    >>>>>>>>>> Then I tried removing partitions completely from the Maxtor,
    >>>>>>>>>> using fdisk and dos to format, using Max Blast to format, using
    >>>>>>>>>> the
    >>>>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>>>>
    >>>>>>>>>> So I then thought I'd see if I could install XP on this drive.
    >>>>>>>>>> No, I get the same message when it gets to the booting from disk
    >>>>>>>>>> stage.
    >>>>>>>>>>
    >>>>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>>>>> software to use, as I've done this before.
    >>>>>>>>>>
    >>>>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>>>>> people it seems to be a completely painless process using Ghost
    >>>>>>>>>> or Acronis. For many others including me, it just doesn't seem to
    >>>>>>>>>> work, and I've seen the same issues reported over and over with
    >>>>>>>>>> no workable solutions.
    >>>>>>>>>>
    >>>>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>>>>> Thanks,
    >>>>>>>>>>
    >>>>>>>>>> Dave Cockram
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >>
    >
  20. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426beea2$0$340$cc9e4d1f@news.dial.pipex.com...
    > Walter,
    >
    > Very simply, I'm just trying to undo the problems caused by deleting that
    > key.
    >
    > Perhaps under most circumstances it can be deleted and it will rebuild,
    > but this is not what has happened here.

    There are exceptions. I have such my self since I don't enumerate partitions
    in default order, however this is, I'll have to admit, the first time I've
    seen some one park a logical volume in front the boot partition. There are
    some other reasons why this is going to be problematic on going other than
    you're inability to do a simple partition clone of the system...

    >
    > So I would like to get back to being able to boot from the first partition
    > (where the OS is) on the Seagate. The second partition is marked active at
    > the moment.

    OK. It's time to be *extremely* specific.
    The first partition on your Segate is a logical volume. No BIOS can initiate
    boot strap on that partition. The second partition in the partition table is
    the active primary. That is the partition the BIOS will bootstrap. That is
    the partition that must contain boot.init, ntldr and ntdetect.com. In turn
    boot.ini must point to the partition from which the OS will loaded.
    Depending on exactly how you got into the partition table layout you have,
    specifically the timing therein, things may get a bit interesting since the
    mounteddevices key has been clipped. The key is what was the OS partition
    enumerated as when you set it up. Once boot.ini is straightened out, you may
    have to use "last known good configuration' to get the mounteddevices values
    back. As an aside, if you alter the physical layout of the Seagate now, you
    could save your self a lot of grief and would not have to worry about the
    old mounteddevices key.

    One 'long' term issue I *think* you're going to have, is if you drop another
    volume into the logical partition, it's going to hose the arc statement.

    >
    > As for the wider picture, I had sorted out a method of cloning that worked
    > as long as I rigidly followed the steps I mentioned earlier. Otherwise I
    > never managed to boot the clone. I assumed that deleting that key would
    > answer that particular issue

    I can get you back to where you want to go at present, but due to the
    partition layout you have on the Seagate you're going to continue to have
    some extreme difficulty in partition cloning of the OS instance. I can
    understand exactly why you're having to jump through the hoops you are
    though.

    Pulling in the other post:
    > Yes, those files are now all on the second (Non OS) partition.
    >
    > boot.ini
    >
    > [boot loader]
    > timeout=1
    > default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
    > [operating systems]
    > multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Home
    > Edition" /fastdetect /NoExecute=OptIn
    >
    > Can I perhaps copy them across and try rebooting? If so, exactly which
    > files?

    Yes, but I'd go a bit further since you're in hunt and peck mode at the
    moment.
    Modify the boot.ini as follows and note the change on the time out value.
    You need the time to be able to select a different arc path.

    [boot loader]
    timeout=5
    default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    Edition 1" /fastdetect /NoExecute=OptIn
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home
    Edition 2" /fastdetect /NoExecute=OptIn
    multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Home
    Edition 3" /fastdetect /NoExecute=OptIn
    multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="Microsoft Windows XP Home
    Edition 4" /fastdetect /NoExecute=OptIn

    In this way you can attempt to load each of the partitions. Also, bring the
    image up in safe mode initially. Do not bring the machine up in normal mode
    directly. Once up in safemode, use diskmgmt.msc to correct any drive letter
    assignment problems you may have.

    The other two files you need are ntldr and ntdetect.com.

    Once you get where you want, you can delete the extraneous [operating
    systems] statements from boot.ini.
  21. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Yes, those files are now all on the second (Non OS) partition.

    boot.ini

    [boot loader]
    timeout=1
    default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Home
    Edition" /fastdetect /NoExecute=OptIn

    Can I perhaps copy them across and try rebooting? If so, exactly which
    files?

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uVL6CuPSFHA.3788@tk2msftngp13.phx.gbl...
    > The partition structure is a bit weird. You have a logical with what
    > appears to be a single volume followed by a couple of standard bootable
    > primaries. In fact, the second partition is currently flagged as active.
    >> MBR Partition Information (HD0):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    >> MBR Partition Information (HD0) Continued:
    >> +====+====+=============+====+=============+===========+===========+
    >> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    >> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >
    > The boot strap code would have to be in the second partition. That
    > includes boot.ini, ntldr, ntdetect.com. The arc statement for that
    > partition will be tricky, that depends on from where you're loading the
    > OS. If you're loading the OS from the same partition, using the current
    > partition and volume tables, the arc statement should read
    >
    >> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    >
    > although the partition number might need be three depending on how things
    > are counted (and I get really fuzzy on how the boot strap code counts
    > logical partitions and volumes; I avoid placing logicals in front of
    > non-logical volumes like the plague).
    >
    > Exactly what are you attempting to accomplish? One thing that sticks out
    > is to move the logical higher in the partition table and drop the bootable
    > primary in front of that.
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426bb863$0$337$cc9e4d1f@news.dial.pipex.com...
    >> The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
    >> missing. I don't know if that's because I'm now bootiing from the other
    >> drive.
    >>
    >> boot.ini from the Maxtor drive I'm now using - SATA 2
    >>
    >> [boot loader]
    >> timeout=30
    >> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >> [operating systems]
    >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >> Edition" /fastdetect /NoExecute=OptOut
    >>
    >>
    >> PARTINFO 1.09
    >> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>
    >> Run date: 04/24/2005 16:06
    >>
    >> ====================================================================
    >> MBR Partition Information (HD0):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
    >> +====+====+=============+====+=============+===========+===========+
    >> Volume Information
    >> +----+----+-------------+----+-------------+-----------+-----------+
    >> | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
    >> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> MBR Partition Information (HD0) Continued:
    >> +====+====+=============+====+=============+===========+===========+
    >> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
    >> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x04E1AF2A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x04E1AF2
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x22F802A6F8027875
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 81915435
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0F065F8A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0F065F8
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xD400C167C150E2
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 333991350
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0F065F8A
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0F065F8
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xA478DD6678DD382E
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> ====================================================================
    >> MBR Partition Information (HD1):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x024C1258
    >> MFT LCN: 0x0B42FF
    >> MFT Mirr LCN: 0x03D54EA
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x4228D79E28D78EF3
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
    >>> Thanks Walter,
    >>>
    >>> I'll do it now, but in the meantime, I'm only up and running on my
    >>> second hard drive, the Maxtor. The Seagate which has the problem is
    >>> inaccessable. I don't know if that affects things. Let me know if it
    >>> does.
    >>>
    >>> Dave
    >>>
    >>>
    >>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>> news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
    >>>>I assume you're up and running on the problematic platform? If so, go to
    >>>>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
    >>>>and run partinfW (yes, that W not O) from a command prompt as follows:
    >>>>
    >>>> partinfw >partinfo.txt
    >>>> start notepad partinfo.txt
    >>>>
    >>>> Then copy and paste the contents back here. Also, do
    >>>> start->run->c:\boot.ini and copy and paste the contents of boot.ini
    >>>> back here as well.
    >>>>
    >>>>
    >>>> I think I know what your issue is now and it's going to revolve around
    >>>> boot.ini and the mbr code and now that I've taken a really fast look at
    >>>> Acronis, it may be the tool isn't the right tool for what you're
    >>>> attempting. Or you may be using it wrong.
    >>>>
    >>>> --
    >>>> Walter Clayton
    >>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
    >>>>> Walter, HELP! ! !
    >>>>>
    >>>>> I deleted that key as suggested, HKLM\system\mounteddevices (except
    >>>>> default
    >>>>> value).
    >>>>> Before restoring the clone onto the other drive I decided to just
    >>>>> check the
    >>>>> values in the key after rebooting and supposedly rebuilding.
    >>>>>
    >>>>> After entering my password at the log in screen, it immediately
    >>>>> reverts to
    >>>>> logging off . . .
    >>>>> I have tried everything I can think of, safe mode, boot disk but can't
    >>>>> log
    >>>>> on any more.
    >>>>>
    >>>>> I then tried restoring the saved cloned partition to the other drive
    >>>>> and got
    >>>>> NTLDR is missing. So now I don't have any bootable drives.Back to
    >>>>> Acronis
    >>>>> boot CD to restore an earlier clone that worked and restored. The
    >>>>> first
    >>>>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
    >>>>> eventually used MaxBlast to repartition and then Acronis restore
    >>>>> worked, and
    >>>>> I'm now back to using an earlier saved clone that I've restored on the
    >>>>> Maxtor. I haven't touched the Seagate C: so if there's a way of
    >>>>> accessing
    >>>>> and putting back this registry key (which I stupidly didn't feel the
    >>>>> need to
    >>>>> save) maybe I can get back to normal.
    >>>>>
    >>>>> I swear once this is over, I won't touch any of this software for a
    >>>>> long,
    >>>>> long time. There are just too many issues and problems here. Restoring
    >>>>> all
    >>>>> my programs in an emergency pales to insignificance compared with the
    >>>>> time
    >>>>> and hassle spent so far.
    >>>>>
    >>>>> Thanks in anticipation,
    >>>>>
    >>>>> Dave
    >>>>>
    >>>>>
    >>>>> ----- Original Message -----
    >>>>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
    >>>>> Newsgroups:
    >>>>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
    >>>>> Sent: Sunday, April 24, 2005 1:28 AM
    >>>>> Subject: Re: error loading os
    >>>>>
    >>>>>
    >>>>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
    >>>>>> just the partition image itself can cause some less than desirable
    >>>>>> results. In fact if you check
    >>>>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
    >>>>>> MS back up / restore tools don't restore that key.
    >>>>>>
    >>>>>> --
    >>>>>> Walter Clayton
    >>>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>>
    >>>>>>
    >>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
    >>>>>>> Presumably XP will just rebuild this from scratch again? Do you
    >>>>>>> think that is what stopped the clone booting when it almost got to
    >>>>>>> the login screen and then reverted to a plain blue screen with
    >>>>>>> cursor?
    >>>>>>>
    >>>>>>> Dave
    >>>>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
    >>>>>>>> Prior to the clone, delete all but the default value from
    >>>>>>>> HKLM\system\mounteddevices.
    >>>>>>>>
    >>>>>>>> --
    >>>>>>>> Walter Clayton
    >>>>>>>> Any technology distinguishable from magic is insufficiently
    >>>>>>>> advanced.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>> OK, we're making some progress here. I can now make and restore a
    >>>>>>>>> clone copy in Acronis 8.0.
    >>>>>>>>>
    >>>>>>>>> I need to follow these steps EXACTLY.
    >>>>>>>>>
    >>>>>>>>> 1. Don't format or give a drive letter to the recipient drive
    >>>>>>>>> (Maxtor first partition here)
    >>>>>>>>> 2. Use Acronis from boot CD not XP
    >>>>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on
    >>>>>>>>> same cable as original Seagate
    >>>>>>>>>
    >>>>>>>>> And this is the killer - if I don't do one of these and the
    >>>>>>>>> cloning process fails, than it will ALWAYS fail UNTIL I do a disk
    >>>>>>>>> copy with Acronis. This overwrites my entire drive and it's not
    >>>>>>>>> entirely convenient to ship out 100GB of data to somewhere else.
    >>>>>>>>> (Andrew mentions earlier in the thread a method using recovery
    >>>>>>>>> console which I'll try if I need to in future.) And bizarrely this
    >>>>>>>>> not only clones the drive correctly, but it puts it back to normal
    >>>>>>>>> such that I can now successfully clone a partition.
    >>>>>>>>>
    >>>>>>>>> So, what on earth is going on here? Why did the boot sector get
    >>>>>>>>> screwed up ( I assume that's what it was) and why did none of the
    >>>>>>>>> standard fixes for this type of problem not work - fixboot
    >>>>>>>>> /fixmbr?
    >>>>>>>>>
    >>>>>>>>> I gather at least some of this is caused by me using SATA drives.
    >>>>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
    >>>>>>>>> 9.0?
    >>>>>>>>>
    >>>>>>>>> Dave
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
    >>>>>>>>>> Hi,
    >>>>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple
    >>>>>>>>>> clone of my Seagate C: partiton to a Maxtor F: partition.
    >>>>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
    >>>>>>>>>> software. In most cases I got as far as a login screen and it
    >>>>>>>>>> reverted to a plain blue screen with cursor. I always remove
    >>>>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
    >>>>>>>>>> thing that did consistently work was Acronis Migrate Easy, but
    >>>>>>>>>> the problem is that you need to copy the entire disk. That means
    >>>>>>>>>> overwriting the other Maxtor partitions. But it proves that it
    >>>>>>>>>> did work. Now why did it, and not the others?
    >>>>>>>>>>
    >>>>>>>>>> Now whilst playing around with all this I noticed that I was
    >>>>>>>>>> getting 'error loading os' when trying to boot. When I went back
    >>>>>>>>>> to Acronis, that was also giving this message, and not even
    >>>>>>>>>> attempting to boot as it had previosly done. I tried using
    >>>>>>>>>> sysprep with the same result.
    >>>>>>>>>>
    >>>>>>>>>> Then I tried removing partitions completely from the Maxtor,
    >>>>>>>>>> using fdisk and dos to format, using Max Blast to format, using
    >>>>>>>>>> the
    >>>>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
    >>>>>>>>>>
    >>>>>>>>>> So I then thought I'd see if I could install XP on this drive.
    >>>>>>>>>> No, I get the same message when it gets to the booting from disk
    >>>>>>>>>> stage.
    >>>>>>>>>>
    >>>>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
    >>>>>>>>>> need to do a low level format to get this drive back to normal
    >>>>>>>>>> shipping condition. If so, could someone tell me how, and what
    >>>>>>>>>> software to use, as I've done this before.
    >>>>>>>>>>
    >>>>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
    >>>>>>>>>> people it seems to be a completely painless process using Ghost
    >>>>>>>>>> or Acronis. For many others including me, it just doesn't seem to
    >>>>>>>>>> work, and I've seen the same issues reported over and over with
    >>>>>>>>>> no workable solutions.
    >>>>>>>>>>
    >>>>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
    >>>>>>>>>> Thanks,
    >>>>>>>>>>
    >>>>>>>>>> Dave Cockram
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >>
    >
  22. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter,
    I had a play around with all this, but gave up in the end, and reinstalled
    XP.

    Could you have a look at this and tell me if it now seems 'normal'.

    At this stage I would like to take regular backup images, (ideally using
    Acronis, as I have that), and restore them to the Maxtor (HD1) for checking.
    Can you forsee any problems now?

    Finally, I believe it would be relatively easy to restore images to any of
    the other partitions on say the Maxtor (there are three). Do I need to
    modify boot.ini in order to access them. My BIOS has a boot loader if I
    press F8 so would they then appear on it's menu?

    Thanks,

    Dave

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    Edition" /fastdetect /NoExecute=OptIn


    PARTINFO 1.09
    Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

    Run date: 04/26/2005 0:36

    ====================================================================
    MBR Partition Information (HD0):
    +====+====+=============+====+=============+===========+===========+
    | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    +====+====+=============+====+=============+===========+===========+
    BOOT SECTOR INFORMATION
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 63
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x03A962B0
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x03A962B
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0x844C0F974C0F8362
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID: 0x2
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 61432560
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x0FA285C7
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x0FA285C
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0xF2281E1A281DDF03
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID: 0x3
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 323741880
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x0FA2C488
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x0FA2C48
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0x7AB4DECCB4DE89D1
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    ====================================================================
    MBR Partition Information (HD1):
    +====+====+=============+====+=============+===========+===========+
    | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    +====+====+=============+====+=============+===========+===========+
    BOOT SECTOR INFORMATION
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 63
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x024C1258
    MFT LCN: 0x0B42FF
    MFT Mirr LCN: 0x03D54EA
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0x4228D79E28D78EF3
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
    File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID: 0x2
    Jump: EB 52 90
    OEM Name: NTFS
    Bytes Per Sec: 512
    Sec Per Clust: 8
    Res Sectors: 0
    Zero 1: 0x0
    Zero 2: 0x0
    NA 1: 0x0
    Media: 0xF8
    Zero 3: 0x0
    Sec Per Track: 63
    Heads: 255
    Hidden Secs: 38539935
    NA 2: 0x0
    NA 3: 0x800080
    Total Sectors: 0x010557821
    MFT LCN: 0x0C0000
    MFT Mirr LCN: 0x01055782
    Clust Per FRS: 0xF6
    Clust Per IBlock: 0x1
    Volume SN: 0x7E38F7BF38F7750D
    Checksum: 0x0
    Boot Flag: 0xAA55
    -------------------------------------------------------------------------------
  23. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    This structure looks better as long as you don't introduce a logical volume
    in the mix at some point in time, based on what you're intending. If you do,
    you're going to have some issues with partition enumeration.

    I'm looking at the Acronis web site and what I don't see right off hand is a
    boot manager as part of your package. It appears that with a different
    package, you can get a boot manager, but I don't have any hands on with it.
    I can't tell if it's capable of doing what needs be done in order to
    actually fire up an OS image from a different BIOS enumerated device. It
    sort of implies that it can, but I since they make a rather outrageous claim
    regarding performance, I can't trust what I'm reading. Regardless, one of
    the issues is going to revolve around the mounteddevices key and the
    secondary issue is with how devices and partitions are enumerated during
    system startup. I don't see a practical way, with the tools you have, to
    validate a partition image outside of restoring it in-situ. Even if you clip
    the mounteddevices key in advance of snapping an image, and configure the
    BIOS to bootstrap HD1 instead of HD0 you're going to get hosed when
    partitions are reenumerated. And if you don't clip the key, you're going to
    get hosed when the system attempts to mount the first partition on HD0 as
    the system image.

    You're either going to have to trust the product or not. If not, then use
    what I use which is a little bit cheaper and that's BootItNG.

    BTW: I do have to disagree with a site that claims, right on their main
    page:

    "Partitioning The Hard Disk Increases Performance ..".

    when it does exactly the opposite. It's sort of an instant turn off for me
    especially when I dig into the details of the article and see the other
    mistakes. Then again, when talking about marketing hype...

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426d8191$0$375$cc9e4d1f@news.dial.pipex.com...
    > Walter,
    > I had a play around with all this, but gave up in the end, and reinstalled
    > XP.
    >
    > Could you have a look at this and tell me if it now seems 'normal'.
    >
    > At this stage I would like to take regular backup images, (ideally using
    > Acronis, as I have that), and restore them to the Maxtor (HD1) for
    > checking. Can you forsee any problems now?
    >
    > Finally, I believe it would be relatively easy to restore images to any of
    > the other partitions on say the Maxtor (there are three). Do I need to
    > modify boot.ini in order to access them. My BIOS has a boot loader if I
    > press F8 so would they then appear on it's menu?
    >
    > Thanks,
    >
    > Dave
    >
    > [boot loader]
    > timeout=30
    > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    > [operating systems]
    > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    > Edition" /fastdetect /NoExecute=OptIn
    >
    >
    > PARTINFO 1.09
    > Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >
    > Run date: 04/26/2005 0:36
    >
    > ====================================================================
    > MBR Partition Information (HD0):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    > | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    > | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > +====+====+=============+====+=============+===========+===========+
    > BOOT SECTOR INFORMATION
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 63
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x03A962B0
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x03A962B
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x844C0F974C0F8362
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID: 0x2
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 61432560
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x0FA285C7
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x0FA285C
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0xF2281E1A281DDF03
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID: 0x3
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 323741880
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x0FA2C488
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x0FA2C48
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x7AB4DECCB4DE89D1
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > ====================================================================
    > MBR Partition Information (HD1):
    > +====+====+=============+====+=============+===========+===========+
    > | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    > | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    > | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    > +====+====+=============+====+=============+===========+===========+
    > BOOT SECTOR INFORMATION
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 63
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x024C1258
    > MFT LCN: 0x0B42FF
    > MFT Mirr LCN: 0x03D54EA
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x4228D79E28D78EF3
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    > File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID: 0x2
    > Jump: EB 52 90
    > OEM Name: NTFS
    > Bytes Per Sec: 512
    > Sec Per Clust: 8
    > Res Sectors: 0
    > Zero 1: 0x0
    > Zero 2: 0x0
    > NA 1: 0x0
    > Media: 0xF8
    > Zero 3: 0x0
    > Sec Per Track: 63
    > Heads: 255
    > Hidden Secs: 38539935
    > NA 2: 0x0
    > NA 3: 0x800080
    > Total Sectors: 0x010557821
    > MFT LCN: 0x0C0000
    > MFT Mirr LCN: 0x01055782
    > Clust Per FRS: 0xF6
    > Clust Per IBlock: 0x1
    > Volume SN: 0x7E38F7BF38F7750D
    > Checksum: 0x0
    > Boot Flag: 0xAA55
    > -------------------------------------------------------------------------------
    >
    >
    >
  24. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    OK, thanks for all that advice Walter. I used a trial version of BootItNG
    some years ago, so I'll check it out again.

    One final thing. Presumably it's ok to restore a cloned HD0 partition
    to HD1. Then to remove HD0 and replace it with HD1 and reboot. That isn't
    going to
    affect anything when I revert back to normal is it?

    Dave

    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uUI0Q3fSFHA.3076@tk2msftngp13.phx.gbl...
    > This structure looks better as long as you don't introduce a logical
    > volume in the mix at some point in time, based on what you're intending.
    > If you do, you're going to have some issues with partition enumeration.
    >
    > I'm looking at the Acronis web site and what I don't see right off hand is
    > a boot manager as part of your package. It appears that with a different
    > package, you can get a boot manager, but I don't have any hands on with
    > it. I can't tell if it's capable of doing what needs be done in order to
    > actually fire up an OS image from a different BIOS enumerated device. It
    > sort of implies that it can, but I since they make a rather outrageous
    > claim regarding performance, I can't trust what I'm reading. Regardless,
    > one of the issues is going to revolve around the mounteddevices key and
    > the secondary issue is with how devices and partitions are enumerated
    > during system startup. I don't see a practical way, with the tools you
    > have, to validate a partition image outside of restoring it in-situ. Even
    > if you clip the mounteddevices key in advance of snapping an image, and
    > configure the BIOS to bootstrap HD1 instead of HD0 you're going to get
    > hosed when partitions are reenumerated. And if you don't clip the key,
    > you're going to get hosed when the system attempts to mount the first
    > partition on HD0 as the system image.
    >
    > You're either going to have to trust the product or not. If not, then use
    > what I use which is a little bit cheaper and that's BootItNG.
    >
    > BTW: I do have to disagree with a site that claims, right on their main
    > page:
    >
    > "Partitioning The Hard Disk Increases Performance ..".
    >
    > when it does exactly the opposite. It's sort of an instant turn off for
    > me especially when I dig into the details of the article and see the other
    > mistakes. Then again, when talking about marketing hype...
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426d8191$0$375$cc9e4d1f@news.dial.pipex.com...
    >> Walter,
    >> I had a play around with all this, but gave up in the end, and
    >> reinstalled XP.
    >>
    >> Could you have a look at this and tell me if it now seems 'normal'.
    >>
    >> At this stage I would like to take regular backup images, (ideally using
    >> Acronis, as I have that), and restore them to the Maxtor (HD1) for
    >> checking. Can you forsee any problems now?
    >>
    >> Finally, I believe it would be relatively easy to restore images to any
    >> of the other partitions on say the Maxtor (there are three). Do I need to
    >> modify boot.ini in order to access them. My BIOS has a boot loader if I
    >> press F8 so would they then appear on it's menu?
    >>
    >> Thanks,
    >>
    >> Dave
    >>
    >> [boot loader]
    >> timeout=30
    >> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >> [operating systems]
    >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >> Edition" /fastdetect /NoExecute=OptIn
    >>
    >>
    >> PARTINFO 1.09
    >> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>
    >> Run date: 04/26/2005 0:36
    >>
    >> ====================================================================
    >> MBR Partition Information (HD0):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    >> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    >> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x03A962B0
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x03A962B
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x844C0F974C0F8362
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID: 0x2
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 61432560
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0FA285C7
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0FA285C
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0xF2281E1A281DDF03
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID: 0x3
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 323741880
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x0FA2C488
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x0FA2C48
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x7AB4DECCB4DE89D1
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> ====================================================================
    >> MBR Partition Information (HD1):
    >> +====+====+=============+====+=============+===========+===========+
    >> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    >> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >> +====+====+=============+====+=============+===========+===========+
    >> BOOT SECTOR INFORMATION
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 63
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x024C1258
    >> MFT LCN: 0x0B42FF
    >> MFT Mirr LCN: 0x03D54EA
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x4228D79E28D78EF3
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >> File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID: 0x2
    >> Jump: EB 52 90
    >> OEM Name: NTFS
    >> Bytes Per Sec: 512
    >> Sec Per Clust: 8
    >> Res Sectors: 0
    >> Zero 1: 0x0
    >> Zero 2: 0x0
    >> NA 1: 0x0
    >> Media: 0xF8
    >> Zero 3: 0x0
    >> Sec Per Track: 63
    >> Heads: 255
    >> Hidden Secs: 38539935
    >> NA 2: 0x0
    >> NA 3: 0x800080
    >> Total Sectors: 0x010557821
    >> MFT LCN: 0x0C0000
    >> MFT Mirr LCN: 0x01055782
    >> Clust Per FRS: 0xF6
    >> Clust Per IBlock: 0x1
    >> Volume SN: 0x7E38F7BF38F7750D
    >> Checksum: 0x0
    >> Boot Flag: 0xAA55
    >> -------------------------------------------------------------------------------
    >>
    >>
    >>
    >
  25. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    If you remove HD0 then anything that goes splat will happen only on the
    exposed partitions on HD1. The problem you're may have is if that particular
    OS image is looking for a volume that was just physically removed (unless
    you clip the mounteddevices key in advance and the partitions enumerate
    correctly thereafter). If you can live with that, then you're OK.

    I'd be hesitant about doing too much physical recabling though. That's how
    connectors wear out and get bent or broken. ;-)

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426e4bef$0$295$cc9e4d1f@news.dial.pipex.com...
    > OK, thanks for all that advice Walter. I used a trial version of BootItNG
    > some years ago, so I'll check it out again.
    >
    > One final thing. Presumably it's ok to restore a cloned HD0 partition
    > to HD1. Then to remove HD0 and replace it with HD1 and reboot. That isn't
    > going to
    > affect anything when I revert back to normal is it?
    >
    > Dave
    >
    > "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    > news:uUI0Q3fSFHA.3076@tk2msftngp13.phx.gbl...
    >> This structure looks better as long as you don't introduce a logical
    >> volume in the mix at some point in time, based on what you're intending.
    >> If you do, you're going to have some issues with partition enumeration.
    >>
    >> I'm looking at the Acronis web site and what I don't see right off hand
    >> is a boot manager as part of your package. It appears that with a
    >> different package, you can get a boot manager, but I don't have any hands
    >> on with it. I can't tell if it's capable of doing what needs be done in
    >> order to actually fire up an OS image from a different BIOS enumerated
    >> device. It sort of implies that it can, but I since they make a rather
    >> outrageous claim regarding performance, I can't trust what I'm reading.
    >> Regardless, one of the issues is going to revolve around the
    >> mounteddevices key and the secondary issue is with how devices and
    >> partitions are enumerated during system startup. I don't see a practical
    >> way, with the tools you have, to validate a partition image outside of
    >> restoring it in-situ. Even if you clip the mounteddevices key in advance
    >> of snapping an image, and configure the BIOS to bootstrap HD1 instead of
    >> HD0 you're going to get hosed when partitions are reenumerated. And if
    >> you don't clip the key, you're going to get hosed when the system
    >> attempts to mount the first partition on HD0 as the system image.
    >>
    >> You're either going to have to trust the product or not. If not, then use
    >> what I use which is a little bit cheaper and that's BootItNG.
    >>
    >> BTW: I do have to disagree with a site that claims, right on their main
    >> page:
    >>
    >> "Partitioning The Hard Disk Increases Performance ..".
    >>
    >> when it does exactly the opposite. It's sort of an instant turn off for
    >> me especially when I dig into the details of the article and see the
    >> other mistakes. Then again, when talking about marketing hype...
    >>
    >> --
    >> Walter Clayton
    >> Any technology distinguishable from magic is insufficiently advanced.
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426d8191$0$375$cc9e4d1f@news.dial.pipex.com...
    >>> Walter,
    >>> I had a play around with all this, but gave up in the end, and
    >>> reinstalled XP.
    >>>
    >>> Could you have a look at this and tell me if it now seems 'normal'.
    >>>
    >>> At this stage I would like to take regular backup images, (ideally using
    >>> Acronis, as I have that), and restore them to the Maxtor (HD1) for
    >>> checking. Can you forsee any problems now?
    >>>
    >>> Finally, I believe it would be relatively easy to restore images to any
    >>> of the other partitions on say the Maxtor (there are three). Do I need
    >>> to modify boot.ini in order to access them. My BIOS has a boot loader if
    >>> I press F8 so would they then appear on it's menu?
    >>>
    >>> Thanks,
    >>>
    >>> Dave
    >>>
    >>> [boot loader]
    >>> timeout=30
    >>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >>> [operating systems]
    >>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >>> Edition" /fastdetect /NoExecute=OptIn
    >>>
    >>>
    >>> PARTINFO 1.09
    >>> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>>
    >>> Run date: 04/26/2005 0:36
    >>>
    >>> ====================================================================
    >>> MBR Partition Information (HD0):
    >>> +====+====+=============+====+=============+===========+===========+
    >>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    >>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    >>> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    >>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>> +====+====+=============+====+=============+===========+===========+
    >>> BOOT SECTOR INFORMATION
    >>> -------------------------------------------------------------------------------
    >>> File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    >>> Jump: EB 52 90
    >>> OEM Name: NTFS
    >>> Bytes Per Sec: 512
    >>> Sec Per Clust: 8
    >>> Res Sectors: 0
    >>> Zero 1: 0x0
    >>> Zero 2: 0x0
    >>> NA 1: 0x0
    >>> Media: 0xF8
    >>> Zero 3: 0x0
    >>> Sec Per Track: 63
    >>> Heads: 255
    >>> Hidden Secs: 63
    >>> NA 2: 0x0
    >>> NA 3: 0x800080
    >>> Total Sectors: 0x03A962B0
    >>> MFT LCN: 0x0C0000
    >>> MFT Mirr LCN: 0x03A962B
    >>> Clust Per FRS: 0xF6
    >>> Clust Per IBlock: 0x1
    >>> Volume SN: 0x844C0F974C0F8362
    >>> Checksum: 0x0
    >>> Boot Flag: 0xAA55
    >>> -------------------------------------------------------------------------------
    >>> File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID: 0x2
    >>> Jump: EB 52 90
    >>> OEM Name: NTFS
    >>> Bytes Per Sec: 512
    >>> Sec Per Clust: 8
    >>> Res Sectors: 0
    >>> Zero 1: 0x0
    >>> Zero 2: 0x0
    >>> NA 1: 0x0
    >>> Media: 0xF8
    >>> Zero 3: 0x0
    >>> Sec Per Track: 63
    >>> Heads: 255
    >>> Hidden Secs: 61432560
    >>> NA 2: 0x0
    >>> NA 3: 0x800080
    >>> Total Sectors: 0x0FA285C7
    >>> MFT LCN: 0x0C0000
    >>> MFT Mirr LCN: 0x0FA285C
    >>> Clust Per FRS: 0xF6
    >>> Clust Per IBlock: 0x1
    >>> Volume SN: 0xF2281E1A281DDF03
    >>> Checksum: 0x0
    >>> Boot Flag: 0xAA55
    >>> -------------------------------------------------------------------------------
    >>> File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID: 0x3
    >>> Jump: EB 52 90
    >>> OEM Name: NTFS
    >>> Bytes Per Sec: 512
    >>> Sec Per Clust: 8
    >>> Res Sectors: 0
    >>> Zero 1: 0x0
    >>> Zero 2: 0x0
    >>> NA 1: 0x0
    >>> Media: 0xF8
    >>> Zero 3: 0x0
    >>> Sec Per Track: 63
    >>> Heads: 255
    >>> Hidden Secs: 323741880
    >>> NA 2: 0x0
    >>> NA 3: 0x800080
    >>> Total Sectors: 0x0FA2C488
    >>> MFT LCN: 0x0C0000
    >>> MFT Mirr LCN: 0x0FA2C48
    >>> Clust Per FRS: 0xF6
    >>> Clust Per IBlock: 0x1
    >>> Volume SN: 0x7AB4DECCB4DE89D1
    >>> Checksum: 0x0
    >>> Boot Flag: 0xAA55
    >>> -------------------------------------------------------------------------------
    >>> ====================================================================
    >>> MBR Partition Information (HD1):
    >>> +====+====+=============+====+=============+===========+===========+
    >>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    >>> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>> +====+====+=============+====+=============+===========+===========+
    >>> BOOT SECTOR INFORMATION
    >>> -------------------------------------------------------------------------------
    >>> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >>> Jump: EB 52 90
    >>> OEM Name: NTFS
    >>> Bytes Per Sec: 512
    >>> Sec Per Clust: 8
    >>> Res Sectors: 0
    >>> Zero 1: 0x0
    >>> Zero 2: 0x0
    >>> NA 1: 0x0
    >>> Media: 0xF8
    >>> Zero 3: 0x0
    >>> Sec Per Track: 63
    >>> Heads: 255
    >>> Hidden Secs: 63
    >>> NA 2: 0x0
    >>> NA 3: 0x800080
    >>> Total Sectors: 0x024C1258
    >>> MFT LCN: 0x0B42FF
    >>> MFT Mirr LCN: 0x03D54EA
    >>> Clust Per FRS: 0xF6
    >>> Clust Per IBlock: 0x1
    >>> Volume SN: 0x4228D79E28D78EF3
    >>> Checksum: 0x0
    >>> Boot Flag: 0xAA55
    >>> -------------------------------------------------------------------------------
    >>> File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID: 0x2
    >>> Jump: EB 52 90
    >>> OEM Name: NTFS
    >>> Bytes Per Sec: 512
    >>> Sec Per Clust: 8
    >>> Res Sectors: 0
    >>> Zero 1: 0x0
    >>> Zero 2: 0x0
    >>> NA 1: 0x0
    >>> Media: 0xF8
    >>> Zero 3: 0x0
    >>> Sec Per Track: 63
    >>> Heads: 255
    >>> Hidden Secs: 38539935
    >>> NA 2: 0x0
    >>> NA 3: 0x800080
    >>> Total Sectors: 0x010557821
    >>> MFT LCN: 0x0C0000
    >>> MFT Mirr LCN: 0x01055782
    >>> Clust Per FRS: 0xF6
    >>> Clust Per IBlock: 0x1
    >>> Volume SN: 0x7E38F7BF38F7750D
    >>> Checksum: 0x0
    >>> Boot Flag: 0xAA55
    >>> -------------------------------------------------------------------------------
    >>>
    >>>
    >>>
    >>
    >
    >
  26. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Understood. Now that would have been it. BUT. . .

    I've just been reinstalling XP Home Ed on HD0. I completely wiped the disk
    of partitions because of the earlier problems, and started again. During
    installation, I had a restored clone on HD1 which seemed harmless, and I
    wasn't accessing or booting from it.

    Then I started having problems. The machine stalled during booting, and
    wouldn't reboot. I tried the other drive, HD1. It booted but then started
    locking up and it eventually hung. I tried removing HD0 and HD1 wouldn't
    boot at all. It became apparent that the drives had become dependent on each
    other.One wouldn't boot without the other. Also my new partitions on HD0
    were all over the place, with C: now being a logical drive.

    I'm coming to the conlusion that either a) I've got some strange unresolved
    hardware issues, although I had no problems prior to having 2 bootable
    drives, or b) XP really doesn't like having 2 bootable drives, although I
    always thought it was ok with this.

    So, yet another reinstall, having first deleted the bootable partition on
    HD1. When I eventually get back on track, I will make a clone, check it
    works on it's own, and then remove it completely until such time as it may
    be needed.

    Would you expect this to happen with two bootable drives?

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uBkyYmqSFHA.228@TK2MSFTNGP10.phx.gbl...
    > If you remove HD0 then anything that goes splat will happen only on the
    > exposed partitions on HD1. The problem you're may have is if that
    > particular OS image is looking for a volume that was just physically
    > removed (unless you clip the mounteddevices key in advance and the
    > partitions enumerate correctly thereafter). If you can live with that,
    > then you're OK.
    >
    > I'd be hesitant about doing too much physical recabling though. That's how
    > connectors wear out and get bent or broken. ;-)
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426e4bef$0$295$cc9e4d1f@news.dial.pipex.com...
    >> OK, thanks for all that advice Walter. I used a trial version of BootItNG
    >> some years ago, so I'll check it out again.
    >>
    >> One final thing. Presumably it's ok to restore a cloned HD0 partition
    >> to HD1. Then to remove HD0 and replace it with HD1 and reboot. That isn't
    >> going to
    >> affect anything when I revert back to normal is it?
    >>
    >> Dave
    >>
    >> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >> news:uUI0Q3fSFHA.3076@tk2msftngp13.phx.gbl...
    >>> This structure looks better as long as you don't introduce a logical
    >>> volume in the mix at some point in time, based on what you're intending.
    >>> If you do, you're going to have some issues with partition enumeration.
    >>>
    >>> I'm looking at the Acronis web site and what I don't see right off hand
    >>> is a boot manager as part of your package. It appears that with a
    >>> different package, you can get a boot manager, but I don't have any
    >>> hands on with it. I can't tell if it's capable of doing what needs be
    >>> done in order to actually fire up an OS image from a different BIOS
    >>> enumerated device. It sort of implies that it can, but I since they make
    >>> a rather outrageous claim regarding performance, I can't trust what I'm
    >>> reading. Regardless, one of the issues is going to revolve around the
    >>> mounteddevices key and the secondary issue is with how devices and
    >>> partitions are enumerated during system startup. I don't see a practical
    >>> way, with the tools you have, to validate a partition image outside of
    >>> restoring it in-situ. Even if you clip the mounteddevices key in advance
    >>> of snapping an image, and configure the BIOS to bootstrap HD1 instead of
    >>> HD0 you're going to get hosed when partitions are reenumerated. And if
    >>> you don't clip the key, you're going to get hosed when the system
    >>> attempts to mount the first partition on HD0 as the system image.
    >>>
    >>> You're either going to have to trust the product or not. If not, then
    >>> use what I use which is a little bit cheaper and that's BootItNG.
    >>>
    >>> BTW: I do have to disagree with a site that claims, right on their main
    >>> page:
    >>>
    >>> "Partitioning The Hard Disk Increases Performance ..".
    >>>
    >>> when it does exactly the opposite. It's sort of an instant turn off for
    >>> me especially when I dig into the details of the article and see the
    >>> other mistakes. Then again, when talking about marketing hype...
    >>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:426d8191$0$375$cc9e4d1f@news.dial.pipex.com...
    >>>> Walter,
    >>>> I had a play around with all this, but gave up in the end, and
    >>>> reinstalled XP.
    >>>>
    >>>> Could you have a look at this and tell me if it now seems 'normal'.
    >>>>
    >>>> At this stage I would like to take regular backup images, (ideally
    >>>> using Acronis, as I have that), and restore them to the Maxtor (HD1)
    >>>> for checking. Can you forsee any problems now?
    >>>>
    >>>> Finally, I believe it would be relatively easy to restore images to any
    >>>> of the other partitions on say the Maxtor (there are three). Do I need
    >>>> to modify boot.ini in order to access them. My BIOS has a boot loader
    >>>> if I press F8 so would they then appear on it's menu?
    >>>>
    >>>> Thanks,
    >>>>
    >>>> Dave
    >>>>
    >>>> [boot loader]
    >>>> timeout=30
    >>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >>>> [operating systems]
    >>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >>>> Edition" /fastdetect /NoExecute=OptIn
    >>>>
    >>>>
    >>>> PARTINFO 1.09
    >>>> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>>>
    >>>> Run date: 04/26/2005 0:36
    >>>>
    >>>> ====================================================================
    >>>> MBR Partition Information (HD0):
    >>>> +====+====+=============+====+=============+===========+===========+
    >>>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    >>>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    >>>> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    >>>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>> +====+====+=============+====+=============+===========+===========+
    >>>> BOOT SECTOR INFORMATION
    >>>> -------------------------------------------------------------------------------
    >>>> File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    >>>> Jump: EB 52 90
    >>>> OEM Name: NTFS
    >>>> Bytes Per Sec: 512
    >>>> Sec Per Clust: 8
    >>>> Res Sectors: 0
    >>>> Zero 1: 0x0
    >>>> Zero 2: 0x0
    >>>> NA 1: 0x0
    >>>> Media: 0xF8
    >>>> Zero 3: 0x0
    >>>> Sec Per Track: 63
    >>>> Heads: 255
    >>>> Hidden Secs: 63
    >>>> NA 2: 0x0
    >>>> NA 3: 0x800080
    >>>> Total Sectors: 0x03A962B0
    >>>> MFT LCN: 0x0C0000
    >>>> MFT Mirr LCN: 0x03A962B
    >>>> Clust Per FRS: 0xF6
    >>>> Clust Per IBlock: 0x1
    >>>> Volume SN: 0x844C0F974C0F8362
    >>>> Checksum: 0x0
    >>>> Boot Flag: 0xAA55
    >>>> -------------------------------------------------------------------------------
    >>>> File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID: 0x2
    >>>> Jump: EB 52 90
    >>>> OEM Name: NTFS
    >>>> Bytes Per Sec: 512
    >>>> Sec Per Clust: 8
    >>>> Res Sectors: 0
    >>>> Zero 1: 0x0
    >>>> Zero 2: 0x0
    >>>> NA 1: 0x0
    >>>> Media: 0xF8
    >>>> Zero 3: 0x0
    >>>> Sec Per Track: 63
    >>>> Heads: 255
    >>>> Hidden Secs: 61432560
    >>>> NA 2: 0x0
    >>>> NA 3: 0x800080
    >>>> Total Sectors: 0x0FA285C7
    >>>> MFT LCN: 0x0C0000
    >>>> MFT Mirr LCN: 0x0FA285C
    >>>> Clust Per FRS: 0xF6
    >>>> Clust Per IBlock: 0x1
    >>>> Volume SN: 0xF2281E1A281DDF03
    >>>> Checksum: 0x0
    >>>> Boot Flag: 0xAA55
    >>>> -------------------------------------------------------------------------------
    >>>> File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID:
    >>>> 0x3
    >>>> Jump: EB 52 90
    >>>> OEM Name: NTFS
    >>>> Bytes Per Sec: 512
    >>>> Sec Per Clust: 8
    >>>> Res Sectors: 0
    >>>> Zero 1: 0x0
    >>>> Zero 2: 0x0
    >>>> NA 1: 0x0
    >>>> Media: 0xF8
    >>>> Zero 3: 0x0
    >>>> Sec Per Track: 63
    >>>> Heads: 255
    >>>> Hidden Secs: 323741880
    >>>> NA 2: 0x0
    >>>> NA 3: 0x800080
    >>>> Total Sectors: 0x0FA2C488
    >>>> MFT LCN: 0x0C0000
    >>>> MFT Mirr LCN: 0x0FA2C48
    >>>> Clust Per FRS: 0xF6
    >>>> Clust Per IBlock: 0x1
    >>>> Volume SN: 0x7AB4DECCB4DE89D1
    >>>> Checksum: 0x0
    >>>> Boot Flag: 0xAA55
    >>>> -------------------------------------------------------------------------------
    >>>> ====================================================================
    >>>> MBR Partition Information (HD1):
    >>>> +====+====+=============+====+=============+===========+===========+
    >>>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >>>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    >>>> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>> +====+====+=============+====+=============+===========+===========+
    >>>> BOOT SECTOR INFORMATION
    >>>> -------------------------------------------------------------------------------
    >>>> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >>>> Jump: EB 52 90
    >>>> OEM Name: NTFS
    >>>> Bytes Per Sec: 512
    >>>> Sec Per Clust: 8
    >>>> Res Sectors: 0
    >>>> Zero 1: 0x0
    >>>> Zero 2: 0x0
    >>>> NA 1: 0x0
    >>>> Media: 0xF8
    >>>> Zero 3: 0x0
    >>>> Sec Per Track: 63
    >>>> Heads: 255
    >>>> Hidden Secs: 63
    >>>> NA 2: 0x0
    >>>> NA 3: 0x800080
    >>>> Total Sectors: 0x024C1258
    >>>> MFT LCN: 0x0B42FF
    >>>> MFT Mirr LCN: 0x03D54EA
    >>>> Clust Per FRS: 0xF6
    >>>> Clust Per IBlock: 0x1
    >>>> Volume SN: 0x4228D79E28D78EF3
    >>>> Checksum: 0x0
    >>>> Boot Flag: 0xAA55
    >>>> -------------------------------------------------------------------------------
    >>>> File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID: 0x2
    >>>> Jump: EB 52 90
    >>>> OEM Name: NTFS
    >>>> Bytes Per Sec: 512
    >>>> Sec Per Clust: 8
    >>>> Res Sectors: 0
    >>>> Zero 1: 0x0
    >>>> Zero 2: 0x0
    >>>> NA 1: 0x0
    >>>> Media: 0xF8
    >>>> Zero 3: 0x0
    >>>> Sec Per Track: 63
    >>>> Heads: 255
    >>>> Hidden Secs: 38539935
    >>>> NA 2: 0x0
    >>>> NA 3: 0x800080
    >>>> Total Sectors: 0x010557821
    >>>> MFT LCN: 0x0C0000
    >>>> MFT Mirr LCN: 0x01055782
    >>>> Clust Per FRS: 0xF6
    >>>> Clust Per IBlock: 0x1
    >>>> Volume SN: 0x7E38F7BF38F7750D
    >>>> Checksum: 0x0
    >>>> Boot Flag: 0xAA55
    >>>> -------------------------------------------------------------------------------
    >>>>
    >>>>
    >>>>
    >>>
    >>
    >>
    >
  27. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Tricky question to answer.

    There are potential issues if you're installing with multiple primaries
    visible, especially if there are multiple primaries on the target drive. I
    touch on one of the issues here
    http://www.dcr.net/~w-clayton/Boot%20and%20System%20partitions.htm and I
    have a sneaky suspicion, in hind sight, this the route you took.

    The biggest issue with multiple primaries is enumeration order, whether or
    not you're deleting and recreating the partitions and sequence of events.
    Literally. It's best, unfortunately, if you're going to do multiple
    partitions, to do partition creation using 3rd party tools (and that also
    specifically excludes DOS fdisk/format; they are dangerous on modern
    drives).

    I'm still debating how to write the issues up since it's rather dynamic. A
    classic example is installing with a zip cartridge mounted. In this instance
    the target partition will be enumerated as the drive after the zip drive(s)
    and all the optical drives are enumerated rather than C: since the zip drive
    took that drive letter when the setup engine was initializing.

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:426fd4b4$0$298$cc9e4d1f@news.dial.pipex.com...
    > Understood. Now that would have been it. BUT. . .
    >
    > I've just been reinstalling XP Home Ed on HD0. I completely wiped the disk
    > of partitions because of the earlier problems, and started again. During
    > installation, I had a restored clone on HD1 which seemed harmless, and I
    > wasn't accessing or booting from it.
    >
    > Then I started having problems. The machine stalled during booting, and
    > wouldn't reboot. I tried the other drive, HD1. It booted but then started
    > locking up and it eventually hung. I tried removing HD0 and HD1 wouldn't
    > boot at all. It became apparent that the drives had become dependent on
    > each other.One wouldn't boot without the other. Also my new partitions on
    > HD0 were all over the place, with C: now being a logical drive.
    >
    > I'm coming to the conlusion that either a) I've got some strange
    > unresolved hardware issues, although I had no problems prior to having 2
    > bootable drives, or b) XP really doesn't like having 2 bootable drives,
    > although I always thought it was ok with this.
    >
    > So, yet another reinstall, having first deleted the bootable partition on
    > HD1. When I eventually get back on track, I will make a clone, check it
    > works on it's own, and then remove it completely until such time as it may
    > be needed.
    >
    > Would you expect this to happen with two bootable drives?
    >
    > Dave
    >
    >
    > "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    > news:uBkyYmqSFHA.228@TK2MSFTNGP10.phx.gbl...
    >> If you remove HD0 then anything that goes splat will happen only on the
    >> exposed partitions on HD1. The problem you're may have is if that
    >> particular OS image is looking for a volume that was just physically
    >> removed (unless you clip the mounteddevices key in advance and the
    >> partitions enumerate correctly thereafter). If you can live with that,
    >> then you're OK.
    >>
    >> I'd be hesitant about doing too much physical recabling though. That's
    >> how connectors wear out and get bent or broken. ;-)
    >>
    >> --
    >> Walter Clayton
    >> Any technology distinguishable from magic is insufficiently advanced.
    >>
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:426e4bef$0$295$cc9e4d1f@news.dial.pipex.com...
    >>> OK, thanks for all that advice Walter. I used a trial version of
    >>> BootItNG
    >>> some years ago, so I'll check it out again.
    >>>
    >>> One final thing. Presumably it's ok to restore a cloned HD0 partition
    >>> to HD1. Then to remove HD0 and replace it with HD1 and reboot. That
    >>> isn't going to
    >>> affect anything when I revert back to normal is it?
    >>>
    >>> Dave
    >>>
    >>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>> news:uUI0Q3fSFHA.3076@tk2msftngp13.phx.gbl...
    >>>> This structure looks better as long as you don't introduce a logical
    >>>> volume in the mix at some point in time, based on what you're
    >>>> intending. If you do, you're going to have some issues with partition
    >>>> enumeration.
    >>>>
    >>>> I'm looking at the Acronis web site and what I don't see right off hand
    >>>> is a boot manager as part of your package. It appears that with a
    >>>> different package, you can get a boot manager, but I don't have any
    >>>> hands on with it. I can't tell if it's capable of doing what needs be
    >>>> done in order to actually fire up an OS image from a different BIOS
    >>>> enumerated device. It sort of implies that it can, but I since they
    >>>> make a rather outrageous claim regarding performance, I can't trust
    >>>> what I'm reading. Regardless, one of the issues is going to revolve
    >>>> around the mounteddevices key and the secondary issue is with how
    >>>> devices and partitions are enumerated during system startup. I don't
    >>>> see a practical way, with the tools you have, to validate a partition
    >>>> image outside of restoring it in-situ. Even if you clip the
    >>>> mounteddevices key in advance of snapping an image, and configure the
    >>>> BIOS to bootstrap HD1 instead of HD0 you're going to get hosed when
    >>>> partitions are reenumerated. And if you don't clip the key, you're
    >>>> going to get hosed when the system attempts to mount the first
    >>>> partition on HD0 as the system image.
    >>>>
    >>>> You're either going to have to trust the product or not. If not, then
    >>>> use what I use which is a little bit cheaper and that's BootItNG.
    >>>>
    >>>> BTW: I do have to disagree with a site that claims, right on their main
    >>>> page:
    >>>>
    >>>> "Partitioning The Hard Disk Increases Performance ..".
    >>>>
    >>>> when it does exactly the opposite. It's sort of an instant turn off
    >>>> for me especially when I dig into the details of the article and see
    >>>> the other mistakes. Then again, when talking about marketing hype...
    >>>>
    >>>> --
    >>>> Walter Clayton
    >>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>
    >>>>
    >>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>> news:426d8191$0$375$cc9e4d1f@news.dial.pipex.com...
    >>>>> Walter,
    >>>>> I had a play around with all this, but gave up in the end, and
    >>>>> reinstalled XP.
    >>>>>
    >>>>> Could you have a look at this and tell me if it now seems 'normal'.
    >>>>>
    >>>>> At this stage I would like to take regular backup images, (ideally
    >>>>> using Acronis, as I have that), and restore them to the Maxtor (HD1)
    >>>>> for checking. Can you forsee any problems now?
    >>>>>
    >>>>> Finally, I believe it would be relatively easy to restore images to
    >>>>> any of the other partitions on say the Maxtor (there are three). Do I
    >>>>> need to modify boot.ini in order to access them. My BIOS has a boot
    >>>>> loader if I press F8 so would they then appear on it's menu?
    >>>>>
    >>>>> Thanks,
    >>>>>
    >>>>> Dave
    >>>>>
    >>>>> [boot loader]
    >>>>> timeout=30
    >>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >>>>> [operating systems]
    >>>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
    >>>>> Edition" /fastdetect /NoExecute=OptIn
    >>>>>
    >>>>>
    >>>>> PARTINFO 1.09
    >>>>> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>>>>
    >>>>> Run date: 04/26/2005 0:36
    >>>>>
    >>>>> ====================================================================
    >>>>> MBR Partition Information (HD0):
    >>>>> +====+====+=============+====+=============+===========+===========+
    >>>>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    >>>>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    >>>>> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    >>>>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>>> +====+====+=============+====+=============+===========+===========+
    >>>>> BOOT SECTOR INFORMATION
    >>>>> -------------------------------------------------------------------------------
    >>>>> File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    >>>>> Jump: EB 52 90
    >>>>> OEM Name: NTFS
    >>>>> Bytes Per Sec: 512
    >>>>> Sec Per Clust: 8
    >>>>> Res Sectors: 0
    >>>>> Zero 1: 0x0
    >>>>> Zero 2: 0x0
    >>>>> NA 1: 0x0
    >>>>> Media: 0xF8
    >>>>> Zero 3: 0x0
    >>>>> Sec Per Track: 63
    >>>>> Heads: 255
    >>>>> Hidden Secs: 63
    >>>>> NA 2: 0x0
    >>>>> NA 3: 0x800080
    >>>>> Total Sectors: 0x03A962B0
    >>>>> MFT LCN: 0x0C0000
    >>>>> MFT Mirr LCN: 0x03A962B
    >>>>> Clust Per FRS: 0xF6
    >>>>> Clust Per IBlock: 0x1
    >>>>> Volume SN: 0x844C0F974C0F8362
    >>>>> Checksum: 0x0
    >>>>> Boot Flag: 0xAA55
    >>>>> -------------------------------------------------------------------------------
    >>>>> File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID:
    >>>>> 0x2
    >>>>> Jump: EB 52 90
    >>>>> OEM Name: NTFS
    >>>>> Bytes Per Sec: 512
    >>>>> Sec Per Clust: 8
    >>>>> Res Sectors: 0
    >>>>> Zero 1: 0x0
    >>>>> Zero 2: 0x0
    >>>>> NA 1: 0x0
    >>>>> Media: 0xF8
    >>>>> Zero 3: 0x0
    >>>>> Sec Per Track: 63
    >>>>> Heads: 255
    >>>>> Hidden Secs: 61432560
    >>>>> NA 2: 0x0
    >>>>> NA 3: 0x800080
    >>>>> Total Sectors: 0x0FA285C7
    >>>>> MFT LCN: 0x0C0000
    >>>>> MFT Mirr LCN: 0x0FA285C
    >>>>> Clust Per FRS: 0xF6
    >>>>> Clust Per IBlock: 0x1
    >>>>> Volume SN: 0xF2281E1A281DDF03
    >>>>> Checksum: 0x0
    >>>>> Boot Flag: 0xAA55
    >>>>> -------------------------------------------------------------------------------
    >>>>> File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID:
    >>>>> 0x3
    >>>>> Jump: EB 52 90
    >>>>> OEM Name: NTFS
    >>>>> Bytes Per Sec: 512
    >>>>> Sec Per Clust: 8
    >>>>> Res Sectors: 0
    >>>>> Zero 1: 0x0
    >>>>> Zero 2: 0x0
    >>>>> NA 1: 0x0
    >>>>> Media: 0xF8
    >>>>> Zero 3: 0x0
    >>>>> Sec Per Track: 63
    >>>>> Heads: 255
    >>>>> Hidden Secs: 323741880
    >>>>> NA 2: 0x0
    >>>>> NA 3: 0x800080
    >>>>> Total Sectors: 0x0FA2C488
    >>>>> MFT LCN: 0x0C0000
    >>>>> MFT Mirr LCN: 0x0FA2C48
    >>>>> Clust Per FRS: 0xF6
    >>>>> Clust Per IBlock: 0x1
    >>>>> Volume SN: 0x7AB4DECCB4DE89D1
    >>>>> Checksum: 0x0
    >>>>> Boot Flag: 0xAA55
    >>>>> -------------------------------------------------------------------------------
    >>>>> ====================================================================
    >>>>> MBR Partition Information (HD1):
    >>>>> +====+====+=============+====+=============+===========+===========+
    >>>>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >>>>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    >>>>> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>>> +====+====+=============+====+=============+===========+===========+
    >>>>> BOOT SECTOR INFORMATION
    >>>>> -------------------------------------------------------------------------------
    >>>>> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >>>>> Jump: EB 52 90
    >>>>> OEM Name: NTFS
    >>>>> Bytes Per Sec: 512
    >>>>> Sec Per Clust: 8
    >>>>> Res Sectors: 0
    >>>>> Zero 1: 0x0
    >>>>> Zero 2: 0x0
    >>>>> NA 1: 0x0
    >>>>> Media: 0xF8
    >>>>> Zero 3: 0x0
    >>>>> Sec Per Track: 63
    >>>>> Heads: 255
    >>>>> Hidden Secs: 63
    >>>>> NA 2: 0x0
    >>>>> NA 3: 0x800080
    >>>>> Total Sectors: 0x024C1258
    >>>>> MFT LCN: 0x0B42FF
    >>>>> MFT Mirr LCN: 0x03D54EA
    >>>>> Clust Per FRS: 0xF6
    >>>>> Clust Per IBlock: 0x1
    >>>>> Volume SN: 0x4228D79E28D78EF3
    >>>>> Checksum: 0x0
    >>>>> Boot Flag: 0xAA55
    >>>>> -------------------------------------------------------------------------------
    >>>>> File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID:
    >>>>> 0x2
    >>>>> Jump: EB 52 90
    >>>>> OEM Name: NTFS
    >>>>> Bytes Per Sec: 512
    >>>>> Sec Per Clust: 8
    >>>>> Res Sectors: 0
    >>>>> Zero 1: 0x0
    >>>>> Zero 2: 0x0
    >>>>> NA 1: 0x0
    >>>>> Media: 0xF8
    >>>>> Zero 3: 0x0
    >>>>> Sec Per Track: 63
    >>>>> Heads: 255
    >>>>> Hidden Secs: 38539935
    >>>>> NA 2: 0x0
    >>>>> NA 3: 0x800080
    >>>>> Total Sectors: 0x010557821
    >>>>> MFT LCN: 0x0C0000
    >>>>> MFT Mirr LCN: 0x01055782
    >>>>> Clust Per FRS: 0xF6
    >>>>> Clust Per IBlock: 0x1
    >>>>> Volume SN: 0x7E38F7BF38F7750D
    >>>>> Checksum: 0x0
    >>>>> Boot Flag: 0xAA55
    >>>>> -------------------------------------------------------------------------------
    >>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >
    >
  28. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter,

    I had a look at that link. Very, very interesting! That is exactly what has
    happened with my system. I think I'd almost be inclined to treat my cloned
    drive like a virus after this.

    I had another look at an older version of BootItNG I had. Perhaps it's a
    confidence thing but I wasn't sure about the fact that it creates it's own
    boot partition, and then I had great difficulty removing it afterwards.
    After I removed it I could no longer boot, but I may well have done
    something wrong. Is it reasonably easy to use for people like me who may be
    computer literate but haven't much of a clue about the intricacies of XP'x
    boot process.

    Would it enable me to clone, leaving both drives in situ, freely booting
    from either, without the worry of all these partion and enumeration
    problems?

    Dave

    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uo5to23SFHA.2424@TK2MSFTNGP09.phx.gbl...
    > Tricky question to answer.
    >
    > There are potential issues if you're installing with multiple primaries
    > visible, especially if there are multiple primaries on the target drive. I
    > touch on one of the issues here
    > http://www.dcr.net/~w-clayton/Boot%20and%20System%20partitions.htm and I
    > have a sneaky suspicion, in hind sight, this the route you took.
    >
    > The biggest issue with multiple primaries is enumeration order, whether or
    > not you're deleting and recreating the partitions and sequence of events.
    > Literally. It's best, unfortunately, if you're going to do multiple
    > partitions, to do partition creation using 3rd party tools (and that also
    > specifically excludes DOS fdisk/format; they are dangerous on modern
    > drives).
    >
    > I'm still debating how to write the issues up since it's rather dynamic. A
    > classic example is installing with a zip cartridge mounted. In this
    > instance the target partition will be enumerated as the drive after the
    > zip drive(s) and all the optical drives are enumerated rather than C:
    > since the zip drive took that drive letter when the setup engine was
    > initializing.
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:426fd4b4$0$298$cc9e4d1f@news.dial.pipex.com...
    >> Understood. Now that would have been it. BUT. . .
    >>
    >> I've just been reinstalling XP Home Ed on HD0. I completely wiped the
    >> disk of partitions because of the earlier problems, and started again.
    >> During installation, I had a restored clone on HD1 which seemed harmless,
    >> and I wasn't accessing or booting from it.
    >>
    >> Then I started having problems. The machine stalled during booting, and
    >> wouldn't reboot. I tried the other drive, HD1. It booted but then started
    >> locking up and it eventually hung. I tried removing HD0 and HD1 wouldn't
    >> boot at all. It became apparent that the drives had become dependent on
    >> each other.One wouldn't boot without the other. Also my new partitions on
    >> HD0 were all over the place, with C: now being a logical drive.
    >>
    >> I'm coming to the conlusion that either a) I've got some strange
    >> unresolved hardware issues, although I had no problems prior to having 2
    >> bootable drives, or b) XP really doesn't like having 2 bootable drives,
    >> although I always thought it was ok with this.
    >>
    >> So, yet another reinstall, having first deleted the bootable partition on
    >> HD1. When I eventually get back on track, I will make a clone, check it
    >> works on it's own, and then remove it completely until such time as it
    >> may be needed.
    >>
    >> Would you expect this to happen with two bootable drives?
    >>
    >> Dave
    >>
    >>
    >> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >> news:uBkyYmqSFHA.228@TK2MSFTNGP10.phx.gbl...
    >>> If you remove HD0 then anything that goes splat will happen only on the
    >>> exposed partitions on HD1. The problem you're may have is if that
    >>> particular OS image is looking for a volume that was just physically
    >>> removed (unless you clip the mounteddevices key in advance and the
    >>> partitions enumerate correctly thereafter). If you can live with that,
    >>> then you're OK.
    >>>
    >>> I'd be hesitant about doing too much physical recabling though. That's
    >>> how connectors wear out and get bent or broken. ;-)
    >>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:426e4bef$0$295$cc9e4d1f@news.dial.pipex.com...
    >>>> OK, thanks for all that advice Walter. I used a trial version of
    >>>> BootItNG
    >>>> some years ago, so I'll check it out again.
    >>>>
    >>>> One final thing. Presumably it's ok to restore a cloned HD0 partition
    >>>> to HD1. Then to remove HD0 and replace it with HD1 and reboot. That
    >>>> isn't going to
    >>>> affect anything when I revert back to normal is it?
    >>>>
    >>>> Dave
    >>>>
    >>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >>>> news:uUI0Q3fSFHA.3076@tk2msftngp13.phx.gbl...
    >>>>> This structure looks better as long as you don't introduce a logical
    >>>>> volume in the mix at some point in time, based on what you're
    >>>>> intending. If you do, you're going to have some issues with partition
    >>>>> enumeration.
    >>>>>
    >>>>> I'm looking at the Acronis web site and what I don't see right off
    >>>>> hand is a boot manager as part of your package. It appears that with a
    >>>>> different package, you can get a boot manager, but I don't have any
    >>>>> hands on with it. I can't tell if it's capable of doing what needs be
    >>>>> done in order to actually fire up an OS image from a different BIOS
    >>>>> enumerated device. It sort of implies that it can, but I since they
    >>>>> make a rather outrageous claim regarding performance, I can't trust
    >>>>> what I'm reading. Regardless, one of the issues is going to revolve
    >>>>> around the mounteddevices key and the secondary issue is with how
    >>>>> devices and partitions are enumerated during system startup. I don't
    >>>>> see a practical way, with the tools you have, to validate a partition
    >>>>> image outside of restoring it in-situ. Even if you clip the
    >>>>> mounteddevices key in advance of snapping an image, and configure the
    >>>>> BIOS to bootstrap HD1 instead of HD0 you're going to get hosed when
    >>>>> partitions are reenumerated. And if you don't clip the key, you're
    >>>>> going to get hosed when the system attempts to mount the first
    >>>>> partition on HD0 as the system image.
    >>>>>
    >>>>> You're either going to have to trust the product or not. If not, then
    >>>>> use what I use which is a little bit cheaper and that's BootItNG.
    >>>>>
    >>>>> BTW: I do have to disagree with a site that claims, right on their
    >>>>> main page:
    >>>>>
    >>>>> "Partitioning The Hard Disk Increases Performance ..".
    >>>>>
    >>>>> when it does exactly the opposite. It's sort of an instant turn off
    >>>>> for me especially when I dig into the details of the article and see
    >>>>> the other mistakes. Then again, when talking about marketing hype...
    >>>>>
    >>>>> --
    >>>>> Walter Clayton
    >>>>> Any technology distinguishable from magic is insufficiently advanced.
    >>>>>
    >>>>>
    >>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>>>> news:426d8191$0$375$cc9e4d1f@news.dial.pipex.com...
    >>>>>> Walter,
    >>>>>> I had a play around with all this, but gave up in the end, and
    >>>>>> reinstalled XP.
    >>>>>>
    >>>>>> Could you have a look at this and tell me if it now seems 'normal'.
    >>>>>>
    >>>>>> At this stage I would like to take regular backup images, (ideally
    >>>>>> using Acronis, as I have that), and restore them to the Maxtor (HD1)
    >>>>>> for checking. Can you forsee any problems now?
    >>>>>>
    >>>>>> Finally, I believe it would be relatively easy to restore images to
    >>>>>> any of the other partitions on say the Maxtor (there are three). Do I
    >>>>>> need to modify boot.ini in order to access them. My BIOS has a boot
    >>>>>> loader if I press F8 so would they then appear on it's menu?
    >>>>>>
    >>>>>> Thanks,
    >>>>>>
    >>>>>> Dave
    >>>>>>
    >>>>>> [boot loader]
    >>>>>> timeout=30
    >>>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    >>>>>> [operating systems]
    >>>>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
    >>>>>> Home Edition" /fastdetect /NoExecute=OptIn
    >>>>>>
    >>>>>>
    >>>>>> PARTINFO 1.09
    >>>>>> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
    >>>>>>
    >>>>>> Run date: 04/26/2005 0:36
    >>>>>>
    >>>>>> ====================================================================
    >>>>>> MBR Partition Information (HD0):
    >>>>>> +====+====+=============+====+=============+===========+===========+
    >>>>>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
    >>>>>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
    >>>>>> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
    >>>>>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>>>> +====+====+=============+====+=============+===========+===========+
    >>>>>> BOOT SECTOR INFORMATION
    >>>>>> -------------------------------------------------------------------------------
    >>>>>> File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
    >>>>>> Jump: EB 52 90
    >>>>>> OEM Name: NTFS
    >>>>>> Bytes Per Sec: 512
    >>>>>> Sec Per Clust: 8
    >>>>>> Res Sectors: 0
    >>>>>> Zero 1: 0x0
    >>>>>> Zero 2: 0x0
    >>>>>> NA 1: 0x0
    >>>>>> Media: 0xF8
    >>>>>> Zero 3: 0x0
    >>>>>> Sec Per Track: 63
    >>>>>> Heads: 255
    >>>>>> Hidden Secs: 63
    >>>>>> NA 2: 0x0
    >>>>>> NA 3: 0x800080
    >>>>>> Total Sectors: 0x03A962B0
    >>>>>> MFT LCN: 0x0C0000
    >>>>>> MFT Mirr LCN: 0x03A962B
    >>>>>> Clust Per FRS: 0xF6
    >>>>>> Clust Per IBlock: 0x1
    >>>>>> Volume SN: 0x844C0F974C0F8362
    >>>>>> Checksum: 0x0
    >>>>>> Boot Flag: 0xAA55
    >>>>>> -------------------------------------------------------------------------------
    >>>>>> File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID:
    >>>>>> 0x2
    >>>>>> Jump: EB 52 90
    >>>>>> OEM Name: NTFS
    >>>>>> Bytes Per Sec: 512
    >>>>>> Sec Per Clust: 8
    >>>>>> Res Sectors: 0
    >>>>>> Zero 1: 0x0
    >>>>>> Zero 2: 0x0
    >>>>>> NA 1: 0x0
    >>>>>> Media: 0xF8
    >>>>>> Zero 3: 0x0
    >>>>>> Sec Per Track: 63
    >>>>>> Heads: 255
    >>>>>> Hidden Secs: 61432560
    >>>>>> NA 2: 0x0
    >>>>>> NA 3: 0x800080
    >>>>>> Total Sectors: 0x0FA285C7
    >>>>>> MFT LCN: 0x0C0000
    >>>>>> MFT Mirr LCN: 0x0FA285C
    >>>>>> Clust Per FRS: 0xF6
    >>>>>> Clust Per IBlock: 0x1
    >>>>>> Volume SN: 0xF2281E1A281DDF03
    >>>>>> Checksum: 0x0
    >>>>>> Boot Flag: 0xAA55
    >>>>>> -------------------------------------------------------------------------------
    >>>>>> File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID:
    >>>>>> 0x3
    >>>>>> Jump: EB 52 90
    >>>>>> OEM Name: NTFS
    >>>>>> Bytes Per Sec: 512
    >>>>>> Sec Per Clust: 8
    >>>>>> Res Sectors: 0
    >>>>>> Zero 1: 0x0
    >>>>>> Zero 2: 0x0
    >>>>>> NA 1: 0x0
    >>>>>> Media: 0xF8
    >>>>>> Zero 3: 0x0
    >>>>>> Sec Per Track: 63
    >>>>>> Heads: 255
    >>>>>> Hidden Secs: 323741880
    >>>>>> NA 2: 0x0
    >>>>>> NA 3: 0x800080
    >>>>>> Total Sectors: 0x0FA2C488
    >>>>>> MFT LCN: 0x0C0000
    >>>>>> MFT Mirr LCN: 0x0FA2C48
    >>>>>> Clust Per FRS: 0xF6
    >>>>>> Clust Per IBlock: 0x1
    >>>>>> Volume SN: 0x7AB4DECCB4DE89D1
    >>>>>> Checksum: 0x0
    >>>>>> Boot Flag: 0xAA55
    >>>>>> -------------------------------------------------------------------------------
    >>>>>> ====================================================================
    >>>>>> MBR Partition Information (HD1):
    >>>>>> +====+====+=============+====+=============+===========+===========+
    >>>>>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
    >>>>>> | 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
    >>>>>> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>>>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
    >>>>>> +====+====+=============+====+=============+===========+===========+
    >>>>>> BOOT SECTOR INFORMATION
    >>>>>> -------------------------------------------------------------------------------
    >>>>>> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
    >>>>>> Jump: EB 52 90
    >>>>>> OEM Name: NTFS
    >>>>>> Bytes Per Sec: 512
    >>>>>> Sec Per Clust: 8
    >>>>>> Res Sectors: 0
    >>>>>> Zero 1: 0x0
    >>>>>> Zero 2: 0x0
    >>>>>> NA 1: 0x0
    >>>>>> Media: 0xF8
    >>>>>> Zero 3: 0x0
    >>>>>> Sec Per Track: 63
    >>>>>> Heads: 255
    >>>>>> Hidden Secs: 63
    >>>>>> NA 2: 0x0
    >>>>>> NA 3: 0x800080
    >>>>>> Total Sectors: 0x024C1258
    >>>>>> MFT LCN: 0x0B42FF
    >>>>>> MFT Mirr LCN: 0x03D54EA
    >>>>>> Clust Per FRS: 0xF6
    >>>>>> Clust Per IBlock: 0x1
    >>>>>> Volume SN: 0x4228D79E28D78EF3
    >>>>>> Checksum: 0x0
    >>>>>> Boot Flag: 0xAA55
    >>>>>> -------------------------------------------------------------------------------
    >>>>>> File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID:
    >>>>>> 0x2
    >>>>>> Jump: EB 52 90
    >>>>>> OEM Name: NTFS
    >>>>>> Bytes Per Sec: 512
    >>>>>> Sec Per Clust: 8
    >>>>>> Res Sectors: 0
    >>>>>> Zero 1: 0x0
    >>>>>> Zero 2: 0x0
    >>>>>> NA 1: 0x0
    >>>>>> Media: 0xF8
    >>>>>> Zero 3: 0x0
    >>>>>> Sec Per Track: 63
    >>>>>> Heads: 255
    >>>>>> Hidden Secs: 38539935
    >>>>>> NA 2: 0x0
    >>>>>> NA 3: 0x800080
    >>>>>> Total Sectors: 0x010557821
    >>>>>> MFT LCN: 0x0C0000
    >>>>>> MFT Mirr LCN: 0x01055782
    >>>>>> Clust Per FRS: 0xF6
    >>>>>> Clust Per IBlock: 0x1
    >>>>>> Volume SN: 0x7E38F7BF38F7750D
    >>>>>> Checksum: 0x0
    >>>>>> Boot Flag: 0xAA55
    >>>>>> -------------------------------------------------------------------------------
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>>>
    >>>
    >>
    >>
    >
  29. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:42714af6$0$307$cc9e4d1f@news.dial.pipex.com...
    > Walter,
    >
    > I had a look at that link. Very, very interesting! That is exactly what
    > has happened with my system. I think I'd almost be inclined to treat my
    > cloned drive like a virus after this.
    >
    > I had another look at an older version of BootItNG I had. Perhaps it's a
    > confidence thing but I wasn't sure about the fact that it creates it's own
    > boot partition, and then I had great difficulty removing it afterwards.
    > After I removed it I could no longer boot, but I may well have done
    > something wrong. Is it reasonably easy to use for people like me who may
    > be computer literate but haven't much of a clue about the intricacies of
    > XP'x boot process.

    Let me preface things by saying, I'm comfortable with using virtually any
    partitioning/boot management tool since I understand things at a rather low
    level.

    I find BING easy to use albeit a bit awkward for some things. Then again,
    it's one of the few tools that is fully functional from diskette, although
    you do have to install it to enable boot management. It lacks some of the
    fancy GUIs and frills of other tools. When I switched from Partition Magic,
    there were some GUI features that I initally missed until I realized how
    much functionality PM lacked for twice the cost. Then again I know some
    rather technically compotent people that find BING unusable.
    It need not go into it's own partition if you have an existing fat partition
    handy. Up until last summer I had BING running out of my Me instance until I
    finally blew that partition away. However by installing it in it's own
    partition you render it totally OS neutral.
    As for uninstalling it and leaving your self non-bootable, yes, that's more
    an indication of having done things incorrectly.
    Part of the problem you're going have regardless, is that you do have to be
    aware of some low level things in order to do what you want, exactly the way
    you want and I can also state that doing so is going to really adventerous.
    Yes, it's possible to do what you want, but it does require that you be
    aware of what you're doing. More in a bit...


    >
    > Would it enable me to clone, leaving both drives in situ, freely booting
    > from either, without the worry of all these partion and enumeration
    > problems?

    Sort of. There are things you need be aware of and it's going to be a PITA
    to do things exactly the way you want with any tool. Keeping multipe OS
    images on a single drive and hot booting between them is no large deal. At
    one time I had 6 different OS images on a single drive (yes 6 bootable
    primaries) I was switching between. When you introduce multiple physical
    bootable drives, things get rather complicated when you start talking NT
    kernels. 9x kernels could be fired up from any drive rather eaisly. NT
    kernels are rather picky since they enumerate the hardware differently. Yes,
    BING can make things a bit safer, but you'll have to boot twice when
    shifting from HD0 to HD1 with jumping into the BIOS in between a necessity.

    >
    > Dave

    Just so I can understand what you're thinking, exactly why do you want to
    copy the OS to a different drive and fire it up from there?

    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.
  30. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Thanks for that insight Walter. This is clearly nothing like as simple a job
    as many software vendors indicate.

    Let me put it on the line. I had an XP installation that started to become
    problematic. No real idea why, but some programs stopped working properly,
    and wouldn't reinstall. I have a lot of installed apps. Reinstalling XP is a
    breeze. Reinstalling all the apps is a complete pita.

    So I decided to do something that I used to do with ease on Win98 (xcopy or
    xxcopy) and create a clone. That's where my problems started.

    Ideally it would be nice to have another bootable XP OS so I could benchtest
    certain apps or hardware with peace of mind. However this is a secondary
    requirement, and mainly I want a security backup. But the point is, how do I
    field test my cloned OS. Obviously I don't want to try it for real in case
    there is a problem, so I figured that the obvious way would be to restore
    the image to my other SATA drive. I did then intend to just leave it there
    and use it occasionally as and when.

    Now you know what I'm aiming for, what would you suggest, and can I do it
    with Acronis 8.0 which I have?

    Many thanks.

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uT54s%23FTFHA.2840@TK2MSFTNGP10.phx.gbl...
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:42714af6$0$307$cc9e4d1f@news.dial.pipex.com...
    >> Walter,
    >>
    >> I had a look at that link. Very, very interesting! That is exactly what
    >> has happened with my system. I think I'd almost be inclined to treat my
    >> cloned drive like a virus after this.
    >>
    >> I had another look at an older version of BootItNG I had. Perhaps it's a
    >> confidence thing but I wasn't sure about the fact that it creates it's
    >> own boot partition, and then I had great difficulty removing it
    >> afterwards. After I removed it I could no longer boot, but I may well
    >> have done something wrong. Is it reasonably easy to use for people like
    >> me who may be computer literate but haven't much of a clue about the
    >> intricacies of XP'x boot process.
    >
    > Let me preface things by saying, I'm comfortable with using virtually any
    > partitioning/boot management tool since I understand things at a rather
    > low level.
    >
    > I find BING easy to use albeit a bit awkward for some things. Then again,
    > it's one of the few tools that is fully functional from diskette, although
    > you do have to install it to enable boot management. It lacks some of the
    > fancy GUIs and frills of other tools. When I switched from Partition
    > Magic, there were some GUI features that I initally missed until I
    > realized how much functionality PM lacked for twice the cost. Then again I
    > know some rather technically compotent people that find BING unusable.
    > It need not go into it's own partition if you have an existing fat
    > partition handy. Up until last summer I had BING running out of my Me
    > instance until I finally blew that partition away. However by installing
    > it in it's own partition you render it totally OS neutral.
    > As for uninstalling it and leaving your self non-bootable, yes, that's
    > more an indication of having done things incorrectly.
    > Part of the problem you're going have regardless, is that you do have to
    > be aware of some low level things in order to do what you want, exactly
    > the way you want and I can also state that doing so is going to really
    > adventerous. Yes, it's possible to do what you want, but it does require
    > that you be aware of what you're doing. More in a bit...
    >
    >
    >>
    >> Would it enable me to clone, leaving both drives in situ, freely booting
    >> from either, without the worry of all these partion and enumeration
    >> problems?
    >
    > Sort of. There are things you need be aware of and it's going to be a PITA
    > to do things exactly the way you want with any tool. Keeping multipe OS
    > images on a single drive and hot booting between them is no large deal. At
    > one time I had 6 different OS images on a single drive (yes 6 bootable
    > primaries) I was switching between. When you introduce multiple physical
    > bootable drives, things get rather complicated when you start talking NT
    > kernels. 9x kernels could be fired up from any drive rather eaisly. NT
    > kernels are rather picky since they enumerate the hardware differently.
    > Yes, BING can make things a bit safer, but you'll have to boot twice when
    > shifting from HD0 to HD1 with jumping into the BIOS in between a
    > necessity.
    >
    >>
    >> Dave
    >
    > Just so I can understand what you're thinking, exactly why do you want to
    > copy the OS to a different drive and fire it up from there?
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
  31. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:427373b0$0$364$cc9e4d1f@news.dial.pipex.com...
    > Thanks for that insight Walter. This is clearly nothing like as simple a
    > job as many software vendors indicate.

    Unfortunately that is an absolutely correct statement. There is nothing that
    makes the process 'idiot proof'. You really have to know what you're doing
    or you'll get into a mess.

    >
    > Let me put it on the line. I had an XP installation that started to become
    > problematic. No real idea why, but some programs stopped working properly,
    > and wouldn't reinstall. I have a lot of installed apps. Reinstalling XP is
    > a breeze. Reinstalling all the apps is a complete pita.

    You're preaching to the choir. :-/
    But you've excluded patch time which does vary with how long it's been since
    the last SP, whether or not you have it stored locally, etc. It took me over
    a week to load my laptop a couple of years ago. And that was then...
    I haven't clean installed me desktop since 98/SE. Migrating to XP 64b is
    going to be a hassle even once drivers and applications are available just
    due to the shear amount of 'stuff' I have installed.
    But I digress.

    >
    > So I decided to do something that I used to do with ease on Win98 (xcopy
    > or xxcopy) and create a clone. That's where my problems started.
    >
    > Ideally it would be nice to have another bootable XP OS so I could
    > benchtest certain apps or hardware with peace of mind. However this is a
    > secondary requirement, and mainly I want a security backup. But the point
    > is, how do I field test my cloned OS. Obviously I don't want to try it for
    > real in case there is a problem, so I figured that the obvious way would
    > be to restore the image to my other SATA drive. I did then intend to just
    > leave it there and use it occasionally as and when.
    >
    > Now you know what I'm aiming for, what would you suggest, and can I do it
    > with Acronis 8.0 which I have?

    With the version of Acronis you have, in short no. One of the issues I've
    found with booting an NT kernel from anything other than HD0 is that it gets
    rather interesting. I quit trying to do that during the beta of XP since it
    was down right ugly. What you can do though, with a tool that allows the
    partition table to be loaded on the fly such as BING, is run hot boot
    between multiple NT kernal images off of HD0. Generally, that's not
    problematic. In fact I have a test version of Pro 64b that I've been toying
    with. Regardless, I have one drive that is I've delegated as nothing but OS
    images. If I need to back one up, I either use BING to directly burn to
    DVD-RW or I simply image the partition to a different drive and if things go
    splat blow the image on HD0 away and replace it.

    I've since switched to using virtual machines for a lot my experimentation
    though. It's easier overall. In fact, I'm playing with a nasty I lifted off
    a client machine today that I had to identify by eyeball.


    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.
  32. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter,

    Everything that you've said so far makes sense and tallies with my
    experience. So I'll go with what you suggest and have HD0 just for OS's.

    I'm happy to do my own research on this, but I gather BootItNG (Is that
    BING?) is what you'd suggest, so I'll go with that. If I maybe create 3
    partitions on HD0, install XP on the first, followed by BootItNG, could I
    then copy clones to partitions 2 & 3 and freely boot from them? Should I
    give BootItNG it's own partition? Any obvious pitfalls I should be aware of
    when installing BootItNG? Incidentally, do you keep all your program files
    with each of your OS's?

    You've been very helpful offering all this advice. I'm sure others
    appreciate it too.

    Many thanks,

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:uetJHagTFHA.2336@TK2MSFTNGP12.phx.gbl...
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:427373b0$0$364$cc9e4d1f@news.dial.pipex.com...
    >> Thanks for that insight Walter. This is clearly nothing like as simple a
    >> job as many software vendors indicate.
    >
    > Unfortunately that is an absolutely correct statement. There is nothing
    > that makes the process 'idiot proof'. You really have to know what you're
    > doing or you'll get into a mess.
    >
    >>
    >> Let me put it on the line. I had an XP installation that started to
    >> become problematic. No real idea why, but some programs stopped working
    >> properly, and wouldn't reinstall. I have a lot of installed apps.
    >> Reinstalling XP is a breeze. Reinstalling all the apps is a complete
    >> pita.
    >
    > You're preaching to the choir. :-/
    > But you've excluded patch time which does vary with how long it's been
    > since the last SP, whether or not you have it stored locally, etc. It took
    > me over a week to load my laptop a couple of years ago. And that was
    > then...
    > I haven't clean installed me desktop since 98/SE. Migrating to XP 64b is
    > going to be a hassle even once drivers and applications are available just
    > due to the shear amount of 'stuff' I have installed.
    > But I digress.
    >
    >>
    >> So I decided to do something that I used to do with ease on Win98 (xcopy
    >> or xxcopy) and create a clone. That's where my problems started.
    >>
    >> Ideally it would be nice to have another bootable XP OS so I could
    >> benchtest certain apps or hardware with peace of mind. However this is a
    >> secondary requirement, and mainly I want a security backup. But the point
    >> is, how do I field test my cloned OS. Obviously I don't want to try it
    >> for real in case there is a problem, so I figured that the obvious way
    >> would be to restore the image to my other SATA drive. I did then intend
    >> to just leave it there and use it occasionally as and when.
    >>
    >> Now you know what I'm aiming for, what would you suggest, and can I do it
    >> with Acronis 8.0 which I have?
    >
    > With the version of Acronis you have, in short no. One of the issues I've
    > found with booting an NT kernel from anything other than HD0 is that it
    > gets rather interesting. I quit trying to do that during the beta of XP
    > since it was down right ugly. What you can do though, with a tool that
    > allows the partition table to be loaded on the fly such as BING, is run
    > hot boot between multiple NT kernal images off of HD0. Generally, that's
    > not problematic. In fact I have a test version of Pro 64b that I've been
    > toying with. Regardless, I have one drive that is I've delegated as
    > nothing but OS images. If I need to back one up, I either use BING to
    > directly burn to DVD-RW or I simply image the partition to a different
    > drive and if things go splat blow the image on HD0 away and replace it.
    >
    > I've since switched to using virtual machines for a lot my experimentation
    > though. It's easier overall. In fact, I'm playing with a nasty I lifted
    > off a client machine today that I had to identify by eyeball.
    >
    >
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
    >
  33. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:42780096$0$340$cc9e4d1f@news.dial.pipex.com...
    > Walter,
    >
    > Everything that you've said so far makes sense and tallies with my
    > experience. So I'll go with what you suggest and have HD0 just for OS's.
    >
    > I'm happy to do my own research on this, but I gather BootItNG (Is that
    > BING?) is what you'd suggest, so I'll go with that. If I maybe create 3
    > partitions on HD0, install XP on the first, followed by BootItNG, could I
    > then copy clones to partitions 2 & 3 and freely boot from them?

    That will work but there's a slight twist that can be employed with BING
    that makes it even better so that you don't have to worry about the number
    of partitions in use, just the ones that you populate into the partition
    table at any given time.

    > Should I give BootItNG it's own partition? Any obvious pitfalls I should
    > be aware of when installing BootItNG?

    By installing BING in it's own partition, which is all of 8M, you isolate it
    from OS related stuff.

    Pitfalls are going to depend on how you choose to run BING.

    The trick to making this work with the least amount of pain is to install
    BING and enable the unlimited partitions capability. This does complicate
    usage though since in this mode you have to tell it how to populate the
    partition table on each drive whenever firing up a given OS instance and
    there's not much automation in this regard. The big advantage is that you
    can fire up any NT kernel from any primary on HD0 with the same boot.ini.
    Without this feature enabled, you'd have to alter boot.ini in each OS
    instance to reflect the position of the OS instance in the partition table.

    I've got to see if I figure out an easy way to describe what needs be done,
    but the best approach may be to have you take a look at the BING support
    page and take a look at some of the tutorials (which I haven't done so I
    don't know what they contain) and see if you have any questions after that.

    > Incidentally, do you keep all your program files with each of your OS's?

    Actually I attempt to keep the data, applications and OS instances
    segregated. Unfortuantely the "All Users" heirarchy has become the common
    'dumping' ground for all applications even when overriding the default
    installation. It's bad enough that application code is still dropped in
    "program files" and/or Windows heiarchy, but still... Unfortunately MS is
    just as bad about this as other vendors, especially since they published a
    recommendation that some vendors take as gospel. Fortuantely most
    applications will allow you to store data outside of the OS partition.
    >
    > You've been very helpful offering all this advice. I'm sure others
    > appreciate it too.
    >
    > Many thanks,
    >


    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.
    http://www.dts-l.org
  34. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter

    I'll keep you posted as to how all this works out. I've looked at the
    tutorials on BING website, and they are very clear and helpful.

    >
    > The trick to making this work with the least amount of pain is to install
    > BING and enable the unlimited partitions capability.

    > This does complicate usage though since in this mode you have to tell it
    > how to populate the partition table on each drive whenever firing up a
    > given OS instance and there's not much automation in this regard.

    Hmmm what exactly is involved here? The tutorials have always opted for
    sticking with 4 primary partitions, and once set up correctly you just boot
    from the menu, so I wasn't aware of this. Do you mean that if I go for
    unlimited partitions then I will have to enter partition table info every
    time I boot to a different OS? That seems like quite a high price to pay. Or
    is it not as compicated as it sounds?


    > The big advantage is that you can fire up any NT kernel from any primary
    > on HD0 with the same boot.ini. Without this feature enabled, you'd have to
    > alter boot.ini in each OS instance to reflect the position of the OS
    > instance in the partition table.
    >

    Again, if this setting up was a one off process that would be fine. I don't
    expect to be testing OS's as a hobby or anything, so once set up not much is
    likely to change.

    Dave
  35. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:4279589c$0$385$cc9e4d1f@news.dial.pipex.com...
    > Walter
    >
    > I'll keep you posted as to how all this works out. I've looked at the
    > tutorials on BING website, and they are very clear and helpful.
    >
    >>
    >> The trick to making this work with the least amount of pain is to install
    >> BING and enable the unlimited partitions capability.
    >
    >> This does complicate usage though since in this mode you have to tell it
    >> how to populate the partition table on each drive whenever firing up a
    >> given OS instance and there's not much automation in this regard.
    >
    > Hmmm what exactly is involved here? The tutorials have always opted for
    > sticking with 4 primary partitions, and once set up correctly you just
    > boot from the menu, so I wasn't aware of this. Do you mean that if I go
    > for unlimited partitions then I will have to enter partition table info
    > every time I boot to a different OS? That seems like quite a high price to
    > pay. Or is it not as compicated as it sounds?

    It's a one time configuration per defined OS instance. The only time you'd
    need to change it is if you had a drive/partition and then only for the new
    drive/partition.

    The first time you set up an OS instance, the partition table entries on the
    right will be empty. For each physical drive hit the partition table
    position then hit the fill button. That will bring up a list of partitions
    on that physical HD. Simply select the partition you want to appear in the
    select spot and repeat for each partition slot you need to define. In this
    instance, you'd only load a single OS instance since you don't want them
    seeing each other.

    >
    >
    >> The big advantage is that you can fire up any NT kernel from any primary
    >> on HD0 with the same boot.ini. Without this feature enabled, you'd have
    >> to alter boot.ini in each OS instance to reflect the position of the OS
    >> instance in the partition table.
    >>
    >
    > Again, if this setting up was a one off process that would be fine. I
    > don't expect to be testing OS's as a hobby or anything, so once set up not
    > much is likely to change.

    Not a problem. It's set up once and change only as needed. :-)

    >
    > Dave
    >
    --
    Walter Clayton
    Any technology distinguishable from magic is insufficiently advanced.
  36. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    OK Walter, that's excellent. I'm awaiting a new drive which I'll just use
    for the OS's and I have my copy of BING ready to go.
    From what I've read so far it seems to be a phenomenally useful little prog.
    It will do everything I want.

    I'll post a follow up when it's working and let you know how it panned out.

    Thanks again,

    Dave


    "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    news:OvLpXKQUFHA.548@tk2msftngp13.phx.gbl...
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:4279589c$0$385$cc9e4d1f@news.dial.pipex.com...
    >> Walter
    >>
    >> I'll keep you posted as to how all this works out. I've looked at the
    >> tutorials on BING website, and they are very clear and helpful.
    >>
    >>>
    >>> The trick to making this work with the least amount of pain is to
    >>> install BING and enable the unlimited partitions capability.
    >>
    >>> This does complicate usage though since in this mode you have to tell it
    >>> how to populate the partition table on each drive whenever firing up a
    >>> given OS instance and there's not much automation in this regard.
    >>
    >> Hmmm what exactly is involved here? The tutorials have always opted for
    >> sticking with 4 primary partitions, and once set up correctly you just
    >> boot from the menu, so I wasn't aware of this. Do you mean that if I go
    >> for unlimited partitions then I will have to enter partition table info
    >> every time I boot to a different OS? That seems like quite a high price
    >> to pay. Or is it not as compicated as it sounds?
    >
    > It's a one time configuration per defined OS instance. The only time you'd
    > need to change it is if you had a drive/partition and then only for the
    > new drive/partition.
    >
    > The first time you set up an OS instance, the partition table entries on
    > the right will be empty. For each physical drive hit the partition table
    > position then hit the fill button. That will bring up a list of partitions
    > on that physical HD. Simply select the partition you want to appear in the
    > select spot and repeat for each partition slot you need to define. In this
    > instance, you'd only load a single OS instance since you don't want them
    > seeing each other.
    >
    >>
    >>
    >>> The big advantage is that you can fire up any NT kernel from any primary
    >>> on HD0 with the same boot.ini. Without this feature enabled, you'd have
    >>> to alter boot.ini in each OS instance to reflect the position of the OS
    >>> instance in the partition table.
    >>>
    >>
    >> Again, if this setting up was a one off process that would be fine. I
    >> don't expect to be testing OS's as a hobby or anything, so once set up
    >> not much is likely to change.
    >
    > Not a problem. It's set up once and change only as needed. :-)
    >
    >>
    >> Dave
    >>
    > --
    > Walter Clayton
    > Any technology distinguishable from magic is insufficiently advanced.
    >
  37. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter,

    Great advice - I'm very, very impressed. I have a 120GB drive which so far
    has 3 XP partitions cloned at various stages of installation. It really
    couldn't be easier using BING. I love being able to resize, and also the
    fact that the partitions are all hidden from one another is a great help.
    The website videos and tutorials make a complex job seem very
    straightforward.

    Yes, I'd give BootIt NG 5 stars and wholeheartedly recommend it to anyone.
    As you know my hassles with Acronis and Ghost were unbelievable. Yet this
    has worked perfectly, first time, and it does more than either of those
    programs.

    Thanks again!!

    Dave Cockram


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:427a6a64$0$328$cc9e4d1f@news.dial.pipex.com...
    > OK Walter, that's excellent. I'm awaiting a new drive which I'll just use
    > for the OS's and I have my copy of BING ready to go.
    > From what I've read so far it seems to be a phenomenally useful little
    > prog. It will do everything I want.
    >
    > I'll post a follow up when it's working and let you know how it panned
    > out.
    >
    > Thanks again,
    >
    > Dave
    >
    >
    > "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    > news:OvLpXKQUFHA.548@tk2msftngp13.phx.gbl...
    >>
    >> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >> news:4279589c$0$385$cc9e4d1f@news.dial.pipex.com...
    >>> Walter
    >>>
    >>> I'll keep you posted as to how all this works out. I've looked at the
    >>> tutorials on BING website, and they are very clear and helpful.
    >>>
    >>>>
    >>>> The trick to making this work with the least amount of pain is to
    >>>> install BING and enable the unlimited partitions capability.
    >>>
    >>>> This does complicate usage though since in this mode you have to tell
    >>>> it how to populate the partition table on each drive whenever firing up
    >>>> a given OS instance and there's not much automation in this regard.
    >>>
    >>> Hmmm what exactly is involved here? The tutorials have always opted for
    >>> sticking with 4 primary partitions, and once set up correctly you just
    >>> boot from the menu, so I wasn't aware of this. Do you mean that if I go
    >>> for unlimited partitions then I will have to enter partition table info
    >>> every time I boot to a different OS? That seems like quite a high price
    >>> to pay. Or is it not as compicated as it sounds?
    >>
    >> It's a one time configuration per defined OS instance. The only time
    >> you'd need to change it is if you had a drive/partition and then only for
    >> the new drive/partition.
    >>
    >> The first time you set up an OS instance, the partition table entries on
    >> the right will be empty. For each physical drive hit the partition table
    >> position then hit the fill button. That will bring up a list of
    >> partitions on that physical HD. Simply select the partition you want to
    >> appear in the select spot and repeat for each partition slot you need to
    >> define. In this instance, you'd only load a single OS instance since you
    >> don't want them seeing each other.
    >>
    >>>
    >>>
    >>>> The big advantage is that you can fire up any NT kernel from any
    >>>> primary on HD0 with the same boot.ini. Without this feature enabled,
    >>>> you'd have to alter boot.ini in each OS instance to reflect the
    >>>> position of the OS instance in the partition table.
    >>>>
    >>>
    >>> Again, if this setting up was a one off process that would be fine. I
    >>> don't expect to be testing OS's as a hobby or anything, so once set up
    >>> not much is likely to change.
    >>
    >> Not a problem. It's set up once and change only as needed. :-)
    >>
    >>>
    >>> Dave
    >>>
    >> --
    >> Walter Clayton
    >> Any technology distinguishable from magic is insufficiently advanced.
    >>
    >
    >
  38. Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (More info?)

    Walter and BING are impressionable. :o)

    --

    All the Best,
    Kelly (MS-MVP)

    Troubleshooting Windows XP
    http://www.kellys-korner-xp.com


    "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    news:427fe5fd$0$375$cc9e4d1f@news.dial.pipex.com...
    > Walter,
    >
    > Great advice - I'm very, very impressed. I have a 120GB drive which so far
    > has 3 XP partitions cloned at various stages of installation. It really
    > couldn't be easier using BING. I love being able to resize, and also the
    > fact that the partitions are all hidden from one another is a great help.
    > The website videos and tutorials make a complex job seem very
    > straightforward.
    >
    > Yes, I'd give BootIt NG 5 stars and wholeheartedly recommend it to
    > anyone. As you know my hassles with Acronis and Ghost were unbelievable.
    > Yet this has worked perfectly, first time, and it does more than either of
    > those programs.
    >
    > Thanks again!!
    >
    > Dave Cockram
    >
    >
    > "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    > news:427a6a64$0$328$cc9e4d1f@news.dial.pipex.com...
    >> OK Walter, that's excellent. I'm awaiting a new drive which I'll just use
    >> for the OS's and I have my copy of BING ready to go.
    >> From what I've read so far it seems to be a phenomenally useful little
    >> prog. It will do everything I want.
    >>
    >> I'll post a follow up when it's working and let you know how it panned
    >> out.
    >>
    >> Thanks again,
    >>
    >> Dave
    >>
    >>
    >> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
    >> news:OvLpXKQUFHA.548@tk2msftngp13.phx.gbl...
    >>>
    >>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
    >>> news:4279589c$0$385$cc9e4d1f@news.dial.pipex.com...
    >>>> Walter
    >>>>
    >>>> I'll keep you posted as to how all this works out. I've looked at the
    >>>> tutorials on BING website, and they are very clear and helpful.
    >>>>
    >>>>>
    >>>>> The trick to making this work with the least amount of pain is to
    >>>>> install BING and enable the unlimited partitions capability.
    >>>>
    >>>>> This does complicate usage though since in this mode you have to tell
    >>>>> it how to populate the partition table on each drive whenever firing
    >>>>> up a given OS instance and there's not much automation in this regard.
    >>>>
    >>>> Hmmm what exactly is involved here? The tutorials have always opted for
    >>>> sticking with 4 primary partitions, and once set up correctly you just
    >>>> boot from the menu, so I wasn't aware of this. Do you mean that if I go
    >>>> for unlimited partitions then I will have to enter partition table info
    >>>> every time I boot to a different OS? That seems like quite a high price
    >>>> to pay. Or is it not as compicated as it sounds?
    >>>
    >>> It's a one time configuration per defined OS instance. The only time
    >>> you'd need to change it is if you had a drive/partition and then only
    >>> for the new drive/partition.
    >>>
    >>> The first time you set up an OS instance, the partition table entries on
    >>> the right will be empty. For each physical drive hit the partition table
    >>> position then hit the fill button. That will bring up a list of
    >>> partitions on that physical HD. Simply select the partition you want to
    >>> appear in the select spot and repeat for each partition slot you need to
    >>> define. In this instance, you'd only load a single OS instance since you
    >>> don't want them seeing each other.
    >>>
    >>>>
    >>>>
    >>>>> The big advantage is that you can fire up any NT kernel from any
    >>>>> primary on HD0 with the same boot.ini. Without this feature enabled,
    >>>>> you'd have to alter boot.ini in each OS instance to reflect the
    >>>>> position of the OS instance in the partition table.
    >>>>>
    >>>>
    >>>> Again, if this setting up was a one off process that would be fine. I
    >>>> don't expect to be testing OS's as a hobby or anything, so once set up
    >>>> not much is likely to change.
    >>>
    >>> Not a problem. It's set up once and change only as needed. :-)
    >>>
    >>>>
    >>>> Dave
    >>>>
    >>> --
    >>> Walter Clayton
    >>> Any technology distinguishable from magic is insufficiently advanced.
    >>>
    >>
    >>
    >
    >
Ask a new question

Read More

Microsoft Maxtor Windows XP