Issues with ATI HDTV Wonder on Windows 10 (1 Viewer)

[mm1352000]

Please answer my previous question:

Would I be right to assume you're using the tuner in the same USB port/connector as you used with W7?

If the answer to the above question is "yes": have you tried plugging the tuner into a USB port which is backed by a different controller?
...a different controller which is not a USB 3 controller?
Also, have you checked the USB controller drivers?

Like I said previously, I'm not able to help you with MP2. The TV engines are not 100% identical so there is a [small] chance the tuner will work with MP1. More to the point: I can supply patches for MP1 where I cannot for MP2.

 

[Gregory Bartels]

It's a PCI card, and there's only one slot for it on my motherboard (and thus, no USB). I'll check the chipset drivers- I think I'm using the ones from Windows Update, but I'll install the ones from from my motherboard manufactuer to see if that helps (which might be the same). What's odd is that I can boot into windows 7 and use MP2 to get channels, but when I boot into Windows 10, I don't get channels (and there I was using Windows Update's chipset drivers). I'll try the chipset drivers and MP1 again, see if those help.

 

[Gregory Bartels]

Tried MP1 after re-installing the chipset drivers from motherboard mfg site, and got similar results (that is, not working). I've attached the tv_server log if you want to look at it. Scanning still returns signal locked, no channels found, and import isn't able to tune into channels either.

 

[mm1352000]

It looks like the tuner is very close to working.

Please ensure "when card enters idle state..." is set to "stop card" and scan again:
http://wiki.team-mediaportal.com/1_...nfiguration/02_TV_Servers#Edit_Tuner_Settings

The log files show you scanning with the setting set to "pause card". Pause can cause problems for certain tuners. If that doesn't help, please also try the ATSC network provider [again] because it is more compatible with older tuners.
To be clear: "stop card" + "ATSC" is the most compatible configuration.

 

[Gregory Bartels]

I went ahead and checked the settings and they were set to stop-generic. I tested at stop-atsc with no channels. Then, thinking it might be confused with my imported channels/settings, I deleted the channels, scanned at pause-atsc, then at pause-generic, then stop-generic. To be extra sure, I re-ran stop-atsc. All 5 times 0 channels found. Attached are all the logs.

1 - stop,atsc (channels mapped)
2 - pause,atsc (after channels deleted)
3 - pause,generic
4 - stop,generic
5 - stop,atsc

 

[mm1352000]

Hmmm, that's so weird. It looks like the tuner is responding to the tune requests because it reports signal lock correctly. However it seems that the tuner simply isn't delivering a stream for TV Server to work with. I've seen similar symptoms several times in the past with other tuners, and if I recall correctly the problems were always caused by one of:

• network provider setting
• idle state setting
• driver issues (generic Windows update driver installed)
• other software using the tuner

I'd supply a patch if I could think of anything that we could tweak that might help the tuner work, but at this point there's nothing I can think of.

 

[Gregory Bartels]

Looking into the driver version, I vaguely remembered that I had seen on the BDA driver a version number of 10 on Windows 10 (specifically, 10.0.10240). So I decided to compare the files listed and here's what I found out.

Windows 10:
atiddcxx.sys (ATI version 3.0.83.2036)
BdaSup.sys (Microsoft version 10.0.10240.16384)
ksthunk.sys (Microsoft version 10.0.10240.16384)

Windows 7
atiddcxx.sys (Ati version 3.0.83.2036)
BdaSup.sys (Microsoft version 6.1.7600.16385)
ksthunk.sys (Microsoft version 6.1.7600.16385)

Looks like Windows 10 updated the BdaSup and the ksthunk versions, and from what it seems like, they're no longer compatible with the ATI HDTV tuner. Not too sure how I can force Windows to use older versions of those files, but I have an idea on how to. I'll give it a shot and see if it works.

Edit: doesn't work. I could only overwrite the bdasup.sys file but not the ksthunk.sys one. Seems my problem is indeed a driver one, but one that can't be resolved due to using some of Microsoft's drivers.[DOUBLEPOST=1446871560][/DOUBLEPOST]Just another clarification, the atiddcxx was under the BDA Capture Device, while the Digital and Analog Tuner Device is listed as atidtuxx.sys. Not sure if BDA capture is the same as HD tuner, but it is the same driver version (3.0.83.2036).

 

[mm1352000]

Yeah, BdaSup and ksthunk are part of the Windows frameworks for tuner support (BDA, DirectShow). I strongly recommend that you do not attempt to modify them.

 

[Gregory Bartels]

Yeah, I made backups of the Windows 10 ones before I did anything and reverted it back once it didn't work (and MS only allowed me to modify the bdasup.sys one anyway). Since this appears to be a driver issue, I suppose this means that the card is not supported for Windows 10?

 

[mm1352000]

If you're feeling adventurous, you may be able to replace ksthunk.sys when you've booted into your W7 partition (or otherwise via Windows safe mode, a Linux live CD etc.). Aside from that, it does appear like the card is not going to work in W10.