Allowed Standby Hours...Please explain this? (1 Viewer)
- Thread starter SciDoctor
- Start date
- Thread starter
- #12
With SVN 19127 this worked fine.
Just installed the latest SVN 19158 last evening and the standby is being blocked for every hour even though the TVSETUP setting is default as 0 -24 .
The service has been stop/started and the pc has been rebooted .
2008-05-24 07:36:17.531250 [21]: PowerScheduler: lastUserTime: 00:40:10.7656 , True
2008-05-24 07:36:17.656250 [21]: PowerScheduler.NextWakeupTime: inspecting handler:GenericWakeupHandler time:31/12/9999 23:59:59
2008-05-24 07:36:18.046875 [21]: PowerScheduler.NextWakeupTime: inspecting handler
cheduledRecordingsHandler time:24/05/2008 11:59:00
2008-05-24 07:36:18.046875 [21]: PowerScheduler.DisAllowShutdown: not allowed hour for standby 7
2008-05-24 07:37:17.532208 [21]: PowerScheduler: Standby allowed until 0 o' clock
It is early in the morniing and my brain may not be working but isn't 0 and 24 actualy the same time (ok technicaly different days) on the clock .Which means the code will block every hour of the 24 hour day
Should the setting be 0 and 23 or 1 and 24 for the code to allow standby for every hour of the 24 hour day.
When changed to 1 - 24 and the service stop/started (needs this to initialize the setting) you do get a correct
2008-05-24 08:13:52.492625 [TVService]: PowerScheduler: Standby allowed until 0 o' clock
2008-05-24 08:13:52.498484 [TVService]: PowerScheduler: Standby allowed starting at 1 o' clock
Just installed the latest SVN 19158 last evening and the standby is being blocked for every hour even though the TVSETUP setting is default as 0 -24 .
The service has been stop/started and the pc has been rebooted .
2008-05-24 07:36:17.531250 [21]: PowerScheduler: lastUserTime: 00:40:10.7656 , True
2008-05-24 07:36:17.656250 [21]: PowerScheduler.NextWakeupTime: inspecting handler:GenericWakeupHandler time:31/12/9999 23:59:59
2008-05-24 07:36:18.046875 [21]: PowerScheduler.NextWakeupTime: inspecting handler
cheduledRecordingsHandler time:24/05/2008 11:59:002008-05-24 07:36:18.046875 [21]: PowerScheduler.DisAllowShutdown: not allowed hour for standby 7
2008-05-24 07:37:17.532208 [21]: PowerScheduler: Standby allowed until 0 o' clock
It is early in the morniing and my brain may not be working but isn't 0 and 24 actualy the same time (ok technicaly different days) on the clock .Which means the code will block every hour of the 24 hour day
Should the setting be 0 and 23 or 1 and 24 for the code to allow standby for every hour of the 24 hour day.
When changed to 1 - 24 and the service stop/started (needs this to initialize the setting) you do get a correct
2008-05-24 08:13:52.492625 [TVService]: PowerScheduler: Standby allowed until 0 o' clock
2008-05-24 08:13:52.498484 [TVService]: PowerScheduler: Standby allowed starting at 1 o' clock
- Thread starter
- #13
It looks like there are three problems.
The default setting is wrong at 0 -24 and the code blocks all hours of the 24 hour clock.
Changes made to the settings aren't saved and/or actioned by powerschedular.
If you stop/start the service in VISTA32 and then return to the PS setting page the changes have reverted . (this worked on previous SVN)
A reboot seems to be the only way to set this PS setting in VISTA 32.
The default setting is wrong at 0 -24 and the code blocks all hours of the 24 hour clock.
Changes made to the settings aren't saved and/or actioned by powerschedular.
If you stop/start the service in VISTA32 and then return to the PS setting page the changes have reverted . (this worked on previous SVN)
A reboot seems to be the only way to set this PS setting in VISTA 32.
Why dont let the tv-server ping the clients and if one or more of them answer, dont let the server go into sleep?
Then you can do other things on the client, I do that on my clients, but with my own program, shouldn't that be a god thing?
I also have a program in my clients that starts the server if its sleeping, the program uses wake on lan feature.
/Juppe
Then you can do other things on the client, I do that on my clients, but with my own program, shouldn't that be a god thing?
I also have a program in my clients that starts the server if its sleeping, the program uses wake on lan feature.
/Juppe
[not bothering with the spec block 'cos it's not a support request]
I like this feature - it's better than having to fire up the setuptv tool and reconfigure powerscheduler if I decide the machine can switch itself off now (it's a single-seat installation, and I use the machine for plenty of other stuff)
It got me at first though, 'cos I'd like to allow standby between 23:00 and 08:00 - I set this to 23 for the first parameter, 8 for the second, and only figured out when I checked the logs that the first parameter has to be lower than the second. A little flexibility there would be useful.
I like this feature - it's better than having to fire up the setuptv tool and reconfigure powerscheduler if I decide the machine can switch itself off now (it's a single-seat installation, and I use the machine for plenty of other stuff)
It got me at first though, 'cos I'd like to allow standby between 23:00 and 08:00 - I set this to 23 for the first parameter, 8 for the second, and only figured out when I checked the logs that the first parameter has to be lower than the second. A little flexibility there would be useful.