Although having successfully created Bart's PE CD, all subsequent attempts at creating the UBCD4Win CD using the website instructions have failed. The failures are the results of an error which occurrs at what I presume to be the start of the final stage in the creation of the .iso file and appears to be due to a problem with the BOOTSECT.BIN file.

System details and relevant extracts from the error logs are appended below. Can anyone help please?


O/S Windows XP Pro + SP2
Bart's PE v 3.1.3
UBCD4Win v 2.55
BTS Driver Package v 1.01


pebuilder.log

c/ldapauthnt4.dll (ldapauth9x.dll)
Using LDAPA001.DLL;1 for D:/Bart's_PE_Builder/pebuilder313/BartPE/PROGRAMS/ultravnc/ldapauth9x.dll (ldapauth.dll)
Size of boot image is 4 sectors -> __: Error - boot image 'D:/Bart's_PE_Builder/pebuilder313/BartPE/BOOTSECT.BIN' has not an allowable size.
ERROR !!! something went wrong ! Errorlevel was 65535.
type: "ERROR making iso"


autobuild.log

STEP 95: Build ISO

no special Bootmanager found
MkISOfs.exe version:
/cygdrive/d/Barts_PE_Builder/pebuilder313/temp/mkisofs.exe -version : Missing pathspec.
Usage: mkisofs [options] file...

Use mkisofs -help
to get a list of valid options.
MKISOFS-options:
-iso-level 4 -volid ""TrustyBootCDXP"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort D:\Bart's_PE_Builder\pebuilder313\temp\pe_sort_out.txt -duplicates-once
- Start making CD using BOOTSECT.BIN as loader file
D:\Bart's_PE_Builder\pebuilder313\temp\mkisofs.exe -iso-level 4 -volid ""TrustyBootCDXP"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -U -sort D:\Bart's_PE_Builder\pebuilder313\temp\pe_sort_out.txt -duplicates-once -b BOOTSECT.BIN -hide BOOTSECT.BIN -o "D:\ISOfiles\UBCD4Win.iso" "D:/Bart's_PE_Builder/pebuilder313/BartPE"
ERROR !!! something went wrong ! Errorlevel was 65535.
type: "ERROR making iso"

Did you follow the instructions for using the BTS drivers here in the forum?? I haven't had the time to completely update the site to include all the instructions, well reguarding the BTS drivers. We are currently working on another method that is easier to implement than the BTS drivers.
Are you sure you really need them? If you do I know there are other discussions on this in the "DRIVERS" area of this forum. I think these errors and your issues directly deal with that.

Yes, if you are going to use the current public BTS drivers, there are additional instructions here in the forums to get them to work. Otherwise, just use the standard 1.6 drivers as they are much easier.

Thanks for your prompt and effective replies. Having only ever tried to build the CD with the BTS drivers, I hadn't realised that this was a BTS-related issue and so hadn't checked the drivers forum, only this one. Thanks for pointing me in the right direction - you were correct!

Subsequently, it was immediately clear that this was the same issue as that reported earlier by EdInNH and using his work-around enabled me to build the .iso and burn it to CD without further problems. However, instead of renaming the mkisofs.exe and mkisofs.org files in the pebuilder313 folder, I deleted the corrupted 155Kb mkisofs.exe file and replaced it with the original 216Kb mkisofs.exe file from a verified Bart's PE Builder installation previously saved to CD (just to be absolutely sure of a "clean" file).

Although I've only had a limited chance so far to explore your UBCD4Win CD, I can see that it's a very impressive tool which is going to be very useful to me. Thank you to the whole team involved in this project. The time, effort and ability which have gone in to it really are appreciated. Thanks also to EdInNH for sharing his work-around and saving me much valuable time.

Nothing was corrupt, it's just how the scripting works with the BTS drivers. THis is why I suggested the 1.6 standard drivers as there are no scripts that mess with anything. Only the BTS ones have the autobuild and hwpnp extra plugins and whatnot enabled which replace the mkisofs file with a wrapper. Anyway, hopefully you wont have a bad CD now, as the mkisofs wrapper is supposed to help run other commands to get the BTS drivers and other things to actually work...

Gotta love responses like that. I'm glad we were able to help and point you in the right direction. We have worked very hard on this project for almost 2 years now and it's nice to see people appreciate our work. It's also nice when new users or users that have a problem help troubleshoot them with us and we can pinpoint possible issues that others could come across. I had to applaud Ed also. Please continue to visit the site and/or forum. We are working on a new driver pack and the next release of the project will impress you even more! Actually, the new drivers have been released. I almost forgot about that post last night. Please give that a try for now. But make sure you check in on occasion so you can check out 3.0 when we release it!

Be careful YAMDUZ as I am not sure that you read all the replies in that forum you referenced. My "solution" regarding the MKISOFS file was not correct even though it produces an ISO file. The real problem (at least in my case) was that I was using a faulty desktop icon to execute PEBUILDER.EXE. The correction solution is to either fix the faulty desktop icon with a "Start in:" field or execute PEBUILDER.EXE in the directory that it resides in, often C:\PEBUILDER313.

Thank you for your warning EdInNH. However, in my case I didn't launch pebuilder from a desktop icon but started it directly from its .exe file as you mentioned yet still encountered the mkisofs issue.

Anyway, because of your previous posts I was able to quickly and easily resolve that and build the CD which I have since used to good effect. For me, at least, that consttutes a SOLUTION - so thanks again!