41 replies to this topic

[Dave7]

I have a "Tower Raid" with 4 drives. Sil 3132

Driver works fine with SATA option checked: 2 Raid1 (mirrored HDs) are correctly detected.

Driver doesn't work with DP option checked: 4 Drives are incorrectly detected.

So there seems to be an issue with DP and RAID?

Cheers,
Dave

[Galapo]

Please post the HWIDs for the device.

Thanks,
Galapo.

[Dave7]

Here is the HWID

PCI\VEN_1095&DEV_3132&SUBSYS_71321095&REV_01\4&1B30CF2&0&00E0: Silicon Image SiI 3132 SoftRaid 5 Controller

I also have (but works fine)
PCI\VEN_8086&DEV_2822&SUBSYS_1082147B&REV_02\3&2411E6FE&0&FA: Intel® ICH8R/ICH9R/ICH10R/DO SATA RAID Controller

Cheers,
Dave

[Galapo]

Hmmm, hwid 'VEN_1095&DEV_3132&SUBSYS_71321095' appears in the DP, and entries generated in the script appear correctly for it:

IniWrite,"%target_win%\txtsetup.sif","HardWareIdsDatabase","PCI\VEN_1095&DEV_3132&SUBSYS_71321095","#$q3132R5C#$q"

IniWrite,"%target_win%\txtsetup.sif","SourceDisksFiles","3132R5C.SY_","1,,,,,,4_,4,1,,,1,4"

IniWrite,"%target_win%\txtsetup.sif","SCSI.Load","3132R5C","3132R5C.SY_,4"

IniWrite,"%target_win%\txtsetup.sif","SCSI","3132R5C","#$qSilicon Image 3132 SoftRaid 5 for BIOS 7223#$q"

Extract Si3132r5.sy_ from the sata script and rename it to 3132R5C.SY_. Then copy it to 'Workbench\Common\DPs\MassStorage\ScriptFiles\common' (replacing the file that was there). Then rebuild the project with the DPs Mass Storage Drivers script selected (do not rebuild it otherwise you'll overwrite the copied file!). Then see if you have access to your disks.

Thanks,
Galapo.

[Dave7]

I will try this, but just to clarify: I have access to all four disks. However all four disks are listed individually. There should be only two Raid1 drives (). That's the strange part.

Cheers,
Dave

[Galapo]

OK, I understand what you mean now. Test and see if what I said works, then we can go from there.

Regards,
Galapo.

[Dave7]

Galapo, there is no 3132R5C.SY_ in 'Workbench\Common\DPs\MassStorage\ScriptFiles\common'. That's probably the issue?

Edit: Actually there is :-)

Cheers,
Dave

[Galapo]

There should indeed be that file.

Open up DPs-MassStorageDrivers.script in either the WB editor or a text editor like notepad and post the line Description= line. I'm now wanting to know which mass storage pack version you built with.

Thanks,
Galapo.

[Dave7]

Galapo, yes, the file is there.

Both, scripts are v37 and I can see you are actually the author :-)

Description=Adds DriverPacks Mass Storage drivers to the build. Script has been automatically generated from DP BASE version '805' and mass storage pack version '805'. Suitable for XP or 2003. (Adds ~8.37mb to the build.)

Cheers,
Dave

[Galapo]

OK, good. Please return to the original test as DP is fine. Let's see if the replaced file makes any difference.

[Dave7]

No difference, unfortunately. Verified with MD5 to make sure the copied file made it into the build.

Cheers,
Dave

[Galapo]

OK, rename 3132R5C.SY_ to SI3132.SY_.

Then change these line in DPs-MassStorageDrivers.script

IniWrite,"%target_win%\txtsetup.sif","SourceDisksFiles","3132R5C.SY_","1,,,,,,4_,4,1,,,1,4"

IniWrite,"%target_win%\txtsetup.sif","SCSI.Load","3132R5C","3132R5C.SY_,4"

to

IniWrite,"%target_win%\txtsetup.sif","SourceDisksFiles","SI3132.SY_","1,,,,,,4_,4,1,,,1,4"

IniWrite,"%target_win%\txtsetup.sif","SCSI.Load","3132R5C","SI3132.SY_,4"

The rebuild the project again and see if there's a difference.

Thanks,
Galapo.

[Dave7]

Sorry for the late response, but I had problems accessing this forum :-)

I did the changes and tried again, but with the same result unfortunately.

Cheers,
Dave

[Galapo]

Try changing the lines now to:

IniWrite,"%target_win%\txtsetup.sif","SourceDisksFiles","SI3132.SYS","1,,,,,,4_,4,1,,,1,4"

IniWrite,"%target_win%\txtsetup.sif","SCSI.Load","3132R5C","SI3132.SYS,4"

