Hi for a first post
I had the traditional Error 5 & 8 on every boot, but thank goodness have now discovered how to clear the error. Next step is to run Drive Image without re-introducing the dreaded error and make a CD image of my virgin load of Windows2000 pro on C:
Problem is that every time I run DI from Windows the d@8% error is re-introduced resulting in "Strike any key...." which boots from the active partition and no image is cut. The error then has to be cleared again
I understand the solution may be to not run DI from Windows but from stiffies. Can someone please tell me in VERY simple terms: what stiffies and how.

ps This happens on a P4 CeleronD 2.4G with 128Mb of Ram. On a P4 Pentium 1.8 with 256Mb of Ram it works perfectly from Windows. Any explanations
Waiting for the solution.
Thanks,
Ken

Ken, Drive Image used to be a part of Power Quest's product line, but since it was sold to Symantec (Norton), there is no further support for it and it's now become part of the Norton Ghost Family. I used DI quite a bit and still have the last 2 versions. The very last version (version 7) was one that you "integrated" into Windows and could start the Imaging Process from Windows - this version had a lot of issues & I wouldn't recommend it for either a beginner or on a system that may have some instability. The version before this (2002), had some problems but was much easier to use and also could be used from a couple of boot floppies. This one is similar to Norton Ghost 2003 and earlier but had a much better user interface and was/is quite easy to use without many issues - it DID NOT have any capability built-in to save the image to an external device such as Norton Ghost does.

That was a bit of a diatribe on DI, but to try to help you further you'll need to provide us detail on:
1. which version you're using,
2. how you're using it,
3. when this problem arises,
4. configuration of your computer & especially the hard drive(s).

Thanks for the reply
Yes I have also found out the sorry tale of PowerQuest. Why Symantec accquired Powerquest is a mystery or was it just plain corporate greed? Support from Symantec is just lousy


Details are as follows:

# Drive Image 2002 ver. 7

# Installed on E: - Started via Start/Programs menu - Starts OK
Select C: to image - Select CD for image - Run - PC reboots - Drive Image screen
ERROR #91 Disk Manager detected on drive 2, but not running. [OK]
ERROR #87 Unable to initilize the engine.

# 2.4 CeleronD with 128 Ram.
A: =Floppy
C: =6G (Master1)
D: =18G (Slave1)
E: =8G F: = 6G G: = 6G (Master2)
H: =CD (R/W). (Slave2)


Also tried second option of image to Hard drive (F:), but that also fails.
This is on the Desktop. All hard drives are FAT.
When I repeat exercise on Laptop all works fine.

Thanks,
Ken

Ken, make the 2 floppy (I see you call them stiffies) bootdisk set using the utility within Drive Image installed under Windows. Use this disk set to make an image to an on-board device such as a hard drive or CD/DVD burner. This should bypass your problem since Windows isn't running when you initiate DI.

Symantec is using DI version 7 as their new Ghost version - it's an improvement on Power Quest's version, but I still prefer the "stiffie" approach - starting from DOS there's a lot less to go wrong.

Hi Alfons
I had previously tried the Floppy/Stiffy approach without success (Guess the term Stiffy gives away my age, but I call them Stiffies since I refer to the old 5" flexible disks as floppies).
Since DI works fine on the laptop and the most obvious difference is that DI is installed on the D: drive there, I took the following route:

# Uninstalled DI from E: - Installed DI on D: - Made the two recue disks - booted from the rescue floppies (Now you have me talking the lingo !!)

# DI loads and displays the splash screen, but then
ERROR #91 Disk Manager detected on drive 2, but not running. - [OK]
ERROR #87 Unable to initilize the engine. - [OK]
A:\>

Guess that leaves us with this one not down yet. Hope my actions give you further insight to the problem and is bringing us closer to the solution.
Cheers,
Ken

You have a Disk Manager such as EZ-Drive (or something else) installed. This was a favorite approach to "fool" a computer that had either BIOS or Hardware Hard Drive limitations - it kept it's own translation tables as to where things were on the HD and fed the BIOS terms it could relate to.

We need to figure out what disk manager you have and then see about how to remove it without loosing access to your files. Here are a couple of questions to start with:

1. What is the make & model of your motherboard?
2. What/who's utility did you use to set-up (configure) the hard drive?
3. Are you adverse to re-doing everything (it may be easier)?
4. What file system do you want to end up with (FAT32 or NTFS)?
5. Do you have access to an external HD box (not an external HD but a box that you can put a HD or CD/DVD unit into)?
6. Do you have access to a partition manager such as Partition Magic?

Hi Alfons

WE CRACKED IT

Thanks to you, you put me on the right track. One of the drives (E:) was recently installed from another PC and of course it was bootable. Deleted the MBR and all is now well, DI runs fine from Windows.
Thanks again, Next time you see me in the Pub, the drinks are on me
Ken

You're welcome Ken, I should have picked up the problem from your second post when you mentioned the error was related to a disk manager - glad you've got that sorted out & happy computing