wcattey;189932 Wrote: > basic problem manifestations like: > > waking up Slimserver... > Blank screen > > would be able to be traced quickly and easily, rather than to live on > as "Is it your wireless hub?" "Is it how much memory your Slimserver > host has?".
How would you get any information beyond that? WOL is "I send a packet to the server.." If the server doesn't wake up, there are a ton of things that could be the problem, and testing them in software is nontrivial. "Oh, I forgot to enable WOL on the server" or "The Server is unplugged" would test the same. An access point would certainly be awake or the SB would complain about a lack of network. But is it like one of mine that would get stupid sometimes and not feel like passing packets? Maybe. Maybe not. Maybe it takes the server 5 seconds to wake up.. maybe it is in ultrasleep mode and had tons of stuff running, loading it all back into RAM can take a while... There really isn't a good way for WOL to know why something isn't waking. The best option would be for the SB to just keep trying... Maybe a UI change to note, "Retry #6, something is broken" would be useful so people don't keep pressing the Power button, but that's just UI stuff. Tracing why WOL doesnt work or is slow is something that needs to be done on the sleeping device. Synching works great for me on my SB's. I don't know why it doesn't work on Roku's, but, then I won't use one. -- snarlydwarf ------------------------------------------------------------------------ snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179 View this thread: http://forums.slimdevices.com/showthread.php?t=33695 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
