Not sure at present, built a new libogc with the extended timeout which went OK, built a modded cIOS which was mostly OK, then trying to build usbloadergx was a complete pain in the ass - it requires a zip library, who knows what zip library or where to get it so I just ripped it out, the libcustomfat is incompatible so needs recompiling and that uses 'st_spare' fields that don't exist so they needed removing, then there's various other issues so I just commented the code out rather that bothered to look into it (an amusing one was using the same declared arrays as libogc had which would then fail to link). So since I don't have the time/space to get devkitPPC I was wondering if someone here already had it and if so could try making a build of libogc with the timeout set to 16 seconds instead of 2, then building usbloadergx with the new libogc build and uploading it to see if my theory is correct or not.
What's interesting is that in libogc in the usb storage file is a hard-coded 2 second timeout, line 88, and I think the issue is that due to the controller being busy (it actually has ECC inbuilt and other features so I think it takes much longer to successfully read a block, especially given the high nature of bad blocks on NAND memory vs hdds) and as a result libogc times out which then times out usbloadergx/nintendont. It sits at 0 for a bit (between 4-12 seconds) then starts going up again and this continues until the copy has finished. Now before you say 'use a hdd not a usb' the one thing I've noticed with this specific flash drive is how the controller (at least from a desktop PC) seems to be masking up how damn slow the NAND flash actually is - if you copy a large file it will say it's transferred at 28MBps (this is nonsense), it then goes down to 20, then 10, then 0.
lauching titles goes to the homebrew channel, nintendont get's errors about being unable to read disc headers. I feel like small dev and small project will not be seen anymore, it's making things complicated to learn and understand for new comers.I've been observing issues with using USB drives on the wii, I have a 16GB one with a phison controller which works flawlessly but a 128GB one with an actel controller works when there's not much on the drive but once you add so much it just entirely fails to function properly, e.g.
it's too complicated to comply with updates and evolution when you don't have enough time and it's just a hobby, not your full time work.
It worked fine, now it doesn't work at all, and nobody seems to care to fix it or update it, even though it's open source. Or maybe it's possible, but require a full rethink and rewrite of the addon over new API, etc. all firefox ended dropping addon if not done the way they want, and mine just can't do it, I have to edit the interface which is now forbidden, I have to use workaround communication between two asynchronous sandboxed processes when I could just set a sync private variable before, my addon doesn't work async at all and I would need to freeze all processes until a variable is transmitted. Obsolescence and forced coding style is why I couldn't maintain my firefox addon. Talking about ECMA? (or is emca a thing?)