With all the details of the steps, photos etc, its an ideal time to update the nztivo wiki with all the new detail.
Good to have your opinion on the 1.6.2 image. As far as nztivo are concerned at this point the recommendation remains the ame, use the specific NZ images. These are the images we test and will refine against the NZ emulator setup as it continues to evolve. Bottom line, the tivo functions the same at the end of the day.
1 x Philips TiVo Series 1, Cachecard, 1 x 1TB SATA (with recent TradeMe sourced adaptor), Mk II Pal Tuner Mod, NZ Emulator, Previously Dual A/V Source, Now Pay Satellite
2 x TiVo HD, Freeview, HNP, 2TB (WD-AV) jmfs upgraded
1 x Thomson UK TiVo, Cachecard, 200GB, Testing Work
Hi again DJC. It would really help to have a better understanding of the questions I outlined a while ago (that I couldn't find a response to) - see below. It would be ideal if these details could be included on the main sticky post at http://forums.oztivo.net/showthread.php?t=1167
This way, I could better weigh up the exact advantages (new features, bug fixes etc) vs the disadvantages (setting PAL tuner to NZ freq's and some more obscure postcodes that don't work is about all I can see) of using ozTivo instead of nzTivo.
I hope I am not being a pain - I don't mean to undermine or undervalue the work you have put into the nzTivo image, but, I guess I see the following advantages:
- A single australasian image to rule them all
Which means less work for you and more/frequent bug fixes and feature updates.
- It also means clear documentation (that ozTivo has) in the form of walkthroughs, logs of changes, lists of feature requests and bug reports/known issues etc. I think these are especially vital in community projects, when things do not always work as expected.
The approach I took to make daily calls via the modem, and still have network access to the tivo (for oztivo 1.6.2):
from the installer/nic_config_tivo, setup the TurboNet card (IP address, MAC etc)
edit /etc/rc.d/rc.sysinit.local
If this file does not exist you will need to create it, then make sure it is executableCode:dbrm /State/PhoneConfig DialPrefix dbsetx /State/PhoneConfig DialToneCheck 0
dos2unix /etc/rc.d/rc.sysinit.local (if created on a windows machine)
chmod +x /etc/rc.d/rc.sysinit.local
edit /etc/tclient.conf
where ispphone, ispusername, and isppassword are your ISP login detailsCode:127:ispphone:127.0.0.1:8000:ispusername:isppassword:
edit /etc/ppp-options
edit /etc/pap-secretsCode:user ISPusername
NOTE: it is a single TAB after each *, not spacesCode:* * ISPpassword
Hope this helps![]()
Bookmarks