New Software Updates Discussion Thread
- Thread starter RandallA
- Start date
- Latest activity Latest activity:
- Replies 588
- Views 67K
-
Server Issues. We are very aware that there have been system issues the past few days. In troubleshooting the system, it has been determined that the issue is at our provider and is hardware related. As of 12:05 PM ET our provider has moved us to a new server.
Things seem to be running better on this new server. However in trying to diagnose the issue (before finding out it was a hardware issue) we made some system changes which we need to undo. So if you find any issues or errors please let us know in the Operations Center Forum.
Thank you for your patience! Sorry for the issue!
CLICK THE X IN THE TOP RIGHT CORNER OF THE BOX TO DISMISS THIS MESSAGE
I don't think they can rollout an ammended L4.49. Your machine recognizes whether to install a new version based on receiver type, hardware versions(bootstraps, build configs), receiver number and superceeded software versions.
See RandallA's post
http://www.satelliteguys.us/1250666-post208.html
You're right, looking at the range it looks like most receivers have it. They now need to fix what they broke.
If it's the same software going out to all machines, why would some have problems and others not. I haven't experienced any problems.
You're right, looking at the range it looks like most receivers have it. They now need to fix what they broke.
I have a 722 that DOESN'T have 4.49 yet. The receiver number stop at about 845xxxxx, Mine is 855xxxxx. I guess I'm in the lucky group and don't mine waiting for a less broke verion of 4.49
Since the 449 FW was installed on my 722, I am noticing that some, but not all, DVR recordings do not go active when selected for START, or START OVER. They just sit there, showing a black screen, and not counting forward.
I have to do a 30 second Skip FWD, or regular FWD to kick them into action. I don't think I ever saw that kind of behavior before.
I have to do a 30 second Skip FWD, or regular FWD to kick them into action. I don't think I ever saw that kind of behavior before.
My other 211 boxes got the L3.47 update today. Tonight I'll hook one up to the router, setup the DishComm, then setup the broadband, and see if it all plays.
It'll be nice to get rid of the telephone cable running across the bedroom floor.
It'll be nice to get rid of the telephone cable running across the bedroom floor.
Are there multipler iterations of L449? Is there something akin to build levels within L449? My 722 shows the Software Version as L449RJKD-N .
L449RJKD-N is
L449 - current FW
RJ - family (722)
K - ? (perhaps PCB revision)
D - spooling batch ID
N - NVRAM as source of settings
L449 - current FW
RJ - family (722)
K - ? (perhaps PCB revision)
D - spooling batch ID
N - NVRAM as source of settings
No there are not multiple version of L449 sent out. The software version you mentioned also shows the Hardware Id. E.g, one of mine is RBDD-N. It is possible that L449 sent has code that detects and installs different portions of the code depending on the Hardware id. Or it might just adapt as it is running depending on your hardware. Noone who knows is saying.
If you look at the info posted in the Dish Tech discussion Forum,
http://www.satelliteguys.us/dish-ne...sions/104840-new-software-updates-thread.html
you will see that the info typically identifies
http://www.satelliteguys.us/1266164-post224.html
all hardware version (BOOTSTRAP AND HARDWARE BUILD)
'1[3-8]1[A-G0-8]' 'RB[BDEGHK-NP][A-DJ]'
and one software version, currentlly L4.49
'L449': 'ABA1'- 'CLL1' 'L040'- 'L448'
replacing all regular builds (L040-L448)(AND SOME BETAS(ABA1-CLL1)
At times, I think, they have rolled out fixes that don't identify all hardware versions to do a quick fix for just that version of the hardware.
Let me know how that goes due to I might replace my 411 to a 211 to get the Ethernet port. I have a 211 in my other room but kind of waiting to see how this turns out..
Thanks for the breakdown. I think your comments and tnsprin's have answered my questions, thanks.
First suggestion is wrong - there is no provision in FW do that way.
Second is correct with short correction - that 'adaptation' checking not the HW ID letters, but bits in HWConfigID ( from not changeable part of NVRAM what set at factory ).
L405 or P405
Sorry that wasn't clear.
Two separate PIDs,
P405 is going to all receivers with 'P050'-'P400'.
L405 is going to some receivers with 'P401'-'P404'
