Normal
Re: [New Plugin] PowerScheduler++ (New Version 1.1.1.5)I can confirm this.With 'as expected', do you mean that it should suspend when the client is no longer active (without using windows power management) or that away mode is now used here as well? If you meant the first case, it unfortunately still isn't working here (please see attached logs showing the server being restarted, the client being restarted, TV being watched on the client, the client suspended from within MP and finally the server staying awake). If you meant the second case - Nice, if only... I must admit that I haven't had windows managing power save for a very long time. It didn't use to work very well (a few years ago when I first set the system up using Vista), but perhaps it's better now in Windows 7. However, considering these machines being dedicated HTPCs makes me somewhat reluctant having windows meddling with power save. One particular reason not using it is that unless MP is running and idle I don't want the machine to suspend. Why? Because this means that I'm doing some work on it. Either directly on it or remotely using remote desktop or just shared folders. This leads to a small feature request: Would it be possible to add the feature to only allow sleep if the mp gui is running? As it is, with the frontend shut down I need to start one of the configuration tools to prevent suspend.I'm not a programmer, but I had a look at the source code and Microsofts documentation (Away Mode in Windows Vista). Is the following correctly understood?When a recording is started you issue a 'SetThreadExecutionState(ES_CONTINUOUS | ES_SYSTEM_REQUIRED | ES_AWAYMODE_REQUIRED);' telling the system to enable away mode.When the recording is finished, you issue a 'SetThreadExecutionState(ES_CONTINUOUS);' telling the system that it's now ok to suspend again.If the power button isn't pressed during the recording the away mode isn't actually entered, and thus ps(++) should be able to suspend afterwards?If the power button is pressed during the recording, the away mode is activated. In this case, ps++ isn't able to suspend the system for some reason. Pressing a key (or somehow simulating it in code) exits away mode, and ps(++) should again be able to suspend the system?Would it make a difference using the newer functions in Power Availability Requests ?//Johannes
Re: [New Plugin] PowerScheduler++ (New Version 1.1.1.5)
I can confirm this.
With 'as expected', do you mean that it should suspend when the client is no longer active (without using windows power management) or that away mode is now used here as well? If you meant the first case, it unfortunately still isn't working here (please see attached logs showing the server being restarted, the client being restarted, TV being watched on the client, the client suspended from within MP and finally the server staying awake). If you meant the second case - Nice, if only...
I must admit that I haven't had windows managing power save for a very long time. It didn't use to work very well (a few years ago when I first set the system up using Vista), but perhaps it's better now in Windows 7. However, considering these machines being dedicated HTPCs makes me somewhat reluctant having windows meddling with power save. One particular reason not using it is that unless MP is running and idle I don't want the machine to suspend. Why? Because this means that I'm doing some work on it. Either directly on it or remotely using remote desktop or just shared folders. This leads to a small feature request: Would it be possible to add the feature to only allow sleep if the mp gui is running? As it is, with the frontend shut down I need to start one of the configuration tools to prevent suspend.
I'm not a programmer, but I had a look at the source code and Microsofts documentation (Away Mode in Windows Vista). Is the following correctly understood?
When a recording is started you issue a 'SetThreadExecutionState(ES_CONTINUOUS | ES_SYSTEM_REQUIRED | ES_AWAYMODE_REQUIRED);' telling the system to enable away mode.
When the recording is finished, you issue a 'SetThreadExecutionState(ES_CONTINUOUS);' telling the system that it's now ok to suspend again.
If the power button isn't pressed during the recording the away mode isn't actually entered, and thus ps(++) should be able to suspend afterwards?
If the power button is pressed during the recording, the away mode is activated. In this case, ps++ isn't able to suspend the system for some reason. Pressing a key (or somehow simulating it in code) exits away mode, and ps(++) should again be able to suspend the system?
Would it make a difference using the newer functions in Power Availability Requests ?
//Johannes