can you test this one for us, please?
http://rapidshare.com/files/22957253/DP … nightly.7z
--------------------

-M-M
Update marvell Driver
replaced Ver= 11/14/2006,1.1.0.51 with marvell downloaded from intel 02/09/2007,1.2.0.24
(this version does not conflict with iastor)

[Marvell]
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6101
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6111
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6121
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6122
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6145

-M-M-O
old marvell DriverVer= 01/06/2006,1.0.0.3 Edited out HWID supported by newer version
Enabled for these three
PCI\VEN_11AB&DEV_6120
   PCI\VEN_11AB&DEV_6140
      VEN_11AB&DEV_6141

Massstorage INI update

removed a duplicate entry
[V-3] appeared twice
adjusted drivercount

edit to Highpoint [H-1] (reported by overflow, confirmed jtdoom)
a Fix for win2003, driver does not exist in XP. (also a Bart_PE fix)

Fixed (Muiz)
ATI (Siliconimage) 3112 driver
-\M\S\4 10/23/2006, 1.3.67.0

Test
edit in Mass storage ini makes Silicon Image raid mode drivers load before Silicon Image NON-raid

a couple guys, we banged our heads together some.
one can edit the mass storage INI, and repack.
one can actually change order by cut/paste a section

that way, if you have raid mode, and see that non-raid mode driver for same chip is listed before this (in the ini), move it and make it load later.
close the notepad editor, and save.
repack, using 7zip

the textmode.sif will then put them in after those that you think conflict.

for god's sake, let us KNOW if a change you made solved an issue, and which issue, so we can adress it, and find a permanent solution.

if it has an impact on a chip that can be used with drives in different modes, it could be that another solution has to be found by the team, for your hard drive mode could conflict with his mode.
(array/no array)
(no array/array)

for single drives, also report issues like "ahci mode does not work"

Changing modes in BIOS for a single drive that is in use, that has been known to be a problem, so... if you did that, tell us.

these days, the mass storage INI can be edited.
One can quite easily disable drivers by changing a 1 to zero
an example
[3-2]
; Disabled! This driver conflicts with the Silicon Image 3112r and Silicon Image 3132 drivers.
ms_count             = 0

I do not know wether Ruud thought about the order, but it is worth looking into.

Found this problem on a si3114, but should be applicable to any controller that has seperate raid and non raid drivers.

The si3114.sys gets loaded BEFORE si3114r.sys. This causes problem if you have configured a raid set since that will not be recongnized by the first driver. The si3114r.sys has to be loaded before si3114.sys for correct behaviour.

This can easily be fixed by changing the order in the driver pack inf file.