Topic: Tutorial For Converting Xbox Retail To Xbox Devkit (Read 418 times)

Artifex · « **Reply #30 on:** July 22, 2003, 02:55:00 PM »

QUOTE (BenJeremy @ Jul 22 2003, 11:47 PM)

QUOTE (Dgege @ Jul 22 2003, 05:44 PM)

Ok.
When I remove xbdm.dll, I get a black screen, and LED cycling (Orange and Red)
If I replace xshell.xbe with a debug version of Evox, same thing happens (Orange and Red + Black screen)
I'll etst some more later this evening, gtg to the movies now ! (Having a g/f doesn't always help !!)

I don't understand why you would replace xbshell.xbe with evox - this makes absolutely ZERO sense to me.

...as does removing the xbdm.dll

I assume this is after you launch the Phoenix Loader to load in 5558 Debug.

Really, you should NOT run Evo-X during development. Run the XDK Launcher (preferred) or MS Dash - nobody should be interested in removing XBDM.dll or using Evo-X; just running a true Debug BIOS is great (any word yet, Artifex?)

Yes, here I am. :-)

We asked him to remove the dll/xbe in conversation with him, in order to pinpoint why the bios would fail to boot.

It appears from my experimentation that these are not the only 2 files that are needed from the debug kit. :-)

I have confirmed this working, both as described, and in a softmod only scenario.
Font Hacks (reloaded, in this case)->EvoX->Phoenix Loader w/ 5558 bios->DEBUG KIT!!!

Phoenix will be releasing some more formal information, and a new version of the Loader soon.

--Artifex

BenJeremy · « **Reply #31 on:** July 22, 2003, 03:01:00 PM »

QUOTE (Artifex @ Jul 22 2003, 06:55 PM)

QUOTE (BenJeremy @ Jul 22 2003, 11:47 PM)

QUOTE (Dgege @ Jul 22 2003, 05:44 PM)

Ok.
When I remove xbdm.dll, I get a black screen, and LED cycling (Orange and Red)
If I replace xshell.xbe with a debug version of Evox, same thing happens (Orange and Red + Black screen)
I'll etst some more later this evening, gtg to the movies now ! (Having a g/f doesn't always help !!)

I don't understand why you would replace xbshell.xbe with evox - this makes absolutely ZERO sense to me.

...as does removing the xbdm.dll

I assume this is after you launch the Phoenix Loader to load in 5558 Debug.

Really, you should NOT run Evo-X during development. Run the XDK Launcher (preferred) or MS Dash - nobody should be interested in removing XBDM.dll or using Evo-X; just running a true Debug BIOS is great (any word yet, Artifex?)

Yes, here I am. :-)

We asked him to remove the dll/xbe in conversation with him, in order to pinpoint why the bios would fail to boot.

It appears from my experimentation that these are not the only 2 files that are needed from the debug kit. :-)

I have confirmed this working, both as described, and in a softmod only scenario.
Font Hacks (reloaded, in this case)->EvoX->Phoenix Loader w/ 5558 bios->DEBUG KIT!!!

Phoenix will be releasing some more formal information, and a new version of the Loader soon.

--Artifex

OK... my bad.... yeah, Debug BIOS needs to be run under a certain set of circumstances, unless it's been hacked, as in the Complex 4627 1.03 Debug BIOS, otherwise it probably EXPECTS those files, hence your inability to run them when you tested.

This is great news indeed!

Now if we could standardize the basic requirements to get all other 'hacked' BIOSes running under the loader, I think the tale will be complete!

garlic · « **Reply #32 on:** July 23, 2003, 02:47:00 PM »

just wanted to point out a couple things.. just for the hell of it.

i've got tatx installed with the 4627 dash on by xbox. booting the phoenix loader the first time works, but then the introlock file is made and must be deleted before it can run again. x2 bfm works fine. i tried 5558 just for the hell of it. it seems to load but then freezes (probably do to having an old xdk installed) its not phoenix's fault as making it xboxrom.bin on d: freezes up as well

oh well just thought i'd get that posted

BenJeremy · « **Reply #33 on:** July 23, 2003, 02:52:00 PM »

QUOTE (garlic @ Jul 23 2003, 06:47 PM)

just wanted to point out a couple things.. just for the hell of it.

