cloning across IDE channels w/Drive Image 2002?

  • Thread starter Thread starter Timothy Daniels
  • Start date Start date
T

Timothy Daniels

Has anyone had any success cloning a HD on one
IDE channel to a HD on another IDE channel
using Drive Image 2002? I find that cloning from
Master to Slave on the same IDE channel goes
OK, but not across channels. Instead of the system
restarting in DOS mode after telling the GUI to
"Copy Drives", the HD just reboots into WinXP.
PowerQuest reps say the cross-channel cloning
should work for DI 2002 under WinXP, but I
haven't found a way.

My system is a Dell Dimension XPS_R450 with
version 13 of the BIOS running under WinXP Pro
and using an SIIG ATA/133 PCI card for the HD
IDE channels.

*TimDaniels*
 
Has anyone had any success cloning a HD on one IDE channel
to a HD on another IDE channel using Drive Image 2002?
Click to expand...

Yep, I usually do it that way if convenient because its faster.
I find that cloning from Master to Slave on the same IDE
channel goes OK, but not across channels. Instead of the
system restarting in DOS mode after telling the GUI to
"Copy Drives", the HD just reboots into WinXP.
Click to expand...

Likely some problem with the drive IDs when in DOS
being different from in XP, so it gives up and reboots.
PowerQuest reps say the cross-channel cloning should
work for DI 2002 under WinXP, but I haven't found a way.
Click to expand...

Never had a problem.
My system is a Dell Dimension XPS_R450 with version
13 of the BIOS running under WinXP Pro and using an
SIIG ATA/133 PCI card for the HD IDE channels.
Click to expand...

Likely its getting confused by that card. I
normally use the motherboard IDE channels.
 
Yes, that step which occurs after the BIOS loads
doesn't occur when the HDs are on different channels.
Any idea what could remedy that? Could the floppy
image be supplied on a floppy disk? Where does one
get the image to put on a floppy disk?

*TimDaniels*
 
Yes, that step which occurs after the BIOS loads
Click to expand...

Cant understand that bit. Try again.
doesn't occur when the HDs are on different channels.
Click to expand...

Its more likely that the job is setup at the Win level,
it does succeed in running the job at the DOS level
but that job cant see the drives in the config it expects
to see the and so it aborts the clone for safety.
Any idea what could remedy that?
Click to expand...

Try setting up the clone after you have booted
from the rescue floppys. That will likely make
the problem visible, you likely wont see the
drives as they appear at the Win level.
Could the floppy image be supplied on a floppy disk?
Where does one get the image to put on a floppy disk?
Click to expand...

Thats what DI calls the rescue floppys.

You just tell it to create them and boot from them.
 
Rod Speed said:
Yep, I usually do it that way if convenient because its faster.


Likely some problem with the drive IDs when in DOS
being different from in XP, so it gives up and reboots.


Never had a problem.


Likely its getting confused by that card. I
normally use the motherboard IDE channels.
Click to expand...


I tried using the motherboard IDE channels for the cloning.
I put one HD on each of the two channels, but Drive Image
acts just like it does when the two HDs are on different channels
of the PCI controller card - it just reboots into Windows XP
instead of looking for a floppy image. PowerQuest says it might
be due to the way the BIOS works, but there aren't too many
people left who still use the XPS_R450 and its BIOS, and Dell's
reps know zip about that BIOS's behavior in regards to HD
cloning.

*TimDaniels*
 
Rod Speed said:
Cant understand that bit. Try again.
Click to expand...


I'm not sure whether the BIOS starts up when
DI's GUI says its going to restart, or whether the PC
shuts doen and immediately starts looking for floppy
image. But there is a single text line which says
"Looking for floppy image", as I recall. After about
a 5 second delay, it says it found it and then starts in
with the cloning.

Its more likely that the job is setup at the Win level,
it does succeed in running the job at the DOS level
but that job cant see the drives in the config it expects
to see the and so it aborts the clone for safety.


Try setting up the clone after you have booted
from the rescue floppys. That will likely make
the problem visible, you likely wont see the
drives as they appear at the Win level.


Thats what DI calls the rescue floppys.

You just tell it to create them and boot from them.
Click to expand...


OK, on my agenda will be making Drive Image rescue
floppys, although the normal cloning procedure shouldn't
need those floppys.

*TimDaniels*
 
