Drive Image 2002 imcompatible with DVD+-RW?

[Ar Q]

I have used Drive Image 2002 (6) for years. It runs ok with all the CD-ROMs,
DVD-ROMs and CD-RWs I have. But recently I upgraded to an TDK DVD+/-RW.
Drive Image hung on the welcome screen when I used the DOS disks trying to
restore an image. Changing back to my old DVD-ROM, then it is ok. Also,
there is no problem with the DVD+RW when using the slightly newer PQ
Partiton Magic 8. My questions are:

(1) Is there a patch to fix such a problem?
(2) If not, does Drive Image 7 fix the problem?

Thanks,

Ar Q

 

[Michael Kimmer]

I have used Drive Image 2002 (6) for years. It runs ok with all the
CD-ROMs, DVD-ROMs and CD-RWs I have. But recently I upgraded to an
TDK DVD+/-RW. Drive Image hung on the welcome screen when I used the
DOS disks trying to restore an image. Changing back to my old
DVD-ROM, then it is ok. Also, there is no problem with the DVD+RW
when using the slightly newer PQ Partiton Magic 8. My questions are:

(1) Is there a patch to fix such a problem?
(2) If not, does Drive Image 7 fix the problem?

Thanks,

Ar Q

Drive Image 2002 may hang on the welcome screen "Loading System...Please
wait". PQDI "sees" an ATAPI DVD-drive, strangely enough, as a fixed disk
ONLY when it is reported as AutoDetect. It attempts to read its MBR which,
of course, is missing, so it loops until hell freezes over... Changing it to
"None" or "Not Installed" may solve this.

So:

(1) Is there a patch to fix such a problem? Read what I wrote above...
(2) If not, does Drive Image 7 fix the problem?

As Drive Image 7.0 operates entirely in Windows it does no longer depend on
the BIOS, so Drive Image which comes currently as version 7.03, bypasses
this BIOS issue and should support your TDK drive...

--
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"

 

[Ar Q]

As Drive Image 7.0 operates entirely in Windows it does no longer depend on
the BIOS, so Drive Image which comes currently as version 7.03, bypasses
this BIOS issue and should support your TDK drive...

First, thanks for your help. Second, does this mean Drive Image 7 no longer
make the rescue disks operating entirely on DOS?

Thanks again,

Ar Q

 

[Michael Kimmer]

First, thanks for your help. Second, does this mean Drive Image 7 no
longer make the rescue disks operating entirely on DOS?

Thanks again,

Ar Q

As DOS is no longer a requirement of Drive Image 7.0 and does no longer
exist the rescue disks can no longer be created.
Creating an image is done in the background while Windows is still running
and functional. Drive Image 7.0 will first create a snapshot of the
operating system and stores in in memory from where the image is created
sector-by-sector. This opens the opportunity to create an image on a
partition from which the snapshot is taken! So, no problems storing an image
on C: whilst C: is being imaged!

When you have the intention to restore a system partition (containing your
operating system) you will have to start from the Drive Image 7.0
application CD-ROM and start the PQRE (which stands for the (P)ower(Q)uest
(R)ecovery (E)nvironment)...There you are able to restore a system image,
browse it using The Backup Image Browser and, if you want, restore single
folders and files...

--
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"

 

[Rod Speed]

First, thanks for your help. Second, does this mean Drive Image 7
no longer make the rescue disks operating entirely on DOS?

Sort of. It comes with the older DI 2002 which you can use that way if you want.

And you dont need the dos rescue floppys anyway, even for a restore
to a blank hard drive, you just boot the CD and that uses a stripped
down version of Win, just like the XP distribution CD does.

 

[Ar Q]

"Michael Kimmer"

ONLY when it is reported as AutoDetect. It attempts to read its MBR which,
of course, is missing, so it loops until hell freezes over... Changing it to
"None" or "Not Installed" may solve this.

