<div class="gmail_quote">On 19 May 2011 22:15, Fluf <span dir="ltr"><<a href="mailto:fluffkinuk@yahoo.co.uk">fluffkinuk@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Probably time to delete it all again and see if starting at the big numbers and going down works better than going from the little numbers up. But it is being a real PITA for something that should be pretty easy.<br>
</blockquote></div><br>Some .. sort of progress!<br>(I hope!).<br>Did a Full Scan (Tuned) of 842Mhz and it found 2 of the correct other frequencies for a change.<br>But this time, no 5* / 5USA etc.<br>So do a Full Scan (Tuned) of 802MHz and ...<br>
It finds lots of stuff, but then forgets about it all because I said ignore duplicates.<br>So do it again.<br>Hit "Suggest" "Update" about 100 times and this time it does remember where it found them.<br>
Now I have (for the first time!) ... the correct minimal 5 frequencies, detected by and generated by myth, so they should work ..<br>I'm hoping a simple "Delete all channels" and one last scan of existing transports might just give me a complete working list.<br>
<br>Phew!<br><br>I think it worked!<br><br>O.o<br><br>Srsly guys ... that's not a simple setup procedure ... For one thing, I'd be stuck with half my channels breaking up if I let it do it's thing. I liked the import channels.conf cake particularly. It took at least a day to figure out why EIT wasn't working. Anyway .. onwards and sideways!<br>