No wonder no channels showed up! Microsoft’s DirectX team has confirmed that the updated file is causing problems with PAL TV tuner cards. This little file was updated to version 5.3.1.902 through DirectX 9.0b, and is described as a ‘WDM Streaming TVTuner’ it is a DirectShow Filter responsible for tuning into the different channels the card can receive. Each time around, the good Doc fingered the kstvtune.ax file in the %windir%\System32 directory. The next time the TV tuner application crashed, I could wade through the information in the log file created by Dr Watson. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug\Auto I told Windows XP Professional to run the built-in debugger, Dr Watson (drwtsn32.exe) (see FIGURE 1), automatically, by firing up regedit and changing the following Registry entry to 1 (one) (see FIGURE 2): As DirectX 9.0b contains performance and security enhancements, it seems like a good thing to have, so I decided to pinpoint the cause of the problem. I discovered that OS installations updated up to DirectX 9.0a worked fine with the card, but beyond that, no go. It was one of those frustrating problems that took a long time and lots of effort to solve, because Windows doesn’t give you any hints as to what’s going wrong: is it the driver for the TV tuner, the video card, or some other part of the operating system that has indigestion?Įventually, I traced it down to Microsoft’s DirectX 9.0b update by trying out the card in different Windows XP Professional installations with and without the patch. Not only did the card not work, but Windows Movie Maker hung, as well. However, despite installing the card correctly and ensuring that there were no hardware conflicts, nothing could be seen or heard. I was recently asked to review a TV capture card with onboard tuner, a task that seemed easy enough.
0 kommentar(er)
