home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
PowerScheduler plugin -- Standby before the timing set
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1194208" data-attributes="member: 82144"><p>The PS time setting does not have any effect unless the option for PS to force standby is also enabled.</p><p>In your case, force standby is not enabled so the the PS time-out has no effect.</p><p>[edit: The setting name is "put computer to sleep...". It's no surprise that the setting would have no effect unless you have also configured PS to put the computer to sleep! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> ]</p><p></p><p>So, for your current settings...</p><p>Windows will try to suspend the system after it has been idle for 20 minutes.</p><p>While a remote client is active, PS will prevent Windows automatic suspension.</p><p>When remote client becomes idle, PS will prevent Windows automatic suspension for 2 extra minutes ("grace period").</p><p>If there is no new remote client activity after 2 minutes, PS will allow Windows to suspend the system.</p><p></p><p>If you want PS to prevent Windows from suspending thing system for 20 minutes after the last remote client activity then you must enable the PS force standby option.</p><p><a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle</a></p><p></p><p>Very simple.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1194208, member: 82144"] The PS time setting does not have any effect unless the option for PS to force standby is also enabled. In your case, force standby is not enabled so the the PS time-out has no effect. [edit: The setting name is "put computer to sleep...". It's no surprise that the setting would have no effect unless you have also configured PS to put the computer to sleep! ;) ] So, for your current settings... Windows will try to suspend the system after it has been idle for 20 minutes. While a remote client is active, PS will prevent Windows automatic suspension. When remote client becomes idle, PS will prevent Windows automatic suspension for 2 extra minutes ("grace period"). If there is no new remote client activity after 2 minutes, PS will allow Windows to suspend the system. If you want PS to prevent Windows from suspending thing system for 20 minutes after the last remote client activity then you must enable the PS force standby option. [URL]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle[/URL] Very simple. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
PowerScheduler plugin -- Standby before the timing set
Contact us
RSS
Top
Bottom