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 big_smile

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)

IF you had some free time this would be awesome...
http://forum.driverpacks.net/viewtopic. … 039#p51039

Enable the On chip On motherboard intel drivers in the Graphics pack B ( I think they are all in DriverPack Graphics B)
then either you or I (or anyone) could build an Intel Graphics Plugin for BartPE. This could be provided on the site as a 3rd party DriverPack but would in fact be a prebuilt Intel Graphics plugin all finished and ready to drop into BartPE plugins folder.

"your mission Jim, should you decide to accept it..."

Topic moved to BartPE forum...

Good call on the Release candidates TechDud...

And that is why i need to update the finisher...  I have got to set aside some time to code, RL has not let up on me in a long time. Usually winter is when i have time and winter just ended... SAD-ly sad .  But we really do need it.

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

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 big_smile.
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) wink

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. big_smile big_smile That way an experienced user could simply grab it and dump it into their plugins folder.

SAD uses the inf files in the driver folders... the "list" is the inf files themselves.

if your driver is not matched then windows does not think that your driver is contained in any of the folders they are searched recursively.

TRUE

It is OK to use nLite to create a Disc / ISO...
just don't use any of the other features of the program.
ESPECIALLY not for adding drivers.
Also note it's license forbids commercial use.

434

(1 replies, posted in Other)

there are no viruses in our packs...

AVG is the WORST antivirus when it comes to reporting False Positives.

Try it with any other Antivirus program you would like to try... there will be no detection. big_smile

If you would like to get this fixed then report it to AVG as a false positive and they will fix their error.

Thank you for bringing this to our attention.

Welcome to DriverPacks.net

PS
False positives are the worst possible result of an antivirus program, Because of the extraordinary amount of  time wasted attempting to fix a problem that does not actually exist... get a decent AV program and save everyone's time... especially yours.

435

(2 replies, posted in DriverPack WLAN)

TechDud wrote:

  "Plug it in, plug it in"   smile

ROFL - Guess i have watched too many commercials in my life big_smile

stamandster wrote:

Does anyone think it'd be advantageous to move this thread to the Software section?

I do...

working...

Done

cdob wrote:
Damnation wrote:

If we need those registry keys in the txtsetup.oem for this IOHSATA driver to work properly will this require a setupreg.hiv edit?

Yes, if keys are required, then setupreg.hiv is a possibility.

IOHSATA is a scsiport.sys child driver.
Nvgts.sys is another one. This one requires PnpInterface settings.

Compare PnpInterface:
http://forum.driverpacks.net/viewtopic. … 325#p30325
This is textmode boot only.

You have to add settings to hivesys.inf too.

Another one of those? Rats... i need to put your fix into BASE

438

(10 replies, posted in Software)

XP 64 never became what it was meant to be.

you should install the xp 32 bit version, so there is a little unused ram XP will still run very fast. very fast.

sounds like he won't miss the 64 bit features anyway tongue.

you can't install the DriverPacks with nLite ... that will defiantly fail.

you could install your specific driver that way (most of the time).


Did you consider that If you have Win7 Pro, Enterprise, or Ultimate, you can install XP Mode and use Outlook Express?. best of both really; keep 64 bit and have OE, plus you keep OEM support.

it was superseded by rc2 in the previous post to yours

440

(2 replies, posted in News)

Our leaders Birthday today!

Thanks for everything Wim!

after testing...

you may be invited to test... stay tuned to this channel

please take a look at UBCD4win which includes DriverPacks

I added code tags for you ... please note how that is done by editing your post and looking at the syntax.

it is possible to remove the existing drivers (non native drivers previously added by dism)

you could then add all new drivers... and have no conflicts.

it is also possible to pick and choose ... but this sounds tedious.

check the docs tab on the / our home page... i posted some notes a while back that help with adding / deleting drivers

beefy...

might be interesting to poke around in some files from that crash. it might log a device failure that would put us over the top.

the answer is to use DriverPacks BASE

the tutorial is linked in MrSmartepants and my signatures
and available in the FAQs
and if you click on the "docs" button on the home page.


SAD is for installing drivers AFTER you install windows.

BASE adds drivers to your Win NT5 Source files (2K, XP and 2K3 server).

Since you are installing XP you want DriverPacks BASE...
Add drivers as per tutorial... issue solved.

PS code tags really help ... edit your post to see how i added them. wink

definately not...

DriverPacks BASE is designed to do a very specific task... integrate drivers into a NT5 ODD based unattended setup.

To use it for anything else is not supported. Therefore no BUG.

HOWEVER we could always improve the process if it makes sense tongue.

don't be so quick to be sure...

I had this issue with BartPE too... I wondered why PEBuilder did not copy the files that were added to the I386 folder from a source slipstreamed with DriverPack MassStorage to the PE build... the answer was related to the files PEbuilder uses to figure out what to copy... one of those files was layout.inf... If they are using a similar method then the issue may be a result of our lazyness tongue.  We update enough files to make it work for what we do, but we do not update it as well as say a service pack would big_smile.

TechDud wrote:

It would seem that WinSetupUSB & Rufus might have a bug in common for at least this controller
on an Inspiron 1525.
  sad

Agreed
Works on ODD fails at USB...

Seems to be Error @ usb preparation.

However, this error may be related to DriverPacks BASE not updating the layout.inf or some other catalog type files.

sounds like my life... i hear you loud and clear.