[schneid]

I have been reading about the 0x0251 roll out beginning 07/09 but when I check the HR20 firmware site:

http://www.redh.com/dtv/index.php?r=HR20

it shows 0x0235 is the currently available National Release. It also shows 0x0251 was up on the bird until 18:31 on 07/09.

The HR21 firmware site shows similar information with 0x0235 being the currently available National Release.

Was the release canceled and pulled down?

 

[bobnielsen]

It looks like that might be the case (it happened once before when some problems were discovered with a NR). The current CE (0x254 for the HR20; 0x255 for the HR21) is another NR candidate.

 

[BuffaloDenny]

It looks like that might be the case (it happened once before when some problems were discovered with a NR). The current CE (0x254 for the HR20; 0x255 for the HR21) is another NR candidate.

Good. Too late for me, but this release is garbage. Worst update experience I've had since being on this box. Besides losing OTA's, for me, the guide and channels are slower than before, but the kicker was losing media share. I usually look forward to NR because of enhancements and new features, but I'm very disappointed with this one.

 

[tonyd79]

The sad thing is that x251 was not tested in the CE program. Why would that be? They obviously introduced some issues in 251 that were not in 250.

 

[cartrivision]

The sad thing is that x251 was not tested in the CE program. Why would that be? They obviously introduced some issues in 251 that were not in 250.

Yep, that (going NR with a non-CE release) should NEVER be done in any case, and especially not done given their track record of inducing new bugs with their "fixes".

 

[Carl Spock]

You're assuming DirecTV doesn't have another avenue of software testing beyond CE. I don't know that. Does anybody?

All in all, I will be glad to see 0251 go. I had my one instance of the dreaded lockup/control slowdown with 0251.

 

[GregLee]

The sad thing is that x251 was not tested in the CE program. Why would that be? They obviously introduced some issues in 251 that were not in 250.

That's not obvious. Maybe 251 was just the same as 250, except for the number. Why give the same software a different number? (1) Why not? (2) Any known issues in 250 would not be known issues in 251 (until rediscovered).

 

[hdtvfan0001]

Yes, DirecTV pulled the plug on 0251 very shortly after it started, due to a bug that was identified and needed repair.

A replacement is being tested internally and in the CE cycle. Hopefully, that new update will be forthcoming "soon".

 

[ToddinVA]

Yes, DirecTV pulled the plug on 0251 very shortly after it started, due to a bug that was identified and needed repair.

Just one??? :lol:

 

[Doug Brott]

I have not verified if 0x251 is still available or not, but we are testing a new CE at the moment that is also a national candidate.

 

[Mike Bertelson]

The sad thing is that x251 was not tested in the CE program. Why would that be? They obviously introduced some issues in 251 that were not in 250.

Yep, that (going NR with a non-CE release) should NEVER be done in any case, and especially not done given their track record of inducing new bugs with their "fixes".

I don't for a second believe CE is the only testing program Directv has.

As beneficial as the CE program is, you can't think it's the benchmark. IMHO, it's merely a way to test some things in the real world beyond official testing.

What's the percentage of CE'ers to the total subscriber base? Pretty small.

Heck, I'm kinda surprised (happily) that they do it at all.

Mike

 

[SPACEMAKER]

So I'm stuck with 0x235 for longer. Well that's just [Mod Edit] wonderful.

 

[Ken S]

So I'm stuck with 0x235 for longer. Well that's just [Mod Edit] wonderful.

Spacemaker,

If someone at DirecTV pulled the 0x251 release you have to believe they felt that was worse than staying with 0x235. It's a positive sign that someone there cares enough to yank an outgoing NR.

 

[SPACEMAKER]

Spacemaker,

If someone at DirecTV pulled the 0x251 release you have to believe they felt that was worse than staying with 0x235. It's a positive sign that someone there cares enough to yank an outgoing NR.

I agree. But I 0x235 is so terrible that I was looking forward to the new update. Also it appears that 0x251 was pulled due to problems with media share which is something I do no care about.

 

[Ken S]

I agree. But I 0x235 is so terrible that I was looking forward to the new update. Also it appears that 0x251 was pulled due to problems with media share which is something I do no care about.

Nahh...as bad as mediashare has been over time I doubt they pulled because of a problem with that function. I would think it was something that may have resulted in data loss or a security issue with the release. Maybe they left a port open they don't want out there?

 

[hdtvfan0001]

Just one??? :lol:

One showstopper....

 

[ATARI]

I've been reading a lot of problems with OTA and 0x251.

Could that be the showstopper?

 

[texasbrit]

I've been reading a lot of problems with OTA and 0x251.

Could that be the showstopper?

I don't think 0x251 has any new OTA issues...

 

[hdtvfan0001]

I don't think 0x251 has any new OTA issues...

Regardless of the issue - the plug on 0x251 was pulled and it will be replaced with another release as soon as it clears testing.

 

[cartrivision]

That's not obvious. Maybe 251 was just the same as 250, except for the number. Why give the same software a different number? (1) Why not? (2) Any known issues in 250 would not be known issues in 251 (until rediscovered).

In the past, the NR has had the same version number as the CE so I think that it's safe to assume that the bumped version number means that changes went into the NR version that did not go through the CE testing process.