Why no "disable" option in device manager?

Gary Li

unread,

Apr 18, 2010, 2:20:01 AM4/18/10

to

I custimized an audio driver based on AC97 sample in WDK, but it does not
expose "disable" in properties of my device in device manager.
Is it because my driver missed anything, or how to make the option show up.

Thanks

-Gary Li

Doron Holan [MSFT]

unread,

Apr 19, 2010, 1:20:22 PM4/19/10

to

a driver or ACPI can be indicating that the device is not disableable

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Gary Li" <gar...@verizon.net> wrote in message
news:52F34F4D-26E0-4112...@microsoft.com...

Gary Li

unread,

Apr 22, 2010, 1:22:01 AM4/22/10

to

The device was enumerated by ACPI with PnP ID = ACPI\xxxx
However, another driver with similar ID can be disabled.
Does DriverUnload(), or PnP IRPs affect disableable feature?

-Gary

"Doron Holan [MSFT]" wrote:

> .
>

Maxim S. Shatskih

unread,

Apr 22, 2010, 8:40:27 AM4/22/10

to

> Does DriverUnload(), or PnP IRPs affect disableable feature?

Yes, "query capabilities" one.

--
Maxim S. Shatskih
Windows DDK MVP
ma...@storagecraft.com
http://www.storagecraft.com

Doron Holan [MSFT]

unread,

Apr 22, 2010, 2:29:37 PM4/22/10

to

the HW ID is not the important part, it is other methods/properties that
acpi exposes for the device or the driver itself which is doing this at
runtime

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Gary Li" <gar...@verizon.net> wrote in message

news:70D9D3A8-2841-4374...@microsoft.com...

Gary Li

unread,

Apr 24, 2010, 8:04:01 PM4/24/10

to

Do you mean QueryDeviceCapabilities() in audio WaveRT miniport API?
That is the chance our audio driver may modify DEVICE_CAPABILITIES
typedef struct _DEVICE_CAPABILITIES {
USHORT Size;
USHORT Version;
ULONG DeviceD1 :1;
ULONG DeviceD2 :1;
ULONG LockSupported :1;
ULONG EjectSupported :1;
ULONG Removable :1;
ULONG DockDevice :1;
ULONG UniqueID :1;
ULONG SilentInstall :1;
ULONG RawDeviceOK :1;
ULONG SurpriseRemovalOK :1;
ULONG WakeFromD0 :1;
ULONG WakeFromD1 :1;
ULONG WakeFromD2 :1;
ULONG WakeFromD3 :1;
ULONG HardwareDisabled :1;
ULONG NonDynamic :1;
ULONG WarmEjectSupported :1;
ULONG NoDisplayInUI :1;
ULONG Reserved1 :1;
ULONG Reserved :13;
ULONG Address;
ULONG UINumber;
DEVICE_POWER_STATE DeviceState[POWER_SYSTEM_MAXIMUM];
SYSTEM_POWER_STATE SystemWake;
DEVICE_POWER_STATE DeviceWake;
ULONG D1Latency;
ULONG D2Latency;
ULONG D3Latency;
} DEVICE_CAPABILITIES, *PDEVICE_CAPABILITIES;
However, by reading the definitions of each field, I could find not anyone
may affect "disable" option in device manager.
Could you point out more clue?

Thanks

-Gary

"Maxim S. Shatskih" wrote:

> .
>

Gary Li

unread,

Apr 24, 2010, 8:07:01 PM4/24/10

to

Could you say it more specificly?
Which portion of device or driver may affect this feature?

Thanks

-Gary

"Doron Holan [MSFT]" wrote:

> .
>

Maxim S. Shatskih

unread,

Apr 25, 2010, 12:37:22 PM4/25/10

to

> However, by reading the definitions of each field, I could find not anyone
> may affect "disable" option in device manager.

Sorry, this is IoInvalidateDeviceState and MN_QUERY_DEVICE_STATE, not the capabilities.