hi, you can try this one

70417 test version was pulled
test versions after 70410 and before 70418 caused commenting out of drivers

------------------
70418


J-1 and J-2 changed folder-order (2007/04/09)
updated [J-1] JMicron JMB36X RAID Processor (2007/04/09)
DriverVer=01/29/2007, 1.17.11.02   replaces 12/05/2006, 1.17.08.01
added HWIDs for Gigabyte motherboards
------------------

cleanup ULI-ALI (2007/04/09)
update section [AU-3] (replaces au-3 au-4 and au-5)
[AU-4] deleted
[AU-5] deleted

----------------------------------------
silicon image (2007/04/09)
Load order; in INI alfa-numerical, folder-names correspond with load order.

Update (2007/04/11)
[S-7]
Silicon Image Serial ATA Raid 5 driver for the 3132 controller
Driver update 01/25/2007, 1.5.14.1 replaces 09/05/2006, 1.5.10.0

------------------------------------

NEW (2007/04/10)
Promise TX2200 DriverVer=11/08/2005, 2.06.0.311
[P-9]
-----------
NEW (2007/04/10) >> (2007/04/18) FIXED ERROR

Compaq SERVER HP ProLiant 32-Bit SCSI Controllers DriverVer=11/12/2002 ,  5.24.00.0
[c]


-----------
FIX (2007/04/13)
FIX in INI section [AD-A] to avoid conflict with IastorOld [IN-1-O]

---------------------------------------
UPDATE

[L-4]

06/13/2005 1.20.18.00 replaces 04/12/2004 1.10.0

=============

details of the changes to structure


ALi/ULi M5287 SATA/RAID Controller (M1573)
10/18/2005, 1.0.1.0
AU\3

ALi/ULi M5288 SATA/RAID Controller (M1575/M1697)
11/21/2005, 1.0.5.2
AU\3

ALi/ULi M5289 SATA/RAID Controller (M1689/M1567)
10/18/2005, 1.0.1.0
AU\3


Compaq SERVER HP ProLiant ProLignia 32 Bit SCSI Controllers
11/12/2002 ,  5.24.00.0
C

JMicron JMB36X RAID Controller
01/29/2007, 1.17.11.02
J\1

JMicron 20360/20363 AHCI Controller
08/15/2005, 5.2.0.207
J\2

LSI
2Gb FC, models 44929,
G2 with 929/with 919 & models 7202,7402 with 929X & models 7102 with 919X
Ultra320 SCSI 2000 series, w/1020/1030
Ultra320 SCSI RAID series, w/1035
SAS 3000 series, 4-port with 1064
SAS 3000 series, 8-port with 1068 /1068E
SAS 3000 series, 6-port with 1066
4Gb FC, models 7204,7404 with 949X & models 7104 with 939X
Dell
SAS 5/E, SAS 5/i, SAS 5/i Integrated, SAS 5/iR Integrated D/C, SAS 5/iR Integrated Emb, SAS 5/iR Adapter
06/13/2005 1.20.18.00
L\4


Promise TX2200
11/08/2005, 2.06.0.311
P\9

Silicon Image CMD PCI-0649 Ultra100 IDE Raid Controller
06/09/2001
S\1

Silicon Image SiI 0680 Ultra-133 Medley ATA Raid Controller
05/31/2002, 1.0.1.7
S\2

Silicon Image SiI 3112 SATARaid Controller
Silicon Image SiI 3512 SATARaid Controller
&
ATI 436E Serial ATA RAID Controller
ATI 4379 Serial ATA RAID Controller
ATI 437A Serial ATA RAID Controller
03/14/2006, 1.0.56.1
& 08/27/2004, 1.7.0.51
S\3, S\3\A

Silicon Image SiI 3114 SATARaid Controller
Silicon Image SiI 3114 SoftRaid 5 Controller
04/10/2005, 1.0.15.0
& 09/05/2006, 1.5.10.0
S\4, S\4\A

Silicon Image SiI 3124 SATARaid Controller
02/02/2004, 1.0.0.2
S\5

Silicon Image SiI 3124 SoftRaid 5 Controller
09/20/2006, 1.5.11.0
S\6

Silicon Image SiI 3132 SoftRaid 5 Controller
01/25/2007, 1.5.14.1
S\7

Silicon Image SiI 0680 ATA/133 Controller
11/15/2006, 1.2.26.0
S\8

Silicon Image SiI 3112 SATALink Controller
Silicon Image SiI 3512 SATALink Controller
ATI 436E Serial ATA Controller
ATI 4379 Serial ATA Controller
ATI 437A Serial ATA Controller
10/23/2006, 1.3.67.0
S\9

Silicon Image SiI 3114 SATALink Controller
06/21/2006, 1.3.10.0
S\A

Silicon Image SiI 3124 SATALink Controller
08/22/2006, 1.3.20.0
S\B

Silicon Image SiI 3132 SATALink Controller
10/31/2006, 1.0.19.0
S\C

2,027

