My guess still is that Gbalpha team (M3 G6..) have contracted the R4 team. But the R4 team releases the loader for their product first and then they release the modified loader for the M3 simplyso wait, the R4 and M3 team are workin on such things, or how does it work?
Like someone else said, it would either unnecessarily re-patch, or detect the need for no patching. Either would work fine. This is how DS-Xtreme has always done it (since before DLDI actually, when it just patched the relevant parts of the embedded libfat drivers). The DS-X method doesn't work when an application is loading another application though (Moonshell?), so in that case you need to patch manually; also, some applications will inspect themselves (ScummVM) and find out they're really unpatched and so need manual patching anyway.I wonder what will happen if you update and then run a program that was already DLDI patched on the new loader. Would it whack out?
If they really fix the Download Play feature, there's no reason IMO to buy a CycloDS Evolution.
The DLDI auto-patching thingy is for really lazy peopleI mean..it can be done with 2 clicks![]()
