Five months to the day since 6.3e!

[chuckg]

on my primary receiver. A week or so after it was activated on my secondary receiver which quickly started rebooting.

And my primary receiver rebooted that evening.

DirecTv is to be commended for the clairity and timeliness of their acknowledgement of this problem. :rolleyes:
DirecTv is to be commended for the swiftness they have demonstrated in resolving this issue. :rolleyes:

Me, for the foreseeable future, I will just use Series 2 DLB DTivos running 6.2a. Provides everything (and more than) I need for TV viewing.

[patonenow]

I agree exactly. All D* has done is given the perception to all that they are working on the problem and will fix it "someday". I firmly believe that they will never fix it because they very well know that would consist of buying new hard drives for all and possible expense to install them for some also. So they offer you the R15 and new commitment as their answer. And yeah I know they could be sued because they in effect voided their contract by pushing that 6.3E download on you and causing problems and I feel strongly that a judge would overrule any arbitration clause and might even let it go to a class action status. But how many are willing to file papers to do that and that is my point. They know not enough would have the guts to get involved and so it stays as is now.
But you as many can see how D* ethics really stand out on this issue.

[wedgecon]

I agree exactly. All D* has done is given the perception to all that they are working on the problem and will fix it "someday". I firmly believe that they will never fix it because they very well know that would consist of buying new hard drives for all and possible expense to install them for some also. So they offer you the R15 and new commitment as their answer. And yeah I know they could be sued because they in effect voided their contract by pushing that 6.3E download on you and causing problems and I feel strongly that a judge would overrule any arbitration clause and might even let it go to a class action status. But how many are willing to file papers to do that and that is my point. They know not enough would have the guts to get involved and so it stays as is now.
But you as many can see how D* ethics really stand out on this issue.

This assumes that the hard drives are the problem and it has been proven by me and many others that this is not a hard drive issue but a software issue. This whole "the upgrade revealed flaws in the drive" stuff is just crap. Even with a new hard drive 6.3e will cause rebooting problems and puting 6.2a on an old drive "fixes" it.

[patonenow]

You're right that it was the new version of software that caused the problem.BUT it wrecked the present hard drives so that one HAD to put a new hard drive in and then use the 6.2 or 6.2a version. At least in many cases so that is why I say what i did-in total of a fix.
Maybe off the subject but today I just got news that TIVO won the case against DISH and now DISH has a permanent injunction against it so no more use for them to use it anymore.

[wedgecon]

You're right that it was the new version of software that caused the problem.BUT it wrecked the present hard drives so that one HAD to put a new hard drive in and then use the 6.2 or 6.2a version. At least in many cases so that is why I say what i did-in total of a fix.
Maybe off the subject but today I just got news that TIVO won the case against DISH and now DISH has a permanent injunction against it so no more use for them to use it anymore.

This is a software problem, it does not "wreck" the drive in any way. All DirecTV has to do to fix the problem is figure out where where their code is messing up and fix it. Then they just download the corrected software version to the drives and force a reboot at 2:00 AM like normal. Once a fixed software version is on the DirecTiVo it will be fixed, no need to physically swap out users drives. The problem is it just takes them forever to figure out what is wrong and fix it. Hopefully the next software release will go through a better QA process than the last one did.

Many of use fixed the problem on our own by removing the drives and either putting an old software version on the existing drive or a new drive, but that was our choice, DirecTV does not need to do this.

In my case I bought a used Phillips DSR7000 to replace my R10 so I could get a hacked unit along with fixing the 6.3e problem. After I got the hacked DSR7000 working I stooped all recording on the R10 and kept it until I had watched all of the shows recored on it. Before selling the R10 I took out the drive and put 6.1 on it and advised the person I sold it to not to plug in the phone line.

What was weird was that once I got rid of all season passes & wish lists and cleared out the to do list I no longer got any reboots during the month or so it took to watch all of the recorded shows.

[CrashHD]

Before selling the R10 I took out the drive and put 6.2a on it and advised the person I sold it to not to plug in the phone line.


Did you also advise them that by putting 6.2a on an R10, it is effectively broken?

[wedgecon]

Did you also advise them that by putting 6.2a on an R10, it is effectively broken?

Woops I meant 6.1, I verified that it still works before shipping.