Post by: skorchir on January 11, 2004, 01:41:00 AM
I will keep adding any findings i come by
-------------------------------------------------------------------------------
well i got progress in getting my boot order working great
i got my boot sequence as follows
d:boot.xbe
c:avalaunch.xbe
c:evoxdash.xbe
c:mxmdash.xbe
c:nexgen.xbe
c:xboxdash.xbe
there seems to be 5 boot options for dashboards i tested it and it boots all in that order. anyway what i did to extend my dash names was simply borrow bits. for each bit removed a bit is inserted. for each bit longer a bit was borrowed from a not used or inserted bit.
i opened Hex Work Shop 4.2 loaded xboxkrnl.img
went to Edit, Find and searched for 'evox' All Instances, ASCII String.
and it showed two sections containing that string
the first one was under X3MAGIC so i fixed it to my liking
borrowing and supplimenting at the end of each xbe name bits '00'. After some customizing i went to the second instance which contained actual boot locations in visable text.
CdRom0boot.xbe...DeviceHarddisk0Partition2avalaunch.xbe
well again i changed what i needed. borrowed bits. in this part i borrowed some bits from cdrom. i used boot.xbe oppsed to default.xbe
apparantly the only thing that works in this part is the Cdrom boot xbe. ive changed it and it works but it seems the rest of the hard drive partition and xbe names are overwritten by x3magic. this is not totally confirmed. I can confirm the cdrom boot xbe remains working.
saved my kernel packed it with xbtool v1.0.12, flashed with evox and all is good :) works to my expectations
This part here is taken from the other thread written by 82ross adding it to keep all information in one post :)
| QUOTE |
TUTORIAL FOR X2 4980 DASHBOARDS ON A DIFFERENT PARTITION Software needed: XBtool Any hex editor (UltraEdit32 is used in this example) 1) Start XBtool. 2) In the "Bios Type" drop down box make sure it says "Multi". 3) Click unpack. 4) Locate and selesct the 4980 bios of your choice and click "Open". 5) Minimize XBtool and goto the folder where your bios was located you should see a folder with the same name as your bios. Enter this folder. You should see 3 files. 2bl.img remainder.img xboxkrnl.img 6) Open up xboxkrnl.img in your HexEditor. 7) In your hexeditor find the Goto function. In UltraEdit32 its "Search>Goto Line/Page" (Ctrl+G) 8) In the box that pops up enter the address 0x2d154. 9) This should jump to that location. In UltraEdit32 it should look like this: 0002d150h: 00 01 00 00 02 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash The first section befiore the : is the address The 16 pairs of numbers after that is the hexcode After the ; is the ASCII version of the hex code. 10) The number in bold is the code we are interested in (0x2d154). 02 means partition2 11) Click on the 2 in the 02 and press: 1 to boot dashboards from partition E: 0002d150h: 00 01 00 00 01 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash 6 to boot dashboards from partition F: 0002d150h: 00 01 00 00 06 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash 7 to boot dashboards from partition G: 0002d150h: 00 01 00 00 07 01 00 00 65 76 6F 58 64 61 73 68 ; . . . . . . . . evoXdash 12) Close and save this file. 13) Go back to XBtool making sure Multi is still selected. 14) Click on the "Pack" button. 15) Select the xboxkrnl.img you have just edited. 16) A Save As dialog pops up. Enter the name you wish the bios to be called. 17) Your new bios will be in the same folder as your xboxkrnl.img. 18) Flash your modchip with this new bios. Following on from 0x2d154 you can see the names of the four dashboards in the order they will be loaded. You can rename these if you wish. I would keep the length of the names the same. Only overwrite current names. Do not extend the names as this maight break the bios. This will probably change in the future. |
if you attempt this BE CAREFUL not to borrow anything not 00 and where you borrowed it from.
-------- TRADE MARK SYMBOL --------
To Remove The 'TM' symbol from the boot simply goto location
00060968 and change hex values 18 to 20
you can also do a hex search for 455c c1e0 1889 and change the 18 to 20
----------- X COLORS ------------
you can get your hex colors by takeing the red,green and blue custom numbers and using the windows calculator in scientific mode and enter the number in decimal and click hex to convert to hex.
X Lip
HEX Offset: [0x0002D1A8]
was 00 01 00
X Lip HighLights
HEX Offset: [0x0002D1AC]
was 4B 9B 4B i changed it to FF 00 00 for a blue color :D
In here it goes backward BLUE GREEN RED (when doing custom colors) so FF = 255 Blue 00 green 00 red
X Inner Walls
HEX Offset: [0x0002D1B0]
was 17 6A 21
X Inner Glow
HEX Offset: [0x0002D1B4]
Was 01 DF CB
XBOX Text
HEX Offset: [0x0002D1B8]
was 13 CA 62 i canged to DA 65 17 for another custom blue text.
ALL TESTED AND WORKS PERFECT! :D
WOOT! :D
---------- SPLASH LOGO ------------
HEX Offset: [0x0005A81C]
was 75 0B to disable change to 90 90
---------- NO ANIMATION -------------
HEX Offset:
[0x0005B222]
was 74 09 now 90 90
[0x0005B989]
was 74 09 now 90 90
[0x0005C083]
was 75 0EE9 979D now E9 0B00 0000
[0x0005C0AB]
was 75 05E8 A99D now E9 0200 0000
---------- X LOGO ----------------
To remove this
[0x0005B56C]
was E8A7 F7FF FF now 9090 9090 90
[0x0005C06D]
was E8 5AF3 FFFF now 90 9090 9090
also add
[0x0005B222]
was 74 09 now 90 90
[0x0005B989]
was 74 09 now 90 90
[0x0005C083]
was 75 0EE9 979D now E9 0B00 0000
[0x0005C0AB]
was 75 05E8 A99D now E9 0200 0000
------------------------------------------------------------------------------
I sure hope NghtShd updates xbtool it was a very useful tool and probly one of the most needed app for the xbox. dont want to see a good program go out of production :(
Hopefully he can use this info to update XBTool or someone else can possibly make a small patcher for this!
I will see what else i can find but a lot of the work is already found for you
Once Again Unless You Can Recover From a Bad Flash Or Improper Editing USE AT OWN RISK. I TAKE NO RESPONSIBILITY!
Enjoy Happy Hacking B)
This post has been edited by skorchir on Jan 14 2004, 04:02 AM
Post by: Xbox-Savage on January 11, 2004, 12:12:00 AM
amazing!! 
nice
Post by: dzv on January 11, 2004, 05:35:00 AM
| CODE |
| \Device\Harddisk0\Partition2\evoXdash.xbe |
to
| CODE |
| \Device\Harddisk0\Partition6\evoXdash.xbe |
However, this didn't make any difference, it still booted to C:\EvoXdash.xbe first
It seems that the first section of boot locations (something called X3 Magic) over-rides the other settings. The problem is, this 'X3 Magic' thingy doesn't allow you to specify the partition, only the filename.
Anybody had any luck with getting it to boot from F: ?
This post has been edited by dzv on Jan 11 2004, 01:37 PM
Post by: 82ross on January 11, 2004, 07:36:00 AM
You can change replace all the other strings with 00's and it will make any difference. They are useless. Dont bother changing the string from partition2 to 6 your wasting your time.
Goodjob skorchir. Youve found most things people have requested. :) It deserves its own thread.
EDIT:
Thanks man :)
This post has been edited by 82ross on Jan 11 2004, 05:30 PM
Post by: skorchir on January 11, 2004, 08:30:00 AM
| QUOTE |
The only one im not sure about is the cdrom one, i havent tested that. |
yup this one works ive changed and tested it :)
Post by: skorchir on January 11, 2004, 11:53:00 AM
Also if anyone knows of anytools that will dissassemble the xboxkrnl.img file into C or any other interpretable language so i can get a closer look and possible re-assemble please let me know.
---Another Discovery---
well i noticed that the new kernel was significantly smaller then their previous ones.. after a bit of poking around i discovered that at the end of their previous kernel 4979 there is a part "Kernel Expansion" which contained the front LED and Fan Speed Offsets. It seems this was removed from the 4980 kernel. What i tried was copying and insertting this section into the new kernel, changed some values, packed it and flashed it to my xbox but didnt see any change same boot up no led change nor fan speed increase.
What can this mean? Well either its been removed from their kernel totally ? or its been moved and simplified in the code.
Il keep messing around to see what i can find.. im actually enjoying this :D
anyone is welcome to support this thread with any help, guidance or information.
This post has been edited by skorchir on Jan 11 2004, 08:24 PM
Post by: NghtShd on January 11, 2004, 01:15:00 PM
| QUOTE |
| ---Another Discovery--- well i noticed that the new kernel was significantly smaller then their previous ones.. after a bit of poking around i discovered that at the end of their previous kernel 4979 there is a part "Kernel Expansion" which contained the front LED and Fan Speed Offsets. It seems this was removed from the 4980 kernel. What i tried was copying and insertting this section into the new kernel, changed some values, packed it and flashed it to my xbox but didnt see any change same boot up no led change nor fan speed increase. What can this mean? Well either its been removed from their kernel totally ? or its been moved and simplified in the code. |
I think you're referring to my XBtool kernel additions. Were you looking at a kernel which had been previously patched using XBtool?
I add my own dashboard loading function (mostly copied from one of the X2 kernels, as I recall, so I probably shouldn't refer to it as my own) and I put my LED color and fan speed setting calls there. It sounds like that's what you're referring to. There's a total of 32k added on to a stock BIOS, though most of it is just slack space, the rest being LBA48 code (where applicable), the dashloader/LED/fan functions, and some code for keeping the expanded kernel code from getting deleted.
Post by: nuzzy on January 11, 2004, 11:41:00 AM
Post by: skorchir on January 11, 2004, 01:37:00 PM
i was reading a unedited kernel but i did save it with XBTool as i was comparing differences between other modified kernel images and thus comparing similaraties to the 4980 kernel this is how i was able to find the kernel hacks within the new kernel.
Im hopeing you can take the information found and update parts of xbtool even if it doesnt do everything just the simple patches already found it makes things easier for people.
:beer:
Post by: Heykrop on January 11, 2004, 06:34:00 PM
| QUOTE (dzv @ Jan 11 2004, 12:35 PM) | ||||
Great work, but I still can't get it to boot from F: first. I had already tried to do this before, by changing the first boot location from
to
However, this didn't make any difference, it still booted to C:EvoXdash.xbe first It seems that the first section of boot locations (something called X3 Magic) over-rides the other settings. The problem is, this 'X3 Magic' thingy doesn't allow you to specify the partition, only the filename. Anybody had any luck with getting it to boot from F: ? |
Yes I did. I followed the instructions that were originally posted by 82ross and are quoted in the first post of this thread. I simply changed the 02 value at offset 0x2d154 to a 06. Saved the file and then repacked with XBTOOL.
All my dashboards are on F: and it booted fine. I may now go back and try the bit borrowing procedure to see if I can get it to boot unleashx.xbe on F: I tried it last night by only renaming a dashboard item in the X3Magic section of the bios and by adding the extra character it caused an error 13 when trying to boot to that item.
I'm aslo going to try the color offset changes as well as the TM removal.
Post by: 82ross on January 12, 2004, 12:55:00 AM
This post has been edited by 82ross on Jan 12 2004, 08:59 AM
Post by: Pathetic on January 12, 2004, 03:12:00 AM
| QUOTE (skorchir @ Jan 11 2004, 09:41 AM) |
| ---------- NO ANIMATION ------------- HEX Offset: [0x0005B222] was 74 09 now 90 90 [0x0005B989] was 74 09 now 90 90 This removed the startup animation. Side Effect: On Power Up Animation was removed successfully but the sound plays for 1/10th of a second very minor and stops. can't even hear or notice it unless you know its there :D This still could be potentially dangerous. |
Does this mean it hangs, won't boot ?
I want to diable animation but im not shure to try this
Post by: Heykrop on January 12, 2004, 04:02:00 AM
| QUOTE (82ross @ Jan 12 2004, 07:55 AM) |
| What extra character? Just type over evoxdash with unleashx (under the x3 magic part only), they are both 8 characters long so it shouldnt be a problem. If you wanna type over the other 3 locations just shorten the name of your dashboard xbe to7 or 6 characters accordingly. |
Thanks for that info. I was aware of that. I usually have 2 or 3 dashboards on the drive as a failsafe incase EvoX or another fails. I generally leave EvoX as my default dash so I can manage Chameleon functions. I have links in all of them to each of the others. This was my method of staving off the system booting to the M$ dash if EvoX failed for one reason or another.
So I could have changed evoxdash.xbe to unleashx.xbe but then EvoX would not be the default. I wanted to replace mxmdash.xbe or nexgen.xbe with unleashx.xbe and that did not work.
Post by: skorchir on January 12, 2004, 09:14:00 AM
| QUOTE (Pathetic @ Jan 12 2004, 06:12 AM) |
| Does this mean it hangs, won't boot ? I want to diable animation but im not shure to try this |
No this actually worked it removed the animation and booted the system there was just a short play of sound on power on it plays for 1/10th of a second hardly noticable. but like i said dont use or try this unless you are able to recover from it
good luck
Post by: skorchir on January 12, 2004, 09:22:00 AM
| QUOTE (Heykrop @ Jan 12 2004, 08:55 AM) |
| So I could have changed evoxdash.xbe to unleashx.xbe but then EvoX would not be the default. I wanted to replace mxmdash.xbe or nexgen.xbe with unleashx.xbe and that did not work. |
you can change evoxdash.xbe to unleashx.xbe to make unleashx your primary dash. now you can overwrite nexgen.xbe or mxmdash.xbe with evoxdash.xbe and steal a bit from another one of the xbe names
this is what my X3 Magic section looks like and it works like a chram :D
| CODE |
| ****X3MAGIC!****........avalaunch.xbe...evoxdash.xbe....mxmdash.xbe.....neXgen.xbe......xboxdash.xbe............ |
this is what it originally was.
| CODE |
| ****X3MAGIC!****........evoXdash.xbe....avadash.xbe.....mxmdash.xbe.....neXgen.xbe......msxboxdash.xbe... |
i renamed msxboxdash to xboxdash. this gave me 2 bits to play with. this is actually all i needed. For your situation it looks like you only need to steal 1 bit so remember to add any unused bits back to the end of the xbe name from which you took it from. unused bit should be added as 00. i hope this helps you. good luck
This post has been edited by skorchir on Jan 12 2004, 05:27 PM
Post by: FLuKE11 on January 12, 2004, 09:45:00 AM
| QUOTE (skorchir @ Jan 11 2004, 07:53 PM) |
| BTW Think This Thread can be pinned? or at least till someone makes a patcher tool |
I AGREE
PLEASE PIN IT UNTIL XBTOOL IS UPDATED
WE LOVE YOU NGHTSHD
SAVE US!
BE A HERO... AGAIN
yes i know the text is huge
Post by: WisdomWolf on January 12, 2004, 11:39:00 AM
Post by: Pathetic on January 12, 2004, 12:25:00 PM
XBtool Color Bios Preset Maker
http://dwl.xbox-scen..._Maker_1.0b.rar
You can change the color and see the results, remember to change from the RGB codes to BGR
My Color Preset is X: 0016E5, XGLOW: E0EEFF, Lip: 0200A8, Lip Spot: 001265
Nothing special
Post by: skorchir on January 13, 2004, 05:58:00 PM
Still USE AT OWN RISK
Post by: dzv on January 13, 2004, 09:29:00 PM
- Multiple boot partition (eg. F:\evoxdash.xbe E:\evoxdash.xbe C:\evoxdash.xbe)
- LED color changing (just red would do for me )
Post by: Heykrop on January 14, 2004, 04:06:00 AM
| QUOTE (dzv @ Jan 14 2004, 06:29 AM) |
Well done to everybody who's been working on this so far. Now, there's just a couple more tweaks I'd like to be able to implement. If anybody can help with these 2 requests, that would be great
|
Nghtshade already posted on those 2 topics. He was inserting his own code into the end of the bios. That was what gave XBTOOL the ability to change the boot partitions and LED color.
Mostlikely inorder for us to be able to change them we would have to get updated code for 4980 and inject it into the bios before repacking.
Post by: Xbox-Savage on January 14, 2004, 04:24:00 PM
WOOOOT!!! , I did it and it worked , everything , colors and partition change , but couldnt remove the trademark , cant find it , also i would like Fan Speed Up. PIN THIS!!!
Post by: luma on January 15, 2004, 10:01:00 AM
Post by: Xbox-Savage on January 15, 2004, 10:13:00 AM
| QUOTE (luma @ Jan 15 2004, 04:01 PM) |
| just cranked out a blue and red 4980 (both 06 and 67) with no ani, no tm, and no splash (left the x on the screen) and all 4 worked great! thanks for the hacking skorchir! |
i cant seem to find the TM Hex offset , i try the one that s writen there but Ultra Edit32 doesnt find it
Post by: ...ReLLiK on January 15, 2004, 11:27:00 AM
Post by: niteblade on January 15, 2004, 12:58:00 PM
Post by: skorchir on January 15, 2004, 03:16:00 PM
| QUOTE (nagmine @ Jan 15 2004, 07:39 PM) |
| hey couldnt someone just make some ppf patches for people ? would make it less complicated i guess for newbs |
yes i was considering something like this but then i was able to find that NghtShd posted his source on his web site. only problem is its an old version 1.0.5
but anyway i started installing VS.NET and am going to look into this code and see if i can whip something up but dont wait on me or expect anything coming. i am merly going to play around and if i can come up with something you will find out. i dont plan on doing a whole lot since 4981 is going to be released and all offsets are going to be relocated again so that will need some tracking down. but dont expect anything i am a very busy and tired person 
and caught up with lots of school work.Post by: FLuKE11 on January 15, 2004, 04:58:00 PM
| QUOTE (skorchir @ Jan 16 2004, 01:16 AM) | ||
yes i was considering something like this but then i was able to find that NghtShd posted his source on his web site. only problem is its an old version 1.0.5 but anyway i started installing VS.NET and am going to look into this code and see if i can whip something up but dont wait on me or expect anything coming. i am merly going to play around and if i can come up with something you will find out. i dont plan on doing a whole lot since 4981 is going to be released and all offsets are going to be relocated again so that will need some tracking down. but dont expect anything i am a very busy and tired person and caught up with lots of school work. |
Hey take your time man. If XBtool isn't gonna be updated ever again, I'm sure we can all wait for you do release whatever you release
I'm personally sticking with 4979 until _someone_ releases an Xbtool type app for 4980/4981. I would mess with hex editing but I have ax xecuter 2.3 Lite, and no programmer. So if the bios goes bad I'm kinda screwed. Not really worth the risk.
So yea. Take your time.
Post by: ...ReLLiK on January 15, 2004, 06:04:00 PM
| QUOTE (FLuKE11 @ Jan 15 2004, 09:58 PM) |
| Hey take your time man. If XBtool isn't gonna be updated ever again, I'm sure we can all wait for you do release whatever you release I'm personally sticking with 4979 until _someone_ releases an Xbtool type app for 4980/4981. I would mess with hex editing but I have ax xecuter 2.3 Lite, and no programmer. So if the bios goes bad I'm kinda screwed. Not really worth the risk. So yea. Take your time. |
It really isn't that complicated. I did mine in about 5-10 minutes and flashed it to a different bank on my x2.1lite and it worked fine... then I just flashed my bank back to normal tested it and then flashed my 4980 back to my main bank... all is well in xboxland! Just use Flash 1.2 on your xbox... as you can flash individual banks! Mine has the colors changed, the no anim and no trademark changed! It is super easy with UltraEdit (The best text viewer able to read tons of formats).
Post by: ^^^Maximus^^^ on January 15, 2004, 11:53:00 PM
Post by: FLuKE11 on January 16, 2004, 01:49:00 AM
| QUOTE (skorchir @ Jan 16 2004, 08:39 AM) |
| i will mess around a bit more but dunno if it will get much further then this.. i am not a very experienced c++ programmer i am just working on the little knowledge i know. I also never worked with win32 c++ programs before i have only done console apps hehe... i might just take an alternate route and make some ppfs but that wouldnt really help much for changing colors unless they were pre-defined. anyway il play some more tomorrow if i have time |
looks good so far
Post by: ZaPhOd on January 16, 2004, 05:48:00 AM
Post by: DBZRacer on January 16, 2004, 12:07:00 PM
so boot sequence would be something like mxmdash.xbe, then unleashx.xbe, then evoxdash.xbe.
I know that there were older vers of the x2 bios out there that xbtool couldn't change before but it's been such a long time and didn't know if that barriers been broken.
Post by: alg5 on January 16, 2004, 12:45:00 PM
| QUOTE (rimmi2002 @ Jan 16 2004, 09:58 PM) |
| Is there any way to change fan speed for 4980? |
of course, but it will be harder to find.
4980 seems to use different code for fan speed than 4979
Post by: heinrich on January 16, 2004, 01:36:00 PM
| QUOTE (alg5 @ Jan 16 2004, 05:45 PM) | ||
of course, but it will be harder to find. 4980 seems to use different code for fan speed than 4979 |
As far as I can tell, there is no code for fan speed (or LED color) in any released bios, that is a function that nghtshd's xbtool put in to make calls to the i2c controller, it's not simply changing existing values.
Post by: NghtShd on January 16, 2004, 04:44:00 PM
Things are further complicated by the fact that the patch code gets moved after the kernel is through with the init section (thats where the DiscardInit patch--devised by oz_paulb--comes in). As you can see, it's kind of a convoluted mess.
You could probably use SantMat's led setting method without resorting to expanding the kernel. You might even be able to patch it up so it changes the fan speed instead. It's been a while since I used SantMat's method and I don't recall exactly what the code it patched looks like (it hooked in around the AV cable check), so I'm not sure if you can do that, but I'm thinking just change the SMBus commands from LED mode/sequence to fan mode/speed.
Post by: Heykrop on January 16, 2004, 08:16:00 PM
| QUOTE (NghtShd @ Jan 17 2004, 01:44 AM) |
| skorchir, those 3 files are binary files containing machine code. XBtool adds 32k to the end of the kernel and adjusts the kernel's PE header to account for that (and to make the init section executable) and sticks those patches in the expanded area. The DiscardInit patch handles making sure that the code added to the end of the kernel doesn't get dumped along with the rest of the init section (it hooks into the kernel's DiscardINITSection function). The other two patch files contain a function to set the fan speed and LED color and a replacement for the dash loading function. The code in those patches gets called by hooking into other kernel functions. Things are further complicated by the fact that the patch code gets moved after the kernel is through with the init section (thats where the DiscardInit patch--devised by oz_paulb--comes in). As you can see, it's kind of a convoluted mess. You could probably use SantMat's led setting method without resorting to expanding the kernel. You might even be able to patch it up so it changes the fan speed instead. It's been a while since I used SantMat's method and I don't recall exactly what the code it patched looks like (it hooked in around the AV cable check), so I'm not sure if you can do that, but I'm thinking just change the SMBus commands from LED mode/sequence to fan mode/speed. |
NghtShd If you do not intend to further develop XBTOOL then do you plan on releasing the source for the last version? 1.0.12 Personally I find it interesting that Team Executer announces XBTOOL like functionality in the X3 chip's OS and there is suddenly no further development for XBTOOL. Are they using your source? Sorry if I sound like I'm on the offensive. Nothing against you. I for one am greatly appreciative of all you have done. I've also fully hexed my 4980 and the only thing I wish I could add is the LED color. I use the alternate color to remind my self that I'm running with the mod on.
Anyway. It would be great to see another release but If not then let me be the first to post
R.I.P. XBTOOL 01-19-03 to 01-05-04
Post by: heinrich on January 16, 2004, 08:40:00 PM
| QUOTE (NghtShd @ Jan 16 2004, 09:56 PM) | ||
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). |
As for the last part, I was actually looking into this today. I don't think it would be too difficult to get running on the xbox, I worked on this a little today with kl0wn, we have a simple UI with some extremely primitive options already, I'll post a few screenshots if anyone is interested in seeing what we've got started.
I agree that the 'x3 live config' does sound like its pretty much a port of xbtool to the xbox, it would be extremely nice to have something for the 'rest of us'.
Post by: heinrich on January 16, 2004, 09:32:00 PM
Post by: NghtShd on January 17, 2004, 07:19:00 AM
Post by: Heykrop on January 17, 2004, 08:35:00 AM
| QUOTE (NghtShd @ Jan 17 2004, 04:19 PM) |
| Ok, I had some free time, so now I have partial 4980 support implemented, but someone on IRC is saying the live disable feature doesn't work or doesn't work on some games. If this is the case then is there much point in supporting this kernel? If you can't trust the live disable it isn't really much good. |
Team Executer said in the initial release that they had not tested all of the available LIVE! titles and were looking for others to test what had not been done. If it is only 1 or 2 titles out of the majority that are having a problem then that is sufficient for me to continue to use 4980.
Were the guys on IRC being specific and trustworthy individuals or
A. Complete N(oYo)Bs that dont know the difference between a pinheader and a pogo pin install?
B. Plants by M$ that are just trying to throw a wrench in the works?
There was a person spouting off on this forum not too long ago that 4980 was a waste of time because he had dozens of EEPROMS that he could use if he were banned. Maybe that person could put a few EEPROMS where his mouth is and test it out. Or possibly share a couple for testing purposes.
Post by: dzv on January 17, 2004, 08:09:00 PM
| QUOTE |
| If the game asks you if you wish to update your dashboard YOU MUST SELECT NO. THIS WILL BAN YOU FROM LIVE. The bios currently does not block access to the server - it is being worked on. You will only be asked for an update if you do not have the latest version of the Xbox Live 2.0 Dashboard (currently 5659.03). It is a good idea to update to the latest dash by using the original game and with your mod disabled. Thanks to forum member and 4980 tester Leftyfb for actually testing this and getting banned less than 24 hours later (on a spare box he had of course hehe). |
Unfortunately, I'd say this still leaves users quite open to getting banned. In fact, it might even make users more inclined to getting banned. I think that most users using 4980 have been given the impression that it is completely Live-Safe, and will become more complacent, therefore increasing the chances of them allowing something like a dashboard update to occur.
Until this hole is plugged, I wonder if it's even a good idea for people to use 4980.
At least when people are using 4979 or M7, they KNOW they will be banned if they make a mistake, and therefore they are (usually) very careful about getting banned.