Hacking Wii Mod

[MassiveRican]

No one has told me about an error quite like this yet so looks like you got a new one. I would be interested if it acts the same when loaded from SD. You mentioned what happens when you load 2.7 from various ways, are you saying 2.8 acts the same whether you load it from HBC or forwarder? When it does eventually load are you in AHBPROT mode? Are you running on a normal nand or is it an emulated one(sneek, nandemu, other)? Have you already run check IOSs, and by that I mean is it loading up a previous csv output or have you not run that and so it's starting fresh? Is there any output(to the screen) while its frozen or is it a black screen(or some other color for that matter)? Eh, if you know what IOSs you have I probably don't need to see your syscheck. Do you have a lot of non official IOSs? What custom IOSs do you have installed bootmii IOS, usb loader CIOSs, other customs? Do you see anything weird in the title manager? I know that is kinda a vague question but I just mean something that really stands out. If you don't have much experience with a title deleter, be careful not to delete any titles just look.

Well I'll give it a try later this weekend, if I can't repeat then I'll likely have more questions or have to make a debug version.

Thanks for the prompt response man and I will definitely give back any feedback or ideas for improvements I come across.

Ok on the reporting. I'm running on a normal NAND, Bootmii as boot2 and cIOS 254, 202, all hermes 222-224 and d2xv7a5 fixed 245-251. Now w/the SD card WiiMod 2.8 so far works flawless. However on USB, 2.8 acts the same way w/lag regardless of how I load it HBC/PL2/Forwarder on SM and I get just a BLACK screen w/no text, unlike 2.7 which shows me some text letting me know it's loading. When I load I'm in AHBPROT mode and w/title manager I didn't see anything strange beyond title names for game channels created w/WiiGSC. On 2.7 w/my USB WiiMod acts almost like it does on SD, quick startup, WAD manager and the apploader work correctly as well. With 2.8 though WAD Manager acts funny, it hangs for a bit when I choose USB Mass Device and when it loads the device it's just a bunch of crazy font w/an infinite amount of files and directories all 0.00mb. Here's a pic. WiiMod 2.8 WAD Mngr pic

With Apploader on 2.8 it says "Mounting Device Please wait... ok! Retrieving file list... No files found. However with 2.7 on my USB, apploader finds and boots files just fine.

Thus far those are the only things I found but one thing that 2.7 & 2.8 have in common is a code dump during check IOS's. Last one I see prior to dump is 251 I only have 254 afterwards so not sure what that means as syscheckb12 does not dump. On SD check IOS's ran fine as well w/2.7 & 2.8 so no idea why it code dumps. Also for some reason i have a stubbed IOS 4,10,40,51,52. I have no idea why or how. I used MauiFrog's guide so I don't know if that has anything to do w/it. I run his guide whenever he makes an update so I have his latest WAD packs installed and all I know is IOS 40 is usually used for Korean Region Wii's.

Ok finally my last comment would be an addition/Enhancement to WiiMOD. I like the check IOS's feature and the resulting output of CSV; I would like the option to see the report in simple text if possible within wiimod right after the report, and the ability to load and see the csv file whenever I want so I can just view the last IOS check run. That way I wouldn't have to exit wiimod at all to see the report. Not necessary but it would be cool if I could do that

Again thanks for taking the time, and have a great weekend.

P.S. oh and do you think I should remove and replace the stubbed IOS's.. I don't really have much problems when I'm playing games or messing around w/my apps but I don't like to have stubbed IOS's unless you think I might mess something up in the process.

 

[jskyboo]

With 2.8 though WAD Manager acts funny, it hangs for a bit when I choose USB Mass Device and when it loads the device it's just a bunch of crazy font w/an infinite amount of files and directories all 0.00mb. Here's a pic.
That bug I have known about thanks to crazyrabbit0 and as it turns out the two bugs are one and the same. They both are because usb is broken. The delay is when it loads the files from usb it is trying to access the usb and failing. The crazy font in wad manager is just garbage as it isn't actually reading the usb. From what I can tell it would seem usb broke a few versions back so I'll try and fix that for the next version. Thanks for letting me know.

