Reply to thread

Message

<blockquote data-quote="michael_t" data-source="post: 817338" data-attributes="member: 85139">AW: PowerScheduler++ Test Version 1.2.5.x for MP 1.2.x / 1.3 Alpha@all:I have to make a decision whether to drop the old &quot;PowerScheduler++ forces system to go to standby when idle&quot; option or not.This does mean a lot more than just deleting a checkbox in the config GUI. PS++ can only issue a forced standby, if it has full information about the system state (not only about MP client and server).It has to check for user activity (mouse, keyboard, ...), active shares, running processes and a lot more activities that should prevent standby and that have to be configured properly to get everything working. This makes PS(++) difficult to understand, complicates its configuration and thus might lead to some frustration by users who just want a &quot;plug and play&quot; solution.With PS++ 1.2.5.x I wanted to give up the legacy behavior (inherited by the original PS) that PS can actively send the system to standby (if configured) and rely totally on Windows standby functionality. This would make PS++ easier to understand, because it has to care only for MP internal states, which need no configuration at all (maybe besides EPG grabbing). All the network, process, shares configuration would be unnecessary then. Of course you have to setup your Windows Power Settings properly to enable standby and wakeup, but this will be done automatically by the PS++ configuration. The only thing a user should have to setup is the type of his PC (dektop, HTPC, ...) and the idle timeout. This would be real &quot;plug and play&quot;.But I have learned now that there are (still) some systems that have problems with proper Windows standby, possibly because of some hardware / driver issues. This would of course make it necessary for PS++ to be able to force a system to standby furthermore. So I am torn between continuing the way that I have begun or to leave PS++ as it was. What are your ideas? How could I match both approaches?Michael</blockquote>

[QUOTE="michael_t, post: 817338, member: 85139"] [b]AW: PowerScheduler++ Test Version 1.2.5.x for MP 1.2.x / 1.3 Alpha[/b] @all: I have to make a decision whether to drop the old [I]"PowerScheduler++ forces system to go to standby when idle"[/I] option or not. This does mean a lot more than just deleting a checkbox in the config GUI. PS++ can only issue a forced standby, if it has full information about the system state (not only about MP client and server).It has to check for user activity (mouse, keyboard, ...), active shares, running processes and a lot more activities that should prevent standby and that have to be configured properly to get everything working. This makes PS(++) difficult to understand, complicates its configuration and thus might lead to some frustration by users who just want a "plug and play" solution. With PS++ 1.2.5.x I wanted to give up the legacy behavior (inherited by the original PS) that PS can actively send the system to standby (if configured) and rely totally on Windows standby functionality. This would make PS++ easier to understand, because it has to care only for MP internal states, which need no configuration at all (maybe besides EPG grabbing). All the network, process, shares configuration would be unnecessary then. Of course you have to setup your Windows Power Settings properly to enable standby and wakeup, but this will be done automatically by the PS++ configuration. The only thing a user should have to setup is the type of his PC (dektop, HTPC, ...) and the idle timeout. This would be real "plug and play". But I have learned now that there are (still) some systems that have problems with proper Windows standby, possibly because of some hardware / driver issues. This would of course make it necessary for PS++ to be able to force a system to standby furthermore. So I am torn between continuing the way that I have begun or to leave PS++ as it was. What are your ideas? How could I match both approaches? Michael [/QUOTE]

Verification