I'm using dvblink as well, since the "stone age" (no IPTV). It works perfectly although i'm using the old 4.1 version.
There was also that user in the Canary Islands with a DVB tuner that couldn't play HBO, although they could play all of the unprotected stuff. That could potentially be related.
1) I had some scripts set up to convert .wtv to .dvr-ms (via WTVConverter.exe), and then to .mpg (via DVRMSToolbox, which can't handle .wtv files AFAIK. I think that's why it's called DVRMSToolbox). 2) I had been trying a utility called DriverMax and it installed the alternate driver which was newer than the Compro driver by a couple of years - it had been working without the scheduled recording errors up until the Anniversary Update, when I switched to v8.6 WMC when V12 wasn't installing for me. (I have deleted DriverMax since then) And finally, I have checked the Protected status - none of my .wtv files are showing as protected. I have other methods to convert .wtv files, but they're so much slower than the scripts I was using. Has anybody else tried using WTVConverter, and have they had the same error message?
It's not me the one to blame, it's another Italian (Cristoforo Colombo). W/o him there were no Americans in troubles
It's not me the one to blame, it's another Italian (Cristoforo Colombo). W/o him there were no Americans in troubles Hey less slap and tickle and more working on HDHomeRun Prime Cable Card
Before Colombo got here, we were quite happy travelling around the continent with birch bark canoes. 1492 was the beginning of the end.
I had problems with WMC v12 installation, error code 0x800f0922. Does anyone know a fix for this error? If not, where can I dwnld 8.6?
I swear to god, last time I used it, (it has been awhile + it was on Win7) all I did was navigate to a WTV file and hit Convert. Today though, it appears to need a little work.
Got it in one, just a simple DVT tuner is all we have to use and get up and running. So version 12 WMC works fine with Redmond Windows 10. Done three machines now, no problems.
oh, those finding Redmond and WMC upgrade and they lose their tuner, well Redmond may install an inappropriate driver during the upgrade. You need to roll back the driver to the previous one, and then stop Redmond Windows 10 from automatically changing it again. That's the only problem I have encountered, BUT easily fixed. Same goes for a clean install, before you do it, keep the old driver somewhere, and after the install, replace, and again stop Windows 10 from changing it.
Driver for what? The tuner? I saw that the upgrade did remove the old driver for HDHomerun but reinstalling it made no difference