Thus far those are the only things I found but one thing that 2.7 & 2.8 have in common is a code dump during check IOS's. Last one I see prior to dump is 251 I only have 254 afterwards so not sure what that means as syscheckb12 does not dump. On SD check IOS's ran fine as well w/2.7 & 2.8 so no idea why it code dumps.Code dumping in check IOS sometimes means you have a bad IOS but not always. Sometimes some custom IOSs cause issues and so if it always dumps on the same IOS and you know its good then you can configure the settings to either skip it by number ex "skipios=254" or whichever is causing the issue. Or you can skip it by hash with "skiphash=58c5d8b1,ccaa035b,14d3e159,3209c037,a915552a". Wii Mod will skip known stubs and some other IOSs but there will always be some that it doesn't already know about so for those you can change the settings to skip your problem IOSs.

Also for some reason i have a stubbed IOS 4,10,40,51,52. I have no idea why or how. I used MauiFrog's guide so I don't know if that has anything to do w/it. I run his guide whenever he makes an update so I have his latest WAD packs installed and all I know is IOS 40 is usually used for Korean Region Wii's.

P.S. oh and do you think I should remove and replace the stubbed IOS's.. I don't really have much problems when I'm playing games or messing around w/my apps but I don't like to have stubbed IOS's unless you think I might mess something up in the process.

It's been a while since I looked at all the details of Maui's guide but most guides don't have you delete the old stubs or replace them with non stubs and just leave them on the Wii. Personally I prefer to delete them and install the latest nonstub for those IOSs. Having the stubs on your Wii won't cause any problems unless you install an old system menu that needs them. Most guides assume you will never intentionally or accidentally install an old system menu and so it doesn't matter(that is Nintendo's view on it as well), I though prefer to keep working IOSs in their place so that it doesn't matter if I switch system menu's I still won't be bricked. Really its up to you, but if you would like to replace them with their latest non stubs, just go to the IOS menu, select to delete all stubs, then select to update all IOSs, that will download the latest non stubs.
Note there are also some issues with some Wiis that they can't use the old non stubs anyways and unless they have 60 installed in their place they will brick. I actually haven't seen this myself and don't know much about why these Wiis can't use the old IOSs. I don't know if this is true at all but it is something to consider for people thinking about downgrading. Its why most are strong advocates against downgrading. And well there really isn't much reason to downgrade, I only do it cause I have bootmii boot2 and it doesn't matter, but I can't recommend it for those that do not have the safety net.

QUOTE(MassiveRican @ Aug 12 2011, 08:58 PM)

Ok finally my last comment would be an addition/Enhancement to WiiMOD. I like the check IOS's feature and the resulting output of CSV; I would like the option to see the report in simple text if possible within wiimod right after the report, and the ability to load and see the csv file whenever I want so I can just view the last IOS check run. That way I wouldn't have to exit wiimod at all to see the report. Not necessary but it would be cool if I could do that

I like the idea of a csv quick viewer, I'll see about getting that in the next version. As for the simple text it does make loading info back from csv next run a little tricky. What would you like the simple out to look like? I'll think about it.

 

[MassiveRican]

Code dumping in check IOS sometimes means you have a bad IOS but not always. Sometimes some custom IOSs cause issues and so if it always dumps on the same IOS and you know its good then you can configure the settings to either skip it by number ex "skipios=254" or whichever is causing the issue. Or you can skip it by hash with "skiphash=58c5d8b1,ccaa035b,14d3e159,3209c037,a915552a". Wii Mod will skip known stubs and some other IOSs but there will always be some that it doesn't already know about so for those you can change the settings to skip your problem IOSs.
Awesome thanks for the tip, and again it's no big deal anyway since using the SD card check IOS's doesn't fail at all.

