The system iterates over all possible standby states, starting with the
deepest state. Anytime a driver vetos a query to into an S state, a
lighter (if supported) S state is attempted until you run out of S
states.
Now, for mice 
… on XP and later, the mouse is automatically armed
for wake if the mouse can wake the machine from the machine’s deepest
sleep state. If the mouse cannot wake the machine from the deepest
state, it is still possible to arm the mouse, but mouclass will reject
any S states that the machine attempts to go into from which it cannot
wake the machine. Since the user is explicitly enabling this feature
(although perhaps unaware of the consequences), this was termed an
acceptable tradeoff. On win2k, there is no automatic enabling, but the
remainder of the behavior is the same. This is how it works for all bus
types (ps2, HID, etc), not just HID.
D
This posting is provided “AS IS” with no warranties, and confers no
rights
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Tuesday, September 16, 2003 8:16 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Question on power management (was Re: BulkUsb sample
experiences?)
It doesn’t in my case. OS asks for S3 and when it is vetoed, it
displayes a
dialog complaining our driver prevents standby. However, canceling
pending
Then a question to anybody who knows:
“Standby” can be mapped to S1, S2 or S3. How it is determined to what
ACPI
power state “Standby” is mapped?
Note that, for notebooks, “Standby” is obviously mapped to different
states
depending on whether the USB mouse is attached and whether wait/wake is
enabled
from it.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com