Print

[mkjones]

QUOTE (zorxd @ May 5 2004, 11:44 AM)

or use the audio exploit to turn on the double dash exploit again after playing on live

But then you would lose all audio abilities such as in game music and soundtracks while you were playing on live games..

Running 2 exploits, although a great idea to get around the clock loop problem shouldnt be any part of this exploit. I am sure people want just one exploit with no switching and still the ability to use audio.

Live! as ever is an issue with this exploit, just like it is with Modchips..

I really hope the people in the know get this thing working
I could use it now as I have all my games on my xbox HD anyway!

Only problem I can forsee is it seems to be "different" for every xbox so a package/installer would be hard to code.

For now, il stick with my package and the MA fonts, the font/audio switch is the 2nd safest option after this one

Does anyone think there is a way to get this working with later Dash versions? Higher than 4920 I mean?

My thinking is it should work, becuase the latest dashboards are simply patched for the fonts and audio hacks, not this.

[krayzie]

QUOTE

or use the audio exploit to turn on the double dash exploit again after playing on live

Yeah that was my understanding that it should work on all dashes untill now so if you have a live 3.0 dashboard it still functions. Only an audio hack to get back to the modded state wouldn't be an option then.
I hope that in the near future when this is more developed it comes with a complete package including old msdash and stuff and working for every xbox the same.

[xb0xb0y]

Can someone give me a hand and possibly point me to what I'm doing wrong?  I have re-installed a backup of my old dash 4034 that came with my xbox, kernal is the same 4034.  I had upgraded my dash to 4920 to use a modified Morden Audio exploit (modified as in integrating it with the Splinter Cell exploit and Fat Finger Fix).

So installing the old dash and renaming the 4034 xboxdash to xonlinedash.xbe and placing it in the xodash directory works fine.  I can launch the old dash from the new dash.

Now when I rename the two .xtf font files to .bak and upload the bert and ernie fonts (the new big bert font posted here), when I try to launch the old dash, I get a service error 21.  It says in the instructions to test at this point.  I'm a suppose to tune the bert font first before this will work?  At first I thought it was cuz I didn't have a habibi signed e:\default.xbe.  So I signed and renamed evoxdash.xbe and placed it in e:, but I still get the service error 21.

I've only been using the audio exploit and never tried the font exploit, so please bare with me.  Any help would be appreciated, thanx!

[ldots]

.

I redid the test of rmenhal - running a xbedumped 4034 dash from the live-tab. No reset since xbedump sets the media flags in the 4034 header. Same when re-running an unmodified 4920 dash.

QUOTE (rmenhal @ May 5 2004, 07:10 AM)

1) at step 13 of readme.txt when the led blinks red, reset-on-eject is not enabled.

This is indeed interesting. Trying to understand this. The bytes you have os replace in the hexed xolinedash.xbe (68 00 10 01 00 C3) for doing the probing. Do they make a jump to the probe.bin code we have imbedded in xonlinedash ? At the point where the led is blinking red the 'reset-on-eject' flag is not set, so seems likely the xbe has to load succesfully before the flag is set. This is good! However

QUOTE (rmenhal @ May 5 2004, 07:10 AM)

2) I put a test into the memory allocation function (look at the comment in bert.asm to figure out the memory location) to test when the overwrite of the SEH pointer happens, and when it happens go into infinite loop. The reset-on-eject is now enabled.

I don't see why this is so good? At the time bert overwrites the SEH pointer the reset-on-eject is enabled? But at this point we dont yet have any real control yet do we? We still havent made the jump to the exploit code of ernie - or? So if the reset-on-eject flag is allready set at this point how could we prevent this? Please educate me . But I mean, dont you think we have to prevent this flag from being set - once it is set it cannot be reverted?

[YoshiKool]

Besides the reset on eject thing, are there any other problems with the doubledash exploit? TIA...

[ldots]

QUOTE (rmenhal @ May 5 2004, 05:15 PM)

It would have been good, because at 1) the reset is disabled, at 2) it is enabled, and by what I said before "This is interesting" the reset was disabled. So Dashboard would have had to (for some odd reason) to enable and then disable it.

OK - see your point. Don't know how far in execution of xonlinedash we are when we reach the blinking led at 1). Are you sure the reset-on-eject has been enabled and then disabled? Before lauching xonlinedash it was disabled so maybe it just stayed that way??? But I take it your conclusion was based on, what you believed was an infinite loop in bert, was before the blinking led at 1). I'm sure you are right. I just thought maybe 1) was before 2). Does that make any sense  

[Angerwound]

Based on some testing I've been doing, I think maybe this was caused by it being disabled before as well. I could be wrong but it does seem like the reasonable explanation for this odd occurence.

[debeautar]

Wait... it might be possible for me to actually have an applicable, not-so-far-fetched, knowledgable offering!

Check this action out.

Okay... so, once all of the kinks are worked out of this process, and the double-dash method indeed works with all features asked for (no reset-on-eject, easy-working-yay)... would it then be possible to pre-train different bert files for each separate version of pre-live dash? Or, does EVERY single dash have its own unique quirks, like an eeprom to an xbox hard drive?