I changed it to "None" and the result is mixed. On my secondary computer, it
is a success. But on my primary computer, "auto detection HD" can't be
disabled, so although I can change seconary IDE primary to none, the BIOS
seems to automatically correct itself and change back from none to TDK DVDRW
for the secondary IDE master. Then the system will freeze on the welcome
screen. I tried to use Drive Image 2002 CD instead of rescue disks to boot
the system, I also can't pass the welcom screen. Now it seems I have also
two options, either disconnecting the DVD+RW everytime I need to make an
image or buy the Drive Image 7 which might not suit my need ( I want
everything works as it used to be, not writing to a new format or using MS
..net framework based on what I read.) Any other options you might suggest?

Thanks again,

Ar Q

 

[Michael Kimmer]

"Michael Kimmer"


I changed it to "None" and the result is mixed. On my secondary
computer, it is a success. But on my primary computer, "auto
detection HD" can't be disabled, so although I can change seconary
IDE primary to none, the BIOS seems to automatically correct itself
and change back from none to TDK DVDRW for the secondary IDE master.
Then the system will freeze on the welcome screen. I tried to use
Drive Image 2002 CD instead of rescue disks to boot the system, I
also can't pass the welcom screen. Now it seems I have also two
options, either disconnecting the DVD+RW everytime I need to make an
image or buy the Drive Image 7 which might not suit my need ( I want
everything works as it used to be, not writing to a new format or
using MS .net framework based on what I read.) Any other options you
might suggest?

Thanks again,

Ar Q

Disabling HDD AUTODETECTION or setting an IDE channel itself to NONE is not
what I recommended...
I was in fact referring to the DVD drive itself...

Based on my own experience:
a.) some Intel chipsets may also result in this behavior.
Would an update may be an answer?
b.) I don't believe this in relation to DM 2002, but could you try a drive
firmware update?

If that fails...upgrade to Drive Image 7.0

--
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"

 

[Ar Q]

Sorry, I did not make it clear. I did set the DVD drive itself to "none",
not the IDE channel. Also, the successful case has Intel chipset and the
failed case has Via chipset. So in the mean time, I will install the TDK DVD
buner on the Intel machine and CD-RW on the VIA machine.

After doing more Google searches, I found many articles warning not to
upgrade to DI 7-- many confirmed my intial impression about the two flaws.
One is the required MS .net framework and the second is lack of floppy disk
support and the rescue CD can be only used to restore an image, not to
create an image.

Thanks again,

Ar Q

 

[Lil' Dave]

Sorry, I did not make it clear. I did set the DVD drive itself to "none",
not the IDE channel. Also, the successful case has Intel chipset and the
failed case has Via chipset. So in the mean time, I will install the TDK DVD
buner on the Intel machine and CD-RW on the VIA machine.

After doing more Google searches, I found many articles warning not to
upgrade to DI 7-- many confirmed my intial impression about the two flaws.
One is the required MS .net framework and the second is lack of floppy disk
support and the rescue CD can be only used to restore an image, not to
create an image.

Thanks again,

Ar Q

Just wondering why "MS .net framework" installation is a flaw? Anything
specific, or just general not know what/how .net framework works or general
suspicion of MS?

Also wondering why it is a flaw for DI 7 to only backup in windows mode
("lack of floppy disk support and the rescue CD can be only used to restore
an image, not to create an image") since this is so much faster than if from
floppy boot as in DI 2002? Why is the DI 7 restore/installation CD such a
problem for restoration purposes?

Am now looking at the original unopened DI 7.0 box. Says DI 2002 saves to
CD, DI 7.0 saves to DVD (I take it as DVD media).

DI 7 can only be installed to a Win2K or XP existing operating system only.
To me, this implies an NTFS file system for the "normal" user of a NT based
operating system. DI 2002 does NOT understand XP's version of NTFS. How
about some specifics of the operating system and file system you're trying
to save? Reading all this bashing and no specifics is rather puzzling to
almost meaningless words.