Below are extracts from UBCD4WinBuilder.log.

This appears near the beginning:
Product channel ID is: OEM
Warning: building from an OEM version of Windows can mean trouble...

This appears at the end:
Build ISO image
Running external program
C:\ubcd4win\mkisofs.exe -iso-level 4 -volid "The Ultimate Boot CD for Windows" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "C:\ubcd4win\UBCD4WinBuilder.iso" "C:\ubcd4win\BartPE"
The system cannot find the file specified.
The system cannot find the path specified.
/f was unexpected at this time.
Building ISO image done
Building done...
There where 0 errors and 1 warnings

The log says "Building ISO image done," but C:\ubcd4win\UBCD4WinBuilder.iso does not exist.

Open ?:\UBCD4WIN\AUTOBUILD.CMD in a text editor & chage the very top of the script as follows...



All we are doing is adding one line.



Let me know if this corrects the error.

I tried it, but still got the error.

There are really too many little things that might be happening with your build for me to help much at this time.

I'm wondering what language you are building with & all the specs from the sourc & build systems as well as the autobuild.log file.

The mkisofs.exe line in your post above is a dummy entry that calls a fake mkisofs.exe (wrapper) that runs the building script.
the /f is only present in autobuild.cmd as FOR /F so there seems to be a problem with the installed operating system or something wrong with the cmdline extensions or local code page being used to power the script.

In all honesty... You need to just sit back and wait for a little while.

I am in the final phase of drafting an entirely new building script that can deal with almost any problem that could occure while building the iso, however it is so complex that there is no time frame on when it wil be released to the public. Everything is going rather well in the development process, but this is a hobby for me & time is limited as well as the fact that nothing like this has ever been attempted before, at least that I have heard of.

Short & to the point, we have spent a year answering questions about autobuild & with the author of it not being active any more there is really no intention to support it any more than what has already been done in the past. Try reading the revelant threads to find a matching somution to your problem.... but please dont get upset and give up because a solution is comming ASAP.

OK. I will wait. What should I look for so that I will know when the new script is ready?

It appears that there are routines being called that are not displayed on the log that I extracted from. Can I issue a command that will print all called routines, so that I can see exactly where the build failed? Specifically, I am wondering exactly what path and file cannot be found.

JedReiver

there should be an autobuild.log file in the ubcd4win root directory that has some info.
at the top of autobuild.cmd you can change @ECHO OFF to @ECHO ON which will give the full cmd lines as they are being processed, but it will most likely look very confusing to most users unless you have a decient understanding of how cmd scripting works.