HDVR2: use fixsub to prevent dial out (for privacy or anti-upgrade)

[sinikal6969]

Thought people might be interested to find out the details of how to accomplish this (for privacy reasons).

If anyone knows how to avoid the test call or avoid the daily calls (or both), please feel free to enlighten everyone with a step-by-step.

Thanks,
O=-SiNiKaL-=O

=============
EDIT
=============
Here's a solution - I'm open to comments...
-------------------------------------------
1) Get ahold of fixsub31.tcl and put it in /var/hack
2) Create a file called callfixsub.tcl in /var/hack the contents of which are:

while true; do
{
date > /var/hack/fixsub.log
/var/hack/fixsub31.tcl
sleep 82800
}
done

3) chmod 777 callfixsub.tcl
4) Add the following to the end of your hackinit:

sleep 60
echo "Calling FixSub"
/var/hack/callfixsub.tcl &
-------------------------------------------
DONE! No need to re-compile anything for HDVR2, and I haven't noticed any slow-down in performance!

NOTE: The "sleep 60" is there because the time is not accurately set upon boot (by the first time fixsub31.tcl is called) and thus you'd have to wait 1 day for your sub to "kick in". By sleeping 60 seconds we wait for the time to be set correctly and your sub can "kick in" immediately. (this will not affect your BASH prompt - it will still come up immediately)

If anyone has a better way, I'd be glad to hear it!

[orangejaylove]

fixsub3.1 maybe check that out

[orangejaylove]

wait on that I might be thinking of another program "touch" or something... alittle new(me). MrBlack51 is going to answer this soon in another post and prolly yell at me because I can't seem to keep track of anything he tells me even though I've read every post in this area 7 times... need to get my drives hooked up and get some hands on... but thats another story and post for that matter



exuse spelling

need sleep

[sinikal6969]

Ok. Maybe someone can tell me if I'm going in the right direction here. Here's my guess...

1) Put the fixsub31 TCL script in your /var/hack directory
2) Re-compile CRON for MIPS (HDVR2)
3) In your hackinit file, CRON the TCL script to have it run once per day

Sound about right?
If so...

QUESTIONS:
- Does anyone have CRON compiled for MIPS?
- Will the fixsub also avoid the "test call"?

Thanks!
O=-SiNiKaL-=O

[pcompact]

I have a Series 2 with lifetime sub. I also have
a Series 1 with no sub. I produce listing
slices for the Series 1 from web data.
To avoid having the Series 1 deactivated
by service calls, I set my router to not allow
out of my home network network connections
to or from the Series 1 machine ( it's on ethernet). My router is a Linksys, but I think
most routers include this functionality.
With TiVoWeb, you can see pretty easily
what mfs spots to patch to make it think it
has a subscription.

And no, I don't feel like I'm cheating Tivo. Inc.

[mrblack51]

pcompact: i would imagine that many on this website are of a similar opinion, in that if you choose to create your own guide data for your SA, then you aren't cheating tivo. Personally, I think that's a perfectly viable way to avoid their advertising stuff.

<rant>
I find it a bit ironic that tivo, a device designed to give you control over how you watch tv, seems to be moving into a business model designed around giving content providers and advertisers control over your tv. examples of this include the forced recording of a show that couldn't be deleted in the UK, advertisements in now showing, etc. Don't get me wrong, I love my tivo...I just think they are shooting themselves in the foot with the direction they seem to be going
</rant>

[BubbleLamp]

Originally posted by mrblack51
pcompact: i would imagine that many on this website are of a similar opinion, in that if you choose to create your own guide data for your SA, then you aren't cheating tivo. Personally, I think that's a perfectly viable way to avoid their advertising stuff.

<rant>
I find it a bit ironic that tivo, a device designed to give you control over how you watch tv, seems to be moving into a business model designed around giving content providers and advertisers control over your tv. examples of this include the forced recording of a show that couldn't be deleted in the UK, advertisements in now showing, etc. Don't get me wrong, I love my tivo...I just think they are shooting themselves in the foot with the direction they seem to be going
</rant>

They've always said they were going to use user viewing habits to bring targeted marketing to their advertisers and stations. It's nothing new really.

[orangejaylove]

So lets see...
1. You pay to watch Dtv or cable, most of the channels you watch are loaded with commericals,
2. Then ones that are "Extra" Comerical channels you have to pay additional for...
3. Then you pay for what we used to call (PayChannels Remember thet? HBO SHO etc. )
4. Then you go out and buy a tivo, which aren't cheap
5. Then you have to pay for the service to use it... now there going to put ads on it also?!?!?!

So to watch "Farscape on the Sci-Fi Channel" I have to pay for basic and extended channels then have to watch the ads and it I record it in on tivo I have to include the price of reciever and service and now have to deal with ads ... sorry but anyone who dosen't think that this is Bullshiet are absolutely outta there mind...

me you and all of use are now PAYING to Watch ADS!!!

pay 5 times to watch tv and record stuff you want for personal use..... how much money you think there makeing off of us?

[mrblack51]

i realize that went off topic, so i will be the one to say that this thread needs to head back on topic.

the questions relate to use of fixsub and such

[TheDoctor]

From working with 3.0 on a sereis 2 SA I can state the following.

Some of the tcl scripts from the sereis 1 are not included on a sereies 2. If those files are moved then a veriation on fix sub does work. I won't have access to my series 2 for a few weeks, so cannot post detail. I also did not take notes when I transfered files.

I believe that a few diffrent database objects are refereneced, but I have not tried 3.x on a sereis 1 so it may use the same structure.

The script I am using on sereis 2 is executed from another machine and is not a standalone tcl script. Afraid I don't have much time for tivo these days so cannot offer much immediate help beyound confirming that it is possible.

[sinikal6969]

FYI, I added a solution to my original post (the first post in this thread).

It is but ONE solution, and I would be glad to hear others -- or if anyone has a reason that we SHOULDN'T use this solution.

Thanks!
O=-SiNiKaL-=O

[FastEddieG]

Thanks for the info. Is there a hack to eliminate the need for the test call?

Thanks!
-Ed

[mrblack51]

if you let it attempt the call while going through guided setup, its no problem. after running setup to verify sat settings, run fixsub. it will tell the tivo that guided setup has been completed

[OvitivO]

2) Re-compile CRON for MIPS (HDVR2)

