QUOTE said:As i understood Waninkoko's CIOS-36-rev06 and WiiGator's 0.3 cIOS use the same dip module.
You would be correct. However, the concern isn't current cIOS compatibility, it's future cIOS compatibility. In cases where the SD card is unavailable, or the config file is missing or incorrect, it will default to IOS 249 to use Waninkoko's cIOS. While currently it will work with either (since the dip module is the same) we don't know that this will always be the case.
Yeah but then it removes all the extras, like region setting, ocarina, etc. Since the release I've been playing alot of PAL versions for compatibility reasons.QUOTE said:I thought some of the old games require an older IOS than IOS36 and that's why they aren't working. I think Waninkoko or WiiGator (or both?) said that.
Again, correct. We can't achieve complete 100% compatibility just yet, but the aim is to get as close to that mark as we can.
QUOTE said:Just a few thoughts about a final version: Many people(myself included) think a perfect version of a backup launcher would use the disc channel(if possible) or a backup launcher channel.
I concur, but I can't comment on the specific development plans for this just yet. (Think patched by nintendo...)
QUOTEWhen i think of it, i see a problem nobody mentioned before. How to store the settings? Settings on a sd card are very comfortable, but to me a perfect loader would have full functionality without a sd card. Just install, make the settings you wish and just play.
Does anybody know how to create a "savegame" or whatever in the Wii's memory which could be used as config file?
Theoretically possible, but I don't want to go poking around in the NAND just yet. That would make the loader too dangerous to run due to the risk of a brick.
QUOTE
QUOTE said:I just think people demand too much here ...
No way. You don't understand the code at all and you're just wasting the time of all of us. You're a n00b who successfully convinced me in the first place and made me spending a lot of time trying to understand your "fix". The code you touched is just dead code.knowitall599 said:I've got good news. The first fix that I posted WORKED because of a memory error. Someone mentioned that it would not seem logical and would not work because we are not using gecko commands in the code. This is quite correct, but this person did not understand that the memory by these gecko functions IS used only by these gecko functions. So, I was thinking that it would be logical for there to be a memory bug in this area if the backup launcher functions were trying to access this part of memory. If I could figure out how the backup launcher functions worked and EXACTLY what they did then I could fix the error bug that some games produce. I hope this message has caught the attention of Wiigator if he is reading this he should know what I am talking about.
roy_hu said:No way. You don't understand the code at all and you're just wasting the time of all of us. You're a n00b who successfully convinced me in the first place and made me spending a lot of time trying to understand your "fix". The code you touched is just dead code.knowitall599 said:I've got good news. The first fix that I posted WORKED because of a memory error. Someone mentioned that it would not seem logical and would not work because we are not using gecko commands in the code. This is quite correct, but this person did not understand that the memory by these gecko functions IS used only by these gecko functions. So, I was thinking that it would be logical for there to be a memory bug in this area if the backup launcher functions were trying to access this part of memory. If I could figure out how the backup launcher functions worked and EXACTLY what they did then I could fix the error bug that some games produce. I hope this message has caught the attention of Wiigator if he is reading this he should know what I am talking about.
Because other people reported speedups. Later requiem4d told me that the speedups he experienced was only caused by the cios change he made. Since I have never hacked wii before, I thought you'd know something because you appeared to be able to read and modify the code. It turned out that you didn't understand the code.knowitall599 said:roy_hu said:No way. You don't understand the code at all and you're just wasting the time of all of us. You're a n00b who successfully convinced me in the first place and made me spending a lot of time trying to understand your "fix". The code you touched is just dead code.knowitall599 said:I've got good news. The first fix that I posted WORKED because of a memory error. Someone mentioned that it would not seem logical and would not work because we are not using gecko commands in the code. This is quite correct, but this person did not understand that the memory by these gecko functions IS used only by these gecko functions. So, I was thinking that it would be logical for there to be a memory bug in this area if the backup launcher functions were trying to access this part of memory. If I could figure out how the backup launcher functions worked and EXACTLY what they did then I could fix the error bug that some games produce. I hope this message has caught the attention of Wiigator if he is reading this he should know what I am talking about.
I don't know about that one. If I am sooo noobish then how exactly did I convince you in the first place?