it is a TEST version
http://forum.driverpacks.net/viewtopic.php?id=1637

-Grub3r

There is no problem in disabling the sis drivers, those will be installed later in device installation portion of xp installation. Those come up with 2110 as you were saying yes. Maybe it's at all not necessary to have those implemented?

I'm getting BSODs until I disable sis driver in masstorage ini file. Currently using 707.1 and it works fine. If I use your driverpacks, I do NOT have to run the siemens CD to install RAID drivers on the computer. The RAID device is recognized by windows installation(together with driverpacks).

will mail you the siemens driver later today.

-Grub3r

Will reply with feedback.

-Grub3r

Q; But why does it come up with BSOD when the same driver is used in graphical portion of installer?

the answer to that?
1, the drivers cannot co-exist on the CD.
2, the 2030 was the one that got updated to 2110

now IF you used the nightly. but DID YOU?
then answer 3 is> version 2110 wont do it in TXTmode.

Did you try that nightly?

When installing from xp cd the driver does not appear in device manager, it doesn't even gets as unknown device. It's not there at all. When I install drivers from drivers CD that came with the computer I get this driver:

;
; SiSRaid.INF
;
; INF file of SiS 180/182 RAID Controller for Windows XP/2000/2003
; Copyright (c) 2003 SiS Technologies, Inc. All rights reserved
;

[Version]
signature="$Windows NT$"
Class=SCSIAdapter
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
CatalogFile=sisraid.cat
Provider=%SiS%
DriverVer=01/05/2005,5.1.1039.2030

[DestinationDirs]
DriverCopyFiles  = 12    ; DIRID_DRIVERS
PropCopyFiles = 11       ; Prop page

[ControlFlags]

[Manufacturer]
%SiS%=SiS

[SiS]
;%PCI\VEN_1039&DEV_0180&REV_01.DeviceDesc%=SIS182PCI,PCI\VEN_1039&DEV_0180
;%PCI\VEN_1039&DEV_0180&REV_01.DeviceDesc%=SIS182PCI,PCI\VEN_1039&DEV_0181
%PCI\VEN_1039&DEV_0182&REV_01.DeviceDesc%=SIS182PCI,PCI\VEN_1039&DEV_0182

When installing with disabled SI-1->SI-3 and all other drivers integrated in unattended installation the device gets recognized and comes up with latest driver from you. 11.01.2007/5.1.1039.2110

How is that. Ohh.. maybe the only portion that does not work is the text installer for RAID drivers, those are copied together with the rest of the drivers and get installed at the graphical portion of installer.

But why does it come up with BSOD when the same driver is used in graphical portion of installer.

-Grub3r

fixes
Intel Iastor error surfaced on Lattitudes, completely redid IASTOR drivers.
Promise 378/376 issue.
compared with new downloads, [P-2] and [P-2-K] was NOT for 378/376..
downloaded new drivers for 378/376.
downloaded new drivers for TX4000/S150 TX2plus/S150 TX4.
downloaded new drivers for FastTrak S150 SX4/SX4000 Series
INI for \P\2 and \P\2\K and \P\2\k3 (08/06/2003, 1.00.0.37).
Silicon Image BIOS issue, old/new drivers cannot co-exist.
Silicon Image 3112/3512 BIOS issue, created SFX file for BIOS 4x79.
Silicon Image 3112R/3512R RAID BIOS issue, created SFX file for BIOS 4x79.
SiS 180-181 issue: another bad case on HWID overlap.
SiS downloaded and compared. [Si-1] is considered obsolete.
[Si-2]cannot co-exist with [Si-3]. Made SFX file and removed older.,

New
\P\2\k3 Promise FastTrak TX4000/S150 TX2plus/S150 TX4 for Win2003 , 08/06/2003, 1.00.0.37.
\P\4\K Promise FastTrak S150 SX4/SX4000 Series for W2K, 05/20/2004, 2.00.00.25.
\P\4\K3 Promise FastTrak S150 SX4/SX4000 Series for W2K3, 05/20/2004, 2.00.00.25.       
\P\B Promise FastTrak 376/378 for XP, 06/16/2003,1.00.1.30.
\P\B\k Promise FastTrak 376/378 for W2K, 06/16/2003,1.00.1.30.
\P\B\k3 Promise FastTrak 376/378 for W2K3, 06/16/2003,1.00.1.30,
SFX 7zip files for devices that cannot co-exist.
SFX have drivers and INI sections..

(this is from changelog, this txt was stripped from whats ready in php)

==================================================================

7.07.2 NIGHTLY does NOT have the SFX in them

[THIS NIGHTLY HAS HAD AN UPDATE°)
link pulled
see later in topic
-------------------------
THESE DRIVERS CANNOT CO-EXIST.
These SFX files are for your convenience.
The TEXT with the latest updates in SFXminiPacks will be here.
http://forum.driverpacks.net/viewtopic.php?id=1772

Hmmmm... These reports about problems began with that update..

Now I have tested this new sfx3 and it doesn't work. As it uploaded and with this change:
;[SI-2]
; Disabled! Si_2.exe 7zipSFX in folder \Si\2. Conflicts with Si\3
   

[SI-3]
; If you disable this section, keep only Si_3.exe 7zipSFX in folder \SI\3
; If you enable this, disable Si-2 section and keep only its 7zipSFX in \Si\2
ms_count=1
ms_1_deviceName="SiS 180/182 RAID Controller"
ms_1_tag="sisraid2"
ms_1_sysFile="sisraid2.sys"
ms_1_hwids="PCI\VEN_1039&DEV_0182,PCI\VEN_1039&DEV_1182"
ms_1_isBusExtender=false

You had hwids for both 180 and 181 when the inf file has those disabled . It didn't help to remove these hwids either.

When I changed ms_count=0 and let the windows load the driver it goes through without bsod.(maybe it's siemens)

Xp self recognizes the raid controller so I think I just disable the SI-1->SI-3 sections in the ini file.

Anyway thanks for the try and nice project.
-Grub3r

will be testing it today.

-Grub3r

contains same drivers as mentioned in that txt with changes
(log is telling you what is different compared to the released version)
(there were some instructional txt changes for the SFX stuff)

method of SFX's inside releases is not approved
testlink pulled..