lumaupdate
lumaupdate copied to clipboard
Automatic support for /arm9loaderhax_si.bin
I currently use Luma as /arm9loaderhax_si.bin (as to have screeninit with Aurora Wright's A9LH). This updater should check for the existence of /arm9loaderhax_si.bin, and if so, set it as the payload. Since it is also a standard payload path, I guess.
I really don't see the need for this tbh. There's a configuration file and a stupid nag if people don't use it, why not use it and solve two problems?
Because, arm9loaderhax_si.bin is also a standard path. (as of a few days ago it is anyway), and imo, it should be supported out of the box.
Just because it's standard in some cases (for example, not in any of my 3DSs) doesn't mean it's worthy of a default. Adding support for _si means rewriting considerable part of my configuration default value management, and I'm not doing that unless a very good reason comes up.
As I said, not having a configuration file is an exception and I'm surprised it's working for so many people, the "standard" is to have it.
So for now I'm not budging from my position.. unless someone else wants to do the work, then idc as long as it's decently written.
I haven't read the source code for this yet, but, at least with StarUpdater, it was fairly easy to add it (unless I forgot something critical, really). I suppose this can be addressed by checking if arm9loaderhax.bin exists, and, if not, and if arm9loaderhax_si.bin exists, write it to the config file (if there isn't a config file). This is how I did it for Corbenik Updater (which runs on LPP, so I'd have to... Re-read some stuff, I haven't used C in a long while). Another way would be to do (in pseudo code, I guess) If (arm9loaderhaxexists! & sipayloadexists) defaultpayload = "/arm9loaderhax_si.bin"; Else defaulypayload = "/arm9loaderhax.bin"
I'm not sure if I'm missing something, but I'll take a look at the code anyway. On 3 Jul 2016 12:36, [email protected] wrote:
Just because it's standard in some cases (for example, not in any of my 3DSs) doesn't mean it's worthy of a default. Adding support for _si means rewriting my considerable part of my configuration default value management, and I'm not doing that unless a very good reason comes up.
As I said, not having a configuration file is an exception and I'm surprised it's working for so many people, the "standard" is to have it.
Unless someone else wants to do the work, then idc as long as it's decently written.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Hamcha/lumaupdate/issues/39#issuecomment-230148866, or mute the thread https://github.com/notifications/unsubscribe/AKvNW6bxEDJPL_Djv4xVLwwMfVTlN-uHks5qR56kgaJpZM4JDve0 .