DriverPacks.net Forum - Problem with Intel drivers in GraphicsB

Re: Problem with Intel drivers in GraphicsB

null@example.com (OverFlow) — Sat, 06 Jun 2009 03:04:53 +0000

don't ever run makePNF...
Clear enough

PNF's are a cached copy of inf contents. however the PNFs are unsigned.
Any driver referenced in a PNF most likely WILL NOT be used, since PNFs are unsigned.
PNFs are meant to speed up driver location but they don't...
PNFs don't work if you want to know why ask MS... But i can tell you for a fact the PNF method fails...

It is very likely that your sounddrivers failed in your other post BECAUSE you DID use makePNF
They might also have failed as a result of KB888111 since you ddi not report your OS or version in that post, I can't be certain.

Re: Problem with Intel drivers in GraphicsB

null@example.com (playtoy) — Sat, 06 Jun 2009 02:08:54 +0000

hey all;

so are you saying not to run makePNF before sysprep? does makepnf need to run to get the drivers to work? Would this solve my sound issue as realtek driver wont install.

thanks

Re: Problem with Intel drivers in GraphicsB

null@example.com (OverFlow) — Fri, 30 Jan 2009 02:24:07 +0000

We are working on supporting sysprep directly with DriverPacks BASE, as a result of the new platform being added that tutorial wil become a historical reference , and be replaced with a tutorial that features the new base functionality

Thanks so much for reporting your success and we are so glad to have been of service to you.

Have a great day!

Re: Problem with Intel drivers in GraphicsB

null@example.com (jcharaoui) — Thu, 29 Jan 2009 15:13:02 +0000

Right, I tried just now without makePNF, and as you predicted, it worked. The Intel graphics driver was installed correctly.

Perhaps the original tutorial ought to be edited to indicate that makePNF could cause problems in some cases...

Re: Problem with Intel drivers in GraphicsB

null@example.com (OverFlow) — Thu, 29 Jan 2009 02:10:29 +0000

if you read on in the skinlayers tutorial thread (which is excellent by the way)

it states quite clearly that makePNF will create duplicate and more importantly Unsigned INF's and will create issues. I realize it is many pages long but if you only read the first post you missed a gold mine of helpful tips and secrets

Don't use makePNF that should solve your issue. Thanks for providing the missing pieces of the puzzle!

Jeff

Re: Problem with Intel drivers in GraphicsB

null@example.com (jcharaoui) — Wed, 28 Jan 2009 23:00:58 +0000

Well, I used the method described in these very forums, there : http://forum.driverpacks.net/viewtopic.php?id=1682

However I was able to understand more of the problem : since I used a universal Sysprep before on this image, it looks like I need to delete all oem*.inf and oem*pnf files from the WINDOWS\inf folder. After doing that, the dialog didn't pop-up during the mini-setup. However, the graphics driver wasn't installed, and a yellow bang appeared in the device manager for the video card item.

The only difference between that Intel driver and the rest that get installed just fine is that those were shuffled around a bit in the latest DriverPack, and now somewhere the old INF/PNF information still stays, even after doing a new makePNF.exe, causing mini-setup to look for the device driver in the wrong folder.

Re: Problem with Intel drivers in GraphicsB

null@example.com (OverFlow) — Wed, 28 Jan 2009 17:16:24 +0000

I am sorry to have to report that the SysPrep platform is not currently supported by DriverPacks...

Posted on wrong forum... moved to Universal Imaging from Graphics.

One of teh sysprep gurus may attempt to help you...
However if you do not tell them (us) the exact steps you took in detail to add DriverPacks to your sysprep I would not expect anyone to respond to your post...

Welcome to DriverPacks
Have a great day and I wish you the best of luck!

moved to correct forum

Problem with Intel drivers in GraphicsB

null@example.com (jcharaoui) — Wed, 28 Jan 2009 16:29:40 +0000

Hi, I use DriverPacks with Sysprep here, and it seems an update to the Intel drivers in Graphics_B is causing a problem. During the minisetup, it pops up a dialog asking for the location of ialmnt5.sys, with the path "C:\D\G\I2" listed. If I change "I2" to "I5", it works and the rest of the drivers are installed without any problems. It worked fine with previous versions of Driverpacks... I thought it could have been a problem with DevPath.exe, but I can confirm that the command runs correctly before Sysprep is launched (I checked the registry key), as well as makePNF.exe. My device id is "2582". Any ideas?