xboxscene.org forums

OG Xbox Forums => No-Modchip Hacks (exploits) => GameSave Exploits => Topic started by: Hexx on June 26, 2005, 10:29:00 PM

Title: Dual-boot
Post by: Hexx on June 26, 2005, 10:29:00 PM
How do I get the dual-boot working on Krayzie's MechAssault softmod?
I installed the dual-boot and that added a folder to my e:>dashboard>"tray open".
Now I am supposed to put whatever .xbe I want in there. I picked XBMC.
I got everything in there including the default.xbe from XBMC. It should work, however it doesn't.
Also, isn't any .xbe that is put into a modded 'box with nkpatcher already signed? I'm confused. Please help.
Thanks in advance.
Title: Dual-boot
Post by: krayzie on June 26, 2005, 10:32:00 PM
if you install the dualboot it should allready create an tray open folder in the dashboard directory. and no with dualboot nkpatcher is bypassed so you should sign it or put nkpatcher in the tray open folder and direct that to the xbe you are trying to load.
Title: Dual-boot
Post by: Hexx on June 26, 2005, 10:36:00 PM
Ah, it's bypassed. No wonder I get error 21. So how should I go about signing this with Habibi? I have the program ex-xbedump2 but when trying to sign the default.xbe, it goes to command prompt and just stays there with a blinking cursor.
Title: Dual-boot
Post by: krayzie on June 26, 2005, 10:39:00 PM
well normally xbedump is a dos app which nmeeds to be executed with a certain command like "xbedump default.xbe -habibi"
Title: Dual-boot
Post by: Hexx on June 26, 2005, 10:41:00 PM
I can't type anything at all. Supposedly I am just supposed to double click the .xbe and it should be signed with Habibi, but when I do that I just get the command prompt screen with a blinking cursor and I can't type anything.
Title: Dual-boot
Post by: krayzie on June 26, 2005, 10:43:00 PM
the normal xbedump just requires you to put the xbe you want to sign in the same directory and then execute it with the comand from a dos window.
Title: Dual-boot
Post by: Hexx on June 26, 2005, 10:46:00 PM
I'm searching tools and I don't see xbedump. I do however see xbedump launcher 1.0.1.
But the options I have for that are sign for freex, sign for audio, sign for font, and personal signature.
Title: Dual-boot
Post by: Hexx on June 26, 2005, 11:15:00 PM
I think I may have got it, so never mind.
Title: Dual-boot
Post by: ikecomp on June 27, 2005, 11:17:00 AM
Well I am still stuck. I used xbedump and it signs and says everything is ok but whenever I install the dual boot and put the second xbe in the folder I get an error 21

p.s. my default dash is XBMC and want evox as my second dash
Title: Dual-boot
Post by: krayzie on June 27, 2005, 11:21:00 AM
QUOTE(ikecomp @ Jun 27 2005, 07:28 PM)
Well I am still stuck. I used xbedump and it signs and says everything is ok but whenever I install the dual boot and put the second xbe in the folder I get an error 21
Title: Dual-boot
Post by: ikecomp on June 27, 2005, 11:26:00 AM
when it finishes signing the evox dash it is named out.xbe. I then rename this to default.xbe and put it into the tray open folder. And I signed it with the habibi key using the command

xbedump default.xbe -habibi

p.s. I took the default.xbe file out of the xbedump folder after signing as not to get the out.xbe file confused with it after renaming
Title: Dual-boot
Post by: krayzie on June 27, 2005, 11:34:00 AM
you need the out.xbe renamed to default.xbe
Title: Dual-boot
Post by: ikecomp on June 27, 2005, 11:42:00 AM
I might have confused u with the last part of my post. I renamed out.xbe to default.xbe as suggested and it gives me an error 21.  I was just saying that since my evox dash is already named default.xbe I didn't want to make a mistake and have two default.xbe files in the xbedump folder.
Title: Dual-boot
Post by: krayzie on June 27, 2005, 11:48:00 AM
well it should work fine then. Maybe something got corrupted somewhere. I just want to note though that if you are planning to use evox as your secondary dash you might rather wanna use a bios loader or kernel patcher in the tray open folder and point that to your evoxdash otherwise you will need to sign everything you wanna run out of evox.
Title: Dual-boot
Post by: ikecomp on June 27, 2005, 11:50:00 AM
how do i point the kernal patcher to evox?
Title: Dual-boot
Post by: krayzie on June 27, 2005, 11:52:00 AM
QUOTE(ikecomp @ Jun 27 2005, 08:01 PM)
how do i point the kernal patcher to evox?
Title: Dual-boot
Post by: Hexx on June 27, 2005, 02:15:00 PM
Oh, that's why I got error 21 from every .xbe I ran from my secondary dash.
Can you elaborate where I can get this bios loader and kernel patcher? After that, hopefully I can figure most of the rest out on my own.
Thanks.
Title: Dual-boot
Post by: krayzie on June 27, 2005, 02:19:00 PM
they are in the usual places.
Title: Dual-boot
Post by: Hexx on June 27, 2005, 02:25:00 PM
wink.gif
OK, there's fbl, pbl, and nkpatcher. Which is a good choice?
Title: Dual-boot
Post by: Hexx on June 27, 2005, 02:57:00 PM
I'll use nkpatcher. How do I get it to load with the .xbe?
Title: Dual-boot
Post by: krayzie on June 27, 2005, 10:32:00 PM
well you need to fill in the bootpath in the config file from the source and then assemble with nasm. It might be easier to get the pbl metoo package since then you can use the added evtool to adjust the bios so it points to the right locattion.
Title: Dual-boot
Post by: Hexx on June 27, 2005, 11:21:00 PM
Is there a specific tutorial for this? I am in major confusion.
Title: Dual-boot
Post by: krayzie on June 28, 2005, 09:49:00 AM
I'll try to put it in a simple explanation cuz it is easier then it looks. If a new bios is loaded or patched after the exploiting of the ms bios rsa key then it looks for a new dashboard. In my installer it looks for E:\dashboard\default.xbe. If you put a bios loader or kernel patcher in the tray open folder it will most likely look for C:\evoxdash.xbe as this is the most comon default bootpath. Now you can do two things. Either put your evox dashboard on C named evoxdash.xbe or you can adjust the bios or kernel patcher to boot another path (e.g. E:\dashboard\tray open\dashboard.xbe or something in that nature so it looks more clean. The kernel patcher can be adjusted by editing the source and assembling. A bios can be adjusted by opening it in special tool (for x2 bioses that xbtool and for evox bioses it's evtool)