rest in pieces. but, we can thank @Billy Acuña for making this so we could draw out information from you the logic chess wayIt's too bad this will probably be obsolete for RocketLauncher/HiyaCFW users when that becomes a thing.
rest in pieces. but, we can thank @Billy Acuña for making this so we could draw out information from you the logic chess wayIt's too bad this will probably be obsolete for RocketLauncher/HiyaCFW users when that becomes a thing.
This is what I'm craving for very impatiently.
no wonder you smile so muchYeah I'm still waiting for a nand file manager to hit the scene. Relying on fwtool to install RocketLauncher will result in more newbies bricking their DSi's. Already starting to see that from people trying to sudokuhax via the leaked ugopwn exploit.
But when that happens, you get to have the convienience of something like this:
View attachment 95848
You shouldn't make posts for likes. Try to learn something and to help other users.Welp, is sad that Apache's posts have more likes than the OP of this release, I will still working on this for my personal porpuses and probably make public updates if I consider enough support on this project.
Well, some cant use this...Is not about "likes", just feld a little pissed of, this is my very first contribution to the DSi scene. This is a very simple boot manager, but I find it useful (ane hope someone else too) since I want to decide what yo boot everytime I run hax and will be useful when RocketLauncher gets released since I own an ak2i for ntrboothax and the autoboot feature on RocketLauncher. I still have many ideas I want to apply to this, not leaving for now
I know that there are some folks waiting for a stable ugopwn to downgrade and install hax, as I said, I will still working on this as my job permits me, just need some free timeWell, some cant use this...
Is not about "likes", just feld a little pissed off, this is my very first contribution to the DSi scene. This is a very simple boot manager, but I find it useful (and hope someone else too) since I want to decide what to boot everytime I run hax and will be useful when RocketLauncher gets released since I own an ak2i for ntrboothax and the autoboot feature on RocketLauncher. I still have many ideas I want to apply to this, not leaving for now
The most prob. is not that stability™, the problem is that only US devices are supported in that leak.I know that there are some folks waiting for a stable ugopwn to downgrade and install hax, as I said, I will still working on this as my job permits me, just need some free time
true, lolI agree that likes don't mean anything. I am in the top ten of most likes despite me contributing nothing to this site other than shitposts.
Do you mean a random NDS file?Suggestion, if a payload is not found it should run default.nds.
I don't understand what you mean by random nds file. Also I realize I was typing fast earlier. I only have default.nds and start.nds, if I hold A then it tries to boot A.nds which doesn't exist and hangs. In this case it should run default.nds.Do you mean a random NDS file?
Let me see what I can doI don't understand what you mean by random nds file. Also I realize I was typing fast earlier. I only have default.nds and start.nds, if I hold A then it tries to boot A.nds which doesn't exist and hangs. In this case it should run default.nds.
I made a patch for you to try, check your pull requests. I wasn't able to test it because make is having an issue with some object file, and I'm not sure all your source files are included in the repository. (nds_loader_arm9.h has an include statement in bootstrap.c but isn't anywhere in the repo, and nds_loader_arm9.c is referenced in the Makefile but also isn't anywhere in the repo). Do you think it's an issue with my environment or is it an issue with the repo?Let me see what I can do
Hello @saphirenI made a patch for you to try, check your pull requests. I wasn't able to test it because make is having an issue with some object file, and I'm not sure all your source files are included in the repository. (nds_loader_arm9.h has an include statement in bootstrap.c but isn't anywhere in the repo, and nds_loader_arm9.c is referenced in the Makefile but also isn't anywhere in the repo). Do you think it's an issue with my environment or is it an issue with the repo?
View attachment 96153