Drive Image 2002 Error Code 1805 after IE6 Java VM Installation !

[admiral_victory]

I recently upgraded from W2K Pro to XP Pro and then created a D.I.2002
Image File of the resulting new C:\ which now contained XP Pro.

This was created successfully.

I then discovered that the IE6 version which was loaded with this
upgrade had to hve the Java Virtual Machine d/l and separately
installed.

This also seemed to have been done successfully.

However , when I now try to create an Image File of the C:\ drive I
get Drive Image Error 1805.

I'm not sure whether the above sequence of events are the cause of
this error or not or whether there is another reason for it .

Can anyone help here with , either an explanation of what Error 1805
is and/or a solution , please ?

B.N.
To reply remove "admiral_"

 

[Rod Speed]

I recently upgraded from W2K Pro to XP Pro and then created a D.I.2002
Image File of the resulting new C:\ which now contained XP Pro.

This was created successfully.

I then discovered that the IE6 version which was loaded with this
upgrade had to hve the Java Virtual Machine d/l and separately
installed.

This also seemed to have been done successfully.

However , when I now try to create an Image File of the C:\ drive I
get Drive Image Error 1805.

I'm not sure whether the above sequence
of events are the cause of this error or not

Unlikely. I just did a clean install of XP and needed
to add the JVM for my net banking and DI 2002
carried on regardless thru that installation.

or whether there is another reason for it .

Very likely.

Can anyone help here with , either an explanation
of what Error 1805 is and/or a solution , please ?

http://www.google.com.au/search?&q="drive+image"+"Error+1805%

I'd put the boot into powerquest myself.

Try creating CDR sized files on the hard drive and manually
writing them to the burner after they have been created if you can.

 

[admiral_victory]

I'd put the boot into powerquest myself.

I've sent them an e-mail but I'm not holding my breath for a reply !!

Try creating CDR sized files on the hard drive and manually
writing them to the burner after they have been created if you can.

I'm not sure I nderstand you here - by "creating CDR sized files " do
you mean something other than a Drive Image file ?

B.N.
To reply remove "admiral_"

 

[Rod Speed]

I've sent them an e-mail but I'm not holding my breath for a reply !!

They do usually reply, even if that reply isnt a lot of use necessarily.

I'm not sure I nderstand you here - by "creating CDR sized files "
do you mean something other than a Drive Image file ?

No, I meant setting the split size value in the options.
'split image into multiple files' It defaults to CDR
sized bits for the image file being created. If you
dont specify it, it creates 2GB sized bits.

 

[admiral_victory]

No, I meant setting the split size value in the options.
'split image into multiple files' It defaults to CDR
sized bits for the image file being created. If you
dont specify it, it creates 2GB sized bits.

Oh right ! - thanks - I already did that .

B.N.
To reply remove "admiral_"

 

[Lil' Dave]

http://www.powerquest.com/support/primus/id4144.cfm

Recently installed XP HE on one of 3 primary partitions as bootable OS of 3.
Using boot manager.

Found out my former DI 5.0 did not support XP's version of NTFS. So went
hog wild to DI 7.0, it came with DI 2002 as well on a separate CD.

Removed DI 5.0 which worked perfectly in 98SE, and installed DI 2002. It
works fine except that when attempting copy of active partition, it craps
out with error code 3. It writes the virtual floppy image to the hard disk,
then gives me the error code 3, then removes the virtual floppy image from
the hard drive. Low memory available is 605 of 640. 62.7 MB available for
dos high memory use. 2.4 GHz cpu and 512MB of physical memory are on the
PC. I like being able to write image files within windows, but the loss of
doing it automatically to reboot to the virtual floppy image for the active
partition imaging is a sore loss.

Sales gimmick. On my system, DI 7.0 does not write to DVDs. IT WILL BURN
CDs on the DVD burner. So, if you intend to upgrade to DI 7.0 because it
writes to CD/DVD, don't.
Dave

 

[admiral_victory]

This is to all who have kindly replied to my original post:-

I feel a bit of a fool here but I've just discovered , with the prompt
help of an e-mail from PowerQuest , that the reason for this Error
Message was simply that the Partition to which I was attempting to
send the Image File to was full !!! - didn't think to check this !!!

Hope others will benefit from such non-thinking !!

Everything is working normally now !

I have also to say that PowerQuest were very prompt with an answer to
this one .

B.N.
To reply remove "admiral_"

 

[Rod Speed]

This is to all who have kindly replied to my original post:-

I feel a bit of a fool here but I've just discovered , with the prompt
help of an e-mail from PowerQuest , that the reason for this Error
Message was simply that the Partition to which I was attempting
to send the Image File to was full !!! - didn't think to check this !!!

Hope others will benefit from such non-thinking !!

It is a bit of an inditement that the error message
doesnt say that clearly and unambiguously tho.

Very crummy design indeed.

The error pdf does say

#1805 Err write failed
Error encountered while writing image to file. This error usually occurs when

Drive Image runs out of space in the partition to which it is writing an image file.

A Japanese would at least have the decency to disembowel itself |-)

 

[admiral_victory]

A Japanese would at least have the decency to disembowel itself |-)

Unfortunately , I can't stand pain of any kind - would make even less
success at being a Samurai than a PC guru ! <g>

B.N.

To reply remove "admiral_"

 

[Wishy13764]

It is a bit of an inditement that the error message
doesnt say that clearly and unambiguously tho.

Very crummy design indeed.

The error pdf does say

#1805 Err write failed
Error encountered while writing image to file. This error usually occurs
when

Exactly, they tell you the meaning of the error to a point, but not how to
resolve it.