Topic: General driver question, why are some reconized and others are not?

Essentially I build a winbuilder xp that boots from usb drive, so our techs can reimage and perform certain tasks...

I am adding support for the HP 5102 mini netbook...

Looking at the intel sata drivers it uses the samve ahci version as the 6440 8.9.2.1002, which I added to DP 901 successfully.

The HWID PCI\VEN_8086&DEV_27C1&CC_0106 is listed a few times in my DP, once for a driver that came with 901 and again with the custom added 8.9.2.1002...

The textsetup for the mini is different but the infs are all the same... my winbuilder couldn't boot into the mini with a 7b error using the packs that work for the 6440 (that uses the same inf).

Looks like the only difference in the drivers (5102 vs 6440) is the textsetup.oem...

I would think that windows would use the same driver... Could there be a reason why the mini isn't using the driver I added (6440)?

Thanks for your help and knowledge...

Re: General driver question, why are some reconized and others are not?

Drivers are installed by HWID. is that devices HWID included in that drivers inf?

IDK how winbuilder works... so i can't tell you how to deal with that issue. They do have a forum for that wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: General driver question, why are some reconized and others are not?

Thanks overflow... I think intel is just messed up... doing more checks looks like the drivers have the same version and date listed in the inf but they are different sizes...  For the most part it looks like the inf for the 5102 was customized just for the 5102, it only has 1 HWID listed but all other entries are identical.

The only HWID reference I could find that was different was...

Just trying to figure out what would possibly make the OS confused... iastor.sys is the same file size/data etc.

inf of 6440

[INTEL_HDC.ntx86]
%PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc% = iaStor_Inst,PCI\VEN_8086&DEV_27C1&CC_0106


The inf of the 5102

[INTEL_HDC.ntx86]
%PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc% = iaStor_mobl_Inst,PCI\VEN_8086&DEV_27C1&CC_0106

[Strings]

PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc    = "Intel(R) ICH7R/DH SATA AHCI Controller"

[Strings]
PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc    = "Intel(R) NM10 Express Chipset"

Re: General driver question, why are some reconized and others are not?

I could guess that in winbuilder the HWID must be associated with the driver in the txtsetup... Just like for windows...
with a DriverPacks slipstream this is accomplished with the mass storage INI file wink. Often times the list of HWIDs in our INI is very different than the list that is actually contained in the drivers inf... Perhaps that helps you? - In other words you may be able to manually ad the entry to the txtsetup and make it work big_smile

from what i can tell PCI\VEN_8086&DEV_27C1&CC_0106 is supported in DriverPack MassStorage 9.01 In folder I3 and should work... ?
More... the specific entries for text mode (what i'll assume is used for winbuilder's Mass support) are referenced / contained in txtsetup (and not in the drivers infs). we populate the txtsetup based on the info contained in the Mass Storage DriverPacks INI file... The drivers  INFs are only used by Plug n Play... BartPE and like kind software (perhaps winbuilder) don't use the drivers inf at all but rely completely on the info in txtsetup alone.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.