Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450)
It's in your mailbox.
You are not logged in. Please login or register.
DriverPacks.net Forum » DriverPack Mass Storage » [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450)
It's in your mailbox.
http://dev.driverpacks.thesneaky.com/dr … nightly.7z
ace7dfff377f7a832db0df4d4ad749ce DP_MassStorage_wnt5_x86-32_7124nightly.7z
SiLicon Hyll changes..
This 7124 nightly has 1.1.56.1 sil3112R in \S5
This driver came from ATI and uses same system binaries as the 3112 RAID driver 1.x.56.x from SiLLyCon.
(It can be found in older catalyst downloads.)
The three HWIDS which could clash with BASE mode driver got tagged with CC_0104 tags in INI only.
The corresponding BASEmode HWIDs in \S4 were tagged with CC_0101 in INI.
Folders \S5A and S5B were removed
(Hey, I am actually GLAD you guys reported that this Raid driver, which SiLicon claims to be for bios 4.x.79, works for older BIOS versions.)
The driver for BIOS 4.x.83 is still in \S5C, and supports a single HWID...
---------
fixes in IB4, Ib5 and AD1 which listed competing SAS HWIDs for the new adaptec.
(A new adaptec in ADb competes with drivers across three folders)
there is a new adaptec in ADa
SiS 180/181/182 1039.1070 in SiS
SiS1 has Sis 1182 HWID (1039.2110)
Intel ICH7/ICH9 update to 09/29/2007,7.8.0.1012
One of the LSI SAS driver required a fix as well.
----
Here's a guess as to why sil3112 would BSOD.
Yesterday it occurred me we loaded the same system binaries TWICE.
%)
It's in your mailbox.
I just got that.
I compared it against the other drivers.
The HWIDs list is an exact match with silicon's driver for Bios 4x83.
(which is a much shorter list than what is in 1.1.56.1)
Just got back from a christmas party. . .
Again try'd your latest testpack.
I'm sorry jaak, still no go, same result: bsod
I also did the promised test with the latest drivers directly from the Silicon website.
Driverver=02/01/2007, 1.0.60.0, integrated with Nlite.
Those work also very well again, a full installation whitout a hitch.
Looks like there is still something very different between the way the driverpacks integrate and how Nlite does it.
Can i be of any service with files from that XPCD ??
If so, which one's do you need?
can you get to the setupapi.log in the windows folder and post the portions related to the si3112 you could put th ewhole thing here but it will take at least three posts
Hi
Three questions
1; instant BSOD, or on restart?
2; RAID array or single drive?
3; current BIOS
usficcient
Usficcient mailed me the RAID drivers, so I assume he runs with RAID array on a
DFI RS482 Infinity - Silicon Version 4.2.49,
SB450 based ATI 437A Serial ATA Controller (Si3112r.inf)
usficcient could try the x84 from SILICON with Nlite, and not do mass storage.
If the newest works on old BIOS, it would be a LOT easier.
He reported he can run on Latest WU: via Windows Updates
1.0.60.0 2/1/2007
BAM
BAM runs on RAID array
- ASUS A7N8X-XE Deluxe Mainboard with a integrated SiI 3112 Sata controller
- SiI3112 Bios version: 4.2.47 (on screen showed during boot)
- Configuration is a Raid-0 set (with 2x 120GB)
Used Nlite on the following:
- XPpro, SP2 (english)
- Integrated driver version: 03/14/2006, 1.0.56.1 (directly from Sillicon website)
Nothing else, and it works pretty well.
BAM has BSOD.. (when? on restart?)
Stiertje
Stiertje had INSTANT death
Stiertje tried earlier testpack on BIOS 4.2.83 and 4.2.84.
(it was not clear what he meant. The driver or the BIOS?)
(the Silicon site says 4.2.84 and download section then says 4.x.83)
Is that in a RAID array?
At the moment, I think we have something badly wrong with the BASE-mode drivers.
I mean, So far, it looks like the newer drivers all work on all BIOSes for this 3112 chip.
The OLDER driver versions were (re-)introduced on the assumption that this was not the case, and that assumption was made because OTHER silicon chips do have that problem.
I think I will go back to the 3112 Base mode driver we used in the earlier release.
I explained to BAM that older drivers should work on newer BIOSes, because people can Flash, and then reboot into windows just fine. I also know that SiL 3132 newest driver does NOT work on OLD bios.
One guy (at work) told me the pack worked on 3112.
--------
We will need the HWID from those machines that do a BSOD.
Meanwhile, I will work on the next test release.
(undo some Base-mode drivers for 3112..)
Last edited by Jaak (2007-12-23 18:44:45)
usficcient
Usficcient mailed me the RAID drivers, so I assume he runs with RAID array on a
DFI RS482 Infinity - Silicon Version 4.2.49,
SB450 based ATI 437A Serial ATA Controller (Si3112r.inf)
I'm not running any type of RAID array although the drivers are available on my system. I think the Si3112r drivers kill two birds in one stone by providing functionality for both isolated SATA and or RAID configurations.
usficcient could try the x84 from SILICON with Nlite, and not do mass storage.
If the newest works on old BIOS, it would be a LOT easier.
He reported he can run on Latest WU: via Windows Updates
1.0.60.0 2/1/2007
Where is the "X84 driver" from Silicon? Could you please provide a link?
Well, here's all of my system's HWIDS:
===========
PCI devices
===========
PCI\VEN_1002&DEV_4370&SUBSYS_310015BD&REV_80\3&18D45AA6&0&A5: Realtek AC'97 Audio
PCI\VEN_1002&DEV_4371&SUBSYS_00000000&REV_80\3&18D45AA6&0&A4: ATI I/O Communications Processor PCI Bus Controller
PCI\VEN_1002&DEV_4372&SUBSYS_100915BD&REV_81\3&18D45AA6&0&A0: ATI I/O Communications Processor SMBus Controller
PCI\VEN_1002&DEV_4373&SUBSYS_43731002&REV_80\3&18D45AA6&0&9A: ATI I/O Communications Processor USB 2.0 EHCI controller
PCI\VEN_1002&DEV_4374&SUBSYS_43741002&REV_80\3&18D45AA6&0&98: ATI I/O Communications Processor USB 1.1 OHCI controller
PCI\VEN_1002&DEV_4375&SUBSYS_43751002&REV_80\3&18D45AA6&0&99: ATI I/O Communications Processor USB 1.1 OHCI controller
PCI\VEN_1002&DEV_4376&SUBSYS_100715BD&REV_80\3&18D45AA6&0&A1: Standard Dual Channel PCI IDE Controller
PCI\VEN_1002&DEV_4377&SUBSYS_43771002&REV_80\3&18D45AA6&0&A3: ATI I/O Communications Processor LPC Controller
PCI\VEN_1002&DEV_4379&SUBSYS_43791002&REV_80\3&18D45AA6&0&90: ATI 4379 Serial ATA Controller
PCI\VEN_1002&DEV_437A&SUBSYS_437A1002&REV_80\3&18D45AA6&0&88: ATI 437A Serial ATA Controller
PCI\VEN_1002&DEV_5950&SUBSYS_59501002&REV_10\3&18D45AA6&0&00: PCI standard host CPU bridge
PCI\VEN_1002&DEV_5974&SUBSYS_100215BD&REV_00\4&152EA2CB&0&2808: RADEON XPRESS 200 Series (Microsoft Corporation - WDDM)
PCI\VEN_1002&DEV_5A3F&SUBSYS_5A3F1002&REV_00\3&18D45AA6&0&08: PCI standard PCI-to-PCI bridge
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&18D45AA6&0&C0: AMD HyperTransport(tm) Configuration
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&18D45AA6&0&C1: AMD Address Map Configuration
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&18D45AA6&0&C2: AMD DRAM and HyperTransport(tm) Trace Mode Configuration
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&18D45AA6&0&C3: AMD Miscellaneous Configuration
PCI\VEN_10EC&DEV_8169&SUBSYS_100A15BD&REV_10\4&28C87A37&0&50A4: Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.0)
PCI\VEN_1106&DEV_3044&SUBSYS_100615BD&REV_80\4&28C87A37&0&48A4: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_14E4&DEV_4318&SUBSYS_03551154&REV_02\4&28C87A37&0&28A4: Broadcom 802.11g Network Adapter
20 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&171A4252&0 : USB Root Hub
USB\ROOT_HUB\4&249291E9&0 : USB Root Hub
USB\ROOT_HUB20\4&3B1D26D3&0 : USB Root Hub
USB\VID_03F0&PID_6204\MY3C84J2V77A : USB Printing Support
USBPRINT\HPDESKJET_5100\6&2D3E044D&0&USB001 : HP Deskjet 5150 series
5 matching device(s) found.
oops, I had 64 bit here
32bit link
http://www.siliconimage.com/support/sup … sid=4&
Last edited by Jaak (2007-12-23 21:09:00)
hehe, Silicon updated the site.. the x.83 /x.84 reference mixup no longer exists.
All pages say x.84 now (driver page ands BIOS DL page it linked to mentioned a different version once.)
Now, if this latest Silicon driver works for usficcient, then we still have to find out what we must do for the fairly long list of silicon/ATI hwids it misses.
(updates often drop support for older HWIDs. The Silicon originals never had many for ATI. There are quite a few HWIDS missing if I only use this one...)
1: Instand bsod AFTER 1st reboot.
2: Raid-0 config (2x 120GB)
3: Bios version 4.2.47 (integrated on my ASUS A7N8X-XE Deluxe mainboard)
You can find my setupapi.log here
This came from the last test i did last night with Nlite, worked good and used driver version 10.0.6.0
Hwid from that machine:
===========
PCI devices
===========
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&3B1D9AB8&0&5840: Silicon Image SiI 3112 SATARaid Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: SM Bus Controller
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: Ethernet Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Multimedia Audio Controller
PCI\VEN_10DE&DEV_006B&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&28: Multimedia Audio Controller
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01EB&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0253&SUBSYS_80431043&REV_A3\4&102AC5BC&0&00F0: NVIDIA GeForce4 Ti 4200 (Microsoft Corporation)
PCI\VEN_11AB&DEV_4320&SUBSYS_811A1043&REV_13\4&3B1D9AB8&0&2040: Ethernet Controller
20 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&36CE346&0 : USB Root Hub
USB\ROOT_HUB\4&37090E00&0 : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0 : USB Root Hub
USB\VID_0457&PID_0151\000000000003C6 : USB Mass Storage Device
USB\VID_046D&PID_C00C\5&DF9F058&0&2 : Logitech USB WheelMouse
USBSTOR\DISK&VEN_UT161&PROD_USB2FLASHSTORAGE&REV_0.00\000000000003C6&0: Ut161 USB2FlashStorage USB Device
6 matching device(s) found.
I think Jaak is right that perhaps the Base drivers mess things up.
Pointed Nlite at the "3112r" drivers with that test, nothing else!
Is it possible to make a "R"only testpack?
For me it is a piece of cake to test, so you'll now it fast if it works.
well, at least BAM does not have a problem device
these are HARD drive firmware IDs the driver has problems on.
ObsProblemDev1Name="ST330013AS 108b"
ObsProblemDev2Name="ST330013AS 1.20"
ProblemDev1Name="Maxtor 4D060H3 DAK05GK0"
ProblemDev1Value="MaxMode = UDMA-5"
ProblemDev2Name="ST320012AS"
ProblemDev2Value="Mod15Write"
ProblemDev3Name="ST330013AS"
ProblemDev3Value="Mod15Write"
ProblemDev4Name="ST340017AS"
ProblemDev4Value="Mod15Write"
ProblemDev5Name="ST360015AS"
ProblemDev5Value="Mod15Write"
ProblemDev6Name="ST380023AS"
ProblemDev6Value="Mod15Write"
ProblemDev7Name="ST3120023AS"
ProblemDev7Value="Mod15Write"
ProblemDev8Name="ST340014ASL"
ProblemDev8Value="Mod15Write"
ProblemDev9Name="ST360014ASL"
ProblemDev9Value="Mod15Write"
ProblemDev10Name="ST380011ASL"
ProblemDev10Value="Mod15Write"
ProblemDev11Name="ST3120022ASL"
ProblemDev11Value="Mod15Write"
ProblemDev12Name="ST3160021ASL"
ProblemDev12Value="Mod15Write"
-------------------
mass testpack 7125 is ready
http://dev.driverpacks.thesneaky.com/dr … nightly.7z
I took radical measures.
The radical changes forced me to merge HWIDS into the latest drivers, because they drop support for some hardware when they update a driver.. (which was another reason why I assumed that newest drivers for latest BIOSes would not function on older BIOSes)
If this works, we have a slimmed down pack, with ONE 3112 base driver, and ONE 3112 raid driver.
I had NO time to run basic tests.
I am late on a date as is.
Food, champagne, Rock and Roll.. I am looking forward to it.
You guys rock. Thanks for helping us help you.
Hi Bam, it is possible to edit the PACK
a truly basic edit is simple
un7zip, open INI, delete relevant section in INI, delete the corresponding folder too.
7zip the INI and D, and give it a higher number
test
adding new driver to this pack is not that simple.
You may have read the learning pains txt...
Jaak: You'll better go now, date, Rock'n Roll, drink but do not pass out.
We need your brains!
(i have to wait for my party till the end of this day)
I'll do the test with your latest testpack.
MAYBE, i will try to edit one if it didn't work.
we shall see if i manage to make a custom one.
enjoy yourself.
The latest nightly didn't do the trick...
BUT, i made a custom one, removed all S sections and folders EXEPT S5.
That worked wonderfull, a full install was my part..
Now it's up to you to figure it out.
hi
elimination works best by halves.
It's like this.
when you start and you have a hundred besides the one you know you need, try by deleting 50 of the 101
the testpack then has 51
If it works, reopen original, then delete 25 from the OTHER 50, and pack has 76
But, if it didn't, delete another 25, and run with 26.
Ruudboek once did this, and discovered we had a baddy in A\3 (it's no longer in the packs now)
I would have left S4 and S5 in at one point.
(you could, of course, also have tried by only removing S4, because that is the prime suspect..)
by the way, AD\9 was another suspect, and since you left that in, it no longer is.
Last edited by Jaak (2007-12-24 10:23:38)
I must say, i'm starting to like doing these things! (again)
For today, i leave it now with my own "custom nightly testpack" and will use all the other driverpacks with that one.
First i want to see if it works as it should with all the others.
Tomorrow, and probably the days after, i will do the elimination trick for you.
But i have one question left: How do i exactly identify the so called base drivers to skip those out first??
O' yeah, i have a confession to make.. i mentioned a raid-0 config.. that machine turned out to be a single drive only.. (but SATA)
My main machine, this one, has exactly same spec's, but the Raid-0 config..
sorry!
Hear you later.
good team work guys!!!
7126 is ready
http://dev. link pulled
minor change
the three HWIDs I tagged with CC_101 are deleted from S4 (and the INI)
The CC_0104 tags in S5 were removed.
The reasoning here is this.
1; We cannot allow dupes in the INI. (The tag should work in the INI, but for PnP probably don't .)
2, you seem to all use S5, on a single drive
(I also think the default in the mobo BIOSes sets the chip to RAID capable. Most users don't change settings in BIOS. and this works...)
so, the three HWIDs that were duplicated in the INF files no longer have that dupe in S4.
(that stops PnP from picking it up.)
Last edited by Jaak (2007-12-29 07:24:04)
the SiLicon Raid capable drivers all have an R in the filename, and the INF files have information at the top.
Raid 5 drivers have R5 in the name. (example of an original is in SC.. In SC1 we renamed files yet SC1 still shows R5 in the filenames.)
The INI sections mention this too, and the overview of supported devices on the site is another list one can look at.
Before i read your post about the S4/S5 changes i made the following testpacks:
1: without AD9 & S4 > went okay
2: without S4 > went okay
So it's definitly a problem with the S4 portion in DP MassStorage pack!
I just DL your new 7126 nightly package and will put it to the test with ALL driverpacks slipstreamed in it.
Will report back to you in about 20min or so.
It's looking good, i think we have the answer today!
There is some other small thing i don't get, but i will have to test it if my eye's don't play tricks on me.
I'm sorry Jaak.
With your adjustments i still get the BSOD..
But when i remove the S4 entry and dir it works flawless!
In there is your problem device..
I go for some fishing now, done enough for this morning
So you have something on your hands now
7127
it uses older driver in S4
http://dev.
link pulled.. newer file 7128 is up
it has a win2000 memory limit fix as well
Last edited by Jaak (2007-12-29 07:23:17)
you'va also been testing streaming of this
CHANGED for 7127
sILICON 3112
s4b AND s4c were removed. (an older in S4)
S5A and S5B and S5C were removed, (covered by latest in S5)
S4, removed three HWIDs in S4 INI.
S5, covers HWIDs from S5A and S5B and S5C (and the three removed in S4)
SiS
SiS 180/181/182/1182 "unified" driver v2110 is not good for all HWIDs.
re-introduced v1070 and disabled duplicated HWIDs in V2110
FIXES
INI fix
Disabled a few more drinvers in INI for windows 2000.
Windows 2000 memory limit for TXTmode requires we disable many, and we had again broken through limit.
INI fixes in [AD2], [AD6],[Ib4],[Ib5] (the new additions required this)
INI fix
[L] LsI SAS, tagname fix
INI fix
[P7] removed a duplicate HWID
Filename fixes; renamed system file in
[S8A],[SA],[SA2],[SB2],[SB3],[SB4],[SB5],[SC2],[SC3] and [SC4]
NEW
[AD1]
Adaptec AAR-1420SA / AAR-1430SA SATA HostRAID Controller
07/03/2007,1.5.11975.0
NEW
[ADa]
"Adaptec AAR-1220SA/AAR-1225SA SATA HostRAID Controller"
07/08/2007,1.5.12073.0
NEW
[ADb] "AACSAS Adaptec SAS/SATA-II RAID"
and "AAC Adaptec RAID Windows 2000/XP/2003 Device Drivers"
09/15/2007, 5.2.0.15317
> supported devices
adptAvonPark.DeviceDesc = "IBM ServeRAID 8i Controller"
adptRombAurora.DeviceDesc = "IBM ServeRAID 8k/8k-l Controller"
adptIntruder4.DeviceDesc = "Adaptec SATA RAID AAR-2420SA Controller"
adptIntruder6.DeviceDesc = "Adaptec SATA RAID AAR-2620SA Controller"
adptIntruder8.DeviceDesc = "Adaptec SATA RAID AAR-2820SA Controller"
ICPIntruder4.DeviceDesc = "ICP SATA RAID ICP9047MA Controller"
ICPIntruder6.DeviceDesc = "ICP SATA RAID ICP9067MA Controller"
ICPIntruder8.DeviceDesc = "ICP SATA RAID ICP9087MA Controller"
adptBlackBird.DeviceDesc = "Adaptec RAID 4000"
adptMarauderX.DeviceDesc = "Adaptec SAS RAID 4800SAS Controller"
adptMarauderE.DeviceDesc = "Adaptec SAS RAID 4805SAS Controller"
icpMarauderX.DeviceDesc = "ICP SAS RAID ICP9085LI Controller"
icpMarauderE.DeviceDesc = "ICP SAS RAID ICP5085BR Controller"
IBM8s.DeviceDesc = "IBM ServeRAID 8s Controller"
adptVoodoo40.DeviceDesc = "Adaptec RAID 5405"
adptVoodoo44.DeviceDesc = "Adaptec RAID 5445"
adptVoodoo80.DeviceDesc = "Adaptec RAID 5805"
adptVoodoo08.DeviceDesc = "Adaptec RAID 5085"
adptVoodoo124.DeviceDesc = "Adaptec RAID 51245"
adptVoodoo164.DeviceDesc = "Adaptec RAID 51645"
adptVoodoo244.DeviceDesc = "Adaptec RAID 52445"
icpVoodoo44.DeviceDesc = "ICP5445SL"
icpVoodoo80.DeviceDesc = "ICP5085SL"
icpVoodoo08.DeviceDesc = "ICP5805SL"
adptMarauder40LP.DeviceDesc = "Adaptec RAID 3405"
adptMarauder80LP.DeviceDesc = "Adaptec RAID 3805"
adptMarauder120.DeviceDesc = "Adaptec RAID 31205"
adptMarauder160.DeviceDesc = "Adaptec RAID 31605"
icpMarauder40LP.DeviceDesc = "ICP5045BL"
icpMarauder80LP.DeviceDesc = "ICP5085BL"
icpMarauder120.DeviceDesc = "ICP5125BR"
icpMarauder160.DeviceDesc = "ICP5165BR"
adptVoodoo120.DeviceDesc = "Adaptec RAID 51205"
adptVoodoo160.DeviceDesc = "Adaptec RAID 51605"
icpVoodoo120.DeviceDesc = "ICP5125SL"
icpVoodoo160.DeviceDesc = "ICP5165SL"
adptMarauder08LP.DeviceDesc = "Adaptec RAID 3085"
icpMarauder08LP.DeviceDesc = "ICP5805BL"
adptAOC_USAS1_S4i.DeviceDesc = "AOC-USAS-S4i RAID Controller"
adptAOC_USAS1_S8i.DeviceDesc = "AOC-USAS-S8i RAID Controller"
adptAOC_USAS1_S4iR.DeviceDesc = "AOC-USAS-S4iR RAID Controller"
adptAOC_USAS1_S8iR.DeviceDesc = "AOC-USAS-S8iR RAID Controller"
adptAOC_USAS1_S8iLP.DeviceDesc = "AOC-USAS-S8i-LP RAID Controller"
adptAOC_USAS1_S8iRLP.DeviceDesc = "AOC-USAS-S8iR-LP RAID Controller"
adptSUN_4i4e.DeviceDesc = "Sun STK RAID REM"
adptSUN_Narvi.DeviceDesc = "Sun STK RAID EM"
adptSUN_Cougar.DeviceDesc = "Sun STK RAID INT"
adptSUN_Prometheus.DeviceDesc = "Sun STK RAID EXT"
aacsas_ServiceName = "Adaptec SAS/SATA-II RAID Miniport Driver"
> supported device list
adptVulcan.DeviceDesc = "Adaptec SCSI RAID 2200S Controller"
adptCrusader.DeviceDesc = "Adaptec SCSI RAID 2120S Controller"
adptSkyhawkscsi.DeviceDesc = "Adaptec SCSI RAID 2020ZCR Controller"
adptSkyhawksata.DeviceDesc = "Adaptec SATA RAID 2020SA Controller"
adptTerminatorscsi.DeviceDesc = "Adaptec SCSI RAID 2025ZCR Controller"
adptTerminatorsata.DeviceDesc = "Adaptec SATA RAID 2025SA Controller"
adptJaguar.DeviceDesc = "Adaptec SATA RAID 2410SA Controller"
adptCorsair8.DeviceDesc = "Adaptec SATA RAID 2810SA Controller"
adptCorsair16.DeviceDesc = "Adaptec SATA RAID 21610SA Controller"
adptBearcat.DeviceDesc = "Adaptec SATA RAID 2610SA Controller"
adptLancer2ch.DeviceDesc = "Adaptec SCSI RAID 2230S Controller"
adptLancer1ch.DeviceDesc = "Adaptec SCSI RAID 2130S Controller"
ICPLancer2ch.DeviceDesc = "ICP SCSI RAID ICP9024RO Controller"
ICPLancer1ch.DeviceDesc = "ICP SCSI RAID ICP9014RO Controller"
aac_ServiceName = "Adaptec RAID Miniport Driver"
UPDATE
intel iastor
from 07/12/2007,7.6.0.1011 to 09/29/2007,7.8.0.1012
Last edited by Jaak (2007-12-25 04:31:33)
7127 = still no joy, sorry Jaak
Again i opened that one up, removed entry + dir S4, and voila!
It runs smooth as a ... as a good MassStoragepack!
I have been looking around here, i promised Bashrat a long time ago to save a working disk i/he/us all made, but still can't find it.
On that disk was the latest pack before the 3112r H*LL started for the first time.
I suppose there are other (older) drivers on it which maybe can help out. For the S4 portion i mean. Hopefully i can find it back somewhere in messed up "office". If so, i can compare those for you.
For the mean time, what can i do to give it happy ending??
* I wonder, why does the slipstream with ONLY massStorage takes more time then almost all packs together?? (-1min or so) *
Hi BAM,
Jeff and I discussed a 'halves" idea I had.
I started to think like this..
Toss half o/t HWIDs from S4.
Test
No go?
Toss more, until we keep just one HWID.
Test
That would prove it is not a HWID, but the sys itself messing this up.
----
I then rethinked. (I know grammar like that sounds ILL Lit.. but it is Engliiz.)
I had also opted to have an older S4 in, or drop it alltogether.
---
Based on your report, older S4 together with S5 doesn't work.
---
So, right now, it looks like newest Raid and any version of base mode won't work together.
---
The pack was up for almost two weeks before you and stiertje started the reports.
All in all, the idea to drop S4 has merit.
The release we have has flaws, and we rather have an unsupported than bsod.
I also do not want to maintain SFXminipacks
In my mindset, S4 has no reason to mess us up, and it does, so it better go.
Mary had a child.
It showed us that the world is with people in need of help.
We share our need, and we help you fix us up.
This time, we cannot do a clambake, tho.
I usually had pleasant thoughts when I thought of Silly Cones. (thinks of Al Bundy's Hoot Hoot hhhoot'ers)
I tried, you did, but I think we better drop it, so we can stand proud.
Thanks for helping us.
Last edited by Jaak (2007-12-25 13:16:24)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.024 seconds, 12 queries executed ]