Re: Regarding the Power Management API

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Thank you Paul.I will try your idea
--
vinoth.R
Technical Lead
e-consystems India Pvt Ltd
www.e-consystems.com



"Paul G. Tobey [eMVP]" wrote:

My first idea is that this is a really strange thing to do. Why? All that
does is make your power manager non-standard (and potentially means that,
when Microsoft decides to use that API entry, your code breaks
spectacularly). Why not just create a DLL that implements the API that you
like and have anyone who wants to use it, include a header file and link
with an import library? At least it's portable... Or just code into your
program the right set of steps. In that case, you don't need some extra
DLL, you don't need a custom kernel, you don't need anything.

Paul T.

"Vinoth" <vinoth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:42FF8338-170C-4704-9773-20D67A94237E@xxxxxxxxxxxxxxxx
Thank you Paul. I will try the same.Now I am trying to add my own
systemcall
to do this by registering this in the devcore.c file as well as the pmif.c
file in the device manager code. I register this function in the mpm.h
file
as 30th system call since this entry is free.I compiled the devcore,pmif
sucessfully. Normally all PM APIs are in the coredll.lib so l link this
lib
but in driver code i am getting unresolved external symbol for that API. I
have done all the procedure followed for the other PM APIs. The way i am
doing is correct or i need to do anything more than that. Please give your
ideas.

Thank you
--
vinoth.R



"Paul G. Tobey [eMVP]" wrote:

No API specifically for that, of course. They're just settings in the
registry. Read the source for the control panel applet that changes them
to
see what it does when the user interactively makes a change and do the
same
thing yourself. It may send some sort of a notification event to tell
anyone who cares that there has been a registry change and those that
care
might read the new values.

Paul T.

"Vinoth" <vinoth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AF6876C6-F994-4A07-B7DB-31E150136FF0@xxxxxxxxxxxxxxxx
Hi all,
Is there any API to change the useridle and systemidle timeout in the
power
mangement ? Because these are registry setting and it is stored iin the
BOOT.hv file,if i enable the hive based registry. But i want to access
these
timings through application. I am unable to change the above registry
through
application. the power management driver is taking the registry entries
from
the BOOT.hv . please help me in this issue
--
vinoth.R







.



Relevant Pages

  • Re: Regarding the Power Management API
    ... does is make your power manager non-standard (and potentially means that, ... Why not just create a DLL that implements the API that you ... anyone who cares that there has been a registry change and those that ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [Full-Disclosure] PLEASE QUIT YACKING ABOUT M$
    ... on in order to get the 5% exploits within a single post, or all posts. ... >> simply another API. ... >> registry editor, in fact, the classes I put together treat them both very ... > from the filesysem, in Windows, you need to learn the filesystem API ...
    (Full-Disclosure)
  • RE: [Full-Disclosure] M$ - so what should they do?
    ... > simply another API. ... > registry editor, in fact, the classes I put together treat them both very ... And before you say you *can* configure apps by directly editing the ...
    (Full-Disclosure)
  • Re: Calling Still Image API in C#
    ... It appears that you are calling the API correctly. ... the interface in C# should be correct. ... recommending that you remove the registry key for your registered ...
    (microsoft.public.dotnet.framework.interop)
  • Re: mscoree.dll creating new appdomain with local configuration
    ... I will have a closer look at the API you ... mscoree.dll would handle some undocumented registry entries. ... loaded, there must be a runtime and a appdomain, the ccw has to be around. ... use a configuration file for that appdomain. ...
    (microsoft.public.dotnet.framework.interop)