Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

OEMs can write applications that manage system power states directly, without customizing Power Manager. Such applications must disable both the Graphics, Windowing, and the Graphics, Windowing, and Events Subsystem (GWES) and Power Manager and handle power states themselves. For more information about disabling GWES and Power Manager, see Power Manager Suspend Timeouts.

Power Manager may not be able to determine the state that it should resume from a suspended state. If OEMs allow the system to resume fully after each suspended state, this may not be an issue. However, if they choose to have real-time clock (RTC) alarms that partially wake the system, they may need to modify Power Manager anyway.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.