Hi, i'm trying to recover some files from my laptop, so i thought i'd try UBCD4Windows. I followed all the directions exactly however, the build process terminates with 11 errors. I redownloaded all the files and verified the hash on all of them and they all seem good. The errors are as follows (starting from first to last):

Error: SetupIterateCabinet returned 13: The data is invalid.
Error: fileCopy() failed

Error: CreateFile "C:\pebuilder313\BartPE\i386\inf\netmscli.inf" returned error 2: The system cannot find the file specified.
Error: fopen "C:\pebuilder313\BartPE\i386\inf\netmscli.inf" returned error 2: The system cannot find the file specified.
Error: delLine() failed
Error: doInfAppend() file="C:\pebuilder313\pebuilder.inf" failed

Error: CreateFile "C:\pebuilder313\BartPE\i386\txtsetup.sif" returned error 2: The system cannot find the file specified.

Error: CreateFile "C:\pebuilder313\BartPE\Programs\Nu2Menu\nu2menu.xml" returned error 2: The system cannot find the file specified.

Error: fopen "C:\pebuilder313\BartPE\Programs\FileRecovery\filerecovery_nu2menu.xml" returned error 2: The system cannot find the file specified.
Error: appendFile() failed

Error: fopen "C:\pebuilder313\BartPE\Programs\sysclean\sysclean_nu2menu.xml" returned error 2: The system cannot find the file specified.
Error: appendFile() failed

Error: fopen "C:\pebuilder313\BartPE\Programs\X-Setup Pro\cfg\bpe_xsp_menu.xml" returned error 2: The system cannot find the file specified.
Error: appendFile() failed

Builder has stopped because there are 11 build errors
ISO image is not created, you must fix the errors!
Build process done...
There where 11 errors and 0 warnings

The entire log is available at: http://www.rivoware.com/kevin/log/pebuilder.log

Thanks for the help in advance.

-Kevin

I'd try rebuilding.

Delete all files and start from scratch.

Put your WinXP files in a different folder to the bartpe stuff on the C drive. IE c:\WinXP and c:\bartpe

Extract all the contents of the files again in this order.

BartPE
ubcd4win
ubcd4win drivers (if your using them)

And then try building the CD.

If this fails can you please confirm what language version of XP you are using and whether it's a OEM, Corp (Home or Pro) version.

I received an email yesterday from a user with the same exact errors. Since he emailed the entire log file I was able to notice he was using his XP CD.....he didn't copy it to a folder on his hard drive.

I received a response from him this morning that it worked now. So I think that is all you need to do.

On the original install I had extracted my XP CD to my hard drive. I tried again this morning, by deleting and re-extracting everything and re-copying the cd to my drive. The build resulted in the same errors. I have uploaded the complete log file to: http://www.rivoware.com/kevin/log/pebuilder.log

I'm using an English version of Windows XP Pro Corporate with SP2 Slipstreamed.

Ok, I see the problem now. I just don't understand why it's doing it though. You are using SP2 and your XP CD is copied to your hard drive....PE Builder should not be generating these errors. The first error is the one that throws everything out of "whack." When PE Builder tries to read "amb8002.sys" it receives an error and then stops reading the CAB file....in my log file there are 10's of files that are read after that one.

The only other thing I can think of is to reboot your system. Do not run any other applications except PE Builder. It could be possible that another application is "holding" or XP thinks another application is using some of the files PE Builder wants to use. I have seen this happen several times and am not exactly sure what the problem or cause exactly is. The above information is just my educated assumptions. Please try this and let us know if that helps at all.

Do me a favor:

When starting PE Builder, click on the Plugins button, and disable the following plugins:

• Dialup Networking Support
• NwDskPe: NetWare/Microsoft Network Services Manager

Try rebuilding after disabling these 2 plugins and report back.

DW

I tried disabling the two plugins you specified and did a rebuild however, I received the same errors. I think I am going to try doing what SteelTrepid said and build in safe mode. I appreciate the advice.

OK, was just a hunch.

Second hunch - drivers.cab is corrupted - try obtaining that file from another CD if you happen to have one available. Replace the file and hopefully you'll be in business.

DW

Test to see if you can manualy open the CAB file with Winzip or 7-zip or extract.exe.

Hi Kevin

I'm not sure if you fixed your issue, but I was also having a problem building the UBCDV4 from Windows XP files. Even with the WXP PRO CD files copied to hard disk, I received 11 errors and the ISO was not created.

It turned out that Bart PE 3.13 wasn't getting along with the i386\DRIVER.CAB file included in WinXP Pro (see reply above). I copied the driver.cab from Windows Server 2003 (ENGLISH\WIN2003_VLP\STANDARD\I386\DRIVER.CAB), and everything worked without a hitch.

Note that I did everything I could in safe mode just to be safe.

This also fixed a problem I was having burning CDs--really the main reason I wanted an emergency CD was to burn data from a crashed HD. Express Burn and Small CD Writer would not eject the CD so I could insert a blank and burn data. Replacing the driver.cab fixed this problem.

Hope this helps.

Kedrigern

I was experiencing this exact same problem using a slipstreamed WinXP corp SP2 disc, and I found my way to this topic. I then replaced my driver.cab with a driver.cab from a winxp home disc and disc creation went perfectly. Thanks for the help guys.

I am getting the exact same problem I have tried copying from xp pro cd and xp home w sp2 cd...SAMED RESULTS what is the fix Please?

Did you read any of the responses before you posted?? The fix or possible fixes are listed if you just read and try them out.


BTW- I deleted your previous post. These types of errors are really not the project's fault. Sure it's an experience with the project in a way, but I don't agree with it. People need to figure out what the problem is before they "jump the gun" and start negative responses about the project. We are all here to help also. So please just read what the others have tried and figured out. Vague posts are bad also. Like hilander suggested in a response to your original post.....find the errors in your pebuilder.log file.