Bâshrat the Sneaky

It's really about time that I write an article about this. Please visit this topic often, until we have a working solution. I'll write a guide then. Did you try this? If you change the root to Z:\ or whatever your share is, it should work. But don't forget you'll have to use METHOD TWO, NOT method 1 for this... trial.

The HWIDs are different.... AHCI & RAID have different CC's... Please post your HWID.

hehe Glad it's fixed EDIT: Topic closed.

Yeah I found it myself. But it sucks that you cannot select several files at once to extract.... It seems they simply have a newer version of the i6comp CLI program... I'll use that again now... That works faster & easier....

Never heard of that app before Thanks

Wow that's some list Thanks

I can't get the new Intel Matrix Storage driver extracted ..... ftp://aiedownload.intel.com/df-support/90...8/iata51_cd.exe tried: -extract archive => .cat files only -setup.exe -A -S -P C:\inteltemp => nothing -extract archive, i6comp x data1.cab, i6comp x data2.cab => all .dll files, but still no .inf or .sys....

ccfly, if you don't post your HWID I cannot help you.

If you put them in UNCOMPRESSED form on a CD (you will need a 700MB CD), then you can just select the .inf file... Or let Windows search through the drivers. Moved to DriverPacks General Discussion.

The only possible reason that you've got this problem is that you've slipstreamed this driver yourself, before using the DriverPacks for the first time and therefor the txtsetup.old file has it too... Which makes the txtsetup.sif file inherit these entries! Please attach your txtsetup.old & txtsetup.sif.

oneless is right, I also doubt you've put DriverPack MassStorae in the DriverPacks folder! Or did you RENAME it, perhaps?

What do you mean? Why would you need 2 distribution points?

Check my sig! @muiz: yes yes, I haven't forgotten about that one... And the SiI3512 driver != comparable with the nVidia nForce drivers...

IT IS working? Thanks

Well... I can assure you this is NOT being caused by the DriverPacks. Anyone else reading this topic will be able to confirm this.

LOL I must have overlooked a fact: AMD 6.66 pataraid dir | nvatabus.sys: ID 01 | nvraid.sys: ID 02 sata_ide dir | nvata.sys: ID 01 sararaid dir | nvatabus.sys: ID 01 | nvraid.sys: ID 02 Intel 7.13 pataraid dir | nvatabus.sys: ID 01 | nvraid.sys: ID 02 sata_ide dir | nvata.sys: ID 01 sataraid dir | nvatabus.sys: ID 01 sata_ide dir | nvata.sys: ID 01 | nvraid.sys ID 02 SO THEY ARE STILL ALL IDENTICAL ****DING DING**** ***We're pleased to announce that EVERY READER OF THIS TOPIC gets one credit to punch Bâshrat the Sneaky*** ***DING DING*** I'm VERY VERY VERY sorry and I hope this didn't affect you all too much... I'm fixing it right away!

I've got an archive with ALL DriverPacks so I've also got all slipstream_DPM.cmd files . This is how I've currently integrated the nVidia drivers: REM NVIDIA REM AMD/INTEL PATARAID %T1% "PCI\VEN_10DE&DEV_008E = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_0085 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_00D5 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_00EE = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_00E3 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_00E5 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_0035 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_0036 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_003E = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_0053 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_0054 = \"nvatabus\"" %T1% "PCI\VEN_10DE&DEV_0055 = \"nvatabus\"" REM AMD SATA IDE %T1% "PCI\VEN_10DE&DEV_0055&CC_0101 = \"a_nvata\"" %T1% "PCI\VEN_10DE&DEV_0054&CC_0101 = \"a_nvata\"" %T1% "PCI\VEN_10DE&DEV_0053&CC_0101 = \"a_nvata\"" REM INTEL SATA IDE %T1% "PCI\VEN_10DE&DEV_003E&CC_0101 = \"i_nvata\"" %T1% "PCI\VEN_10DE&DEV_0036&CC_0101 = \"i_nvata\"" %T1% "PCI\VEN_10DE&DEV_0035&CC_0101 = \"i_nvata\"" REM AMD SATARAID %T1% "PCI\VEN_10DE&DEV_0055&CC_0104 = \"a_nvraid\"" %T1% "PCI\VEN_10DE&DEV_0054&CC_0104 = \"a_nvraid\"" REM INTEL SATARAID %T1% "PCI\VEN_10DE&DEV_003E&CC_0104 = \"i_nvraid\"" %T1% "PCI\VEN_10DE&DEV_0036&CC_0104 = \"i_nvraid\"" REM NVRAID %T1% "GenNvRaidDisk = \"nvraid\"" %T1% "*_NVRAIDBUS = \"nvraid\"" %T1% "*NVRAIDBUS = \"nvraid\"" If anyone knows the solution, please tell me.

Without a doubt this is NOT being cauded by the DriverPacks. The DriverPacks don't edit ANY system .dll file, except for adding a high definition audio patch (hdaud* files). So the problem lies a 100% sure somewhere else! Did you use nLite, did you use RyanVM's UpdatePacks, did you use....? Topic moved to DriverPack General Discussion.

F*CK!!! If all nvraid stuff is broken.... then it's one misery... pfffff **** that. Chertoianov, please post your HWID, so I know which one is giving trouble. Maybe we can find a solution that way...

The nForce driver isn't working???

??? Like i said : i did a fresh xp with your pack, so no i didnt just copied it. it was just missing, you deleted the driver but not the entry. I took out the sys file from old uaxpcd, put that in i386 folder, problem solved.(viaidexp.sys) Staying D folder problem..not solved ← The entry IS removed... The 'D' folder that stays... does anyone else have that problem too?

That seems to be a brand with no chips of its own. Probably they just relabel chips as their own. Did you already test DriverPack WLAN in combination with any of their WLAN controllers?

That's correct. WatchDriverSigningPolicy.exe should prevent this from happening, but for some odd, unknown reason it doesn't do that. These entries in the winnt.sif might solve the problem, but that chance is VERY little... Though it's worth trying. This problem has been reported before, but I haven't heard it for a while... So I forgot about it... Maybe an AutoIt script is the solution...

Yes, I forgot to add that to the changelog...

:o WTF... I'll check it... Did you simply copy the new DP MassStorage, didnt' you slipstream it?