DriverPacks.net Forum - [SLVD] Duplicate Hwids in 11.08

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (OverFlow) — Sun, 28 Aug 2011 02:43:46 +0000

Excellent... you never did create a bug report over at the bugtracker.

Not many people get the opportunity to do so .

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (mr_smartepants) — Sat, 27 Aug 2011 09:39:36 +0000

All the appropriate duplicated HWIDs are fixed in 11.08.1b1 (and b2). These will be in the next major release.

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (PaulDG) — Sun, 21 Aug 2011 22:58:49 +0000

All Done, Those last 3 items in the scsi section were the last problem.

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (OverFlow) — Sun, 21 Aug 2011 20:14:03 +0000

I think copy the sif is the better idea...
there are way to many exceptions and general weirdness to start from scratch... took us years to get it even close to right.

But I am glad you tried it and found some anomlies. Go ahead if you like but you are going to pull you hair out before it's over .

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (PaulDG) — Sun, 21 Aug 2011 12:24:11 +0000

Ok how did I Find them !!!

I install across a network share created in PE, this leaves "$WIN_NT$.~BT" and "$WIN_NT$.~LS".
I like pure sources and prefer to apply the driverpacks only when they are needed, not wanting to have multiple sources I decided to drop the DriverPack files into the above folders after the copy stage.

For this I needed the txtsetup.sif file, I know I could have copied them from a dp'ed source but I figured I would parse the MassStorage ini file and create my own. Early results found the duplicate tag names from my first report.

My original routine for adding the [hwidsiddatabase] entries didn’t account for the duplicates and caused duplicate errors in the sif, which showed up in a side by side comparison.

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (mr_smartepants) — Sat, 20 Aug 2011 21:41:50 +0000

A3 and A5 share PCI\VEN_1191&DEV_0009&SUBSYS_00091191 (Fixed in 11.08.1b1)
M - All 5 hwids are duped accross ms_1 ("mv61xxmm") and ms_2 ("mv61xx") (Normal, this is intended)
M4 - All 3 hwids are duped accross ms_1 (mv64xxmm) and ms_2 (mv64xx) (Normal, this is intended)
M5 - All 29 hwids are duped accross ms_1 ("mvxxmm") and ms_2 ("mv91xx") (Normal, this is intended)
S5 and S4 Share PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 & PCI\VEN_1002&DEV_4379&SUBSYS_43791002 & PCI\VEN_1002&DEV_437A&SUBSYS_437A1002 (Fixed in 11.08.1b1)

List of Inline Dupes
D3 - PCI\VEN_1028&DEV_000A&SUBSYS_011B1028 & PCI\VEN_1028&DEV_000A&SUBSYS_01211028 (Fixed in 11.08.1b1)
L2 - PCI\VEN_8086&DEV_1960&SUBSYS_0466101E & PCI\VEN_8086&DEV_1960&SUBSYS_0467101E & PCI\VEN_8086&DEV_1960&SUBSYS_0490101E (Fixed in 11.08.1b1)
S3 - PCI\VEN_1095&DEV_3531&SUBSYS_30d4103c (Fixed in 11.08.1b1)
S4 - PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D (Fixed in 11.08.1b1)

All the duplicates between the SC# folders are because of the different card BIOS revisions. They've been like that for years.

Seriously though, how did you find those? Jeff's right, you need to be on the testing team!

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (PaulDG) — Sat, 20 Aug 2011 17:50:26 +0000

So the mv*xxmm details in the HardwareIdsDatabase section of txtsetup are not required ?

Also i forgot to add my first example to the list, ill edit.

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (mr_smartepants) — Sat, 20 Aug 2011 15:29:49 +0000

PaulDG wrote:

M - All 5 hwids are duped accross ms_1 ("mv61xxmm") and ms_2 ("mv61xx")
M4 - All 3 hwids are duped accross ms_1 (mv64xxmm) and ms_2 (mv64xx)
M5 - All 29 hwids are duped accross ms_1 ("mvxxmm") and ms_2 ("mv91xx")

Those are all by design. The mv*xxmm driver needs to load before it's corresponding mv##xx driver. That's how magic happens!
I'll look into the others.
Thanks for reporting.

Re: [SLVD] Duplicate Hwids in 11.08

null@example.com (OverFlow) — Sat, 20 Aug 2011 15:09:36 +0000

How would you like to be on the testing team?

[SLVD] Duplicate Hwids in 11.08

null@example.com (PaulDG) — Sat, 20 Aug 2011 12:27:52 +0000

Should there be duplicate hwids in either the same driver or other drivers ?

Driver A3's second hwid is "PCI\VEN_1191&DEV_0009&SUBSYS_00091191" which is also Driver A5's First and only hwid, This results in both .sys files being compressed but no reference in the "HardwareIdsDatabase" for the A3 Driver as its overwritten by the A5 entry
There are a number of other drivers with the same conditions.

Also there are a number of drivers where some of the hwids are duplicated on the same "ms_x_hwids=" line, One even has lower case letters in the second occurrence. Are the duplicates intended? and if so is the lowercase letters intended?

List of Cross Drive Dupes
A3 and A5 share PCI\VEN_1191&DEV_0009&SUBSYS_00091191
M - All 5 hwids are duped accross ms_1 ("mv61xxmm") and ms_2 ("mv61xx")
M4 - All 3 hwids are duped accross ms_1 (mv64xxmm) and ms_2 (mv64xx)
M5 - All 29 hwids are duped accross ms_1 ("mvxxmm") and ms_2 ("mv91xx")
SC and SC2 share PCI\VEN_1095&DEV_3132&SUBSYS_71328086 & PCI\VEN_1095&DEV_3132&SUBSYS_2C0A17F2
SC and SC3 share PCI\VEN_1095&DEV_3132&SUBSYS_820F1043 & PCI\VEN_1095&DEV_3132&SUBSYS_2A49103C
SC and SC4 share PCI\VEN_1095&DEV_3132&SUBSYS_0011182D
SC and SC5 share PCI\VEN_1095&DEV_3132&SUBSYS_8177103c (Small c) & PCI\VEN_1095&DEV_3132&SUBSYS_F001147B
S5 and S4 Share PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 & PCI\VEN_1002&DEV_4379&SUBSYS_43791002 & PCI\VEN_1002&DEV_437A&SUBSYS_437A1002

List of Inline Dupes
D3 - PCI\VEN_1028&DEV_000A&SUBSYS_011B1028 & PCI\VEN_1028&DEV_000A&SUBSYS_01211028
L2 - PCI\VEN_8086&DEV_1960&SUBSYS_0466101E & PCI\VEN_8086&DEV_1960&SUBSYS_0467101E & PCI\VEN_8086&DEV_1960&SUBSYS_0490101E
S3 - PCI\VEN_1095&DEV_3531&SUBSYS_30d4103c
S4 - PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D