Hacking Mighty Channels

[Skater4599]

Glad to hear it Marc_Max! Question, will you be including the mods that have been made? I really liked the latest with the titles under the pictures and being able to scroll left/right from page 1-end etc.

 

[XFlak]

I'm back to MC development, expect BETA6 soon. It will be ready to be tested with special d2x 21003 version.

marc, I have a suggestion. Can you have mighty channels treat cIOSs with version numbers 21003-21020 as d2x cIOSs? That way when d2x v4 (or v4 beta) is released you won't need to update mighty channels to detect it... and the same applies for v5, v6... v20, etc.

what do u think?

 

[scooby74029]

good idea xflak

way to plan ahead

scooby74029

 

[marc_max]

I'm back to MC development, expect BETA6 soon. It will be ready to be tested with special d2x 21003 version.

marc, I have a suggestion. Can you have mighty channels treat cIOSs with version numbers 21003-21020 as d2x cIOSs? That way when d2x v4 (or v4 beta) is released you won't need to update mighty channels to detect it... and the same applies for v5, v6... v20, etc.

what do u think?

Yes, I already thought on that, don't worry

In fact, it's already implemented.

 

[XFlak]

Yes, I already thought on that, don't worry

In fact, it's already implemented.

well... you know what they say about great minds!
good job m8!

 

[Hugh Verdam]

I'm back to MC development, expect BETA6 soon.

Wonderful! What a great app!

 

[Taleweaver]

I'm currently testing out things in uneek...but I'll gladly give beta 6 some test runs.

 

[marc_max]

BETA6 on the first post.
Features:
*multilanguage (please try your language and check if there is any error)
*some fixes
*support for Bit Trip Flux
*support for d2xb3 partition and path selector


The support for d2x isn't tested, so I can't guarantee it will work.
I have commented the lines that check for 2100X for now (it still checks for 21). If you are using d2xb3 please try if --partition and --path parameters are still working. I changed the way davebaol modified beta5 and I haven't tested it yet.
Also, if it works please check if banner sound plays correctly and if Bit Trip savegames are created correctly.
NOTE: path can't be longer than 32 bytes.

 

[davebaol]

- d2xv3
- partition=0
- path=/nand

now banner sound plays but when you launch the game MC crashes on "Searching for main DOLl"

 

[marc_max]

- d2xv3
- partition=0
- path=/nand

now banner sound plays but when you launch the game MC crashes on "Searching for main DOLl"

Oh yes, I know what's happening. I'll fix it tomorrow.

 

[davebaol]

Well that's weird, now MC doesn't crash anymore.
Really don't know why, but everything seems to work.
I'm a bit confused 'cause nothing has changed. Same cios, same config, same everything.

EDIT:
Ok, sometimes it works and sometimes it doesn't.

 

[freestile]

So far So good for me with Mighty Channels BETA6 d2xv3. Keep up the good work guys.

 

[XFlak]

BETA6 on the first post.
Features:
*multilanguage (please try your language and check if there is any error)
*some fixes
*support for Bit Trip Flux
*support for d2xb3 partition and path selector


The support for d2x isn't tested, so I can't guarantee it will work.
I have commented the lines that check for 2100X for now (it still checks for 21). If you are using d2xb3 please try if --partition and --path parameters are still working. I changed the way davebaol modified beta5 and I haven't tested it yet.
Also, if it works please check if banner sound plays correctly and if Bit Trip savegames are created correctly.
NOTE: path can't be longer than 32 bytes.

I just put out a minor DB update to ModMii so all d2x v3 cIOSs will now all be v21003

 

[Gan1664]

Very good !!

I didn't look very close but the french translation seems good !

The path argument works.

I just wonder how to change skin and what is done in the NAND management options (sysconf and Mii) I tried it but it seems to have no effect.

Thank you again Marc.

 

[Taleweaver]

First checks:
(mighty channels beta 6, d2x v3).

+folder redirection works
+dr Mario works
+tetris pary worked since the second time (the first time, it gave me "An error occurred when writing to/reading from wii system memory. Refer to the wii operations manual for further instructions").

-sonic 4 now blackscreens on me (never did that before). With rev17, it gives me "Identify failed" (note: since rev17 doesn't support the folder redirection, this is an attempt to run the game from my UNEEK nand).
-blackscreen from star fox 64 and swords&soldiers (base 56 & 38...s&s gave a "an error has occurred" on 38).
-"an error has occurred" from maboshi arcade. Second time, the screen just stayed black (base 56).
-the "return to" menu doesn't work from within games that work.


Not exactly the best of results. Especially since I used these games (sonic, star fox) mainly to check whether any game works. I haven't tested much 'known problem' games, but I doubt it'll make things much better. Sorry.

I have to mention that I haven't tested the released v3 version of d2x before, so I can't really say what is causing all these errors.

 

[papermanzero]

I like Mighty Channles. =D
Great work so far, marc.

The game compatibility is handled by the emu in the cios.

The "An error occurred when writing to/reading from wii system memory. Refer to the wii operations manual for further instructions" messages is a regular message in d2x V3 (in my case).
I got it in Bonsai Barber (which is working sometimes, but most times not), Max & the Magic Marker, Swords and Shields (as good as never working) and Megaman 9 (which is working most times and the message appears very rare).

I didn't get the time to switch to d2x beta 6 v3 to log the data.
But everyone who has problems should do that and post the logs (in the cios thread).
I guess it's easier to see the root cause (and to debug this problem)

My settings:
Partition 1
path: mighty/NAND
IOS: 248 with d2x v3 Base 56

 

[davebaol]

@marc_max
Often MC beta 6 crashes on "Searching for main DOL" for me.
TBH I cannot exclude it's a cios problem.
Can you replicate the issue?
And then can you isolate with a bunch of printf in check_dol the code or the system call causing the crash?
if you like I'm ready to be your tester.

 

[M1r0]

If SNEEK can preform NAND emulation without any cIOS's, why does this program require them?

 

[Taleweaver]

That question is more a sneek-related question and should be asked in this thread. I think the last question of the first post answers it best:

What is SNEEK and How does it do what it does?
sneek is basically just a way to lie to the PPC in the wii. the wii has 2 processors ARM and PPC. games, the system menu, channels, most homebrew, and pretty much every other program that accepts user input and draws on the screen run on the PPC. when these programs want information from the wii's internal memory, internet, dvd, sd card, or pretty much anywhere else, they have to ask the program running on the ARM (an IOS usually) for it (except when the wii is in gamecube mode).

sneek runs on the ARM and it redirects where information comes from and in some cases, patches that information with false data. the end result is that the program running on the PPC asks for data from the wii's nand and it gets it from the sd card instead. if the PPC wants data from the dvd drive, sneek can give it data from a usb drive instead. when the system menu asks how much space is used for channels, sneek flat out lies about it and gives a low number so the system menu doesnt give the "system memory is full" message.

about cIOS and sneek, since IOS and sneek both run on the arm, there is a chance that they will not play nicely together. they are both trying to patch stuff and be smart, but they dont realize that each other is there and both are trying to be smart. the end result is that when sneek tries to load a cIOS, it doesnt load all of it and the parts of it that do load start doing their normal cIOS stuff and end up patching memory where sneek is and both of them end up not working right.

A bit technical answer, but yeah...it is a technical question.

 

[M1r0]

I'm sorry that I'm still posting here, but I didn't feel like this answered my question. I was wondering that, if SNEEK, which can emulate the nand, requires no cIOS to do so, why does this program, which also does NAND emulation, need a cIOS