Reposting as top level comment also: these are PWDIS drives: if you’re not using them somewhere with sata 3.2/3.3, you need to use an adapter for the power plug, or some tape, to block pins 1-3 (3.3v) as supplying it to these causes them to reset. Might be worth doing the taping anyway, if you’re using an enclosure or cage (where you can’t use the adapters) Just be aware.
2nd catch, behind the power on time: PWDIS drives: if you’re not using them somewhere with sata 3.2/3.3, you need to use an adapter for the power plug, or some tape, to block pins 1-3 (3.3v) as supplying it to these causes them to reset. Might be worth doing the taping anyway, if you’re using an enclosure or cage (where you can’t use the adapters)
Nintendo went after a emu dev team that was actively (and demonstratively) enabling piracy for something they are currently selling. On top of that, the dev team is making significant money off of that work, to the tune of 30k/mo. Every other dev is probably thinking “finally, the other shoe drops on this obvious outcome”, most avoid making money off it, and also avoid current systems, both for just this reason. The relieving part is Nintendo’s argument isn’t about the emulator specifically, there’s nothing in the injunction stopping yuzu from continuing, and a settlement means no legal precedent.
Edit: Read more, the settlement includes stopping development.
I mean, small developers who set up a money-making pateron based on an emulator for a currently sold system, without providing a way to pull your own system info or games from carts (and is therefore heavily reliant on piracy of things currently being sold by the parent company to run) is basically screwed, but this isn’t news, and pretty much every other emu dev would run away screaming from such a setup.
They really put themselves in this boat, but since that money-making pateron is a thing, they’re probably wiping those tears with dollar bills.
AFAIK materialize.is is still active, but you need an invite, and I am not “in”, as it were, though I would like to be.
If I’m reading this right, 80_PA is a keygen, and does not need to run on the target system. If it did, how would an android version be useful?
Install it elsewhere and follow its instructions.
Otherwise, if you’re stuck with this as your only system (do you even phone?), it’s VM time.
Ah, you are correct… then yes, sata to mobo, with something to secure that cable very well.
1.) Yes, SATA to eSATA will work.
2.) It is not worth it, for stability. Having a cable from mobo to something outside case is unsafe at minimum.
I would go with the other recommendation: get a cheap pci sata/esata card. Cost is small, safety and reliability goes way up, no more kludge adapter going to inside of case.
For Android: learn the hard reset combo for your phone, especially if you encrypt it.
After rebooting, pattern/PIN will be required to decrypt the phone. Biometrics won’t work for this step. This is what graphene does for security, tries to keep the phone in a “before first unlock” state by rebooting on a timer. You can’t even read anything over USB/ADB, it’s scrambled until you unlock the phone.
The only drawback to just keeping your phone in this state is none of your apps are loaded, so no notifications/updates/processing at all.