Wha, wha what?SatelliteGuys.US - Error
You do not have permission to view this page or perform this action.
Wha, wha what?SatelliteGuys.US - Error
You do not have permission to view this page or perform this action.
That is incorrect. Again, it's a firmware, isolated from the drive. Google disabling external WD sleep mode. If I knew I would walk you through, but like I said, I bypass that problem.
You are putting the target on the wrong hay bale How can Dish possibly know about every firmware version WD may come up with. We have provided with you with idea/sources to solve YOUR problem. Up to you now.The 2007 Western Digital drive does not support sleep timer. The 2010 and 2016 Western Digital drives both support the sleep timer. They are both set to On and set for 30 minutes. I shut the sleep timer off and will evaluate if this fixes the issue. If it fixes the problem, it is really a bandaid since the Hopper 3 system should really control the drive. The drive should not have to run continuously. I am sure that the internal drive on the Hopper 3 does not run continuously.
You are putting the target on the wrong hay bale How can Dish possibly know about every firmware version WD may come up with. We have provided with you with idea/sources to solve YOUR problem. Up to you now.
You are putting the target on the wrong hay bale How can Dish possibly know about every firmware version WD may come up with. We have provided with you with idea/sources to solve YOUR problem. Up to you now.
That's what I get when I click on your link. Firefox browser. I'll try Edge and Explorer.Wha, wha what?
You are putting the target on the wrong hay bale How can Dish possibly know about every firmware version WD may come up with.
QUOTE]
The sleep mode problem has long been documented and discussed. Ironically, when Dish first made the introduced the EHD capability, long before the advent of Hopper, Seagate did a PR tie-in with Dish. Well, guess who's drives never worked correctly??? I think in time, they fixed the sleep problem on later models. You can call my suggestion a band-aide if you like. Others might call it a fix.Well, you dismissed him right smartly didn't you. Use your band aid or go sit in the corner.
Does it occur to you that not everyone has the sources/resources that you do and they
may not know what you're talking about?
Dish offers a port for an EHD and they should make it work instead of having to
apply band aids and have the EHD run itself into the ground.
The sleep mode problem has long been documented and discussed. Ironically, when Dish first made the introduced the EHD capability, long before the advent of Hopper, Seagate did a PR tie-in with Dish. Well, guess who's drives never worked correctly??? I think in time, they fixed the sleep problem on later models. You can call my suggestion a band-aide if you like. Others might call it a fix.
EDHs were not being recognized AT ALL earlier in the year. Took a month or more to fix. No esoteric snark!Only DISH can apply the fix.
Users are left to apply band aids.
Early in this thread you said the problem was fixed with the recent Big Fix.
Did you actually mean that or was it some kind of esoteric snark?
It's worked for many. One can only try.I tested it today on my two Hopper 3 receivers and it did not fix the problem. I still get the 1 sec error message and then the blank screen. Your idea of disabling sleep mode did not solve the problem.
They must have fixed it, because I got a 1TB Seagate drive from Dish, and I have never had any problems using it with a ViP211k or a Wally.The sleep mode problem has long been documented and discussed. Ironically, when Dish first made the introduced the EHD capability, long before the advent of Hopper, Seagate did a PR tie-in with Dish. Well, guess who's drives never worked correctly??? I think in time, they fixed the sleep problem on later models.
"RAID 1 array."
They must have fixed it, because I got a 1TB Seagate drive from Dish, and I have never had any problems using it with a ViP211k or a Wally.
If sleep mode on the EHD is causing the problem, then why didn't we have the problem before CUI was introduced. The CUI is causing the problem.
I am leaving more and more stuff on my HWS HD to avoid the problem, because it is a pain in the ass. I have even looked into DirectTV,p but have not bit the bullet yet, but I am really considering the switch. I HATE having to go into the EHD twice to watch any and every program.