Post by: xman954 on August 16, 2007, 10:33:00 AM
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
Post by: Movax on August 16, 2007, 11:49:00 AM
Too bad I like my X3 bios..I'll flash M8 on there too I guess.
Post by: FrostyTheSnowman on August 16, 2007, 02:27:00 PM
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.
Post by: xman954 on August 16, 2007, 06:51:00 PM
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 finethere was only 1 game that need that tool work.. (Race driver 3)
Post by: xman954 on September 19, 2007, 09:35:00 AM
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...
Post by: Movax on January 11, 2008, 07:15:00 AM
Will it just load default.xbe in the same directory as itself?
Post by: xman954 on January 11, 2008, 09:16:00 PM
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...
Post by: ldotsfan on March 16, 2010, 07:40:00 AM
Post by: rocky5 on June 13, 2010, 05:01:00 AM
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 ?Post by: JLsoft on August 28, 2011, 07:39:00 PM
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
Post by: HiTMaN-239 on November 18, 2011, 10:39:00 PM
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.
Post by: Movax on November 20, 2011, 09:20:00 PM
I'm going to try to add the detaching functionality to the patcher, or chain the detacher as well.
Post by: Movax on November 21, 2011, 01:12:00 AM
Post by: Movax on November 22, 2011, 11:04:00 AM
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.
Post by: Movax on November 22, 2011, 12:39:00 PM
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.
Post by: Movax on November 22, 2011, 05:34:00 PM
For ind bios, my understanding was that you were supposed to hold the triggers as per most bioses and the nfo.
( http://www.tdubel.co...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..
Post by: Movax on November 22, 2011, 06:22:00 PM
Post by: Movax on November 23, 2011, 08:29:00 PM
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.
Post by: Little-G on November 24, 2011, 07:12:00 AM
Post by: Movax on November 24, 2011, 09:30:00 AM
Post by: Little-G on November 25, 2011, 07:12:00 AM
QUOTE(HiTMaN-239 @ Nov 25 2011, 01:52 AM)
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!
Taken from the release information from the Yoshihiro Debug Bios:
QUOTE
* If you press eject button during booting animation, bios will boot BFM bios located on E:\\biosbfm\\xboxrom.bin
They work in a similar way.
Post by: FrankMorris on January 20, 2012, 04:14:00 AM
Link is down. Anyone still have this?
Post by: Movax on January 20, 2012, 10:18:00 AM
Post by: Movax on March 04, 2012, 10:10:00 AM
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..)