Yet another locals question.

[chhamilton]

I'm not normally one to ask questions, but I've gotten to the point of complete frustration on this issue, which has been discussed here many times before: TO BE ANNOUNCED.

I'm running a T60 with software version 2.5-01. I'm able to receive the Seattle and Portland spotbeams. When I originally hacked my Tivo, I was set up (back in the old days of H emu, a topic I know is not discussed here) to receive Seattle locals, which I have always received without any problem.

As soon as I try to add the Portland locals, I get TBA for ever. I tried mvch136 first, but after a couple weeks, that lost the guide data for my Seattle locals as well. I then did a Season Pass/Guide Data restart, and tried using mvch136 again; same result. Another reset, and tried using mvch135. The result was guide data as normal for Seattle locals, TBA forever on the Portland channels. I've also tried changing emu zip-codes/guide bytes etc to receive Portland locals. Through everything, I've been able to retain my SE locals, but never get guide data for the PO ones.

I have not yet tried selectlocals or xplusz. Are either of these recommended, and known to work for my configuration?

Is there a concrete solution to this problem? Something that is repeatable, and has worked for many others? I've read every thread in this forum regarding: TBA, spot beams, locals, etc.., and found nothing conclusive or concrete.

Perhaps we can finally put this issue to rest for good.

[genericuser]

Firstly, mvchannels 1.3.6 is for 2.5.2... You need to use 135.

You need to STOP mvchannels from running (comment it out of the rc.sysint or comment it out of cron). Then reboot. Now run mvchannels.tcl reset (version 1.3.5). Then reboot.

You should now have absolutely NO locals listed in the guide.

Now you need to (one at a time), get a set of locals you can receive into the guide. Seems like you have 2 sets of locals you want (Seattle, Portland).

1) Somehow get a set of those locals to come in. The manner in which I am talking is not discussed here. You will have to go to a board that discusses DirecTV hacking if you dont understand what I am saying.

2) Once guide data for that set of locals appears (could take up to 24 hours), reboot and let the system simmer for at least 15 minutes.

3) Now change to the OTHER set of locals. Go to set #1. Get the guide data for that set of locals. Your first set will dissapeer, but do not worry, everything will work out.

4) Now that you have guide data for both sets of locals, run mvchannels 1.3.5:

./mvchannels.tcl dumpall

That creates the channels.dat file. Edit the file and remove ALL the lines that are not associated with the locals you want to receive.

Now:

./mvchannels.tcl

That should move things around and enable both sets of locals and you should have guide data for them.

If all that works, then you need to set up mvchannels to run in a loop if you want to move channels from their natural 2-99 positions to somewhere else (or if you want to hide channels).

Let me know how that works. That is the exact process I used on my t-60 when I was running 2.5

[boboli]

Originally posted by genericuser
Firstly, mvchannels 1.3.6 is for 2.5.2... You need to use 135.

You need to STOP mvchannels from running (comment it out of the rc.sysint or comment it out of cron). Then reboot. Now run mvchannels.tcl reset (version 1.3.5). Then reboot.

You should now have absolutely NO locals listed in the guide.

Now you need to (one at a time), get a set of locals you can receive into the guide. Seems like you have 2 sets of locals you want (Seattle, Portland).

1) Somehow get a set of those locals to come in. The manner in which I am talking is not discussed here. You will have to go to a board that discusses DirecTV hacking if you dont understand what I am saying.

2) Once guide data for that set of locals appears (could take up to 24 hours), reboot and let the system simmer for at least 15 minutes.

3) Now change to the OTHER set of locals. Go to set #1. Get the guide data for that set of locals. Your first set will dissapeer, but do not worry, everything will work out.

4) Now that you have guide data for both sets of locals, run mvchannels 1.3.5:

./mvchannels.tcl dumpall

That creates the channels.dat file. Edit the file and remove ALL the lines that are not associated with the locals you want to receive.

Now:

./mvchannels.tcl

That should move things around and enable both sets of locals and you should have guide data for them.

If all that works, then you need to set up mvchannels to run in a loop if you want to move channels from their natural 2-99 positions to somewhere else (or if you want to hide channels).

Let me know how that works. That is the exact process I used on my t-60 when I was running 2.5

Thank you for the step-by-step.
However, I have this problem. When I try to run './mvchannels.tcl reset' I get this error:

<166>Jan 30 23:29:10 tcl[320]: Tcl created pool of 1458176 bytes
Delaying reset minutes.
syntax error in expression "(reset * 60000)"
while executing
"expr ($min * 60000)"
(file "/var/hack/locals/mvchannels.tcl" line 309)

I had mentioned this before, but thought it might be 3.1.0 related. But I am getting it again with 2.5.2
B

[chhamilton]

Originally posted by genericuser
Firstly, mvchannels 1.3.6 is for 2.5.2... You need to use 135.

You need to STOP mvchannels from running (comment it out of the rc.sysint or comment it out of cron). Then reboot. Now run mvchannels.tcl reset (version 1.3.5). Then reboot.

You should now have absolutely NO locals listed in the guide.

Now you need to (one at a time), get a set of locals you can receive into the guide. Seems like you have 2 sets of locals you want (Seattle, Portland).
That would be the trick that has not been plainly mentioned elsewhere: get each of the desired locals to work ONE AT A TIME before trying them all together.

Thanks!
:D

[genericuser]

chhamilton:

I sucessfully used the same technique to get multiple locals working in version 2.5.2 of the software. So I know that it works. You just have to be patient. It took me 3 days to get each of the three spotbeams in. Once I had all three in independantly, I ran mvchannels 136 and WHAM! Everything has guide data and is showing.

[genericuser]

boboli,

You are running versin 2.5.2 of the tivo software?

What version of mvchannels.tcl are you running?

Sounds like you need to download the software to your tivo again.

[quantum_3]

does the guide data last after you get them in?

[boboli]

Originally posted by genericuser
boboli,

You are running versin 2.5.2 of the tivo software?

What version of mvchannels.tcl are you running?

Sounds like you need to download the software to your tivo again.

I am using whatever version of mvchannels is part of SZ's Update. I seem to recall that I did a 'nano mvchannels.tcl' and I did not see a version number.
B

[Will]

>> That would be the trick that has not been plainly mentioned elsewhere: get each of the desired locals to work ONE AT A TIME before trying them all together.
<<

Actually it's been plainly mentioned a number of times. And it works. For a couple of cities, three, more in some combinations. For a large number of cities or with certain combinations of cities it breaks down eventually.

For people who just need their local market and a couple/few others this is great. For those fanatics who get overlapping spot beams, the 119, and want guide data for ALL the locals their dish sees, it is much more complicated. If any know how to do this they're keeping it to themselves.

[genericuser]

quantum_3:

I have been up since 1/28 and I am still getting data as of this morning. Are you having problems?

[quantum_3]

yep...i have holes in the guide data and it only goes to 2/14......i hope it fixes itself but i doubt it. i tried 11 markets, maybe i want a little overboard:)?