You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Damnation
Changing extension from DLL to SYS seems to do it.
but the SCSI sections make it freeze on "MS Kernel-Mode Driver Framework v1.9"
So is there a way to tell DP BASE to add
[SourceDisksFiles]
wdf1009.sys=1,,,,,,4_,4,1,,,1,4and nothing else?
(and also to accept DLL files too?)
You just did.
You'll notice that several new forums have been opened to you.
Thanks very much! appreciate it.
I think I've solved the wdf01000 error and leftover file.
I had trouble getting DP BASE to add a DLL file to txtsetup.sif, so I ended up doing this manually
I CAB compressed WdfCoInstaller01009.dll
renamed to
wdf1009.dll
added wdf1009.dll to \I386
added to txtsetup.sif
[SourceDisksFiles]
wdf1009.dll=1,,,,,,4_,4,1,,,1,4no more error or left over wdf01000
it still needs testing on real hardware though, anyone able to test?
attached txtsetup.sif and edf1009.dll
http://www.mediafire.com/?3gb5cz0uqsh22z8
Also, is there a way to get DP BASE to accept a DLL file in massstorage.ini?
I could never get it to work
I just noticed,
the HWIDs given to wdfldr and wdf01000
arent being written to txtsetup.sif - they seem to be ignored
but they are being written for the lines below eg viahub3, xhcdrv
KMDF is troublesome isn't it,
I'm inclined to agree that Fresco/VIA should be left out for now.
PS: Have you thought about joining the testing team?
Sure, how do i join?
I seem to have gotten rid of the error in event viewer.
now have a wdfldr under non pnp devices instead of wdf01000,
there was an error in setupapi.log - only difference being wdfldr instead of wdf01000.
the wdfldr service is running however, so i'm not sure if anything is wrong.
heres what i used
[UFV]
ms_count=6
ms_1_deviceName="MS Kernel-Mode Driver Framework v1.9 loader"
ms_1_tag="wdfldr"
ms_1_sysFile="wdfldr.sys"
ms_1_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09,PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201,USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"
;ms_2_deviceName="MS Kernel-Mode Driver Framework v1.9"
;ms_2_tag="wdf01000"
;ms_2_sysFile="wdf01000.sys"
;ms_2_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09,PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201,USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
;ms_2_isBusExtender=false
;ms_2_exc_skipIfOS="w2k,w2k3"
ms_3_deviceName="FRESCO USB3 Controller"
ms_3_tag="flxhcic"
ms_3_sysFile="flxhcic.sys"
ms_3_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400"
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="w2k,w2k3"
ms_4_deviceName="FRESCO USB3 Hub Controller"
ms_4_tag="flxhcih"
ms_4_sysFile="flxhcih.sys"
ms_4_hwids="FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_4_isBusExtender=false
ms_4_exc_skipIfOS="w2k,w2k3"
ms_5_deviceName="VIA USB3 Controller"
ms_5_tag="xhcdrv"
ms_5_sysFile="xhcdrv.sys"
ms_5_hwids="PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201"
ms_5_isBusExtender=false
ms_5_exc_skipIfOS="w2k,w2k3"
ms_6_deviceName="VIA USB3 Hub Controller"
ms_6_tag="Viahub3"
ms_6_sysFile="Viahub3.sys"
ms_6_hwids="USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_6_isBusExtender=false
ms_6_exc_skipIfOS="w2k,w2k3"does this work?
I think I may have gotten around the 0x50 BSOD with wdfldr.sys
or at least with my VM I have
[UFV]
ms_count=5
;ms_1_deviceName="MS Kernel-Mode Driver Framework v1.9"
;ms_1_tag="wdf01000"
;ms_1_sysFile="wdf01000.sys"
;ms_1_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09,PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201,USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
;ms_1_isBusExtender=false
;ms_1_exc_skipIfOS="w2k,w2k3"
ms_1_deviceName="MS Kernel-Mode Driver Framework v1.9 loader"
ms_1_tag="wdfldr"
ms_1_sysFile="wdfldr.sys"
ms_1_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09,PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201,USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"
ms_2_deviceName="FRESCO USB3 Controller"
ms_2_tag="flxhcic"
ms_2_sysFile="flxhcic.sys"
ms_2_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k,w2k3"
ms_3_deviceName="FRESCO USB3 Hub Controller"
ms_3_tag="flxhcih"
ms_3_sysFile="flxhcih.sys"
ms_3_hwids="FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="w2k,w2k3"
ms_4_deviceName="VIA USB3 Controller"
ms_4_tag="xhcdrv"
ms_4_sysFile="xhcdrv.sys"
ms_4_hwids="PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201"
ms_4_isBusExtender=false
ms_4_exc_skipIfOS="w2k,w2k3"
ms_5_deviceName="VIA USB3 Hub Controller"
ms_5_tag="Viahub3"
ms_5_sysFile="Viahub3.sys"
ms_5_hwids="USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_5_isBusExtender=false
ms_5_exc_skipIfOS="w2k,w2k3"and commented out wdf01000,
but I don't have the real hardware to test this with.
Try maybe, deleting everything related to KMDF, including exe's, inf's, except the 2 sys files and the dll files, maybe that might stop it from installing itself.
I agree that we should remove USB3 from chip-set and have them in mass storage,
regarding KMDF, does it still load if it's separated from the fresco/via drivers in it's own folder like how I had it originally?
also I thought you said KMDF was harmless?
I found this in update_xp.inf
;;
;; Uncomment this if the update.exe crash bug is fixed for xp 64 bit.
;;
;;[DeleteFilesInUninstallSections]
;;
;; The name of the setcion is a misnomer. This allows us to prevent the following files from being deleted.
;; if a previous vesion is present in that case this actually reverts to the previous version.
;;
;; SystemRoot\system32\drivers.delete.files,"wdf01000.sys"
;; SystemRoot\system32\drivers.delete.files,"wdfldr.sys"maybe if this is un-commented it might uninstall wdf01000 automatically itself
what are these alternate-OS Inf's your referring to?
Here's hoping the STOP $50/$7E BSOD's when doing a DP-Integrated XP install on non-USB3.0 systems will soon be vanquished! :^u
I never encountered those BSODs, but then all the systems I have tested all have USB3 on them.
Does this problem only occur on older systems that are exclusively USB2?
PS: Would one feature of this pack be the ability to do an install from a USB3 device at USB 3.0 speeds?
Pretty much
PPS: If an individual driver supports Server 2k3, would this not work for that OS too,
if one makes the appropriate edits?
I don't see why it wouldn't
Try swapping them round so that the driver Framework loads first, then load the driver.
[UF]
ms_count=4
; THIS IS NEEDED FOR FRSCO LOGIC AND VIA USB3 DRIVERS
ms_1_deviceName="Microsoft Kernel-Mode Driver Framework 1.9 loader"
ms_1_tag="wdfldr"
ms_1_sysFile="wdfldr.sys"
ms_1_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"
ms_2_deviceName="Microsoft Kernel-Mode Driver Framework 1.9"
ms_2_tag="wdf01000"
ms_2_sysFile="wdf01000.sys"
ms_2_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k,w2k3"
ms_3_deviceName="FRESCO USB3 Controller"
ms_3_tag="flxhcic"
ms_3_sysFile="flxhcic.sys"
ms_3_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400"
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="w2k,w2k3"
ms_4_deviceName="FRESCO USB3 Hub Controller"
ms_4_tag="flxhcih"
ms_4_sysFile="flxhcih.sys"
ms_4_hwids="FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_4_isBusExtender=false
ms_4_exc_skipIfOS="w2k,w2k3"put this in your mass-storage.ini
[N8]
; From nForce 15.56 DriverVer=04/09/2010,11.1.0.43
ms_count=1
ms_1_deviceName="NVIDIA nForce MCP61 SATA/RAID"
ms_1_tag="nvgts7r"
ms_1_sysFile="nvgts7r.sys"
ms_1_hwids="PCI\VEN_10DE&DEV_0266&CC_0104,PCI\VEN_10DE&DEV_0267&CC_0104,PCI\VEN_10DE&DEV_037E,PCI\VEN_10DE&DEV_036F,PCI\VEN_10DE&DEV_03F6&CC_0104,PCI\VEN_10DE&DEV_03F7,PCI\VEN_10DE&DEV_03E7,PCI\VEN_10DE&DEV_044C,PCI\VEN_10DE&DEV_07F8&CC_0104,PCI\VEN_10DE&DEV_07F9,PCI\VEN_10DE&DEV_07FA,PCI\VEN_10DE&DEV_07FB,PCI\VEN_10DE&DEV_0AD9,PCI\VEN_10DE&DEV_0AD8&CC_0104,PCI\VEN_10DE&DEV_0ABD&CC_0104,PCI\VEN_10DE&DEV_0ABC&CC_0104,PCI\VEN_10DE&DEV_0BC4,PCI\VEN_10DE&DEV_0BC5"
ms_1_isBusExtender=true
ms_1_exc_skipIfOS="w2k"
;ms_2_deviceName="NVIDIA nForce RAID Class Controller"
;ms_2_tag="nvrd327r"
;ms_2_sysFile="nvrd327r.sys"
;ms_2_hwids="SCSI\NVIDIA__Raid_Disk________,SCSI\__NVIDIA_______Raid_Disk,SCSI\NVIDIA__Raid_Disk_20_____,SCSI\__NVIDIA____Raid_Disk_20,*NVRAIDBUS,*NVRAID20"
;ms_2_isBusExtender=true
;ms_2_exc_skipIfOS="w2k"So where do I place SAD2 in XP ISO?
OK
So would this work for SAD2 on XP?
%WinXP-Disc%\$oem$\$1\D\SAD2
%WinXP-Disc%\$oem$\$$\Setup\scripts\setupcomplete.cmdAlso only option for XP driver integration is DP BASE?
if so, would method1 preserve the system repair option?
Do you have an driver integration and SAD2 script for XP aswell?
Thanks very much!
Since DISM is used would your scripts work for vista aswell?
Also, something newer for XP textmode (besides DP BASE - breaks repair)?
so I create a setupcomplete.cmd file with the above right?
I would like it to inject the driver packs into boot.wim will SAD2 do this?
So I extract the ISO
then I create these folders in \sources?
\$oem$
\$oem$\$!\D\SAD2
\$oem$\$$\setup\scripts\is this correct?
do I keep the $ symbols?
so do I run setupcomplete.cmd before I build the ISO?
I currently use DP BASE for driver integration into XP SP3, and rt7lite for Win7
Can SAD2 be used to integrate drivers into an ISO?
or is it only for existing installations?
if I can integrate into an ISO, I'd like to be able to do it for XPSP3, Vista and Win7
Thanks for the help! Universal Extractor did the trick! (admittedly, I skipped universal extractor because I assumed 7zip would be able to do it)
Updated renesas drivers
http://www.mediafire.com/?1hh429whwdv48ha
anything else I need to do?
Congratulations Damnation, your test pack has sorted it!!
Many apologies for the delay!
Glad to be of assistance.
So, should we have the ini changed for the next version of the mass storage driverpack?
or is there a better solution for this?
Maybe I didn't extract properly the first time
heres what I got
http://www.mediafire.com/?cy8bmup4bnfwz23
do they match what you extracted?
OK
AMD USB 3 Drivers added,
but these
"The latest driver for the uPD720200(a) series is 2.1.36.0"
...
"The latest driver for the uPD720201, 2 series is 3.0.20.0"
don't work,
Windows XP says they are corrupt
So I've used the ones in Chipset 12.09
I made a test pack with Megaintel loading between I and I2
candles, can you try it out? (remove megaintl from filename before you integrate)
DriverPacks.net Forum » Posts by Damnation
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.016 seconds, 5 queries executed ]