<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[DriverPacks.net Forum - General driver question, why are some reconized and others are not?]]></title>
	<link rel="self" href="http://forum.driverpacks.net/extern.php?action=feed&amp;tid=4560&amp;type=atom"/>
	<updated>2010-05-19T19:56:43Z</updated>
	<generator>PunBB</generator>
	<id>http://forum.driverpacks.net/viewtopic.php?id=4560</id>
		<entry>
			<title type="html"><![CDATA[Re: General driver question, why are some reconized and others are not?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=38336#p38336"/>
			<content type="html"><![CDATA[<p>I could guess that in winbuilder the HWID must be associated with the driver in the txtsetup... Just like for windows...<br />with a DriverPacks slipstream this is accomplished with the mass storage INI file <img src="http://forum.driverpacks.net/img/smilies/wink.png" width="15" height="15" alt="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 <img src="http://forum.driverpacks.net/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /></p><p>from what i can tell PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106 is supported in DriverPack MassStorage 9.01 In folder I3 and should work... ?<br />More... the specific entries for text mode (what i&#039;ll assume is used for winbuilder&#039;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&nbsp; INFs are only used by Plug n Play... BartPE and like kind software (perhaps winbuilder) don&#039;t use the drivers inf at all but rely completely on the info in txtsetup alone.</p>]]></content>
			<author>
				<name><![CDATA[OverFlow]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=1097</uri>
			</author>
			<updated>2010-05-19T19:56:43Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=38336#p38336</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: General driver question, why are some reconized and others are not?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=38333#p38333"/>
			<content type="html"><![CDATA[<p>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...&nbsp; 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.</p><p>The only HWID reference I could find that was different was...</p><p>Just trying to figure out what would possibly make the OS confused... iastor.sys is the same file size/data etc.</p><p>inf of 6440</p><p>[INTEL_HDC.ntx86]<br />%PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106.DeviceDesc% = iaStor_Inst,PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106</p><br /><p>The inf of the 5102</p><p>[INTEL_HDC.ntx86]<br />%PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106.DeviceDesc% = iaStor_mobl_Inst,PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106</p><p>[Strings]</p><p>PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106.DeviceDesc&nbsp; &nbsp; = &quot;Intel(R) ICH7R/DH SATA AHCI Controller&quot;</p><p>[Strings]<br />PCI\VEN_8086&amp;DEV_27C1&amp;CC_0106.DeviceDesc&nbsp; &nbsp; = &quot;Intel(R) NM10 Express Chipset&quot;</p>]]></content>
			<author>
				<name><![CDATA[dandirk]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=11924</uri>
			</author>
			<updated>2010-05-19T18:25:58Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=38333#p38333</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: General driver question, why are some reconized and others are not?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=38331#p38331"/>
			<content type="html"><![CDATA[<p>Drivers are installed by HWID. is that devices HWID included in that drivers inf?</p><p>IDK how winbuilder works... so i can&#039;t tell you how to deal with that issue. They do have a forum for that <img src="http://forum.driverpacks.net/img/smilies/wink.png" width="15" height="15" alt="wink" /></p>]]></content>
			<author>
				<name><![CDATA[OverFlow]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=1097</uri>
			</author>
			<updated>2010-05-19T14:28:01Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=38331#p38331</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[General driver question, why are some reconized and others are not?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=38328#p38328"/>
			<content type="html"><![CDATA[<p>Essentially I build a winbuilder xp that boots from usb drive, so our techs can reimage and perform certain tasks...</p><p>I am adding support for the HP 5102 mini netbook...</p><p>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.</p><p>The HWID PCI\VEN_8086&amp;DEV_27C1&amp;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...</p><p>The textsetup for the mini is different but the infs are all the same... my winbuilder couldn&#039;t boot into the mini with a 7b error using the packs that work for the 6440 (that uses the same inf).</p><p>Looks like the only difference in the drivers (5102 vs 6440) is the textsetup.oem...</p><p>I would think that windows would use the same driver... Could there be a reason why the mini isn&#039;t using the driver I added (6440)?</p><p>Thanks for your help and knowledge...</p>]]></content>
			<author>
				<name><![CDATA[dandirk]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=11924</uri>
			</author>
			<updated>2010-05-19T13:01:54Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=38328#p38328</id>
		</entry>
</feed>
