• Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Topic: [Final] Mass Storage 711

Hi

This one was finalised and published

changes compared with 71012X are > folder structure change and Silicon 3114 downgrade

This effort has a history.

Let's look at was done, step by step, while we made 710**
(I will mention major chanhes compared to 7.09.2)

When I used the driverINFinfo spotlight utility and an excell "sort" formula (thanx for that tip, Mr EchoPlatoon.), all sorts of little "things" came to light.

Why did I ask to test  eXperimental testpacks in the public forum?
Debugger had suggested a workaround for issues where a RAID driver got the overhand when the chip was in Base-Mode.
This TestPack uses his technique.
Now, because it most certainly looks like this is going to be our solution to many problems we had with silicon, promise, and other drivers which caused clashes between raid/non-raid variants, I'll continue work on the 'eXperimental'.

The testfiles try to solve issue with drivers intended for different BIOS versions in Mass storage Chips.
We also use debugger's idea.
&CC_010* gets tagged to some drivers we have had issue reports on

When compared to the main release (Mass Storage 7092.), The current 71012X pack had these changes.
= = = =

All OEMSETUP.INF files renamed, the driver's name is used if possible.
(this is with SySprep users in mind. They cannot have duplicate INF files.)
All NODEV.INF files renamed.


3\1 3Ware 9000/9500/9650 updated to 12/04/2006,3.00.02.090
3\1\o removed

ad\6 updated to 01/22/2007,7.00.00.06
ad\6\c (INF renamed and moved into ad\6, overlap HWIDs removed from INF.)
ad\A removed

d\2 updated to 02/15/2007,1.21.26.01

D\3 is a new addition
DELL PERC 5/E 5/i 6/e 6/i & CERC 6/i RAID Controller 12/15/2006,2.8.0.32

Emulex had duplicated lines in INF.

H\1R rocketraid 1520, removed folder.
Highpoint INF names were made unique

I\2 Intel updated from 6.2 to 7.0 (the highest found for this single device ID)

J\ Jmicron, updated to 08/30/2007, 1.17.25.02   
(and I did an INI FIX; wrong mode could be picked during txtmode.)

L\4  updated to 01/27/2006,1.21.12.00

A fix for Marvel in M\1, issue reported by Rockbow

Nvidia.
we Looked at the duplicate HWIDs.
We added some for TXTmode.
Later in the topic you will find a them descibed.

Promise drivers; all fasttrak and ulsata drivers were given unique TAGNAMES for separate Operating systems.
(an INI fix.)
in P\1 (xp/w2k/w2k3) I disabled PCI\VEN_105A&DEV_4d33. It was also found in newer driver in P\8
for fasttrak &CC_0104 got tagged to the HWIDs in INF and INI.
for ulsata, &CC_0101 got tagged to the HWIDs in INF and INI.
All Promise (like we find in P\B P\B\k and P\B\k3) got unique INF names

Then there (was) the battle for Silicon Hyll. We got that licked, far as I know.. smile
I searched for SiLicon duplicate HWIDs. Fixed some.
I also want to rid ourselves of the need for SFXminiPacks.

S\4 for bios 4.2.50 (SiL Image 3112/3512, 06/14/2004, 1.2.0.57)
S\4B for bios 4.x.79 (SiL Image 3112, 10/23/2006, 1.3.67.0)
S\4C for bios 4.x.83 (SiL Image 3112, 04/13/2007, 1.3.68.2)

S\5 for bios 4.3.47 (SiL Image 3112/3512 Raid, 08/27/2004, 1.0.0.51)
S\5B for bios 4.x.79 (Sil Image 3112 Raid, 03/14/2006, 1.0.56.1)
S\5C for bios 4.x.83 (Sil Image 3112 Raid, 02/01/2007, 1.0.60.0)
(S\5A still has the ATI 3112/3512 raid variants.)

[S-B] = "Silicon Image 3132 SATALink for BIOS 7223, 04/25/2005, 1.0.0.9"
[S-B2] = "Silicon Image 3132 SATALink for BIOS 7230, 01/25/2006, 1.0.14.1"
[S-B3] = "Silicon Image 3132 SATALink for BIOS 7310, 03/16/2006, 1.0.15.0"
[S-B4] = "Silicon Image 3132 SATALink for BIOS 7313, 10/31/2006, 1.0.19.0"
[S-B5] = ="Silicon Image 3132 SATALink for BIOS 7405, 06/05/2007, 1.0.21.1"

