15 replies to this topic

[Damnation]

I'm trying to get the Kernel Mode driver Framework working on an XP install CD(both for phase 1 and 2)

This is for

Fresco Logic and VIA USB 3.0 support

but so far I keep getting a Stop 0x7E or a Stop 0x50 with WDFLDR.SYS

If anyone has any ideas, or has gotten this working before, please help!

heres my TXTSETUP.SIF

http://www.mediafire...t16qb6xanxi4zo7

Thanks!

[Sha0]

I'm trying to get the Kernel Mode driver Framework working on an XP install CD(both for phase 1 and 2)
...
but so far I keep getting a Stop 0x7E or a Stop 0x50 with WDFLDR.SYS

If anyone has any ideas, or has gotten this working before, please help!

My impression is that WDFLdr.Sys is not supposed to drive devices directly, but is a library for other drivers to use. In your TxtSetup.SIF, it seems that you have CriticalDeviceDatabase entries for driving certain devices with WDFLdr. This doesn't make sense, to me. I'd suggest finding out what the correct drivers are (if I'm correct) and then adding those into your TxtSetup.SIF.

heres my TXTSETUP.SIF

It might be easier for readers if you uploaded the original plus a diff. That way, readers could see what has changed from the original.

[cdob]

I'm trying to get the Kernel Mode driver Framework working on an XP install CD(both for phase 1 and 2)

Fresco Logic and VIA USB 3.0 support

but so far I keep getting a Stop 0x7E or a Stop 0x50 with WDFLDR.SYS

Do you get the BSOD at textmode boot or at guimode PNP?

If anyone has any ideas

http://forum.driverp...id=49723#p49723
One approach: Add one file \I386\WDFLDR.SY_
And edit txtsetup.sif

[SourceDisksFiles]

wdfldr.sys=1,,,,,,3_,4,0,0,,1,4

No other wdfldr addings to txtstup.sif: that's remove other lines with wdfldr.

[Damnation]

I need WDFLDR and WDF01000 loaded in textmode, or else textmode halts saying it can't find the files

I get 0x7E in textmode if WDFLDR is in bus extenders
I get 0x50 in guimode if WDFLDR isnt in bus extenders

is there a way to call WdfCoInstaller01009.dll when the driver needed in textmode? it might stop it from halting, so then I can avoid using these sys files extracted from it

[cdob]

I need WDFLDR and WDF01000 loaded in textmode, or else textmode halts saying it can't find the files

I get 0x7E in textmode if WDFLDR is in bus extenders

At which hardware do you get a BSOD 0x7E ?
I doubt bus extenders section. I doubt any [*.load] section.
Dosn't VIA xhcdrv.sys chainloads a file wdfldr.sy? ?

Did you tried the suggestion? What happens?

Feel free to add file WDF01000.SY_ at a second try.

I get 0x50 in guimode if WDFLDR isnt in bus extenders

At which hardware do you get a BSOD 0x50 ?
Does exist files %SystemRoot%\system32\drivers\wdfldr.sys and %SystemRoot%\system32\drivers\wdf01000.sys after first reboot?

How does include XP USB3 drivers at relating Fresco/VIA hardware?
Are there any service hints at registry?

is there a way to call WdfCoInstaller01009.dll when the driver needed in textmode? it might stop it from halting, so then I can avoid using these sys files extracted from it

I doubt this approach.
PNP installs WdfCoInstaller01009.dll as called by Fresco flxhcic.inf and VIA xhcdrv.inf.
Include WdfCoInstaller01009.dll to PNP drivers. Not to textmode.

[Damnation]

[SourceDisksFiles]

wdfldr.sys=1,,,,,,3_,4,0,0,,1,4

this leave behind, post-install, a wdfldr non pnp service and an error in event viewer saying that service cannot start, and recurs on every boot

adding wdf01000.sys causes the stop 0x50 BSOD with WDFLDR on the first reboot to phase 2

I get the 0x7E BSOD when I try to give hardware IDs to WDFLDR

[Sha0]

I'd suggest finding out what the correct drivers are (if I'm correct) and then adding those into your TxtSetup.SIF.

And sharing a link to where the vendor offers them for download, too.

[Damnation]

OK heres the driver

VIA

http://www.via-labs....V1.90A_WHQL.zip

FRESCO

station-drivers.com/telechargement/fresco%20logic/fresco_usb3_3.5.93.0(www.station-drivers.com).exe

[Sha0]

OK heres the driver

What is one set of PCI VENdor and DEVice IDs that you will be able to test?

[Damnation]

The VIA one

[cdob]

this leave behind, post-install, a wdfldr non pnp service

Read the suggestion again:
did you delete the bus extender section?
Keep the SourceDisksFiles line only, delete all other parts.

Which hardware do you use?
Which part installs a wdldr non pnp service?

[Sha0]

The VIA one

I am asking you for a specific VENdor and DEVice ID set that you will be able to test, please. Something like VVVV:DDDD.

[Damnation]

Controller

PCIVEN_1106&DEV_3432,PCIVEN_1106&DEV_9201

hub

USBVIA_ROOT_HUB,VUSB3CLASS_09,VUSB2CLASS_09,VUSB1CLASS_09

[Sha0]

Controller

PCIVEN_1106&DEV_3432,PCIVEN_1106&DEV_9201

[SourceDisksFiles]

wdfldr.sys = 100,,,,,,3_,4,1,,,1,4

wdf01000.sys = 100,,,,,,3_,4,1,,,1,4

xhcdrv.sys = 100,,,,,,3_,4,1,,,1,4



[HardwareIdsDatabase]

PCIVEN_1106&DEV_3432 = "xhcdrv"



[BootBusExtenders.Load]

wdf01000 = wdf01000.sys



[BusExtenders.Load]

xhcdrv = xhcdrv.sys



[files.wdf01000]

wdf01000.sys,4

wdfldr.sys,4



[files.xhcdrv]

xhcdrv.sys,4

wdfldr.sys,4

wdf01000.sys,4



[BootBusExtenders]

wdf01000 = "WDF01000",files.wdf01000,wdf01000



[BusExtenders]

xhcdrv = "VIA USB",files.xhcdrv,xhcdrv

Do the above changes help?

[Damnation]

I've since discovered that the VIA drivers are happy with wdfldr/wdf0100.sys just being present in the I386 folder, they don't need to be referenced in txtsetup.sif (not sure why that is)

[Sha0]

I've since discovered that the VIA drivers are happy with wdfldr/wdf0100.sys just being present in the I386 folder, they don't need to be referenced in txtsetup.sif (not sure why that is)

My impression is that WDFLdr.Sys is not supposed to drive devices directly, but is a library for other drivers to use.

You might enjoy using Dependency Walker. When NTLdr or SetupLdr load .SYS files, they first load the dependencies, if needed.