@d0k3 you have really outdone yourself this time. I am loving the new chainloading capabilities, especially useful with this new exploit. Not that the RTC feature isn't handy so I can tell when files were modified. I also thoroughly enjoyed seeing the "encrypt" and "decrypt" options added. Now I can setup a dedicated folder for removing seed encryption from CIAs by decrypting and re-encrypting them with a script. It might be nice if there was a "log" command, so I could see which ones actually had seed encryption, though.
Thanks again for all you do for the scene.
And, thanks to you, too! Useful feedback is always appreciated.
I think a "run" command would go well with this new chainloading feature. That or a configurable menu for the chainloader. I'm working on a drag-and-drop method for NTRBootHax that only requires one trip to the PC. The basic concept is already complete. Use GM9 to chainload Safe B9S Installer instead of running it directly. Then use a script to copy "boot.firm.bak" (a backup copy I'll be including with my configurations in the next version of my AIO pack) to "boot.firm" and delete the temporary installation files. It would be convenient if I could have Safe B9S Installer launch from a menu instead of having to tell people to find it on the SD card and launch it. It will still work as is, it's just that it would look more polished that way.
Though a "run" command has other possibilities as well. Renaming external firmware files for CFWs that still require them, for example. You could have a script copy "firmware90.bin" to "firmware.bin" right before launching Cakes or Corbenik/Skeith with a 9.2 EmuNAND, and have another copy "firmware114.bin" to "firmware.bin" so you could easily switch to running it with your updated SysNAND.
A 'run' or 'boot' command will be added and I'll also add a menu for quick booting of payloads.
Now, the A9LH compatibility. Yeah, I'll be honest, it wasn't planned to ditch it that fast, but, right now, it will not work. Don't worry though, I have something in the works that will cover this (and more) and that will be released very soon.probably still works if you build the source yourself and use the output binary. I would imagine d0k3 just didn't put it in the release archive because everyone should have moved on to b9s now. I didn't check if it actually runs on a9lh though.