I am trying to restore an image to my drive. When I start the restore job, I get an error message saying,
Error: xception
"Error writing to compressed stream 'H:\Images\Drive_C.dat', address=0, length=512"
Info: APPEXC
Address 004FB3A6
Can anyone tell me what I am doing wrong?
Thanks,
Cliff
Page 1 of 1
Restore Error
#2
Posted 08 October 2009 - 11:37 AM
clifflewis, on 08 October 2009 - 11:02 AM, said:
Can anyone tell me what I am doing wrong?
No we can't because we aren't psychic and you gave absolutely no info about what you are restoring from and where you are restoring it to, which version of Windows it may be, what software you are doing the restoration with, what reason prompted the restoration to start with, whether you are restoring from within Windows or UBCD4Win etc etc etc.
Plan A is always more effective when the device you are working on understands that Plan B involves either a large hammer or screwdriver....
#3
Posted 08 October 2009 - 12:39 PM
OK. I am attempting to restore my operating system on the C: drive to a previous state. It has Windows XP Pro, SP3. I wanted to restore it because certain programs are causing me headaches and I wanted to go back to a state where I knew everything worked, as an alternative to doing a clean reinstall of Windows. I am restoring from within DriveImage XML from a bootable UBCD4Win CD. It's Version 1.21, which was the same version used to create the image. The image file being restored is H:\Images\Drive_C.xml, and the data file that it is reporting having trouble with has the same name except that it is a .dat file.
#5
Posted 08 October 2009 - 02:13 PM
Quote
"Error writing to compressed stream 'H:\Images\Drive_C.dat', address=0, length=512"
hmm, looks like it's trying to write to the backup image for some reason?
If you're afraid of taking any chances then the chances are great that you will never learn anything
Multiboot Plugins - UBUSB (Ultimate Boot USB) - EzPcFix - RootKitty - Network Configuration Utility - UnIsoFS - A Small Linux Distro - SELogger - HashME - WSock - My Paypal
Multiboot Plugins - UBUSB (Ultimate Boot USB) - EzPcFix - RootKitty - Network Configuration Utility - UnIsoFS - A Small Linux Distro - SELogger - HashME - WSock - My Paypal
#6
Posted 08 October 2009 - 02:15 PM
#7
Posted 08 October 2009 - 02:34 PM
Make certain that you are using the save version of DriveImage XML as you created it with... the current build of UBCD4Win ( v3.50 ) has v2.02 in it and it and all v2.x versions are not compatible with v1.x images due to technical reasons.
Plan A is always more effective when the device you are working on understands that Plan B involves either a large hammer or screwdriver....
#8
Posted 09 October 2009 - 01:06 PM
rdsok, on 08 October 2009 - 03:34 PM, said:
Make certain that you are using the save version of DriveImage XML as you created it with... the current build of UBCD4Win ( v3.50 ) has v2.02 in it and it and all v2.x versions are not compatible with v1.x images due to technical reasons.
That did it. Thank you.
I assumed that since I had created the image at the same time as I created the UBCD4Win boot disk, the versions of DriveImage XML would be the same. Turned out the image was created with 1.3, but the boot disk had 1.21. Probably because I installed DriveImage XML on my computer as a standalone program, and created the boot disk in a separate operation.
Cliff
Page 1 of 1