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.bobnielsen said: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.
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".tonyd79 said: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).tonyd79 said: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.
Just one??? :lol:hdtvfan0001 said:Yes, DirecTV pulled the plug on 0251 very shortly after it started, due to a bug that was identified and needed repair.
tonyd79 said: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.
I don't for a second believe CE is the only testing program Directv has.cartrivision said: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".
Spacemaker,SPACEMAKER said:So I'm stuck with 0x235 for longer. Well that's just [Mod Edit] wonderful.
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 said: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.
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?SPACEMAKER said: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.
One showstopper....ToddinVA said:Just one??? :lol:
I don't think 0x251 has any new OTA issues...ATARI said:I've been reading a lot of problems with OTA and 0x251.
Could that be the showstopper?
Regardless of the issue - the plug on 0x251 was pulled and it will be replaced with another release as soon as it clears testing.texasbrit said:I don't think 0x251 has any new OTA issues...
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.GregLee said: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).