this way, once we're in the packaging phase (cart before horse, I know)... most everyone would be covered.

I will be forced to wait for progress, as I apparently suck rocks with a hex editor... tried following instructions, and couldn't find the right offsets, NOR could I find particular values for editing.

I leave the fate of exploitation in all of your capable hands. I am but a yutz.

Yeah.

[xb0xb0y]

QUOTE (xb0xb0y @ May 5 2004, 08:56 AM)

Can someone give me a hand and possibly point me to what I'm doing wrong?  I have re-installed a backup of my old dash 4034 that came with my xbox, kernal is the same 4034.  I had upgraded my dash to 4920 to use a modified Morden Audio exploit (modified as in integrating it with the Splinter Cell exploit and Fat Finger Fix). So installing the old dash and renaming the 4034 xboxdash to xonlinedash.xbe and placing it in the xodash directory works fine.  I can launch the old dash from the new dash. Now when I rename the two .xtf font files to .bak and upload the bert and ernie fonts (the new big bert font posted here), when I try to launch the old dash, I get a service error 21.  It says in the instructions to test at this point.  I'm a suppose to tune the bert font first before this will work?  At first I thought it was cuz I didn't have a habibi signed e:\default.xbe.  So I signed and renamed evoxdash.xbe and placed it in e:, but I still get the service error 21. I've only been using the audio exploit and never tried the font exploit, so please bare with me.  Any help would be appreciated, thanx!

You guys can keep talking amongst yourselves and ignore my previous question, which has been up to this point anyway   .  I've figured out how the font exploit works and got the double dash working.

Good work rmenhal, great job!

BTW, I didn't do any of the tuning of BERT at all.  Am I suppose to?  And how many people actually needed to?  Can someone explain what the tuning is for?  Thanks.

Cheers!  

[afon]

To rhemnal:
Hmm...how did you happen to stumble upon the way to edit bert? Hex editing all those offsets, doing whatever you did to st.db.. it just seems like you would need to know what your doing and whats happening.

To anyone who can help:
Unfortunately, i cant get this hack working. Ive tried to hex edit all those offsets, but it just seems like alot of random work. Plus, Some of the offsets just arent there. Can someone maybe PM me with 3944's where..about..sss.

[Angerwound]

First of all, Afon, you shouldn't be hexediting at all if you haven't gotten it working at all yet. The hex editing only tunes your file to your setup. I in fact have never tuned my files and have never had a reboot....  Can you get the old dash to even boot?

[Angerwound]

QUOTE

To rhemnal: Hmm...how did you happen to stumble upon the way to edit bert? Hex editing all those offsets, doing whatever you did to st.db.. it just seems like you would need to know what your doing and whats happening.

Rmenhal is god, this is how.

[digisatman]

I dont understand any of this double-dash thinky...well...not fully anyway...

PLease can some tell me in an n00b way and ill try it as soon as i know what the function of all this is!


Regards

[mkjones]

Hmm, is anyone else starting to get sceptical about this?

If the reset on eject can never be fixed (it could become the new clock loop) for most users this will be unusable, especially for users wishing to watch a few movies from disk in Media Player.

As I used to before I got my large HD.

Sure, placing the disk in while the exploit loads would work, if you do it before you get the M$ Dash disk error that is...

Also, it would make DVD2XBOX unusable. So anyone upgrading a HD using softmods (as I have) wouldnt be able to back up their games

Also, I reolized if I made some kind of memory card package I couldnt get it hosted anywhere becase it would contain origional M$ dash files and xbins dont allow that kind of thing, so for noobs and people without FTP access this is a no go

Then I wonderd if removeing the Live! dash was a good idea.

Sure for people who will never use live this is a great idea, but we can use live with the audio hack, I have never tried it but have read a few posts of people who have, can anyone elaborate?

I mean, I would feel pretty safe running live with the audio hack on, but not this? Like the fonts, its too big a change of the xbox operating system, dont you think?

IMO The audio hack is a great stepping stone into softmodding....
I would always reccomend the Audio hack over this, the only loss is in game music and Morden got around that in some way. I mean, its safe, leaves your C drive clean and has little chance of causing Error 21.

For people like me and some other used to softmodding this could be great, but IMO it still doesnt beat the Audio hack for safety and simplicity

I mean, I stuck with Mordens for months before I started messing around with the MA fonts and making font/audio switch code to combat the clock loop etc... And finally making my own packages...

I look back and if I had to 'start' with this hack, It would blow my mind? Its WAY more complex than just FTPing some fonts or an st.db file over.. You have to know what you are doing..

Anyway..
I plan on virginizing my xbox at the weekend and trying this, see what its like. I guess its just like pressing "PHEONIX" in the MA fonts, as I do anyway, but I always like to tinker

My point?
Well, if you are a noob! stick with the audio hack..

That is until this becomes more useable and works properly..

Or, if you are happy with your set up, dont jump ship just yet..

[Code-X]

I'm sure Live will still work even with this, because isn't it the game that connects to live, and the live dash is only for updating (I could be wrong on this).
This is quite simple to set up, but takes a bit of time.

Any one want me to make a simple patcher app, that would add the probe code and change the 7 bytes.