r-win said:Then submit a patch, it's open source.
I've no problem with that, apart from time as I said (christmas and all that, I'm sure you know the problem). Once I've hooked up the USB Gecko to windows 7, I might be more inclinded to fix the crashes I'm getting as well.
As an outsider it's hard to know whether you're wasting your time by submitting patches as for all I know someone is completely rewriting the part that I'd want to change. Which is why I thought I'd mention it first.
And last thought: I don't like the way these discussions are going. Having a constructive thread is more useful than flaming.r-win said:Edit: Now that I think about loading the config from the boot device, I think we already do that. We might as well add some small checks there, so that only for people without a config file, the checks are done. We could also check if the drive works with default libogc, and TRY to load the config file, before running the checks. This will only execute these checks the first time for most people, and always for people with an incompatible drive.
In the case of an incompatible drive, I assume they can't have booted from the drive (or can it be compatible with the forwarder/hbc and not with libogc?).
So they are probably running from an SD card, and the config ( at least which IOS to use ) can be stored there. If they are running from nand then it's trickier, a game save maybe?
r-win said:I also still think that using cios 236 is NOT a bad idea. People who softmod their wii and use a newer guide, will have 236 installed, instead of a patched 36. Maybe we *could* inverse the check, first use 36, if that fails, use 236.
Anyone following those guides is going to have CIOS 249 as well. It's only people that don't follow the guides or have just upgraded without removing the stubs that could ever benefit.
If Nintendo look at the guides and see that 236 is being installed, then you're going to be back at square one.
QUOTE(r-win @ Dec 10 2009, 12:59 PM)
yes, I don't have a problem with that.