Search options (Page 74 of 159)

Read the 'News' page.

Updated \S2 with .inf from that package (same version).

So what driver works for you then?  Let me know and I'll have a look at it.

That more than likely does not apply to this thread.  This thread is for the realtek overlap bug (conflict between driver versions).
There will always be duplicated HWIDs between Soundmax/Realtek but we won't know there's a problem unless you report the HWID of the affected machine.
So create a new thread with the info required from this post.

Well I think the Intel RST 9.??6.??0.??1014 that supports your HWID is broken.  I've been playing with the new RST 10.0.0.1046 with great success.  I'll be putting it in a nightly soon for more testing.
Please be patient.

Editing all the .inf files is a LOT of work.  And what if you replace the drivers in a folder with a newer set which alters the HWID list (add/remove) then you'll have to go through and uncomment the HWIDs that are missing.  I (and many of the team) have been working under the policy of leaving the .inf (and driver signing) intact whenever possible and only editing the HWIDs to prevent a problem-causing conflict.  Once a problem is reported, then we break driver-signing if there is no other solution.  Sure, there are loads of duplicates then, but Windows setup does a pretty good job of sorting them out on its own.
That's just my policy, but it's worked for us in the past.

Forget about PE for a moment, What about a normal disc-based install.  Do any of the test packs work in that scenario?

Isn't that what I said about three posts above?

Well, only the folder wnt5 is created with this particular test pack because no other drivers are loaded, only the one nvidia folder.  The tests were really designed for normal disc-based installs, not BartPE.  But creating an empty wxp folder within the UBCD4Win\plugin\DriverPacks.net\MassStorage folder before building the PE disc should get rid of the error.  Maybe adding a w2k3 folder also would help.  I think those paths are hard-coded into the UBCD4win app.

Yeah, I figured that would be the case. [T] has been in there since last year, but it has caused problems for others as well.
The key here is that yours DOES work with [I4], but the install is somehow getting confused and using [T] even though the HWID is not a match.

I noticed one driver that was present in the MSI blob but not in any DriverPacks.
It's in the "Filter" folder but it looks to be only for Vista/Win7.  Other than that, no other differences I could see.

OK, I've gone through the drivers from the MSI site and they don't support the HWIDs you posted...at all.
Well, the only HWID supported is the SMBUS driver from 2007, which is already in the DriverPack Chipset.
Strange.

I don't have access to v6.2.0.2002.  But have you tried moving your HWID to the [i] .ini header?

[i]
; 5.5.0.1035
ms_count=1
ms_1_deviceName="Intel 82801ER/6300ESB SATA RAID"
ms_1_tag="iastor"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24DF&CC_0104,PCI\VEN_8086&DEV_25B0&CC_0104,PCI\VEN_8086&DEV_27C5&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

It's an even older version, but should work.

You shouldn't need any specialized touchpad drivers with PE.  The system will just use the generic mouse driver.  It's PE, you're not going to need advanced scrolling or multi-touch are you?