Dear Sirs.
screen keeps darking status…after USB remote wakeup.
How can i get my desktop back?
ps. my device is not keyborad or mouse
Dear Sirs.
screen keeps darking status…after USB remote wakeup.
How can i get my desktop back?
ps. my device is not keyborad or mouse
Why does the screen need to come back up? The screen only comes back up
if the user needs to use the machine. By indicating that a user is
present, all power timers are reset.
With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
screen will come up, but like I said, any timers (for auto standby or
hibernate for instance) will be reset. Furthermore, it is my experience
that when any device on the usb bus signals remote wakeup, all the
devices which have sent a wait wake request will have it complete with
success. This means that you will not definitively know that it was
your device which woke the machine through a successful wait wake
completion. Unless you definitively know your device woke the machine,
you should not call PoSetSystemState(ES_USER_PRESENT)
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of polybear
Sent: Thursday, August 19, 2004 3:28 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] darking screen after remote wakeup
Dear Sirs.
screen keeps darking status…after USB remote wakeup.
How can i get my desktop back?
ps. my device is not keyborad or mouse
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
oh… there is a trouble again.
I try to call PoSetSystemState in the callback routine of
PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
(ES_DISPLAY_REQUIRED ).
It seem good in 2000 and XP. The screen come back up smoothly.
But, in win98 se, it doesn’t work. Driver even can’t be loaded by
NTKERN.VXD ,
says by device manager. Since driver doesn’t run , i can’t skip
PoSetSystemState by difference OS version.
???why…how?
ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
“Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev ¤¤¼¶¼g
…
Why does the screen need to come back up? The screen only comes back up
if the user needs to use the machine. By indicating that a user is
present, all power timers are reset.
With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
screen will come up, but like I said, any timers (for auto standby or
hibernate for instance) will be reset. Furthermore, it is my experience
that when any device on the usb bus signals remote wakeup, all the
devices which have sent a wait wake request will have it complete with
success. This means that you will not definitively know that it was
your device which woke the machine through a successful wait wake
completion. Unless you definitively know your device woke the machine,
you should not call PoSetSystemState(ES_USER_PRESENT)
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of polybear
Sent: Thursday, August 19, 2004 3:28 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] darking screen after remote wakeup
Dear Sirs.
screen keeps darking status…after USB remote wakeup.
How can i get my desktop back?
ps. my device is not keyborad or mouse
—
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
Build in 2000 DDK , in win2000.
“polybear” ¦b¶l¥ó news:xxxxx@ntdev ¤¤¼¶¼g…
> oh… there is a trouble again.
> I try to call PoSetSystemState in the callback routine of
> PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
> (ES_DISPLAY_REQUIRED ).
> It seem good in 2000 and XP. The screen come back up smoothly.
> But, in win98 se, it doesn’t work. Driver even can’t be loaded by
> NTKERN.VXD ,
> says by device manager. Since driver doesn’t run , i can’t skip
> PoSetSystemState by difference OS version.
>
> ???why…how?
>
> ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
>
>
>
> “Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev ¤¤¼¶
¼g
> …
> Why does the screen need to come back up? The screen only comes back up
> if the user needs to use the machine. By indicating that a user is
> present, all power timers are reset.
>
> With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
> screen will come up, but like I said, any timers (for auto standby or
> hibernate for instance) will be reset. Furthermore, it is my experience
> that when any device on the usb bus signals remote wakeup, all the
> devices which have sent a wait wake request will have it complete with
> success. This means that you will not definitively know that it was
> your device which woke the machine through a successful wait wake
> completion. Unless you definitively know your device woke the machine,
> you should not call PoSetSystemState(ES_USER_PRESENT)
>
> d
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of polybear
> Sent: Thursday, August 19, 2004 3:28 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] darking screen after remote wakeup
>
> Dear Sirs.
> screen keeps darking status…after USB remote wakeup.
> How can i get my desktop back?
>
> ps. my device is not keyborad or mouse
>
>
>
> —
> 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
>
>
>
Are you always calling PoSetSystemState in the po request completion routine? Or only if NT_SUCCESS(IoStatus->Status) ? As for win9x, it appears that PoSetSystemState is not exporte on that OS. See Oney’s book on how to overcome that problem. As for XP not working, perhaps you are calling the API when the system is still moving down into Sx.
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of polybear
Sent: Thursday, August 19, 2004 10:46 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] darking screen after remote wakeup
oh… there is a trouble again.
I try to call PoSetSystemState in the callback routine of
PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
(ES_DISPLAY_REQUIRED ).
It seem good in 2000 and XP. The screen come back up smoothly.
But, in win98 se, it doesn’t work. Driver even can’t be loaded by
NTKERN.VXD ,
says by device manager. Since driver doesn’t run , i can’t skip
PoSetSystemState by difference OS version.
???why…how?
ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
“Doron Holan” ?b?l?? news:xxxxx@ntdev ???g
…
Why does the screen need to come back up? The screen only comes back up
if the user needs to use the machine. By indicating that a user is
present, all power timers are reset.
With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
screen will come up, but like I said, any timers (for auto standby or
hibernate for instance) will be reset. Furthermore, it is my experience
that when any device on the usb bus signals remote wakeup, all the
devices which have sent a wait wake request will have it complete with
success. This means that you will not definitively know that it was
your device which woke the machine through a successful wait wake
completion. Unless you definitively know your device woke the machine,
you should not call PoSetSystemState(ES_USER_PRESENT)
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of polybear
Sent: Thursday, August 19, 2004 3:28 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] darking screen after remote wakeup
Dear Sirs.
screen keeps darking status…after USB remote wakeup.
How can i get my desktop back?
ps. my device is not keyborad or mouse
—
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
—
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
Windows 98/98SE exports only PoSetPowerState() function that is a simple
stub. Therefore NTKERN can’t load your driver because of unresolved function
call (PoSetSystemState()).
Winsows Me exports both PoSetPowerState() (again it’s a simple stub) and
PoSetSystemState().
----- Original Message -----
From: “polybear”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Friday, August 20, 2004 9:45 AM
Subject: Re:[ntdev] darking screen after remote wakeup
> oh… there is a trouble again.
> I try to call PoSetSystemState in the callback routine of
> PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
> (ES_DISPLAY_REQUIRED ).
> It seem good in 2000 and XP. The screen come back up smoothly.
> But, in win98 se, it doesn’t work. Driver even can’t be loaded by
> NTKERN.VXD ,
> says by device manager. Since driver doesn’t run , i can’t skip
> PoSetSystemState by difference OS version.
>
> ???why…how?
>
> ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
>
>
>
> “Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev
¤¤¼¶¼g
> …
> Why does the screen need to come back up? The screen only comes back up
> if the user needs to use the machine. By indicating that a user is
> present, all power timers are reset.
>
> With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
> screen will come up, but like I said, any timers (for auto standby or
> hibernate for instance) will be reset. Furthermore, it is my experience
> that when any device on the usb bus signals remote wakeup, all the
> devices which have sent a wait wake request will have it complete with
> success. This means that you will not definitively know that it was
> your device which woke the machine through a successful wait wake
> completion. Unless you definitively know your device woke the machine,
> you should not call PoSetSystemState(ES_USER_PRESENT)
>
> d
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of polybear
> Sent: Thursday, August 19, 2004 3:28 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] darking screen after remote wakeup
>
> Dear Sirs.
> screen keeps darking status…after USB remote wakeup.
> How can i get my desktop back?
>
> ps. my device is not keyborad or mouse
>
>
>
> —
> 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
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@nival.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
yes… i am always calling PoSetSystemState in po request(ww) callback
reutine.
I had checked Oney’s book , and overcome that problem. But
PoSetSystemState(after readdressing) almost do nothing in Oney’s
wdmstub.sys.
So, the screen keep dark in win98. @.@
I am learning…i will try harder!!
“Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev ¤¤¼¶¼g
…
Are you always calling PoSetSystemState in the po request completion
routine? Or only if NT_SUCCESS(IoStatus->Status) ? As for win9x, it
appears that PoSetSystemState is not exporte on that OS. See Oney’s book on
how to overcome that problem. As for XP not working, perhaps you are
calling the API when the system is still moving down into Sx.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of polybear
Sent: Thursday, August 19, 2004 10:46 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] darking screen after remote wakeup
oh… there is a trouble again.
I try to call PoSetSystemState in the callback routine of
PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
(ES_DISPLAY_REQUIRED ).
It seem good in 2000 and XP. The screen come back up smoothly.
But, in win98 se, it doesn’t work. Driver even can’t be loaded by
NTKERN.VXD ,
says by device manager. Since driver doesn’t run , i can’t skip
PoSetSystemState by difference OS version.
???why…how?
ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
“Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev ¤¤¼¶¼g
…
Why does the screen need to come back up? The screen only comes back up
if the user needs to use the machine. By indicating that a user is
present, all power timers are reset.
With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
screen will come up, but like I said, any timers (for auto standby or
hibernate for instance) will be reset. Furthermore, it is my experience
that when any device on the usb bus signals remote wakeup, all the
devices which have sent a wait wake request will have it complete with
success. This means that you will not definitively know that it was
your device which woke the machine through a successful wait wake
completion. Unless you definitively know your device woke the machine,
you should not call PoSetSystemState(ES_USER_PRESENT)
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of polybear
Sent: Thursday, August 19, 2004 3:28 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] darking screen after remote wakeup
Dear Sirs.
screen keeps darking status…after USB remote wakeup.
How can i get my desktop back?
ps. my device is not keyborad or mouse
—
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
—
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
oh… i got it…, the program will be ok in WinME.
Could you tell me what is the meaning of “simple stub”?
I couldn’t understand this word ,“stub”?
“Konstantin Manurin” ¦b¶l¥ó news:xxxxx@ntdev
¤¤¼¶¼g…
> Windows 98/98SE exports only PoSetPowerState() function that is a simple
> stub. Therefore NTKERN can’t load your driver because of unresolved
function
> call (PoSetSystemState()).
>
> Winsows Me exports both PoSetPowerState() (again it’s a simple stub) and
> PoSetSystemState().
>
>
> ----- Original Message -----
> From: “polybear”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Friday, August 20, 2004 9:45 AM
> Subject: Re:[ntdev] darking screen after remote wakeup
>
>
> > oh… there is a trouble again.
> > I try to call PoSetSystemState in the callback routine of
> > PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
> > (ES_DISPLAY_REQUIRED ).
> > It seem good in 2000 and XP. The screen come back up smoothly.
> > But, in win98 se, it doesn’t work. Driver even can’t be loaded by
> > NTKERN.VXD ,
> > says by device manager. Since driver doesn’t run , i can’t skip
> > PoSetSystemState by difference OS version.
> >
> > ???why…how?
> >
> > ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
> >
> >
> >
> > “Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev
> ¤¤¼¶¼g
> > …
> > Why does the screen need to come back up? The screen only comes back up
> > if the user needs to use the machine. By indicating that a user is
> > present, all power timers are reset.
> >
> > With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
> > screen will come up, but like I said, any timers (for auto standby or
> > hibernate for instance) will be reset. Furthermore, it is my experience
> > that when any device on the usb bus signals remote wakeup, all the
> > devices which have sent a wait wake request will have it complete with
> > success. This means that you will not definitively know that it was
> > your device which woke the machine through a successful wait wake
> > completion. Unless you definitively know your device woke the machine,
> > you should not call PoSetSystemState(ES_USER_PRESENT)
> >
> > d
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of polybear
> > Sent: Thursday, August 19, 2004 3:28 AM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] darking screen after remote wakeup
> >
> > Dear Sirs.
> > screen keeps darking status…after USB remote wakeup.
> > How can i get my desktop back?
> >
> > ps. my device is not keyborad or mouse
> >
> >
> >
> > —
> > 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
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@nival.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
>
>
Hi Polybear,
A stub in programming sense, is usually an “empty function” or “place
holder”, i.e. some function that is there to fill the space of a future=
functio. It’s also used when there is a set of function pointers that a=
re
required by some protocol in an interface, and the current project does=
n’t
need the functionality supported.
I think you’ll find that the disassembly of the PoSetSystemState is an
empty function (in Win9X/ME), and that’s what it means here.
Hope this helps.
“polybear” =
m.tw> =
To
Sent by: “Windows System Software Devs =
bounce-184978-140 Interest List” =
xxxxx@lists.osr.com =
=
cc
=
08/20/2004 12:52 Subj=
ect
PM Re:[ntdev] Re:darking screen aft=
er
remote wakeup =
=
Please respond to =
“Windows System =
Software Devs =
Interest List” =
com> =
=
=
oh… i got it…, the program will be ok in WinME.
Could you tell me what is the meaning of “simple stub”?
I couldn’t understand this word ,“stub”?
“Konstantin Manurin” =A6b=B6l=A5=F3 news=
:xxxxx@ntdev
=A4=A4=BC=B6=BCg…
> Windows 98/98SE exports only PoSetPowerState() function that is a sim=
ple
> stub. Therefore NTKERN can’t load your driver because of unresolved
function
> call (PoSetSystemState()).
>
> Winsows Me exports both PoSetPowerState() (again it’s a simple stub) =
and
> PoSetSystemState().
>
>
> ----- Original Message -----
> From: “polybear”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List” >
> Sent: Friday, August 20, 2004 9:45 AM
> Subject: Re:[ntdev] darking screen after remote wakeup
>
>
> > oh… there is a trouble again.
> > I try to call PoSetSystemState in the callback routine of
> > PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
> > (ES_DISPLAY_REQUIRED ).
> > It seem good in 2000 and XP. The screen come back up smoothly.
> > But, in win98 se, it doesn’t work. Driver even can’t be loaded by
> > NTKERN.VXD ,
> > says by device manager. Since driver doesn’t run , i can’t skip
> > PoSetSystemState by difference OS version.
> >
> > ???why…how?
> >
> > ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in =
XP.
> >
> >
> >
> > “Doron Holan” =A6b=B6l=A5=F3 news:61=
xxxxx@ntdev
> =A4=A4=BC=B6=BCg
> > …
> > Why does the screen need to come back up? The screen only comes ba=
ck
up
> > if the user needs to use the machine. By indicating that a user is=
> > present, all power timers are reset.
> >
> > With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
> > screen will come up, but like I said, any timers (for auto standby =
or
> > hibernate for instance) will be reset. Furthermore, it is my
experience
> > that when any device on the usb bus signals remote wakeup, all the
> > devices which have sent a wait wake request will have it complete w=
ith
> > success. This means that you will not definitively know that it wa=
s
> > your device which woke the machine through a successful wait wake
> > completion. Unless you definitively know your device woke the mach=
ine,
> > you should not call PoSetSystemState(ES_USER_PRESENT)
> >
> > d
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of polybear
> > Sent: Thursday, August 19, 2004 3:28 AM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] darking screen after remote wakeup
> >
> > Dear Sirs.
> > screen keeps darking status…after USB remote wakeup.
> > How can i get my desktop back?
> >
> > ps. my device is not keyborad or mouse
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=3D256
> >
> > You are currently subscribed to ntdev as: xxxxx@windows.microsoft.=
com
> > To unsubscribe send a blank email to xxxxx@lists.osr.c=
om
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=3D256
> >
> > You are currently subscribed to ntdev as: xxxxx@nival.=
com
> > To unsubscribe send a blank email to xxxxx@lists.osr.c=
om
> >
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=3D256
You are currently subscribed to ntdev as: xxxxx@3dlabs.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
ForwardSourceID:NT00001BBA=
Sir Mats PETERSSON
I understand waht you say. thank you…
“Mats PETERSSON” ¦b¶l¥ó news:xxxxx@ntdev ¤¤¼¶¼g
…
Hi Polybear,
A stub in programming sense, is usually an “empty function” or “place
holder”, i.e. some function that is there to fill the space of a future
functio. It’s also used when there is a set of function pointers that are
required by some protocol in an interface, and the current project doesn’t
need the functionality supported.
I think you’ll find that the disassembly of the PoSetSystemState is an
empty function (in Win9X/ME), and that’s what it means here.
Hope this helps.
–
Mats
“polybear”
m.tw> To
Sent by: “Windows System Software Devs
bounce-184978-140 Interest List”
xxxxx@lists.osr.com
cc
08/20/2004 12:52 Subject
PM Re:[ntdev] Re:darking screen after
remote wakeup
Please respond to
“Windows System
Software Devs
Interest List”
com>
oh… i got it…, the program will be ok in WinME.
Could you tell me what is the meaning of “simple stub”?
I couldn’t understand this word ,“stub”?
“Konstantin Manurin” ¦b¶l¥ó news:xxxxx@ntdev
¤¤¼¶¼g…
> Windows 98/98SE exports only PoSetPowerState() function that is a simple
> stub. Therefore NTKERN can’t load your driver because of unresolved
function
> call (PoSetSystemState()).
>
> Winsows Me exports both PoSetPowerState() (again it’s a simple stub) and
> PoSetSystemState().
>
>
> ----- Original Message -----
> From: “polybear”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Friday, August 20, 2004 9:45 AM
> Subject: Re:[ntdev] darking screen after remote wakeup
>
>
> > oh… there is a trouble again.
> > I try to call PoSetSystemState in the callback routine of
> > PoRequestPowerIrp(…IRP_MN_WAIT_WAKE…) as PoSetSystemState
> > (ES_DISPLAY_REQUIRED ).
> > It seem good in 2000 and XP. The screen come back up smoothly.
> > But, in win98 se, it doesn’t work. Driver even can’t be loaded by
> > NTKERN.VXD ,
> > says by device manager. Since driver doesn’t run , i can’t skip
> > PoSetSystemState by difference OS version.
> >
> > ???why…how?
> >
> > ps. PoSetSystemState (ES_USER_PRESENT ) can’t light the screen in XP.
> >
> >
> >
> > “Doron Holan” ¦b¶l¥ó news:xxxxx@ntdev
> ¤¤¼¶¼g
> > …
> > Why does the screen need to come back up? The screen only comes back
up
> > if the user needs to use the machine. By indicating that a user is
> > present, all power timers are reset.
> >
> > With that said, if you call PoSetSystemState(ES_USER_PRESENT), the
> > screen will come up, but like I said, any timers (for auto standby or
> > hibernate for instance) will be reset. Furthermore, it is my
experience
> > that when any device on the usb bus signals remote wakeup, all the
> > devices which have sent a wait wake request will have it complete with
> > success. This means that you will not definitively know that it was
> > your device which woke the machine through a successful wait wake
> > completion. Unless you definitively know your device woke the machine,
> > you should not call PoSetSystemState(ES_USER_PRESENT)
> >
> > d
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of polybear
> > Sent: Thursday, August 19, 2004 3:28 AM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] darking screen after remote wakeup
> >
> > Dear Sirs.
> > screen keeps darking status…after USB remote wakeup.
> > How can i get my desktop back?
> >
> > ps. my device is not keyborad or mouse
> >
> >
> >
> > —
> > 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
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@nival.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.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@3dlabs.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
ForwardSourceID:NT00001BBA