<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
I haven't seen you on the lists in quite a while. I'm still having
problems with some channels with this card in Melbourne, Australia, and
these changes should improve this.<br>
Are you going to get some time to look into this soon? Is there
anything I can do to help? If you give me an overview of the changes
I could try to develop a patch for this.<br>
Patrick Boettcher wrote:
<pre wrap="">Hi all,
I have discussed with the people involved with Hauppauge at DiBcom and
wanted to know the problem.
They explained me, that the actual problem/mistake is the broadcaster:
They are using SFNs (single-frequency network, a DVB-T mux is transmitted
by several, geographically different, transmitters) and each transmitter
has its own cell-id in the TPS. As the channels are the same, the cell-id
should be the same as well.
I have the register settings for the dib3000p and dib7000p (no rev-eng
necessary) which disable some algos to work-around that. However I would
like to make that a module-load option, because here in France and afaik
in Berlin, Germany, the SFNs are OK and disable the algos may cost other
I will try to prepare a patch for that as soon as I can.
On Tue, 10 Apr 2007, Matt Doran wrote:
<pre wrap="">Hi all,
I've been using the Nova-T 500 PCI card and I'm using the Ubuntu 2.6.20
kernel. I and others in Melbourne, Australia have been having reception
problems on a couple of channels. The problem is not related to signal
strength/quality, but region specific. The Windows Media Center community in
Australia were also having the same reception problems (see very long thread
<a class="moz-txt-link-rfc2396E" href="http://www.xpmediacentre.com.au/community/tuners-mce/12244-hauppage-nova-t-500-driver-bug-20.html#post120121"><http://www.xpmediacentre.com.au/community/tuners-mce/12244-hauppage-nova-t-500-driver-bug-20.html#post120121></a>).
This community worked with the Australian distributer (New Magic), who worked
closely with Hauppauge to debug/fix the problem. After a couple of months
they got a fix.
Apparently the problem was with the dib0700 chipset. So this might affect
more than just this card. Here's the quote:
"For those interested the issue actually had nothing to do with
Hauppauge, but rather was a chipset issue which we have identified
in other tuner and set-top products. Because the issue is unique to
only small parts of Australia, many users and manufacturers write
the symptoms off as a reception problem."
The update hasn't been released publicly yet, but is available upon request
from New Magic (see note on this page
<a class="moz-txt-link-rfc2396E" href="http://www.newmagic.com.au/support/Hauppauge_Vista_Drivers.html"><http://www.newmagic.com.au/support/Hauppauge_Vista_Drivers.html></a>). Any one
interested can also email me off list, and I'd be happy to send it through.
The Windows instructions for installing the fix are:
* Install the latest drivers from here:
<a class="moz-txt-link-freetext" href="http://www.newmagic.com.au/support/Hauppauge_Vista_Drivers.html">http://www.newmagic.com.au/support/Hauppauge_Vista_Drivers.html</a>
* Copy the updated file "hcw99bda.sys" into the
C:\windows\system32\drivers into the driver directory.
* Restart the system.
Hopefully this is just a firmware fix, or something easy to reverse engineer.
Anyone know if "hcw99bda.sys" contains firmware? And how to extract it?
Let me know if there is anything I can do to help.
linux-dvb mailing list
<a class="moz-txt-link-abbreviated" href="mailto:email@example.com">firstname.lastname@example.org</a>
<a class="moz-txt-link-freetext" href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb">http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb</a>