I am ever in debt to you guys for providing this wonderful boot disc, and up till today I have always found whatever answer I needed through searching these forums. So let me begin that although I've searched both yesterday and today, and in every combination I could think of - I can't find my answer. So here is to hoping you guys can give a guy a break for posting on a subject that deems a single sentence FAQ entry with no follow up on an explanation of procedure.

To put it simply, I can't get my 2nd RAID controller to show me my RAID5 array. I have 2 RAID controllers, one is a si3114r and the other a si3114r5.
After reviewing the latest MassStorage DriverPack, I have come to the conclusion that the si3114r5 driver is NOT included in it. si3114r IS included but not the RAID5 driver (hence why I can see my first RAID array, but not the second).

I have no idea how to add these missing drivers. I keep reading that you guys send us over to the driverpacks forums and ask nicely to have them added, however although that is a nice solution for the masses to benefit from, I would still like to know how to be able to install my own personal drivers on the disc as we used to be able to do in older versions. Actually, what I'd like to know is a cold hard answer that tells us either "YES you can, and this is how...." or "NO you can't, and this is why...". I'm honestly completely confused on what should be a straightforward answer to what would seem to be a very common problem.

I can't seem to completely understand what happened between v3.0.3 and v3.0.6 on the driver end. All the data I can find out there seems to read that we have 2 options at this point:

1) use the driverpacks for the MassStorage drivers
2) through a fresh install of UBCD4Win, do NOT activate the driverpacks and enter your desired mass storage drivers in <UBCD4Win>\Drivers\SCSI\<FolderName>

Is this correct? Or is it possible to have both the driverpacks installed AND also throw in my own custom drivers? Cause last time I tried by using the path schema listed above, it didn't work.

Please help!

P.S. It seems that my si3114r5 driver was not too popular with some folk and this thread might explain why it was taken out.

Ok.. I'm not "the driver guy" so to speak but I can give you some direction in your questions...

First let me try and address the issue directly... If I'm reading the driver list properly, they do now support both driver sets.. So if they had removed them at one time is appears they've addressed the issue and their back. But before you run off and get the latest driver pack.. might I suggest you try the latest UBCD4Win PRC v3.10 found here http://www.ubcd4win.com/forum/index.php?s=&...ost&p=53910 ... It should be pretty solid and already includes the latest driver pack in it. It would also mean that you wouldn't have to correct a minor issue we made in v3.06 with the driverpacks before you updated them.

From here on... I'm just speaking generically about drivers and the possible issues of trying to use both the driverpack and adding your own... The big issue is that often two different driver sets will use the same filename for the drivers they use... This creates a potential conflict with the drivers causing one driver set to work properly and the other driver set to either cause an error or worse yet corrupt a drive/partition.

So here is my crappy basic example of of the issue...

Take 2 different driver sets... each driver set has its own unique INF file which describes the hardware id's of each set... but both use the same filename... What happens if driver set B overwrites the driver files ( remember they have the same names in this example )... then when a system that actually uses driver set A tries to load, Windows looks up the hardware id and finds it needs the files named the same a driver set B and then attempts to load them. I think you can see that it certainly couldn't go well after that type of problem happens... most of the time I suspect you would see just the typical "IRQ_NOT_EQUAL _OR_LESS" error... but much worse could also happen.

So to answer your question can you do both... yes you can but only if you can also ensure that you don't create a conflict with other hardware id's or filenames in the process. Its much safer to just disable the driverpacks, drop in the driver set that came with your controller in the folder you mentioned ( in its own unique folder name to keep it organized ) and create a build for just that one system... than to chance corrupting the system and then having to repair the damage ( if its even possible then ).

Oh hell... Steeltrepid made a liar out of me while I was typing that... he just pulled the PRC download availability... he is going to release the final tomorrow now... sorry about the misdirection

Sorry, I thought I mentioned that it would be limited time download. I do not like to lie and try to just disappoint......ask my wife about our sex life!!!!

RE: Actually, what I'd like to know is a cold hard answer that tells us either "YES you can, and this is how...." or "NO you can't, and this is why...".

Yes you can!
the how can't be explained in a simple step by step because it's not linear
there are exceptions and special cases and constraints.
the best solution is the recomended one to get us to do it over at driverpacks.
much experience comes into play to make these all work in harmony.

