Back in December, DISH sent me a replacement 722k to replace my old one that had problems unrelated to this thread.
After setup and several transfers from a HD to the replacement, I tried to use the Groups to organize.
Every one of the fifty groups was populated with what appeared to be data strings. These contents could not be deleted, so groups could not be used.
I contacted DISH about the issue, but since the unit was working ok otherwise, I told them I preferred to wait to exchange it until I once again could clear the unit's storage.
Now, four months later, I requested another replacement. Certain that the previous issue was a fluke, I didn't check until after re-setting up over 60 timers in the new replacement.
The new replacement has the same problem, except that the December unit displayed ASCII characters while the new one has all of the Groups filled with machine language characters.
Like before, the entries cannot be deleted. It has to be something in their refurbishment process that causes this.
Has anyone else seen this?
Is there anyway to get past DISH tech support to reach someone who might actually understand what's happening?
Thanks
After setup and several transfers from a HD to the replacement, I tried to use the Groups to organize.
Every one of the fifty groups was populated with what appeared to be data strings. These contents could not be deleted, so groups could not be used.
I contacted DISH about the issue, but since the unit was working ok otherwise, I told them I preferred to wait to exchange it until I once again could clear the unit's storage.
Now, four months later, I requested another replacement. Certain that the previous issue was a fluke, I didn't check until after re-setting up over 60 timers in the new replacement.
The new replacement has the same problem, except that the December unit displayed ASCII characters while the new one has all of the Groups filled with machine language characters.
Like before, the entries cannot be deleted. It has to be something in their refurbishment process that causes this.
Has anyone else seen this?
Is there anyway to get past DISH tech support to reach someone who might actually understand what's happening?
Thanks