Thanks,
Galapo.

[Dave7]

Didn't work either. Is there a tool to verify the test is correct? What driver is actually loaded instead etc?

Cheers,
Dave

[Galapo]

Running 'devcon driverfiles *' doesn't seem to list files for mass storage devices under PE unfortunately.

What I'm trying to do is to find out which difference between the sata2 script and DP script introduces the difference. So far we changed back to the driver file from the sata2 script, we changed its name back to its original, we've altered the service name back to its original. There's only one more, and that's to remove the line

IniWrite,"%target_win%\txtsetup.sif","SourceDisksFiles","SI3132.SYS","1,,,,,,4_,4,1,,,1,4"

Regards,
Galapo.

[Galapo]

Hold it!

Likely we've been working on the wrong driver and service entry, as at some point in the DP a change in naming was introduced that seems to now have been reversed. Hence for 805, which I just rebuilt to check, we have:

IniWrite,"%target_win%\txtsetup.sif","HardWareIdsDatabase","PCI\VEN_1095&DEV_3132&SUBSYS_31321095","#$qSI3132B#$q"

This hopefully explains why we haven't seen a difference despite altering things to conform to the sata2 script.

Unfortunately, what this means is that we should start again. So:

First test: extract SI3132.SY_ from sata2 script, name it to SI3132B.SY_, and copy it to 'Workbench\Common\DPs\MassStorage\ScriptFiles\common'. Rebuild ISO and test.

Sorry,
Galapo.

[Galapo]

An even quicker test. Change this entry in DPs-MassStorageDrivers.script

IniWrite,"%target_win%\txtsetup.sif","HardWareIdsDatabase","PCI\VEN_1095&DEV_3132&SUBSYS_31321095","#$qSI3132B#$q"

to

IniWrite,"%target_win%\txtsetup.sif","HardWareIdsDatabase","PCI\VEN_1095&DEV_3132&SUBSYS_31321095","#$qSI3132#$q"

[Galapo]

An even quicker test. Change this entry in DPs-MassStorageDrivers.script

IniWrite,"%target_win%\txtsetup.sif","HardWareIdsDatabase","PCI\VEN_1095&DEV_3132&SUBSYS_31321095","#$qSI3132B#$q"

to

IniWrite,"%target_win%\txtsetup.sif","HardWareIdsDatabase","PCI\VEN_1095&DEV_3132&SUBSYS_31321095","#$qSI3132#$q"

I take that back. I checked the SI3132.sy_ driver and it is not the same as the one in the sata2 script, so this test cannot be used as an alternative to the one above. That is to use the SI3132B service name, extract SI3132.SY_ from sata2 script, name it to SI3132B.SY_, and copy it to 'Workbench\Common\DPs\MassStorage\ScriptFiles\common'.

Regards,
Galapo.

[Galapo]

Goodness me. I've checked over the posts here again to see where we might be going wrong, and at some point I started to use HWID VEN_1095&DEV_3132&SUBSYS_31321095 rather than VEN_1095&DEV_3132&SUBSYS_71321095!!

So I've made things a little easier. Please use this script here: http://galapo.boot-l...Si3132r5.script. Place it in the \storage\ folder and disable all other mass storage driver scripts. Then test one option at a time and post back which worked and which didn't.

Thanks,
Galapo.

[Dave7]

Thanks, will test it. Will take some time :-)

Here is also the link to the original driver.

http://www.siliconim..._15180_logo.zip

Not sure whether that would help you.

Cheers,
Dave

[Dave7]

One more question. It looks like that the driver SI3132r5 in the "newer" folder is actually a very old driver from

http://www.siliconim...2_raid_1231.zip.

The driver SI3132r5 in the "older" folder is actually one of the new drivers.

http://www.siliconim...6_1550_logo.zip

Any idea?

Cheers,
Dave

[Galapo]

I chose "newer" for "newer script" = DP script. I chose "older" for "older script" = sata2. I didn't mean to imply driver version. I also have noticed that the one in the sata2 script is a newer version.

Regards,
Galapo.

[Dave7]

I changed "newer" with "older" in the "test1" section in your script and then it worked (let's call this case test0).

By the way, the BIOS version of my controller is 7405.

Cheers,
Dave

[Dave7]

I believe there is a problem with the information in DriverPack_MassStorage_wnt5_x86-32.ini

The HWID in my case is PCI\VEN_1095&DEV_3132&SUBSYS_71321095 and the BIOS is 7405. According to Silicon Image the driver 31232R5C5 should be used (version 1.5.18). But the DriverPack_MassStorage_wnt5_x86-32.ini specifies 3132R5C (which is a very old driver 1.2.3.1). Could that be the problem?

Cheers,
Dave