Post by: eh. on December 14, 2004, 10:15:00 PM
It wouldn't "reset on eject" and could be used as a non-gamesave backdoor, on any current box.
It's possibly compatible with XBL (via retail 185ead00, currently) but the Live console would hang.
Can anyone think of other usages/benefits? If it's potentially worthwhile, forum mod's might pursue it eh...
_______
(Related: Direct booting via the xodash font route probably wouldn't be of use eh.)
Post by: devz3ro on December 14, 2004, 10:16:00 PM
Hopefully I can get new double dash fonts made for owners who do not have K:5713 and K:5838 as its still a great solution.
-devz3ro
Post by: devz3ro on December 14, 2004, 10:17:00 PM
I asked rmenhal to remake these fonts (changing the landing zone) but realized it would be worthless, check out my last post on my live 2.0 thread if you are searching for a Uber EEE
-devz3ro
Post by: eh. on December 14, 2004, 10:33:00 PM
(It pioneered UberXBL .xbe's for some though eh. 
)
Post by: devz3ro on December 14, 2004, 10:40:00 PM
. But back to K:5713 and K:5838 and their handling of EEE. I've noticed both on local 5713 & 5838 boxes that when performing the EEE on them it does not bios error. Instead, the box shows a dashboard error about not being able to read the disc (with no disc inside) and the box locks up.
Post by: eh. on December 14, 2004, 10:40:00 PM
| QUOTE (devz3ro @ Dec 14 2004, 11:20 PM) |
| Problem with this is definitely the live console access. Updating games would hang |
I don't have Live so am a bit unsure about it; does this mean that XBL's updates for new content and/or fixes run via the /C/xodash/xonlinedash.xbe eh?
(185ead00's /C/xodash/update.xbe wouldn't hang, as it doesn't reference the xodash fonts.)
Post by: devz3ro on December 14, 2004, 10:50:00 PM
| QUOTE (eh. @ Dec 15 2004, 07:43 AM) |
| I don't have Live so am a bit unsure about it; does this mean that XBL's updates for new content and/or fixes run via the /C/xodash/xonlinedash.xbe eh? |
I am not 100% sure, but if I recall correctly it does. I remember messing around with it a while ago and having it error 21 I'll have to play when I get some time. Even if it does, the user could just update the game then install if they don't care about live dashboard access. It wouldn't be that bad.
I asked rmenhal whenever he had free time to change the landing zone in these fonts and remake the double dash fonts about 1/2 a week to a week ago. Hopefully we will have them to play with sometime soon. Whether it kills the console or not, it would be nice just to have the collection.
-devz3ro
Post by: devz3ro on December 14, 2004, 10:58:00 PM
). Hopefully this will lead you to the road to becoming a moderator if you are interested. I will be speaking with Xant about your progress and what you have brought to the scene. Hopefully I can get you a position the same way I was able to get Angerwound and Pedro theirs. Let me know.Sorry for bringing it up now, had to say it before I forgot.
-devz3ro
Post by: eh. on December 14, 2004, 11:27:00 PM
Post by: DaddyJ on December 15, 2004, 04:34:00 AM
Post by: eh. on December 15, 2004, 06:12:00 PM
| QUOTE (devz3ro @ Dec 14 2004, 11:19 PM) |
| Hopefully I can get new double dash fonts made for owners who do not have K:5713 and K:5838 as its still a great solution. |
Regarding "double dash"ing, I'd expect the kernel constraint could be overcome by using UD-eh!'s xonlinedash.xbe (via xodash fonts) instead of a pre-live dash (via C fonts)...
However, the DD method is always dash constrained (as 185ead00 doesn't allow it) eh.
Post by: DaddyJ on December 15, 2004, 06:15:00 PM
Post by: eh. on December 15, 2004, 06:15:00 PM
| QUOTE (devz3ro @ Dec 14 2004, 11:43 PM) |
| I've noticed both on local 5713 & 5838 boxes that when performing the EEE on them it does not bios error. Instead, the box shows a dashboard error about not being able to read the disc (with no disc inside) and the box locks up. |
Regarding "easter egg"ing, I'd expect UD-eh!'s xonlinedash.xbe wouldn't be kernel constrained. I'd be very surprised if it's dash constrained too, so I'm wondering whether those boxes still had the M$ settings_adoc.xip in place (which isn't suitably dated for EEing on those kernels) eh?
Post by: The_Truth on December 15, 2004, 07:06:00 PM
Post by: devz3ro on December 15, 2004, 08:01:00 PM
| QUOTE (eh. @ Dec 16 2004, 03:15 AM) |
| Regarding "double dash"ing, I'd expect the kernel constraint could be overcome by using UD-eh!'s xonlinedash.xbe (via xodash fonts) instead of a pre-live dash (via C fonts)... However, the DD method is always dash constrained (as 185ead00 doesn't allow it) eh. |
No, you misunderstood what I meant.
I meant getting the double dash fonts remade to be used as EEE. They were the first used to make the EEE work to our advantage as you probably already know. The DD fonts and xbe as EEE still work on 5960 just not on the two kernels. rmenhals xonlinedash fonts method as EEE and DD as EEE both have their flaws, I just pick DD as EEE for full live access since I can tsop flash up and down from 5101 to 5530 to 5713 (5530 being the winner).
btw: wtf is UD-eh!?
Double dash in it's original form has been deceased for quite some time, I believe I was the one who posted about it when 5960 was first introduced
. Don't really remember though it was a while ago.-devz3ro
P.S. I haven't forgot about you, just haven't had time to send any mail around yet, I'll get to it soon I promise.
Post by: devz3ro on December 15, 2004, 08:24:00 PM
| QUOTE (eh. @ Dec 16 2004, 03:18 AM) |
| Regarding "easter egg"ing, I'd expect UD-eh!'s xonlinedash.xbe wouldn't be kernel constrained. I'd be very surprised if it's dash constrained too, so I'm wondering whether those boxes still had the M$ settings_adoc.xip in place (which isn't suitably dated for EEing on those kernels) eh? |
Regarding rmenhal's xonlinedash font find as EEE,
No they don't bail out on K:5713 & K:5838. Yes dashboard 5960 still holds the xip which executes the same exact way. I tested this out (on both kernels) about a week before you posted
. I get a black screen when executing it on the console, so the fonts are fine, the landing zone just needs to be changed. I mailed rmenhal and asked him to do so, but you can understand he is a very busy man. Pedro and Angerwound are also very aware. I didn't start a thread about it because we kind of wanted to keep this internal and test (as we do most things) then decide whether to announce to the world.This is the main reason why I have invited you, you are letting out our secrets!!
I Kid!, I Kid!.
Anyways, look forward to getting a email soon, I'm off to work for now, then bed directly after
-devz3ro
Post by: eh. on December 16, 2004, 01:58:00 AM
but it sounds like this will be a surprise for you... these "secrets" and more were outlined Nov.8 in this linked post (and that page explains "wtf is UD-eh!?"). 
Post by: devz3ro on December 16, 2004, 05:16:00 AM
| QUOTE (eh. @ Dec 16 2004, 11:01 AM) |
| Understood; no worries but it sounds like this will be a surprise for you... these "secrets" and more were outlined Nov.8 in this linked post (and that page explains "wtf is UD-eh!?"). |
I did not mean that in a negative way eh. I just thought it was something super secret that I did not know about
-devz3ro
P.S. rmenhal; thanks for the info, I'll play when I get home.
Post by: devz3ro on December 16, 2004, 06:37:00 AM
| QUOTE (rmenhal @ Dec 16 2004, 12:38 PM) |
| The existing kernel-specific xonlinedash fonts and fonts in c:\xodash should work with EEE (with no Live console access), you just need to put the media directory and files under c:\xboxdashdata.whatever\. If it doesn't, then it's just the memory layout issue; try putting in some s.xtf files (though they probably don't have as much effect as they have for UDE/UXE) and maybe try changing file name lengths of xtf files. |
Just tried atleast 20 different setups, all leave me at a black screen
. I'll keep trying, if anyone else has any luck please let me know. I am really looking forward to this working or new double dash fonts for dd as eee.-devz3ro
Post by: devz3ro on December 16, 2004, 07:25:00 AM
| QUOTE (rmenhal @ Dec 16 2004, 04:25 PM) |
| Try also having just the ernie.xtf, Xbox.xtf (in the correct order), but hexedit ernie.xtf at offset 0x30: change 01 00 00 00 to 02 00 00 00 or 03 00 00 00 and so on. |
You are a genius man, works beautifully now from kernel 5530 after that edit.
-devz3ro
P.S. changed to 02 00 00 00 btw
And I think I was using incorrect s.xtf files to start off.
Post by: PedrosPad on December 16, 2004, 07:38:00 AM
| QUOTE (rmenhal @ Dec 16 2004, 12:38 PM) |
| The existing kernel-specific xonlinedash fonts and fonts in c:\xodash should work with EEE (with no Live console access), you just need to put the media directory and files under c:\xboxdashdata.whatever\. |
For information only - The original fonts worked fine for me - no hex edit needed, no s.xtf files - on my PAL K:4817/D:5960.
PS. This was Uber-xonlinedash.xbe as EEE, chaining NKPatcher 8.1, complete with shadowed C drive - all worked fine.
Post by: eh. on December 17, 2004, 12:40:00 AM
| QUOTE (devz3ro @ Dec 16 2004, 06:19 AM) |
| I did not mean that in a negative way eh. I just thought it was something super secret that I did not know about |
Phew... I thought maybe I'd published too much/too soon back then and possibly put something at risk (which I'd tried to avoid doing) eh.
Re. the fonts: it's incredible that rmenhal had created them suitably for this more than 6 months ago eh!
-
Title: Uber Easter Egg Exploit
Post by: eh. on December 18, 2004, 04:04:00 PM
-
-
Title: Uber Easter Egg Exploit
Post by: eh. on January 26, 2005, 10:53:00 AM
-
(It's also so I can correct a couple of things: as devz3ro indicated, accessing the live console still results in an error code ... 21 I think; definitely not a "hang" like I'd said. Also, I've since learnt that the fonts it uses aren't as old as I'd thought ... but rmenhal had produced them quite a while ago eh.)
Re. the fonts: it's incredible that rmenhal had created them suitably for this more than 6 months ago eh!
Post by: eh. on December 18, 2004, 04:04:00 PM
Post by: eh. on January 26, 2005, 10:53:00 AM
(It's also so I can correct a couple of things: as devz3ro indicated, accessing the live console still results in an error code ... 21 I think; definitely not a "hang" like I'd said. Also, I've since learnt that the fonts it uses aren't as old as I'd thought ... but rmenhal had produced them quite a while ago eh.)