Why do you need to initialise the CIOS before showing the menu anyway?
It seems to be starting up alot slower than before & the console output is annoying.
Initialising SD & WBFS when I'm not using them seems pointless.
Actually, we do initiliaze them when showing the menu. That is the whole point of starting up. USB GX is designed to be an USB Loader which is able to run games from USB. Therefor, it's first thing is to access the drive, and search for games. So we added the check right before.
Btw, about the slower load time. It seems that way, because you saw console output now. Reloading into 36 and 236 doesn't cost a thing. Checking costs something, but the longest reload is into 222. And the fact that we show console output now, and the menu a bit later, makes it "look" longer. Anyway, the console output will only visible when booting from HBC.
smf said:
Putting the CIOS to use in the config would be good, you should be able to read the config using a standard IOS.
Not true. A lot of harddrives are not supported by libogc, while they are by using a cios. We would drop support for those drives. Making an exception for such drives is useless and a waste of our time, since we can make it generic. The cost is a few milliseconds, over which this discussing goes.
QUOTE(smf @ Dec 9 2009, 09:19 AM) Relying on 236 is only good until Nintendo stubs that. If Nintendo stubs everything then you're back at square one.
It doesn't rely on it, it just checks the options. Btw, stubbing also goes for 222, 223, 249 and 250, so that's not a valid argument imo.
QUOTE(smf @ Dec 9 2009, 09:19 AM)