Drive Image 2002 and /ide=on switch

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

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?

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Tom Voltaggio wrote:
> 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"

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

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.


"Michael Kimmer" <michaelkimmer@NOSPAM.xs4all.nl> wrote in message news:<412fad4a$0$36860$e4fe514c@news.xs4all.nl>...
> Tom Voltaggio wrote:
> > 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

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

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" wrote:
> 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.
>
>
> "Michael Kimmer" wrote:
> > Tom Voltaggio wrote:
> > > 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

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

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?



"Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message news:<QP-dnWmzxaWCsKzcRVn-vA@comcast.com>...
> 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" wrote:
> > 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.
> >
> >
> > "Michael Kimmer" wrote:
> > > Tom Voltaggio wrote:
> > > > 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