dib said:
Okay, so in other words you're using some odd sorting scheme over multiple directories. I just tested exactly as you illustrated above, and it's still fine. I soft reset out of the game back into the loader exactly in the same directory as the game.
So the real question is why are you getting a bug with one and not the other, and if that's a problem you need fixed then I suggest troubleshooting it before bringing it here. Are you using some sort of long filename for one and not the other? Multiple words? Unusual characters? Specific game? For all I know, you're trying to name them in Japanese and using small paragraphs for filenames. You should understand that Smiths has already stated that they're not interested in tracking down every bizarre bug that surfaces when people are using habits outside of normal operation, and will not idiot-proof the loader. And it sounds like you may be using some bizarre convention that won't surface for most people.
I'm not using some "odd sorting scheme", I just keep everything organized, instead of just dumping everything on the root of the card all unorganized. For example, Homebrew has it's own folder with sub-folders for different genres and the other files have their own folder with sub-folders for different genres. As for the "file names", those are unchanged, I do not rename the files as there is no need to, because the OS will show you the internal name (great feature guys!). Is "Organization" a "habit outside of normal operation"? And what is "Normal"? Ask five different people to give you the definition of "Normal" and you'll get five different answers. "Normal", is unique and individual, not global. So I could say, "Normal" for me, is "Organization" or "Order", and for you, "Normal" could be "Disorganization" or "Disorder", I don't know. ...Anyway, the problem still arises no matter where the file (0168.nds (trimmed or untrimmed)) is located, for example, it could be in a folder (or sub-folders) or on the root of the NAND of the card. But when "Soft Reset" is used to exit the rom, everything still gets messed up with the OS' UI. Now, if I go to the roms own settings and set "no save" for it, load the file (0168.nds) and then exit the file with "Soft Reset", the OS' UI is not messed up and everything is fine. Repeating the mentioned steps with any file that has caused a problem, will not mess up the OS' UI. So maybe there is a problem with how the OS accesses the save info from the memory when "Soft Reset" is used?