So has anyone actually hex edit'd the file path and tried to run it on their 360?
\Device\CdRom0\default.xex
to something like
\Device\CdRom0\crashn.here
[being sure to make the replacement of default.xex 11 characters]
just to see if the xex still runs? If it says the file is not valid, then we know it checks the hash of the file before running it, which means bad news for us as we will have to find another method of running unsigned xex content. I personally don't have the $400 to drop on a game system, but if anyone is willing to give it a spin, the worst that will happen is it will give you an error about corrupt data.
hm, if that would work it may be a way to start up other files. at least if that line means that it needs to start a file...