Is this compilation of cron available anywhere?

I believe that 31cron-v2.zip is not for mips, but I could be wrong. (I do know that it does not work on a HDVR2.)

[mrblack51]

Originally posted by OvitivO
Is this compilation of cron available anywhere?

I believe that 31cron-v2.zip is not for mips, but I could be wrong. (I do know that it does not work on a HDVR2.)

thats for the ppc...as with everything for the s1 units. in general, i believe everything for mips is labeled as such

[thedistance]

I'm wondering if fixsub would allow you to skip the initial dial to tivo or would only allow you to skip the normal dailys?

[mrblack51]

Originally posted by thedistance
I'm wondering if fixsub would allow you to skip the initial dial to tivo or would only allow you to skip the normal dailys?

let it attempt the initial dial and fail. run fixsub, reboot. should be good to go

[sinikal6969]

Hey mods, it might be nice to sticky this thread for people, since it's a procedure that most people will be interested in. Agree?

Thanks,
O=-SiNiKaL-=O

[Copper Top]

im looking for the fixsub31.TCL file, i found the 31fixsub.cpio, .sh .txt and .rc files but not the .tcl file. is there something special i need to do to get this file in this format?

[thedistance]

If you "cat 31fixsub.sh" you will see a command in there that starts with "cpio". Run that command which will expand the 31fixsub.cpio which contains 31fixsub.tcl.

[Copper Top]

do i rz the files over to the var/hack dir. and do all this form there?

[thedistance]

It depends if you have cpio on your machine or not... from bash prompt just type cpio to see if it's there or not. If it's not you can use one of the boot cd's and put the hard drive in your computer to do it.

[billisnow]

Hi all,
need a little help......
I have rz the fixsub31.tcl file to my hack directory and chmod 777.
But when I try test run it using the ./fixsub31.tcl command I just get the following.....errors......and it does not run

WARNING: couldn't scan startup script /tvlib/tcl/tv/tv.ini
WARNING: eval result : Cant read " env<TIVO_ROOT>": no such element in arrayTmk
Assertion Failure:
FsstartFunction, line 141 <>
Tmk Fatal Error: Thread tivosh <181> died due to signal -2
ccffde8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c4522c bbd270 400778 d75 3d0

Do I not have a good copy of fixsub31.tcl (I got it from 31fixsub module then from the 31fixsub.cpio) or have I missed somthing?? (maybe in my hackinit file?)
Any help would be appreciated
Thanks

[ghstrdr5]

Does the top of your hackinit look like this

#!/bin/bash
date>>/var/hack/hackinit.log
PATH=/var/hack/bin:/sbin:/bin:/tivobin:/tvbin:.
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF


if not you wont be able to run scripts

[Thorvald]

