TiVoNCID should call ncid-tivo, and it in turn calls /tvbin/text2osd, changeable in ncidscript.conf. If you find the problem and make any fixes, they will be incorporated in the next release.
Originally Posted by Narf54321
Yes, it needs to be set from sysinit. I usually set the path to include /var/hack/bin and /var/hack/sbin in /var/hack/etc/rc.hack which is called from rc.sysinit.author using this line:
It is also unreliable if you don't have the rc.sysinit.author PATH environment variable set to the ncid directory (usually /var/hack/bin ). Just setting it at your telnet prompt isn't enough, as it stops working once you log out.
I am thinking of changing the NCID location to /opt or /usr/local instead of /var/hack. This would be compatible with the rest of the world.
[ -x /var/hack/etc/rc.hack ] && /var/hack/etc/rc.hack
I firmly believe in testing so I agree. Take a look at the begining of ncid. Both tivocid and tivoncid are aliases and just set options. The running code is the same. Be warned, ncid code is tricky. The same script can be executed by shell, tcl, and tk.
I'll certainly willing to change the instructionsto tivocid, but I have gotten it working in the fashion described and I'd want to personally do a little testing to avoid unexpected glitches.
EDIT: Okay, I tried it with the tivocid utility instead of tivoncid and it bombs out. I had moved uni2osd back to my tivotools directory with a symlink called out2osd but it didn't work.
EDIT: Copying uni2osd back to the /var/hack/bin folder and re-symlinking it fixed the problem. I still want to give it a couple of days to make sure its all working proper and doesn't go zombie on me or anything.