I have read messages about people changing settings via the MS Dashboard (after having installed the UXE exploit) that messed up their Xbox (wouldn't boot properly). I have a couple questions for anyone who might be familiar with Memory Layout issues:

1) What changes to the MS Dash would/could cause the Xbox to not boot? I'm just curious so that I can try and prevent people from complaining that a box I modded isn't working, by letting them know in advance what they can and cannot do.

2) Depending on what the answer to #1 is, what is the worst thing that changing a MS Dash setting could do? I assume that there will always be a way to correct the issue, but is it something easy enough that I could set up boxes in a way that the tools to correct the issue would be available to the user to fix it themselves (obviously this only pertains if the memory layout doesn't break a box to the point that a homebrew app can be run).

3) This one is a little off the topic, but I have wondered about for a while. I see that some people can't even boot retail games (007) if they delete a certain file from C or E ("accidently"), while others seemingly have deleted several files they shouldn't have, but are still able to boot a retail game to FTP back in and correct the issue. What exactly is the reason for this? Is there certain files that are absolutely required on the C and/or E drive in order to boot a retail game? I know that might sound like a stupid question, but from what I have read in the past, some people have apparently gone goofy with deleting, but were able to fix it without a hotswap or modchip, while others whacked "only" a bios file from their exploit and said they got an error and couldn't boot a retail game.

Again, thanks for helping out an inquisitive rookie who's trying to figure this all out!

From what I've Read, Changing the language in the ms dash, can change the way the xbox boots, and cause an error.

Pretty sure that the parental controls can throw a spanner in the works as well.

If it goes wrong then you won't be able to run non-MS signed code, so a gamesave would be the easiest way back in.

Or your handy XboxHDM Restore CD

Would this affect UDE and/or UDE2 as well?

Not sure about those fonts, but concerning UXE

rmenhal recommended you using all 7 of the s fonts to eliminate this issue.
Rename s, s1,s2,etc.


I will try and find where I read this.

EDIT: Found IT