Originally posted by billisnow
WARNING: couldn't scan startup script /tvlib/tcl/tv/tv.ini
WARNING: eval result : Cant read " env<TIVO_ROOT>": no such element in arrayTmk
Assertion Failure:
FsstartFunction, line 141 <>
Tmk Fatal Error: Thread tivosh <181> died due to signal -2
ccffde8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c4522c bbd270 400778 d75 3d0

I have the same issue, the first was an easy fix (if it is the same error I had), the path statment to TCL lib is incorrect in fixsub31.tcl (at least for my HDVR2). It was tvsource $tcl_library/tv/mfslib.tcl, turns out that $tcl_library was a undefined enviroment variable on my machine, so I hardcoded the correct path. I also fixed the lib path and then the script ran ok...almost.

The script then bombed, printed some errors/exceptions and caused the Tivo to reboot.... happens each time I run it now.

After some heavy searching and reading, I have a few ideas to try, they are:

1. Let it attempt the initial dial and fail. run fixsub, reboot. I hadn't done this yet, I tried to run fixsub right away from the shell prompt manually. Perhaps there are some settings that need to be setup which get done by the first failed call?

2. Make sure my hackinit is the same as the previous poster. Though you should make sure that MFS_DEVICE=/dev/hda10 is the correct partition on your system for mfs_device). Also curious why TIVO_ROOT is set to nothing.

I'll be trying these soon and will sit down and parse through the fixsub31.tcl script just to see if I missed anything obvious (pretty simple script though).

If anyone cares to point us in the right direction, please do, otherwise I'll likely figure it out soon enough.

Thanks
Thorvald

[dogbreath]

could someone please send me a copy of 31fixsub.tcl?

[lazerexp]

When I run my fixsub this is what I get.

bash-2.02# ./31fixsub.tcl
': not a valid identifierIGNOREEOF
: command not found
./31fixsub.tcl: tvsource: command not found
: command not found
./31fixsub.tcl: proc: command not found
./31fixsub.tcl: puts: command not found
./31fixsub.tcl: try: command not found
./31fixsub.tcl: RetryTransaction: command not found
./31fixsub.tcl: line 19: syntax error near unexpected token `($'
'/31fixsub.tcl: line 19: ` set today [expr ($now / 86400)]
bash-2.02#


Attached is my fixsub.tcl to review

[mrblack51]

Originally posted by ghstrdr5
Does the top of your hackinit look like this

#!/bin/bash
date>>/var/hack/hackinit.log
PATH=/var/hack/bin:/sbin:/bin:/tivobin:/tvbin:.
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF


if not you wont be able to run scripts

lazerexp: did you do this? if not, then the script wont work

[lazerexp]

I have a hacked prom so I placed it on top of the 31fixsub.tcl script. I also tried in at the top of rc.sysinit.author.

[Thorvald]

I edited my hackinit to be exactly as shown above and it worked perfect for me.

If you performt he Path, Tivo_Root, Mfs and Ignore manually and then export them all manually, you should be able to run callfixsub manually as well. That also worked for me.

Here is my current:

#!/bin/bash
echo "Starting Hackinit..." > /dev/ttyS2
PATH=/var/hack/bin:/sbin:/bin:/tivobin:/tvbin:.
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF
echo "Sleeping 60 seconds for time sync/setup..." > /dev/ttyS2
sleep 60
date>>/var/hack/hackinit.log
/bin/bash</dev/ttyS2&>/dev/ttyS2&
echo "Calling FixSub..." > /dev/ttyS2
/var/hack/callfixsub.tcl &

Course now my question is, do we need a cron job for this or will the old 'while true' loop trick work? (with a long sleep period, hence callfixsub will never terminate).

[lazerexp]

I tried it manually and it didn't work either. I know I am missing something stupid....as we all know it usually is :)

[txag93]

The callfixsub will never terminate. NOTE, be sure to use & on the line calling callfixsub or you will not return from the command and only way out is a reboot. No job control in this shell!


