Check my post about 43 recordings being bad. Do an RBR and watch the bad recordings go away. Hopefully this should help with new recordings.
Thanks, I do remember reading that now. That stinks. I did a RBR, but I am afraid to rely on it now. I had just begun to phase out the old HR10, but it looks like I am going to be relying on it a little longer.jgrade said:Check my post about 43 recordings being bad. Do an RBR and watch the bad recordings go away. Hopefully this should help with new recordings.
I've done a full disk check and format, and I had the problems immediately afterwards - I was gone for a week and only about 40% of my recorded stuff was watchable.elvisizer said:if it keeps having problems with unplayable recordings after resetting it, do a full format and disk check. you will lose all your recordings and settings. if problems continue after formatting, request a new dvr from d*tv.
Thanks, I made sure to get everything off this weekend and I will reformat if it happens anymore. I just thought that it was strange that no problems and then WHAM!!! Hit all at once. Wondering if there was some condition that caused it.elvisizer said:if it keeps having problems with unplayable recordings after resetting it, do a full format and disk check. you will lose all your recordings and settings. if problems continue after formatting, request a new dvr from d*tv.
What are you basing that belief on?dukefan said:I've done a full disk check and format, and I had the problems immediately afterwards - I was gone for a week and only about 40% of my recorded stuff was watchable.
I do not believe that this is a hardware problem. Even if it were, why should I get a refurbished box just weeks after paying for a brand new one?
that's the million dollar question. if d*tv could answer it, we'd all be much happier.jclark said:I just thought that it was strange that no problems and then WHAM!!! Hit all at once. Wondering if there was some condition that caused it.
Sorry, I am convinced we are still seeing many issues caused by software defects. While it is possible dukefan also has hardware/installation/cabling/karma issues, when I analyze the entirety of the data, anecdotes, and facts, I'm still left with major software defects. Alas, I'm not in possession of any data not available here; perhaps there is something known by Directv that could convince me that the software is adequate.elvisizer said:What are you basing that belief on?
you've eliminated the software on the HR20 as a possible source of the problem by doing the full format. the only other options are that the HR20 has hardware issues and you need a new one, or HDTVFAN001 is finally right for once, and you've got issues elsewhere in your install- bad cabling, multiswitch, dish, or LNB.
I did not mean to imply that all software issues are gone. On the contrary, I thought I was highlighting the extent to which software issues are still with us.tibber said:Sorry, I am convinced we are still seeing many issues caused by software defects. While it is possible dukefan also has hardware/installation/cabling/karma issues, when I analyze the entirety of the data, anecdotes, and facts, I'm still left with major software defects. Alas, I'm not in possession of any data not available here; perhaps there is something known by Directv that could convince me that the software is adequate.
My opinion, all are welcome to share it or dispute it.
Cheers,
Tom
As so many of us... Been there, done that!elvisizer said:that's the million dollar question. if d*tv could answer it, we'd all be much happier. in my recent experience, i was having lots of problem recordings. Then I did a full format while on FA, and didn't have a single bad recording for over a month. then 10b got pushed out to me, and ever since i've had more problems creeping back in. So, in my case at least, it's been related to firmware updates. I'm going to do another full format later this week, and if i'm still having problems after that, i'll be requesting a new HR20 from d*tv.
Sure, it could be any of those. It could also be fairies living in my house.elvisizer said:What are you basing that belief on?
you've eliminated the software on the HR20 as a possible source of the problem by doing the full format. the only other options are that the HR20 has hardware issues and you need a new one, or HDTVFAN001 is finally right for once, and you've got issues elsewhere in your install- bad cabling, multiswitch, dish, or LNB.
I hope by now you've come to the realization that you can get just about any answer [you want] from D* whether right or wrong. I've had a level 2 supervisor give me wrong information [we would be getting OTA in Feb. if she was right].dukefan said:P.S. And DTV does classify it as a software bug when you report it through Level 2 support...
Good luck in trying to do that, you will likely grow very old trying. Many of the behaviors of the bugs documented act like poor state management, resource management and basic exception processing logic. The HR20 bugs remind me of inexperienced programmers, working on IPC and threading, attempting to do asynchronous programming in constrained systems. The bugs feel like function calls are made and return codes are not checked for exception processing, this is where some child process or functions are failing but the parent just keeps on going like there is no problem. This kind of problem can happen when resources are constrained, there is poor memory management, leaky code, or bad garbage collection. There is no way of knowing for sure with out having access to the OS, code and debuggers, but this kind of "random" presentation of similar defects, does walk and quack like a duck.veryoldschool said:... I'm still leaning toward poor hardware, until I can get two units to misbehave the same. So far, each has acted differently in my testing. #4 is on the way.
You seem to be a software guy. I'm from the hardware side.btmoore said:Good luck in trying to do that, you will likely grow very old trying. Many of the behaviors of the bugs documented act like poor state management, resource management and basic exception processing logic. The HR20 bugs remind me of inexperienced programmers, working on IPC and threading, attempting to do asynchronous programming in constrained systems. The bugs feel like function calls are made and return codes are not checked for exception processing, this is where some child process or functions are failing but the parent just keeps on going like there is no problem. This kind of problem can happen when resources are constrained, there is poor memory management, leaky code, or bad garbage collection. There is no way of knowing for sure with out having access to the OS, code and debuggers, but this kind of "random" presentation of similar defects, does walk and quack like a duck.
Well, this is the only glitch that I have had since xFA. I think that something happened to put it in a bad state. I was just afraid that the box was going bad. Everything seems to be working fine again.Bay CIty said:5 of 6 shows did not record- WOW-what a confidence builder this is.