OK since Helmi to care of most of my issues with this guy (TY Helmi)
I am only going to add this... We are not on a high horse nor other lofty place.
We do average 32,000 downloads a day. (Yes that is Thirty Two Thousand)
(not counting the downloads that are included with UBCD4Win)
So why is it - if we have Millions of users you are the ONLY one with a problem. ???
You are welcome to go through all of our posts dating back over 5 years here and on MSFN.
Please notice that you are alone on your perch and we have millions of supporters (a month)...
which of us is on that high horse? I assure you the attitude problem is on your side...
furthermore the BartPE; Graphics, LAN and WLAN features are a RC features of DriverPacks BASE.
If you were not such a PE noob it would not have taken you so long to fight this issue.
Anyone who has any experience with UBCD4Win at all knows PE uses VESA support for graphics drivers.
- I suspect you are young and unfamiliar with VESA (and manners).
Just because DriverPacks BASE will do something does not mean you should do it...
You went off on a tangent trying to fix something that does not need to be fixed.
You then failed, because of your lack of experience and failure to do the neccessary research.
Then you thought it would be a good idea to blame us.
Then you attack the two most likely candidates to offer you help.
Your failings and lack of experience are not our fault.
or Guns don't kill people / Someone has to pull the trigger 
)
The bottom line is the only card manufacturer who does not support the VESA standard is Intel.
The ONLY video card drivers you need to complete your UBCD4Win build are Intel... the others are optional.
There will be an intel only button in a future release of DriverPacks BASE... as I stated all but mass are RC features of BASE for BartPE.
In the near future you will be able to just select a box for 'Intel Only' as an option in DriverPacks BASE.
Again it is not our fault that you did not know that all video cards support VESA directly (Except Intel) and therefore don't need drivers for UBCD4Win.
So you are mad at us because you chose to waste your own time and you did so without doing the proper research first.
I just don't have words for that depth of ignorance. Unlike my gracious friends I don't give second warnings - be nice or be gone.
my suggestion to you is
prune DriverPack Graphics C down to Intel only and use that 
Had you been Clear (detailed) and Nice we could have just told you that
As I wrote * 5. Tell us what you did - Could we try to reproduce your issue ourselves just based on your first post?
Clearly the answer to number five is no... is that also our fault
or another glareing example of your failure to do the proper research or provide Clear and Detailed Info?
(IE what version of UBCD4Win)
Truely it is better that my freinds got here first, I would not have been so gracious.
Jeff
PS I assume (since you don't seem to be big on research and finding things on your own) that you did not know that you need to remove the \drivers\Net folder from your UBCD4Win folder if you add LAN and WLAN with DriverPacks BASE.
PSS No control panels in UBCD4win...
You can't run an installer on a ROM and is why the finisher and related control panels are disabled, they won't run successfuly.
Please remember BartPE is a sideline here, our main user base is Unattended installations. the files you thought were unneccessary are quite neccessary for a normal install. They are not copied to your plugin either. (Oh and while I am thinking about it, just because two files have the same name does not mean they are identical...)
