ViP622 L4.04 Coming!

I had troubles with the receiver rebooting alot, when tuned to an OTA channel, sometimes up to 6 times a day. I don't know if this counts. I had email exchange with an Dish engineer about this, and they even sent me an USB stick to have the receiver dump a trouble report on it and then sent it back. Never heard anything again, though I asked for the results about what's wrong with my receiver. Doesn't mean I am included in the update. Still wanna know what's wrong with it though...:confused:
 
I have no OTA problems. Not bragging, just hoping I'm not tempting fate. And that 4.04 doesn't mess things up.
 
5/7/2007: 0959 Software Version L4.04 for ViP 622 DVR
Effective Tuesday, May 8th, Engineering plans to spool a PARTIAL PHASE of software version L4.04 for the ViP 622 DVR receiver. This is primarily a non-forced maintenance release available at ALL satellite locations.


At this time L4.03 and L4.04 will be the valid software versions for the ViP 622 DVR.
 
PID: 08AEh, ID: 3KDC, FW: P415, Model: DP311.
PID: 08B1h, ID: 1DKC, FW: L404, Model: ViP622
Mon May 07 23:16:31 2007

DETAILS:

PID=08B1h

DownloadID:'1DKC'
Upgrading FW:
'L404': 'ABA1'- 'BLA1' 'L040'- 'L402'
'L404': 'ABA1'- 'BLA1' 'L040'- 'L402'
New FW:'L404'
List of BootStraps and BuildConfigs:
'1[3-8]1[AB0-4]' 'RB[BDEGHKL][A-DJ]'
IRD Model: ViP622
List of Serial Numbers:
[2] 1-4000000000
 
PID: 08AEh, ID: 3KDC, FW: P415, Model: DP311.
PID: 08B1h, ID: 1DKC, FW: L404, Model: ViP622
Mon May 07 23:16:31 2007

DETAILS:

PID=08B1h

DownloadID:'1DKC'
Upgrading FW:
'L404': 'ABA1'- 'BLA1' 'L040'- 'L402'
'L404': 'ABA1'- 'BLA1' 'L040'- 'L402'
New FW:'L404'
List of BootStraps and BuildConfigs:
'1[3-8]1[AB0-4]' 'RB[BDEGHKL][A-DJ]'
IRD Model: ViP622
List of Serial Numbers:
[2] 1-4000000000

So if I am reading the Bootstrap info correctly, it applies to my box?
 
If I read it right, the boot strap would apply, but folks with L403 will *not* get it.

(correct me if I'm wrong, Smith, P.).

LER
 
If I read it right, the boot strap would apply, but folks with L403 will *not* get it.

(correct me if I'm wrong, Smith, P.).

LER



Yeah, I missed the note at the top that ends it with L402. Basically what they are doing is just making all boxes that dont have 403 yet get 404 instead since its the newest. But, the people with 403 working correctly, they do not need 404?
 
elwaylite said:
Yeah, I missed the note at the top that ends it with L402. Basically what they are doing is just making all boxes that dont have 403 yet get 404 instead since its the newest. But, the people with 403 working correctly, they do not need 404?

Yea, well I had 4.01 and what it didn't screw up, 4.03 did. What was previously a good solid receiver is now a POS that does screaming re-boots by itself multiple times a day.

For example, I DVR'd the Nextel race Sunday to watch later that night and it ended up recording in 4 separate chunks and of course missing spaces for whatever time it takes to go through it's foolish reboot cycle. It basically rebooted every hour during the race. This is NOT OTA either, it was the Dish local Fox.

And when it's not rebooting, the unit is often plagued with audio & video anomalies. Last night's "Heros" (OTA NBC) suffered terribly.

And before anyone mentions it, I know the rap about hard & soft resets and running checkswitchs.

And before the apologists jump in and say how "hard" Dish is working to fix this, let me remind people that having been with Dish 10 years and having seen them do this to too many other receivers thru the years, they have an established pattern of either releasing garbage hardware that they have to scramble to fix with updates or good hardware that they eventually screw up with updates.
 
I pay $130 a month and should not have a DVR, that can't be used as a DVR because of these reboots. Especially the $6 for the DVR service enabled. This is BS. If ya can't do it, then LEAVE IT!:mad:
 
And before the apologists jump in and say how "hard" Dish is working to fix this, let me remind people that having been with Dish 10 years and having seen them do this to too many other receivers thru the years, they have an established pattern of either releasing garbage hardware that they have to scramble to fix with updates or good hardware that they eventually screw up with updates.

Still don't understand the screaming reboot problem. I have two 622's that haven't skipped a beat since L4.03. Most people are not having this problem. So to call the hardware or software garbage is not a completely true statement. With electronics there will always be lemons. And with a setup anything can go wrong. Maybe your receiver is suspect and needs replacement. Maybe even something else wrong. But you can't say that the whole lot is bad. Most people, including me are pretty happy with the 622.
 
Still don't understand the screaming reboot problem. I have two 622's that haven't skipped a beat since L4.03. Most people are not having this problem.
None of those problems here either (knock on wood).
So to call the hardware or software garbage is not a completely true statement. With electronics there will always be lemons. And with a setup anything can go wrong.
When a number of people here have the problem -- and people here are a tiny fraction of Dish customers -- it does suggest a more widespread problem than just a "lemon" here and there.

Dish rushed out L4.01 with too many problems. Since, they've put out (3) band-aids in just over a month to try and fix things.
 
I've had mine reboot a couple of times the last few days while watching it.I did notice Sunday when it done it was when the 3rd tuner kicked in to record, it rebooted but when it came back on all three shows was recording.
 
Still don't understand the screaming reboot problem. I have two 622's that haven't skipped a beat since L4.03. Most people are not having this problem. So to call the hardware or software garbage is not a completely true statement.

My guess is that the OTA problem is caused not so much by the receiver but by slightly non-standard broadcasts. I found I experienced reboots much more often with one OTA station than I do with others. Luckily the problem has since disappeared, but when I first got my 622 anytime I tuned to that one station it would lock the receiver up and reboot within 5 minutes.

Ideally the receiver should be immune to such things, but a single station doing things in an unexpected way may cause unexpected problems.
 
I had no problem with any of my OTA until, the upgraded from 3.66 to ver 4, ever since then, even if I get a 98 signal on the tv side, the best I can get is 72 with numerous dropouts through the 622, now if Dish would bring my locals in HD I wouldn't even use OTA
 

n00b with some issues/questions

Switch or receiver

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)