Drive Image 2002 and /ide=on switch

[Tom Voltaggio]

I found out about this switch and have used it to boost my image times
to over 1 Gig/Min with low compression on my Abit KT7a with a 1.5 GHz
Athlon! Astounding!
I understand that it allows Drive Image to switch from PIO to UDMA
mode.

One thing that did happen is interesting, however. I have a 200 gig
drive and a 120 gig drive as master/slave on one IDE channel. My main
backup procedure is to back up from the 200 to the 120 and it works
fine.

Here's the problem. I have a 30 gig FAT32 partition at the end of the
200 gig drive which I use for various things and is totally visible
under my Windows 2000 SP4.

Under both DI5 and DI2002, if I put on the /ide=on switch, I can't see
this 30 gig partition which starts beyond the 137 gig boundary in
Drive Image. It shows up as unallocated. If I switch off the
/ide=on, the partition shows up fine. The drive shows up fine in the
Award BIOS (version 7/2002) and I enabled the 48 bit switch in Win
2000 (although SP4 has it built in).

Any ideas?

 

[Michael Kimmer]

I found out about this switch and have used it to boost my image times
to over 1 Gig/Min with low compression on my Abit KT7a with a 1.5 GHz
Athlon! Astounding!
I understand that it allows Drive Image to switch from PIO to UDMA
mode.

One thing that did happen is interesting, however. I have a 200 gig
drive and a 120 gig drive as master/slave on one IDE channel. My main
backup procedure is to back up from the 200 to the 120 and it works
fine.

Here's the problem. I have a 30 gig FAT32 partition at the end of the
200 gig drive which I use for various things and is totally visible
under my Windows 2000 SP4.

Under both DI5 and DI2002, if I put on the /ide=on switch, I can't see
this 30 gig partition which starts beyond the 137 gig boundary in
Drive Image. It shows up as unallocated. If I switch off the
/ide=on, the partition shows up fine. The drive shows up fine in the
Award BIOS (version 7/2002) and I enabled the 48 bit switch in Win
2000 (although SP4 has it built in).

Any ideas?

Run a partinfo in pure DOS mode and post a link to its output...

NOTE: Run a PARTINFO > info.txt from rescue disk #1

--
M.f.G.
Michael Kimmer

"Ein Tag an dem Du nicht lächelst ist ein verlorener Tag"
"Eine Nacht in der Du nicht schläfst ist eine verschlafene Nacht"

 

[Tom Voltaggio]

No need. I found the workaround. With the /ide=on switch, Drive
Image will not show any partition that STARTS beyond 137 GB as
anything but unallocated. I used Partition Magic to resize and move
the partitions such that all partitions on the 200 GB drive start
BEFORE the 137 GB boundary and they all show up in Drive Image, even
though the last partition extends beyond 137 GB and all the way to 200
GB. So, if you wish to take advantage of the /ide=on switch, you MUST
have all partitions starting before the 137 GB boundary. If you don't
wish to use the switch, this is not necessary.

 

[Timothy Daniels]

For what it's worth, I had switched to Drive Image 2002
because I could never get Drive Image 7 and 7.01 to work.
But I could never get DI 2002 to work in the DMA mode,
and it took more than an hour to clone a local drive.

In the interim, I installed Visual Studio.NET (which included
the .NET Framework). I saw a posting mentioning DI 7 needing
the .NET Framework, so I dumped DI 2002 and reinstalled
DI 7.01. Voilà! Now DI 7.01 works with DMA, and the
cloning takes a few minutes. Since .NET Framework is a free
download from Microshift, why not just dump DI 2002 and
go with DI 7.01 (or its successor)? The .NET class library is
probably all that you need.

*TimDaniels*

 

[Tom Voltaggio]

Actually, I was using DI7, but after a trojan attack, I couldn't get
DI7 to work again. It would fail on startup with an RPC failed message
(it also said that it couldn't read drive information). After posting
a number of google help posts and trying to get Symantec to help, I
gave up qnd went back to DI2002.

What was your experience with not getting it to work and what did you
do to get it back?

For what it's worth, I had switched to Drive Image 2002
because I could never get Drive Image 7 and 7.01 to work.
But I could never get DI 2002 to work in the DMA mode,
and it took more than an hour to clone a local drive.

In the interim, I installed Visual Studio.NET (which included
the .NET Framework). I saw a posting mentioning DI 7 needing
the .NET Framework, so I dumped DI 2002 and reinstalled
DI 7.01. Voilà! Now DI 7.01 works with DMA, and the
cloning takes a few minutes. Since .NET Framework is a free
download from Microshift, why not just dump DI 2002 and
go with DI 7.01 (or its successor)? The .NET class library is
probably all that you need.

*TimDaniels*

partitions such that all partitions on the 200 GB drive start

 

[Timothy Daniels]

As I vaguely recall, the problem was in not getting a bootable clone.
The image was there, but I couldn't get it loaded. PowerQuest
techs advised me to use DI 2002 (even though I was using WinXP).
DI 2002 worked, but slowly - I couldn't get the /ide=on switch to
work. Upon hearing of the .NET Framework requirement, I
uninstalled DI 2002 and then installed DI 7.01 again (since I had
by then installed the .NET Framework as part of Visual Studio
..NET). Be aware that there was a fix to version 7.0 of DI that was
available on CD free from PowerQuest that was known as version
7.01 . That is what I had been using and what I am now using. I
don't know if it's available from Symantec. I suspect that Symantec
has folded version 7.01 of DI into its Ghost product now and would
rather forget the Drive Image legacy left from PowerQuest. As for
the .NET Framework, it's free for download from MS, but it's huge,
and Drive Image probably uses just a couple routines from it. Maybe
it's time to get Symantec's new Ghost product. At least that sucker
is supported.

*TimDaniels*

 

[Tom Voltaggio]

Yes, I actually tried version 7.04 as well as 7.0 and .NET 1.03 and
1.1. Nothing got me working. I gave up and went back to 2002.