Since the newest release (v3.5) implements parts of yifanlu's Cosmo3DS injector for things like region-free, does it also include the eShop fixes for region-swapped 3DSes?
how can redNAND be faster when it is physically the same card it reads from and writes to as emuNAND?
Because of the way SD card works. Sequential read is faster, and with GW EmuNAND you need to reach first bytes at the end of EmuNAND partition, before going back to the start of the partition. With RedNAND everything is in the right order so basically it's sequential read.
Also, RedNAND can be shrinked so less bytes to read (even if reading sequential 0 is really fast with "expended" emuNANDs).

RedNAND is sightly faster because of how it's written in the partition table or something like that, it shifts everything by 512 bytes instead of writing the NAND on the end of the 512 bytes or some thing like that.how can redNAND be faster when it is physically the same card it reads from and writes to as emuNAND?
--------------------- MERGED ---------------------------
what do you mean by "better" emunand loading? in what way did loading improve?
so changing emuNAND to redNAND is not recommended only because of the small performance increase, right?RedNAND is sightly faster because of how it's written in the partition table or something like that, it shifts everything by 512 bytes instead of writing the NAND on the end of the 512 bytes or some thing like that.

Well, I guess it depends on how much it takes to boot emuNAND, cutting a few seconds might be nice. Otherwise just keep emuNANDso changing emuNAND to redNAND is not recommended only because of the small performance increase, right?

yea, just seeing all the replies while having my coffee, lol. Gotta head to work for the next 8 hrs in a min. Brainstorming some ideas as well.
thanks for clearing that up. and does it make a perceptible difference? or is it an impact that is barely measurable.
so changing emuNAND to redNAND is not recommended only because of the small performance increase, right?
Just a tiny clarification, you switch using EmuNAND9Tool, not Decrypt9WIP.It is slighty faster, not a huge difference. But RedNAND has no real downside except of the compatibility (but ReiNAND, AuReiNAND and Cakes are compatible, so not a big deal).
Where did you see that it was not recommended ? It's reliable, you can switch to RedNAND with Decrypt9.
Just a tiny clarification, you switch using EmuNAND9Tool, not Decrypt9WIP.
Just a tiny clarification, you switch using EmuNAND9Tool, not Decrypt9WIP.
You actually need to do the switch in EmuNAND9You can do with both, using the latest Decrypt9 build. @d0k3 made me testing it...

You actually need to do the switch in EmuNAND9. Decrypt9 can handle both, but it can't convert.
EDIT: I have to add, I still recommend you make a EmuNAND backup before the conversion, just in case something totally unexpected happens.
Every time I add something, it needs not to impact the code much or the performance, and multiple different people (like 5 or so) asked for it.I dont really follow her mod. i just know it has a ton of random feature.. i feel like shes making the same mistakes rxtools did, but i digress..
I still focus on emunand because its just as fast as sys, and if you have a decent SD card, the emunand partition shouldnt be a problem.
Currently, RN has emunand, firmlaunch sys, RF, sig patches, custom ver string, etc and still keeps a fairly minimal codebase

Fuck the haters Aurora.Every time I add something, it needs not to impact the code much or the performance, and multiple different people (like 5 or so) asked for it.
Other than that, yes it has several options, but I spend most of the time cleaning the code (yeah, I'm OCD about it. you can notice it if you look at the commits). I simplify everything that can be simplified, remove every line that I can remove.
I also try to keep it readable and comment everything.
As an example, to avoid the bloat of having the user input a loader.cxi compatible with their FIRM, I found a way to patch the loader to make it "universal". I also cleaned the patching code in loader a lot.
Also, so much hating on this thread. Makes me think I'm dumb to spend hours (and, often, hours in a single day) on this.
Part of it I think stems from ignorance. Most people do not know what they are talking about on the forum. Do not be discouraged, you have an interesting project, just people have different opinions of what they want. I like to think about it like the Emacs vs vi debate. HahaEvery time I add something, it needs not to impact the code much or the performance, and multiple different people (like 5 or so) asked for it.
Other than that, yes it has several options, but I spend most of the time cleaning the code (yeah, I'm OCD about it. you can notice it if you look at the commits). I simplify everything that can be simplified, remove every line that I can remove.
I also try to keep it readable and comment everything.
As an example, to avoid the bloat of having the user input a loader.cxi compatible with their FIRM, I found a way to patch the loader to make it "universal". I also cleaned the patching code in loader a lot.
Also, so much hating on this thread. Makes me think I'm dumb to spend hours (and, often, hours in a single day) on this.
you 2 make a great job, just in opposite ways there are no winners, just people that use emunand or people that use sysnandEvery time I add something, it needs not to impact the code much or the performance, and multiple different people (like 5 or so) asked for it.
Other than that, yes it has several options, but I spend most of the time cleaning the code (yeah, I'm OCD about it. you can notice it if you look at the commits). I simplify everything that can be simplified, remove every line that I can remove.
I also try to keep it readable and comment everything.
As an example, to avoid the bloat of having the user input a loader.cxi compatible with their FIRM, I found a way to patch the loader to make it "universal". I also cleaned the patching code in loader a lot.
Also, so much hating on this thread. Makes me think I'm dumb to spend hours (and, often, hours in a single day) on this.

i've had several people ask for region free, but im OCD too, so i told them as soon as i can do it right. I was gonna do what salt did and add a new process, but with the custom loader, thats even better. Point is i'm ocd in other ways but also minimalism is more than just a small codebase, its minimal functionality to be called a (in this case) cfw.Every time I add something, it needs not to impact the code much or the performance, and multiple different people (like 5 or so) asked for it.
Other than that, yes it has several options, but I spend most of the time cleaning the code (yeah, I'm OCD about it. you can notice it if you look at the commits). I simplify everything that can be simplified, remove every line that I can remove.
I also try to keep it readable and comment everything.
As an example, to avoid the bloat of having the user input a loader.cxi compatible with their FIRM, I found a way to patch the loader to make it "universal". I also cleaned the patching code in loader a lot.
Also, so much hating on this thread. Makes me think I'm dumb to spend hours (and, often, hours in a single day) on this.




