Re: [KMDF] Removing FDO and let PDO running

Thanks,

Doron Holan [MS] a écrit :
instead of uninstalling, disable the device.

Device manager won't let me, the disable icon is not present for my device. Where can I find all the reasons why it's like that ?

does an application open a handle to your device? if so, that application must register for handle notifications, otherwise the disable/remove will fail.

I don't think so, WinObj tells me :
- 1 reference
- 0 handle

the setup logs (see http://blogs.msdn.com/doronh/archive/2006/08/31/734412.aspx) will tell you why the uinstall/disable required a reboot. by default, KMDF allows a graceful disable/uninstall, so there is something else that is keeping your device stack around and requiring the reboot.

setupapi.log shows something strange when I disable then reenable the PDO for the system timer without my FDO installed on top :

[HERE I DISABLE]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc /s
#I292 Changing device properties of "ACPI\PNP0100\3&2411E6FE&0".

[HERE I RE-ENABLE]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc /s
#I292 Changing device properties of "ACPI\PNP0100\3&2411E6FE&0".
#I292 Changing device properties of "ACPI\PNP0100\3&2411E6FE&0".
#W165 Device "ACPI\PNP0100\3&2411E6FE&0" required reboot: Device not started (unknown reason).
#I294 DICS_ENABLE DICS_FLAG_GLOBAL: Enabling device globally.

Maybe it has something to do with the PDO being "no driver"
.

Loading