It's been a while since I looked at all the details of Maui's guide but most guides don't have you delete the old stubs or replace them with non stubs and just leave them on the Wii. Personally I prefer to delete them and install the latest nonstub for those IOSs. Having the stubs on your Wii won't cause any problems unless you install an old system menu that needs them. Most guides assume you will never intentionally or accidentally install an old system menu and so it doesn't matter(that is Nintendo's view on it as well), I though prefer to keep working IOSs in their place so that it doesn't matter if I switch system menu's I still won't be bricked. Really its up to you, but if you would like to replace them with their latest non stubs, just go to the IOS menu, select to delete all stubs, then select to update all IOSs, that will download the latest non stubs.
Note there are also some issues with some Wiis that they can't use the old non stubs anyways and unless they have 60 installed in their place they will brick. I actually haven't seen this myself and don't know much about why these Wiis can't use the old IOSs. I don't know if this is true at all but it is something to consider for people thinking about downgrading. Its why most are strong advocates against downgrading. And well there really isn't much reason to downgrade, I only do it cause I have bootmii boot2 and it doesn't matter, but I can't recommend it for those that do not have the safety net.
Well I'm glad I do have that safety net but regardless I care not for d/grading so I won't be doing any of that anyway. I went to take a look at MauiFrogs guide and my stubbed IOS's have nothing to do with it, the IOS's stubbed on my Wii aren't even in his WAD packs and I have not attempted to region change. Most likely they were stubbed by ninty themselves way back before my mod when I was updating to 4.3. Thanks for your help on this as well I'm going to remove them individually and replace them w/the latest non-stubs, keeping 40 stubbed though as now I feel reassured w/your assistance.

QUOTE(jskyboo @ Aug 14 2011, 02:01 PM)

I like the idea of a csv quick viewer, I'll see about getting that in the next version. As for the simple text it does make loading info back from csv next run a little tricky. What would you like the simple out to look like? I'll think about it.

Hey thanks for the feedback I'm glad you like the idea I'm not sure what it takes and I don't know much about csv but however you see fit to make it happen is obviously best. I said simple text because I thought it's easy and low on resource like notepad or something lol. Whichever way you know of or think of to view the file then excellent. I was just saying it would be awesome to have the option to take a look at the output csv whenever you want by choosing to "view last Check IOS's run" or "View output CSV" under the Check IOS's options menu. Hmm and what the output should look like?... good question, sorry I'm not too creative lol I would just take examples from any outputs you might like that other IOS check programs use and modify it a little right?

On that note I'm glad you're not discouraged by the bugs you hear about and I really appreciate your work. Have a great and productive week bro. Laterz

 

[jskyboo]

Special Delivery!!! Ok so I looked into the usb issues people have been reporting and unfortunately they are being caused by the new Set AHBPROT patch, the one that lets us keep AHBPROT after a IOS reload. And for those of you that followed the thread on this patch tueidj's patch had the same behavior. So that means right now those two features cannot coexist. And since there can be only one I made a new option so you can choose. So by default Set AHBPROT is enabled and so usb doesn't work but if you set DisableSetAHBPROT=1 in the settings you can fix usb but you cannot pass AHBPROT on without a patched IOS. So now that's out of the way, new things, batch installs now give a summary of errors, at the suggestion of MassiveRican I've added a csv quick viewer. I tweaked the wiimote controls so let me know what you think. Also various bug fixes some other goodies here and there(skipping cboot252, switch to priiloader) as well so here is Wii Mod v2.9.

Download:http://www.mediafire.com/?xpv73jih82adc5q

Changelog since 2.8 :

Fixed Wad manager crashing on install failures
Batch wad installs now give a summary of errors they had
When wad dump fails it now skips the rest of the contents
Changed any title manager menus so its not easy to accidentally delete something
Tweaked wiimote controls
The new setAHBPROT patch causes usb to fail so added an option DisableSetAHBPROT to fix usb
Added a csv output quick viewer

 

[JoostinOnline]

Sweet update! Thanks man, especially for the cBoot252 support.

 

[tueidj]

The patch that I called an unsafe dirty hack has unintended side effects even though other people said it was perfectly fine? Gee, I didn't expect that.

 

[JoostinOnline]

The patch that I called an unsafe dirty hack has unintended side effects even though other people said it was perfectly fine? Gee, I didn't expect that.

Did you say what those side effects could be?

 

[tueidj]

Sure I did, because when you update code in memory and don't invalidate the CPU instruction cache the results are completely predictable.

 

[JoostinOnline]

Sure I did, because when you update code in memory and don't invalidate the CPU instruction cache the results are completely predictable.

I was actually being serious.

 

[burritoboy9984]

