I dunno what to do. I'm not getting that problem.@Robz8, help me, it's the same problem from last time, the TWLoader freezes when veryfing the banners of the games, i've already deleted the bnricons and nothing, what i need to do?
Make a backupBut then i'm gonna lose everything, i use Emunand yet
Just copy alla yer junk onto your desktop, ya looney!But then i'm gonna lose everything, i use Emunand yet
When you format, you will lose EmuNAND, so that's why you backup EmuNAND, first. You can use Decrypt9 to backup EmuNAND.But when u format, you don't lose the Emunand partition?
After you backup EmuNAND, you should be able to restore EmuNAND.bin with Decrypt9.^Okay i'm doing the backup, after i format, how i'm going to restore the emunand?
Yes.Oh ok, so when i backup all files from the SD, format it, and put it back, the CTRBOOTMANAGER should work with HBL right? it doesn't depend on EmuNand right?
Where goes the roms?
I put it on SD:/nds
But no appears
Would like to double this notion with my own experience. Playing SM64DS and the load times are abysmal. Also audio crackling. I thought this was supposed to load up digital forms of DS games to run in the nds bootstrap? If so, then why is there so much difficulty in running these properly? I mean I get the code's still pretty early, but from what I understand, the nds bootstrap is already a standard in all 3DS consoles, and is the firmware to read NDS game cartridges in the first place, right?I'm running the latest stable 6.6 release of Luma, the latest A9LH, etc. Games just have rather long load times (I tried New Super Mario Bros. and Super Mario 64 DS - the former is so slow that it appears to freeze on a white screen when booting, but the 3DS itself isn't frozen) which might just be because of the relatively slower speeds of SD cards compared to cartridges, but there is also audio crackling. My R4i Gold, however, runs absolutely fine when booting through TWLoader, as if I had just launched it from the home menu. Clock rate settings in TWLoader make no difference.
nds-bootstrap is homebrew that redirects Slot-1 access to SD. This isn't an easy task, since, among other things, DS games can access Slot-1 from either ARM9 or ARM7, but the SD card is only accessible from ARM7.Would like to double this notion with my own experience. Playing SM64DS and the load times are abysmal. Also audio crackling. I thought this was supposed to load up digital forms of DS games to run in the nds bootstrap? If so, then why is there so much difficulty in running these properly? I mean I get the code's still pretty early, but from what I understand, the nds bootstrap is already a standard in all 3DS consoles, and is the firmware to read NDS game cartridges in the first place, right?
Oh, alright. Do I need nds-bootstrap to run TWLoader more effectively?nds-bootstrap is homebrew that redirects Slot-1 access to SD. This isn't an easy task, since, among other things, DS games can access Slot-1 from either ARM9 or ARM7, but the SD card is only accessible from ARM7.
You're thinking of TWL_FIRM, which is used for DS mode in general (and by nds-bootstrap), but doesn't have the ability to run DS games from SD card at all.
TWLoader includes a copy of nds-bootstrap.Oh, alright. Do I need nds-bootstrap to run TWLoader more effectively?