- Add wiimote support (instead of reset button) Cboomf 19:51, 6 July 2009 (UTC)
The wiimote cause code dumps on some ios, so reset button is the only way --The Lemon Man 16:58, 9 July 2009 (UTC)
- Make the scans automagic (don't need to press a button for each one) Cboomf 19:51, 6 July 2009 (UTC)
You may need some time to see the result --The Lemon Man 16:58, 9 July 2009 (UTC)
- -Couldn't a file be placed on the SD if no pause is required ? Cboomf 21:16, 14 July 2009 (UTC)
- Fix "Trucha bug""Flash access" in csv to seperate columns Cboomf 19:53, 6 July 2009 (UTC)
Fixed :D --The Lemon Man 16:58, 9 July 2009 (UTC)
- Some IOS is not detected. (Not sure if it's only my case) List of IOS not detected in my wii: 4,9,11,16,50,51,254 Wwywong 07:01, 7 July 2009 (UTC)
Heh, this is a feature, this time it wont process stub ios --The Lemon Man 16:58, 9 July 2009 (UTC)
What do the results actually mean? Does FIXED mean it's been patched to use fakesign, or that it's been fixed by nintendo to not use fakesign? I ask because it reports all of mine (save for the system menu one) as FIXED, when I run fakesigned stuff all the time, and have used the IOS downgrader to make sure I could run fakesigned apps.
I'd guess it means FIXED = Works. :P If you run fake-signed stuff, it works. ~ Vithon
Fixed means that the homebrew can't use fake tickets on that ios. The_Lemon_Man
Makes sense since GREEN means good to go and RED means Error, Problem, etc.
I also have an issue with the results. I know a particular IOS is unfixed, yet the checker says it is fixed. I know it is not fixed since I can run Trucha signed content off of it. Ccfman2004 00:20, 5 May 2009 (UTC)
Requires Fakesign Accepting ios
Does it really nedd a fakesign accepting ios to work? Whats the point of creating a fakesign checker if yu cant run it unlesss your wii accept fakesign code? ChuckBartowski
I just loop trough a table of ioses and for each ios tries to use a fake ticket to identify as SU, if he fails it means that the ios is patched The_Lemon_Man
OK i kind of get what your going at but that doesn't mean it requires a fakesign capable ios to work like the page says does it? Because if i understand what your saying correctly it will always run thought the different versions of ios even if you arent capable of actually running fakesign code. So therefore you dont need it to run it.-- ChuckBartowski
OK nm scratch that i see youve changed it already-- ChuckBartowski
Length of Check?
I got through IOS31, and after that it just seemed to do nothing, so I ended up shutting it off. How long is a normal check supposed to take? --WB3000 20:08, 16 March 2009 (UTC)
I've experienced this as well. It seems the program hangs when it scans an IOS that has been (re?)installed manually. In my case, I had patched 37 with freethebug, and it stopped after 31. After I had deleted that title, the program went up to 55. Another issue I've had is during that scan, 51 checked as fixed, and I'm pretty sure I had opted to patch the bug back into IOS51 with tona's IOS51 and Wii Shop installer.
I too am having a problem. It shows IOS9, 30, 31 then stops.
Also, it seems to only check a few IOS's, not all installed IOS's EDIT: I took a look at the source code and it has been hardcoded to only check certain IOS's. I think it should modified to check all installed IOS's.
I too have the hang problem. It check the first few, and stops after IOS37. Is it because it have problem reading later IOS? Is the above comment true about the problem caused by having freethebug version of IOS? I remember I have a few in there. I ended up have to hard power off my wii to quit the app. I guess that's not normal. Could the author respond to that? Thanks! --wwywong
You may use temporary files on the sd card to actually check all the ios'es, hence repeated running would skip the failing ones and report that... or display a selection for starting ios number... since now if it stucks in one of them then the rest of the ios'es are not checked... --I R on 18:24, 27 March 2009 (UTC)
How would I go about doing that? Ccfman2004
Well that suggestion was not to end users but to the coder of the app. --I R on 18:24, 27 March 2009 (UTC)
Whoops, I must need more sleep. Ccfman2004