(3 replies, posted in DriverPack Graphics)

they are updates and new ones, and being worked on.
do you have hardware that requires these drivers, perhaps?

your solution number three would be best, don't you think so?

I will implement it.

roger that..
and done the fix

Jeff, it could be disheartening, but yes, the silence was deafening.

I am in favour for a subforum, tho.
this function is a real godsend and a LOT of work was put into it.

OOPS, should have posted this here

isn't it strange that aarich.sys is branded adaptec, but that the INF is using HWIDs for INTEL?

if we had any idea which chip and (probably more important) Boot-ROM this adaptec used, we might get rid of this driver and put the HWIDs in a driver that uses same chip/ROM.

as it is, I looked at the sys files (like others before me), and did not remove it.
Iastor OLD [IN-1-O] lists  PCI\VEN_8086&DEV_24DF with &CC_0104 behind that

adaptec's aarich [ad-a] just uses PCI\VEN_8086&DEV_24DF

I would like to make that [ad-a] load AFTER intel's

one can do that by unpacking the mass storage folder into new (empty) folder, open its INI, cut [AD-A] section, and paste it at bottom.
that would make it still support adaptec embedded, but intel would get loaded first when a full match was made for intel.

another option, one can disable aarich by putting a zero in drivercount = 1  in [AD-A]

after editing, 7zip the INI and the D folder (with a name like DP_MassStorage_wnt5_x86-32_70432)
hehe, that 32 is a joke, but you do want to differentiate it from the downloaded one... wink

then use it, and if that works, let us know

isn't it strange that aarich.sys is branded adaptec, but that the INF is using HWIDs for INTEL?

if we had any idea which chip and (probably more important) Boot-ROM this adaptec used, we might get rid of this driver and put the HWIDs in a driver that uses same chip/ROM.

as it is, I looked at the sys files (like others before me), and did not remove it.
Iastor OLD [IN-1-O] lists  PCI\VEN_8086&DEV_24DF with &CC_0104 behind that

adaptec's aarich [ad-a] just uses PCI\VEN_8086&DEV_24DF

I would like to make that [ad-a] load AFTER intel's

one can do that by unpacking the mass storage folder into new (empty) folder, open its INI, cut [AD-A] section, and paste it at bottom.
that would make it still support adaptec embedded, but intel would get loaded first when a full match was made for intel.

another option, one can disable aarich by putting a zero in drivercount = 1  in [AD-A]

after editing, 7zip the INI and the D folder (with a name like DP_MassStorage_wnt5_x86-32_70432)
hehe, that 32 is a joke, but you do want to differentiate it from the downloaded one... wink

then use it, and if that works, let us know

hi shaz
this update made it into Mass storage 704 and later
can you change this topic title to [implemented] please?

hi debugger, read this, and updated the pack.
at the moment, it is up for testing in testing-forum.

if you will, change topic title to [implemented]

pulled the one posted yesterday, it had an error

if you want to test this version (which has these proliant drivers)

XP is NOT going to use these. I disabled this for XP given that all machines listed were server.

http://rapidshare.com/files/25278696/DP … 2_70410.7z

pulled the one posted yesterday, it had an error

if you want to test newer version, here goes

http://rapidshare.com/files/25278696/DP … 2_70410.7z

it got included in a test version

added to testing version 7049

this file was pulled

hi
included in 704

Helmi?
please close it
the file is no longer up RS, and no response (and it is in 704 anyway)

Saw you can reply to a topic and assumed you can start one too.. will start one

Hi Bigbrit

apparently, Jmicron drivers are a PITA.
do you care to go to testing forum, we can do your test version together.

does Firefox have privacy settings in its options?
you could look at that, to allow refferal cookies for driverpacks.net

what's bugging me is that they are just INF files (and their cat)
no sys files are copied at all.

your jmicron chip, is that installed correctly?

I just corrected that post, I looked a bit harder..

DP has the newer, 8.00.1008 is newer than 7.00.1020 (asus)

yesterday I downloaded the intel INF installer listed at Asus, for the type of mobo you listed.

in DP 8.00.1008, at asus 7.00.1020
>edit> the HWIDs? same... Strange, huh?

I'l have to look wether I have a copy of DP chips 605.

Helmi has a point here, I have noticed different hotfix versions for the different platforms.

One of these days I ought to run these in testrigs with vanilla versions of different platforms, and look at the files they create.. (ugh, it sounds like just more work... the testrigs are abused as they are.)

masterwolfe, can you please give us a link to driver that works?
I want to look at the supported HWIDs in that one.

Muiz has a point here..

I did look at that file, and expanded it, but cannot for the life of me remember wether I took action.
had I done so, it would have been commented in the changelog (When I first started doing changes, that could result in a log not neccesarily with my name next to it. Later on I got aware the team NEEDS awareness of every interim version change.)

anyway, muiz has a point.
sooner or later, it gets asked as a properly put request, without team or mod having to go to extra length to figure out wether other team member is looking at it.
(actually, I thought muiz was handling it)