Hacked 6.2 - Getting dial up nag screen? HELP!

[dmurray14]

What the hell? I am getting the "Final Setup Steps" screen when I try to access Now Playing. I don't understand why it's doing this. I followed the steps to do the fakecall thing, but I guess it's not working? PLEASE HELP, I can't get to Now Playing!!

Dan

[Gunnyman]

did you modify fakecall so it works with 6.2? If so, did you edit the file with a Unix compatible txt editor? if not, run it through dos2unix (found in the tivotools set)
did you chmod the file?
if you're still having trouble try putting /tvbin/tivoshell fakecall.tcl in teh author file instead of just fakecall.tcl.

[fixn278]

What the hell? I am getting the "Final Setup Steps" screen when I try to access Now Playing. I don't understand why it's doing this. I followed the steps to do the fakecall thing, but I guess it's not working? PLEASE HELP, I can't get to Now Playing!!

Dan

Assuming you did it properly... reboot.

[dmurray14]

did you modify fakecall so it works with 6.2? If so, did you edit the file with a Unix compatible txt editor? if not, run it through dos2unix (found in the tivotools set)
did you chmod the file?
if you're still having trouble try putting /tvbin/tivoshell fakecall.tcl in teh author file instead of just fakecall.tcl.

Nope, didn't know there were differences. I'll see if a search turns up anything...

Dan

[dmurray14]

Found it! Thanks a lot!


Dan

[eastwind]

Found it! Thanks a lot!


Dan
Thanks for sharing!!

ew

[Jeff D]

I haven't had the nag yet, but I wanted to check if my technique will work.

I had the fakecall40 and callfakecall from my 4.0 disk so I continued to call callfakecall from the rc.sysinit.author file and then just replaced the old fakecall40 tcl file with the 6.2 fakecall. The only reason I ask is because I don't understand how the callfakecall script works and if the changes for 6.2 would do anything to screw it up. I know the other option is cron, but I'm not ready to do that yet.

[Gunnyman]

Jeff:
You won't have the nag if you've super-patched.
The fakecall is especially useful for imaging a system to 6.2 without slicing.
Fakecall lets you get to now playing without the initial setup phone call.

The new tcl file should be all you need.

[newbiewan]

I'm having a similar problem...EVerything is working w/ my hacked 6.2 upgrade except I am stuck at the initial service call. I made the edits to the fakecall.tcl file needed for 6.2, ran it through dos2unix and chmod'd it, but every time I try and run it from bash prompt I get "/tivo-bin/fakecall.tcl: No such file or directory"?

Any ideas?

[hayreass]

Is it in /tivo-bin?

[newbiewan]

yes, I have verified it several times. /tivo-bin has been set up in my .profile as one of my Path's too. I was curious if this was causing me problems so tried executing a copy of fakacall.tcl that I placed in the root directory temporarily, and I still get this message?

No real rush needed to figure this out...I managed to get it up and running...my solution...:

1. crond is executed from rc.sysinit (even though I can't seem to execute fakecall.tcl it manually as described above)

2. callFakeCall40.tcl is ececuted from rc.sysinit (it executes FakeCall40.tcl)

3. I also executed SetupComplete.tcl manually

I basically tried everything I could find on the board :) I wish I could tell you which one solved the problem...but as my name board name imples...I am lucky to even have this thing running at all ;)

It is definitely cool having all the HMO features activated! The wife was impressed and this whole thing has solved my original issue...the constant nagging screens caused by not being able to make the daily calls through Vonage.

This board has a great wealth of information...as a newbie, the hardest problem I have had is sifting through it all to find the process which is up to date for my application.

Anyway...back on topic. Any more ideas on why I can't seem to execute fakecall.tcl directly?

Thanks!

[Jamie]

Any more ideas on why I can't seem to execute fakecall.tcl directly?"No such file or directory" usually means the inital "pound bang" line is screwed up and has the wrong path to /tvbin/tivosh. One way it can be screwed up is if the file has dos rather than unix line endings. Try runing dos2unix on it.

You can always run tivosh scripts directly via: "/tvbin/tivosh myscript.tcl". This does not need a pound bang line to find tivosh.

[newbiewan]

Thanks for the info...

I'm not sure what "pound bang" means (so I will do a search to get myself up to speed on that).

I did perform the dos2unit on both the .profile and the rc.inint files when I first noticed this problem.

Is ther a simple answer to why /tvbin/tivosh should precede the fakecall.tcl file call?

[Jamie]

I'm not sure what "pound bang" means (so I will do a search to get myself up to speed on that)."#!" is pronounced 'pound bang'.
I did perform the dos2unit on both the .profile and the rc.inint files when I first noticed this problem.It's the fakecall.tcl script I'm talking about, in this case.Is ther a simple answer to why /tvbin/tivosh should precede the fakecall.tcl file call?The pound bang line tells linux where to find the program to run to process the script. You can also just run that program directly and tell it what script to run. That's what '/tvbin/tivosh fakecall.tcl' does. If you do that, the pound bang line doesn't matter.

[Gunnyman]

the pound bang is
this thing: #! at the beginning of the script. It tells the system what command environment to execute the script in.
If you edited fakecall.tcl using a windows text editor and then didn't run it through dos2unix once on the tivo, this very important line will be misread and the script will not execute.

[LanMan]

newbiewan

I've seen this also when ftping a file over in ascii mode rather than binary.

LanMan

[newbiewan]

Bingo!!! That was exactly why it was not running. I made sure to ftp it over in binary mode and then retested it...now it works straight from the bash prompt...without even using the "/tvbin/tivosh " prefix.

I wonder how many other files I am going to stumble across that have this problem :o Oh well, everything seems to working OK now.

Thanks for all your help!

[bozo8787]

Bingo!!! That was exactly why it was not running. I made sure to ftp it over in binary mode and then retested it...now it works straight from the bash prompt...without even using the "/tvbin/tivosh " prefix.

I wonder how many other files I am going to stumble across that have this problem :o Oh well, everything seems to working OK now.

Thanks for all your help!

newbiewan

I've seen this also when ftping a file over in ascii mode rather than binary.

LanMan

Thank u both, I had similar issue and now found success after ftp via binary. For Flashfxp is set to "auto"