thanks.

I think we can conclude that iastor Version 7.5.0.1017 is a non-viable update.
Like Rolf Harris says "Back to the drawing board". sad

tonight I can

Hi
welcome to DriverPacks
The request has already been posted before, and some people have found testversions which has this.

here is a link
http://forum.driverpacks.net/viewtopic.php?pid=11237

Veel leesgenot

hi

this topic has links to test versions
http://forum.driverpacks.net/viewtopic.php?pid=11237

Hi Alex,
this testpack has an updated driver in folder S\5\A 5 (silicon Image 3112r).

There is also an attempt to fix Jmicron 36X issues in this testpack.
The test here is that Gigabyte's HWIDs were put in the newer Jmicron driver's INF, rather than keep this older version used by Gigabyte. (located at J\1 in previous test versions. )
If all is well, both RAID and AHCI modi are supported by a single driverset.

These testpacks also had newest official Intel driver.

(link to mass storage testpack removed here)

Well, if this works for you, let us know. We hope it does, because that is better than using customised packs.
if it fails, then there is a driver which causes a clash and crash, and we hope to find it.

To help you out, you can find a tiny pack in your mailbox, with those updated drivers for your model motherboard.
If that one works, then it is like you said.. Then we KNOW FOR SURE there is some undetected partybuster.
Good luck, and please let us know the results.

1,856

(2 replies, posted in Software)

hi

Media Center Edition is XP pro with addons, so XP drivers work in that.
It is as simple as that.

Hi

Jmicron 1.17.17.00  is actually put in the mass storage 7.05 release (located at \J\2) and now that you posted this, I am beginning to wonder about this driver.
It was the first such that supports both AHCI and RAID from within one INF.
(the JMIDE in there is for people who selected IDE mode, and intended for plug and play, not txtmode)

in 7.05, the old driver for AHCI is still there.  (at \J\1)

There is a test version in feedback, wich has J-1 replaced with a Gigabyte Jmicron release, which also supports AHCI, and in that test pack, J-1 only does Gigabyte's version, and J-2 will do all but gigabyte's.

you could find it, and test it, and reply in the topic you got the testpack in.

1,858

(9 replies, posted in News)

Hi
I got a mail with the corrected INI, but a corrected mobility.inf was not attached, so I looked for those "funny" characters..
I am repacking and will re-release as 7.05.1

all the more true if you do not use a higher version number after you fixed something by your sweet self.
Then it uses a NON updated QSC.

This is gonna be solved soon.
Jeff got to the code, and fixed some.

MORE fixing is expected.

Hi Burle, how about becoming testing team member?
you'd have the ability to test and help fix, and so on.

we had test versions linked to here, and the mass storage updates do not work.
I am pulling them

all these mass storage test versions, and the updates do not work.
I am pulling them
sad

we had test versions linked to here, and the mass storage updates do not work.
I am pulling them

line 13151 error, caused by a difficult to spot " character that wasn't a "correct" " sad

it looked correct, but was not.

mass 7059test3 is running a live test here.

1,865

(9 replies, posted in News)

Dear Gentlebeings,

LAN Pack updated to 7.05.1
Graphics A updated to 7.05.1
ATI Catalyst changed its ways, and we had a problem.
Mr Smartepants worked on the ATI CCC problem and found a solution, got help from Muiz, and that's how this got done.
Fresh minds with fresh ideas are always welcomed.
Thanks for the hard work!

Update!
Graphics A 7.04 was put back as 7.05.2 on 29th.
Final fixes had somehow not been included in the 7.05.1 Copy on server, and this Older one was put back.

hi
many drivers have a (note, "a") reference to a CAT file which is not there but no reference to it in "sourcediskfiles".

gor instance, in mass storage, AU-1
a reference to catalog and then this
[SourceDisksFiles]
aliide.sys =1;
(here there is no reference)

When it is listed as a sourcefile to be copied, a log will show you if that this file was missing.
(I've seen logs like these, and it is not a critical error.)

Hi
muiz updated the broadcom driver after 705 release, but that (soon to be released) pack does not have

&REV_02\4&21E4E6E0&0&00E4

this is the one he has updated
http://www.broadcom.com/support/etherne … esktop.php

1,868

(16 replies, posted in DriverPack WLAN)

Good catch there, Erik.

Is that called a catch 22?

7058 and 7059, yes, indeed, found comma at start.
and iastor2 had to be iastor3.

a hit in [IN-3] for ICH6 had no description. I looked at that, and think I got that section right now.

uploading 7058test2 and 7059test2
since these test two different principles described above, I keep the names close to what they were.

test 705.9
putting the "unsupported' HWIDs of iastor 6.2.1.x into iastor 7.5.0.x and then get rid of 6.2.1.x 5 (and make the adjustments in the pack's INI file accordingly)
The renamed files are still renamed..
6.2.1.x is disabled during txtmode

hi

I am thinking about this, and would like to do an experiment, by putting the "unsupported' HWIDs of iastor 6.2.1.x into iastor 7.5.0.x and then get rid of 6.2.1.x 5 (and make the adjustments in the pack's INI file accordingly)

yesterday, I made a testpack 705.8 with another approach.
I did INF edits, and renamed the files so that references in the INF could not point to a (wrong) identically named file. Then I made changes to the pack's INI because the filenames changed.

hi

if all driverpacks are in the driverpacks folder (where they have to be), and then you still see this, it it because you selected the BartPE plugin option. smile

mass storage 7054 had error
link pulled

2007/05/30 NEW chipset test version
http://users.pandora.be/jtdoom/DP_Chips … 59test1.7z

oops, your source was already slipstreamed..

Hi
you can slipstream the service pack before you run Base
Base cannot do that.

http://www.microsoft.com/downloads/deta … laylang=en