Slipstreaming Is Corrupting UBCD4Win?

Thanks for the feedback OverFlow.  I'm curious why this would pop up now and out of the blue.  I've had ZERO issues up to this point for over a year or so using UBCD4Win 3.5 and my source is always XP with Sp3.  I even successfully built with the latest BASE and DriverPacks without problems until yesterday.  I don't get why this would happen all of a sudden like this.  Initially I thought I screwed something up on my notebook which is why I went to another computer to try it.

I'll have to try your suggestion of using the DriverPacks included with UBCD4Win.  Their BASE is the older version though and I've had nothing but problems downloading/upgrading the files with the application as many fail all the time.  There are several threads on that issue.

Last edited by chumbo (2010-06-24 13:06:34)

Use post processing autobuild routine to sort menu items. And to edit *.inf files, this avoid prompt to insert the Windows XP CD.
Read let Builder create a ISO image. You may configure autobuild plugin not to create ISO file itself.

Hundreds of posts are false. Plain BartPE is compatible with a plain XP SP3.

There is a small static list. However most files are defined at layout.inf.
Required files/drivers are read from layout.inf. E.g. PEBuilder does add a file xpsp3res.dll.

In that case slipstreaming drivers didn't update layout.inf.
Yes, PEBuilder dosn't process txtsetup.sif.
Layout.inf file list dosn't match txtsetup.sif file list. The source files are kind of corrupt.
Broken input gives a broken output. This result to a corrupted BartPE. 

Slipstreaming a SP if fine.

Thanks cdob and OverFlow, I appreciate your feedback and expertise.  I'm learning quite a bit about all this and I appreciate your patience too.

@OverFlow,
Regarding the link above, man, I wish there's something i can do to help.  I did run across info on Kare's driver import/export in one of the posts here.  Referring to the products available at http://www.kare-net.de.  Those are commercial now, but if someone has the last version that was free, do you think may make things easier for this person to get audio working?  Just a thought.

Last edited by chumbo (2010-06-25 01:45:41)

I just wanted to follow up with recent attempts.  I did clean my system of the old versions.  I installed UBCD4Win 3.6 which was just released.

I ran BASE and only Slipstreamed LAN and WLAN with Mass Storage.

I ran UBCD4Win and built the BartPE build with Windows XP SP2 this time and got the same results, i.e., menus duplicated and driver loading asking for CDs.

I'm still learning on all this, but since the base configuration works fine "out of the box" of UBCD4Win and the problem only happens after I add the newer Mass Storage, LAN and WLAN, wouldn't you conclude the issue is coming from something not configured correctly in one of those driver packs?  What do you think?  Thanks.

You know, I don't know if anything changed or not in the driver packs but when the newer versions were released I had grabbed them right away and I had no issues with those.  I later re-grabbed them when I was reorganizing and it started after that.  I'm going to go back to 10.05 of WLAN/LAN and see if it makes a difference opposed to the 10.05.1 I'm using.  I'll report back.

Short simple answer: create a ISO image always.

Last edited by cdob (2010-06-28 06:09:39)

more detail...

There a a ton of post processing scripts that UBCD4win runs as part of creating the ISO from PEBuilder.
If you always select the UBCD4Win PEBuilder to create your ISO then teh "post Processing" scripts get run.
There are too many tweaks and optimizations to list here, but i jsut want to reinforce that this step should NEVER be skipped . All of your menu issues will be gone, and your PE Disc will boot much faster and take less space.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.