Reply to thread

Message

<blockquote data-quote="LosWochos" data-source="post: 828629" data-attributes="member: 101015">AW: PowerScheduler++ 1.2.2.0 - Stable version for MediaPortal 1.2.xHi and a happy new year!on my installation, the Powerscheduler++ seems to stop working after some time (around 3-4 days, but it could also depends on the number of standby/wakeup cycles). My system is configured to wake up for Mediaportal recordings and EPG grabbing, as well as for backup tasks through Windows Scheduler. This usually works fine for several days and standby/wakeup cycles, regardless of who triggered the sleep or wakeup (User through power button, Powerscheduler++, Windows Scheduler) until at some point Powerscheduler++ does not send the PC back to sleep.With extensive Logging activated, I noticed that at some point the [Powerscheduler Timer] events stop appearing in the log. You can see this in the attached log files, where the old .bak-logfile contains [Powerscheduler Timer] lines until the shutdown on 2. Jan and the .log-file starting on the evening of 3. Jan does not contain any of them until I restarted the system today (4. Jan at 12:31). If you need any more infomation please contact me.Regards,StefanPS: The process &quot;MPNoStandby&quot; that prevents standby in the logs is a self-written program with empty event loop (only reacts on WM_DESTROY) that is launched by Windows Scheduler on user login and killed on logout. It prevents automatic standby while the user is active. This is my solution to the problem that Powerscheduler++ sends the PC to sleep even when a user is sitting in front of it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="LosWochos, post: 828629, member: 101015"] [b]AW: PowerScheduler++ 1.2.2.0 - Stable version for MediaPortal 1.2.x[/b] Hi and a happy new year! on my installation, the Powerscheduler++ seems to stop working after some time (around 3-4 days, but it could also depends on the number of standby/wakeup cycles). My system is configured to wake up for Mediaportal recordings and EPG grabbing, as well as for backup tasks through Windows Scheduler. This usually works fine for several days and standby/wakeup cycles, regardless of who triggered the sleep or wakeup (User through power button, Powerscheduler++, Windows Scheduler) until at some point Powerscheduler++ does not send the PC back to sleep. With extensive Logging activated, I noticed that at some point the [Powerscheduler Timer] events stop appearing in the log. You can see this in the attached log files, where the old .bak-logfile contains [Powerscheduler Timer] lines until the shutdown on 2. Jan and the .log-file starting on the evening of 3. Jan does not contain any of them until I restarted the system today (4. Jan at 12:31). If you need any more infomation please contact me. Regards, Stefan PS: The process "MPNoStandby" that prevents standby in the logs is a self-written program with empty event loop (only reacts on WM_DESTROY) that is launched by Windows Scheduler on user login and killed on logout. It prevents automatic standby while the user is active. This is my solution to the problem that Powerscheduler++ sends the PC to sleep even when a user is sitting in front of it :) [/QUOTE]

Verification