Originally posted by Thorvald
[
Course now my question is, do we need a cron job for this or will the old 'while true' loop trick work? (with a long sleep period, hence callfixsub will never terminate). [/B]

[txag93]

laserexp, since you are using a modded prom and initrd kill, you are not following the same rules as those putting things in their hackinit file. (I don't even know if you have or need a hackinit file).

However, you should still confirm that the rc.sysinit or some other script is executing the basic structure outlined by mrblack51 above. You should then be able to let it fully boot to bash, and type fixsub31.tcl and it should say inside fixsub, then done with fixsub if all is well. Post your errors if not. If you place the call to fixsub at top of rc.sysinit, you probably are not setting up the variables and defining the locations above.

TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF

needs to execute before fixsub31.tcl

[dogbreath]

What partition is /var/hack in? Is it 7 or 9?

[mrblack51]

Originally posted by txag93
You should then be able to let it fully boot to bash, and type fixsub31.tcl and it should say inside fixsub, then done with fixsub if all is well. Post your errors if not. If you place the call to fixsub at top of rc.sysinit, you probably are not setting up the variables and defining the locations above.

TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF

needs to execute before fixsub31.tcl

this is pretty accurate. you should be attempting to run fixsub at the end of rc.sysinit. and you should check your ability to run it after the system fully boots by running it from the command prompt.

[lazerexp]

/var/hack in on partition 9

My rc.sysinit.author is as follows:

TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF

/bin/bash < /dev/ttyS2 >& /dev/ttyS2 &
stty sane
stty 115200

insmod /diag/usbcore.o
insmod /diag/usb-ohci.o
insmod /diag/pegasus.o
ifconfig eth0 10.30.0.5 broadcast 10.30.0.255 netmask 255.255.255.0
#route add default gw 10.30.0.1 netmask 0.0.0.0 metric 1
tnlited 23 /bin/bash -login &
/bin/tivoftpd

sleep 60
echo "Calling FixSub"
/var/hack/callfixsub.tcl &






My callfixsub.tcl is as follows

while true; do
{
/var/hack/31fixsub.tcl
sleep 82800
}
done


My 31fixsub.tcl look like this

##############
# fixsub.tcl #
##############

tvsource /tvlib/tcl/tv/mfslib.tcl

proc FixSub {db} {
puts "Inside fixsub"
try {
RetryTransaction {
set now [clock seconds]
set today [expr ($now / 86400)]
set stateExpiration [expr ($today + 1)]
set nextCall [expr ($stateExpiration * 86400)]
set lastCallStatus "Succeeded"
set callStatusInfo "Succeeded"

set sobj [db $db open /State/PhoneConfig]

dbobj $sobj set LastDialInUpdateDate $today
dbobj $sobj set CallStatusInfo $callStatusInfo
dbobj $sobj set LastCallAttemptSecInDay $now
dbobj $sobj set LastSuccessPgdCallSecInDay $now
dbobj $sobj set LastSuccessCallSecInDay $now
dbobj $sobj set LastCallStatus $lastCallStatus
dbobj $sobj set NextCallAttemptSecInDay $nextCall

set ssobj [db $db open /State/ServiceConfig]

dbobj $ssobj set ServiceStateExpiration $stateExpiration

set ssobj [db $db open /State/GeneralConfig]

dbobj $ssobj set Complete 7
}
puts "done with fixsub"
} catch errCode {
puts "Failed to FixSub, code=($errCode)"
return 0
}
return 1
}

set db [dbopen]
FixSub $db
dbclose $db


proc Succeeded {db} {
puts "Setting call to Succeeded"
try {
RetryTransaction {
set lastCallStatus "Succeeded"
set sobj [db $db open /State/PhoneConfig]
dbobj $sobj set LastCallStatus $lastCallStatus
}
} catch errCode {
puts "Failed to set LastCallStatus, code=($errCode)"
return 0
}
return 1
}


all are in partition 9 in /var/hack and chmod +x
All created with TextPad on PC and zmodem'd over

the error message is:

bash-2.02# ./31fixsub.tcl
': not a valid identifierIGNOREEOF
: command not found
./31fixsub.tcl: tvsource: command not found
: command not found
./31fixsub.tcl: proc: command not found
./31fixsub.tcl: puts: command not found
./31fixsub.tcl: try: command not found
./31fixsub.tcl: RetryTransaction: command not found
./31fixsub.tcl: line 19: syntax error near unexpected token `($'
'/31fixsub.tcl: line 19: ` set today [expr ($now / 86400)]
bash-2.02#

[egocentric]

Try adding this to the top of your 31fixsub.tcl file:

#!/tvbin/tivosh

[lazerexp]

Originally posted by egocentric
Try adding this to the top of your 31fixsub.tcl file:

#!/tvbin/tivosh

same error :(

bash-2.02# ./31fixsub.tcl
': not a valid identifierIGNOREEOF
: command not found
./31fixsub.tcl: tvsource: command not found
: command not found
./31fixsub.tcl: proc: command not found
./31fixsub.tcl: puts: command not found
./31fixsub.tcl: try: command not found
./31fixsub.tcl: RetryTransaction: command not found
./31fixsub.tcl: line 19: syntax error near unexpected token `($'
'/31fixsub.tcl: line 19: ` set today [expr ($now / 86400)]
bash-2.02#

[txag93]

My thoughts, and I am no linux expert.

If using TextPad on PC, Open all files you have edited/saved and do a File >> Save As Be sure to choose UNIX as the file type and then choose the existing file name and overwrite. This bit me on my callfixsub.tcl script not running, which is of course not your current problem.

Second, one of your lines below is different from mine, but again I don't know if it would cause what you are seeing.

/bin/bash</dev/ttyS2&>/dev/ttyS2& Your & are outside the > below, probably just a typo.

Originally posted by lazerexp
/var/hack in on partition 9

My rc.sysinit.author is as follows:

TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF

/bin/bash < /dev/ttyS2 >& /dev/ttyS2 &
stty sane
stty 115200

[lazerexp]

Thanks for the hint. But it didn't work either. That was just the kind of dumb mistake I was looking for. Too bad it wasn't it.

As for my BASH it is /bin/bash < /dev/ttyS2 >& /dev/ttyS2 &
and it is working fine.

[txag93]

Did you hard code the tvlib path on purpose, or is that the way you found fixsub31.tcl?

Mine starts:

#!/tvbin/tivosh

##############
# fixsub.tcl #
##############

tvsource $tcl_library/tv/mfslib.tcl

This is different from yours, and may explain why you get the not found errors. That or control characters due to a windows editor. I would re-download/ re
cpio -idmu the file and see if that changes anything. Remember, don't run it from callfixsub.tcl until you get it working from bash prompt.

Originally posted by lazerexp
/My 31fixsub.tcl look like this

##############
# fixsub.tcl #
##############

tvsource /tvlib/tcl/tv/mfslib.tcl

[egocentric]

Originally posted by lazerexp
same error :(

bash-2.02# ./31fixsub.tcl
': not a valid identifierIGNOREEOF
: command not found
./31fixsub.tcl: tvsource: command not found
: command not found
./31fixsub.tcl: proc: command not found
./31fixsub.tcl: puts: command not found
./31fixsub.tcl: try: command not found
./31fixsub.tcl: RetryTransaction: command not found
./31fixsub.tcl: line 19: syntax error near unexpected token `($'
'/31fixsub.tcl: line 19: ` set today [expr ($now / 86400)]
bash-2.02#

Sorry, but that's impossible.

The errors you're getting are because the bash interpreter can't interpret the tcl commands.. for obvious reasons. Bash is not a tcl environment. tivosh is a tcl environment... And the error output from tivosh looks nothing like the errors from bash.

Are you sure you put it exactly as I typed it as the very first line in 31fixsub.tcl?

#!/tvbin/tivosh

If so, check /tvbin and make sure there is a tivosh file there.

Try running tivosh first, then when you see the '%' prompt, type 31fixsub.tcl and press enter. Now you are running the tcl script from within the tivosh tcl environment.

[Harvick29]

txag93...I was getting the same error as Lazerexp now with the changes you suggested I'm now getting this error..

WARNING: couldn't scan startup script /tvlib/tcl/tv/tv.ini
WARNING: eval result : can't read "env(TIVO_ROOT)": no such element in arrayTmk
Assertion Failure:
FsStartFunction, line 141 ()
Tmk Fatal Error: Thread tivosh <189> died due to signal -2
ccfde8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c4522c bbd270 400778 d75
3d0

any ideas what to try next?

[lazerexp]

Tried the removal of the hard coded back to tvsource $tcl_library/tv/mfslib.tcl with no luck

tried tivosh manually and got same error.

tried moving the & on my BASH and no change.

I sure do appreciate all the suggestions as this is boggling my mind :)

I just know it is going to be something simple.

[FastEddieG]

Originally posted by Harvick29
txag93...I was getting the same error as Lazerexp now with the changes you suggested I'm now getting this error..

WARNING: couldn't scan startup script /tvlib/tcl/tv/tv.ini
WARNING: eval result : can't read "env(TIVO_ROOT)": no such element in arrayTmk
Assertion Failure:
FsStartFunction, line 141 ()
Tmk Fatal Error: Thread tivosh <189> died due to signal -2
ccfde8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c4522c bbd270 400778 d75
3d0

any ideas what to try next?

Read the thread.. does your hackinit have the following?!?!

#!/bin/bash
date>>/var/hack/hackinit.log
PATH=/var/hack/bin:/sbin:/bin:/tivobin:/tvbin:.
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF


If not, then that is more than likely the case of your errors.

Good luck,
-Ed

[txag93]

I was getting that once too, read fasteddie's post above, make sure your hackinit has that, and is indeed running at boot. I bet your system resets itself after the error you posted below too :-(


Originally posted by Harvick29
txag93...I was getting the same error as Lazerexp now with the changes you suggested I'm now getting this error..

WARNING: couldn't scan startup script /tvlib/tcl/tv/tv.ini
WARNING: eval result : can't read "env(TIVO_ROOT)": no such element in arrayTmk
Assertion Failure:
FsStartFunction, line 141 ()
Tmk Fatal Error: Thread tivosh <189> died due to signal -2
ccfde8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c4522c bbd270 400778 d75
3d0

any ideas what to try next?

[tivosohn]

After messing arround and experiment with my sparkling brand new HDVR2 for a month and step on millions of traps and restores. I have see those errors in one of my trial and errors. If you did set your path as mentioned in all the above posts, then it looks like the image on your disk is somewhat screwed up. It seems to be some of your required commandline binary files are missing due to some unknown reason. I think your best bet is to restore from a good image and reload the /var/hack and fixsub file into it, then rerun to see if you see these errors again.

IMPORTANT! NEVER RUN YOUR "/etc/rc.d/rc.sysinit" ON YOUR BASH PROMPT. IT WILL TOTALLY SCREW UP BOTH YOUR HDA7 AND HDA9 PARTITIONS. If you want to see what that does, I STRONGLY advise you to backup your current drive or have a good backup handy. I can assure you will hit your PC within 10 minutes after you did that.

Cheers...:p

[Requiem]

Originally posted by mrblack51
let it attempt the initial dial and fail. run fixsub, reboot. should be good to go

Forgive my ignorance on this matter but what if I didn't let it dial and fail (I didn't). Fixsub seems to be working. When I go to the phone connection page it does want me to configure the phone options, but when I check the system information screen it does report that my last call attempt was successful. Will I run into trouble in a few days?

- Req

[mrblack51]

Originally posted by Requiem
Forgive my ignorance on this matter but what if I didn't let it dial and fail (I didn't). Fixsub seems to be working. When I go to the phone connection page it does want me to configure the phone options, but when I check the system information screen it does report that my last call attempt was successful. Will I run into trouble in a few days?

well, you have to run fixsub once a month or so to make sure that the tivo doesnt get pissy for not calling in. if you ran fixsub and it didnt require you to attempt a call, then great. the reason for that is when you initially setup your unit, it usually wants to go through guided setup right away, which includes a dial out. fixsub will set the flag which indicates that that portion of the setup has completed.

[Requiem]

Thanks for the quick reply.

Durring guided setup it only forced me to setup the satellite aspect of the system. So hopefully all will be ok.

By the way, I really appreciate all your posts. You and a few others on the board really go the extra mile to help out folks and make this a really fun hobby... I'd be lost without the dealdatabase.

- Requiem

[yngdiego]

Even with the fixsub script, with 3.1 and a series 2, don't you need to have DTV set a flag on the card? There's no way like the series 1 DTIVOS to be completely on your own.

[lazerexp]

Originally posted by yngdiego
Even with the fixsub script, with 3.1 and a series 2, don't you need to have DTV set a flag on the card? There's no way like the series 1 DTIVOS to be completely on your own.

Correct no way.

[Requiem]

I'm not suggesting this should be discussed in great detail on this board but wouldn't you be able to bypass that tier requirement in the 3.1 software somewhere?
Sounds similar to 3.1 not normally allowing a HU card, but that too is a software restriction.

- Req

[nitrous]

well, they play a role in deciding what card will be accepted by the TiVo! :)
3.x only works with P4 cards (unless you make a change or two)
n|trous

