- Joined
- Sep 13, 2009
- Messages
- 31,487
- Solutions
- 2
- Reaction score
- 32,216
- Trophies
- 3
- Location
- Gaming Grotto
- XP
- 31,049
- Country
See, this is why "external" testing is important. This problem hasn't crossed my mind a single time, all I focused on was the verification process.But I don't understand the point
You are checking the "Launcher.dat" on the micro SD in the NDS Flashcart?
No offense man, but that doesn't prevent you from nothing .... and it's also not portable either.
How are you supposed to get the Launcher.dat on the SD card after you checked with your app? (without any computer near by).
And since your app can't access the SD card (which is a limit from the console, not your app), there is still a chance that your SD card is messed up ... and it has been proven that this can also be a cause of bricking your 3DS.
This is no critic to your app, it's good that you are trying to help .... but it's not protecting you from bricking your 3DS.
I'm currently adding a routine which will allow you to switch SD cards on-the-fly - the idea is that you start the app from your DS-Mode flashcart, remove the miniSD (a stylus would be useful), press a button and then it verifies the Launcher.dat.
Users who are using full-sized SD's will be out of luck, but those with a microSD and an adapter will be able to utilize the app no problem.
EDIT: Issue fixed, app now supports SD switching on-the-fly, or at least I should think so. You can use it on anything from a standard DS to a 3DS - it's all same difference.
