2020-12-24, 10:21 AM
Hello,
Got an unusual one. I finally completely moved machine from an old Win 7 based one to a brand new Win 10 one (all new hardware). I went from a Hauppauge Nova-T Dual Tuner to a Hauppauge quadHD. Mostly everything working as I expect.
The one big difference is the Windows screensaver. I use the system screensaver as the PC also gets used for browser stuff (Youtube etc) and it's a plasma TV, so seems sensible to have a system screensaver. In other words, I can't rely on the NextPVR native screensaver.
On my old machine (Win 7), the Hauppauge IR.exe calls NextPVR. If the system screensaver was on, the Hauppauge IR.exe call to NextPVR seemed to clear the screensaver.
On Win 10, if I launch the screensaver as a preview or from it's *.scr file, then the above behaviour works entirely as expected. However, if the system launches the screensaver (because it has been idle), then IR.exe won't close it. It is still able to call and execute commands, but they all appear behind the screensaver.
As a workaround, I've used 'pskill' and mapped it to a button to kill the screensaver, and this works. It seems rather inelegant though. Killing the process seems a brute force method. I am guessing the issue must be one of privileges or permissions, that when the system launches the screensaver it is elevated. Maybe not. I'm not sure!
Just wondering if this has been encountered before? Any thoughts appreciated.
Thank you
Got an unusual one. I finally completely moved machine from an old Win 7 based one to a brand new Win 10 one (all new hardware). I went from a Hauppauge Nova-T Dual Tuner to a Hauppauge quadHD. Mostly everything working as I expect.
The one big difference is the Windows screensaver. I use the system screensaver as the PC also gets used for browser stuff (Youtube etc) and it's a plasma TV, so seems sensible to have a system screensaver. In other words, I can't rely on the NextPVR native screensaver.
On my old machine (Win 7), the Hauppauge IR.exe calls NextPVR. If the system screensaver was on, the Hauppauge IR.exe call to NextPVR seemed to clear the screensaver.
On Win 10, if I launch the screensaver as a preview or from it's *.scr file, then the above behaviour works entirely as expected. However, if the system launches the screensaver (because it has been idle), then IR.exe won't close it. It is still able to call and execute commands, but they all appear behind the screensaver.
As a workaround, I've used 'pskill' and mapped it to a button to kill the screensaver, and this works. It seems rather inelegant though. Killing the process seems a brute force method. I am guessing the issue must be one of privileges or permissions, that when the system launches the screensaver it is elevated. Maybe not. I'm not sure!
Just wondering if this has been encountered before? Any thoughts appreciated.
Thank you
"It's better than a box!"