anyway both drivers seems to work great with my mobo.  asus a7n8x deluxe rev1.04, 1008 bios modded with latest sil3112 rom.

Thanks JakeLD.
I'll look at the update.
I should update the excell files one of these days.

updated to 8044

[V] from 07/12/2007, 5.1.6000.562 to 01/22/2008, 5.1.6000.574 [5.16a]

[edit Jaak]  I updated the link to new version created by jakeLD.

DP_MassStorage_wnt5_x86-32_8044Test.7z

 '8.04',
'11 April 2008',
'INI change; sorted Silicon Image sections into THREE blocks'.
'|Marked blocks Silicon Image softRAID (aka RAID-5) and Silicon Image RAID and Silicon Image NON-RAID'.
'|NON-RAID load after softRAID-5 and RAID.'.
'|[S8A] silicon Image removed (see [S8]).',
'INI Fixes in [C1], [C3], [D1], [L2], [N-6] (OverFlow.) '.
'|INI fix, [S8] supports HWIDS we had in [S8A]',
'[S2] from 11/15/2006, 1.2.26.0 to 11/13/2007, 1.2.30.0'.
'|[S4] from 04/13/2007, 1.3.68.2 to 06/28/2007, 1.3.70.0'.
'|[S7A] from 11/02/2004, 1.0.0.8 to 10/03/2007, 1.0.21.0'.
'|[S8] from 08/22/2006, 1.3.20.0 to 11/20/2007, 1.3.21.0'.
'|[V] from 07/12/2007, 5.1.6000.562 to 01/22/2008, 5.1.6000.574 [5.16a] (JakeLD)'

and, it has something what could perhaps fix intel AHCI when AHCI is set in BIOS.

11 april, update by JakeLD (from 8043 to 8044 testversion)

devcon hwids =SCSIAdapter > temp.txt & notepad temp.txt

If you can Post the result here it may help us to resolve this issue for you and others...

thanks

for Silicon 3112 IDE compatibility mode we have 04/13/2007, 1.3.68.2

Conclusion,
If you have a series of these machines, you have to put the raid below the IDE, or remove the IDE section [s4].
I will get to WU and update the [S5] driver.

You are probably right, though it didn't prompt that way on install.  However, the device manager behavior was certainly peculiar.

What I did next, was to go into device manager and do an update driver.  I put the original CD that did NOT work during the install.   There are literally hundreds of drivers for all different make pieces of hardware.  It found something and installed it.  With great trepidation, I rebooted.  It came up fine.  The yellow ! was gone in device manager and on the driver it said:
Silicon Image SiL 3112 SATARaid Controller
Silicon Image
1.0.0.51
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&2B96F39&0&48F0

Next I went to the Microsoft update site to see if it wanted to replace the driver.  It did.  I opted to take the hardware install, and deselected XP SP3 so as not to inject too much carnage.  It rebooted, I went into Device Manager, only this time no yellow !.
Silicon Image
8/17/2007
1.0.62.0
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&2B96F39&0&48F0

The driver we have for the RAID is located in D\M\S5.
In the testpack I have uploaded this month there are no Bios variants mentioned for this Raid-driver.

--------
(Link killed) DP_MassStorage_wnt5_x86-32_803RC3.7z
This testpack has the following changes when we compare to released mass storage driver pack.

[N-TM] loads after other Nvidia
[N-TM] contains two extra abit HWIDs
INI Fixes by Overflow for server and windows 2000.
INI fix for Symmpi for XP.
INI fix for [N-6] by OverFlow

S8A,  Silicon removed
V3, Via updated

Silicon sections now in THREE blocks so that a user can easily move these around or remove these from INI.
Silicon image load order changed
first softraid, then raid, then base-ide

It does not yet fix AHCI. (an intel driver, we will probably roll back to an older version with same HWIDs.)
-------------
Because there are quite a few changes in INIyou should NOT re-stream an old source.
Use a fresh copy of a source you have not yet used DriverPacks on.
Make another copy of that to fall back to..

Now, if this testpack does not work, I will ask you do the following.
Unpack this testfile.

Open the mass storage.INI, and move section [s5] under all other.
Close, and save changes.
Then recompress. (select INI and D, rightclick to run 7zip.)
7z, ultra, lzma, 256wordLength, compact.
Use the changed file to stream a new copy.

Test.
And if THAT works, I will want to know.

I would also like to know what the DEFAULT setting in the chip's BIOS is.
I've always assumed RAID is the most used default, but in LAPTOPS we see that the chip was set to IDE-mode.

Users can move the sections (and delete them..)
We know that the driver we put last in INI loads last, and for some reason windows setup sometimes decides that this one is the best match..
(despite specific HWIDS..)
So, we have to make people aware that the mass storage DriverPacks IN can be edited to change load order.

We do have FAQ about trimming  mass storage..
------

If you are in a real hurry, you CAN unpack the mass storage DriverPacks, and tell windows to use the driver in D\M\S5.

I would like it VERY much that you test the pack I link to, and if you have to change load order to make it work so be it, but you would learn something, and we will learn something as well.
Please help us help you.
Your first post was thought out and helpful.

That is quite interesting.
I will look at the mass storage pack and see what I put in there.
I will also look at windows update site, because I think these WU drivers will work regardless of which BIOS that thing uses. If we can reduce the number of drivers for silicon, I would.

I may ask you to test a mass storage testpack with the changes in it, and hope you will when I make it available.
Thanks for the help.

When you reply in another topic, please hit the subscribe link. (or bookmark it.. hit the link is easier..)
This board does not automatically subscribe you and you cannot change the default.