Originally Posted by wajo
There's still an open question whether or not these DVDRs can be returned to a previous FW after a machine takes on the newer/different Model No. TV123 just *might* be the first here who has to answer that question if his problem continues?
IMO, IF the FW can be "reversed" it should take OK. If not, I believe it'll just spit the FW disc out?
I think answering that reversal question is an important element in deciding whether ot not to update, i.e., peace-of-mind if possible to reverse.
Originally Posted by JoeKustra
You're hurting me. But I'm here for you. Yes, I just performed the 2160A update for the finalize cure. No problem. I had to do the rescan and verify the date. My schedule was wiped, but titles were not harmed. Going to the V2160A was the same. I set it to auto clock to test PBS tonight.
I have no problems. I never did, but just want to help. I'll switch back (up) tomorrow. In summary, you can apply either update at any time but can not go back to the factory firmware. Someone else will have to prove me wrong on that.
Thanks, Wajo & Joe for the reassurances. Since I updated my (previously completely reliable) 2160a a little over a week ago, it has had freezes
- searching for a time signal,
- playing back a timer recording,
- recording a timer recording,
- when I pressed the power on button,
plus random appearances and disappearances of military time. I will miss the title naming and skip-a-day flag, but they really didn't do anything for me if I need to reenter my timers every day or two.
I still had the file from April 2010 that I was previously operating with, and I just installed it and reset. Everything looks normal, but time will tell.
But I noticed one thing. In the instructions from April 2010 (and in Wajo's post #8946 announcing it), it said to do a skip-654 and then insert the disc. In the new upgrade instructions, it just said to set the unit to DVD and insert the disc. Any idea why the difference/is it significant? I found the help entries on the skip codes but didn't see anything about that one.
Again, thanks for the help. I'm hoping if anyone else has similar problems, we might be able to narrow down a cause.