Drive Image 2002 does not boot to Caldera DOS

[milleniumaire]

When I use the Windows version of Drive Image 2002, I am warned that a
re-boot will be made because I have chosen to image the O/S drive.
When I hit the Yes button to start imaging, Windows shuts down and the
re-starts. No backup is performed, no DOS version of Drive Image is
started.

So far PowerQuest tech support have not supplied any useful
information on why this is not working.

If I boot the machine using the rescue disks, the DOS version of Drive
Image starts and I can perform my required backup. Part of the reason
I bought this version was to be able to control everything from
Windows - even if it does have to re-boot, but even that isn't
working.

Anyone had similar problems?

Regards.
Paul.

 

[sli]

There is a compatibility issue with PQDI 2002 and Windows XP with SP1
installed. Common problems are with the Disk Utilities and
ImageExplorer. From what I've read, PowerQuest is not going to fix it
in version 6. Their recommendation is to upgrade to version 7 for use
Windows 2000 & Windows XP.

And yet, DI 5.0 works just fine with XP/SP1. I use it all the time.
Whatever they did they should have left it alone.

 

[Michael Kimmer]

When I use the Windows version of Drive Image 2002, I am warned that a
re-boot will be made because I have chosen to image the O/S drive.
When I hit the Yes button to start imaging, Windows shuts down and the
re-starts. No backup is performed, no DOS version of Drive Image is
started.

So far PowerQuest tech support have not supplied any useful
information on why this is not working.

If I boot the machine using the rescue disks, the DOS version of Drive
Image starts and I can perform my required backup. Part of the reason
I bought this version was to be able to control everything from
Windows - even if it does have to re-boot, but even that isn't
working.

Anyone had similar problems?

Regards.
Paul.

What does your HDD configuration look like? Only IDE? IDE + SCSI? SCSI?
In either scenario Drive Image 2002 seems to write its boot code in the
WRONG MBR area, that is *not* in the MBR of your physical bootdisk.

_Check_:
Compare your bootdrive config by comparing the contents of both a Windows
partition info file (PartInNT.EXE) and a DOS partition info file
(Partinfo.EXE). Please, bear in mind what partition is flagged as part of
disk #0/$80 (boot flag).

As you may already know, IDE drives have a higher priority than their SCSI
equivalents. So, booting from a SCSI drive will naver (!) result in running
Drive Image 2002 in Caldera DOS...Some system have the ability to change
this priority hierarchy, otherwise, either the program CD or the bootdisks
are to be used...

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

 

[CS]

On 28 Aug 2003 13:02:34 -0700, (e-mail address removed)
(milleniumaire) wrote:

Hi Paul:

If the DI 2002 boot disks are working OK, that indicates the system
and hard drive(s) are probably OK.

What I would suggest is to completely uninstall DI 2002 using Control
Panel, Add/Remove and try reinstalling it again. Be sure upon
reinstallation that you let it install all options. If it still
refuses to boot to the Virtual Caldera DOS boot, you may have
something preventing it from doing so. Do a virus scan just in case
although I don't think that's it since you can boot with the disks.

Also, are you able to make an image of your other partitions from
within Windows XP? Can you use the image viewer within XP? Is
anything at all working in XP?

 

[djs]

There is a compatibility issue with PQDI 2002 and Windows XP with SP1
installed. Common problems are with the Disk Utilities and
ImageExplorer.

From what I've read, PowerQuest is not going to fix it
in version 6. Their recommendation is to upgrade to version 7 for use
Windows 2000 & Windows XP.

What a surprise--PowerQuest wants more of your money to try to get past
their own damn bugs.

 

[John]

When I use the Windows version of Drive Image 2002, I am warned that a
re-boot will be made because I have chosen to image the O/S drive.
When I hit the Yes button to start imaging, Windows shuts down and the
re-starts. No backup is performed, no DOS version of Drive Image is
started.

So far PowerQuest tech support have not supplied any useful
information on why this is not working.

If I boot the machine using the rescue disks, the DOS version of Drive
Image starts and I can perform my required backup. Part of the reason
I bought this version was to be able to control everything from
Windows - even if it does have to re-boot, but even that isn't
working.

Anyone had similar problems?

Regards.
Paul.

If your C: disk uses the NTFS file system, make sure that the directory
that Drive Image is installed in is NOT compressed (blue file names).
On my system it is in \Program Files\PowerQuest\Drive Image 2002\
The Caldera DOS image is under that directory and the boot loader does
not know how to uncompress a compressed file.

 

