Search options (Page 85 of 99)

Hi
copy or get soundpack B, (where the required driver is in), and put it in a empty folder
and get 7zip ( at http://www.7-zip.org )
install 7zip

rightclick and unpack soundpack B
you will find a D folder and an INI file
next, find STHDA.inf
open the INF with notepad

you'll find a section [sigmatel]

add this line under [SigmaTel]
%ST.DeviceDesc%=STHDA,HDAUDIO\FUNC_01&VEN_8384&DEV_7662&SUBSYS_104D0C00&REV_1002\4&B1E7652&0&0001
save, close, and now you have to repack soundpack B
(select BOTH the INI and the D folder, and 7zip it. )

call it DP_Sound_B_wnt5_x86-32_703test.7z

copy this to driverpacks folder, and use it for a test.
and, if it works, PLEASE post the result, so we can implement this.

hi

a couple guys, we banged our heads together some.
one can edit the mass storage INI, and repack.
one can actually change order by cut/paste a section

that way, if you have raid mode, and see that non-raid mode driver for same chip is listed before this (in the ini), move it and make it load later.
close the notepad editor, and save.
repack, using 7zip

the textmode.sif will then put them in after those that you think conflict.

for god's sake, let us KNOW if a change you made solved an issue, and which issue, so we can adress it, and find a permanent solution.

if it has an impact on a chip that can be used with drives in different modes, it could be that another solution has to be found by the team, for your hard drive mode could conflict with his mode.
(array/no array)
(no array/array)

for single drives, also report issues like "ahci mode does not work"

Changing modes in BIOS for a single drive that is in use, that has been known to be a problem, so... if you did that, tell us.

Hi
welcome

Vista and 64 bit versions are not supported (not yet....)

test version

far as I know, base 7.01 started to allow users to customise mass storage ini
this test version used this feature.
http://rapidshare.com/files/22957253/DP … nightly.7z
--------------------

-M-M
Update marvell Driver
replaced Ver= 11/14/2006,1.1.0.51 with marvell downloaded from intel 02/09/2007,1.2.0.24
(this version does not conflict with iastor)

[Marvell]
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6101
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6111
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6121
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6122
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6145

-M-M-O
old marvell DriverVer= 01/06/2006,1.0.0.3 Edited out HWID supported by newer version
Enabled for these three
PCI\VEN_11AB&DEV_6120
   PCI\VEN_11AB&DEV_6140
      VEN_11AB&DEV_6141

Massstorage INI update

removed a duplicate entry
[V-3] appeared twice
adjusted drivercount

edit to Highpoint [H-1] (reported by overflow, confirmed jtdoom)
a Fix for win2003, driver does not exist in XP. (also a Bart_PE fix)

Fixed (Muiz)
ATI (Siliconimage) 3112 driver
-\M\S\4 10/23/2006, 1.3.67.0

Test
edit in Mass storage ini makes Silicon Image raid mode drivers load before Silicon Image NON-raid

can you test this one for us, please?
TEST Silicon Image driver conflicts

--------
testversion 70319 will be pulled, this supercedes it

sneak preview to Mr Smartepants tutorial (after some more collaboration, it became revision 6)

this looks better than V5

http://users.pandora.be/jtdoom/basetute/Eng_tut6b.htm

you can still suggest changes.

actually, less.
the nighttly I referenced to, >1.01.51< had more Hwids, and the current release, 1.0.0.3 supplied in DP MS v7.0.1.1, has still more.

I think intel found out there were issues with older driver sets.
the nohdrv inf is like a filter, I guess.
that is just theories, I am prepared to help put together a test pack, where this is implemented.

TESTS
the main problem is that mass storage is a crucial factor in go or miss.
Some drivers have exclude sections, and Bâshrat the Sneaky has MOST probably collected more facts about conflicts than what we know about.
I just got home, and need zzz.
Thanks for the feedback, tho.

I put it on rapidshare, I am not sure you will be able to get the nightly..

http://rapidshare.com/files/21319178/DP … NIGHTLY.7z

I hope you have hardware you can test this on, and we would VERY much like to get feedback about the tests.

NOTES
in this new intel driver version, support for some older chips, still supported in the previous release, was dropped.

I have tried to keep support for the 910, 915 and 915 mobile versions, have therefore edited INF, and repacked.

what to test.
Intel(R) 82915G/GV/910GL Express Chipset Family, Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
and "Mobile Intel(R) 965 Express Chipset Family" (the new devices)

I tried to keep support for
%iGDGD0% = i915G0, PCI\VEN_8086&DEV_2582
%iGDGD1% = i915G1, PCI\VEN_8086&DEV_2782
%iALVD0% = i915GM0, PCI\VEN_8086&DEV_2592
%iALVD1% = i915GM1, PCI\VEN_8086&DEV_2792
they are..
iGDGD0    = "Intel(R) 82915G/GV/910GL Express Chipset Family"
iGDGD1    = "Intel(R) 82915G/GV/910GL Express Chipset Family"
iALVD0    = "Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family"
iALVD1    = "Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family"

NEW devices, not supported by the older version were these

%iCRGD0% = iCRG0, PCI\VEN_8086&DEV_2A02
%iCRGD1% = iCRG1, PCI\VEN_8086&DEV_2A03
they are
iCRGD0    = "Mobile Intel(R) 965 Express Chipset Family"
iCRGD1    = "Mobile Intel(R) 965 Express Chipset Family"

(editing the INF could break things.. I think I did it right, tho. The other option was to have a duplicate with newer drivers, overlapping the older one, for benefit of the newer hardware.)
I will update this post once the upload finishes

THIS IS A TEST VERSION.
http://rapidshare.com/files/21319178/DP … NIGHTLY.7z

looked for newest version, and found DriverVer= 02/09/2007,1.2.0.24
http://downloadfinder.intel.com/scripts … p;lang=eng

This one has an aditional inf file

[Files.SCSI.i386_61xx]
inf    = disk1, mv61xx.inf
inf     = disk1, mvnodrv.inf
driver    = disk1, mv61xx.sys, mv61xx
catalog = disk1, mv61xx.cat

the HWIDs here are
[Marvell]
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6101
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6111
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6121
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6122
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6145

looked at nightlies, and found one in there that has more HWIDS than the newest has
DriverVer= 11/14/2006,1.1.0.51
this one is found here

http://www.opendrivers.com/driver/23672 … nload.html

it also does Nodrv, from inside the inf

the one you pointed to
DriverVer= 07/06/2006,1.0.2.15 has still more HWIDs. More than any one of the newer ones.
it does not do the nodrv stuff

%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6145
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6141
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6140
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6121
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6122
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6120
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6111
%mv614xDesc%=mv614x_Inst,PCI\VEN_11AB&DEV_6101

I'll have to post in the testing forum, I think we have to bang our heads together about this one, and the "finisher" mass storage INI entries for Marvell.

hi fragbert,
I had not seen the edit.

so, this looks like a exceptions filtering job so as to replace the XP built in with the newest universal marvell.
I'll look wether one of our nightlies has the newest marvel in it, and if not, I will try make a testing verssion

I attended a funeral today, and will probaly not get around it tonight (not totally sober, sorta, and tired)
but, let us assume I take the task.
if another member wants to do it, post it here, for doubled effort is a waste of time.

(a testing version can be put on rapidshare or other public ftp)

hi
the intel made moboes would have their own particular filtering built in the driver INF
intels also makes moboes for large OEMs, usually with changes requested by the large OEM. (Dell come to mind).

drivers for the large OEM will be different than the pure intel, and will also differ from OEM mobo manufactors wich just use intel chipsets (in combination with their own selection of tertiary controllers)

in other words, it can be a mess.

here you go
http://forum.driverpacks.net/viewtopic. … 4030#p4030

the topic is a good read, and has plenty posters

I have just updated some txt in there...