Just guessing. But I think that while an undetected driver or tuner may be easily fixable, something related to the DRM maybe next to impossible to fix, i guess that given its purpose the whole thing is buried deeply in the kernel itself and the needed "hooks" maybe removed altogether from it. But knowing the habits of MS, they tend to just disable the access on a first run. See the w7 style start menu on win 8. It was still there. Just not accessible. Then, in win8.1, they removed it completely. Same thing for the older CPU support. The installation of W8/W8.1 is blocked on some older PCs, but a small patch was enough to make them working even on my 2003 Tablet. Seem that the same patch is impossible to get in W10 although it is not more resource demanding than W8.x In short, no matter how the work on RS1 will head, RS2 will be likely hopeless.
For RS1, I think the first 10 lines of the InfiniTV4 device.log make or break it. This is a clip from the 2nd spoiler. [ 2.760000] ctn91xx_register_leon_driver:363 : (0) Driver initialization successful for CTN-9120 v5000 [ 2.770000] ctn91xx_eth_init:450 WARNING: (0) Failed to find greth device [ 2.770000] TCP cubic registered [ 2.770000] NET: Registered protocol family 17 [ 2.770000] leon: power management initialized [ 2.870000] Freeing unused kernel memory: 3172k freed [ 3.730000] ctn91xx_net_set_mac_addr:124 DUMP: "MAC Address" (f10db088) length 6 [ 3.730000] 00000000 00 22 2c 80 49 4b |....IK | [ 4.420000] ctn91xx_interrupt_rpc_recvd:83 : (0) queueing rpc recvd: payload_start: 1 msg_type: 8 [ 4.420000] ctn91xx_interrupt_rpc_recvd:83 : (0) queueing rpc recvd: payload_start: 1 msg_type: 8 redirected stderr *** any clues? When they run this in RS1, we will know more.
Is it a DRM problem though? Shouldn't non DRM channels work regardless of whether DRM is initialized?
I think the problem is initialization of the CC. Of which, DRM is just a part of. There appears to be 10 tests...fail one, you get nothing.
Basically I have no idea. No one has tested what I suggested, I have no way to test nor reports, so... Theorectically shouldn't be only a DRM problem, but given I never used a CC I have no idea about how it's is recognized normally, before the setup wizard and so on. In short I can help just with suggestions, and guesses, nothing more.
With the enhanced WMC logging on RS1, I would like to see the difference between a clean install and with the missing files added back. See if that makes any sort of progress.
I opened a ticket with Ceton about this issue. I left it as, I know it's unsupported and I would 100% understand if you told me "We cant help you" but, asked if there was something in the logs that they might see that could figure out why this is happening. I guess it's a shot in the dark...Not sure anyone over there will help but, MAYBE we'll get a good tech who knows his stuff and takes a little peak and can point us in the right direction. I'll post anything I get back, even if a rejection... Still trying to find my notes on how to enable advanced logging in WMC.... I do have a tool called MCDiag that will pull TONS of info from WMC but, the sad part is the version I have is x86 and errors out on x64....I tried to find a x64 version (MCDiag_x64.msi) but, all links I could find are dead...
Quite some time ago, I heard that someone installed the Ceton drivers, just for the "exceed tuner limit patch". If that was true, the Ceton driver was installed without even having a Ceton. or it was put in and taken out. another if coming up... If the Ceton driver would install in RS1, the Advanced logging would be available in RS1. I havent tried this, and as of yet, I havent seen much in the diagnostics, so far, related to HDHR. other than a few lines in the ehRecvr log. The logger might be customized specifically for Ceton. I would think Silicon Dust must have some way to view the HDHR Device Log, Boot log, or whatever its called. It likely has the same 10 step CC initialization as Ceton. Might have to wait for David to find the CLI logger.
Could you post mcdiag_x86? The test machine I have 14393 on is x86. I tired installing the Ceton software, but the Windows 7 version wouldn't install in compatibility mode and the Windows 8 version is x64 only.
As people realise M$ might have finally made it impossible for Cable card users to use it on Redmond Windows 10, without somehow paying a fee for the right software, which in turns pays M$, I often wonder if people who took up Windows 10 have waken up to that light bulb moment. M$ GOTCHA!!!!!!!!!!!!!!! Its a for-warning of things to come. Windows 10 for free is not going to be free as such.
Heres a thought. If Redmond filters DRM within Wondows 10, and this is near impossible to crack, the dumb question I ask Has anyone tried loading and get working WMC outside Windows 10. That would circumvent the DRM filter . Or am I missing something.
I did use the WMC inside a VM well before we had a workaround to install it on Win 10 (see the first pages of this thread). Then given the RDP patch also using it as a remote app is pretty easy from any OS (including W10, Linux, Android and so on)
I don't think it was that simple, new regulation on communications were bogged down in the political mire of Washington, and rather than wait for a definitive answer on whether cablecard technology was going to have it's FCC protected status beyond 2014, (in my opinion) Microsoft walked away from the whole thing to concentrate on Internet delivery of media which seems to be the way things are going. They had already abandoned a concept they had been working on to develop Windows Media Center as a Home Hub for the "Internet Of Things" which more or less ended any hope of them continuing to develop and support it. I'm not saying they were right to do it, just giving some background as to how we got where we are now.