this app was pulled from NKPatcher to enable that feature for modchip users
so far evox M8 and IND-5003 Bios's are fully working

all the tables are configured for Xecuter 4981 and 5035
but these 2 refuse to boot the game, they show in the dash as a game loaded
and you can see the ISO contents in D:\ using FTP or a file browser, so it's almost there
so if anyone has any ideas of why the Xecuter bios's refuse to work
let me know..

the advantage's of using ISO's from the HDD are titles that have long file names
and other reasons that prevent them from working normally from the HDD
not to mention that it's 1 big file and FTP speed is a lot faster and no waisted slack space

1 the ISO-patcher.xbe can be chained (set it as your boot dash and config it's path to your dash)
it will set a byte in the kernel and check that byte to know if it was previously patched
this prevents it from trying to repatch and crashing

2 the new attach.xbe (xboxhdd\games\test_game\default.xbe) must be used
it was patched the hard way (hex edit)
to add LDP \device\cdrom0;default.xbe then HalReturnToFirmware(2)
this enabled the IND-5003 bios to work
use a xbe renamer to change to the ISO title's name

everything was tested using BFM bios's and a 1.0 xbox
who knows the Xecuter bios's may actually work

check sig for files to try it

Finally! This is great, I'll try it soon. Does the (forget what it's called) 'createISO' softmod tool work as well? chained ISOs? (Split ISOs if more than 4gb..)

Too bad I like my X3 bios..I'll flash M8 on there too I guess.

Interesting...

I originally thought of creating a kernel patcher for hacked BIOSes when I was first developing my VGA patchers, but I couldn't really get it working, so I ended up making an actual BIOS file patcher instead.

But, i'm glad to see that someone on this scene is still interested in improving the BIOSes available for the original XBOX. I myself have actually lost almost all interest in the system just because of some recent life changes (divorce...) but i'm always glad to see others working to improve the original XBOX.

Yes but it will create a iso much larger then needed Quix, Craxtion work just fine
there was only 1 game that need that tool work.. (Race driver 3)

anyone tried this ?
don't understand how to use it ?