Special Delivery!!! Ok so I looked into the usb issues people have been reporting and unfortunately they are being caused by the new Set AHBPROT patch, the one that lets us keep AHBPROT after a IOS reload. And for those of you that followed the thread on this patch tueidj's patch had the same behavior. So that means right now those two features cannot coexist. And since there can be only one I made a new option so you can choose. So by default Set AHBPROT is enabled and so usb doesn't work but if you set DisableSetAHBPROT=1 in the settings you can fix usb but you cannot pass AHBPROT on without a patched IOS. So now that's out of the way, new things, batch installs now give a summary of errors, at the suggestion of MassiveRican I've added a csv quick viewer. I tweaked the wiimote controls so let me know what you think. Also various bug fixes some other goodies here and there(skipping cboot252, switch to priiloader) as well so here is Wii Mod v2.9.

Download:http://www.mediafire.com/?xpv73jih82adc5q

Changelog since 2.8 :

Fixed Wad manager crashing on install failures
Batch wad installs now give a summary of errors they had
When wad dump fails it now skips the rest of the contents
Changed any title manager menus so its not easy to accidentally delete something
Tweaked wiimote controls
The new setAHBPROT patch causes usb to fail so added an option DisableSetAHBPROT to fix usb
Added a csv output quick viewer

Thanks for the update!

-Erik

 

[jskyboo]

The patch that I called an unsafe dirty hack has unintended side effects even though other people said it was perfectly fine? Gee, I didn't expect that. Yep, that same hack. And I never said it was perfectly fine, I said it was useful and it still is. And expecting a patch to code we don't have the source to, to have unintended side effects is not all that prophetic. It's more in line with saying a flipped coin will land on one of it's two sides, while correct, it would have been more impressive to actually call it as heads or tails. So we are once again playing with a patch we do not fully understand. And it doesn't only do the task that we hoped it would, just like the ticket version check patch has some side effects. It would be nice if we had better patches, but that's not always the case and until we do sometimes we will dabble in the unknown. As for it being a dirty hack, yep your right, and yours is dirtier, that's why I'm still using davebaol's. Although I now am not relying on it to fix the HBC no net bug, I switched to the other idea you suggested changing ipcbufferLo and ipcbufferHi, thanks for the tip hopefully I did it right if not please let me know.

QUOTE(tueidj @ Aug 28 2011, 07:41 PM) Sure I did, because when you update code in memory and don't invalidate the CPU instruction cache the results are completely predictable.

If you are saying there is another way to get the same positive results without the negatives then please let me know.

 

[tueidj]

How is mine dirtier?

 

[jskyboo]

How is mine dirtier?

Well davebaol's patch is based on a conditional that switches on some data, and depending on which it calls a method with a different value for the parameter. Davebaol's patch makes it so no matter what the data the same value is passed to the method. Yours is similar(from set AHBPROT perspective) but does it slightly different in that it changes the data the conditional is switching on. So davebaol's patch changes the outcome of that one conditional, yours has other effects, like to DVD video and possibly other things. When looking at it like that, yours would be expected to have more side effects. As it is set_ahbprot(1) alone has these effects on usb so both patches share that aspect, but yours might be doing a lot more, some good too like with DVD video, but also possibly more we don't know. And if I had a use for the DVD video patch who knows maybe I would be using it, but as it is I do not and so I'm using davebaol's.

 

[tueidj]

If the input data to a condition is constant, it's no longer a condition - it's a branch. Both patches modify only a single instruction (2 bytes). If either method is going to have "side effects" that is where they are going to happen, not during the set_ahbprot() or set_dvdvideo() calls.
My original comment in this thread was obviously not directed at you, since (as you pointed out) you never said the patch was perfectly fine:

it's still a 100% safe solution

Let's say it's 99.99% safe.QUOTE(davebaol @ Aug 20 2011, 11:53 AM)

I'm still waiting for a real failure report.

 

[jskyboo]

If the input data to a condition is constant, it's no longer a condition - it's a branch. Both patches modify only a single instruction (2 bytes).Ah, but which single instruction is what matters. Like I said his changed what is passed to a method, yours changed data which caused conditionals to yes no longer be conditionals but branches because they are constant, but were just talking semantics there. What's important is davebaol changed the path of one conditional at most, yours many more and since I don't know how to decompile the sm I don't have a clue if the data you changed has other effects.

If either method is going to have "side effects" that is where they are going to happen, not during the set_ahbprot() or set_dvdvideo() calls.That is one place but it also could have side effects simply because we are calling methods we do not fully understand when the system is in a state we do not fully know. So even if we did understand the methods pretty precisely running them during an unknown state is going to end in an unknown state.

QUOTE(tueidj @ Aug 29 2011, 07:16 PM)

