: Bell TV 9242 Firmware Update V187 (Sept 15, 2010))
2010-10-03, 03:45 PM
I disagree considering that there was nothing wrong with the receiver before the update. Since the bell menu does not offer an option to split downloading of the firmware and the programming information, they are forcing us to update the firmware, potentially rendering our equipment unusable.
If your had your car serviced and the mechanic damaged something in the process of said service, are you obligated to pay for the repairs?
Anyone who knows about electronics understands the risks of flashing equipment. Its risky business. My pvr failed to re-initialize after the firmware and was frozen on the "attention" screen with the progress stuck at 2 of 5.
Considering that bell is aware that owners of 9242 are having problems after the firmware update and they have a history of such issues,
they need to be accountable to protect their customer base. They will simply take my PVR and re-flash it and send it back into service
on my dime.
The gear is only part of the issue. What about all the programming that will be lost?
One might argue that since it wasn't watched during the scheduled broadcast but instead recorded, it was "consumed" and therefore no longer the responsibility of bell. Well under normal circumstances I could accept this argument, but when a firmware update results in lost programming I'm much less inclined to agree particular when the PVR feature is the prime selling point for their service.
Many have lost programming which is akin to not having service at all. It was not viewed and enjoyed therefore the user did not benefit from the satisfaction of the service.
I should have paid for the extended warranty from FS.
2010-10-03, 04:56 PM
If the problem was as widespread as you imply, Bell would have updated the software again, just like they did earlier in the year.
I am sure that if they are aware, a fix will be issued soon.
What have Bell told you when you called them to make them aware.?
2010-10-03, 07:31 PM
I don't think 8 people that I personally know constitutes "wide spread", however my four colleagues (locally) and friends in London(2), Kitchener(1) and Ottawa(1) have all had very similar occurances. One friend is a level 2 bell tech. The statement "Bell is aware" is just that. They know that some customers have experienced issues. You can report that to your bell boss. The tech on the phone certainly did not confirm the issue, but they would not deny it either.
2010-10-03, 11:37 PM
No problems before or after the update - so far - touch wood - my 9242 has never frozen or hiccuped in the least. I have a Lacie 1TB drive attached [no delay when hitting the show recordings button - the hard drive is always on]
2010-10-04, 12:32 AM
They will simply take my PVR and re-flash it and send it back into service on my dime.
Do you know a way to force the PVR to receive again the last firmware? After all i did (reformatted the hard drive, clear NVRAM), i don't know if receiving it again will not correct my problem.
If Bell only do that and after, sold it like a refurbished, if i can do that by myself, i want to try it.
2010-10-04, 09:47 AM
I don't think there is anyway to do that. I haven't noticed any changes at all with the last firmware update. No problems here.
2010-10-04, 10:19 AM
I have 2 x 9242's and they work just the same as before, nothing changed.
The firmware cannot be rolled back, it would be better if the newer receivers had an option in the menu like the older ones, where you could choose to update or not. My 3100 is still running an old version as I have it set to not accept new updates, it still works fine.
I used to let others update, wait a few weeks to see if it screwed up, then accept, shame we cannot do that now.
2010-10-04, 12:54 PM
my 9242 with V187 is working fine. For those with a 9242 that is freezing do you have a lot of timers set up? How about VuPass timers?
2010-10-04, 12:55 PM
Sunday morning, sometime before 7am the receiver restarted and wouldn't boot. I let it run until 12 noon like this as I was fed up. Unplugged the unit and it restarted and has been running ever since.
As far as flashing the eeprom, we would typically have to pull the chip and reprogram it on an eeprom programmer attached to a pc via a serial connection. I'm not familiar with with bell's newest receivers as I haven't worked on any of them since the early 2000's. Occasionally, when we had a bad flash, the device was damaged due to it running in a mode that it wasn't intended causing excessive heat buildup. In other cases re-flashing the equipment fixed the issue. What I'm saying is that simply re-flashing the unit's eeprom chip(s) may not be enough. This works if the chips can be removed from a socket and easily replaced. If the chip is integrated on the main board removing the chip is very tricky and delicate and in most cases not worth the effort.
when we flashed modems in our modem pool and the firmware failed, we just tossed the modem because the chip was not removable or it wasn't compatible with the eeprom programmer we used.
ruserious: I only had three timers set. Stargate Universe (not active as new the new season had not started), cash cab and Nakita.
I only allowed the update to proceed to get the new programming for discovery and space. Problems started immediately after.
2010-10-04, 02:14 PM
I got a different freeze problem last night. Was watching a show from the PVR at the same time as it was recording (started watching about 20 minutes late). When the show finished recording, the screen froze with the last viewed frame from the show. I could go back to the PVR menu to try to restart it but anything I chose went back to the frozen screen from the show. Finally I chose another recorded show and that "unfroze" it. Went back to the original show and could now restart it from the beggining and FF to where I was.
Never seen this before the update and I watch shows while they are recording all the time.
NOTE to all. Lets stick to the topic at hand which is the latest firmware update.
With regards to those having freezing issues. My guess is that this is a hardware issue and not a firmware issue.
If this was an issue caused by the recent firmware update then we would likely have hundreds of complaints in the first few days after the update.
My advice for those having problems is to reboot your receivers, check your signal strength and your wiring, and if you are still having problems then call Bell.
2010-10-04, 09:23 PM
Sorry Hugh, but i not alright with you.
At this time, we can say the new firmware cause the hardware problem that we talked.
Gpicard, I'm sorry but I really have no idea what your saying.
2010-10-05, 10:35 AM
I understood you
2010-10-05, 11:51 AM
Sorry Hugh, but my english was not good.
I don't know the correct word but, i just wanted to say that i don't think like you.
For me, firmware have a direct link with the hardware. If many people have problem with the hardware after a firmware update, we can report it in a discussion about that firmware.