6.3a & caller-id stops working

[100Tbps]

Hello,

Caller-id seems to intermittently stop working on my unit. I'm running a zippered 3.1 -> slicer-upgraded to -> 6.3a.

After a reboot, caller-id works fine. I guess an alternative to diagnosing the problem would be to edit the cron job to stop and restart the service each night, but I have no idea how to do this, nor am I sure exactly which service to manipulate.

I was originally using the caller-id tools local on the machine, but recently disabled the caller-id server so I could use my SD unit as a server and my HD unit as a client. My SD unit seems to work fine all the time, so I thought this might work. Since caller-id stops displaying on my HD unit whether or not it's configured to be a server (and it works just fine after a reboot, server or not), I believe this may not a failing of NCID, but perhaps the out2osd program - or at least that's my latest guess.

I'd really appreciate it if anyone could help me step through how to diagnose this or properly edit my cron file. Since I imagine stopping this might mean an external script to locate and kill one or multiple instances, this is beyond something I've done before - and am overly cautious when it comes to this device. Every bit of help is greatly appreciated!!

[cheer]

I seem to recall that out2osd was broken on the 7.x Tivo software, so it stands to reason that it's broken on 6.3a as well.

Your best bet would be to try using the text2ost version ("tivoncid" instead of "tivocid").

[100Tbps]

Thanks!

I've done some quick reading and may be missing something, but is this as easy as changing references in the ncid file from /var/hack/bin/out2osd to /tvbin/text2osd?

The INSTALL-TiVo link on this page: http://ncid.sourceforge.net/tivoncid/tivoncid.html doesn't offer a command example of how to invoke text2osd.

[cheer]

Thanks!

I've done some quick reading and may be missing something, but is this as easy as changing references in the ncid file from /var/hack/bin/out2osd to /tvbin/text2osd?

The INSTALL-TiVo link on this page: http://ncid.sourceforge.net/tivoncid/tivoncid.html doesn't offer a command example of how to invoke text2osd.
No -- it's much simpler than that. In your rc.sysinit.author, change your line that executes "tivocid" to "tivoncid" -- both are just symlinks to ncid of course, but ncid figures out what to do based on which alias you use.

EDIT: all of this assumes you're running the latest ncid package, of course. If you're not, you should be.

[100Tbps]

I really appreciate your assistance. I'm certain I don't have the latest ncid, so I need to look into installing it.

With what I have now, I modified the author file and rebooted, but the caller-id didn't work. I suspect it may be my ncid package is too old or I may have something else wrong. I'll experiment later tonight or through the weekend.

Thanks again!