Post by: 82ross on January 16, 2004, 03:56:00 AM
This will help so many people.
Post by: Bizarro on January 16, 2004, 04:26:00 AM
one recommendation on the tool.
add in a funciton that shifts the priority of the cdrom boot
move "\Device\CdRom0\default.xbe" in the unpacked bin after the dashboards.
i already did this manualy and it seems to work to my satisfaction.
i'm sure there are others that still want to boot to the dash if there
is a disk in the dvd rom when powering up.
now that people are bugging you to update the tool, you'll probably see why NghtShd got fed up.
Thanks again!
Post by: nuzzy on January 16, 2004, 04:51:00 AM
Post by: ZaPhOd on January 16, 2004, 05:49:00 AM
Post by: devlkore on January 16, 2004, 05:52:00 AM
Nice work on the DC BTW.
Post by: heinrich on January 16, 2004, 05:52:00 AM
| QUOTE (Plagued @ Jan 16 2004, 10:01 AM) |
| People may well start bugging you for features like the ability to change the Front LED colour? beg beg |
I don't think that will happen until/if nghtshd releases his most recent sources. I think that he did most of the work on the fan speed and led change code injection himself, so its understandable that he wants to keep the code to himself. I would hope that if really does drop the project for good that he would release the source though.
Post by: burnerO on January 16, 2004, 07:56:00 AM
I'm not as hardcore as some of you (fan modding), but this works for my purposes as I only remove the animation/trademark, and customize the colors.
As far as the led goes, this green to red tutorial is very simple:
http://xbox-scene.co...s/front-led.php
Also, if anyone knows of a site with color presets, I'll start converting/posting a few.
Post by: nagmine on January 16, 2004, 08:26:00 AM
Post by: Bizarro on January 16, 2004, 08:29:00 AM
X Lip 00 01 00
X Lip Highlights 4B 9B 4B
X Inner Wall 17 6A 21
X Inner Glow 01 DF CB
"Xbox" Text 13 CA 62
RED
00 01 00
66 66 FF
00 00 D9
A4 A4 FF
2F 2F FF
ORANGE
00 01 00
20 68 FF
00 2A A5
5B AD FF
20 68 FF
BLUE
00 01 00
FF 00 00
8B 00 00
FF FF C0
DA 65 17
DARKER BLUE
00 01 00
FD 00 00
9F 00 00
FF 8A 8A
8B 00 00
GRAY
00 01 00
7F 7F 7F
66 66 66
FF FF FF
7F 7F 7F
PURPLE
00 01 00
82 00 4B
5E 00 36
FF 22 A2
79 00 46
YELLOW
00 01 00
00 FF FF
00 D7 FF
E0 FF FF
00 FF FF
copied these presets from Bloody Mary's bios collection
Post by: HAL2001 on January 16, 2004, 09:10:00 AM
I had been holding out on upgrading my bios until I could customize it. It worked perfectly the first time!
For those not sure what RGB values to put into your 4980.ini, I used XBtool Color BIOS Preset Maker to determine the values. Just find the color and take the RGB values from the upper left hand corner.
Again, great work! Thanks a lot!
Post by: nagmine on January 16, 2004, 09:32:00 AM
| QUOTE |
| For those not sure what RGB values to put into your 4980.ini, I used XBtool Color BIOS Preset Maker to determine the values. Just find the color and take the RGB values from the upper left hand corner. |
yeah i did the same thing worked great
Post by: Bogus8 on January 16, 2004, 10:34:00 AM
So did I miss some trick on getting xbtool to work with 4980?
Thanks in advance!
Post by: Xbox-Savage on January 16, 2004, 10:42:00 AM
I LOVE OPENSOURCE
Post by: ...ReLLiK on January 16, 2004, 12:40:00 PM
| QUOTE (burnerO @ Jan 16 2004, 08:22 AM) | ||
|
How 'bout ya add a dash boot order...
Dash 1 - 0x0002d158-0x0002d167
Dash 2 - 0x0002d168-0x0002d177
Dash 3 - 0x0002d178-0x0002d187
Dash 4 - 0x0002d188-0x0002d197
Dash 5 - 0x0002d198-0x0002d1a7
Dashes are:
avadash.xbe 61 76 61 64 61 73 68 2E 78 62 65 00 00 00 00 00
evoXdash.xbe 65 76 6F 58 64 61 73 68 2E 78 62 65 00 00 00 00
mxmdash.xbe 6D 78 6D 64 61 73 68 2E 78 62 65 00 00 00 00 00
neXgen.xbe 6E 65 58 67 65 6E 2E 78 62 65 00 00 00 00 00 00
xboxdash.xbe 78 62 6F 78 64 61 73 68 2E 78 62 65 00 00 00 00
unleashX.xbe 75 6E 6C 65 61 73 68 58 2E 78 62 65 00 00 00 00
You can just tags to the ini to fill out...
Just a thought, I know this works ' cause I changed mine...
Post by: randomidiot on January 16, 2004, 01:04:00 PM
Post by: skorchir on January 16, 2004, 02:18:00 PM
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
Post by: bi786 on January 16, 2004, 02:21:00 PM
. 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
Post by: burnerO on January 16, 2004, 03:48:00 PM
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.
Post by: NghtShd on January 16, 2004, 04:56:00 PM
| 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).
Post by: muerte on January 16, 2004, 05:24:00 PM
Post by: HiRoll3r on January 16, 2004, 05:50:00 PM
| 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
Post by: bebrewer1 on January 16, 2004, 07:09:00 PM
Post by: pstar26 on January 16, 2004, 07:10:00 PM
it would be nice if this could be added to the tool.
Post by: pstar26 on January 16, 2004, 07:11:00 PM
Post by: burnerO on January 16, 2004, 07:25:00 PM
| 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.
Post by: Bizarro on January 16, 2004, 07:54:00 PM
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
Post by: pstar26 on January 16, 2004, 09:03:00 PM
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.
Post by: ...ReLLiK on January 16, 2004, 09:04:00 PM
| 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... lolALSO PLEASE NOTE the forum got rid of the backslashes!
Post by: b16mcc on January 16, 2004, 11:57:00 PM
I made up both files , 4981.06 & 4981.67 both tested working just fine.
Post by: burnerO on January 17, 2004, 08:50:00 AM
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
Post by: NghtShd on January 17, 2004, 09:57:00 AM
| QUOTE |
| I've seen many projects canned, simply because the author was unnecessarily flamed by a few ungrateful children. |
Check out my mail bag page for an example of an ungrateful child. Not that I would ever let an idiot like that stop a project.
Post by: XBoxgeek on January 17, 2004, 10:05:00 AM
| QUOTE (NghtShd @ Jan 17 2004, 07:57 PM) | ||
Check out my mail bag page for an example of an ungrateful child. Not that I would ever let an idiot like that stop a project. |
Now that's funny
Post by: ChrisF on January 17, 2004, 01:00:00 PM
NghtShd - that Mailbag is the funniest shit. What a freaking moron. Like someone who can't accept that he made an error and just keeps trying to stuff that foot further and further down his throat.
Post by: bigshooter13 on January 17, 2004, 03:22:00 PM
| QUOTE (NghtShd @ Jan 17 2004, 01:57 PM) | ||
Check out my mail bag page for an example of an ungrateful child. Not that I would ever let an idiot like that stop a project. |
That poor poor, extremely computer illiterate guy. That must really be tough not knowing one save button from the other.
I feel sorry for you NghtShd getting all of those kind of people. But then again it must be fun every now and then seeing how dumb some people truly are and how they won't admit that they made a mistake.
Post by: Heykrop on January 17, 2004, 04:30:00 PM
| QUOTE (NghtShd @ Jan 17 2004, 06:57 PM) | ||
Check out my mail bag page for an example of an ungrateful child. Not that I would ever let an idiot like that stop a project. |
That guy is in our gene pool. Quick! everyone, except Mike, get out and piss in it so they'll have to clean it. I'm sorry I have a 3 year old and am fully confident that even he could press the correct button. Someone check Mike's meds. I think he needs another dose.
Post by: tox on January 20, 2004, 02:08:00 PM