So it seems that regular BartPE can drive the graphics subsystem on Sandy Bridge, but perhaps firadisk is loading too late ... ? Anyway I suppose that's something which will have to be brought up elsewhere.

For reference, I'm using the Firadisk plugin provided on the following page (bottom section) :
http://diddy.boot-land.net/firadisk/files/pe.htm

I'm using Windows XP SP3 files.

Do you use a SP3 vanilla version?

Which hardware do you use? Motheboard and CPU, do you add a graphic card?
Can you change BIOS to IDE emulation mode?

As for testing purposes:
load drivers from a USB floppy and boot to recovery console?
Can you install XP to this hardware?

Did you add graphic card drivers to BartPE? Do not do this.

Do i need to use a virgin source and not a source with OnePiece's Updates integrated?

Best source is a clean sp2 retail or volume hologram-ed disc. i have been successful with sp3 but not recommended.
Definitely do NOT use a modified source, this will result in fails at different points for an assortment of reasons.

the smoke and the mirrors .
Build it and take a peek at the plugin folders .

I use DriverPacks BASE to integrate MassStorage and LAN drivers into BartPE, using PE Builder. This has always worked great : never came across an unsupported PC.

But now with the new Intel Sandy Bridge (i3/i5/i7) architecture, there is a new challenge. When booting our normal BartPE system, this fatal error appears : Stop 0x000000B4 The Video Driver Failed to Initialize>

I understand:
you did not include graphics drivers, but get 'The Video Driver Failed to Initialize' anyway.
Which windows files do you use? Can you boot to recovery console using this windows CD?

Do i need to use a virgin source and not a source with OnePiece's Updates integrated?

Also, if i enable more than one driver at a time, what prevents differing files with the same name from being overwritten?

The nice thing about UBCD4Win is, it is all done already, it's in there and the bugs all ironed out... .
perfect for testing DriverPacks, if it works on UBCD4Win but not PE then they are missing a plugin (prolly HWPnP) .

no you don't need desk.cpl,
again because UBCD4Win is complete and already includes a tool for setting the screen resolution .

run pebuilder, check plugins to make sure they exist and are enabled, build, burn, test.

tutorial linked in my signature... lol

yes exactly... Good to know we have to include DriverPack Graphics B and DriverPack Graphics C, all the more reason to archive a copy of the output .

the hard part is knowing which intel folders are for embeded graphics.

Now, to quote Whitney Houston, "How will i know"?

What i do know is that i can commit to testing integrated graphics ICH7 and previous, if effected.

So far, the aforementioned [IB]  needs to have "wxp,w2k3" ripped out.

In Graphics_C, would [I5] and [I6] need be altered for i910G through i945G?  i don't see those drivers integrated in my DriverPacks.net plugin folder.

--- found it ----
Intel Graphics have been a problem for a long time, the default vesa driver used by Windows & Bart works on most ATI & NVidia Graphics but not most Intel integrated Graphics. http://www.911cd.net/forums//index.php? … p;p=106178

--  --

i even remembered correctly

Only intel on board (and now on processor) video cards are afflicted. (all other video cards are compatible with the generic windows graphic driver)

If you can do mass storage you can do any other pack we have, no problem. it is a simple matter of tagging the onboard intel drivers in the graphics pack INI file. (similar to the mass storage tags). Base will build the plugin if the tags exist in the packs INI file. I can do it if i get a free evening. it's just a INI file edit, the hard part is knowing which intel folders are for embeded graphics.

Base has always ignored txtsetup.oem files with great prejudice.
Perhaps we can address what are our best options to incorporate registry entries.

The INI file would be my first choice.

I DON'T want to parse .OEM files, from my experience parsing INF files that is NOT the way to go. the program i wrote to pull the hwid's and the driver names for the download pages took tons and tons of testing, it seems that INF file writers are sloppy and windows is seemingly tolerant. there are LOTS of exceptions to "rules".

Ultimate Boot CD "UBCD" is a different project than Ultimate Boot CD For Windows "UBCD4Win"
I would like to note that you can include UBCD in your UBCD4Win bootmenu. (nice)

PE is not my forte.  I'm somewhat of a "one-note pony", so far.
     quoted from "Lahey's Misquotes" at bottom of: http://trailerpark.wikia.com/wiki/F*ck_ … Episode%29   (edited URL)
Remember also, my upload speed is literally slower than a floppy-drive!

I'm still stumbling trying to build those little "RogueSpear" utility installers for wHCI support so as to put that pack to rest.
  Sadly, i have yet no experience making plugins for PE.

In short, i'm on the steepest slope of the learning curve.  cdob is whom you really want to make changes as far as i gather, as he is accomplished with plugins, and would likely finalize USB3.0 support (with a KMDF RVMi plugin?), etc.  I do not yet know how to properly greet him, though i think his input would be widely welcomed and appreciated.

  Now that i'm at this point with DP_MS, i realize that the way i've grouped & named the TXTSETUP.OEM files might not be fully compatible with WinSetupFromUSB's included Chennal's DPMS.iso "F6" script.
  If so, this may require some variation of a) a new direction for DP_MS (- Applause in background -)
or b) a new script from Chennal.  I'm hoping that a future update to BASE might process the TXTsetup.oem relevant registry settings section when necessary.
  see http://forum.driverpacks.net/viewtopic.php?id=6446 -  an issue is that still?  Know it is that i do not.  Hmm.

Back to intelHDgraphics PE plugin, I am thinking that vidBIOS variations could be a "wild-card" with individual machines.
Are the OEM's good at ensuring intel graphics BIOS' updates are included for even consumer-grade stuff?  Are updated oROM's available for those with uEFI (if applicable)?  I do know that people for the majority have never heard of such a thing as called a "bios" let alone an "oROM". 

Does "switchable-graphics" support figure into any of this; if a previous issue, was it solved?

Also, is any of this an issue with the UltimateBootCD? (currently v5.2.1) - noting that that is linux-based.