A lot of people have been asking (in other forums) about getting Moonshell 2 to boot up on an Ak2i - to be used as an alternative file selector to that of AK2i and AKAIO I've managed to 'cheat' by using AK2i/AKAIO autorun function to run Moonshell straight away (my guide is here) since the 'usual' guides for booting into Moonshell2 directly doesn't work for the AK2i (usually it's somewhere along the lines of 'DLDI Moonshell & renaming it to the flashcard firmware name') In the AK2i case - doing this (renaming to 'ak2menu.nds') doesn't work because the AK2i comes up with a message of 'System file missing', so I'm guessing that somewhere in the AK2i and AKAIO 'ak2menu.nds' code there's a piece of code that AK2i 'looks' for on boot-up & if it doesn't see it - up comes 'System file missing' error So my question is this..... Is there way to 'patch' Moonshell2 to include this mystery 'system file' code so that we can just boot straight into it (moonshell), a bit like DLDI-ing but for the missing 'system file' code, & if not is there a way of creating a mini 'ak2menu.nds' loader/launcher that 'fools' the AK2i on bootup then automatically load 'Moonshel2.nds' without having to load all the other bits of AK2i/AKAIO firmware (Skins/Graphics etc) [People who still want to use Ak2i/AKAIO firmware (for those stubbon ROMS) then only need to copy the ak2menu.nds into moonshells 'resetmse' folder & rename it appropriately, then use Moonshells 'reset to firmware' to choose AK2i/AKAIO] Could one of the AKAIO developers answer this ?? - for all I know it could be just one hex value missing in Moonshell's header that exists in ak2i/AKAIO that's the problem. Anyone with a hex editor could change it - & problem solved !!