With the last couple T3CH XBMC SVN releases (at least those from April 2007) there has been a problem when attempting to launch XBEs from within XBMC. This appears to be a problem with the X2 series of chips specifically when running an X2 BIOS. Problem doesn't appear when running X2CL 5035 on an X3 chip or (confirmed by a member of the XBMC forums) when running a non-X2 BIOS (ex., EvoX... bleh.) on an X2 chip. This is similar to a problem I've seen in UnleashX when the chip ID info is querried.
This XBMC issue seems to take a combination of three things... an X2 chip, an X2 BIOS and the recent builds of XBMC. The XBMC team is aware of the issue but needs help to solve it. If anyone reading has help that can be offered please go to this thread in the XBMC forums - http://www.xboxmediacenter.com/forum/showthread.php?t=25274
Please don't flood this forum, the XBMC forum or any other forum with simple "I'm having this problem too!" or "please fix!" posts. This will not be productive and simply wind out adding unnecessary bulk to the forums. If you have useful information to add, do so. If not, please be patient and wait for the brains of the scene to debug and remedy the situation. Thanks.
-Whoopin'
This XBMC issue seems to take a combination of three things... an X2 chip, an X2 BIOS and the recent builds of XBMC. The XBMC team is aware of the issue but needs help to solve it. If anyone reading has help that can be offered please go to this thread in the XBMC forums - http://www.xboxmediacenter.com/forum/showthread.php?t=25274
Please don't flood this forum, the XBMC forum or any other forum with simple "I'm having this problem too!" or "please fix!" posts. This will not be productive and simply wind out adding unnecessary bulk to the forums. If you have useful information to add, do so. If not, please be patient and wait for the brains of the scene to debug and remedy the situation. Thanks.
-Whoopin'