[mckitrick]

Requiem - If you find out, Let ME know! :)

[rpl]

bash-2.02# ./31fixsub.tcl
': not a valid identifierIGNOREEOF
: command not found
./31fixsub.tcl: tvsource: command not found
: command not found
./31fixsub.tcl: proc: command not found
./31fixsub.tcl: puts: command not found
./31fixsub.tcl: try: command not found
./31fixsub.tcl: RetryTransaction: command not found
./31fixsub.tcl: line 19: syntax error near unexpected token `($'
'/31fixsub.tcl: line 19: ` set today [expr ($now / 86400)]
bash-2.02#


Attached is my fixsub.tcl to review

I was getting these same error messages that Lazer did when I tried using the fixsub file he attached in this post. I see 110 people have downloaded this file and probably will have the same issues.

If you don't have call succeeded on your system info screen this fixsub file works for me. I had to remove the "puts" command from the file to get it to work for me.

It only took two weeks before I started getting the nag message that TIVO has not phoned in. Then I realized my fixsub wasn't working duh

[mrblack51]

Originally posted by rpl
I was getting these same error messages that Lazer did when I tried using the fixsub file he attached in this post. I see 110 people have downloaded this file and probably will have the same issues.

If you don't have call succeeded on your system info screen this fixsub file works for me. I had to remove the "puts" command from the file to get it to work for me.

