True, but previously it wasn't possible to load them without chainloading (have a payload that loads another arm9 payload that then loads the kernel) due to payload size limitations. Not to mention it is now possible to have a full custom firmware, including custom FIRMs rather than just a custom ctrnand.
True, but previously it wasn't possible to load them without chainloading (have a payload that loads another arm9 payload that then loads the kernel) due to payload size limitations. Not to mention it is now possible to have a full custom firmware, including custom FIRMs rather than just a custom ctrnand.
- Joined
- Oct 6, 2015
- Messages
- 1,863
- Trophies
- 1
- Location
- Canada
- Website
- jackomix.neocities.org
- XP
- 3,782
- Country
Literally the only difference is the location. You could have had a "full custom firmware" before, though you'd have to store the files in the CTRNAND partition instead of the FIRM partition, and then chainload those files from a stub. This is literally the same as MBR boot on IBM-compatible PCs; the BIOS loads the MBR, which has a small chainloader that loads the actual operating system from the partition.
Again, if this is the new "standard" for custom firmware, that means you're using a "fake" operating system if you boot from anything other than the C: drive.
EDIT: For what it's worth, if you do implement a full "custom OS" on 3DS, it won't run 3DS games unless you also reimplement all of the 3DS system services. You'd need to dual-boot between the "custom OS" and the 3DS OS.
Last edited by GerbilSoft,
, Reason: +reimplement 3DS
Similar threads
- No one is chatting at the moment.
-
-
-
@ HiradeGirl:
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
