Reply to thread

Message

AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)

@sfang

From Microsoft "Away Mode in Windows Vista":

Thank you for the hint. I didn't realize that before, since I am using hybrid sleep mode for my PC. I will add this information to the PowerScheduler++ documentation.

@Wbunaarf

Hi Johannes,

Yes, I think this would be the best way to narrow down the error.Yes, these are the 1.2.0.10 files, so the error must be somewhere else.
I also thought about changing this, but then I realized that the system idle timeout is retriggered at the end of a recording (by the last call to SetThreadExecutionState(SYSTEM_REQUIRED) from Scheduler.cs), which I cannot change. So I decided to let PowerScheduler behave identically, so that system idle timeout and standby forced by PS++ happen (nearly) at the same time.

Michael

@romadd64

Hi romadd,

PowerScheduler triggers the external command by the SUSPEND and RESUMEAUTOMATIC / RESUMECRITICAL power events. The advantage of this solution is, that the command is triggered on each suspend / wakeup, not only when caused by PS. But since there are no power events for shutdown or boot, the command cannot be triggered in these situations.

Michael

<blockquote data-quote="michael_t" data-source="post: 716481" data-attributes="member: 85139">AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)@sfangFrom Microsoft &quot;Away Mode in Windows Vista&quot;: Thank you for the hint. I didn't realize that before, since I am using hybrid sleep mode for my PC. I will add this information to the PowerScheduler++ documentation.@WbunaarfHi Johannes,Yes, I think this would be the best way to narrow down the error.Yes, these are the 1.2.0.10 files, so the error must be somewhere else. I also thought about changing this, but then I realized that the system idle timeout is retriggered at the end of a recording (by the last call to SetThreadExecutionState(SYSTEM_REQUIRED) from Scheduler.cs), which I cannot change. So I decided to let PowerScheduler behave identically, so that system idle timeout and standby forced by PS++ happen (nearly) at the same time.Michael@romadd64Hi romadd,PowerScheduler triggers the external command by the SUSPEND and RESUMEAUTOMATIC / RESUMECRITICAL power events. The advantage of this solution is, that the command is triggered on each suspend / wakeup, not only when caused by PS. But since there are no power events for shutdown or boot, the command cannot be triggered in these situations. Michael</blockquote>

[QUOTE="michael_t, post: 716481, member: 85139"] [b]AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)[/b] @sfang From Microsoft "Away Mode in Windows Vista": Thank you for the hint. I didn't realize that before, since I am using hybrid sleep mode for my PC. I will add this information to the PowerScheduler++ documentation. @Wbunaarf Hi Johannes, Yes, I think this would be the best way to narrow down the error.Yes, these are the 1.2.0.10 files, so the error must be somewhere else. I also thought about changing this, but then I realized that the system idle timeout is retriggered at the end of a recording (by the last call to SetThreadExecutionState(SYSTEM_REQUIRED) from Scheduler.cs), which I cannot change. So I decided to let PowerScheduler behave identically, so that system idle timeout and standby forced by PS++ happen (nearly) at the same time. Michael @romadd64 Hi romadd, PowerScheduler triggers the external command by the SUSPEND and RESUMEAUTOMATIC / RESUMECRITICAL power events. The advantage of this solution is, that the command is triggered on each suspend / wakeup, not only when caused by PS. But since there are no power events for shutdown or boot, the command cannot be triggered in these situations. Michael [/QUOTE]