It only took two weeks before I started getting the nag message that TIVO has not phoned in. Then I realized my fixsub wasn't working duh

did you set the IGNOREEOF environment var in your hackinit? looks like it wasnt set properly

[RadOD]

I'm getting the same errors as lazerexp was getting:


': not a valid identifierIGNOREEOF
: command not found
./31fixsub.tcl: tvsource: command not found
: command not found
./31fixsub.tcl: proc: command not found
./31fixsub.tcl: puts: command not found
./31fixsub.tcl: try: command not found
./31fixsub.tcl: RetryTransaction: command not found
./31fixsub.tcl: line 19: syntax error near unexpected token `($'
'/31fixsub.tcl: line 19: ` set today [expr ($now / 86400)]


but i DO have the stuff in my hackinit:


#!/bin/bash
date>>/var/hack/hackinit.log
PATH=/var/hack/bin:/sbin:/bin:/tivobin:/tvbin:.

#Environmental variables
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF
/bin/bash</dev/ttyS2&>/dev/ttyS2&

#Load ethernet drivers
insmod /var/hack/lib/usbcore.o
insmod /var/hack/lib/hcd.o
insmod /var/hack/lib/ehci-hcd.o
insmod /var/hack/lib/ax8817x.o
sleep 10
ifconfig eth0 192.168.0.50 broadcast 192.168.0.255 netmask 255.255.255.0
route add default gw 192.168.0.1 netmask 0.0.0.0 metric 1

