Info - eboots
So I've 'successfully' edited some eboots and got them working using the dev_hdd0/NEW_GAME/ directories etc.
I was just wondering why some games, even when you edit the eboot to work from dev_hdd0/NEW_GAME/ it doesn't work or run from there unless you put the files in the dev_hdd0/game/TITLEID folder?
e.g. I edited sonic eboot so it reads from "dev_hdd0/SON_ICCC/" and I placed the USRDIR in that folder, but it froze and black screened and then I moved the USRDIR to "dev_hdd0/game/BLES00475/" and it suddenly works, even though the eboot was directed to the other folder, why?
Either the game uses relative paths internally, or the hex edit is causing the game's attempts to locate files to fail, and it just reverts to relative paths because of such.
Originally Posted by titchy
What you could try with Sonic is to just take the retail eboot, unself it, make_self_npdrm it, and then package, finalize and install, then put the game data in the package folder with the EBOOT and see if it runs. If so, the game just uses relative paths internally.
Good idea. I'll try it, cheers!