Just a thought: when you tried using a cat5 wire, did you also turn off the wireless? Not at the roku (which is questionable) but at the router itself. This way you _know_ the cat5 is being used.<br><br>Second thought, put the laptop in the same physical location at the roku and try the netflix again. There may be a localized interference that is exacerbated by heating of the device.<br>
<br>Lastly: external fan effect - does it make a difference if you have really excellent cooling? shoebox with 6" fan and roku in the front to make sure all air flows through the gizmo is cheap test rig.<br><br><div class="gmail_quote">
On Mon, Aug 2, 2010 at 12:24 PM, Chris Fowler <span dir="ltr"><<a href="mailto:cfowler@outpostsentinel.com">cfowler@outpostsentinel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Mon, 2010-08-02 at 11:59 -0400, Jerald Sheets wrote:<br>
><br>
</div><div class="im">> I get no wireless failures with Roku nor do I get wired failures.<br>
<br>
</div>The wireless failure is a hardware failure that happens with time. My<br>
daughters use the Roku so it stays on 24x7. I bought the box in 07/09<br>
and I think the wireless failed in 01/10. What happens is that the box<br>
no longer can "see" access points. It will lock up in the configuration<br>
page for wireless. If you try to get the MAC address of its wireless<br>
adapter you get all 0's. This is not an intermittent problem. It is<br>
death of the wireless transceiver. If you google and look in forums<br>
you'll see this scenario.<br>
<br>
I do not know what causes this. Possibly the heat from being left on<br>
either makes solder joints fail or kills the chip.<br>
<br>
Before the wireless failed we had some issues streaming anything on the<br>
first box. It is so hilarious because the girls stopped watching Roku<br>
but used a laptop in the same room running Windows XP and Netflix<br>
streaming! After I saw that I doubted signal strength was an issue and<br>
decide more on hardware. When someone is doing something on a laptop<br>
next to a device that should be able to do it, it is hard to blame the<br>
network on that one.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br>I would rather stumble along in freedom than walk effortlessly in chains.<br><br><br>