#Telnet and FTP
tnlited 23 /bin/bash -login &
tivoftpd
/var/hack/tivoweb-tcl/tivoweb

kmem 800b23b4 00001021


don't I?

Edit: I tried rpl's version which worked. But again, I set the IGNOREEOF didn't I? Above is an exact cut and past of my hackinit which was originally cut from mrblack51's file.

[Mr novice]

RadOD:
Add this to your hackinit

#Corrects Daily calls
sleep 60
echo "Calling FixSub"
/var/hack/31fixsub.tcl &

[Shr00m]

Is this what should happen when I run fixsub?



bash-2.02# ./31fixsub.sh
31fixsub.cpio.gz: No such file or directory
5 blocks
bash-2.02#


EDIT:

I downloaded the 31fixsub.tcl from the above post and now I get this when I run it:


bash-2.02# ./31fixsub.tcl
bash-2.02#


Is this now correct?? I think the other I ran wasn't compiled for mips

thanks.

[mrblack51]

Originally posted by Shr00m
Is this what should happen when I run fixsub?

EDIT:

I downloaded the 31fixsub.tcl from the above post and now I get this when I run it:

Is this now correct?? I think the other I ran wasn't compiled for mips

thanks.

fixsub is just a script (hence the .tcl extension). scripts are cross platform (as noted in the series 2 faq). if you check your system info screen, you should see it indicate that a daily call occured about the same time that you ran the script. if it does, than it worked.

[dogbreath]

Would someone please post a copy of "fixsub31.tcl", not "31fixsub.tcl".

dogbreath

[captain_video]

How about just a plain old fixsub.tcl without the "31". It's the same script as the "31" version and has been tested on a S2 DTivo. Just extract it from the zip, upload it to your /var/hack directory, and do a chmod 777 fixsub.tcl. To run it just type in the following at bash:

cd /var/hack
./fixsub.tcl


The last call status should convert to successful and your account should indicate it's in good standing.

[vsaltv]

I tried a long time to get this file 31fixsub.tcl to work and couldn't. But then I ran this command instead:

tivosh /var/hack/31fixsub.tcl

and it executed finally. Rebooted then went in to take a look and sure enough it updated the test call status like it should.

Before this I kept getting file not found, or a whole bunch of errors.

[chromacloud]

Everything I try gives me this error, which also causes my unit to restart:
Filesystem assert: hDeviceM >= 0 at fsphysdisk.C line 151 in FsPhysDisk::FsPhysD
isk(FsInitParams*, const char*)
Tmk Assertion Failure: hDeviceM >= 0
FsPhysDisk::FsPhysDisk(FsInitParams*, const char*), line 151 (fsphysdisk.C)
Tmk Fatal Error: Thread tivosh <186> died due to signal -2
ce6800 cf79c4 cfbbc4 ccfaa8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c45
22c bbd270 400778 d753d0

