Originally Posted by robnitro
Any way to disable the rtp and just use normal how it was from a while back? If that was the case, that is.
I can't guarantee that this will address your problem, or that it will actually work to solve your problem when it occurs, but it might.
I had a problem with the Ceton tuners not being returned correctly for normal use following my use of a VPN connection to a remote mainframe from the HTPC. For security, most VPN software products almost always locks out general TCPIP (and always seems to prevent any secure access to the Internet, e.g. for email, etc.). For sure, the two VPN products used in my case have that effect.
Since the Ceton tuners (even from the internal PCIe card) are accessed using IP addresses, when VPN is active the Ceton tuners are inaccessible. But when the VPN connections are closed the Ceton tuners should once again be visible and usable. Except they are not. Other Internet-related software works perfectly again following the termination of VPN, but the Ceton drivers for some reason do not see the tuners. That meant scheduled recordings would encounter "no available tuners" and would get flushed.
Prior to communicating about this with Ceton my only solution at this point was to re-boot the HTPC, which as you can imagine was annoying and inconvenient. I had to remember to re-boot right after terminating my VPN work, so that any scheduled recordings would succeed.
After working with Ceton on several possible solutions, they eventually provided me with what I packaged into two BAT-file commands which I executed sequentially in a command-prompt window. VPN1.BAT kills EHRECVR.EXE (i.e. Windows Media Center task), and I wait about 15-30 seconds for things to "settle down". Then I run VPN2.BAT, which reinitiates the WMC task and also re-discovers all of the Ceton tuners... which are now operating normally again!
This combination of VPN1 and VPN2 thus allows me to avoid having to re-boot following any VPN work, and gets all four tuners operating visibly and properly. Scheduled recordings now proceed without any problem.
So... you might try these two commands yourself, on any machine where your tuners are not behaving correctly or are "dangling" in some inoperative state. There's certainly no harm in running these two commands as I describe (assuming you have a minute or two with nothing else scheduled to be using WMC), and it might very well be a solution to your problem.
Give it a try, and report back whether it was useful... or harmful... or accomplished nothing.