My original comment in this thread was obviously not directed at you, since (as you pointed out) you never said the patch was perfectly fine

Fair enough, there were those who boasted a little too much.

 

[kylster]

Thanks for the update

are you adding any new features you need testing out?

P.S.
I think the blue strip up top was way cooler ^^

EDIT: Is there a way to do an offline install for a custom system menu?
When I goto System Menu
Set version# and IOS required; it will grab the IOS from the root of my sd card or download it from online but it never does this with the System Menu. It seem to always download it. So does it need to be renamed? cause the system menu.wad I have is the same one I DL off ModMii.

Thanks in advance.

EDIT2: Sad to say this is only possible after it has been dumped. I'm going to try a lower IOS maybe IOS 1; not sure atm cause i'm currently dumping my nand. Will post back but I dont see it being any different then what I already have it.

EDIT3: There is no IOS1/2 but there is an IOS3 which http://wiibrew.org/wiki/IOS_History labels it as a non-functional IOS so this is my starting point since WiiMod

For some reason the Wii does not like to install this IOS 3 hm... it only shows up in WiiMod under Option Change IOS but not under IOS. Still I managed to get it installed by changing to IOS236; however this is not a working case as even some Wad installs for a System Menu give me Ret=unknown error. hm... yet if I exit out and go back in I can usually successfully install another System Menu from Wad.

My point is this IOS3 is not even being used and if it can be functional as a Custom System Menu slot this would be great as it's not detected by homebrew apps as a STUB or anything else for that matter.

Under Wii System Information; SM4.1U running off IOS123 shows System Menu v4.1a IOS123; while SM4.1U running off IOS3 shows System Menu v4.1X IOS123.

 

[jskyboo]

Thanks for the update

are you adding any new features you need testing out?

P.S.
I think the blue strip up top was way cooler ^^

EDIT: Is there a way to do an offline install for a custom system menu?
When I goto System Menu
Set version# and IOS required; it will grab the IOS from the root of my sd card or download it from online but it never does this with the System Menu. It seem to always download it. So does it need to be renamed? cause the system menu.wad I have is the same one I DL off ModMii.

Thanks in advance.

EDIT2: Sad to say this is only possible after it has been dumped. I'm going to try a lower IOS maybe IOS 1; not sure atm cause i'm currently dumping my nand. Will post back but I dont see it being any different then what I already have it.

EDIT3: There is no IOS1/2 but there is an IOS3 which http://wiibrew.org/wiki/IOS_History labels it as a non-functional IOS so this is my starting point since WiiMod

For some reason the Wii does not like to install this IOS 3 hm... it only shows up in WiiMod under Option Change IOS but not under IOS. Still I managed to get it installed by changing to IOS236; however this is not a working case as even some Wad installs for a System Menu give me Ret=unknown error. hm... yet if I exit out and go back in I can usually successfully install another System Menu from Wad.

My point is this IOS3 is not even being used and if it can be functional as a Custom System Menu slot this would be great as it's not detected by homebrew apps as a STUB or anything else for that matter.

Under Wii System Information; SM4.1U running off IOS123 shows System Menu v4.1a IOS123; while SM4.1U running off IOS3 shows System Menu v4.1X IOS123.

Yes that is correct right now you cannot install a modified system menu from a clean wad but I'll add that in. You cannot use IOS 1 or 2 because those numbers are reserved(not used for IOSs), technically the System Menu is "IOS 2". As for IOS 3 not showing up in the IOS menu, yep that's a glitch, I'll fix it in the next release. There is also glitch in installing a custom system menu that uses IOS 3 I'll see about having that fixed in the next release as well. It is a little tricky but I'll see what I can do about it. As for the results you are seeing for the region with system menu 4.1 Joostin has notified me about that already and I will have a fix for that as well in the next release(that's what I get for doing my testing with 4.3 I guess, also the strip not being blue is related to this as well so it will go back to blue in the next version

). As for recognizing IOS 3 rev 65280 as a stub, well I have never actually come across that IOS. It's not on nus, but if you have seen it and are sure it is official, dump the hash and I can add it.

 

[kylster]

Spoiler

Thanks for the update

are you adding any new features you need testing out?

P.S.
I think the blue strip up top was way cooler ^^

