<br><br><div><span class="gmail_quote">On 26/11/2007, <b class="gmail_sendername">Mike McKay</b> <<a href="mailto:mike.mckay@dsl.pipex.com">mike.mckay@dsl.pipex.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Mike, Paul,<br>
<br>
Thanks for your replies. It seems that my problems are not due to an
unintentional mis-configuration.<br>
<br>
What I find rather mystifying is that this functionality worked around
18 months ago on version 0.18. At that time I was a completely new to
mythTV. As far as I recollect, I did a transport scan then ran
mythfilldatabase and ended-up with channels that had program data
attached. It wasn't trouble-free by any means and it took quite a few
attempts but the resulting set-up worked with mythfilldatabase until I
recently deleted my channels and transports as described earlier.<br>
<br>
I can think of only two possibilities:<br>
<br>
1. There has been a regression in this area between version 0.18 and
0.20.2 and the functionality no longer works.<br>
<br>
2. There is some completely non-obvious change that it's possible to
make which breaks the functionality, e.g. some set-up parameter or user
selection.<br>
<br>
My current assumption is (for whatever good it might do me) that the
functionality is present but isn't working properly . Do you know of
any related bug reports.<br><span class="sg">
<br>
Mike McKay</span></div></blockquote></div><br>I'm afraid I've only ever used 0.20+ and for the first few months I was using EIT data only as I had no internet connection. <br clear="all"><br>-- <br>Paul Mason