Now that is interesting....the "news" looper is a routine that I use to cycle RSS news feeds. Basically I set it up on default for the Xlobby RSS feed, and every 30seconds, move to the next "article" in the RSS feed. Now I know there has been a bit of a bug that seemed to occur after the computer would come out of standby. It seemed that the looper did not recognize the 30second delay, and would start to randomly cycle through the RSS feed at different durations. I never thought it would cause a lockup like this.

One thing you could try:In the xStreamed\database directory, there are a bunch of "news_xxx".xml files (one being news_xlobby.xml). Maybe these RSS .xml files HAVE to reside in the xlobby\databases directory instead. Then restart xlobby.

Hmm...actually I just experimented by removing all news entries from the xlobby\databases directory, and it still started fine, so I doubt that will be problem.

If that doesn't work, then open the menu.xml file (found in the root directory of xStreamed), and remove this line:

This is for cross-fading images based on the new xFade plugin. I was experimenting with it prior to the release, with the hopes of introducing it formally to the world, but I had issues on my HTPC with it (just didn't cross-fade smoothly like on a test system that I used it on). Instead of taking out the events, I just hid them with the intentions of using them in the future. I'm wondering if that is having a profound side affect.