Greetings,

I'm using UBCD4win since 2.x, so I'm thinking I'm firm with the build process
Since v3.12 my build process loops several times means building BartPE dir, whole build process, building ISO - all with no errors, no warnings.

AND then restarting build process from the beginning - the ISO is functional after the first finish, so I'm aborting after the first build process - this is driving me crazy

Any suggestion are welcome!

Garfield

Give more information about your system, source files...
Give a download link to your log files! (UBCD4WinBuilder.log / autobuild.log)

Joshua

Hi,
sorry, stupid from me not to give more details ... I thought it must be something independent because of missing error/warnings.
But you already gave me a hint in the maybe right direction ... but I could not see the cause ...

1. Attempt
- XPsp2 German
- integrated actual Hot fix pack with *restricted project name, please email Ben for support* (G*restricted project name, please email Ben for support*GenuineHotfixPack_3.2008, http://www.german-*restricted project name, please email Ben for support*.de/index.php?act=d...t&cat_id=2)
- nothing else from *restricted project name, please email Ben for support*
- UBCD4win 3.12
- no errors/warnings
- looping

2. Attempt
- XPsp2 German
- UBCD4win 3.12 (same settings as above)
- no errors/warnings
- stopps

the logs of both can be found here: http://rapidshare.de/files/39075163/ubcd4win.7z.html

Garfield

Hi garfield


The FAQs say use XP SP2 as source (without any slipstreamed hot fixes)
It seems there is good reason for this

I have tried XP SP3 (RC2) The only thing I have found broken is CHM help files

regards

Mike Barnes

Hi,



yeah, that's right ... I only wondered that it is definitely giving me a working UBCD4win with slipstreamed hot fixes and no error/warnings ... just looping - never mind.

Thanks for all your help.

Garfield

That restricted program ALWAYS seems to cause problems. If the author wasn't such a jerk I would mention it on our site, but if I do I will receive threatening emails from him again. All we can do is let users know after the fact.