u bastard!
edit: that was @ joostin
edit2: @mauifrog, Etheboss had the same problem, but before using his fix, can u test something for me. I think the problem can be fixed in a batch file, and thus can be added to modmii as a precautionary measure for ppl in your situation
save this code into a new text file, then rename it from *.txt to whatever.bat, then just run it (don't run as administrator, it shouldn't be required and I want it tested with normal rights first)
Code:
set PATH=%homedrive%\windows\system32;%PATH%
and that's it, so try using ModMii to build the problematic cIOSs again. If this works, let me know and I'll add that code to ModMii so it will set the environmental variable for everyone just in case they might be vulnerable to the same problem as u.
if it doesn't work, try what Etheboss did to fix the same problem
HERE, basically the same thing as what I said above except using cmd line
edit3: why are so many smart people actually installing WADs that ModMii is calling "invalid"?? The ret -1022 info is helpful, but still, if ModMii says its invalid, I wouldn't install it
edit4: typical mauifrog behaviour, since I posted this solution he's helped 3 other ppl before helping himself. What a good guy, so selfless... or maybe I should bump this thread to make sure he's actually seen these edits, lol
edit5: reason for edit-->changed comma to semi-colon