[SLV] Chipset 8.03 Locking up on Dell GX 620 (Page 2 of 2)

You could also might be able to use the tool and specify only certain folders. Like C:\D\M\I1|C:\D\M\I2|C:\D\M\I3|C:\D\M\I4|C:\D\M\I5|C:\D\M\I6

The fix is to not run the makePNF command

I'm not running it either cause I have heard some people having issues with it. Thanks for letting us know.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs



Donate!

you want to keep makepnf for what you do (you do this like i do)

PNF's made simple:
It's a "catalog cache" of the currently available drivers, a table of contents if you will.
windows will check the PNF files first before doing a full blown search or the hardware wizard
if you are old enough you may remember window 98 say building a driver information database I belive this is an extention of that...
this is a speed increase for finding drivers for new hardware  (and possably input reduction)

when you prepare your image don't let the finisher run... !

this will leave the drivers in place and ready to go
(make pnf has been done and so has the PnP search path in the registry)

Run the finisher at deployment on the target machine

this will install any required control panels or other required software
and then remove the driverpacks and clean up reg entries ect...

old method
I used to do this manually after checking device manager...
and then make "per machine type" image if i had some identical machines.

a better idea is to
simply set a runonceex or guirunonce command...
copy the DPINST.exe and DPInst.xml files to the \D\ folder
(they are in the  dp_base\bin\wnt5_x86-32  folder)

1) call dpinst.exe /c /s /sh
2) call the finisher

since most imaging software do compression creating the image haveing the packs extracted is NBD.

You could use the Stand Alone Drivers (SAD) platform feature of base.
This will be a far superior way to do this...
We are still in beta testing on this feature though.
and it has a few rough edges still - but not for long!
(i am going to rename SAD to SoFI  Software First Installer... )

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

Mrguiter, if I'm reading this right the issue I think is that you are putting both INF's in. Do only the *ide.inf or *id2.inf, not both.

The issue is that the finisher will run against the location of INF's for driverpacks (C:\D) and miss all the drivers that windows has in it's collection (C:\Windows\inf) by default. And the reason why it chooses the driverpacks version is because it's newer. I think the only real way to accomplish this is to somehow change the version of the original driver to a later date than the one in the driverpacks. Or the other way around. However, I haven't tested this, it's only a theory.

Perhaps an option for the SoFI ini would be to skip driverpacks in favor of the windows driver?

Last edited by stamandster (2008-10-29 05:08:19)

You're right. I copied and pasted from an earlier post that was showing the nightly build. I guess my point was to show the identical hardware IDs for two different drivers. Sorry for the confusion.

Ongoing Problem