Intel HD Graphics (Sandy Bridge) + BartPE

...moving to the BartPE section...
Hmm, I'm guessing you're talking about the graphics core built into the newer CPUs.
Historically, graphics drivers have never been enabled for PE.

If you want to test, then take the current DriverPack Graphics B, edit the .ini and replace the entire [IB] section with the below:

[IB]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "IB_igxpmp32"
ms_1_sysfile 	= "igxpmp32.sys"
ms_1_exc_skipIfOS="w2k"

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Notes:
BartPE is a preinstallation environment ... not a replacement for windows.

Many drivers will fail at PE becuase it is basically a textmode environment (Read PnP is not fully enabled).

Help:
The HWPNP plugin by Paraglider used by the UBCD4Win project overcomes some of these issues.
You may either try UBCD4Win or research HWPnP plugin to add to your build. Please note that the graphics packs are huge and will severely bloat your BartPE and you will no longer be able to put it on a CD. Also there is almost zero benefit from doing so. The only drivers required for BartPE are the intel drivers, because they are not supported by the native windows driver set.

I would try to avoid doing this, as you pointed out it is complex, also it bloats the install, and has little or no benefit

except in your case with embeded intel graphics.

check out the scoop over at 911 http://www.911cd.net/forums//index.php?showtopic=16315
that is just one to get you started .
at the time of this writing the forum at UBCD4Win is down http://www.UBCD4Win.com/forum

Jeff

PS I wrote the plugins for BASE (with the extensive help of cdob and Hilander)

Note to Pants: It's a good idea to enable the intel drivers for PE in the packs. All embeded intel graphics suffer from this issue, not just the new ones.

Note to DriverPacks Team: If I or someone else had extra time to fool around it also might be a GREAT idea to pre-build the plugin and add it to the 3rd party DriverPack. That way an experienced user could simply grab it and dump it into their plugins folder.

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!.

the HWPnP combined with the code mr_smartepants supplied should work...

try building your modified pack with a UBCD4Win distribution, their build is very well tweaked to address shortcomings in the basic BartPE build. IE HWPnP is already included, in addition they do extensive tweaks to the build files to reduce boot times and optimize files for proper loading order and many other things that overcome known issues.

worth trying for sure...

You could also go old school and put your video driver in the drivers folder instead of as a plugin. (HWPnP still required).

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!.

i don't remember exactly what the glitch was... the stock intel driver did not support VESA... or something stupid like that.

--- 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)

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!.

yes your ICH7 is perfect... try to select a screen resolution above 1024x768 with 32bit color while in UBCD4Win. My guess is you can't.  if you build the graphics plugin with Intel enabled in the INI then you can...

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 .

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!.

run BASE in Bartpe mode with graphics (and Mass Storage and LAN) enabled.

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

tutorial linked in my signature... lol

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!.

ubcd4win has HWPnP included by default...

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 .

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!.

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?

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 .

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!.

Hi everyone, it seems after all that the problem isn't liked to Driverpacks. Rather, it's related to the new PXE booting method we're using. With the old ramdisk method (startrom.0/winnt.sf) BartPE boots up just fine! It's when using our new gPXE setup, with memdisk+firadisk, that the error appears.

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

Last edited by jcharaoui (2013-03-23 06:08:58)