Thank's that's why I was asking to modify it somehow to out something there before the version numberOnly original Reinand has version string, AuReiNand has the entire process deliberately removed.
Thank's that's why I was asking to modify it somehow to out something there before the version numberOnly original Reinand has version string, AuReiNand has the entire process deliberately removed.
i am trying to add armips.exe to my path and to see if i can find what is the code,Thank's that's why I was asking to modify it somehow to out something there before the version number
oh, PLEASE @Aurora Wright re-add it!Read the first post, the code isn't there. Aurora removed the arm9 thread.
No, there are other ways (unlink your stuff and give sysnand another theme then emunand and setup your icons in another way.)oh, PLEASE @Aurora Wright re-add it!
i have RED in EMUNAND because i never use it (except decrypt9) while i use arm9loaderhax on sysnand, it would be useful to see if you are actually in reinand cfwNo, there are other ways (unlink your stuff and give sysnand another theme then emunand and setup your icons in another way.)
On my other system i have red for sysnand (warns me enough to know i'm in sysnand) and miiplaza theme on emunand, on sysnand there are no icons, all is in folders, on emunand i have my icons i play every day and the rest in folders
I said countless times that I won't, as it patches unrelated things in RAM and as of today it's completely useless (we have Home Menu themes and other ways to tell apart the NANDs). On top of that, it requires work to keep all the offsets updated for O and N3DS (the thread would have to be different for the two).oh, PLEASE @Aurora Wright re-add it!
ah, ok, thanks for the explanation.I said countless times that I won't, as it patches unrelated things in RAM and as of today it's completely useless (we have Home Menu themes and other ways to tell apart the NANDs). On top of that, it requires work to keep all the offsets updated for O and N3DS (the thread would have to be different for the two).
If you mean 3dsx then yeah I can compile it as I still have a9lhax source around.I assume this is AurReinand (this thread) someone compiled my OTP for me and gave me the files for n3ds and I have no idea what I'm running as it just has normal firm version numbers in emunand
I said countless times that I won't, as it patches unrelated things in RAM and as of today it's completely useless (we have Home Menu themes and other ways to tell apart the NANDs). On top of that, it requires work to keep all the offsets updated for O and N3DS (the thread would have to be different for the two).
Edit: it would have to be different for emuNAND and sysNAND too, if you want different strings
The only "code" I could provide that didn't mean "doing it on my own" would be to tell you "go check out the original ReiNand source". If you're able to "mess with things" (I don't define myself as a coder yet... but I like to mess with things) you'll figure it out easily. Can't boot HBL from boot from a CFW, and there's no use (yet) in having both the FIRM for NTR and the latest FIRM (currently, everything works fine on both. So just use the NTR one if you use NTR).Could you provide some code to make it ? Having "Rei" in front of my firmware was nice, and with A9LH I would like to see if I'm on SysNand or EmuNand (even if that's pretty obvious, it was still a nice thing to see it on settings, a bit like rxTools did).
More importantly, could you add some buttons shortcuts at boot on A9LH ? For example, it would be really nice to boot HBL from boot, or using a 10.2 FIRM on 10.6 SysNAND to be able to use NTR.
Anyway, thanks a lot for your work, it's really, really great.
Is it normal to have sig checks disabled on my SysNAND with this because it is for some reason on my 9.2 when I boot into it holding down LThe only "code" I could provide that didn't mean "doing it on my own" would be to tell you "go check out the original ReiNand source". If you're able to "mess with things" (I don't define myself as a coder yet... but I like to mess with things) you'll figure it out easily. Can't boot HBL from boot from a CFW, and there's no use (yet) in having both the FIRM for NTR and the latest FIRM (currently, everything works fine on both. So just use the NTR one if you use NTR).
Sig checks are always disabled. There's no con to it.Is it normal to have sig checks disabled on my SysNAND with this because it is for some reason on my 9.2 when I boot into it holding down L
The only "code" I could provide that didn't mean "doing it on my own" would be to tell you "go check out the original ReiNand source". If you're able to "mess with things" (I don't define myself as a coder yet... but I like to mess with things) you'll figure it out easily. Can't boot HBL from boot from a CFW, and there's no use (yet) in having both the FIRM for NTR and the latest FIRM (currently, everything works fine on both. So just use the NTR one if you use NTR).
This CFW is meant to be minimal, so to provide everything an user would *really* need without adding useless features. A it's open source, everyone can customize it to their needs.
if you know how and you will be able to make it arm9loaderhax compatible... YES PLEASE!I saw that on GitHub, but this would patch emuNAND and sysNAND, I didn't saw any code to add, let's say "Rei-E" for EmuNAND" and "Rei-S" for SysNAND...
I know it's supposed to be minimal and this will not be merged, but I was thinking about making few "patches" for personal use to let users custom it like they want, that would be really great, I think.
if you know how and you will be able to make it arm9loaderhax compatible... YES PLEASE!
Patches require asm. Main logic of cfws is in c.I know a bit of C++ (I'm a Java dev but I know the syntax and basics of C++) and making a patch is really easy. That said I'm not familiar at all with 3DS architecture and code, and I don't have any hardmod, so I'm a bit worried of bricking it by letting my own code running on it.
That said, if I ever do some modifications, then I'll release it as a fork and make patches available .
Patches require asm. Main logic of cfws is in c.