also would like to see if I can make a X3 BFM bios or X3 bios patcher, but will need
someones help that uses a X3 chip and bios
(all thats needed is to burn a disk with a special default.xbe and cold boot it and FTP the file it's creates)
PM if you can help...

Okay, I know it's not 'soon' like I said, but I was going to try this. One thing I don't understand. The patcher will patch the kernel, and then?? You said it would chain, but what does it load after, or how can I specify what it will load?

Will it just load default.xbe in the same directory as itself?

the easiest way to use is to put the default.xbe in a apps folder (IE: F:\apps\patcher\default.xbe)
run it from any dash then it will return to the dash when patched with the LED red

the game iso need to be in a folder with the the special attache xbe (default.xbe) from the test_game folder
IE F:\games\game_ABC\game_ABC.iso
and
F:\games\game_ABC\default.xbe (use xberenamer to title it)

if you want to chain it
then edit xboxapp.asm
uncoment %define BOOT_TO_DASH
and set the path in the next line to the boot dash
point your bios to boot the default.xbe or rename it

any other ? just ask..

also this will work with NKpatcher without the virtual CDRom enabled to give you this function
without recompiling and risking messing up...

I am resurrecting a old thread here....... anyone get this to actuall work with a flashed IND-BIOS 5003? I am having trouble getting it to work.

Cheers.

Try sending a PM to xman954

I did, he says he used a BFM IND 5003....... I will try it with a different dash. and then I will try it with a BFM BIOS. Will post here with results.

How did you get on? as i found out you could do this yesterday lol i miss this option from softmods.

I has the same problem as this guy I have a Tsop flashed with IND_Bios_5003 but the LEDS don't change to red when i run the kernel patcher nor does the loader work just crashes the xbox (if run without kernel patcher it just restarts the dashboard)

Update if you use the original NKPatcher Attach.xbe it mounts the ISO but doesn't execute it you have to do that manually (via file-manager or launch disc).

OK another update this hex string is the cause of the crash (in the new attach.xbe)

CODE

E984000000

if you replace it with the original string

CODE

6A02A10410

it will not crash the xbox so not sure what this does if its just a bit of code to jump to a point in the file to execute the xbe ?

I just want to say that this is awesome and works wonders. I have a 1.0 tsop with m8 plus bios. Was having to run retail bios(upgraded from launch to 4034) instead of modded for the lack of the virtual cd feature. Now I have the near perfect game compatibility I had with my softmod, a kernel version I am pleased with, and now even some games that wouldn't load before with old retail bios+softmod work perfectly(ex. Pro Skater 4). This was also very easy to modify to have it load my dash after execution. Anyway, thank you very much for this.

I'd like to thank f_d_m for talking about this elsewhere and convincing me to attempt again to get it to work.

It seems my problem was that I was using the ind-bios beta that's named internally '5004'...and the kernel patcher wouldn't work with it.


I flashed my tsop with 5003 and now it's working fine (and I don't seem to be running into the black+white poweroff problem I've had before with 5003



...now if only someone could add the attaching/detaching of .ISOs into xbmc4xbox somehow

I am glad this thread is still active, lol. I want to give this another shot. Any one with a link to the files so I try this again? how did you guys get it going with IND BIOS 5003, maybe a brief step by step. My xbox1 knowledge is rusty.

Thanks.

I have this chaining and it works well. I have to do some testing, but I assume the .ISO will stay attached through an IGR, so I will have to run the detacher.xbe to use a real disk. I think it would work smoother, and seem transparent to the end user if the patcher could detach any current .ISO before continuing to the dash.

I'm going to try to add the detaching functionality to the patcher, or chain the detacher as well.

I don't think that the attach is persistent through a IGR, and I have found the default.xbe from DVD2Xbox to work better for me so far, though the ISO ripper from the version of DVD2Xbox I have always makes 6gb worth of ISO.

Follow up:
xmans attach xbe freezes my xbox, I didn't try patching it. If you rip a game in ISO mode with DVD2Xbox it creates a default.xbe in the game folder. This is an attach and launch app, that seems to work well. You'll need an xbe renamer to have it display properly in a game list, and probably you'll want some boxart or somethig for an icon. Ripped games in ISO mode always take up a way more space than needed though, so rip games normally and use your favorite xbox ISO tool to make your ISO.

Suggestion: If you use Linux/Unix i would suggest using extract-xiso to create (it can create too) ISO images from ripped games. The binary on sourceforge will run in xbox linux so you can create optimized ISO images on the xbox. Ask if more info wanted, this could be automated with a small loopback xbox linux to run like an app.

Movax, thanks for the info. What xbox version and tsop bios you using? when chaining, which dashboard do you use?

I have been testing with ind-5003 bios. I got it working first with out the chain, and using dvd2xbox attacher. Xman's attacher didn't work for me.

But then, when I chained it, it freezes using the dvd2xbox launcher. (I know it patches correctly because I compiled the version with the red led status, and it indeed flashes red on boot).

The patcher file I am using was pm'ed to me by Jlsoft from this thread, where did you get your patcher file?

this is a great functionality, if I can get it to work! hopefully I can with help from this thread.

To chain load, I edited the xboxapp.asm as instructed by xman and ran nasm as it shows in the comments of that file:



Partition2 is C
startxbmc.xbe: This is just my preference, you can name any xbe to launch your dashboard.
(startxbmc.xbe is XBMC team shortcut, it needs the same name config file, in this case startxbmc.cfg which contains the line E:\Apps\XBMC\default.xbe)

So I just changed those two define lines and ran nasm for the chained loader. I am using Evox M8+. I really wanted to use Ind cause it seemed cool, but 5003 has a weird slow IGR, 5004 has the back+black no trigger bug and 5004 beta I have read has weird sound problems, I don't think i tried it. M8 works perfect though, it is full featured, I don't see any advantage for Ind.

Arlight, just did some more testing. Turns out that it works after all. My problem was I had the ind bios option "in game reset boot to dashboard" enabled. What I figure was happening, is that the patcher was working fine, but when I used the launcher it triggers an IGR function to load the mounted image, this gets intercepted by the ind bios and because of the boot to dash igr option being enabled it would just reload the dash again (making it look like the launcher failed).

When I disabled that option, the launcher worked like a charm!

But now I have another problem, when I launch my game, and i am done with it, I like to go back to my dashboard. Unfortunately, when I use my IGR combo, I get a constant loop of the mounted game. It seems like the bios is trying to load my dashboard, but the patcher keeps wanting to load the mounted iso, and they fight it over in a nice loop.

My work around has been to use the power cycle combo, that works no problem, but the combo is really awkward, and I wouldl like to see if there is a way around this, how does your IGR work in M8?

By the way, IND 5003 IGR is fine, not sure what issues you have had with it. The 5003 problem is that the power off combo is back and white, no triggers like it was supposed to be. The main thing that I like about 5003 is the disable xbox flubber intro option, and the fact that I can keep playing around with a config file without have to reflash everytime I want to try a different option. Does M8 have those two options? maybe I will put that on my other half of the tsop to play around with if it does.

By the way, why the convulated way of launching xbmc with the shortcut? can't M8 launch xmbc's default.xbe directly from where ever you have it?

I am not sure if the ISO is still attached after IGR and something with my configuration is detaching the ISO. Maybe there should be a detacher chained or that ability added to the patcher as an option when assembling it. I don't have source for the detacher, we may need xmans help.

For ind bios, my understanding was that you were supposed to hold the triggers as per most bioses and the nfo.

( http://www.tdubel.com/artikkelit/tiedostot...D-BiOS.5003.nfo )

Regardless, I see it as a bug, and unusable for me. You can customize evox using evtool, mine has no animation and displays a blue X logo, cause I think it looks nice.



^This is not my configuration, just an example of the tool.

M8 has no config file loading ability, but, right or wrong, (no testing done) I feel it will slow down my bootup as the bios has to wait for the HD to spin up. Custom X logos is the only place I think Ind has an advantage, which does seem pretty cool.

For the XBMC short cut, I just like having the ability to quickly edit the dashboard that is launched, I see it as flexable. I don't think m8 can boot from E, but the XBMC shortcut can..

I think I misunderstood, you are acknowledging the triggers are supposed to be pressed? I am too used to using back with black/white for mame/coinops, plus i've accidentally pressed them before. That's enough that I won't use it, though I would be interested in finding the code in the kernel and fixing it.

Yeap, I was aknowledging that the triggers are supposed to be pressed (i.e. a bug).

I think I have got a setup I am happy with for now. I found that using IGR mode 1 (complete not quick) seems to fix my looping issue. Its a bit of a weird igr mode (it resets twice in a row), but whatever it works.

I now have two games, I turn my box on, and I can launch a game, I can then IGR (triggers+back+white), and then launch another game. I can shut down, run a different game. So its all working good. (keep in mind I am using the DVD2XBOX launcher and not xman's)

My only complain, is the IGR mode 1 is a bit weird.

Now, I am being greedy, but I was hoping I can chainload this with a PBL to load a VGA BFM bios. I tried just chainloading to Frosty's BFM vga ind bios without the patcher just to try it, but it didn't work it would hang. I can launch the PBL from the dashboard normal and sucessfully load the bfm vga bios, but I can't seem to get ind 5003 to load it directly. It might be an issue with the PBL that frosty packaged with his realease (it think it is the Metoo version).

I saw a thread where you were doing soemthing like this, i.e. chainloading a tsop bios to load a BFM through a PBL. I think you were loading a retail bfm bios. Any tips?

I think there is a bug with that Ind bios load BFM bios function, are you pointing it to the bios or the PBL?

Yeah I wanted to load a softmod from chip to have the best of both - softmods are the more advanced mods and were last to be seriously worked on - but I wanted to be able to turn off the boot animation and have unlocked hard drives etc. I think I might be happy with m8 and this patcher, since this was one of the softmod features I really wanted.

I gave up though, I could boot the first dash and it seemed to work, but any other xbe's would freeze. I think I couldn't figure out how to make a BFM retail bios. I might try again sometime.

What I want now is an xbox app that scans all subfolders and looks in the ISO for the default.xbe and finds the game name and patches the launcher with the game. It might as well grab the icon at the same time and create a thumbnail.

Yah, there is a bug for launching BFMs directly. By a bug I mean it doesn't work at all, lol.

But all I was doing was instead of setting the bios to boot my dash xbe, I set it to boot the PBL xbe (which in turn launches the BFM). But it didn't work, it would just keep flashing green after booting.

I think my issue is that the BFM is looking for the dash in the wrong place, I will have to double check.

Okay, I read your softmod thread, I read that you got your tsop bios to launch a PBL, which version did you use? and did it work okay as far as getting the BFM loaded with whatever dash it launches?

getting a litte off topic here, sorry.

And yes, a script of sorts to do what you said with the games would be nice, a scraper for games and a game library mode in xbmc would be nice as well. Maybe I will code something up, the xbox1 scene is kind of dead here. Maybe I will head over to xbmc4xbox and join their forums.

Hitman, to get the ind bios BFM launch to work, make sure you have the flubber sequence enabled and then press the eject button during the sequence. That should make it look for and launch the BFM bios

I think I was using Ind bios for most of my testing actually. For now I am happy.. I'll try it again sometime - I do want to get into the assembly more and understand it better (I find it interesting). If I do that I should be able to figure out how to fix it.

Good to know (by the way, where did find this? it's not in the 5003 documentation). I will give it a shot, thanks for this!




I got it booting through PBL Metoo, I was loading a BFM ind on top of my TSOP ind, so the bfm was also reading the config and in turn launching the PBL again, and kept looping

I think I am done with the software side of things for now, going to focus on the hardware for my slim box now.

By the way, movax, you might like this.

Taken from the release information from the Yoshihiro Debug Bios:



They work in a similar way.

This sounds totally cool..

Link is down. Anyone still have this?

It's in the link in xman's sig.. but it's here too: http://www.mediafire.com/?w45cavj4cu7w3ct

Thanks!

The link in the xman's sig wasn't working..

EDIT: Now it works

For the sake of accuracy and completeness:

The attach.xbe file used to mount the .iso actually mounts the .iso file(s) (using the new system call that was patched into the kernel) then quick reboots the system ->the bios will boot whatever is first on the list in it's configuration. This is normally default.xbe on the DVD so it seems like the attach app is mounting and executing the .iso. In my previous posts in this thread I said it unmounts the .iso on a IGR, but this is only true because I had my bios set to 'more compatible' which is more like a power cycle. If it is set to 'quick' the .iso is still attached through a IGR.


The only downside of this setup is using trainers: As it is you would have to setup your system to not boot default.xbe on the DVD so after the quick IGR you could use a trainer on the virtual DVD and launch the game.
It would be nice if the trainer support in XBMC could be modified to handle looking at the default.xbe/ISO and recognizing the setup and checking for a default.xbe in the .iso itself to match up with trainers. (I might look into this...someday..)