malte Wrote:Is an xbox game a normal xbe or how do you launch them?
On the root of each game disc is a file called "default.xbe". That's the executable. When users import their games to their HDD, they usually make a parent folder (eg F:\Games), then have sub-folders within that for each title.
In XBMC, you'd then add F:\Games as a source, and it'll automatically detect each sub-folder containing a "default.xbe" file and add that as a game on the list. Each XBE contains a thumbnail icon and game title, which XBMC extracts and stores in the programs database file. You then just browse the games list like you would, say, your videos, highlight the one you want, select it, and it boots (the sub-folders become transparent to the user). Game titles stored in XBEs can even be altered via the context menu.
(The icons/titles were
intended for use within the original MS dash for the save game management system).
If you stick an image file titled "default.tbn" in a game folder, XBMC will use that as the game icon instead of the image embedded in the XBE (same as using a TBN with just about any other sort of media).
Some games have multiple XBE files. For example,
Prince of Persia: Sands of Time has an "unlockable" version of the original PoP game, which has its own alternative XBE on the disc. Other discs might contain demos for other games, which again, get their own XBE files.
Others include multiple XBEs for launching what seems to be the exact same game. Presumably there are minor changes between them, or... something.
Detecting all XBEs (as opposed to just "default.xbe") is problematic in that any game that supported Xbox Live has two on the root of the disc, "dashupdate.xbe" and "update.xbe". These are used to update the original MS dash on stock consoles to maintain Live compatibility. Users wouldn't want them presented within the script, and they certainly wouldn't want to
run them - they'll mess up older softmods, and some of the (really) old hardmods too. In theory, modern mod setups will stop them executing in the first place.
Some disc extractors even strip the files out completely, which makes sense in that they're only half-way valuable on an unmodded system - which can't run backups.
So either search for just "default.xbe", or search for all XBEs except "dashupdate.xbe" and "update.xbe".
The only difference between launching the XBE for a standard game (compared to an emulator) is that there's no need to tell games what ROM to run. Homebrew apps tend to use the same "default.xbe" standard, because that's what dashboards (like XBMC) expect them to use.
paybac, were you able to get any extra logged data with your later tests, or does it always cut off "randomly"?