i've got tatx installed with the 4627 dash on by xbox. booting the phoenix loader the first time works, but then the introlock file is made and must be deleted before it can run again. x2 bfm works fine. i tried 5558 just for the hell of it. it seems to load but then freezes (probably do to having an old xdk installed) its not phoenix's fault as making it xboxrom.bin on d: freezes up as well

oh well just thought i'd get that posted

There is more you have to do.... I don't believe the BIOS can be used without patching the 2BL.

Iriez · « **Reply #34 on:** July 29, 2003, 06:27:00 PM »

PS - the 4977 runs debug stuff guys. You can use it to launch the xbshell.xbe

Frag Daddy · « **Reply #35 on:** July 30, 2003, 05:08:00 PM »

How do I run games through the debug bios (XDK Launcher)?

BenJeremy · « **Reply #36 on:** July 30, 2003, 05:51:00 PM »

QUOTE (Frag Daddy @ Jul 30 2003, 09:08 PM)

How do I run games through the debug bios (XDK Launcher)?

You put a dashboard in your E:\DevKit directory and use that to launch other games by calling it from the XDKLauncher.

Really very simple.

stcogolin · « **Reply #37 on:** July 30, 2003, 11:46:00 PM »

QUOTE

QUOTE (Frag Daddy @ Jul 30 2003, 09:08 PM)
How do I run games through the debug bios (XDK Launcher)?

You put a dashboard in your E:DevKit directory and use that to launch other games by calling it from the XDKLauncher.

Really very simple.

If you start a game from the E:DevKit dash, do you lose the debug features? Can you still capture?

BenJeremy · « **Reply #38 on:** July 31, 2003, 03:15:00 AM »

QUOTE (stcogolin @ Jul 31 2003, 03:46 AM)

QUOTE

QUOTE (Frag Daddy @ Jul 30 2003, 09:08 PM)
How do I run games through the debug bios (XDK Launcher)?

You put a dashboard in your E:DevKit directory and use that to launch other games by calling it from the XDKLauncher.

Really very simple.

If you start a game from the E:DevKit dash, do you lose the debug features? Can you still capture?

The BIOS remains active until a power cycle with the Phoenix Loader.

Wishi · « **Reply #39 on:** August 03, 2003, 04:16:00 AM »

Is this a couple of merged threads? I don't seem to remember some posts but do others.

Anyway, hydrasworld, just though I'd say we'd be glad to host this (with full credit obviously) if you'd like as there are quite a lot of first timers who come into the chat asking on this particular topic.

EliteModz · « **Reply #40 on:** August 16, 2003, 12:07:00 PM »

Is there a reason why everything is like....Pink?

EliteModz · « **Reply #41 on:** August 16, 2003, 12:11:00 PM »

Its weird, all my screen's have pink hue and i get networking errors when tryint to play split screen halo

EliteModz · « **Reply #42 on:** August 16, 2003, 07:03:00 PM »

Well, I got the pink hue to go away. Anyone wanna clue me in on howto get Halo to play on XDK so i can take screen shots?

Dgege · « **Reply #43 on:** August 20, 2003, 11:36:00 AM »

Only software signed with Retail flag can be run.
You can use CXBE to enable that flag.
And for the xdk examples, just compile them in VS.NET and run.

Hope that helps

Dgege

SpencerBr · « **Reply #44 on:** August 20, 2003, 10:07:00 PM »

CODE

[xbdm]
dbgname name=sNt
staticip use=1, addr=0x00000000
subnet addr=0x00000000
gateway addr=0x00000000
memtrack flags=0x0 stackdepth=0x0
dbgoptions crashdump=1 dpctrace=1

In DEVKIT folder I found this: "xbdm.ini".
I would like to put my static ip adress here, because dhcp doesn't work.
but "0x000...." I dont understand this, lol

Anyone can give me codes for:
ip: 192.168.0.2 = ?x?

?
gateway: 192.168.0.2 = ?x?

?
smask: 255.255.255.0 = ?x?

?

I would like to know what best, lame(easy), gui program to patch xbe to debug xbe (for running on xdk launch) If possible run for example.. my remoteX, Xbmp, games, etc from xdk launcher. And more, can i take a screenshot of these programs running?

I know some about running softs from xdk, because i read here, i just need put my softs on:

e:
-devkitt
+tools

right?
Thanks again and sorry for bad english.

Author Topic: Tutorial For Converting Xbox Retail To Xbox Devkit (Read 418 times)