They only belong in subdirectories if you're not using tueidj's loader. But be warned: no support if you don't use his loader. So when reporting bugs, make sure it happens in his loader.

I asked because, in terms of security, it is not a good idea to have such information being sent out on the network. If network logging is to be used, I would prefer if it were restricted to only the standalone Devolution loader and used solely for debugging purposes.It won't automatically work with other loaders, they have to add support for it I believe. But other loaders will be able to use it if they implement the code.Is network logging only enabled with the standalone Devolution loader or does it log to the network when using other USB loaders as well?
I am also having this problem (official memory cards) but I was able to get around it like this.Thanks for the new build Tueidj!
Unfortunately,the MC bug still exists...
Try the same tests as before, see if it mentions anything about writing to SRAM. You should be able to test with slot A now though (using gecko for logging) provided the card is inserted when you boot the loader.Thanks for the new build. Should I check for any changes in the official memory card situation?
Try the same tests as before, see if it mentions anything about writing to SRAM. You should be able to test with slot A now though (using gecko for logging) provided the card is inserted when you boot the loader.Thanks for the new build. Should I check for any changes in the official memory card situation?



