G
Guest
Guest
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
>>> -------------------------------------------------------------------------------
>>>
>>>
>>>
>>
>
>
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
>>> -------------------------------------------------------------------------------
>>>
>>>
>>>
>>
>
>