[S-C] = "Silicon Image 3132 SoftRaid 5 for BIOS 7223, 03/31/2005, 1.2.3.1"
[S-C2] = "Silicon Image 3132 SoftRaid 5 for BIOS 7230, 10/18/2005, 1.3.0.9"
;comment; driver for BIOS 7310 had no unique HWIDs
[S-C3] = "Silicon Image 3132 SoftRaid 5 for BIOS 7313, 09/05/2006, 1.5.10.0"
[S-C4] = "Silicon Image 3132 SoftRaid 5 (it had a unique HWID), 01/25/2007, 1.5.14.1"
[S-C5] = "Silicon Image 3132 SoftRaid 5 for BIOS 7405, 05/30/2007, 1.5.18.0"


S-7 update; Silicon Image 3114 SoftRaid 5 from 09/05/2006, 1.5.10.0 to 02/05/2007, 1.5.15.0
S-8 Silicon Image 3124 SATALink generic
S-8A Silicon Image 3124 SATALink for BIOS 6217
S-9 Silicon Image 3124 SATARaid generic
S-A Silicon Image 3124 SoftRaid 5 for BIOS 6217"
S-A2 Silicon Image 3124 SoftRaid 5 for BIOS 6318"


There is only one workaround for different BIOS versions in Sil 3114.
(Eight drivers: SEVEN BIOS versions. 1 for base, four for raid5, and three for raid.)
Using the NEWEST driver cannot be done because there is only ONE difference for seven BIOS versions.
The oldest driver is not the best. The next one and all newer than that have just one more HWID than the oldest.

The workaround in 711nightly is that I decided to use the next to oldest driver, because it is proven that newest drivers do not work on older card's BIOSes. It read reports that an older driver worked on newer BIOS and could verify this.
(Not only by tests I did myself. There was a post at a sister project which made me decide to downgrade Sil 3114 drivers.)

SIS 180/181/182 in si\1. Newest driver 01/11/2007,5.1.1039.2110 replaces si\1 si\2 and si\3.

V\3 Duplicate HWIDs removed for TXTmode.
V\4 rewrote INI (This driver is newer than V\3.)
= = = =

FOLDER STRUCTURE CHANGED IN 711_NIGHTLY

PAR EXAMPLE. D\M\V\4 becomes D\M\V4
When you have 129 folders with drivers in them, we can reduce path lenght by over 200 characters.
We decided to do it long ago, and the time is here.
It was sanctioned by Bâshrat the Sneaky.
quote = "You want to do it, go ahead."
I know I will have to update the supported device list, and it will take work to do it, but it really is worth it, because Method 1 will benefit.
_______

NOTES.
Please ALWAYS select  QSC ON, DISC based installation for WINDOWS XP.
Windows 2003 and 2000 were NOT yet tested by me.

This "experimental" testpack still has a number of files with same name.
Future packs will attempt to get rid of duplicated names.

What works for SySprep, works for Disc based installations.
(We cannot implement everything, though. ) °
Tell us how you fixed driver info and systemfiles and help us help you..
= = =
I want a raise. smile
I want to buy a licence for araxis merge 2007.
It's the best file/folder compare tool I have used so far.
--------------