[I'm Dan]

SP1
Oh ya? Such as?...............

Uhmmm? What are these "common problems...". Speaking in general terms is one
of your stronger characteristics and providing us with arguments is one of
your weaker ones!

Drive Image 2002 has no known issues with XP Pro/Home with SP1...

Michael, if you're going to come in here with an attitude, you should at
least keep up. Problems have been widely reported here in the ng over
the last 6-9 months, and I suspect Sparker9 had seen those threads.

It seems the issue stems from some changes Microsoft made to the NTFS
spec with SP1, but I don't know exactly what about it causes
partitioning and cloning utilities to break. What is clear is that some
people have no trouble at all while others either get crashes or get
images that DI claims are successfully created but fail to restore
correctly. The common element in all those reports was the use of SP1
with NTFS partitions. Not everyone with SP1/NTFS has problems, but a
disconcerting number of people do. FWIW, I've also seen a few reports
in the Win2K forums of the same DI/Ghost problem with SP3 or 4
(off-hand, can't remember which) -- again, the common element was NTFS
and a recent SP release.

PowerQuest has acknowledged the issue publicly with PartitonMagic 7 and
privately with DI 2002 -- do a google newsgroup search for
(e-mail address removed) to find one example. There have been reports of
similar problems with Ghost 2003, so I suspect the issue may affect
Ghost as well, although I don't think Symantec has made any comment.

I use DI 2002 without problems, but wouldn't go so far as to say there
are "no known issues."

 

[Bob Huntley]

Have you tried booting the Powerquest CD itself - you might need to change a
BIOS option, or press a key (F12 in my case) to tell the PC to try and boot
from the CD Drive.

I use DI 5.0, and the CD boots into Caldera DOS.

 

[KG]

His issue is when inside Windows and he decides to image the C: drive (with
his OS) DI 2002 says it has to reboot and create the image from DOS. DI
2002 reboots back into Windows instead of booting to Caldera DOS to create
the image. Using the DI 2002 rescue disks is a workaround as well as your
suggestion.

KG

| Have you tried booting the Powerquest CD itself - you might need to change
a
| BIOS option, or press a key (F12 in my case) to tell the PC to try and
boot
| from the CD Drive.
|
| I use DI 5.0, and the CD boots into Caldera DOS.
|
|
| | >
| > | > > When I use the Windows version of Drive Image 2002, I am warned that a
| > > re-boot will be made because I have chosen to image the O/S drive.
| > > When I hit the Yes button to start imaging, Windows shuts down and the
| > > re-starts. No backup is performed, no DOS version of Drive Image is
| > > started.
| > >
| > > So far PowerQuest tech support have not supplied any useful
| > > information on why this is not working.
| > >
| > > If I boot the machine using the rescue disks, the DOS version of Drive
| > > Image starts and I can perform my required backup. Part of the reason
| > > I bought this version was to be able to control everything from
| > > Windows - even if it does have to re-boot, but even that isn't
| > > working.
| > >
| > > Anyone had similar problems?
| > >
| > > Regards.
| > > Paul.
| > If your C: disk uses the NTFS file system, make sure that the directory
| > that Drive Image is installed in is NOT compressed (blue file names).
| > On my system it is in \Program Files\PowerQuest\Drive Image 2002\
| > The Caldera DOS image is under that directory and the boot loader does
| > not know how to uncompress a compressed file.
| >
| >
|
|

 

[milleniumaire]

I do have SP1 installed, however the problem may also be due to my
machine configuration which is as follows:

2 x 40GB UDMA133 DiamondMax disks stipped in RAID 0 (giving 80gb
stripped drive) connected on IDE 3&4
This "drive" has 4 partitions:
C: Windows XP O/S (NTFS)
E: Data (NTFS)
F: Oracle (NTFS)
G: Programs (NTFS)

1 x 80GB ATA/133 DiamondMax Plus connected on IDE1 with one partition:
H: Backup 1 (FAT32)

1 x 9GB Maxter 90840D6 connected on IDE2 with on partition:
I: Backup 2 (FAT32)

If I try to create an image for ANY partition on the RAID array
(partitions C:, E:, F: or G Drive Image forces a reboot to DOS in
order to perform the imaging process. Needless to say the image is
never created and the machine simply reboots into Windows. This
happens even when I don't include C: (the O/S partition). I assume
this is something to do with the drives being stripped.

If I create an image for one of the other drives e.g. I: then this
works fine in Windows without booting to DOS.

H: is the drive I used to create the images on and was purchased
specifically for the job.

I am aware of the existance of Drive Image 7 and it looks like it
would resolve me problem, however based on my experience of Drive
Image 2002 I am reluctant to part with more money only to find that it
doesn't work as documented or that there is some quirk due to the
version of O/S being used or due to my use of a RAID array. I have so
far been very disapointed with the level/quality of support I have
received.

The software appears to work perfectly when I boot into DOS and run it
from the rescue disks. I say "appears" as I haven't yet had to
restore from one of the image files. If I had wanted to use it this
way I could have bought Drive Image 5!

Paul.