Hacking m3utils incl. kernel switcher

  • Thread starter Thread starter Xenon++
  • Start date Start date
  • Views Views 12,952
  • Replies Replies 54
DeltaBurnt said:
Can you please try and explain to me how this extlink will help?
So this extlink writes /system/boot.ini and jumps to TouchPod. Then TouchPod "auto boots" the nds.
This enables MoonShell2/MoonShellSimply/DScovered to launch ROM.

Well, if my memory isn't wrong, PinkCatBoy wants to use DScovered on M3DS... That's all...
 
Xenon++ said:
DeltaBurnt said:
Can you please try and explain to me how this extlink will help?
So this extlink writes /system/boot.ini and jumps to TouchPod. Then TouchPod "auto boots" the nds.
This enables MoonShell2/MoonShellSimply/DScovered to launch ROM.

Well, if my memory isn't wrong, PinkCatBoy wants to use DScovered on M3DS... That's all...

So what was so hard about getting it to work?

Don't you just edit the ini?
 
DeltaBurnt said:
So what was so hard about getting it to work?

Don't you just edit the ini?
I don't think it had anything with being hard to get it to work. From the sounds of it, Xenon++ has made the inilink write the .nds name (for simplicity's sake, it shall be called blargh.nds) directly to the touchpod's autoboot feature and then loads Touchpod. So that would mean that if you have blargh.nds somewhere, you could be using Sakura's GUI and have Touchpod's compatibility and quicker updates (the best of both worlds o.0?). Of course that is if I'm understanding this stuff correctly.
The only thing I can't understand at the moment is how this extlink's ability can be expanded (if it can be expanded) because if it can, then maybe it could be possible utilize something similar to moonshell2's extlinks (thus no need to load up GBAExploader, tunavid, etc. Note: GBAExploader example is if user doesn't have the M3 gba expansion).
 
So, he created a NDS file that loads/runs touchpod's auto boot feature for any type of .nds file you want? So that way you compatibility from touchpod as well?

That would be epic.

We could also get NES and SNES integration like moonshell has as well (unless this ext link can only use touchpod's auto boot feature).
 
So MoonShell 2.06 can launch commercial ROMs on M3DS (all roms supported by TouchPod).

I'm afraid but the auto boot feature in TouchPod cannot launch homebrews, so mshl2wrap falls backs to internal homebrew loader.
 
Xenon++ said:
So MoonShell 2.06 can launch commercial ROMs on M3DS (all roms supported by TouchPod).

I'm afraid but the auto boot feature in TouchPod cannot launch homebrews, so mshl2wrap falls backs to internal homebrew loader.

So, it's only for launching roms through moonshell with touchpods engine...and not for Sakura?
 
DeltaBurnt said:
So, it's only for launching roms through moonshell with touchpods engine...and not for Sakura?
I don't know what you mean by saying Sakura... Sakura itself can launch ROMs... Could you explain?

#Of course mshl2wrap can be used for Sakura, but no game settings...
 
Xenon++ said:
DeltaBurnt said:
So, it's only for launching roms through moonshell with touchpods engine...and not for Sakura?
I don't know what you mean by saying Sakura... Sakura itself can launch ROMs... Could you explain?

#Of course mshl2wrap can be used for Sakura, but no game settings...

I know Sakura can launch roms, but what it can't do it launch roms with Touchpod's new game engine updates.
 
DeltaBurnt said:
I know Sakura can launch roms, but what it can't do it launch roms with Touchpod's new game engine updates.
Well I'm using Kaura/Sakura 1.44 with 4.8 game engine. Wrong?

PS. M3R_R4i_r6 comes (no binary change)
 
Xenon, awhile back you said a certain file needing to be copied over (I don't remember the name) was no longer needed to be patched/copied over.

So I took it out of my translated patching instructions for the hex boot, but I had someone in my Kaura FAQ saying he got black screens in the R4 RTS menu by following the instructions I had up.

So would you mind putting the instructions for patching all the files up again so I can add my translated version to my Kaura FAQ.

(Unless you have all these required instructions in the readme of r7)
 
R4iRTS still works if you don't use the new LOADER.ENG to make g6dsload.eng
and iTouch has been blocked to run games
 
dsrules said:
R4iRTS still works if you don't use the new LOADER.ENG to make g6dsload.eng
and iTouch has been blocked to run games
Well, I know what you mean now. So R4iRTS "updating" works. New installation fails.

iTouch kernel works on iTouchDS (as expected)? Now we have to check which is protected, iTouch.* or it_firegame.*...

And It seems that region changing in TouchPod doesn't work. We have to confirm. (Does menu.jp in TouchPod 4.7h works?)
Well, I only want to know how I can see Japanese characters on TouchPod(any lang)

Anyway I'd like to know why they have not blocked M3R_iTDS_PP2 earlier.
 
Xenon++ said:
And It seems that region changing in TouchPod doesn't work. We have to confirm. (Does menu.jp in TouchPod 4.7h works?)
Well, I only want to know how I can see Japanese characters on TouchPod(any lang)
Japanese menu for iTouch 3.8 is working fine, you just need to use boot.gb to make iTouchDS.nds or g6dsload.eng, if you use boot.eng, it cannot be change the Japanese or Chinese
So, I think firegame has been blocked
 
So I have to clarify which is true: "iTouch.* loads it_firegba" or "it_firegame jumps to GBA mode"

#If latter we could search for "swi 6"
 

Site & Scene News

Popular threads in this forum