that said - unpack the mass storage pack and look at the INI file for 3114 add your folder and your ini section (docs in the base's docs folder)
you will need to determine your HWID and ensure they are unique (or you are doomed to fail) then edit the inf files for the drivers to ensure your hwid only apears in one driver inf file. and copy the HWIDS you wish to apply to the mass storage.ini then you need to ensure your driver name is not in use already if it is you need to set the tag file name in the mass INI so the driver gets renamed to a unique name. (starting to sound like building an atomic bomb yet) and repack

If you are lucky your si3114r5 driver suppoerts both cards and you can simply update your driver in the pack - it will be neccessary to see if there were any HWIDS commented out by the DriverPacks Team to prevent known conflicts and BSODs. If you are able to update and make this work it would stil be nice if you posted what you did over at Driverpacks in case someone else lands here too.

there is volumes more... much if it is available for the reading at driverpacks.net.
if this is not enough info to get you going.. then just drop it in our laps.

or disable driverpacks and install the old way.

@fuderyuu

Unfortuantely Silicon Image is a big exception.

Silicon Image offers different drivers, but use overlapping HardwareID's.
And BIOS version is importand. This behaviour is highly unusual.

Which hardware do you use? What's the first RAID array?
Which HardwareID's does controller use.

As for 3114 http://www.siliconimage.com/support/suppor...amp;osid=4&
BASE Driver 1.3.10.0 7/28/2006
SATARAID Driver 1.0.20.0 6/24/2007 for SATARAID BIOS 5.0.73
SATARAID5 Driver 1.5.15.0 6/24/2007 for SATARAID5 BIOS 5.4.03
IDE Driver 1.2.0.5 6/30/2005

Currently Silicon Image driver support are under construction.
http://forum.driverpacks.net/viewtopic.php?id=1772

Try current testing massstorage drivers.
Sil si3114, si3114r and si3114r5 are included.
http://forum.driverpacks.net/viewtopic.php?id=2082

Before I forget, I wanted to thank everyone here for their quick, honest, and professional responses. It is such a relief to post a question in the midst of frustration and not receive half-assed answers as well as non-conductive juvenile dribble that basically amounts to "we'll u'r a dumbass for not getting it!"

I'm sorry I won't be able to get to you guys till after the Thanksgiving break. Although I was able to get what I wanted done via another sata drive I was had laying around and connecting that to one of my 2 leftover slots in the Sil3114r controller while disconnecting the RAID5 controller so as to avoid any conflicts, I will still attempt later this week all your suggestions and report back with the outcome. I appreciate your time and efforts, both those involved at UBCD4Win as well as DriverPacks, so I will make sure to not leave you guys without a follow up, however with today being Thanksgiving, I'm sure none of us really are worried or care about this particular problem at this momment.

So, to you all, Happy Thanksgiving.

p.s. Before I got any responses here, I hurriedly tried following this guide in trying to create my own driverpack:
http://www.wincert.net/forum/index.php?sho...0&#entry238

it failed.

hi

over at driverpacks, we have an experimental pack (you could find link in public mass storage forum) which hopes to fix SiLicon Image issues.
What's so special about them?
Well, newest drivers can fail on old BIOS versions, but they have the HWIDs you also find in older drivers..

Some SiLicon simply do not boot. Period.
(it is not exceptional to find them as tertiary controllers, for storage only.)

SiL 3114 is a very special case..
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.

http://forum.driverpacks.net/viewtopic.php?id=2082

I should have scanned the links before I posted.
The SFX_MiniPacks do not have the drivers for SiL 3114.
(Those MiniPacks were invented before SiLicon decided to have all versions for older BIOS available. We want to rid ourselves of the need for them Minis too. The Post has not been updated recently, and I removed some of those Minis because of the fixing in main..)

I bet that in your case, it would be as simple as replacing the three drivers for 3114 with the versions for your BIOS, or still older.
The system files were not renamed, so you would not have to edit the driverpack's INI.
To repack, you need 7zip.
Select both INI and D folder, set to max compression and set to make compact archive.

The solution I think would work for most people is something simple, but if I do it some folks will probably demand I undo it.
I could put the next to oldest drivers for SiLicon 3114 in, because there is good reason to believe (based on older reports) that older drivers work on newer BIOS, whereas I have personal proof that newest drivers do not work on older BIOSes.
(I would use next to oldest because it has the full range of HWIDs.)
Anuway, I think what we have here is an instance of newest ain't best.

Hi, that's because mass storage is not made available for txtmode when you put it in a third party pack.
DpsBase uses the mass storage Pack's INI to slipstream the drivers for txtMode, and only renames the zips in 3party folder.
(It won't work for txtmode even if you put one you download from us, in there.)

I tried this version, without adding anything nor running the DriverPacks.net - BASE and it still wasn't able to load the RAID5 array, only the SIL3114r with the 2 mirrored drives.

After rebooting and trying to build a new UBCD4Win and enabling the DriverPacks.net - BASE I received 2 error messages, the first was a crash report of the MakeCab program crashing, then this error message:



I assumed that the mass storage DriverPacks were already comipled and set by default in v3.10, that's why I didn't try to run it the first time round.

So did I approach the v3.10 wrong, or did I do something wrong?

As said, there is Silicon Image development under construction.
This testing massstorage driver pack is not part of UBCD4Win v3.10.

Try this testing massstorage driver pack yourself. Currently DP_MassStorage_wnt5_x86-32_711_nightly.7z
http://forum.driverpacks.net/viewtopic.php?id=2082
Download file and copy to plugin\DriverPacks.net\BASE\DriverPacks\

Launch UBCD4WinBuilder.exe, goto plugins, goto line "# DriverPacks.net - BASE - Press <CONFIG> to enable or reset DriverPacks plugins"
Select CONFIG.

This creates a new "# DriverPacks.net - MassStorage". This is enabled.
Don't enable "# DriverPacks.net - BASE - Press <CONFIG> to enable or reset DriverPacks plugins"

CAB compress does work here. XP is running.
Which running windows do you use? Which virus scanner or protection software do you use?

And which HardWareIds does your controllers use?