Homebrew MoonShell2Tools incl. Link Launcher

  • Thread starter Thread starter Xenon++
  • Start date Start date
  • Views Views 78,980
  • Replies Replies 265
Status
Not open for further replies.
I select rearrange method because this is useful in "using TF in multiple carts"

### nds.yslaunch.nds is the one and only ysloader which works on DSONEi/SDHC.
 
i`m using it on moonshell 2.10 stable
everything worked
now i can load Commercial Roms
but when i load i cannot find nds.akaio.nds
and it`s already in Moonshl2 extlink what to do now?
ps.i`m using the latest version of nds.akaio.nds
 
i get the error cannot open /nds.akaio.nds i know this means there is something wrong with my config.ini but i dont know what it is im using ysloader to try and launch them can anyone copy and past their full ini file so i can see it.

also whenevr i run ysmenu from my r4 fw it now goes to this screen also
 
ok now it goes into a loop that flashes from a blue loading screen to a brown one and i can exit into ysmenu by holding b, anyway to prevent this loop
 
Your autoboot is being set onto itself or something similar creating an infinite loop. You could go to your ysmenu.ini and clear it out. Then just make sure you don't open anything that loads into something that will once again loop back (thus the infinite loop).
 
xtreme1 said:
ok now it goes into a loop that flashes from a blue loading screen to a brown one and i can exit into ysmenu by holding b, anyway to prevent this loop
Sounds like your loader is loading the menu which is loading the menu which is loading the menu which is loading the menu, etc.

Fix your INI file.
 
i dont know how to do this. i obviously know how to open and edit it just not how to edit and fix my problem i believe all im using is the ndslinker with the moonshell wrap program and yslaunch, and yes it is a constant menu loop as u described
 
Copy/paste the contents of your INI files...
wrap each file in [.code][./code] tags.

There should be 2 INI files, one for the loader, one for the wrapper
 
good news i managed to break the loop and my roms boot, however when i open ysmenu from my r4 fw it boots whatever my last rom opened was instead of just going to the fw anyway to prevent this besides holding b? also how do i autoboot moonshell 2.10
 
If you want to use another nds file to open ysmenu, you need to have a boot that clears the ysmenu.ini's autoboot automatically (unneon's loader does that, and I believe Xenon's ysboot does something similar, but I have never tried it before). As for autobooting to moonshell2, I'm guessing you are using an R4 original or one of its clones. In the case of an R4 clone, you can just use R4denc (google) and use the encoder bit to encode the mshl2.nds that you use and rename that to _DS_MENU.DAT
 
Well thank you for help jurassicplayer
Unneon ttmenu.dat clears auto_boot? (not tested as it doesnt support SDHC)
 
About the looping, (theoretical situation) its as if the autoboot is set to boot nds.ysloader.nds which would then load itself again and again until the end of time.

From what I have played around with, Unneon's loader does clear out the autoboot. It was a long time ago I found that out (so maybe I'm totally off), when I still could use linoul's loader. Linoul's leaves the autoboot there, but somehow I think Unneon's clears it.
 
xenons works well, all that remains for me to fix is now my soft reset wont work in moonshell, since it is autobooting now i have no way to get to my classic r4 menu. it loads a soft reset text about r4 and rudolph instead of an actual menu
 
You could do what I do and decrypt the original _DS_MENU.DAT and just execute that like a regular .nds file. It might work as the Exit to Firmware .nds, though the last time I tried it, I couldn't get it to work (way back when my ds wasn't broken.)
 
so i put it through the r4dencs decryptor, it puts it out as a .dec file do i just rename it a .nds file?
 
Possibly try loading it through a ysmenu loader (think that was how I ended up making mine work). I'm not sure if mine works anymore since I accidentally overwrote it some time ago while trying to fix up a friend's microsd.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum