Homebrew [RELEASE] CtrBootManager9

  • Thread starter Thread starter cpasjuste
  • Start date Start date
  • Views Views 108,189
  • Replies Replies 502
  • Likes Likes 68
hmm thats funny
Well, the directory of the file is in the path, but there is no way that removing that would be correct. It would break compatibility with compiling other stuff. Cakes would be broken (off the top of my head) since armips.exe which is needed for compiling it is also in that directory

3VqeTvM.png


I imagine I'm just simply doing it wrong. I have to pick different compilers or something (which I don't know what they would be)
 
So yeah I can't figure out what I'm doing wrong. Must be something with Cmake not recognizing an asm compiler with virtual studio. Has anyone successfully compiled this in Windows?
 
Maybe you can direct us to the right compilers? I'm guessing windows or Linux might not be that relevant?
Any info would help :)
Well no it's not easy like this. I don't use windows for development and don't know anything about it. It would require me some hours of work to get all running on windows.

By the way, i uploaded a new version which should solve some inputs problems and so should fix autoboot/override key
 
@cpasjuste
Not sure at all but maybe if you add delay on entries booting may fix rxtools, It's what BootCtr9 does...
It should not be the delay, which fixes rxTools(since the should be no difference, the delay is only for showing the splashscreen to the user, and the time the user has for pressing the button). But Bootctr9 gets written to another memory address, to make it easier to load payloads to the brahma payload address, while bootctr get loaded to the brahma address, from what I know(haven't checked how the payload loading is working exactly in ctrbootmanager).
The different address for the bootctr9 payload is also the reason why there is a bootloader loader needed, for normal arm9loaderhax users.
 
Last edited by RednaxelaNnamtra,
  • Like
Reactions: chronoss
It should not be the delay, which fixes rxTools(since the should be no difference, the delay is only for showing the splashscreen to the user, and the time the user has for pressing the button). But Bootctr9 gets written to another memory address, to make it easier to load payloads to the brahma payload address, while bootctr get loaded to the brahma address, from what I know(haven't checked how the payload loading is working exactly in ctrbootmanager).
The different address for the bootctr9 payload is also the reason why there is a bootloader loader needed, for normal arm9loaderhax users.
You know how to modified the delay for splashscreen in ctrbootmanager ?
 

Site & Scene News

Popular threads in this forum