You must have known about this, but in case other people didn't know, I found the following links very useful:requiem4d said:QUOTE said:I compared your code with wiigator's side by side, but couldn't figure out where the problem lies. I also made a few changes I thought might help, but they didn't work. The only way to debug this I can think of, is to replace every piece of your code with wiigator's, until we locate the bug. It must be a very tiny one that we overlooked.
Feel free do to that, at least to figure out where the problem lies. However, that isn't the proper solution to this issue. While a lot of the calls may be similar (they really have to be) to WiiGator's, this is not based on his loader. I thought of using his code as a base, but decided against it to keep from having to sort through tons of "original application" code. Most of the information used in construction of this loader came from the dip module, wiibrew, information gathered by examining the structure of a Wii disc, and old-fashioned trial and error.
In order to truly have a "fix", we need to analyze the apploader further to figure out what I'm doing wrong.
I know this information has already been reversed, but other than the apploader by marcan, bushing, and others, I don't have a very reliable reference on how this particular part works beyond loading the apploader into memory, setting a pointer to a function, and retrieving function pointers needed to load the system file sections, boot, fst, bi2, and main.dol.
It's times like these I wish I knew a little more about the console.
http://dolwin.emulation64.com/docs/Apploader.txt
http://gbatemp.net/index.php?showtopic=98663
I didn't find anything special that you were doing differently from wiigator. I'm confused why you have a bug