Post by: unleashx on April 14, 2004, 10:33:00 AM
Post by: heinrich on April 14, 2004, 12:31:00 PM
| QUOTE (unleashx @ Apr 14 2004, 03:33 PM) |
| Of course, you are aware that the last post before yours was made almost 10 months ago, right? |
22 months
More importantly, almost a full month before the first version of evox was released. Things have come a long way since then.
Post by: aweelz on April 14, 2004, 09:00:00 PM
Aweelz
Post by: Hammy on June 10, 2002, 03:31:00 AM
I would like to know why the xbox retail can not boot assigned code and then the assigned code executes some unassigned code to take over???
Post by: Hammy on June 10, 2002, 03:32:00 AM
I would like to know why the xbox retail can not boot assigned code and then the assigned code executes some unassigned code to take over???
Post by: monkeycrew on June 10, 2002, 05:16:00 AM
Sounds like a good idea. About the code;
Every official release by MS is digitally signed so the XBOX will accept the XBE file as an official MS file, and therefore run it.
The digital signiture is indiviual to each official release, and is probably generated accorrding to:
. no of files
. file structure
. folder structure
. file sizes
. file names
. etc.
If any data changes on the release,
e.g. a file is swapped; then the chances are that the signiture will be invalid, therefore rendering the software unusable.
If a chip was used however, the system will boot this invalid signature anyway, so the menu system could be used on mod. machine.