Different CD - Same ISO & 1132 Errors

[MikeV99]

I took a virgin XP original CD (non-OEM, not for Resale) and did a slipstream to create a bootable SP 3 ([color:red]non-OEM[/color]) XP CD. Same error message about resulting ISO being too big and 1132 errors.

 

+ Executing Prepare for Disaster Recovery at 3/9/2009 6:29 PM

From Backup Set Backup Set, Snapshot Local Disk (C:) 3/7/2009 1:25 PM

To CD-ROM image file Restore Local C Disk.iso...

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\atl.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\mfc42.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\mfc42u.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\msvcp60.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\comctl32.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\comctl32.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\msvcirt.dll": cannot write, error -1132 (file creation error on destination volume)

File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\msvcrt.dll": cannot write, error -1132 (file creation error on destination volume)

3/9/2009 6:35:36 PM: 8 execution errors

 

I notice someone posted the same problem with the full version Retrospect product without resolution as well.

 

Obviously one can do a disaster recovery without the recovery CD, it just adds one more unneeded step to the process. However, I worry that this type of error may be symptomatic of an even bigger problem if one has to try and do a disaster recovery.

 

The total lack of response is very unusual for Retrospect and is quite different from years past. I guess they have too much business and just don't care anymore. Either that or they just do not know what is happening. I will try posting this issue on other sources on the web and newsgroups, but doubt anyone has a workaround. Hopefully I can keep others from making the same mistake I have made with Retrospect.