711 was based on 71012x and should be good. (I put some faith in JakeLD's work)

It's a long one to read, but the info about the future is in here.
Please provide feedback, and do not forget to subscribe when you post.

This post  about X testpackx has had its last revision

Last edited by Jaak (2007-11-28 06:40:10)

The answer was 42?
Kind regards, Jaak.
  • cdob
  • DriverPacks Guru
  • Offline
  • Registered: 2006-08-13
  • Posts: 270

Re: [Final] Mass Storage 711

When I used the driverINfinfo spotlight tool and sort formula, all sorts of "things" came to light.
Because it looks like this is going to be our solution to many problems we had with silicon, promise, and other drivers which caused clashes between raid/non-raid variants, work will continue on the 'Xperimental'.

Thanks, driverINfinfo spotlight tool is great. This come in handy.

Unfortunalely I have limited different hardware.

L\4  updated to 01/27/2006,1.21.12.00

Nvidia, Looked at the duplicate HWIDs. Looks like it can be left as is.
The TXTmode driver we use has pretty much all HWIDs and is most current.

What about: http://www.nvidia.com/object/nforce_520 … 12.15.html
nForce 520/560 
Version:    12.15
Release Date:    July 24, 2007

  • From: Russia
  • Registered: 2006-06-14
  • Posts: 326

Re: [Final] Mass Storage 711

I have SiI 3132 onboard at my MoBo (MSI K8N Diamond). But I haven't two sata HDDs to work with DriverPacks... I want to try to build raid with two IDE HDDs via IDE>SATA converters. Do you know could work it or not?

  • realhyg
  • DriverPacks newbie
  • Offline
  • Registered: 2007-10-12
  • Posts: 8

Re: [Final] Mass Storage 711

V/4 can not be used by sysprep,It han an register error

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Hi realhyg,
welcome to DriverPacks.

Thanks for the report. I'll have an update ready later tonight.
I first want to live test it on at least one machine before I upload it.

I bet my first impression about V\4 was the right one (before I used the spotlighht tool), and while I was making the experimental I started to doubt and I changed it from busextender = true to false.

the burn is ready, and test will be soon.

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

7105X is up.
Via\4 again uses VIBUS now. (the way I had set it before I thought that was wrong.)

The answer was 42?
Kind regards, Jaak.
  • realhyg
  • DriverPacks newbie
  • Offline
  • Registered: 2007-10-12
  • Posts: 8

Re: [Final] Mass Storage 711

Hi Jaak,
In my test,I did not use the DriverPack_MassStorage_wnt5_x86-32.ini file.
So just edit this ini file will not slove this error in sysprep.
It seems like the ViPrt.inf not support to be used by sysprep.

;[V-4]
PCI\VEN_1106&DEV_3149&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_3349&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0581&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0591&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5287&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5324&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5337&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5372&CC_0101=C:\sysprep\M\V\4\ViPrt.inf

  • Registered: 2007-06-01
  • Posts: 14

Re: [Final] Mass Storage 711

@Jaak

Please , can you correct the download link , because it does not work.

after self-effort , i found it works with

http://dev.driverpacks.thesneaky.com/driverpacks_nightlies/DP_MassStorage_wnt5_x86-32_7105X.7z

Last edited by waleed_wwn (2007-10-13 17:20:44)

  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: [Final] Mass Storage 711

waleed_wwn wrote:

Please , can you correct the download link , because it does not work.

Fixed. smile

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • From: Netherlands, Amsterdam
  • Registered: 2006-05-30
  • Posts: 141

Re: [Final] Mass Storage 711

@Jaak,

i noticed the following 2 sections:

[S-5]
ms_count=1
ms_1_deviceName="Silicon Image 3112 SATARaid Controller for Bios 4.x.79"
ms_1_tag="si3112r"
ms_1_sysFile="Si3112r.sys"
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_61121095&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_611215D9&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_34228086&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_B0031458&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0111019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0121019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0131019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0141019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0151019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1014147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_100B147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1402147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1404147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1802147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1804147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1C00147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_5930107D&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_249510F1&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_809D1043&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0270A0A0&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_044DA0A0&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_044CA0A0&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_92011905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_92151905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_904C1905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_904B1905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A41810FD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A41910FD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A71910FD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_90171695&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_C2001297&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_C2011297&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_15D40035&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_340217F2&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_100415BD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_F641270F&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C0F105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C13105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C58105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C40105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C41105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C42105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C43105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C44105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C22105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C2A105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_2A1E103C&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_65121095&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_B0031458&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1014147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1021147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_100B147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C06147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C00147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C03147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C04147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1406147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1407147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_90191695&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_C2021297&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_C2031297&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_C2041297&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_534D108E&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_02C51095&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_2A1E103C&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_0C22105B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_0C2A105B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_91451462&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_006C1025&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_010D1025&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_A43110FD&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_F3631297&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_07201462&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_B0031458&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_92691509&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_5005148C&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_0A44174B&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_0A45174B&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_00301462&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_100516F3&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_43791002&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_437A1002&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_3009103C&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_3009103C&CC_0104"
ms_1_isBusExtender=false

[S-5-B]
ms_count=1
ms_1_deviceName="Silicon Image 3112 SATARaid for Bios 4.x.83"
ms_1_tag="3112r483"
ms_1_sysFile="Si3112r.sys"
ms_1_hwids="PCI\VEN_1095&DEV_3512&SUBSYS_0010182D&CC_0104"
ms_1_isBusExtender=false

Both section have the same sysfile, i thought that textmode setup can only load .sysfiles that do not have the same name as other .sys files do.
If you want a specific version of Si3112r.sys to be loaded during textmode, you probably have to rename one of the Si3112r.sys filenames to something else.  I Could be wrong here though.

Last edited by ruudboek (2007-10-14 23:31:19)

I think this is a Useful Project. Do you? Help us help you, and click here.

ruudboek's Website

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Hi Ruud,
the tagnames are unique, the INF have not (yet) been edited to "compensate" for changing system file names.

If you are interested about making the systemfiles unique as well, then I can point you to an example where it was done.
In the Intel sections, all iastor drivers have unique system file names, and the INF was edited to "compensate" for the references to names.

I have worked on the Sil 3132 drivers, and will run a live test on the machine that has a Sil3132 here.
With latest driver only, I get a yellow in hardware manager.
(A note to myself and Ruud.. :  Months ago, I could not get a driver for "floppy" for my mobo at Gigabyte. This week I found one such. It has same version as the oldest found at Silicon Image site. So, the testpack following this one here has this old version and all the newer, and I'll see what that does.)

A note to all, the testpack is for tests.
If a sysprep user requires additional changes , he better tell us what we need do. smile

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

good news.
The work on Sil 3132 was running OK on my rig with the 3132 chip in it
smile

gotta go now, but tonight I'll finish another few, and we'll then have this.

S\4 for bios 4.2.50 (SiL Image 3112/3152, 06/14/2004, 1.2.0.57)
S\4B for bios 4.x.79 (SiL Image 3112, 10/23/2006, 1.3.67.0)
S\4C for bios 4.x.83 (SiL Image 3112, 04/13/2007, 1.3.68.2)

S\5 for bios 4.3.47 (SiL Image 3112/3152 Raid, 08/27/2004, 1.0.0.51)
S\5B for bios 4.x.79 (Sil Image 3112 Raid, 03/14/2006, 1.0.56.1)
S\5C for bios 4.x.83 (Sil Image 3112 Raid, 02/01/2007, 1.0.60.0)
(S\5A still has the ATI 3112/3152 raid variants.)

[S-B] = "Silicon Image 3132 SATALink for BIOS 7223"
[S-B2] = "Silicon Image 3132 SATALink for BIOS 7230"
[S-B3] = "Silicon Image 3132 SATALink for BIOS 7310"
[S-B4] = "Silicon Image 3132 SATALink for BIOS 7313"
[S-B5] = ="Silicon Image 3132 SATALink for BIOS 7405"

[S-C] = "Silicon Image 3132 SoftRaid 5 for BIOS 7223"
[S-C2] = "Silicon Image 3132 SoftRaid 5 for BIOS 7230"
;comment; driver for BIOS 7310 had no unique HWIDs
[S-C3] = "Silicon Image 3132 SoftRaid 5 for BIOS 7313"
[S-C4] = "Silicon Image 3132 SoftRaid 5 (it had a unique HWID)"
[S-C5] = "Silicon Image 3132 SoftRaid 5 for BIOS 7405"

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Hi, Updated to 7106X

local test on live machine what uses 3132 silicon ran OK
One other test in Aalst (a friend with a Sil 3112), ran OK.

let's get reports.

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: [Final] Mass Storage 711

Gonna build a new cd with those goodies and hopefully I can test it in the evening. Will let you know the results.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Hi,
I will upload after I could test it myself.
I just did this:

we're getting there.
DONE; Sil 3124 (TWO BIOS versions; One IDE "base" driver not tied to particular BIOS?)
DONE; Silicon Image 3114 SoftRaid 5 from 09/05/2006, 1.5.10.0 to 02/05/2007, 1.5.15.0


S-7 update; Silicon Image 3114 SoftRaid 5 from 09/05/2006, 1.5.10.0 to 02/05/2007, 1.5.15.0
S-8 Silicon Image 3124 SATALink generic
S-8A Silicon Image 3124 SATALink for BIOS 6217
S-9 Silicon Image 3124 SATARaid generic
S-A Silicon Image 3124 SoftRaid 5 for BIOS 6217"
S-A2 Silicon Image 3124 SoftRaid 5 for BIOS 6318"

CANNOT BE DONE.
there is no workaround for different BIOS versions in Sil 3114.
(Eight drivers: SEVEN BIOS versions. 1 for base, four for raid5, and three for raid.)
It cannot be done because there is only ONE difference for seven BIOS versions.
The next to oldest has one more HWID than the oldest, and newer have same.
I still want a raise. smile

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

updated to 7107X

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

This is a separate testpack for an new addition of NVIDIA.

For Nvidia, I looked at the duplicate HWIDs.
The generic TXTmode driver we use has pretty much all HWIDs and is most current.

it has all of the stuff 7107x has, and I added NEW driver: (not the one mentioned in this topic. We had a newer in our pack.)

N\6 Nforce 630; 05/04/2007,10.1.0.12, it provides AHCI support.
N\6R Nforce 630; 05/04/2007,10.1.0.12, it provides SATA RAID support


already superceded by 7109x version

Last edited by Jaak (2007-10-20 13:25:44)

The answer was 42?
Kind regards, Jaak.
  • cdob
  • DriverPacks Guru
  • Offline
  • Registered: 2006-08-13
  • Posts: 270

Re: [Final] Mass Storage 711

Jaak wrote:

For Nvidia, I looked at the duplicate HWIDs.
The generic TXTmode driver we use has pretty much all HWIDs and is most current.

DP_MassStorage_wnt5_x86-32_7108X.7z

What about:
\12.15_nforce_520_winxp32_english_whql\IDE\WinXP\sataraid\nvrd32.inf
%NVSTOR_DESC%=Crush11_Inst,PCI\VEN_10DE&DEV_044C&CC_0104

\12.15_nforce_520_winxp32_english_whql\IDE\WinXP\sata_ide\nvgts.inf
%NVSTOR_DESC%=Crush11_Inst,PCI\VEN_10DE&DEV_044D&CC_0106


Added:
I wonder about, haven't tested this:
[S-5]
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_61121095&CC_0104

Devcon list:

devcon hwids PCI\CC_01* 

PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\3&61AAA01&0&80
Name: SCSI Controller
Hardware ID's:
PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01
PCI\VEN_104B&DEV_1040&SUBSYS_1040104B
PCI\VEN_104B&DEV_1040&CC_010000
PCI\VEN_104B&DEV_1040&CC_0100
Compatible ID's:
PCI\VEN_104B&DEV_1040&REV_01
PCI\VEN_104B&DEV_1040
PCI\VEN_104B&CC_010000
PCI\VEN_104B&CC_0100
PCI\VEN_104B
PCI\CC_010000
PCI\CC_0100

Devcon dosn't list VEN_*&DEV_*&SUBSYS_*&CC_*.
Is VEN_*&DEV_*&SUBSYS_*&CC_* a valid HardwareID ?

Does different Silicon Image controller BIOS use different REV_* numbers?
If, then VEN_*&DEV_*&SUBSYS_*&REV_* maybe a unique HardwareID.

Last edited by cdob (2007-10-19 07:00:40)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

hi

12.15_nforce_520_winxp_international_whql.exe

nForce 520/560   (folder 18)
Version: 12.15 Release Date: July 24, 2007
WHQL driver package for nForce 520/560 motherboards.

Windows XP/2000 Driver Versions:

IDE SataRAID Driver (v9.95) "WHQL" ( OLDER THAN FOLDER 2 ( 14.10 ))
IDE SataIDE Driver (v9.95) "WHQL" ( OLDER THAN FOLDER 2 ( 14.10 ))
RAIDTOOL Application (v9.85) "Sedona" ( OLDER THAN FOLDER 2 ( 14.10 ))
SMU Driver (v1.31) "WHQL" (SAME AS FOLDER 2 ( 14.10 ))
NTune System Performance Utility (v5.05.49.00) (which is newer than the online nTune download)

--------------
14.10_nforce_630a_winxp_english_whql.exe

nForce 630a - Windows XP/2000 (folder 2)
Version: 14.10 Release Date: May 3rd, 2007 (yep, quite strange, huh?)
+ IDE SataRAID Driver (v10.1.0.12) WHQL
+ IDE SataIDE Driver (v10.1.0.12) WHQL
+ RAIDTOOL Application (v10.1.0.12)
= SMU (v1.31) WHQL

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Hi,

I do say that tagging CC_010* may not be neccesary in Silicon image.
(the subsys they provide are probably dealing with this.)
I also know that it works on the machine with Sil3132, which had a yellow flag in HW before.

The INI sections have no duplicate subsys in them.
(this was always a no-no..)
And, because of the nature of this problem, the duplicated HWIDs were removed from INF files.
(HWIDs in INF have  not been tagged with CC_010*)

I can quite easily upload a testPack where the CC_010* are not tagged to HWIDs in the silicon INI sections.

The answer was 42?
Kind regards, Jaak.
  • cdob
  • DriverPacks Guru
  • Offline
  • Registered: 2006-08-13
  • Posts: 270

Re: [Final] Mass Storage 711

Thanks for nvidia version compare.
It's not strange, it's nvidia wink

Sorry I'm not convinced yet.
A search *.inf and *.ini dosn't match PCI\VEN_10DE&DEV_044C&CC_0104 and not PCI\VEN_10DE&DEV_044D&CC_0106.
Does DP_MassStorage_wnt5_x86-32_7108X.7z support this two devices?

About Silicon image SUBSYS_*CC_010* tagging:
I'm guessing only, because I don't have this hardware.
Based on devcon output, I would remove CC_010* tagging.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

you were correct after all.
the HWID you posted was missing.

; thur, 2007 okt 19, removed N-6R INI section, added N-5 (AHCI driver) and N-5R sata raid driver
(The INI fix was because the newer driver did fewer PCI hwids)

590SLI removed ((all HWIDs were covered by either 5, 5r, or 6, 6r so it would not get used anyhow))
removed duplicated HWIDS in 4 and 4intel.

must run basic test, then I can upload.

Last edited by Jaak (2007-10-19 13:21:08)

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Jaak wrote:

This is a separate testpack for an new addition of NVIDIA.
N\6 Nforce 630; 05/04/2007,10.1.0.12, it provides AHCI support.
N\6R Nforce 630; 05/04/2007,10.1.0.12, it provides SATA RAID support

c31eba1646cec1beac8a5d182eb69563
DP_MassStorage_wnt5_x86-32_7108X.7z

we've learned CDOB had found a valid reason to update this.
12.15_nforce_520_winxp_international_whql.exe did have something unique we did not have in previous DriverPacks.

Therefore, 7109X is an update to 7108X

; okt 19, removed N-6R INI section,
added N-5 (AHCI driver) and
N-5R sata raid (07/02/2007,5.10.2600.0995 [12.15]) with an INI section for both.

removed N-590SLI drivers from the pack (it had no INI section)

; okt 19, pack 7109X_NO_CC removed CC_010* tagged to Silicon HWIDs
5b2393d933b0bdb504db866e324e1d9d DP_MassStorage_wnt5_x86-32_7109X_SiL_no_CC.7z
DP_MassStorage_wnt5_x86-32_7109X_SiL_no_CC.7z

enjoy.
Please mention which test pack version you report on.

Last edited by Jaak (2007-11-04 06:30:39)

The answer was 42?
Kind regards, Jaak.
  • Registered: 2007-08-21
  • Posts: 102

Re: [Final] Mass Storage 711

This is from the latest tagged pack, 7109X. If you dont understand, I will post a more elaborate explaination.
Also I have not tested anything after sysprep yet, I havent got that far yet.:P

Location:C\D\M\3\2
Problem: Driver not extracted- 2.exe
Fix: Extract driver

Location: C:\D\M\A\3\AEC6280.INF
Problem: Hardware id not formated correctly
Fix: Remove semicolon from hardware id

Location: C:\D\M\A\3\AEC6290.INF
Problem: Hardware id not formated correctly
Fix: Remove semicolon from hardware id

Location: C:\D\M\E\
Problem: Driver is for windows 2003
Fix: Possibly rename folders to k3.

Location:C:\D\M\I\3
Problem:Same driver as in C:\D\M\I\2 just for windows 2003
Fix: Add folder under C:\D\M\I\2 named k3 and add driver to it.

Location:C:\D\M\I\5
Problem: Same driver as in C:\D\M\I\4 just for windows 2003
Fix: Add folder under C:\D\M\I\4 named k3 and add driver to it.

Location: C:\D\M\V\4
Problem: Folder contains 64bit drivers.
Fix: Remove drivers.

Location:C:\D\M\Q\3
Problem: Prompts user to find file during sysprep.
Fix: Change qlsdm.dll=2 to qlsdm.dll=1

Location:C:\D\M\Q\
Problem: Folder contains all 2000 drivers
Fix: Possibly rename folders to K or 2k.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [Final] Mass Storage 711

Hi

searched original, and downloaded the drivers for AEC6280.INF and AEC6290.INF, and the semi-colon is in the originals as well, but not in the original INFs for Win2000. ??? strange.

3\2\2.exe is a disabled driver.

The answer was 42?
Kind regards, Jaak.