EDIT: Is there a way to do an offline install for a custom system menu?
When I goto System Menu
Set version# and IOS required; it will grab the IOS from the root of my sd card or download it from online but it never does this with the System Menu. It seem to always download it. So does it need to be renamed? cause the system menu.wad I have is the same one I DL off ModMii.

Thanks in advance.

EDIT2: Sad to say this is only possible after it has been dumped. I'm going to try a lower IOS maybe IOS 1; not sure atm cause i'm currently dumping my nand. Will post back but I dont see it being any different then what I already have it.

EDIT3: There is no IOS1/2 but there is an IOS3 which http://wiibrew.org/wiki/IOS_History labels it as a non-functional IOS so this is my starting point since WiiMod

For some reason the Wii does not like to install this IOS 3 hm... it only shows up in WiiMod under Option Change IOS but not under IOS. Still I managed to get it installed by changing to IOS236; however this is not a working case as even some Wad installs for a System Menu give me Ret=unknown error. hm... yet if I exit out and go back in I can usually successfully install another System Menu from Wad.

My point is this IOS3 is not even being used and if it can be functional as a Custom System Menu slot this would be great as it's not detected by homebrew apps as a STUB or anything else for that matter.

Under Wii System Information; SM4.1U running off IOS123 shows System Menu v4.1a IOS123; while SM4.1U running off IOS3 shows System Menu v4.1X IOS123.

Yes that is correct right now you cannot install a modified system menu from a clean wad but I'll add that in. You cannot use IOS 1 or 2 because those numbers are reserved(not used for IOSs), technically the System Menu is "IOS 2". As for IOS 3 not showing up in the IOS menu, yep that's a glitch, I'll fix it in the next release. There is also glitch in installing a custom system menu that uses IOS 3 I'll see about having that fixed in the next release as well. It is a little tricky but I'll see what I can do about it. As for the results you are seeing for the region with system menu 4.1 Joostin has notified me about that already and I will have a fix for that as well in the next release(that's what I get for doing my testing with 4.3 I guess, also the strip not being blue is related to this as well so it will go back to blue in the next version

). As for recognizing IOS 3 rev 65280 as a stub, well I have never actually come across that IOS. It's not on nus, but if you have seen it and are sure it is official, dump the hash and I can add it.

Thanks for the info about IOS1+2; I was not aware. I currently do not have an IOS3 on my Wii; I was looking for lower IOS that I could install my Custom SM to (so far I've been using IOS123) but considering how it is ill-advised to delete any IOS below 200 or even 100 since it's unsurpassed I was hoping; no matter how grim it may look and having bootmii/boot2 only makes me feel more at ease.

I do have an IOS0 but not an official IOS3 and I'll even post a pic for you to see; I have been doing a lot of reading about IOS lately and found IOS0 to be somewhat rare or exclusive.

Spoiler

You mentioned dumping the hash; it's time for a noob question, how do I do that? seriously... I have a bootmii nand dump; could I just as easily extract it from there and let you look at the said wad or a full bootmii dump?

I will try re-installing some my IOS236 cause sometimes it worked and sometimes it didnt but it does make me feel a little better knowing that there is a glitch in installing IOS3 with a Custom SM. I can get it installed just have to play with it at times; what worried me was after getting IOS3 installed and Custom SM to go with it, when I tried to re-install IOS123 (this would install with no problem) and the Custom SM (this would always ret=unkown error) it failed at the end and 1 time even froze. Still if it's a glitch I'm not worried but would you say since I managed to get IOS3 installed along with a Custom SM to go with it that the Wii should act ok?

I should also mention that the reason I'm even remotely curios in a very low IOS being used with a Custom SM is a few months back when I read up on SM-X; the idea is just brilliant. If the an IOS like this was used for this particular purpose it would be kind of noob proof once the procedure was completed and most people wont even mess with an IOS that low anyways.

Well jskyboo, thanks for the info and advice. I'll keep it in mind; just let me know if you want to check into IOS0.

Here is a sysCheck of my Wii using sysCheck v2.1.0b13 < http://www.mediafire.com/?ym70hf052dtqm

IOS0 does not show up in ShowMiiWads nor is it able to be extracted??? Confusion.

 

[JoostinOnline]

Just use IOS60v65535. It won't be overwritten.

 

[kylster]

Simplicity yes, but I'm looking for something under the radar. I'm still curious about IOS0.