Blue Screen With Adaptec 1205SA - DriverPack Thinks it's a SiL 3112 (Page 1 of 2)

Hi Jimbo,

I wish we could make the driverpacks DETECT the BIOS, but unfortunately, we can't.

The mass storage section for Silicon Image driver which causes the BSOD says this

[S-4]
; driver 04/13/2007, 1.3.68.2 for BIOS 4.x.84.
; replace S-4 section if you replace driver with SFXzip.
; keep SFXzip files
ms_count=1
ms_1_deviceName="Silicon Image 3112 SATALink Controller"
ms_1_tag="si3112"
ms_1_sysFile="Si3112.sys"

ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_31121095,PCI\VEN_1095&DEV_3112&SUBSYS_34238086,PCI\VEN_1095&DEV_3112&SUBSYS_34238086&REV_02,PCI\VEN_1095&DEV_3112&SUBSYS_311215D9,PCI\VEN_1095&DEV_3112&SUBSYS_B0021458,PCI\VEN_1095&DEV_3112&SUBSYS_01661028,PCI\VEN_1095&DEV_3112&SUBSYS_81E8104D,PCI\VEN_1095&DEV_3512&SUBSYS_35121095,PCI\VEN_1095&DEV_3512&SUBSYS_01661028,PCI\VEN_1095&DEV_3512&SUBSYS_35121014,PCI\VEN_1095&DEV_3512&SUBSYS_02B71014,PCI\VEN_1095&DEV_3512&SUBSYS_B0021458,PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D,PCI\VEN_1095&DEV_3512&SUBSYS_820B104D,PCI\VEN_1095&DEV_3512&SUBSYS_145A1462,PCI\VEN_1095&DEV_3512&SUBSYS_001F6409,PCI\VEN_1095&DEV_3512&SUBSYS_9003104D,PCI\VEN_1095&DEV_3512&SUBSYS_35121A5F,PCI\VEN_1095&DEV_3512&SUBSYS_000E182D,PCI\VEN_1095&DEV_3512&SUBSYS_901B104D,PCI\VEN_1095&DEV_3512&SUBSYS_3512131F"

ms_1_isBusExtender=false

------------------------
The adaptec driver in section [AD-9] lists only the last two of five HWIDS.
(the first three were removed from the ash1205.INF)
%PCI\VEN_1095&DEV_3112.DeviceDesc%=SI_3112, PCI\VEN_1095&DEV_3112&SUBSYS_31121095
%PCI\VEN_1095&DEV_3112.DeviceDesc%=SI_3112, PCI\VEN_1095&DEV_3112&SUBSYS_34238086
%PCI\VEN_1095&DEV_3512.DeviceDesc%=SI_3512, PCI\VEN_1095&DEV_3512&SUBSYS_35121095
They were removed because they are also inside [S-4] (for both old And New BIOS) and the Silicon Image driver would win over the older ash1205.

These two were kept in ash1205.INF and AD-9 section.
%PCI\VEN_1095&DEV_3512.DeviceDesc%=SI_3512, PCI\VEN_1095&DEV_3512&SUBSYS_34238086
%PCI\VEN_1095&DEV_3112&SUBSYS_02509005.DeviceDesc%=SI_3112, PCI\VEN_1095&DEV_3112&SUBSYS_02509005

Since the device YOU have is one of the three inside the Silicon with the "bad" BIOS, you have to replace the S-4 driver with the SFX_MiniPack.

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

the file you need is
http://driverpacks.mirror.thesneaky.com … S_4x79.exe

You will need 7zip.
--------------------

comment.

I cannot say whether the older driver for older BIOS works on matching HWIDS detected in machines with newer BIOS.
The OLD and NEW driver for S-4 have massive overlap
(the NEW had maybe only 4 Unique, all the other were duplicate HWIDs, which means I could NOT put BOTH in).
If ANYONE knows for sure that the OLD driver for silicon works on NEW BIOS, then I can do something.

Last edited by Jaak (2007-09-05 07:18:32)

the S-4 part was NOT missing.

they are not in alphanumerical order.

I re-did everything and I still keep getting that same error.

You might be right!
What's the procedure for that after I have unpacked and edited them?
Do I just select BOTH files and then tell 7z to "add them to archive"?

I finally got this thing to work by re-flashing to the newest BIOS provided by SiL for the 3112 by using a bootable DOS floppy (simply made in XP) and then I added the SiL 3112 flash utility and .bin file to the floppy, booting into DOS from the floppy and the running the flash utility.
I couldn't get it to flash by using the other two methods from within Windows XP.
I then grabbed an old driverpack CD I made back on May 15th and got the thing to finally install windows and then updated the driver and restarted.
Finally it worked and now I have an Adaptec 1205SA card that I can eventually use in Vista if I ever decide to go that way.

Last edited by Jimbo (2007-09-07 13:08:49)

I'm surprised I got anywhere with it either and I only tried it out of desperation and the sheer coincidence that I put that CD up with my old windows 2000 disks.
I found that CD and said what the h*ll and it actually installed!
That was only AFTER the BIOS re-flash.

The CD is dated May 15th, 2007. That would be the day I made it and it would have been whatever the most recent Mass Storage driver build existed on that date.
I'll pop the CD in my machine and see if I can get a clue as to what the exact driver build was.
Hang on...

thank you very much.

hi

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

Right after text mode, I get a mesage:

The file percsas.sys cannot be found
Press any key to continue

when I hit any key, I get told that setup has failed

weird, txtsetup.sif is OK here, and percsas.sy_ is cabbed into i386.

Did you have QSC ON?
There are some bugs when it is OFF. (in Method 2 too.)

hi
ran tests in virtual PC2007 until it loaded and goes past T39

txtmode error (percsas error) fixed by INI edit.

Last edited by Jaak (2007-09-23 09:15:28)

HOLY CRAP Jaak!
I just noticed the part about Quick Stream Cache
That likely explains A LOT of the problems that I started having with the Bâshrat the Sneaky driverpacks for the last several months.

I'm going to start over from scratch and enable Quick Stream Cache and see if some of my problems don't mysteriously go away.

three folders were removed, others got added, so yes, this is normal.

Last edited by Jaak (2007-09-24 05:38:22)