I've tried also tried:
bash-2.02# /tvbin/tivosh
% /var/hack/31fixsub.tcl

And: bash-2.02# tivosh /var/hack/31fixsub.tcl
And: bash-2.02# /var/hack/31fixsub.tcl
And: bash-2.02# /var/hack/call31fixsub.tcl
And: bash-2.02# /tvbin/tivosh
% /var/hack/call31fixsub.tcl

My call31fixsub.tcl:
while true; do
{
date > /var/hack/fixsub.log
/var/hack/31fixsub.tcl
sleep 82800
}
done


All methods give me the same problem. I'm thinking that either my 31fixsub file is bad or it has to be something else, which I have no idea. I used the posted 31fixsub.tcl file by "rpl" above in the thread. Also if it matters, I get a similar error when I run tivoweb console. I've attached my hackinit for review. Thanks for the help.
-chromacloud

EDIT: This hackinit is incorrect, do not copy.

[David Bought]

Originally posted by chromacloud
Everything I try gives me this error, which also causes my unit to restart:
Filesystem assert: hDeviceM >= 0 at fsphysdisk.C line 151 in FsPhysDisk::FsPhysD
isk(FsInitParams*, const char*)
Tmk Assertion Failure: hDeviceM >= 0
FsPhysDisk::FsPhysDisk(FsInitParams*, const char*), line 151 (fsphysdisk.C)
Tmk Fatal Error: Thread tivosh <186> died due to signal -2
ce6800 cf79c4 cfbbc4 ccfaa8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c45
22c bbd270 400778 d753d0

MFS_DEVICE is set according to the Tivo's POV and therefore should be hda10, not hdc10.

And they're called environment variables, not "environmental" variables.

[chromacloud]

Originally posted by David Bought
MFS_DEVICE is set according to the Tivo's POV and therefore should be hda10, not hdc10.

And they're called environment variables, not "environmental" variables.

Thanks David, all this time trying so many things and it was a typo on my hackinit I would of never noticed. I remember being so tiered when I typed that which explains the problem. Now I got fixsub to work, tivoweb, and tserver YAY!. I changed my hackinit file and attached it for review.
Thanks again,
-chromacloud.

[chromacloud]

I forgot to put the file, sorry.
-chromacloud

[Ingineer]

Remember, if you use FTP to transfer files, make sure you issue the BIN command first! Using ASCII mode can sometimes add an extra CR or LF in the wrong place and it will kill your script.

I have transferred several TCL scripts without BIN, and sometimes they work, sometimes they don't. But they are always ok with BIN.

[Darkrider]

Guess that would explain why when I changed my hackinit in Editpad Pro and transfered it back to my DVR and restarted, I lost all access to it including serial bash. The file was probably corrupted on the transfer. I will hook my Tivo drive back to my computer and copy the hackinit file and see if this brings it back up.

Thanks for the heads up.

Remember, if you use FTP to transfer files, make sure you issue the BIN command first! Using ASCII mode can sometimes add an extra CR or LF in the wrong place and it will kill your script.

[ModdedOutXbox]

WARNING: couldn't scan startup script /tvlib/tcl/tv/tv.ini
WARNING: eval result : can't read "env(TIVO_ROOT)": no such element in arrayTmk
Assertion Failure:
FsStartFunction, line 141 ()
Tmk Fatal Error: Thread tivosh <189> died due to signal -2
ccfde8 cd031c bd3c50 bc7bf8 bbf014 c1fa98 bf6d78 c41a00 c4522c bbd270 400778 d75
3d0



try adding the folowing line into your hackinit:

#!/bin/bash
date>>/var/hack/hackinit.log
PATH=/var/hack/bin:/sbin:/bin:/tivobin:/tvbin:/tvlib:.
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF

/bin/bash</dev/ttyS2&>/dev/ttyS2&

[Meathead]

I tried chromacloud's hackinit and I lost bash. I will reimage and start over. I have had difficulty in getting fixsub to work at all. I have had all the same errors as listed here before. Unfortunately. I haven't been able to get an editor running on the tivo either. Tried joe and vi. couldn't get either to work. I guess I need to read more to figure this out.

[citivolus]

As fixsub seems to only set the time for the last successful call, why don't we simply set it to some time in the future so we don't need to run it once a month?

change the line:

set today [expr ($now / 86400)]

to

set t [expr ($now / 86400)]
set today [expr ($t + 365)]

and run it once. That would set the "last" successful call to one year from today. Presumably, no nag screens should appear for at least a year. This of course depends on how they calculate the nag period...guess I'll find out in a few weeks, since the "Last Successful Call" on the status page doesn't show the year.