DriverPacks.net Forum - SAS vs SATA vs RAID vs Bus-Extenders

Re: SAS vs SATA vs RAID vs Bus-Extenders

null@example.com (Jaak) — Fri, 13 Jul 2007 19:43:20 +0000

@ Helmi et OverFlow et EchoPlatoon.
That HWID database Helmi just stickied lists some interesting facts.
http://forum.driverpacks.net/viewtopic. … 573#p12573

Rich, this work we did will pay off.
You can see I posted a link to what we worked on.
Its based on what's in Mass storage INI.
And, what's in the INI must not cause a conflict once PnP runs.
Therefore, some INF's got edited.

Jeff, our work on LAN can be linked to too.
(it has relevance, because what we did was useful in dupe filenames/INF names)

Why I started this topic is obvious now.
Some drivers cannot be IN the packs.
A driver for NEWER BIOS/Firmware causes BSOD when the user has OLDER BIOS/firmware, and when the ORIGINAL old and ORIGINAL newer have 100 percent HWID match, there is NO WAY to write an exception that would find a NON-COMMON to disable the other driver.
THE EDIT HERE ADDED ORIGINAL to above paragraph.
(because some INF had changes, origininal content must looked at too.)

The SFXminiPacks idea was approved.
If we have a single HWID in a BIOS for an OLD BIOS that is NOT in the newer driver, then I would very much like to see exceptions written so that both BIOS versions of a chip could be in the DriverPacks.

I would not know how to write that sort of exception, but, we's going to be a team with real solutions.

Re: SAS vs SATA vs RAID vs Bus-Extenders

null@example.com (Helmi) — Fri, 13 Jul 2007 18:32:51 +0000

OverFlow wrote:

looks like it might be like the raid / non raid thing again
or just a duplicate?

Yeah, but without the ususal different HWIDs for each case...

I wish HW manufacturers would put more efford into the IDs.
It can't be that hard to manage that properly, especially since they already re given unique manufacturer IDs in the first place!

Re: SAS vs SATA vs RAID vs Bus-Extenders

null@example.com (Echo_Platoon) — Thu, 12 Jul 2007 12:35:20 +0000

I was reading on IBM that SAS drives use RAID functionality on such controllers as ServeRAID 8s which is one of the controllers in both [I-4] and [I-5]

Here is the article on IBM's website about ServeRAID 8s.
http://www-304.ibm.com/jct01004c/system … GR-5069848

Under "Features, functions, and key advantages" on that page, it states that "IBM ServeRAID 8s SAS Controller (39R8765)" "Functions as a hard drive RAID controller".

Re: SAS vs SATA vs RAID vs Bus-Extenders

null@example.com (OverFlow) — Thu, 12 Jul 2007 05:55:52 +0000

looks like it might be like the raid / non raid thing again
or just a duplicate?

Re: SAS vs SATA vs RAID vs Bus-Extenders

null@example.com (Jaak) — Thu, 12 Jul 2007 00:11:02 +0000

yep, Mr. Holmes, you are right.
Those INI sections do not exist in the release.

But, the files for i-3, i-4, i-5 and i-6 are in the pack. (I think a request was not finalised, but the files were in none the less)

Ruudboek, if you read this, have a look.
they are all SCSI miniport, and i-5 is SAS

SAS vs SATA vs RAID vs Bus-Extenders

null@example.com (Jaak) — Thu, 12 Jul 2007 00:05:10 +0000

Many Mass Storage drivers we download have overlap in HWIDs.

we have a dillemma.
http://en.wikipedia.org/wiki/Serial_Attached_SCSI

We must know wether SAS and server RAID drivers can co-exist in the DriverPacks.

full overlap.

