Confirmation I'm an ***** please.

[VoR]

I've been having trouble with my DTiVo and suspected its the Power Supply, but also thought I could have a bad .bak.

So I wondered over here to find a new image to try. After reading the FAQ download and seeing this on 25Xtreme:

"The only caveat is that you may want to keep the phone line disconnected to prevent inadvertent software upgrades from downloading automatically and overwriting the 2.5Xtreme software."

I assumed I'd be okay letting the DTiVo call in since I have a legit sub (monthly). To enable TiVo recording.

After not being able to get passed the "TiVo service not avalable until call is made" msgs I came back today to read somemore and see people saying "NEVER let your Xtremed TiVo call in"

Is this true even though I have not done anything with bash etc?

The OS is now up to 2.5.2.


I am still thinking something, power supply or otherwise is bad as I had to reboot the system by pulling the plug after many self reboots and then getting stuck on the upgrading software screen. I'm asumming my .bak file is bad or there's something (missing?) in Xtreme that is letting my DSR6k boot.

PS I've tried 3 drives, cleaning white ribbon, new IDE cables. :confused:

[rd001]

Originally posted by VoR

After not being able to get passed the "TiVo service not avalable until call is made" msgs I came back today to read somemore and see people saying "NEVER let your Xtremed TiVo call in"

Is this true even though I have not done anything with bash etc?
I always had the impression that the more knowledgable people here said that it didn't matter if you ran Xtreme as long as you subscribe.

The primary reason not to allow an Xtreme'd Dtivo call in is when you've installed fixsub to evade legitimate service. A secondary reason is to avoid receiving software updates.

But I don't claim to be an expert and am sticking with 25Xtreme for now. No 2.5.2 for me just yet.

[rpongett]

I'm in the same ***** boat, but I one-upped you in that department. After getting locked out with 3.1, I ran kill_initrd and decided -- since I never got around to doing it -- I would install 25xtreme. As I found out, it wiped out everything (not just OS data but my videostreams, too). I had to reinstall turbonet just to get bash access, then I installed Kraven's update.

Now, I actually WANT to get 3.1 (and I'll have to run kill_initrd again, I know), and can't. My Tivo now isn't making its service calls. I'm pretty sure its because Kraven's update sets the device to net0 on purpose so it won't update.

Problematic is that: (a) I'm not sure that's the problem (turbonet being set to net0) and don't know how to find out; and (b) I have zero idea how to change it back to eth0 (I'm new with this stuff and need lines and location to enter).

[VoR]

Originally posted by rd001
I always had the impression that the more knowledgable people here said that it didn't matter if you ran Xtreme as long as you subscribe.

This appears to be correct after all. Phew! Came home to a working TiVo again. Much thanks to those that made the FAQs and hosted the images.

I am still extremely weary of the PS (or something) but so far it's up for 12 hours.

Could the main power cord be bad?