Timothy Daniels said:
Rod Speed wrote
Click to expand...
I tried using the motherboard IDE channels for the cloning.
I put one HD on each of the two channels, but Drive Image
acts just like it does when the two HDs are on different
channels of the PCI controller card - it just reboots into
Windows XP instead of looking for a floppy image.
Click to expand...

Weird. What happens if you initiate
the clone from the rescue floppys ?
PowerQuest says it might be due to the way the BIOS works,
Click to expand...

Yeah, most likely.
but there aren't too many people left who still use the
XPS_R450 and its BIOS, and Dell's reps know zip
about that BIOS's behavior in regards to HD cloning.
Click to expand...

Yeah, that virtual boot was always a bit of a kludge
so its not surprising that there are some wierditys.

What happens if you use Ghost 2003 ? It does the
detail of the virtual boot differently, basically creating
a temporary bootable partition on the hard drive.
 
Timothy Daniels said:
I'm not sure whether the BIOS starts up when
DI's GUI says its going to restart, or whether the PC
shuts doen and immediately starts looking for floppy
image. But there is a single text line which says
"Looking for floppy image", as I recall. After about
a 5 second delay, it says it found it and then starts in
with the cloning.
Click to expand...
OK, on my agenda will be making Drive Image rescue
floppys, although the normal cloning procedure shouldn't
need those floppys.
Click to expand...

Sure, I just meant that that would provide some evidence
on whether the problem is with the virtual boot or whether
its with what can be seen at the DOS level drives wise.

Its almost certainly the virtual boot thats the problem and
if it works fine from the rescue floppys, that proves that.
 
Well, no. Not really. The floppy image is created when you initiate the
image creation in XP.
Upon reboot, through the bios, then hits the floppy image which doesn't
exist in your case.
You can use the physical floppies (plural) that can be created by DI 2002.
You can do the same thing in that environment that the floppy image does.
Dave
 
It works now. Yahoooo!! I can clone an HD
from one PCI card IDE channel to another!

And I do *not* know how I finally made it work.
But there are clues....

First, I uninstalled Drive Image 2002 and then
I re-installed it again. I also used normal startup
rather than the abbreviated startup that had a
few services turned off, such as IIS and memory
stick support. I had made the 2 floppy rescue
disks per Rod Speed's advice when re-installing.
But it turned out that Drive Image was able to find
and "load the floppy image" and proceeded to
clone between the 2 ATA/133 channels on the
PCI controller card.

This means that I can clone any HD in my system
to an HD in a removeable caddy - and flout the
specs! Yay!! :-)


*TimDaniels*
 
Timothy Daniels said:
It works now. Yahoooo!! I can clone an HD
from one PCI card IDE channel to another!

And I do *not* know how I finally made it work.
But there are clues....

First, I uninstalled Drive Image 2002 and then
I re-installed it again. I also used normal startup
rather than the abbreviated startup that had a
few services turned off, such as IIS and memory
stick support. I had made the 2 floppy rescue
disks per Rod Speed's advice when re-installing.
But it turned out that Drive Image was able to find
and "load the floppy image" and proceeded to
clone between the 2 ATA/133 channels on the
PCI controller card.

This means that I can clone any HD in my system
to an HD in a removeable caddy - and flout the
specs! Yay!! :-)


*TimDaniels*
Click to expand...


Desiring a small and simple to use drive cloning app, I came across Drive
Wizard, which worked flawlessly and easily. Has a trial 30-day freebie so
that the user can verify function before purchase:

http://www.compuapps.com/Download/DriveWizardEval/drivewiz.htm

I have not, however, attempted to use it across IDE channels.

Stew
 
It works now. Yahoooo!! I can clone an HD
from one PCI card IDE channel to another!
Click to expand...
And I do *not* know how I finally made it work.
But there are clues....
Click to expand...
First, I uninstalled Drive Image 2002
and then I re-installed it again.
Click to expand...

Unlikely to be relevant, essentially because DI
recreates the virtual boot every time its used.
I also used normal startup rather than the abbreviated
startup that had a few services turned off, such as IIS
and memory stick support.
Click to expand...

Most likely its that, it didnt like that for some reason.
I had made the 2 floppy rescue disks per Rod Speed's
advice when re-installing. But it turned out that Drive
Image was able to find and "load the floppy image"
and proceeded to clone between the 2 ATA/133
channels on the PCI controller card.
Click to expand...
This means that I can clone any HD in my system to an
HD in a removeable caddy - and flout the specs! Yay!! :-)
Click to expand...

Nothing like a good flouting to make the day |-)
 
Back
Top