Cloning problems

I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:. THIS HAS
BEEN WORKING FOR A YEAR or so. I image backup often, but clone only
when I happen to think about it. This week I plugged the clone drive's
power cable in (it resides in my tower in it's own rack space). When I
initiated MaxBlast it hung when it was analyzing the clone drive d:.
Tried xxclone, it also hung. I found that an Avast antivirus scan
would hang at 5% complete. When I disconnected the clone drive and
booted these problems disappear. I thought to delete d:'s partition
using Partition Magic 7 - it hung when I attempted it. Likewise XP's
Computer Management hangs when I attempt to delete d:'s partition.
It's almost like it thinks the d: drive is part of the operating
system. I have a Knoppix Adrianne dvd that I boot sometimes to delete
troublesome files. I booted it but couldn't figure out how to delete
a partition with it.
Anyone know what is going on with this? Any way to delete the clone
drive partition outside Windows XP? (it's an NTFS partition).

John B. Smith crasso verizon.net wrote:

I'm using WindowsXP. I back up by using an imaging program on my
C; drive. I also use a cloning drive.

In other words... A drive to keep a copy of another drive.

It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor
MaxBlast to clone the c: drive to this extra drive. When I boot
with both of these drives plugged in, the cloned drive comes up
as d:. THIS HAS BEEN WORKING FOR A YEAR or so.

We should assume that "THIS HAS BEEN WORKING FOR A YEAR" is your
name of the copy.

I image backup often, but clone only when I happen to think
about it. This week I plugged the clone drive's power cable in
(it resides in my tower in it's own rack space). When I
initiated MaxBlast it hung when it was analyzing the clone drive
d:. Tried xxclone, it also hung. I found that an Avast antivirus
scan would hang at 5% complete. When I disconnected the clone
drive and booted these problems disappear. I thought to delete
d:'s partition using Partition Magic 7 -

PartitionMagic is obsolete.

Apparently... What worked for you before does not work now, now
the clone drive messes up your system.

Forget about using more than one type of backup. You're making
things more complex than they have to be. First, make sure that
any important data is backed up redundantly. Then, use a free copy
of Macrium Reflect to make compressed images of your Windows C
drive to another drive. Besides the fact that it will not mess up
your ability to boot into Windows, the compressed image is also
browsable from within Windows. Copies are made quickly from within
Windows. Restores require the boot CD and take a while, but
restores should be rare.
--














it hung when I attempted it. Likewise XP's Computer Management
hangs when I attempt to delete d:'s partition. It's almost like
it thinks the d: drive is part of the operating system. I have a
Knoppix Adrianne dvd that I boot sometimes to delete troublesome
files. I booted it but couldn't figure out how to delete a
partition with it. Anyone know what is going on with this? Any
way to delete the clone drive partition outside Windows XP?
(it's an NTFS partition).

John B. Smith wrote:
I'm using WindowsXP. I back up by using an imaging program on my C;
drive.

This week I plugged the clone drive's power cable in (it resides in
my tower in it's own rack space). When I initiated MaxBlast it hung
when it was analyzing the clone drive d:.

I have a Knoppix Adrianne dvd that I boot sometimes to delete
troublesome files. I booted it but couldn't figure out how to delete
a partition with it.

If the Knoppix and its ware/interface isn't to your liking, boot another
different linux live CD/DVD. Some of them are specialized for just this
kind of situation.


--
Mike Easter

"John B. Smith" wrote in message
...
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:.


snip


that's your mistake

once a drive is cloned...
the clone *must* be disconnected and you need to boot with it ...

if you leave it in place and reboot after the cloning process it will be
assigned the wrong drive letter

"philo" wrote:

"John B. Smith" wrote in message ...
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:.


snip


that's your mistake

once a drive is cloned...
the clone *must* be disconnected and you need to boot with it ...

if you leave it in place and reboot after the cloning process it will be assigned the wrong drive letter


I think you meant that the *original* should be disconnected
and the clone be allowed to boot alone so that it doesn't see its
"parent" OS when it boots up for the first time. Thereafter, the
two OSes can be allowed to see the other when one or the
other boots up

*TimDaniels*

"Timothy Daniels" wrote in message
m...
"philo" wrote:

"John B. Smith" wrote in message
...
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:.


snip


that's your mistake

once a drive is cloned...
the clone *must* be disconnected and you need to boot with it ...

if you leave it in place and reboot after the cloning process it will be
assigned the wrong drive letter


I think you meant that the *original* should be disconnected
and the clone be allowed to boot alone so that it doesn't see its
"parent" OS when it boots up for the first time. Thereafter, the
two OSes can be allowed to see the other when one or the
other boots up

*TimDaniels*



Yes...

John B. Smith wrote:
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:. THIS HAS
BEEN WORKING FOR A YEAR or so. I image backup often, but clone only
when I happen to think about it. This week I plugged the clone drive's
power cable in (it resides in my tower in it's own rack space). When I
initiated MaxBlast it hung when it was analyzing the clone drive d:.
Tried xxclone, it also hung. I found that an Avast antivirus scan
would hang at 5% complete. When I disconnected the clone drive and
booted these problems disappear. I thought to delete d:'s partition
using Partition Magic 7 - it hung when I attempted it. Likewise XP's
Computer Management hangs when I attempt to delete d:'s partition.
It's almost like it thinks the d: drive is part of the operating
system. I have a Knoppix Adrianne dvd that I boot sometimes to delete
troublesome files. I booted it but couldn't figure out how to delete
a partition with it.
Anyone know what is going on with this? Any way to delete the clone
drive partition outside Windows XP? (it's an NTFS partition).

NEVER EVER PUT THE CLONED DRIVE IN AS DRIVE D!!!!!!!!!
Xp keeps track of the drive letter, so, when you later
use it as main drive, it is still D:.
I had to r4e-do the clone, to make it work.
So, clone, then remove that drive and store it.
Dont even peek at it using xp, as long as it sits as second drive.

Timothy Daniels wrote:
"philo" wrote:
"John B. Smith" wrote in message ...
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:.

snip


that's your mistake

once a drive is cloned...
the clone *must* be disconnected and you need to boot with it ...

if you leave it in place and reboot after the cloning process it will be assigned the wrong drive letter


I think you meant that the *original* should be disconnected
and the clone be allowed to boot alone so that it doesn't see its
"parent" OS when it boots up for the first time. Thereafter, the
two OSes can be allowed to see the other when one or the
other boots up

*TimDaniels*


No, after cloning, both drives are "DRIVE C".
Take a peek with XP at the second drive and it is no longer drive c.
So, after cloning, remove it and use it only a primary drive.
Never have both drives in the machine, except when cloning.

"Sjouke Burry" wrote:
Timothy Daniels wrote:
"philo" wrote:
"John B. Smith" wrote in message ...
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:.

snip


that's your mistake

once a drive is cloned...
the clone *must* be disconnected and you need to boot with it ...

if you leave it in place and reboot after the cloning process it will be assigned the wrong drive letter


I think you meant that the *original* should be disconnected
and the clone be allowed to boot alone so that it doesn't see its
"parent" OS when it boots up for the first time. Thereafter, the
two OSes can be allowed to see the other when one or the
other boots up

*TimDaniels*
No, after cloning, both drives are "DRIVE C".
Take a peek with XP at the second drive and it is no longer drive c.
So, after cloning, remove it and use it only a primary drive.
Never have both drives in the machine, except when cloning.


Both OSes think they are on "C:", but remember that only one
OS runs at a time, and when running and thinking that it is on "C:"
drive, the OS refers to other drives with some other letter. I run
XP as well, and this works perfectly well - as long as there are no
shortcuts (i.e. pathnames) that refer to another drive besides the
local drive. As a matter of fact, I have several XP clones on various
partitions scattered over 2 or 3 drives, at times, when they can all
"see" each other, and there is no confusion among them - each OS
clone, when running, refers to its own drive by the same letter that
the original OS's drive had when the clone was made. Of course
it does - it's a clone! The other clones which are not running are
just data (not running OSes) and they don't care *what* their
drives are called.

*TimDaniels*

"Sjouke Burry" wrote:
John B. Smith wrote:
I'm using WindowsXP. I back up by using an imaging program on my C;
drive. Being a belt-and-suspenders man, I also use a cloning drive.
It's a SATA 80gig Seagate, same as my C: drive. I use Maxtor MaxBlast
to clone the c: drive to this extra drive. When I boot with both of
these drives plugged in, the cloned drive comes up as d:. THIS HAS
BEEN WORKING FOR A YEAR or so. I image backup often, but clone only
when I happen to think about it. This week I plugged the clone drive's
power cable in (it resides in my tower in it's own rack space). When I
initiated MaxBlast it hung when it was analyzing the clone drive d:.
Tried xxclone, it also hung. I found that an Avast antivirus scan
would hang at 5% complete. When I disconnected the clone drive and
booted these problems disappear. I thought to delete d:'s partition
using Partition Magic 7 - it hung when I attempted it. Likewise XP's
Computer Management hangs when I attempt to delete d:'s partition.
It's almost like it thinks the d: drive is part of the operating
system. I have a Knoppix Adrianne dvd that I boot sometimes to delete
troublesome files. I booted it but couldn't figure out how to delete
a partition with it.
Anyone know what is going on with this? Any way to delete the clone
drive partition outside Windows XP? (it's an NTFS partition).

NEVER EVER PUT THE CLONED DRIVE IN AS DRIVE D!!!!!!!!!
Xp keeps track of the drive letter, so, when you later
use it as main drive, it is still D:.
I had to r4e-do the clone, to make it work.
So, clone, then remove that drive and store it.
Dont even peek at it using xp, as long as it sits as second drive.


That's too restrictive. As long as the clone is alone (not able to
"see" its parent OS) when it boots up for *the first time*, both the
parent and the clone can be allowed to "see" each other. The OS
which is not running will just be seen as data. You can even boot
up the parent to check the clone's file structure and data before the
clone has ever been booted. But when you get around to booting
the clone *for the first time*, its parent should not be visible to it.
Can it be allowed to see other clones that were made from the
same parent? I haven't seen any problems from that happening,
but I don't know why.

*TimDaniels*