Reply to thread

Message

<blockquote data-quote="pdiaz" data-source="post: 511349" data-attributes="member: 57690">An update,Rebooting doesn't help...I have discovered the solution though. Turns out that Vista defaults to returning to standby after 2 minutes when it has Resumed Automatically - that is with no user input. Hence why my scheduled starting of uTorrent was able to wake the system but Vista was forcing a standby 2 minutes later. Apparently Microsoft introduced this feature after some laptops cooked themselves inside peoples bags when they woke up without user input, I guess PowerScheduler can't override this. There is a Regise try fix see: <a href="http://www.vistax64.com/tutorials/171042-sleep-return-timeout-unattended-wake-up.html" target="_blank">Sleep Return Timeout for Unattended Wake Up - Vista Forums</a>. Setting the value to 0 prevents Vista from forcing the system back into standby and hence uTorrent happily runs away overnight, freeing up PowerScheduler to do its thing.Maybe this registry fix can be included as an option inside PowerScheduler, a checkbox that will modify the registry for users who aren't comfortable modding it directly?</blockquote>

[QUOTE="pdiaz, post: 511349, member: 57690"] An update, Rebooting doesn't help... I have discovered the solution though. Turns out that Vista defaults to returning to standby after 2 minutes when it has Resumed Automatically - that is with no user input. Hence why my scheduled starting of uTorrent was able to wake the system but Vista was forcing a standby 2 minutes later. Apparently Microsoft introduced this feature after some laptops cooked themselves inside peoples bags when they woke up without user input, I guess PowerScheduler can't override this. There is a Regise try fix see: [url=http://www.vistax64.com/tutorials/171042-sleep-return-timeout-unattended-wake-up.html]Sleep Return Timeout for Unattended Wake Up - Vista Forums[/url]. Setting the value to 0 prevents Vista from forcing the system back into standby and hence uTorrent happily runs away overnight, freeing up PowerScheduler to do its thing. Maybe this registry fix can be included as an option inside PowerScheduler, a checkbox that will modify the registry for users who aren't comfortable modding it directly? [/QUOTE]

Verification