can it be hex edit or extracted and placed in correct folder just guessing not a clue what iam talking about
Would this section of 10586 give us a better picture of "What is supposed to happen"? Code: C:\Program Files\Microsoft\DigitalCableAdvisor\Registration.xml Here are the contents of the file: Code: <?xml version="1.0"?> -<application title="DigitalCableAdvisor" id="{5e9e46fd-547d-4c3c-a126-29137e648e4d}"> -<entrypoint title="Digital Cable Advisor" id="{25964053-235e-4eeb-b099-c633aa43add0}" AcceptWebInvoke="True" ImageUrl=".\Application.png" description="Analyze and update your system for digital CableCARD™ tuners" addin="DigitalCableAdvisor.MyAddIn, DigitalCableAdvisor,Culture=Neutral,Version=1.0.0.0,PublicKeyToken=31bf3856ad364e35"> <category category="More Programs"/> </entrypoint> </application> BTW, I was trying a new installation on a different 10586, and while watching the HDHR progress indicator in HdHomeRun/Config, the progress indicator appeared to be getting more done than the progress indicator in 14393 (this sentence should be posted after the picture)
The host and the guest VM both see the InfiniTV as local, with the default 192.168.200.1 IP. I've been afraid to try network bridging it with Ceton's plug-in for that with how much difficulty I had getting things back to normal last time.
I don't know if this has been asked, but I cannot add an XBOX360 extender to connect to my Media Center. It looks like there might be some files missing. Please help
I think seeing the tuner's as local is a good thing. I'm not messing with Network Tuners ever again. I was suggesting that you Enable Advanced Logging in the Ceton Diagnostic Tool, boot and logging starts. Since your InfiniTV is local, you will get the logs for 192.168.200.1 and also 192.168.180.1 as well as a bunch of other stuff. Spoiler Directory of C:\Win10Project\Documents\CetonDiagnostics\CetonInfiniTVDiagnostic_M4A78PRO_20160805_13-59 08/06/2016 03:12 AM <DIR> . 08/06/2016 03:12 AM <DIR> .. 08/05/2016 01:59 PM 50 antispyware_product.txt 08/05/2016 01:59 PM 32 antivirus_product.txt 08/05/2016 01:59 PM 77,150 Ceton-Diag.log 08/05/2016 01:58 PM 114 ceton_diag_fields.txt 08/06/2016 03:12 AM <DIR> Ceton_InfiniTV_PCIe_(00-80-49-4b) 08/05/2016 01:59 PM 268 ceton_versions.txt 08/06/2016 03:12 AM <DIR> DCA_Logs 08/05/2016 01:58 PM 26,455 dxdiag.txt 08/06/2016 03:12 AM <DIR> ehRecvr_Logs 08/06/2016 03:12 AM <DIR> Event_Logs 08/05/2016 01:59 PM 113,709 hardwareList.txt 08/05/2016 01:59 PM 82,259 installed_applications.txt 08/05/2016 01:59 PM 3,596 ipconfig.txt 08/05/2016 01:59 PM 4 num_infinitvs_found.txt 08/05/2016 01:59 PM 229 ping_192.168.180.1.txt 08/05/2016 01:59 PM 452 ping_192.168.200.1.txt 08/05/2016 01:59 PM 17,561 process_list.txt 08/05/2016 01:59 PM 4,964 reg_ehprivjob.txt 08/05/2016 01:59 PM 15,656 reg_network_adapter.txt 08/05/2016 01:59 PM 2,868 reg_network_client.txt 08/05/2016 01:59 PM 6,792 reg_power.txt 08/05/2016 01:59 PM 128,962 reg_tuners.txt 08/05/2016 01:59 PM 310 reg_weaksignaldroppedthreshold.txt 08/05/2016 01:59 PM 176,375 services.txt 08/05/2016 01:59 PM 57 support_bridging.txt 08/05/2016 01:59 PM 10,784 system_info.txt 08/05/2016 01:59 PM 76 system_up_time.txt 08/05/2016 01:59 PM 24 timezone.txt 08/05/2016 01:59 PM 33 troubleshootingFlags.txt 08/05/2016 01:59 PM 3,354 windows_activated.txt 08/05/2016 01:59 PM 2,390 windows_version.txt 08/05/2016 01:59 PM 1,430 winsat_query.txt 28 File(s) 675,954 bytes 6 Dir(s) 391,084,191,744 bytes free C:\Win10Project\Documents\CetonDiagnostics\CetonInfiniTVDiagnostic_M4A78PRO_20160805_13-59>
I just wanted to thank everyone for all the hard work and tips... I ended up having to do multiple reinstall and cleanups to get my Hauppage PCIE tuners detected. It finally worked when I uninstalled everything (including the Hauppage drivers).... Ran CC cleaner... reboot... uninstalled with 8.8.1 package... installed DCA, Installed Playready, rebooted.... ran CC Cleaner... rebooted... Installed 8.8 (then applied the reg edit).. Went in and it saw the tuners and is all happy again.. Thanks againg... 10 with anniversary and WMC all working fine...
Please don't do that. The files are hosted on datafile host for a reason. It has a counter and I want to know ho much downloads are taking place. Regard the compression format the whole 7zip + the the 7zip package are smaller than than the zipped file alone. No need to rely on formats from the '80s.
crash2009 if you can get CableCards working again I will happily buy you a #MichiganBeer in person if you are in the SE Michigan area.
The same ^^ is valid for you. Also reposting a long superseded version is just matte od confusion for the newbies.
What problematic link? Any hosting service is "problematic". The smaller cyberlockers because the aggressive ADs, the services offered from the big brothers, because the privacy. Datafilehost is a good compromise. It's clean enough for everyone is able to browse the web using something ore than a single neuron, is fast and easy to use. The mirror was temporarily offered because the v8.8.1 was released at the same time they had a major website overhaul. That's all
Wow, You are pretty close. I'm almost exactly midpoint between Liberty Street Brewing Company and Canton Brew Works.
New finding that I guarantee that others will need to follow. Take note. On 14393, Windows\system32 does not contain msdri.dll, despite all the other msdri files being installed and present in system32, WinSxS, etc.. You can copy over msdri.dll from 10586 into Windows\system32 and register the dll using regsvr32 (from administrative command prompt, "regsvr32 c:\windows\system32\msdri.dll"). If you do not do this before installing HDHomeRun and running HDHomeRun Setup, the installation will run, you will not see any errors, and the HDHomeRun View app will work. However, essentially all the registry entries needed for the HDHomeRun tuners to be recognized in WMC will not be set up (e.g., HKLM\Software\Classes\CLSID\[GUIDs]). Only the entries under HKLM\Software\SiliconDust will be created. Created keys (not a full list): HKLM\SOFTWARE\Classes\CLSID\{71985F48-1CA1-11D3-9CC8-00C04F7971E0} HKLM\SOFTWARE\Classes\CLSID\{71985F48-1CA1-11D3-9CC8-00C04F7971E0}\Instance (includes 1 GUID subkey and many subentries for every tuner, will vary by tuner) HKLM\SOFTWARE\Classes\CLSID\{ED34623A-4E73-401B-B16A-21771F14BE2B} HKLM\SOFTWARE\Classes\CLSID\{ED34623A-4E73-401B-B16A-21771F14BE2B}\Instance (includes 1 GUID subkey and many subentries for every tuner, will vary by tuner) HKLM\SOFTWARE\Classes\CLSID\{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0} HKLM\SOFTWARE\Classes\CLSID\{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Instance (includes 1 GUID subkey and many subentries for every tuner, will vary by tuner) HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\Video\Tuners\{71985F48-1CA1-11D3-9CC8-00C04F7971E0} (many subkeys and subentries for every tuner) I think running HDHomeRun Setup and clicking over to the last tab ("Advanced") can tell if you have the problem or not because the Windows Media Center background channel scan option box will not be displayed. I was checking registry entries at the time and not paying attention to UI behavior as much. Install msdri.dll, run HDHomeRun Setup, click over to the Advanced tab, the Windows Media Center background channel scan option box should now be visible, click APPLY, and the registry entries will be created in full. Still not sufficient to get things running, but apparently a necessary step. Now I need to combine that with WMDRM.