When the unit is hanging (stuck), the displayserver does not respond to either winamp or IE if I try to load any of the web pages. I don't use the DNS to resolve the empeg, just its static IP # (which is outside the DHCP ranges). With emplode the behavior is a little different, emplode will 'see' the IP address, but then sometimes fail to connect. Sometimes emplode does connect, and emplode behaves normally, but my streams don't come back after I sync, even if I quit & re-launch winamp. The empeg disk is thrashing the whole time displayserver is stuck.
As to the home/work thing, I've listened much more at work, so I cannot say that for certain. Let's see...There, I just made it do the same thing at home (a few browse windows and two copies of winamp). Interestingly enough the two winamp instances returned at the exact same time while the two IE windows are still not responding. Now both winamps have cut out again, they seem to have played out their buffers. The empeg is still responding to pings here at home while the streams & webserver are stuck/not responding. About 5 minutes now.
I've just rebooted the empeg and the streams have both started up again with no help from me and a refresh brings up the web pages. Very disconcerting listening to Surf Safaris' Wipeout and Moby Ah-Ah at the same time.
Another interesting thing is that when I unplugged the empeg the winamps slowed their connecting/failed to connect cycle from very fast to quite slow. I can only assume that is because the request packets are timing out instead of coming back refused from a valid address, causing a greater delay in the attempt/fail cycle in winamp.
Ok, the Frantics (CBC) and techno do not mix. That is official. The Frantics win. Enough for tonight.
-Zeke
just say you weren't paying much attention...
ps, been listening for about 40 minutes here with no problems where as at work it's about 3 songs max (and I don't mean Genesis Supper's Ready length songs either).
Edited by Ezekiel on 05/04/01 04:20 AM.