I used Partition Magic to clone the partition containing my new Windows
XP installation. Both are on the same hard drive, and they're the only
two partitions on it. Basically, this just gives me a backup of my
system which I can use to copy back over the original if the original
(the one on Partion 1) gets corrupted. I keep Partition 2 marked
"hidden" and therefore inacessible most of the time, though I will
occasionally use BootMagic to boot into Partition 2 to copy a deleted
file or something.
This backup method worked perfectly for me for all the years I've used
it. Until now. I recently built a new computer, and as usual I
installed Windows and then all my apps and then cloned the entire
"install" onto a new partition.
But after the cloning, many of my apps needed to have their
configurations redone, and those that require "activation" need to
be RE-activated. It's as if my apps can't find the registry. Yet the
drive letter assignments all seem right, and I believe the boot.ini
files are written correctly as well. The one on partition 1 reads:
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
The one on Partition 2 is the same, except the [boot loader] line reads:
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
The problem was the same on both partitions, and the result was the same
when I wiped the drive and reinstalled everything from scratch.
Needless to say, I can't figure out the reason for this behavior. The
only difference between this machine and all the other PCs I've built is
that this is the first one that has SATA hard drives instead of IDE; the
only IDE device on this system is an HP DVD+/-R recorder. Can anyone
suggest what I might have overlooked, or what I can do to get my apps
able to read their config info again?
Dennis Wilson wrote:
> I used Partition Magic to clone the partition containing my new Windows
> XP installation. Both are on the same hard drive, and they're the only
> two partitions on it. Basically, this just gives me a backup of my
> system which I can use to copy back over the original if the original
> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
> "hidden" and therefore inacessible most of the time, though I will
> occasionally use BootMagic to boot into Partition 2 to copy a deleted
> file or something.
>
> This backup method worked perfectly for me for all the years I've used
> it. Until now. I recently built a new computer, and as usual I
> installed Windows and then all my apps and then cloned the entire
> "install" onto a new partition.
>
> But after the cloning, many of my apps needed to have their
> configurations redone, and those that require "activation" need to
> be RE-activated. It's as if my apps can't find the registry. Yet the
> drive letter assignments all seem right, and I believe the boot.ini
> files are written correctly as well. The one on partition 1 reads:
>
> [boot loader]
> timeout=0
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>
> The one on Partition 2 is the same, except the [boot loader] line reads:
>
> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>
> The problem was the same on both partitions, and the result was the same
> when I wiped the drive and reinstalled everything from scratch.
>
> Needless to say, I can't figure out the reason for this behavior. The
> only difference between this machine and all the other PCs I've built is
> that this is the first one that has SATA hard drives instead of IDE; the
> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
> suggest what I might have overlooked, or what I can do to get my apps
> able to read their config info again?
>
> Thanks.
> ** Posted from http://www.teranews.com **
Has the cloned installation retained the same drive letter as the
parent? I suspect that it hasn't and that this is the cause of your
problems. Boot to the parent installation and at the Command Prompt issue:
set systemroot
Then boot to the clone and issue the same command, both should return
the same drive letter, if not that is the cause of your problems.
John
Dennis Wilson wrote:
> I used Partition Magic to clone the partition containing my new Windows
> XP installation. Both are on the same hard drive, and they're the only
> two partitions on it. Basically, this just gives me a backup of my
> system which I can use to copy back over the original if the original
> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
> "hidden" and therefore inacessible most of the time, though I will
> occasionally use BootMagic to boot into Partition 2 to copy a deleted
> file or something.
>
> This backup method worked perfectly for me for all the years I've used
> it. Until now. I recently built a new computer, and as usual I
> installed Windows and then all my apps and then cloned the entire
> "install" onto a new partition.
>
> But after the cloning, many of my apps needed to have their
> configurations redone, and those that require "activation" need to
> be RE-activated. It's as if my apps can't find the registry. Yet the
> drive letter assignments all seem right, and I believe the boot.ini
> files are written correctly as well. The one on partition 1 reads:
>
> [boot loader]
> timeout=0
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>
> The one on Partition 2 is the same, except the [boot loader] line reads:
>
> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>
> The problem was the same on both partitions, and the result was the same
> when I wiped the drive and reinstalled everything from scratch.
>
> Needless to say, I can't figure out the reason for this behavior. The
> only difference between this machine and all the other PCs I've built is
> that this is the first one that has SATA hard drives instead of IDE; the
> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
> suggest what I might have overlooked, or what I can do to get my apps
> able to read their config info again?
>
> Thanks.
> ** Posted from http://www.teranews.com **
Of what importance is the drive letter that a Windows OS uses
while it is running? As long as there are no shorcuts which include
the name of a partition, there will be no problem. Are you
assuming that there are such shortcuts?
*TimDaniels*
"John John (MVP)" wrote:
> Has the cloned installation retained the same drive letter as the parent? I
> suspect that it hasn't and that this is the cause of your problems. Boot to
> the parent installation and at the Command
> Prompt issue:
>
> set systemroot
>
> Then boot to the clone and issue the same command, both should
> return the same drive letter, if not that is the cause of your problems.
>
> John
>
> Dennis Wilson wrote:
>
>> I used Partition Magic to clone the partition containing my new Windows
>> XP installation. Both are on the same hard drive, and they're the only
>> two partitions on it. Basically, this just gives me a backup of my
>> system which I can use to copy back over the original if the original
>> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
>> "hidden" and therefore inacessible most of the time, though I will
>> occasionally use BootMagic to boot into Partition 2 to copy a deleted
>> file or something. This backup method worked perfectly for me for all the
>> years I've used
>> it. Until now. I recently built a new computer, and as usual I
>> installed Windows and then all my apps and then cloned the entire
>> "install" onto a new partition. But after the cloning, many of my apps needed
>> to have their
>> configurations redone, and those that require "activation" need to
>> be RE-activated. It's as if my apps can't find the registry. Yet the
>> drive letter assignments all seem right, and I believe the boot.ini
>> files are written correctly as well. The one on partition 1 reads: [boot
>> loader]
>> timeout=0
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>
>> The one on Partition 2 is the same, except the [boot loader] line reads:
>>
>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>
>> The problem was the same on both partitions, and the result was the same
>> when I wiped the drive and reinstalled everything from scratch. Needless to
>> say, I can't figure out the reason for this behavior. The
>> only difference between this machine and all the other PCs I've built is
>> that this is the first one that has SATA hard drives instead of IDE; the
>> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>> suggest what I might have overlooked, or what I can do to get my apps able to
>> read their config info again?
>>
>> Thanks.
>> ** Posted from http://www.teranews.com **
Timothy Daniels wrote:
> Of what importance is the drive letter that a Windows OS uses
> while it is running? As long as there are no shorcuts which include
> the name of a partition, there will be no problem. Are you
> assuming that there are such shortcuts?
>
> *TimDaniels*
>
> "John John (MVP)" wrote:
>> Has the cloned installation retained the same drive letter as the parent? I
>> suspect that it hasn't and that this is the cause of your problems. Boot to
>> the parent installation and at the Command
>> Prompt issue:
>>
>> set systemroot
>>
>> Then boot to the clone and issue the same command, both should
>> return the same drive letter, if not that is the cause of your problems.
>>
>> John
>>
>> Dennis Wilson wrote:
>>
>>> I used Partition Magic to clone the partition containing my new Windows
>>> XP installation. Both are on the same hard drive, and they're the only
>>> two partitions on it. Basically, this just gives me a backup of my
>>> system which I can use to copy back over the original if the original
>>> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
>>> "hidden" and therefore inacessible most of the time, though I will
>>> occasionally use BootMagic to boot into Partition 2 to copy a deleted
>>> file or something. This backup method worked perfectly for me for all the
>>> years I've used
>>> it. Until now. I recently built a new computer, and as usual I
>>> installed Windows and then all my apps and then cloned the entire
>>> "install" onto a new partition. But after the cloning, many of my apps needed
>>> to have their
>>> configurations redone, and those that require "activation" need to
>>> be RE-activated. It's as if my apps can't find the registry. Yet the
>>> drive letter assignments all seem right, and I believe the boot.ini
>>> files are written correctly as well. The one on partition 1 reads: [boot
>>> loader]
>>> timeout=0
>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>>> [operating systems]
>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>>
>>> The one on Partition 2 is the same, except the [boot loader] line reads:
>>>
>>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>>
>>> The problem was the same on both partitions, and the result was the same
>>> when I wiped the drive and reinstalled everything from scratch. Needless to
>>> say, I can't figure out the reason for this behavior. The
>>> only difference between this machine and all the other PCs I've built is
>>> that this is the first one that has SATA hard drives instead of IDE; the
>>> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>>> suggest what I might have overlooked, or what I can do to get my apps able to
>>> read their config info again?
>>>
>>> Thanks.
>>> ** Posted from http://www.teranews.com **
>
>
Oh HO, my friend. The drive letter is in many, many places in the
registry. If you clone something from C: and it ends up on D: or
anything other than C:, Windows is going to choke because many things
use the registry to find out where things are stored.
How is something "cloned from C:" going to "end up on D:"?
*TimDaniels*
"Hula Baloo" wrote:
> Oh HO, my friend. The drive letter is in many, many places in the registry.
> If you clone something from C: and it ends up on D: or anything other than C:,
> Windows is going to choke because many things use the registry to find out
> where things are stored.
>
> Timothy Daniels wrote:
>> Of what importance is the drive letter that a Windows OS uses
>> while it is running? As long as there are no shorcuts which include
>> the name of a partition, there will be no problem. Are you
>> assuming that there are such shortcuts?
>>
>> *TimDaniels*
>>
>> "John John (MVP)" wrote:
>>> Has the cloned installation retained the same drive letter as the parent? I
>>> suspect that it hasn't and that this is the cause of your problems. Boot to
>>> the parent installation and at the Command
>>> Prompt issue:
>>>
>>> set systemroot
>>>
>>> Then boot to the clone and issue the same command, both should
>>> return the same drive letter, if not that is the cause of your problems.
>>>
>>> John
>>>
>>> Dennis Wilson wrote:
>>>
>>>> I used Partition Magic to clone the partition containing my new Windows
>>>> XP installation. Both are on the same hard drive, and they're the only
>>>> two partitions on it. Basically, this just gives me a backup of my
>>>> system which I can use to copy back over the original if the original
>>>> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
>>>> "hidden" and therefore inacessible most of the time, though I will
>>>> occasionally use BootMagic to boot into Partition 2 to copy a deleted
>>>> file or something. This backup method worked perfectly for me for all the
>>>> years I've used
>>>> it. Until now. I recently built a new computer, and as usual I
>>>> installed Windows and then all my apps and then cloned the entire
>>>> "install" onto a new partition. But after the cloning, many of my apps
>>>> needed to have their
>>>> configurations redone, and those that require "activation" need to
>>>> be RE-activated. It's as if my apps can't find the registry. Yet the
>>>> drive letter assignments all seem right, and I believe the boot.ini
>>>> files are written correctly as well. The one on partition 1 reads: [boot
>>>> loader]
>>>> timeout=0
>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>>>> [operating systems]
>>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>>>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>>>
>>>> The one on Partition 2 is the same, except the [boot loader] line reads:
>>>>
>>>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>>>
>>>> The problem was the same on both partitions, and the result was the same
>>>> when I wiped the drive and reinstalled everything from scratch. Needless to
>>>> say, I can't figure out the reason for this behavior. The
>>>> only difference between this machine and all the other PCs I've built is
>>>> that this is the first one that has SATA hard drives instead of IDE; the
>>>> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>>>> suggest what I might have overlooked, or what I can do to get my apps able
>>>> to read their config info again?
>>>>
>>>> Thanks.
>>>> ** Posted from http://www.teranews.com **
>>
>>
If he cloned an installation residing on drive "C" to another partition
on the disk and if the clone adopts another drive letter when it boots,
lets say drive "D" for example, then there will be serious problems!
The Windows installation must *always* retain the drive letter onto
which it was installed, if your Windows installation is installed on
"C:" do a search in your registry for C: and the importance of
maintaining the installation drive letter will become clearly apparent,
shortcuts will be the least of your problems if the Windows volume is
assigned a different drive letter!
John
Timothy Daniels wrote:
> Of what importance is the drive letter that a Windows OS uses
> while it is running? As long as there are no shorcuts which include
> the name of a partition, there will be no problem. Are you
> assuming that there are such shortcuts?
>
> *TimDaniels*
>
> "John John (MVP)" wrote:
>
>>Has the cloned installation retained the same drive letter as the parent? I
>>suspect that it hasn't and that this is the cause of your problems. Boot to
>>the parent installation and at the Command
>>Prompt issue:
>>
>>set systemroot
>>
>>Then boot to the clone and issue the same command, both should
>>return the same drive letter, if not that is the cause of your problems.
>>
>>John
>>
>>Dennis Wilson wrote:
>>
>>
>>>I used Partition Magic to clone the partition containing my new Windows
>>>XP installation. Both are on the same hard drive, and they're the only
>>>two partitions on it. Basically, this just gives me a backup of my
>>>system which I can use to copy back over the original if the original
>>>(the one on Partion 1) gets corrupted. I keep Partition 2 marked
>>>"hidden" and therefore inacessible most of the time, though I will
>>>occasionally use BootMagic to boot into Partition 2 to copy a deleted
>>>file or something. This backup method worked perfectly for me for all the
>>>years I've used
>>>it. Until now. I recently built a new computer, and as usual I
>>>installed Windows and then all my apps and then cloned the entire
>>>"install" onto a new partition. But after the cloning, many of my apps needed
>>>to have their
>>>configurations redone, and those that require "activation" need to
>>>be RE-activated. It's as if my apps can't find the registry. Yet the
>>>drive letter assignments all seem right, and I believe the boot.ini
>>>files are written correctly as well. The one on partition 1 reads: [boot
>>>loader]
>>> timeout=0
>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>>> [operating systems]
>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>>
>>>The one on Partition 2 is the same, except the [boot loader] line reads:
>>>
>>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>>
>>>The problem was the same on both partitions, and the result was the same
>>>when I wiped the drive and reinstalled everything from scratch. Needless to
>>>say, I can't figure out the reason for this behavior. The
>>>only difference between this machine and all the other PCs I've built is
>>>that this is the first one that has SATA hard drives instead of IDE; the
>>>only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>>>suggest what I might have overlooked, or what I can do to get my apps able to
>>>read their config info again?
>>>
>>>Thanks.
>>>** Posted from http://www.teranews.com **
>
>
>
It's the same kind of thing that can sometimes happen when the parent
drive is left plugged in when the clone is booted for the first time,
you already know all of that, Tim. The problem may be more difficult to
circumvent when cloning to other partitions on the same disk.
John
Timothy Daniels wrote:
> How is something "cloned from C:" going to "end up on D:"?
>
> *TimDaniels*
>
> "Hula Baloo" wrote:
>
>> Oh HO, my friend. The drive letter is in many, many places in the registry.
>>If you clone something from C: and it ends up on D: or anything other than C:,
>>Windows is going to choke because many things use the registry to find out
>>where things are stored.
>>
>>Timothy Daniels wrote:
>>
>>>Of what importance is the drive letter that a Windows OS uses
>>>while it is running? As long as there are no shorcuts which include
>>>the name of a partition, there will be no problem. Are you
>>>assuming that there are such shortcuts?
>>>
>>>*TimDaniels*
>>>
>>>"John John (MVP)" wrote:
>>>
>>>>Has the cloned installation retained the same drive letter as the parent? I
>>>>suspect that it hasn't and that this is the cause of your problems. Boot to
>>>>the parent installation and at the Command
>>>>Prompt issue:
>>>>
>>>>set systemroot
>>>>
>>>>Then boot to the clone and issue the same command, both should
>>>>return the same drive letter, if not that is the cause of your problems.
>>>>
>>>>John
>>>>
>>>>Dennis Wilson wrote:
>>>>
>>>>
>>>>>I used Partition Magic to clone the partition containing my new Windows
>>>>>XP installation. Both are on the same hard drive, and they're the only
>>>>>two partitions on it. Basically, this just gives me a backup of my
>>>>>system which I can use to copy back over the original if the original
>>>>>(the one on Partion 1) gets corrupted. I keep Partition 2 marked
>>>>>"hidden" and therefore inacessible most of the time, though I will
>>>>>occasionally use BootMagic to boot into Partition 2 to copy a deleted
>>>>>file or something. This backup method worked perfectly for me for all the
>>>>>years I've used
>>>>>it. Until now. I recently built a new computer, and as usual I
>>>>>installed Windows and then all my apps and then cloned the entire
>>>>>"install" onto a new partition. But after the cloning, many of my apps
>>>>>needed to have their
>>>>>configurations redone, and those that require "activation" need to
>>>>>be RE-activated. It's as if my apps can't find the registry. Yet the
>>>>>drive letter assignments all seem right, and I believe the boot.ini
>>>>>files are written correctly as well. The one on partition 1 reads: [boot
>>>>>loader]
>>>>> timeout=0
>>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>>>>> [operating systems]
>>>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>>>>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>>>>
>>>>>The one on Partition 2 is the same, except the [boot loader] line reads:
>>>>>
>>>>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>>>>
>>>>>The problem was the same on both partitions, and the result was the same
>>>>>when I wiped the drive and reinstalled everything from scratch. Needless to
>>>>>say, I can't figure out the reason for this behavior. The
>>>>>only difference between this machine and all the other PCs I've built is
>>>>>that this is the first one that has SATA hard drives instead of IDE; the
>>>>>only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>>>>>suggest what I might have overlooked, or what I can do to get my apps able
>>>>>to read their config info again?
>>>>>
>>>>>Thanks.
>>>>>** Posted from http://www.teranews.com **
>>>
>>>
>
>
When restoring a "Clone" you have the option of restoring to the original
loction (C) or an alternate (D).
Any good backup utility will not let you set as the target the same drive
that contains the partition your backing up or cloning - or at least warn
you that it is not advisable .
Note the following from the original post: "...use BootMagic to boot into
Partition 2 to copy a deleted file or something. ..." and from boot.ini "...
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Window s XP 1"
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"...."
Clones are usually compressed images - recovering individual files requires
the clone utility or mounting the image via a virtual HD -not BootMagic .
The boot.ini - and use of BootMagic - indicate a dual boot scene - can
"cloning" with Partition Magic create a dual boot setup or is it possible
the first partition was copied and not cloned?
"Timothy Daniels" <NoSpam@SpamMeNot.com> wrote in message
news:e9K7Ywc9IHA.5928@TK2MSFTNGP05.phx.gbl...
> How is something "cloned from C:" going to "end up on D:"?
>
> *TimDaniels*
>
> "Hula Baloo" wrote:
>> Oh HO, my friend. The drive letter is in many, many places in the
>> registry. If you clone something from C: and it ends up on D: or anything
>> other than C:, Windows is going to choke because many things use the
>> registry to find out where things are stored.
>>
>> Timothy Daniels wrote:
>>> Of what importance is the drive letter that a Windows OS uses
>>> while it is running? As long as there are no shorcuts which include
>>> the name of a partition, there will be no problem. Are you
>>> assuming that there are such shortcuts?
>>>
>>> *TimDaniels*
>>>
>>> "John John (MVP)" wrote:
>>>> Has the cloned installation retained the same drive letter as the
>>>> parent? I suspect that it hasn't and that this is the cause of your
>>>> problems. Boot to the parent installation and at the Command
>>>> Prompt issue:
>>>>
>>>> set systemroot
>>>>
>>>> Then boot to the clone and issue the same command, both should
>>>> return the same drive letter, if not that is the cause of your
>>>> problems.
>>>>
>>>> John
>>>>
>>>> Dennis Wilson wrote:
>>>>
>>>>> I used Partition Magic to clone the partition containing my new
>>>>> Windows
>>>>> XP installation. Both are on the same hard drive, and they're the
>>>>> only
>>>>> two partitions on it. Basically, this just gives me a backup of my
>>>>> system which I can use to copy back over the original if the original
>>>>> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
>>>>> "hidden" and therefore inacessible most of the time, though I will
>>>>> occasionally use BootMagic to boot into Partition 2 to copy a deleted
>>>>> file or something. This backup method worked perfectly for me for all
>>>>> the years I've used
>>>>> it. Until now. I recently built a new computer, and as usual I
>>>>> installed Windows and then all my apps and then cloned the entire
>>>>> "install" onto a new partition. But after the cloning, many of my apps
>>>>> needed to have their
>>>>> configurations redone, and those that require "activation" need to
>>>>> be RE-activated. It's as if my apps can't find the registry. Yet the
>>>>> drive letter assignments all seem right, and I believe the boot.ini
>>>>> files are written correctly as well. The one on partition 1 reads:
>>>>> [boot loader]
>>>>> timeout=0
>>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>>>>> [operating systems]
>>>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>>>>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>>>>
>>>>> The one on Partition 2 is the same, except the [boot loader] line
>>>>> reads:
>>>>>
>>>>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>>>>
>>>>> The problem was the same on both partitions, and the result was the
>>>>> same
>>>>> when I wiped the drive and reinstalled everything from scratch.
>>>>> Needless to say, I can't figure out the reason for this behavior. The
>>>>> only difference between this machine and all the other PCs I've built
>>>>> is
>>>>> that this is the first one that has SATA hard drives instead of IDE;
>>>>> the
>>>>> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>>>>> suggest what I might have overlooked, or what I can do to get my apps
>>>>> able to read their config info again?
>>>>>
>>>>> Thanks.
>>>>> ** Posted from http://www.teranews.com **
>>>
>>>
>
>
In most NGs, perhaps most forums as well, "clone" refers to an
exact byte-for-byte copy of the original partition, and it resides
on a hard drive in the same bootable form as its "parent" OS.
An "image" refers to a *file* that contains all the information
necessary to rebuild a replica of the original partition. Because
an image is just a data file, it can be compressed using various
algorithms and put on something other that a hard drive storage
medium (such as CDs/DVDs/USB "thumb" drives/etc.), but it
requires the extra step of "restoration" to return it to a bootable
form on a hard drive. Beacause a clone is an exact copy of all
that is in a partition - even in the registry, in the case of a Windows
OS - I can't see how that copy would have its registry contents
changed so that it would thereafter refer to its own partition by
any other letter name than that which its "parent" OS had. If
does, indeed, occasionally happen, it's a rare and perhaps
intended occurrence.
The scenario you hypothesized involves an *image* file and its
restoration, not the making of a clone. I know that several of the
commercial backup utilities refer to their images as "clones", but
the industry has no accepted standards of nomenclature, probably
partially because many of the utilities blur the distinction between
the two forms of backup by enabling incremental backups to a
clone - previously just doable with an image file.
*TimDaniels*
"AJR" wrote:
> When restoring a "Clone" you have the option of restoring to the original
> loction (C) or an alternate (D).
>
> Any good backup utility will not let you set as the target the same drive that
> contains the partition your backing up or cloning - or at least warn you that
> it is not advisable .
>
> Note the following from the original post: "...use BootMagic to boot into
> Partition 2 to copy a deleted file or something. ..." and from boot.ini "...
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Window s XP 1"
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"...."
>
> Clones are usually compressed images - recovering individual files requires
> the clone utility or mounting the image via a virtual HD -not BootMagic .
>
> The boot.ini - and use of BootMagic - indicate a dual boot scene - can
> "cloning" with Partition Magic create a dual boot setup or is it possible the
> first partition was copied and not cloned?
>
> "Timothy Daniels" wrote:
>> How is something "cloned from C:" going to "end up on D:"?
>>
>> *TimDaniels*
>>
>> "Hula Baloo" wrote:
>>> Oh HO, my friend. The drive letter is in many, many places in the
>>> registry. If you clone something from C: and it ends up on D: or anything
>>> other than C:, Windows is going to choke because many things use the
>>> registry to find out where things are stored.
>>>
>>> Timothy Daniels wrote:
>>>> Of what importance is the drive letter that a Windows OS uses
>>>> while it is running? As long as there are no shorcuts which include
>>>> the name of a partition, there will be no problem. Are you
>>>> assuming that there are such shortcuts?
>>>>
>>>> *TimDaniels*
>>>>
>>>> "John John (MVP)" wrote:
>>>>> Has the cloned installation retained the same drive letter as the parent?
>>>>> I suspect that it hasn't and that this is the cause of your problems.
>>>>> Boot to the parent installation and at the Command
>>>>> Prompt issue:
>>>>>
>>>>> set systemroot
>>>>>
>>>>> Then boot to the clone and issue the same command, both should
>>>>> return the same drive letter, if not that is the cause of your problems.
>>>>>
>>>>> John
>>>>>
>>>>> Dennis Wilson wrote:
>>>>>
>>>>>> I used Partition Magic to clone the partition containing my new Windows
>>>>>> XP installation. Both are on the same hard drive, and they're the only
>>>>>> two partitions on it. Basically, this just gives me a backup of my
>>>>>> system which I can use to copy back over the original if the original
>>>>>> (the one on Partion 1) gets corrupted. I keep Partition 2 marked
>>>>>> "hidden" and therefore inacessible most of the time, though I will
>>>>>> occasionally use BootMagic to boot into Partition 2 to copy a deleted
>>>>>> file or something. This backup method worked perfectly for me for all the
>>>>>> years I've used
>>>>>> it. Until now. I recently built a new computer, and as usual I
>>>>>> installed Windows and then all my apps and then cloned the entire
>>>>>> "install" onto a new partition. But after the cloning, many of my apps
>>>>>> needed to have their
>>>>>> configurations redone, and those that require "activation" need to
>>>>>> be RE-activated. It's as if my apps can't find the registry. Yet the
>>>>>> drive letter assignments all seem right, and I believe the boot.ini
>>>>>> files are written correctly as well. The one on partition 1 reads: [boot
>>>>>> loader]
>>>>>> timeout=0
>>>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
>>>>>> [operating systems]
>>>>>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP 1"
>>>>>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP 2"
>>>>>>
>>>>>> The one on Partition 2 is the same, except the [boot loader] line reads:
>>>>>>
>>>>>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
>>>>>>
>>>>>> The problem was the same on both partitions, and the result was the same
>>>>>> when I wiped the drive and reinstalled everything from scratch. Needless
>>>>>> to say, I can't figure out the reason for this behavior. The
>>>>>> only difference between this machine and all the other PCs I've built is
>>>>>> that this is the first one that has SATA hard drives instead of IDE; the
>>>>>> only IDE device on this system is an HP DVD+/-R recorder. Can anyone
>>>>>> suggest what I might have overlooked, or what I can do to get my apps
>>>>>> able to read their config info again?
>>>>>>
>>>>>> Thanks.
>>>>>> ** Posted from http://www.teranews.com **
>>>>
>>>>
>>
>>
>
>
Programs not working right after cloning 
Linear Mode
