ray

Distinguished
Aug 14, 2001
630
0
18,980
Archived from groups: microsoft.public.windowsxp.general (More info?)

Just ran into Drive Image Error #1810, "Image file could not be
opened." A check on Google turned up few references to this error, and
most were for Drive Image versions much older than my Drive Image 2002,
so I thought I would post a brief comment for posterity.

I got the error message about three-quarters of the way through an
image restore. To my surprise, though, when I closed the error message
and Drive Image automatically rebooted, the system came up in the new
format. That is, my system restore had been successful, at least as
far as I could see at a brief glance.

I thought that maybe the restore had been only 3/4 successful, and that
I would later discover that something important was missing. So I
decided to redo the restore. This time, I did not check the various
safety options -- "Check for file system errors," etc. That had been a
problem in some other DriveImage operations, but I had felt like trying
it in this situation. But unchecking the box did not make a
difference.

The problem, it turned out, was that I was trying to restore two
separate drives at once. I had backed up both C: and D: in one drive
image. When I restored one drive at a time, the Error #1810 message
did not appear -- even though, this time around, I had checked all of
the verification options.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

This may occur because your system, when it was imaged, had logical drive
errors.

I have found that for an absolutely reliable image I first run chkdsk c: /f
from the command prompt. I then reboot and allow chkdsk to fix any errors.
Then, after booting up again, I defrag the drive with PerfectDisk. Then I
create the image using either DriveImage, Ghost 9 or True Image 8. I also
choose to verify the image after creation.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from: George Ankner
"If you knew as much as you thought you know,
You would realize that you don't know what you thought you knew!"

"Ray" <Ray.Woodcock@gmail.com> wrote in message
news:1127046718.416694.316120@g49g2000cwa.googlegroups.com...
> Just ran into Drive Image Error #1810, "Image file could not be
> opened." A check on Google turned up few references to this error, and
> most were for Drive Image versions much older than my Drive Image 2002,
> so I thought I would post a brief comment for posterity.
>
> I got the error message about three-quarters of the way through an
> image restore. To my surprise, though, when I closed the error message
> and Drive Image automatically rebooted, the system came up in the new
> format. That is, my system restore had been successful, at least as
> far as I could see at a brief glance.
>
> I thought that maybe the restore had been only 3/4 successful, and that
> I would later discover that something important was missing. So I
> decided to redo the restore. This time, I did not check the various
> safety options -- "Check for file system errors," etc. That had been a
> problem in some other DriveImage operations, but I had felt like trying
> it in this situation. But unchecking the box did not make a
> difference.
>
> The problem, it turned out, was that I was trying to restore two
> separate drives at once. I had backed up both C: and D: in one drive
> image. When I restored one drive at a time, the Error #1810 message
> did not appear -- even though, this time around, I had checked all of
> the verification options.
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

On Sunday 18 September 2005 05:51 am, Richard Urban [MVP] had this to say in
microsoft.public.windowsxp.general:

> This may occur because your system, when it was imaged, had logical drive
> errors.
>
> I have found that for an absolutely reliable image I first run chkdsk c:
> /f from the command prompt. I then reboot and allow chkdsk to fix any
> errors. Then, after booting up again, I defrag the drive with PerfectDisk.
> Then I create the image using either DriveImage, Ghost 9 or True Image 8.
> I also choose to verify the image after creation.
>
So how many hours does it take to backup your drive? You must have the
patience of a saint Richard.


--
Now this is Eye-Candy! Most beautiful desktop in the world.
Checkout ELive - a live Linux CD - run E17
http://www.elivecd.org/gb/About/index.html
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

I would agree about the Disk status before attempting an Image.
I use Drive Image 2002 and Ghost 2003 for some "Unusual" setups.
Before I ever attempt the image, I'll at the least do a cursory chkdsk.
It would a nice feature if these utilities did some type of integrity type
check before starting the imaging process. Drive Image 2002 does
have the System Check, but it's not very comprehensive. There are
some errors (Improper Dismounts) that can cause imaging issues.
There aren't too many things associated with a PC that can irritate
you like an image store that turns out to be corrupted or unusable.

"-rwxrw-r--" <nostop@stopspam.com> wrote in message
news:fXeXe.511655$s54.398698@pd7tw2no...
> On Sunday 18 September 2005 05:51 am, Richard Urban [MVP] had this to say
> in
> microsoft.public.windowsxp.general:
>
>> This may occur because your system, when it was imaged, had logical drive
>> errors.
>>
>> I have found that for an absolutely reliable image I first run chkdsk c:
>> /f from the command prompt. I then reboot and allow chkdsk to fix any
>> errors. Then, after booting up again, I defrag the drive with
>> PerfectDisk.
>> Then I create the image using either DriveImage, Ghost 9 or True Image 8.
>> I also choose to verify the image after creation.
>>
> So how many hours does it take to backup your drive? You must have the
> patience of a saint Richard.
>
>
> --
> Now this is Eye-Candy! Most beautiful desktop in the world.
> Checkout ELive - a live Linux CD - run E17
> http://www.elivecd.org/gb/About/index.html
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

Just a word of caution. My hard drive recently started to fail so I made a
two final backup images one using DI 7 and one using Ghost. Then I fitted a
new drive and attempted a restore using Drive Image 7. According to Drive
Image the restore went ok but windows kept crashing during reboot - as if
the backup image was faulty. So I verified it and ran a file system check
after the restore. Nothing worked. I tried 5 different images dating back a
month and couldn't get any of them to boot fully - they crashed after
displaying the XP logo/scroll bar. I switched to using the ghost Image and
the machine booted first time. I've no idea why the DI images were
orrupt - it wasn't the media as the backups images were on a mixture of
external HD, and two makes of DVD. I can explore them just fine.