v1.61:* Fixed a NAND offset miscalculation while parsing EmuNANDs.* Fixed a regression bug where the NCSD header was always written/read to/from offset "nandsize + 512" instead of the appropiate sector (EmuNAND only).* Fixed a bug where the calculated NAND size would be zero if a new EmuNAND with a size greater than the current layout was being injected.* Improved FAT32 format procedure reliability (based on code from Rufus).* Fixed a crash that occurred when attempting to format a new FAT32 partition (debug build only).* The program is now licensed under GPLv3.v1.6:* Added support for 1.82 GiB N3DS NAND dumps.* Added proper detection of 2DS NAND dumps.* The "Format EmuNAND" procedure now defaults to the 'minimum' setup size, using a RedNAND.* The program now forces the "Remove NAND" button to be enabled if a previous attempt to remove the first EmuNAND failed.* The MBR is now manually initialized with zeros before creating it using WinAPI instructions (leftover data is kept in sector #0 otherwise).
Je me le demande aussi, a quoi bon avoir plusieurs emunand sur une même SDA quoi peu servir concretement une 2e, voir 3e ou 4e emunand ?
Sur ma 3ds Luma, je ne me sert plus de mon emunand gateway. J'ai l'A9LH d'installer. Est-ce mieux de s'en servir ???