syphix said:
Anything new? A quick bug fix of some sort?
Good tidings and cheer, fairy dust, and raspberry marmalade.
No, but seriously, I believe any hardware/software type company that's worth their salt
will tell you what's in an update. For example, just last week I purchased a new GPS receiver from Garmin. Even though the thing works
flawlessly right out of the box, I went to the company's page for the product to check if I had the latest firmware/software. I was not surprised to see that they have an
extremely detailed log of the updates the product has received. That's the way a company
should operate; receive feature or bug complaints, address the issues, release the updates, and tell the consumer what's been fixed or changed. How the hell am I supposed to know if Dish has addressed any of my (many) complaints? What, should I just keep on beta testing this piece of garbage and try to see for myself? What would be so hard about listing what the complaints were, and what the update fixes? Well, that's a rhetorical question, really. I know why Dish doesn't say what's in the software updates (and so do all of you). If they were to say what's in the update, that would create some serious problems for Dish. First, they would end up publicly admitting that their crappy receivers are riddled with bugs. And that can't be good for business. Second, when they release an update that doesn't fix a known problem (something that happens
every time they "update" the 522), people would no doubt question, "Hey, Dish, why didn't you fix problem 'XYZ' in this last update?" Third, we all know that every Dish update creates more problems than it solves. But even though I say that we "know" that, we really don't have any documentation to back it up. It's more of an anecdotal observation, really. See, this way they can kind of leave everything up in the air. No one on this side of the fence really knows
what Dish considers to be the problems/bugs with the 522 (or any of their receivers, for that matter). But if Dish were to start publicly documenting what every update "fixes," it would leave a nasty trail for observant customers like me to follow. So if the 522 never had a problem with guide button reboots (which it didn't), and then all of a sudden it develops the problem after an update (which it did), an update log would set in stone that the problem was
created by an earlier "update." It would publicly illustrate the ineptitude that exists in the development of the 522. They would look really, really stupid. And I suppose they just don't want to look
that stupid...even though they do anyway.
