Tivo upgraded (nuked) my (hacked) upgrade...ouch

[rob_gendreau]

I have a series 1 DSR6000 Directivo into which I installed a TurboNet card and the various hacks, mainly so I could run TivoWeb and TivoTool (vserver Mac). After a long absence I returned and discovered no access (telnet, http) to my Directivo...it apparently was upgraded to System 3.5. If memory serves, this means it installed the new system on a partition and used that to boot...so is my old hacked system available on the other partition, and how do I get the Directivo to boot from it? (I seem to recall there were some numbers you could enter with the remote during the Directivo's boot sequence to do something like that.)

If I do succeed in doing that, I'd be back to an older system, but I guess at least I'd have access again, etc. Should I then apply the same hacks to the partition with the new system? I've got a hard drive backup and a tivo.bak as well. And how do I avoid this happening again?

I noted that my Directivo is still making "phone" calls over the Turbonet card...unless the elves inside it purchased a cellphone while I was gone, since there's no phone line attached. Anyway I could access it that way? I just used to get in via telnet to a static IP address I assigned it, but that's not working. I mean if it can call Tivo, how do I call it?

TIA,
Rob

[puffdaddy]

I have a series 1 DSR6000 Directivo into which I installed a TurboNet card and the various hacks, mainly so I could run TivoWeb and TivoTool (vserver Mac). After a long absence I returned and discovered no access (telnet, http) to my Directivo...it apparently was upgraded to System 3.5. If memory serves, this means it installed the new system on a partition and used that to boot...so is my old hacked system available on the other partition, and how do I get the Directivo to boot from it? (I seem to recall there were some numbers you could enter with the remote during the Directivo's boot sequence to do something like that.)While the old /root partition and kernel is still present, the modifications to the MFS database are not backwards compatible, and the unit will most likely barf if you attempt to boot from the old root partition.
If I do succeed in doing that, I'd be back to an older system, but I guess at least I'd have access again, etc. Should I then apply the same hacks to the partition with the new system? I've got a hard drive backup and a tivo.bak as well. And how do I avoid this happening again?Set up your bootpage correctly (i.e. "upgradesoftware=false") and don't let your unit phone home. Though, I think that you'll want the need 3.5 software and 3.5 will very likely be the very last version for S1 DTiVos--so you'd probably be alright ever if you don't correct your bootpage.

I noted that my Directivo is still making "phone" calls over the Turbonet card...unless the elves inside it purchased a cellphone while I was gone, since there's no phone line attached. Anyway I could access it that way? I just used to get in via telnet to a static IP address I assigned it, but that's not working. I mean if it can call Tivo, how do I call it?Telnet? How did you hack your unit originally? If you used some automated script (Xtreme25), then it probably set the dialing code to instruct your unit to make it's daily call over the network adapter. If this is the case, then you might have some reading to do, as there's no longer a maintained auto-script for S1 v3.5.

Good luck

[rob_gendreau]

Thanks for the help.

In the end, it was just easier to yank the drive and re-hack it. My /var/hack directory remained on the partition it was placed on; both my active and inactive partitions on 4 and 9 had the new software from Tivo.

Everything's easier the second time; I agree that there's a little chance of another upgrade for this unit (fine with me).