Timothy Daniels said:
With Drive Image 2002, I don't get a bootable drive
on the new disk if I don't disconnect the old disk
before the 1st bootup. All the files and the file structure
are there except for (I guess) the master boot record.
Presumably you cloned the partition, not the physical drive.
Works fine for me with DI 2002 when cloning the physical drive.
It's great for archiving files, but not for making a
bootable backup system or a replacement system.
Works fine for me, tho I normally do it when putting a bigger
physical drive in place of a too small one, rather than for
backup. I prefer to do image backups, mainly so I can keep
more than just the latest so I can step back gracefully if a
significant change turns out to have operational downsides.
And I normally clone the physical drive in the drive upgrade
situation because its a lot faster than restoring the image
across the lan and I have to have the system open anyway.
If one disconnects just the power plug from
the old drive, leaving the data plug connected
to the disk drive to prevent signal reflections,
Thats never a good idea. And you wont prevent reflections
by having the drive connected but not powered anyway.
I believe the new drive may be left jumpered
as Slave and left at the intermediate connector
and it will boot up despite not being Master
That varys with the drive. Some drives are happy to be
the only drive on a ribbon cable jumpered as slave, and
some arent. That flouts the ATA standard anyway.
and not being at the end connector.
Doesnt matter if its the end connector with a
temporary config, just the first boot after the clone.
(I haven't yet tried this.)
Thats obvious.
As I understand Master/Slave, though, it is to implement
data collision avoidance at the IDE channel level,
Nope, nothing to do with collision avoidance
whatever. There are no collisions with ATA.
and the rest of the system just sees 2 drives
without any reference to Master/Slave attributes.
Utterly mangled all over again.
Thus my comment about the jumpering not
mattering for the solo first bootup of the new drive.
You're wrong. If the new drive is a WD, it
just plain wont work jumpered as slave and
the only drive on the cable in most systems.
Its not just a problem with WD drives either.
My comments, and this thread, are about the 2 WinXP
systems which result from the cloning of a WinXP system.
You will never see XP automatically setup
a multiboot config however you clone XP.
If the original drive is visible to XP on the first boot,
and you tell the bios to boot the clone, XP will get
seriously confused and will boot from the clone and
use quite a bit of the XP basics from the original drive.
That will boot fine, BUT you'll find that if you disconnect
or reformat the original drive later, the boot will fail,
because XP configured the boot to use XP components
from both physical drives and that stuff will be gone
when the original drive is gone.
In my experience in using Drive Image 2002 to
clone a Windows XP Pro drive I've been unable
to *avoid* generating a dual-boot option.
God knows what you were doing, presumably you got
that result when thrashing around after you didnt clone
the physical drive but cloned the XP boot partition to the
new drive instead, and you then manually ran one of the
utes thats will repair a broken XP boot.
You certainly wont get a multiboot config if you clone
the physical drive, disconnect the original drive for
the first XP boot after the cloning, have the clone
boot fine, and comment that its seen new hardware,
request a reboot because of that, allow that reboot,
boot off the clone again, turn the system off, plug the
original drive back in again and boot of the clone again.
You still have the simple XP boot and the original
drive is visible at the XP level and can be formatted
etc and the clone will still boot fine after you have
formatted the original drive.
What I get repeatedly is a boot.ini file which
names both WinXP OSes as options for a dual boot.
Only if you use one of the utes that scans
for other than the XP you've booted from.
You'll never get that auto just by plugging
the original drive back in again.
At some point, I don't know exactly when, the 2nd WinXP
is seen by the first, and the dual boot option is implemented.
Likely because you told it to scan for
other OSs and add them to the boot config.
I have to go back into the boot.ini files in both OSes
and comment out the 2nd WinXP name (by surrounding
it with square brackets) to avoid the dual boot option
dialog each time I boot one or the other drive.
Only if you tell it to scan for other OSs.
And for completeness, that will only find other OSs
from the NT/2K/WP family, it wont find say a 98SE
bootable drive thats been plugged back in later.
As I said, I can't *avoid* it.
Only because you clone wouldnt boot because you cloned
the partition and not the physical drive and you had to
repair the boot using one of the available ways to do that.
Nope, nothing auto about it.
You've fooled yourself.
I didn't mention multiple installs. I've been referring to
cloning of a WinXP OS from one drive to another.
Which produces multiple installs.
Somehow the multi-boot feature gets
enabled everytime I clone my WinXP system.
Because you have to repair the boot of the clone when it wont
boot, because you cloned the partition, not the physical drive.
Neither do I, but somehow the cloning of WinXP gives it to me.
Not the cloning didnt, that was the repair
you had to do when the clone wouldnt boot.