Yet Another Syscheck Issue

[GoogleCodeExporter]

What IOS did you use?
36 and 55 
What is the first 4 digits of your Wii's Serial Number?

What steps will reproduce the problem?
1. Install a new patched IOS36 to slot236
2. Run a syscheck

What is the expected output? What do you see instead?

(using 36)* The new IOS236 is correctly checked but the scan stop to IOS9, 
it doesn't show the IOS4.

(using 36)* I added another new IOS, a copy of no-patched 36 to slot237 
and run the syscheck, Now, it correctly detect IOS236 and 237 but stop to 
IOS12 then it ask me if i want to save reports, said No and CHECK 
CONTINUE, IOS9 appeard for a second and i get code dump.

(using 36)* I reloaded Dop-Mii, i have done the same check, it again stop 
to IOS12 then ask me if i want to save the report , said No, then continue 
to IOS9 but now there is no code dump. :o

(using 55)* My IOS55 accept already fakesign so i tested with it,like 
others check, it show 236 & 237, stop to 12 ask me, so said No and.. Code 
dump...

(using 55)* Reloaded Dop-Mii, select IOS55 and run the syscheck, exactly 
the same but now there is no more code dump.

I want to do more test, adding one more IOS and see if it stop to IOS13 
and continue after asking me if i want to save and i want also test if 
when i delete all the new IOS, it run perfectly.

Original issue reported on code.google.com by cs-nut...@live.fr on 11 Mar 2010 at 7:47

[GoogleCodeExporter]

Take a look at Issue 7

Original comment by Lunatik.CN@gmail.com on 11 Mar 2010 at 8:03

[GoogleCodeExporter]

Also anytime you get a code dump. Please provide me with the Stack Dump. With 
it I
can pinpoint the exact line of code on where it crashes.

Original comment by Lunatik.CN@gmail.com on 11 Mar 2010 at 8:12

[GoogleCodeExporter]

yeah i took picture of the two code dump

Stack dump:
800470bc -> 80034a34 -> 80021848 -> 80021efc ->
800225e4 -> 800226c4 -> 800042cc -> 80047ddc ->
80047d7c

&

Stack dump:
800470bc -> 80034a34 -> 8002629c -> 800218b8 ->
80021efc -> 800225e4 -> 800226c4 -> 800042cc ->
80047ddc

Original comment by cs-nut...@live.fr on 11 Mar 2010 at 8:29

[GoogleCodeExporter]

Thanks that helps. I'll let you know if what I find is similar to the problem 
with
Issue 7

Original comment by Lunatik.CN@gmail.com on 11 Mar 2010 at 9:22

[GoogleCodeExporter]

Both of these stack dumps are caused by the WiiMote crashing the IOS. Can you 
go to
the IOS menu and tell me what IOSes you have installed < IOS9 and what versions 
it shows.

Original comment by Lunatik.CN@gmail.com on 11 Mar 2010 at 9:30

[GoogleCodeExporter]

Just IOS4 v65280 stub

*I just became aware of syscheck doesn't show me my IOS11*

Original comment by cs-nut...@live.fr on 12 Mar 2010 at 1:05

[GoogleCodeExporter]

K, I have a theory on the crash and a possible way of fixing it. Currently when 
the
prompt to continue comes back it tries to load the WiiMote on the very last IOS 
that
was just ran for checking the various patches. I believe what I should do is 
reload
back to the selected IOS and try to avoid reloading the older IOS as it may have
issues with reloading the WiiMote.

As far as IOS11 goes, what revision does it show installed?

Original comment by Lunatik.CN@gmail.com on 12 Mar 2010 at 2:37

[GoogleCodeExporter]

I Gonna take a look at Issue 7 ;)

IOS11 v256 (stub)

Original comment by cs-nut...@live.fr on 12 Mar 2010 at 5:31

[GoogleCodeExporter]

If it's a stub then yes it won't show up on the report.

Original comment by Lunatik.CN@gmail.com on 12 Mar 2010 at 5:44

[GoogleCodeExporter]

I'm too bad, i fogot that :s

Original comment by cs-nut...@live.fr on 12 Mar 2010 at 5:56

[GoogleCodeExporter]

Hello again !
I have made more tests ;)
But finally, I just made a Nintendo update and rehack my Wii then I added a lot 
of 
IOSes in différents slots (patched or not, here or there xD)
I ran Syscheck and get no codedump anymore !! :D
Deleted all the useless IOSs and now it's OKAY !

Maybe, a null tmd like in Issue7 but I don't use de boot.dol you gave there.

So I think the problem was my IOSs and not the Syscheck so you can now close 
the 
Issue

Original comment by cs-nut...@live.fr on 18 Mar 2010 at 9:05

[GoogleCodeExporter]

csnut, see here:
http://hackmii.com/2009/08/timing-is-everything-the-case-of-the-unsoftmoddable-w
ii/
I also had freeze during syscheck, I found out that was because I had 
unsupported old
IOSes on my Wii.  I removed them and it's OK now :)
Maybe that's your problem too.

Original comment by lpq...@gmail.com on 18 Mar 2010 at 10:57

[GoogleCodeExporter]

Yes I Know it but it's not that, my Wii was always 4.2 with latest IOS, just 
applied 
some patches ;)

Original comment by cs-nut...@live.fr on 19 Mar 2010 at 6:18

[GoogleCodeExporter]

Thanks for the feedback. But, I still think it's a WiiMote issue when it tries 
to
reinitialize for some of the older IOSes. I do have a planned patch to hopefully
correct the WiiMote timing issue causing the crash in our next issue.

Original comment by Lunatik.CN@gmail.com on 19 Mar 2010 at 12:14

• Changed state: Accepted

[GoogleCodeExporter]

Okay ;)
If you have an ideas of what steps will reproduce the problem, maybe i can make 
more 
tests :)

Original comment by cs-nut...@live.fr on 19 Mar 2010 at 12:48

[GoogleCodeExporter]

Should all be fixed now. Any new issues with syscheck please make a new issue.

Original comment by castleva...@yahoo.com on 21 Nov 2010 at 4:19

• Changed state: Fixed