I ran 8 trials with this updated driver, and nothing I do fixes the case sensitivity issue we have here.

I'll postpone that update, and put a working file in the air.
the silicon solution should be released.

HpCISSs2.sys or hpcisss2.sys...

that's the strangest thing with some of those.
The filenames should not be case sensitive, and sometimes they behave that way.

BIG question,
Did you turn QSC ON?

Hi Jeff
that's standard practice with MSFT betas

thanks, I will fix it.

please redownload ( kept the name for this link)
when I looked at the HWIDs, I missed the fact that the filenames had changed.
SORRY.

hi

please try the following

get 7zip, and install it

rightclick and unpack sound A to folder
delete Alcxau.inf from D\S\R1
Then select both the INI and D folder, and rightclick
7zip the pack, and use a higher version name
(for instance, change 712 to 7121)
set to Max compression, and compact.

Then use this in combination with sound B.
If this works, tell us about it, and if it doesnt you should get the driver that works, and show us a link to it.

newsposter wrote:

If the current Intel SATA/Storage Manager drivers are in the nightlies, I can test that too over the weekend.  I have a new mobo to get into service.

yes. they are
iastor 7.8.xx
please test

982

(26 replies, posted in DriverPack Mass Storage)

a testpack is ready
the megaIDE is enabled in this one

-----------------------
in less than 40 minutes you will know...

btw, I once told Ruud a release candidate is a convict... He wants out. LOL.
http://dev link pulled for release

Changes (compared to 712 release)

sILICON 3112
s4b AND s4c were removed. (covered by latest in S4)
S5A and S5B and S5C were removed, (covered by latest in S5)

S4, removed three HWIDs in S4 INI. (and it loads after S5)

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 drivers 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

UPDATE
intel iastor
from 07/12/2007,7.6.0.1011 to 09/29/2007,7.8.0.1012


Updated Jmicron to 11/26/2007, 1.17.31.00

in less than 40 minutes you will know...
Because, here it is. the Release candidate.

btw, I once told Ruud a release candidate is a convict... He wants out. LOL.
http://dev.driverpacks.thesneaky.com/dr … 32_7128.7z

Changes (compared to 712 release)

sILICON 3112
s4b AND s4c were removed. (covered by latest in S4)
S5A and S5B and S5C were removed, (covered by latest in S5)

S4, removed three HWIDs in S4 INI. (and it loads after S5)

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 drivers 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

UPDATE
intel iastor
from 07/12/2007,7.6.0.1011 to 09/29/2007,7.8.0.1012

Updated driver in [C2] to 06/21/2007,6.8.0.32

Updated Jmicron to 11/26/2007, 1.17.31.00

Well,
it was not all in vain..
We did learn that the 3112 driver for new bios works on OLD bios.

And you, you learned some very useful things.

Jeesh
Thanks