[I-4]
ms_count=1
ms_1_deviceName="IBM ServeRAID 8i/8k/8k-l/8s RAID by ADAPTEC"
ms_1_tag="aacsas"
ms_1_sysFile="aacsas.sys"
ms_1_hwids="PCI\VEN_9005&DEV_0285&SUBSYS_02f21014,PCI\VEN_9005&DEV_0286&SUBSYS_95801014,PCI\VEN_9005&DEV_0286&SUBSYS_029D9005,PCI\VEN_9005&DEV_0286&SUBSYS_029C9005,PCI\VEN_9005&DEV_0286&SUBSYS_029B9005,PCI\VEN_9005&DEV_0286&SUBSYS_02A09005,PCI\VEN_9005&DEV_0286&SUBSYS_02A69005,PCI\VEN_9005&DEV_0286&SUBSYS_02A19005,PCI\VEN_9005&DEV_0285&SUBSYS_02989005,PCI\VEN_9005&DEV_0285&SUBSYS_02999005,PCI\VEN_9005&DEV_0285&SUBSYS_029A9005,PCI\VEN_9005&DEV_0285&SUBSYS_02A49005,PCI\VEN_9005&DEV_0285&SUBSYS_02A59005,PCI\VEN_9005&DEV_0285&SUBSYS_034D1014,PCI\VEN_9005&DEV_0286&SUBSYS_02A29005,PCI\VEN_9005&DEV_0286&SUBSYS_02A39005,PCI\VEN_9005&DEV_0286&SUBSYS_02AC9005,PCI\VEN_9005&DEV_0286&SUBSYS_02A79005,PCI\VEN_9005&DEV_0286&SUBSYS_02A99005,PCI\VEN_9005&DEV_0286&SUBSYS_02B39005,PCI\VEN_9005&DEV_0286&SUBSYS_02B49005,PCI\VEN_9005&DEV_0286&SUBSYS_02A89005,PCI\VEN_9005&DEV_0286&SUBSYS_02AA9005,PCI\VEN_9005&DEV_0285&SUBSYS_02B59005,PCI\VEN_9005&DEV_0285&SUBSYS_02B69005,PCI\VEN_9005&DEV_0285&SUBSYS_02B79005,PCI\VEN_9005&DEV_0285&SUBSYS_02B09005,PCI\VEN_9005&DEV_0285&SUBSYS_02B515D9,PCI\VEN_9005&DEV_0285&SUBSYS_02B615D9"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="wxp"
ms_1_exc_disableIfOS="w2k"
ms_1_exc_replaceIfOS="w2k3"



[I-5]
ms_count=1
ms_1_deviceName="IBM ServeRAID 8i/8k/8k-l/8s SAS MiniPort by ADAPTEC"
ms_1_tag="arcsas"
ms_1_sysFile="arcsas.sys"
ms_1_hwids="PCI\VEN_9005&DEV_0285&SUBSYS_02f21014,PCI\VEN_9005&DEV_0286&SUBSYS_95801014,PCI\VEN_9005&DEV_0285&SUBSYS_034D1014,PCI\VEN_9005&DEV_0286&SUBSYS_029D9005,PCI\VEN_9005&DEV_0286&SUBSYS_029C9005,PCI\VEN_9005&DEV_0286&SUBSYS_029B9005,PCI\VEN_9005&DEV_0286&SUBSYS_02A09005,PCI\VEN_9005&DEV_0286&SUBSYS_02A69005,PCI\VEN_9005&DEV_0286&SUBSYS_02A19005,PCI\VEN_9005&DEV_0285&SUBSYS_02989005,PCI\VEN_9005&DEV_0285&SUBSYS_02999005,PCI\VEN_9005&DEV_0285&SUBSYS_029A9005,PCI\VEN_9005&DEV_0285&SUBSYS_02A49005,PCI\VEN_9005&DEV_0285&SUBSYS_02A59005,PCI\VEN_9005&DEV_0286&SUBSYS_02A29005,PCI\VEN_9005&DEV_0286&SUBSYS_02A39005,PCI\VEN_9005&DEV_0286&SUBSYS_02AC9005,PCI\VEN_9005&DEV_0286&SUBSYS_02A79005,PCI\VEN_9005&DEV_0286&SUBSYS_02A99005,PCI\VEN_9005&DEV_0286&SUBSYS_02B39005,PCI\VEN_9005&DEV_0286&SUBSYS_02B49005,PCI\VEN_9005&DEV_0286&SUBSYS_02A89005,PCI\VEN_9005&DEV_0286&SUBSYS_02AA9005,PCI\VEN_9005&DEV_0285&SUBSYS_02B59005,PCI\VEN_9005&DEV_0285&SUBSYS_02B69005,PCI\VEN_9005&DEV_0285&SUBSYS_02B79005,PCI\VEN_9005&DEV_0285&SUBSYS_02B09005,PCI\VEN_9005&DEV_0285&SUBSYS_02B515D9,PCI\VEN_9005&DEV_0285&SUBSYS_02B615D9"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="wxp"
ms_1_exc_disableIfOS="w2k"
ms_1_exc_replaceIfOS="w2k3"