From 76ff7713c2591c551b86e811f8fafdaf9af1f98b Mon Sep 17 00:00:00 2001 From: Aurora Date: Sat, 16 Apr 2016 00:35:58 +0200 Subject: [PATCH] Updated Options and usage (markdown) --- Options-and-usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Options-and-usage.md b/Options-and-usage.md index bf0e1c9..f38d4e6 100644 --- a/Options-and-usage.md +++ b/Options-and-usage.md @@ -11,7 +11,7 @@ Once it's loaded, you'll be presented with a configuration menu (remember, after - **Force A9LH detection**: This option shouldn't really be needed by most users. If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx) after booting a 9.0 Emu/SysNAND on Arm9LoaderHax, you can force the same behavior you would get by booting with the arm9loaderhax.bin with this setting. Otherwise, this has no effect. -- **Autoboot SysNAND**: Determines if you want to boot SysNAND or the default EmuNAND by default (which means, when holding no buttons on AuReiNand boot). +- **Autoboot SysNAND**: Determines if you want to boot SysNAND or the default EmuNAND by default (which means, when holding no buttons on AuReiNand boot). If the option is **on**, **holding L** boots **the default EmuNAND**. Viceversa, it boots **SysNAND**. - **Use SysNAND FIRM as default (A9LH-only)**: This option does two things. First, it tells AuReiNand that the FIRM inside SysNAND is the main one and that it's capable to boot EmuNAND with R (you can only boot a NAND with a FIRM which is the same, or newer than the minimum one, so you couldn't boot a 10.x NAND with the 9.0 FIRM for example). Other than that, it makes the SysNAND FIRM the one which can be overridden by the firmware.bin in the aurei folder. If the option is disabled, the EmuNAND FIRM will be assumed to be newer or equal than the SysNAND one, so if you boot with R, SysNAND will be booted with the FIRM of SysNAND if you hold R. Other than that, firmware.bin will only be used as a replacement for the EmuNAND FIRM.