@mooglazer and
@MelonGx , you two first brought up this issue, so I hope you'll help me decide what to do with it. I already contacted
@n1ghty via PM and I hope he will be doing an update or release the source code.
If I have to fix EmuNAND9 for compatibility, I have these options...
- Use the biggest possible size for EmuNAND (meaning: 1GB for O3DS, 2GB for N3DS), hoping that this will fix it. Big downside: this won't help anyone who already set up his EmuNAND with EmuNAND9.
- Do the above, but let the user decide which size to use. Downside: This will be confusing for noobs. Also, won't help anyone who already set it up.
- (in addition to the above): Automatically trim / pad NAND backups when injecting. Downside: Less safety, cause the size is an additional factor to check the validity of a NAND backup.
Any ideas? As I said, the problem right now lies in how EmuNAND tool dumps and injects NAND backups (uses the biggest possible size).