Reply to thread

Message

<blockquote data-quote="jbagh" data-source="post: 1232092" data-attributes="member: 64252">Message back from Support to you:Hello,unfortunately we did not know so far about that problem, as we ship the TT-Viewer along with our products.The driver was indeed issued and signed by DVBSKy, which is the developer of the hardware and drivers.We don't know why this device shows up in Mediaportal, as the driver only creates one entry in device managercalled &quot;TechnoTrend Connect S2-4650&quot;. Maybe it's an issue about the BDA implementation in Mediaportal, asthe Vendor-ID seems to be indentical to DVBSky, nevertheless the SUB-ID is connected to CityCom /Technotrend.We did not experience that problem with DVBViewer Pro, too. So we can only recommend that maybe Mediaportalis checking their BDA implementation for that device and either rename it or split it into 2 existing devices, one toDVBSky, the other one to TechnoTrend.</blockquote>

[QUOTE="jbagh, post: 1232092, member: 64252"] Message back from Support to you: Hello, unfortunately we did not know so far about that problem, as we ship the TT-Viewer along with our products. The driver was indeed issued and signed by DVBSKy, which is the developer of the hardware and drivers. We don't know why this device shows up in Mediaportal, as the driver only creates one entry in device manager called "TechnoTrend Connect S2-4650". Maybe it's an issue about the BDA implementation in Mediaportal, as the Vendor-ID seems to be indentical to DVBSky, nevertheless the SUB-ID is connected to CityCom /Technotrend. We did not experience that problem with DVBViewer Pro, too. So we can only recommend that maybe Mediaportal is checking their BDA implementation for that device and either rename it or split it into 2 existing devices, one to DVBSky, the other one to TechnoTrend. [/QUOTE]

Verification