Print

[skorchir]

well for dash support you can use two bits from msxboxdash when renamed to xboxdash dunno if u can steel anymore, i havent tried but i didnt need more then two bits.

i was going to attempt cutting down the boot sequence from 5 dashs to 4 and extend the dash names but i havent tried this yet.

also it could be a problem if people make the dash names too long. there would need to be a check to make sure you dont go over the amount of bits supplied

[bi786]

. I just flashed two boxes with modded logo colours just perfect . Thanks to everyone who has given input like the colours in RGB etc , keep up the good work  

[burnerO]

And just for fun, here's my colors.

X Lip Color(R G B): 000 000 000
X Lip Hlight Color: 000 000 000
X Inner Wall Color: 255 255 255
X Inner Glow Color: 000 000 000
Xbox Text Color   : 187 221 255

I think they're rather swell.

[NghtShd]

QUOTE

With NghtShd making threats of not updating XBtool

Just for the record, I wouldn't characterize it as a threat. It sounds like I'm trying to extort something out of someone.

Although 4981 may be nearly identical to 4980, I'll wait till that's out and then look into doing a patcher for it (just to be on the safe side).

I'll also try to get my latest source code out, along with the assembley language patch file sources.

After that, I'm looking for something new and different, though I'd also be glad to assist if someone wanted to do an Xbox hosted version of XBtool (my feeble DirectX skills prevent me from doing it a user interface, though I've always thought it would be cool).

[muerte]

i've been suggesting this for a long time.  it would be amazing if you could choose a bank, turn off protection of the flash bank, and edit the bios.  you could take a page out of PBL's book possibly.  Also, it would be awesome to just be able to edit a bios.bin on your xbox as well.  AWESOME!  Please work on this nghtshd!

[HiRoll3r]

QUOTE (burnerO @ Jan 16 2004, 05:44 PM)

Partition(C/E/F/G): C Boot Avalaunch.xbe: 1 Boot Evoxdash.xbe : 2 Boot Mxmdash.xbe  : 3 Boot Unleashx.xbe : 4 Boot Xboxdash.xbe : 5 Trademark         : Y Splash            : Y

So, does this mean, if I use this tool, that I'll have to rename avadash.xbe (the default filename for the dash in 4980) to avalaunch.xbe on my hard drive? I know it's a stupid question, but flashing the X-Bit, regardless of what DMS says, is kind of a pain in the ass, so I do it as little as possible

[bebrewer1]

[pstar26]

Bizarro can you tell me how u changed the boot sequence on the cdrom drive after the dashes, I've tried several times unsuccessfully, so in the meantime i just disabled it by changing default.xbe to defaul1.xbe so i can leave a cd in the drive.
it would be nice if this could be added to the tool.

[pstar26]

sorry double post

[burnerO]

QUOTE (pstar26 @ Jan 17 2004, 05:10 AM)

Bizarro can you tell me how u changed the boot sequence on the cdrom drive after the dashes, I've tried several times unsuccessfully, so in the meantime i just disabled it by changing default.xbe to defaul1.xbe so i can leave a cd in the drive. it would be nice if this could be added to the tool.

If someone can better explain that, along with the offsets, I'll toss it in.

[Bizarro]

i only changed it so evox could boot before the dvdrom.

in xboxkrnl.img, go to hex offset
[0x0002de50h]

just change the priority from this
\Device\CdRom0\default.xbe  \Device\Harddisk0\Partition0\evoXdash.xbe

to this
\Device\Harddisk0\Partition0\evoXdash.xbe  \Device\CdRom0\default.xbe

in hex lt looks like this:
change this
5C 44 65 76 69 63 65 5C 43 64 52 6F 6D 30 5C 64 65 66 61 75 6C 74 2E 78 62 65 00 00 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 65 76 6F 58 64 61 73 68 2E 78 62 65

to this
5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 65 76 6F 58 64 61 73 68 2E 78 62 65 00 00 5C 44 65 76 69 63 65 5C 43 64 52 6F 6D 30 5C 64 65 66 61 75 6C 74 2E 78 62 65

[pstar26]

Bizarro i Tried that and it does not do anything different than what i did by disabling cd on boot, for instance if evox fails to load it does not boot  from cd it just frags 13.

This could be a problem for Tsop people if they do this and something happens to evox they can't boot to cd to enable ftp to fix the problem.

[...ReLLiK]

QUOTE (Bizarro @ Jan 17 2004, 12:54 AM)

i only changed it so evox could boot before the dvdrom. in xboxkrnl.img, go to hex offset [0x0002de50h] just change the priority from this DeviceCdRom0default.xbe  DeviceHarddisk0Partition0evoXdash.xbe to this DeviceHarddisk0Partition0evoXdash.xbe  DeviceCdRom0default.xbe in hex lt looks like this: change this 5C 44 65 76 69 63 65 5C 43 64 52 6F 6D 30 5C 64 65 66 61 75 6C 74 2E 78 62 65 00 00 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 65 76 6F 58 64 61 73 68 2E 78 62 65 to this 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 65 76 6F 58 64 61 73 68 2E 78 62 65 00 00 5C 44 65 76 69 63 65 5C 43 64 52 6F 6D 30 5C 64 65 66 61 75 6C 74 2E 78 62 65

This could be tough to implement as it probably would be safer to replace the boot priority to make them in order of the boot sequence followed by the cddrive last... (OR WOULD IT???)

Originally Here:
5C 44 65 76 69 63 65 5C 43 64 52 6F 6D 30 5C 64 65 66 61 75 6C 74 2E 78 62 65 00 00 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 65 76 6F 58 64 61 73 68 2E 78 62 65 00 00 00 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 61 76 61 64 61 73 68 2E 78 62 65 00 00 00 00 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 6D 78 6D 64 61 73 68 2E 78 62 65 00 00 00 00 5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 78 62 6F 78 64 61 73 68 2E 78 62 65 00 00 00


That is a range of 0x0002DE50 to 0x0002DF1C.

Broken Down:
5C 44 65 76 69 63 65 5C 43 64 52 6F 6D 30 5C 64 65 66 61 75 6C 74 2E 78 62 65 00 00 DeviceCdRom0default.xbe

5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 65 76 6F 58 64 61 73 68 2E 78 62 65 00 00 00 DeviceHarddisk0Partition2evoXdash.xbe

5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 61 76 61 64 61 73 68 2E 78 62 65 00 00 00 00 DeviceHarddisk0Partition2avadash.xbe

5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 6D 78 6D 64 61 73 68 2E 78 62 65 00 00 00 00 DeviceHarddisk0Partition2mxmdash.xbe

5C 44 65 76 69 63 65 5C 48 61 72 64 64 69 73 6B 30 5C 50 61 72 74 69 74 69 6F 6E 32 5C 78 62 6F 78 64 61 73 68 2E 78 62 65 00 00 00 DeviceHarddisk0Partition2xboxdash.xbe

Notice there is no DeviceHarddisk0Partition2neXgen.xbe in there...

Anyways, but now it is cut and paste so to speak and to rearrange them in the order of your chosen boot sequence.
Then, followed up last with the cdrom hex. But what about the 5th priority boot? is it just dropped? (aka nexgen above). This could take some testing...
AND... what about the partition set under the X3 Magic Section? OFFSET 0x0002D154?? And would we change the above (highlighted) from 32 to 36 to use partition 6 instead 2?

Sorry if this is a bit confusing?  as it is late... lol
ALSO PLEASE NOTE the forum got rid of the backslashes!

[b16mcc]

Nice one burner it works a treat !

I made up both files , 4981.06 & 4981.67 both tested working just fine.

[burnerO]

Hey guys, just wanted to speak my peace before NghtShd updates XBtool and this post fades into oblivion.

Once again, I'd like a chance to thank everyone involved.  It does my heart well to know that we're able to band together in "time of need" to see that something is done.  It is this spirit of community; of positive encouragement that drives the developers to code.  None of this would have ever occurred without the foundation that NghtShd so generously has provided with XBtool.  I can recall the first time I'd seen the boot sequence with the flubber animation, and thinking how tiring it must be to endure it every time the system is powered on.  My friends were quick to point me in the direction of XBtool, and I've used it ever since.  I'd also like to thank skorchir and 82ross for their dedication in picking apart the kernel.  Often times people like oz_paulb, with his LBA48 code go unrecognized, although he's the reason many of you have obnoxiously large drives in your system.

If this has done little more than serve to attest to the popularity of XBtool, then I'm ok with that.  This certainly wasn't any grand production; just a couple of days translating and verifying the provided hacks to a workable state.  Often times developers underestimate the impact of their work, and that's a shame.  I've seen many projects canned, simply because the author was unnecessarily flamed by a few ungrateful children.  If anything, NghtShd should take note of the twelve hundred some odd hits this post has accumulated, and realize how much what he does is appreciated.  If you're staring at a colorful boot logo when your system is launched, it wouldn't hurt to take a moment to tell NghtShd thanks.  The same could be said for any of the various applications/emulators/games released on a regular basis that we've come to expect. Typically we forget that there's someone tireless hacking away at code for free, in their spare time nonetheless.  It's reasons such as these that I'm angered when seeing flaming occur out of sheer ignorance.  These are the kids who download Surreal 64, and race to the boards to spam about how much it "sucks", because they're unable to play Conker's Bad Fur Day, or any other game that they've never legitimately owned to begin with that really get under my skin.

I mod systems, albeit tsop, free of charge for my friends.  It's not that I couldn't use the money, because quite the contrary I'm a typical desolate college student.  But rather, I feel that in sharing the joy of emulation and sense of excitement that comes from tinkering with the system, that I'm giving back in a sense.  It would discredit the works of everyone who's contributed to the applications that I use, the Xecuter/Avalaunch/ Evolution-X teams; lantus, Xport, oDD, and the countless other authors who's applications I use on a daily basis for me to sell their work.  I'm more than happy to mod someone's system, simply on the premise that they'll be able to play some of their old favorite games.  I assure you that emulation really is a gift, especially after having played emulated nes titles with children who'd have never have been exposed to them otherwise.  It's great for me to be able to play the games that I hold in such high regard, and show them to kids with such a level of enthusiasm that allows them to see beyond the limitations of the original hardware.

My apologies if this comes off like a long-winded rant; I'm frequently guilty of writing as much.  I'm sure that NghtShd will return to XBtool momentarily, and am glad that I've not "hosed" anyone's bios in the meantime.  Take it easy.  -Kyle