Reply to thread

Message

Hi fred,
Good work. I have some thoughts I want to share. Please make comments about them...
I'm not sure PS (PowerScheduler) handling hibernate etc in right way.
In my point of view it would be better if it works like this:

1/ If the user have done any input (keyboard, mouse) then PS should never suspend/hibernate automaticly. It's up to the user (or windows internal shut down timers) when he wants power off / hibernate / suspend. Many people (at least me) have other tasks ongoing sometimes (server, DC, whatsoever)
2/ If PS have waked up the computer for a task, then after the task have completed, PS should put it to the same sleepstate as it was in before. But only if the user don't have done any inputs (keyb, mouse).
3/ I think its better to kill MP before going to sleepstate, and start it after a resume (than any h/w shouldn't have any problem!). PS must take in care to start MP (other small exe) after a resume from hibernate or suspend. After a cold/warm boot it's up to the user to start MP throught "autostart".

regards /gabbe

<blockquote data-quote="gabbe" data-source="post: 6002" data-attributes="member: 10337">Hi fred,Good work. I have some thoughts I want to share. Please make comments about them...I'm not sure PS (PowerScheduler) handling hibernate etc in right way.In my point of view it would be better if it works like this:1/ If the user have done any input (keyboard, mouse) then PS should&nbsp; never suspend/hibernate automaticly. It's up to the user (or windows internal shut down timers) when he wants power off / hibernate / suspend. Many people (at least me) have other tasks ongoing sometimes (server, DC, whatsoever)2/ If PS have waked up the computer for a task, then after the task have completed, PS should put it to the same sleepstate as it was in before. But only if the user don't have done any inputs (keyb, mouse).3/ I think its better to kill MP before going to sleepstate, and start it after a resume (than any h/w shouldn't have any problem!). PS must take in care to start MP (other small exe) after a resume from hibernate or suspend. After a cold/warm boot it's up to the user to start MP throught &quot;autostart&quot;.regards /gabbe</blockquote>

[QUOTE="gabbe, post: 6002, member: 10337"] Hi fred, Good work. I have some thoughts I want to share. Please make comments about them... I'm not sure PS (PowerScheduler) handling hibernate etc in right way. In my point of view it would be better if it works like this: 1/ If the user have done any input (keyboard, mouse) then PS should never suspend/hibernate automaticly. It's up to the user (or windows internal shut down timers) when he wants power off / hibernate / suspend. Many people (at least me) have other tasks ongoing sometimes (server, DC, whatsoever) 2/ If PS have waked up the computer for a task, then after the task have completed, PS should put it to the same sleepstate as it was in before. But only if the user don't have done any inputs (keyb, mouse). 3/ I think its better to kill MP before going to sleepstate, and start it after a resume (than any h/w shouldn't have any problem!). PS must take in care to start MP (other small exe) after a resume from hibernate or suspend. After a cold/warm boot it's up to the user to start MP throught "autostart". regards /gabbe [/QUOTE]