Several problems with DriveImage

  • Thread starter Thread starter Kai Tebbe
  • Start date Start date
K

Kai Tebbe

First of all when I installed DriveImage 2002 it creates bad Rescue floppies.
When I tried to use them later the computer remarked:
"NTLDR is Missing
Press any key to restart".

When I create another pair of rescue floppies the first floppy told me:

"HIMEM.SYS: Cannot control address line A26
HIMEM.SYS 2.36"

Hmmm, what does that mean ?

However I proceeded with the Image creation and DriveImage reuqested me to
specify the target name of the image (*.pqi) with a target path similar to D:\images\system.pqi

I tried exactly this name but DriveImage refused to accept it.
Fiddling around I found out that I have to enter a path like:

\\.\disk1.part1\images\system.pqi

Why this ?
Why aren't drive letters accepted? Very poor!

Thx in advance
Kai
 
For detailed answers you should post your queries in
a DriveImage newsgroup. I also recommend that you
read the DriveImage manual in detail.

The message "NTLDR is missing" simply means that your
"Rescue" floppy is not a boot disk.

"HIMEM.SYS: Cannot control address line A26
This is a message that is generated by certain motherboards
after an imaging operation. Do a cold boot instead of a warm
boot to get rid of it.

"\\.\disk1.part1\images\system.pqi"
You were probably trying to save your image file to an
NTFS partition after booting the PC with DOS/Win9x boot
disk.
 
Dexter said:
Upon roobting my computer, the last step in the installation process
of Drive Image 7, my computer kept rebooting on its own, without
completing the installation process. The only way to stop this
sequence was to turn it off. Turning the computer on resulted in self
repeating bootup sequence. "Last good.." and "Safe Mode" did not work.
To make things worse, the computer would not access the CD Drive,
although the ROM Startup sequence provided for it. Not having acces to
that drive eliminated the option of starting the computer with Windows
installtion disk. Power Quest support was not helpful either. After a
lengthy dialogue on the phone, the tech support person shared with me
that he had several people with a similar problem and had two
suggestions: (1)Wait until they fix the bugs in this software. (2)
Re-install windows.
Click to expand...

Too bad you got suckered into DI7. See
http://www.langa.com/newsletters/2003/2003-07-03.htm. FWIW, I've used
DI from version 2 to 2002 and have been a big supporter of DI, but have
to agree with Langa regarding DI7.
 
Earlier versions of DriveImage would not work on NT Server,
unless you ran the Emergency Recovery Disk. I suspect
that the same applies to DriveImage 2002: That its ERD does
not care about the operating system. After all, it's just copying
bytes from a FAT32 or NTFS partition. It has no way of
knowing what these bytes mean, especially in a multi-boot
situation.

Perhaps someone who owns DriveImage 2002 can confirm
this.
 
I don't know how you and Langa can come up with that baloney (not what I
really call it). I've been using it with W2K and XP Pro since it came out
(in fact I'm using it at this moment backing up a Linux installation to an
XP storage location).

Prove your statement!
 
I've gotta go with UserFriendly on this. DriveImage 2002 works just fine on
Windows 2000 and has performed flawlessly for me. Also, AFAIK, DriveImage 7
has DriveImage 2002 bundled inside it, and is just a wraparound with new
functionality for Windows XP and such. I do recall a problem with my first
set of rescue disks, but when I created them again with new floppies, they
worked just fine. DI2002 is still downloadable from PQ's website, by the
way.

For my money, DriveImage 2002 is the fastest and easiest way to do a full
recovery of a Windows system that has totalled itself. I played around with
a lot of alternatives, including the Windows Recovery Disk, after my last
big f**kup with partition management overwrites. All I have to do next time
is boot from a floppy, insert the first backup CD in the drive and the hard
disk is restored back to its last backup state in less then 30 minutes,
ready to run again. No operating system or other utilities required. I can
even keep incrementals that I can run over the top to update to later
version backups one step at a time. I cannot say how it might work with dual
boot systems or heavily configured partitions, etc.

If someone can illustrate an easier or faster recovery method, I'd be
interested to hear about it.

Tony
 
Salt_Peter said:
Drive Image 2002 isn't for W2K. Only Win9x and NT4 workstation.
Click to expand...

Actually, Drive Image 2002 is for all versions of Windows. Drive Image 7
is for W2K and XP only, and comes bundled with a copy of DI 2002 for the
"lesser" Windows versions. If you already have DI 2002, there appears to
be no reason to buy DI 7.
 
My only contribution to this discussion is that I'm using DeployCenter,
which is the enterprise version of DriveImage. It is equivalent to some
consumer version, but I'm not sure which and I'm pretty sure the only
difference is licensing which allows you to use it on servers and deploy
cloned workstations.

Anyway, it kicks ass and I can *fully* backups my servers in about 10
minutes total downtime each (not including data).

In addition, PowerQuest's imaging utilities have been years ahead of
Symantec, being able to save images to NTFS partitions long before
Symantec could and native support for hardware RAID, which I think Ghost
still can't do.
 
You raise a fair point. On the other hand I use DI to create
images of my clients' PCs so that I can restore those PCs
when they go south. My philosophy is: If I cannot fix a
broken machine within 30 minutes then I will restore it.
To get a result with a guaranteed outcome I will always
restore the whole setup, not just some specific folder.

I suppose it's a question of personal preference.
 
kewl. Fair enough.

Pegasus (MVP) said:
You raise a fair point. On the other hand I use DI to create
images of my clients' PCs so that I can restore those PCs
when they go south. My philosophy is: If I cannot fix a
broken machine within 30 minutes then I will restore it.
To get a result with a guaranteed outcome I will always
restore the whole setup, not just some specific folder.

I suppose it's a question of personal preference.
Click to expand...
 
Back
Top