(This is handy as a backdoor incase you arse up your dashboard and it loops) It uses my dashloader so any patch my softmod loads this loads also, you can create a dashloader.cfg file and put a custom path to a dashboard of your choice in there to boot that first and you can also populate the dashloader.rec file with a path to a recovery dashboard if you want to use the start+y feature of dashloader. If you want it to load on each boot, just get your bios to run C:\Bios Virtual Drive Patcher\default.xbe on boot. If you use XBMC4Gamers you can use the XISO to HDD script to parse and process your XISO files into folders and it will also populate the attach.xbe with the correct certificate information of the game so trainers and save managers work properly. Unfortunately ind-bios5003 won’t work 100% and 5035 doesn’t work either, so we need to use M8Plus to get it working 100% (this goes for BFM or flashed) this package should be self explanatory. Here you go, works on all bios since it’s patching a BFM bios. 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. Modchip BIOSes: X2 4981, iND-BiOS 5003, X2 5035 and M8plus are supported. (Use XBMC or UnleashX's File manager to change the XBE Title.) 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. 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. 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. Here's my precompiled XISO patcher XBE named (Update: Not really needed as I've attached a pre-compiled patcher below named evoxdash.xbe.)Īs 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. It rips the disc image and includes the default.xbe (attach app with the game's name set as it's XBE Title).Īnd, the CDROM modchip archive. 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. 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.) The mounted image looks like a DVD disc is loaded. (Update: Long filenames are not problem as a DVD disc image is mounted that doesn't have the FATX filename length limitation. Any file less than the cluster size will take a full cluster to store on the HDD - 32KB or 64KB for large extended partitions. I think, the XISO's will take less space in the long run than extracting the files/folders from them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |