I have a Dish Network 522 DVR, and ever since the NBR software update I've never gotten any sort of recurring event timer to work correctly. (Software version: L232-GALD-N).
Once a make an All Episodes, New Episodes, Daily, Mon-Fri, Weekly, or a DISH pass timer it searches for events that match the criteria and makes the appropriate timers (which in my case would be whenever the show plays within about 44 hours of when I make the timer). But it doesn't seem to ever search for new occurances of the show after that first search when making the timer. So a "Monday-Friday" timer will work the first day, and the second day after I make it, but after that it doesn't do anything, so I have to delete it and re-make it all over again every day or two days. This is a serious "downgrade" for me, as the "dumb" timers in the previous version (pre-mid-December) worked fine for me, albeit as expected they would record whatever was in the time slot they were set for even if it wasn't the program I wanted.
Unfortunately, when I noticed the new features I deleted all my existing "dumb" timers for my favorite shows, thinking that the new timer system would be better.
Is anyone else having this problem, and is there a way to fix it or create "dumb" timers again that don't follow the NBR rules?
As a sidenote, I'm in Hawaii and I only have one dish looking at 119, while I have never been able to conculsively get a straight answer on this I assume that's why I can only get a 44-hour guide. I read the the EEPG guide for (Microsoft/WebTV) DishPlayers is only available off of sat. 110, is that the same for regular DISH receivers/DVRs too? (My 322 (which doesn't have DishPlayer in it's name) also only gets 44-hrs. too, instead of the 3 (?) days it should get.) Dish Network CSRs have been pretty clueless about this situation, one told me the problem was that I have to have at least 70% signal for the EPG to work properly (which I do!), another said that I should turn off my receivers at night using the button on the front (not on the remote) and leave them off all night to get the software to update and "it should be fixed" (it wasn't).
Thanks,
Ryan
Once a make an All Episodes, New Episodes, Daily, Mon-Fri, Weekly, or a DISH pass timer it searches for events that match the criteria and makes the appropriate timers (which in my case would be whenever the show plays within about 44 hours of when I make the timer). But it doesn't seem to ever search for new occurances of the show after that first search when making the timer. So a "Monday-Friday" timer will work the first day, and the second day after I make it, but after that it doesn't do anything, so I have to delete it and re-make it all over again every day or two days. This is a serious "downgrade" for me, as the "dumb" timers in the previous version (pre-mid-December) worked fine for me, albeit as expected they would record whatever was in the time slot they were set for even if it wasn't the program I wanted.
Unfortunately, when I noticed the new features I deleted all my existing "dumb" timers for my favorite shows, thinking that the new timer system would be better.
Is anyone else having this problem, and is there a way to fix it or create "dumb" timers again that don't follow the NBR rules?
As a sidenote, I'm in Hawaii and I only have one dish looking at 119, while I have never been able to conculsively get a straight answer on this I assume that's why I can only get a 44-hour guide. I read the the EEPG guide for (Microsoft/WebTV) DishPlayers is only available off of sat. 110, is that the same for regular DISH receivers/DVRs too? (My 322 (which doesn't have DishPlayer in it's name) also only gets 44-hrs. too, instead of the 3 (?) days it should get.) Dish Network CSRs have been pretty clueless about this situation, one told me the problem was that I have to have at least 70% signal for the EPG to work properly (which I do!), another said that I should turn off my receivers at night using the button on the front (not on the remote) and leave them off all night to get the software to update and "it should be fixed" (it wasn't).
Thanks,
Ryan