Leaderboard

I found the easiest way to get this working was to use XBMC4Gamers by Rocky5. It does all the hard work for you really. I think most people struggle to get their head around the fact that they have to load the attach.xbe in before they can load their iso game. I did write a bit of an explanation of how to do it using XBMC4Gamers earlier in this thread i think... Lol, its been a while since i've messed with the OG.

Some programs have problems with ISOs larger than 4.7 GB. I'll try with my version of extract-xiso and I'll let you know.

I think, the XISO's will take less space in the long run than extracting the files/folders from them. Any file less than the cluster size will take a full cluster to store on the HDD - 32KB or 64KB for large extended partitions. (Update: Long filenames are not problem as a DVD disc image is mounted that doesn't have the FATX filename length limitation. The mounted image looks like a DVD disc is loaded. Also for games larger than 4GB's in size, the max size of a single file allowed in FATX, the ripper splits the image into multiple files <4GB each that are mounted as one larger than 4GB disc for those games that require it.) You'll need the NKPatcher driveimageutils-v1.0.1 archive which contains an attach and detach XBE as well as an Xbox XISORipper app to create the XISO images from original discs. It rips the disc image and includes the default.xbe (attach app with the game's name set as it's XBE Title). And, the CDROM modchip archive. (Update: Not really needed as I've attached a pre-compiled patcher below named evoxdash.xbe.) As most modchip BIOS's are set to boot evoxdash.xbe as the first xbe in the boot order, name the XISO patcher - evoxdash.xbe - and rename your current default dashboard that's already named evoxdash.xbe to evox.xbe. Here's my precompiled XISO patcher XBE named evoxdash.xbe (Size: 10,232 bytes, SHA-1: 7E486314DE185FB68B274FC52843E751C03C52B9) It chain loads evox.xbe after patching the in-memory BIOS routines to be able to mount/run the XISO images with the NKPatcher driveimageutils' attach app - default.xbe. You either use the ripper to create the XISO image and it adds the attach app into the game's name rip subfolder in your Games folder on F (or G if you edit the ripper's config file) for the game's XISO (dot iso file) or add the default.xbe attach app if you already have the ISO in a subfolder. However, if you do it this way, you'll need to edit the attacher's, default.xbe, XBE Title to see the game name in the menu. (Use XBMC or UnleashX's File manager to change the XBE Title.) Works with the following BIOS/Kernel versions: 3944, 4034, 4817, 5101, 5530, 5713, 5838 and Evox M8plus (it's kernel version is 5838 so duh). Update - sorry the above list is not quite right (the source file's comments had not been updated to match the actual code): 3944, 4034, 4817, 4981, 5003, 5035, 5101, 5530, 5713, and 5838. Modchip BIOSes: X2 4981, iND-BiOS 5003, X2 5035 and M8plus are supported. P.S. If you don't boot a bank flashed with a supported BIOS, the patcher will still load your default dashboard (C:\evox.xbe) without applying the patches to an unsupported kernel version.