-
Yes . . . well . . . ahem . . . cough, cough . . . shuffle of feet, etc.
Technically, my description of what I did is correct. I DID put the disk back into the TiVo. What I DIDN'T do, is connect it up. Seems to make a difference. (And in my defence had worked this out before Peter's message just now.)
1. However, fixing that small oversight, and plugging power cord back in had it coming up with Guided Setup OK but failing as before at the Connecting . . . step with "Failed. Service Unavailable" as before (but after 3minutes rather than the previous 16).
2. Putty'd in with no problem, and Pico'd /etc/postcodezones. Noticed that 02110 is missing so added that and tried again. No change.
3. Did a Full Restart (closest thing I could see on the new menu system that looks like a Reboot), which finished instantly (a bit suspicious that), and tried again but no joy.
4. Unplugged TiVo and plugged it back in. Browsed to TiVo and used SysAdmin/PAL-NTSC/Set PAL Guided Setup Mode which produced:
TiVo set for PAL Guided Setup. Please reboot.
root=/dev/hda4 runideturbo=false TV_STD=PAL GS=1 GS=1
Tried Full Restart but it really doesn't seem to do anything (doesn't even change the screen from the failure message) so unplugged power cord and plugged back in and it ran through GS again. No change.
5. Used SysAdmin to Set PAL and then SetPAL Guided Setup Mode (gets rid of the double GS = 1 at the end but don't suppose that matters). Used Pico to look at tclient.conf and found following:
126::66.23.218.193:80:::
# This is for the server emulator on minnie. Trouble if your ISP blocks HTTP .9
#127::131.244.9.101:80:::
# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
127::127.0.0.1:8000:::
# NZ legacy
126::210.48.107.133:80:::
# NZ develop
128::210.48.107.133:8888:::
So now I need to know if there is anything I should change there.
a) The file is tiny compared with what was there before. Hope this is a good thing.
b) I note two live lines with 126 in them and referring to port 80.
c) Line 127 is the revised line that Wibble originally mentioned for getting around a proxy.
d) rc.sysinit.author does have the correct corresponding line
emuProxy2 -s 210.48.107.133 -p 8000 &
So that's probably all correct.
My next plan is to take it to a friend's house who has a different Telco and ISP to eliminate network issues as a cause but guess I'll have to go back into the reimage process to change over the network address to blank.
Have also downloaded Wibble's Ultimate Boot CD and will use it to test disk.
Unless anyone has any other ideas?
David
Last edited by David Stott; 20-09-2008 at 01:29 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks