Print

[xman954]

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

[Movax]

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.

[FrostyTheSnowman]

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.  

[xman954]

QUOTE

Does the (forget what it's called) 'createISO' softmod tool work as well

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)

[xman954]

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...

[Movax]

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?

[xman954]

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...

[ldotsfan]

Try sending a PM to xman954

[rocky5]

QUOTE(HiTMaN-239 @ Mar 17 2010, 08:23 AM)

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 ?

[JLsoft]

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

[HiTMaN-239]

QUOTE(JLsoft @ Aug 28 2011, 09:39 PM)

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.

[Movax]

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.

[Movax]

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.

[Movax]

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]

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

QUOTE

;;;
;;; Compile using the command:
;;;    nasm -o default.xbe xboxapp.asm
;;;

%define BOOT_TO_DASH       ; uncomment to boot the 2nd Dashboard when done

%define DASH_PATH   '\Device\Harddisk0\Partition2\startxbmc.xbe'

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.