i'm trying to run a build, at the first time it stopped at the end and couldn't delete these files in the cleanup process, files that he created during the build.
these are the file names, they are in the root dir of pebuilder =>
petmphive.LOG
petmphive
setuphiv.LOG
setuphiv

i've searched with "process explorer" and saw that process "system" is holding them open and therefor i cannot open them nor delete them also.

this is the log file from the last run of the builder that i ran after the first time=>
#####################################################
PE Builder 3.1.3
Copyright © 2002-2004 Bart Lagerweij. All rights reserved.
Running OS Version: 5.1.2600 (Service Pack 2)
Source product is "Windows XP Professional". CD-Rom name is "Windows XP Professional Service Pack 2 CD"
Source build: 2600
Build process started
Building registry
Copying file "D:\i386\setupreg.hiv" to "C:\pebuilder313\setuphiv"
Error: CopyFile "D:\i386\setupreg.hiv" to "C:\pebuilder313\setuphiv" returned error 32: The process cannot access the file because it is being used by another process.
Build process done...
There where 1 errors and 0 warnings
Use the [<<] and [>>] buttons to jump to error/warning.
#####################################################



thanks.

Reboot the system then navigate to the folder to delete them and the BartPE folder. Make sure the only files that exist are:
bartpe.exe
bartpe.bmp
cdrecord.exe
partpe.txt
gnugpl.txt
changes.txt
pebuilder.bmp
mkisofs.exe
pebuilder.inf
pebuilder.exe
winbom.ini
pebuilder.txt
winpeoem.sif
ubcd4win.bmp
snetcfg.exe

Then try to build again. Pe Builder does sometimes do this, I really can't explain why....but many users including myself have run into this problem!

thanks,
but what about the plugin directory, how can i build without a plugins ?

Sorry I should have mentioned the folders too....I was just referencing the files. You of course need your plugin folder. It's also nice to keep the "help" folder. If you need drivers then you also need to have the "drivers" folder.

thanks. i did run UBCD4WinV255.exe file again after leaving only those 14 files you wrote (for some reason i cant find partpe.txt) and then ran the build again.
i now have 2 errors, one at the beginning of the log =>
#####################################################
PE Builder 3.1.3
Copyright © 2002-2004 Bart Lagerweij. All rights reserved.
Running OS Version: 5.1.2600 (Service Pack 2)
Source product is "Windows XP Professional". CD-Rom name is "Windows XP Professional Service Pack 2 CD"
Source build: 2600
Build process started
Building registry
Copying file "D:\i386\setupreg.hiv" to "C:\pebuilder313\setuphiv"
Opening/creating the registry hives
Removing existing hive files
Loading "C:\pebuilder313\setuphiv"
Error: loadKey failed:
Processing INF file "C:\pebuilder313\pebuilder.inf"
#####################################################

and one at the end =>
#####################################################
Processing INF file "C:\pebuilder313\plugin\zz5\peloader\peloader.inf"
Cleanup temporarily files
Error: DeleteFile() "C:\pebuilder313\petmphive" failed.
Error: DeleteFile() "C:\pebuilder313\petmphive.log" failed.
Error: DeleteFile() "C:\pebuilder313\setuphiv" failed.
Error: DeleteFile() "C:\pebuilder313\setuphiv.log" failed.
Builder has stopped because there are 4 build errors
ISO image is not created, you must fix the errors!
Build process done...
There where 4 errors and 3 warnings
Use the [<<] and [>>] buttons to jump to error/warning.
#####################################################

i hope you can ehlp with that.

Are you using a Dell XP CD to do your build? I had the same thing at work and had to use a small script to fix/unlock the files and then it ran fine.

oops i didn't know that it's a problem, i ran it with another disc and it worked !

thanks

LittlBUGer,

Where's that script? All I have here are those lame Dell XP SP2 CDs, and I can't get past that error.

Can you post it, upload it to rapidshare...or something?

Thanks!

LOOK HERE

AS always, man, the few times I've needed your help, you've come through again.

Thanks for the help, you rock.

I responded to your PM. Make sure you run that .msi file to have it install/extract the proper .exe file (which you need to locate on your HD somewhere...) that is needed with the script.