[Windows 8.1, windows kdbclass.sys, kbdhid.sys]
On our USB HID Keyboard Device (Scanner device enumerating a keyboard), we are missing the Power Management Tab.
Under the Power Data Properties I’ve got the following:
Current Power State:
D0
Power Capabilities:
00000019
PDCAP_D0_SUPPORTED
PDCAP_D3_SUPPORTED
PDCAP_WAKE_FROM_D0_SUPPORTED
Power state mappings:
S0 -> D0
S1 -> D3
S2 -> D3
S3 -> D3
S4 -> D3
S5 -> D3
As it turns out, this is windows 8, not 8.1. Is this a known issue ?
On Mon, Nov 3, 2014 at 3:19 PM, wrote:
> [Windows 8.1, windows kdbclass.sys, kbdhid.sys]
>
> On our USB HID Keyboard Device (Scanner device enumerating a keyboard), we
> are missing the Power Management Tab.
>
> Under the Power Data Properties I’ve got the following:
>
> Current Power State:
> D0
>
> Power Capabilities:
> 00000019
> PDCAP_D0_SUPPORTED
> PDCAP_D3_SUPPORTED
> PDCAP_WAKE_FROM_D0_SUPPORTED
>
> Power state mappings:
> S0 -> D0
> S1 -> D3
> S2 -> D3
> S3 -> D3
> S4 -> D3
> S5 -> D3
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Thanks in advance,
Roscoe Casita
xxxxx@gmail.com wrote:
[Windows 8.1, windows kdbclass.sys, kbdhid.sys]
On our USB HID Keyboard Device (Scanner device enumerating a keyboard), we are missing the Power Management Tab.
Why did you expect one? That’s not intended as a snarky question. All
the conditions have to be right to let that tab appear. Are you looking
at the HID device (in the HID class in Device Manager) or at the
keyboard device (in the Keyboards class)? The device in the Keyboards
group should have the tab. The HID device might not.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Well, as it turns out, because it shows up under the HID Device section
some times… and under the Keyboard Section some times =) Thank you for
the clue we where at least able to find out where it was located …
But now I’m left more confused… what are the conditions it should show up
under the property sheet?
On Mon, Nov 3, 2014 at 4:42 PM, Tim Roberts wrote:
> xxxxx@gmail.com wrote:
> > [Windows 8.1, windows kdbclass.sys, kbdhid.sys]
> >
> > On our USB HID Keyboard Device (Scanner device enumerating a keyboard),
> we are missing the Power Management Tab.
>
> Why did you expect one? That’s not intended as a snarky question. All
> the conditions have to be right to let that tab appear. Are you looking
> at the HID device (in the HID class in Device Manager) or at the
> keyboard device (in the Keyboards class)? The device in the Keyboards
> group should have the tab. The HID device might not.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Thanks in advance,
Roscoe Casita
Roscoe Casita wrote:
Well, as it turns out, because it shows up under the HID Device
section some times… and under the Keyboard Section some times =)
Thank you for the clue we where at least able to find out where it
was located …
A USB keyboard should always have an entry in both sections.
But now I’m left more confused… what are the conditions it should
show up under the property sheet?
If you were writing your own driver, this is determined by the call to
WdfDeviceAssignSxWakeSettings. If you look at that page, you can see
there is a complicated set of rules to get things to line up.
From a UI perspective, it’s the keyboard that has the ability to wake
the system. The HID device is just plumbing.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Ahha! Thank you!
On Nov 3, 2014 5:20 PM, “Tim Roberts” wrote:
> Roscoe Casita wrote:
> > Well, as it turns out, because it shows up under the HID Device
> > section some times… and under the Keyboard Section some times =)
> > Thank you for the clue we where at least able to find out where it
> > was located …
>
> A USB keyboard should always have an entry in both sections.
>
>
> > But now I’m left more confused… what are the conditions it should
> > show up under the property sheet?
>
> If you were writing your own driver, this is determined by the call to
> WdfDeviceAssignSxWakeSettings. If you look at that page, you can see
> there is a complicated set of rules to get things to line up.
>
> From a UI perspective, it’s the keyboard that has the ability to wake
> the system. The HID device is just plumbing.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
A filter can’t enable wake though. Kbdclass is the power policy owner
d
Bent from my phone
From: Roscoe Casitamailto:xxxxx
Sent: ?11/?3/?2014 5:31 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: Re: [ntdev] Power Management Tab Missing…
Ahha! Thank you!
On Nov 3, 2014 5:20 PM, “Tim Roberts” > wrote:
Roscoe Casita wrote:
> Well, as it turns out, because it shows up under the HID Device
> section some times… and under the Keyboard Section some times =)
> Thank you for the clue we where at least able to find out where it
> was located …
A USB keyboard should always have an entry in both sections.
> But now I’m left more confused… what are the conditions it should
> show up under the property sheet?
If you were writing your own driver, this is determined by the call to
WdfDeviceAssignSxWakeSettings. If you look at that page, you can see
there is a complicated set of rules to get things to line up.
From a UI perspective, it’s the keyboard that has the ability to wake
the system. The HID device is just plumbing.
–
Tim Roberts, xxxxx@probo.commailto:xxxxx
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See http://www.osr.com/careers For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>