I had just built a 7128 with the shuffled INI, (also a shuffle for VIA (where [V] was put below [V4] ) and with an updated Jmicron and an updated proliant server driver.

I can just as well reupload a pack with a shuffled Sil3112 with the latest 3112 in it

hi chiners

you are not a newbie by any means, and I would like you to try something simple.

unpack sound A
delete Alcxau.inf from D\S\R1 and repack it

it looks as if this INF sports nothing but generics, which is is causing numerous drivers to be ignored, because Realtek is newer (and not neccesarily the driver you need)

If you do this, and the pack works when you have both sound A and B loaded, please report back.

987

(26 replies, posted in DriverPack Mass Storage)

edited with extra info

988

(26 replies, posted in DriverPack Mass Storage)

@ profp62

the megaIDE you link to had no unique HWIDs.
Now, in the event that the INI edit to enable the driver does not work, you can downgrade the files by replacing the content of D\M\L with the drivers from your download.

The files have same name, so the Pack's INI will reference them.
(it wouldn't be the first time a newer driver will not work on older hardware... and we used LSI reference driver.)

OOPS,  don't try it just like that.
the LSI reference driver has MORE hwids..
Your older driver supports only three HWIDS

For old driver, the section would look like this

[L]
ms_count=1
ms_1_deviceName="LSI MegaRAID IDE Controllers"
ms_1_tag="MegaIDE"
ms_1_sysFile="MegaIDE.sys"
ms_1_hwids="PCI\VEN_1095&DEV_0649&SUBSYS_0649101E,PCI\VEN_1095&DEV_0649&SUBSYS_005D0E11,PCI\VEN_1095&DEV_0649&SUBSYS_007E0E11"
ms_1_isBusExtender=false

@ bolivas
update B1 with that

@ jhsands
put content of the agere file in B1 folder in modem, and repack it

Hi
welcome to DriverPacks

It's a little strange that you link to an agere modem file, and post information about an entirely different driver.
If your E-machine uses the agere, there is no way that other could get installed because it is too different.

991

(26 replies, posted in DriverPack Mass Storage)

Hi
I just lost the post I wrote

can you edit the INI?
Well, the file you requested is older than what we have.
We have a newer megaIDE..
However, it is disabled for win 2000
This line disables it
ms_1_exc_disableIfOS="w2k"

I want to get people savvy to some of these tricks.
Rigchtclick the pack, Un7zip to folder, open folder, then open the INI.
go to section [L]
below that section you find ms_1_exc_disableIfOS="w2k"
cut it, and paste it below Jmicron

(we are really close to windows 2000 txtmode meory limit, so it is probaly best to paste it under a driver you do not need.)
Save.

Then select the INI and D folder, Rightclick and run 7zip to pack it up.
It will show the PACK's name, and you better give it higher version number
(example; 7122, if you had 7121)

Then copy the edited pack in the folder you use for slipstreaming.
Then test the build you make with the edited pack.
(You  don't have to run full setup to see whether txtmode DETECTED the hard drive. When it detected the drive, you can bail out, or go ahead and do full setup.)

Full setup would tell you about PnP issues.
I did find a good update in the four files, and an incomplete update which adds no new HWIDs.)

The good update will be in a testpack soon.
(softpac cp007703 has five new HWIDs.

Hi

can any of you edit the INI, and switch the sections?

One can also move INI sections around, see..
The INI sections make drivers load in TXTmode in the order they are in he INI.
This INI section shuffle has worked in the past.

In old packs, you could see comment lines in INI where all silicon RAID were put below the non-raid.
I had done that to make a massive move of silicon RAID sections possible.
They was all together, and one could easily put them in the order you wanted.
Loading RAID after NON-raid was done many months ago.
And later on, when I added new sections, I made a RAID version load after Non-raid.
They was no longer all together.

Now, SFX minipacks is something I want to rid us off.
There were people who would not find a section, so they pasted a SFX minipack section in when they where supposed to REPLACE a section. (They did not use something as simple as txt search.)

I thought debugger's tagging made it possible to have them in any sort of sequence..
Of course, there is always someting like SillY 3112 to prove me wrong, eh?

Anyway..
You can move [S4]  below [S5].

I want to get people savvy to some of these tricks.
Rightclick the pack, Un7zip to folder, open folder, then open the INI, move the [S4] section below [S5], save INI.
Then select the INI and D folder, Rightclick and run 7zip to pack it up.
It will show the PACK's name, and you better give it higher version number (7128, if you had 7127).

Then copy the edited pack in the folder you use for slipstreaming.
Then test the build you make with the edited pack.

You  don't have to run full setup to see whether txtmode DETECTED the hard drive.
When it detected the drive, you can bail out, or go ahead and do full setup.

Full setup would tell you about PnP issues.

When I reread all this, it still looks as if some variants of Sil 3112 were/are causing a BSOD at different stages.. This depends on the mode this 3112 chip is set to, most likely.

The mode for the chip is selected in BIOS, and moving the INI section load order for the different modi of that chip can make a difference.

If you try one of those techniques, report back..
Help us help you..

I got the gigabyte CD download.
thanks

I will also compare VIA in 7902 with 712 release.

the Via drivers we have is newer than what Asus has in that link.

I found a new Jmicron reference driver, much newer than the asus download.
a 7128 tespack is in the making.

Hi
many moons ago somebody requested we put the IDE mode driver in TXTmode.
(I vaguely recall this IDE mode driver (Vibus) was in the Pack, but not put in the INI so it would only be used for PnP.)


now, let's tell a story..
During november/early December, fourteen testpacks were looked at, and the release still had an issue with Sil 3112 but it got no feedback until weeks after the release.
An additional 8 testpacks were built.
(the 7128 I last built has not been uploaded yet, because I have other requests to look into)
That last one would use a technique we used before..
One can move INI sections around, see..
The INI sections make drivers load in TXTmode in the order they are in he INI.

I would like to find out if we really need that Via IDE mode driver in the INI.
I have moved [V] viaraid section below the three other VIA like ten seconds ago.

We would also like to get people savvy to some of these tricks.
Rigchtclick the pack, Un7zip to folder, open folder, then open the INI, move the [V] section below [V4], save INI.
Then select the INI and D folder, Rightclick and run 7zip to pack it up.
It will show the PACK's name, and you better give it higher version number (7121, if you had 712)

Then copy the edited pack in the folder you use for slipstreaming.
Then test the build you make with the edited pack.
(You  don't have to run full setup to see whether txtmode DETECTED the hard drive. When it detected the drive, you can bail out, or go ahead and do full setup.)

Full setup would tell you about PnP issues.
(if any... Some variants of Sil 3112 were/are causing a BSOD at different stages.. Depending on the mode this 3112 chip was set to, most likely.)

Now, if this edit you tried does not work, you could try again, with the [V4] section removed (vibus)
If you try one of those techniques, report back..
Help us help you..
My part of the deal is that I'll look for an updated VIA raid driver and at the links I saw, and for your feedback.

996

(26 replies, posted in DriverPack Mass Storage)

hi
a mass storage driver you put in third party will only get looked at after windows has set up up and reboots into Plug N Play detection phase.

Put in third party, the mass storage driver would not be used for hard disk detection, which is what most people need. (during TXTmode, when windows setup is started.)

I saw other requests about this HP model, and have FOUR mass storage drivers to look at for this thing.
I just got up, and if it looks like I must work around duplicates (Like in, it is no update but uses same filenames), then I think I will make a TINY pack as a temporary solution.

this would be tested by you.
it MUST be tested by you.
If it works, and I have to do extra work to combine it into the released pack, then you MUST test the full pack too.
That's the deal.

997

(26 replies, posted in DriverPack Mass Storage)

Hi
I got four softpac files for that HP machine.. and I have some time off, but want some time off too..
I'll try to help you, and hope you will help us help you.

we never had the VIA's subsys
I think a generic was killed..

Hi
just got home..

I could be mistaken, but I have reason to believe some systemfiles have calls (or pokes?) to other files hardcoded in the binary.
That would mean we can try code the INF to get around dupe filenames and dupe HWIDs, and still see failure.
OK... if it works, it works, but if it doesn't we would have a hard time finding out what causes it.

When echoplatoon mailed me that solution, I was wondering why there was a call for these DLL and SYS files, because we see no such poke in the INF.

Of course, BartPE uses some techniques to build a CD, and Joshua's plugin works in PE.
JakeLD is quite good at combining and elimination, and I just read he got a new NV driver..
Yesterday I briefy looked at a 12.15 for 520/560 (we have 12.14 in the pack)

Jeff is coding, and the way things are going, chipset will be optimised for cabbing earlier than LAN will be ready for cabbing. (in chipset, we have maybe 20 problem files.. In Lan, I estimate we'll have 150)
These last few months, the work JakeLD and I did was aimed at optimisation of the packs, and I have been in the belief that what works for sysprep will work for DISC install.
I have not said it was achieved with ease.
I do believe we have made life easier for many by doing what we did.

It was a start?
Let's not falter in sight of the finish line..

Hi

too bad araxis cannot compare XLS files.
to find UNEDITED INFs and compare them with what we have now, you need 711

the grooming and pruning was started with 711 release as starting point.
It could be some INTEL INF files were edited..