Separate names with a comma.
Discussion in 'TiVo Underground' started by rbautch, Jul 21, 2005.
I'll work with these examples this evening and report my findings.
I'm in the process of incorporated NCID caller ID into the enhancement script. Since I don't have a phoneline, I can only test portions of installation. Please PM me if you are interested in helping me test this feature.
Here's a helpful page:
I found two problems with the latest version of your script.
First, the profile that is installed: root has the wrong path. It tries to read the file from /usr/spool, where /var/spool is the correct path.
Fakecall would not work from me, even tough cron was running, and busybox is my path. I fixed this by adjusting the path also on the root file like this: tivosh /busybox/fakecall.tcl
It would a good idea, in order to debug this, that you do the
echo "`date` fakecall made" >> /var/spool/cron/cronlogs/CRONLOG-MAIN
from within the fakecall script, that way you not the script actually was executed. The way it was working for me, cron did tivosh fakecall.tcl (and failed) and then the echo, which confused me into believing that fakecall actually was executed succesfully.
Other than some minor tweaks to the scripts (files not found when runnint the script a second time, some directories not created, etc) everythins is working great.
Great job! This script has reduce the number of steps I have to do to hack my tivo from about 10 to 4...
Those issues have been mentioned previously in the thread... but I missed that too when I ran his script, so good catch. I noticed the "file not found" error when I tried "tivosh fakecall.tcl" from the bash prompt. I like the idea about logging in the script itself; I think I'll incorporate that in my setup. Thanks for the idea.
Anyone have any success with the safereboot? The way the script ran on my TiVo, it was TOO safe (wouldn't reboot during suggestions).
Great suggestions, thanks jasch. Timing is good too. I'm just finishing a beta of the next version of the script. One of the things I incorporated is safereboot. I increased the reboot frequency to twice/week just in case something is trying to record on the first attempt. I'm wondering if this is an appropriate freqency, or if perhaps I should make safereboot optional for people who are keeping a phone line connected and don't want to take a chance on reboot not happening.
Fakecall is a tcl script, not a bash script, so the code you suggested won't work. I'll do some checking about how to do it in tcl.
In order to save on space, I wrote the script to delete certain files after they're used, which prevents you from running the script multiple times. However, the uninstall script very neatly (and smartly) deletes everything that was installed by the script, and moves the files archive to the root directory. Using uninstall, you can run the script over and over again without any issue.
Successfully installed NCID and out2osd last evening. I reconnected the phone line and now see white text on a black background announcing the name and number of the caller ID information.
I vote for that option, I'd much rather risk missing a 3am recording than I would losing my hacks.
The one way I just have to worry about making sure that the 3am once a week recording isn't set up. The other way I have to "baby-sit" the phone call info logs to make that the last phone call is reported as "succeeded".
Thanks for all of the work on your part.
You're welcome. I will indeed make this an optional feature.
just a heads up, over at "DDB" there's a new superpatch-67 all that supports 6.1 and 7.2 tivoapps, also new USB2 backport drivers that now supports the Linksys USB200M(version 2)adapters, in case you wanted to include it into your scripts here
Does this mean the R10's are hackable?
EDIT] - It's the future , and 6.1 (R10) tivoapps are supported in the '1.1' release.
Not that there's a software hack available publicly, no
I'm thinking that a hardware modification would still be in order before that patch can be applied. And I don't believe that this hardware mod something that the novice hacker could do on their own.
I've had my R10 hacked for months now (after a prom upgrade). It works great. Actually I modded at the same time a night-light S2 (TCD5400) using the same prom code.
(I had the work done by somebody with lots of soldering experience, as the procedure is a little tricky for a novice obviously)
I don't own a R10 so I don't know. So after prom update, you I assume can apply all the hacks just as you would with all the other D*tivos. I just thought that meant something when they say "It's the future R10 supported."
What he meant is the v1.1 of the Superpatch supports 6.1 and 7.2 units. About the future I guess it means that all sold DTivo units are not R10 (and thus 6.1)
Thanks. I've been wanting to include the backported drivers for awhile, but out of respect for Jamie and ADH, I wanted to wait until I had their permission to use them. Now that I have it, I'll include them in the next version.
Jasch, who did your prom socketing? Was it a friend, or someone who will do it for anybody for a fee?
It was a friend who does engineering work. But I've heard of people that has taken the tivo to repair shops to get the work done. Altough it's not cheap. I've heard quotes from $50-$100 (plus the cost of the prom kit, which is around $30-$40).
That's an expensive price tag just to be able to hack your tivo. But seeing that the alternative is to buy a probably used TiVo... it's the only way to go.
I guess it all depends on how much you want to hack it. I myself did it to MRV between my TiVo and SA units, as well as having Tivoweb, vserver (I have a MAC, so I have no TiVotoGo) and softpadding.
Does this tweak work with TiVo Series 1 boxes? I tried to install it, but got and error that said tar was not found when it tried to execute. Not sure why that happened since tar was used when I upgraded my box with tivoweb and tivoftpd using Jenkins. now it is saying it is not found. Very strange. I'd reall like to install this tweak as I think I just had the memory leak problem with tivoweb. Not sure, but would like to get it installed none the less.
Does anyone have any insight as to why this is happening? Any quidance and suggestions are welcome. Workarounds welcome too! I have full access to the web with my box and can get a reliable telnet session on the box.