There were plenty of hacks that allowed you to circumvent this. Once you get some form of code execution on the Xbox, it's over, everything runs in Ring 0, meaning you get full access. You can use exploitable executables to maintain persistence without having to do any hardware modifications. However, all these methods relied on an initial entry through either:
A. Installing new hardware (a modchip) to run an altered version of the Microsoft Xbox kernel that doesn't perform the usual checks.
B. Transferring an altered save game to the Xbox through the memory card (internally it's just a USB drive), running the game and loading the save, which triggers an exploit
C. Booting the console (which unlocks the hard drive), waiting until the hard drive activity ceases, "hotswapping" the IDE cable to your computer, modifying the files, swapping it back and turning the console off so the drive locks again. (If the hard drive loses power, it locks itself again too, hence why the hotswap-which is not supported by the PATA standard obviously-is needed)
Now, with this, there is no more reliance on bespoke modchip hardware, aging vulnerable game discs or machines that you can still hotswap an IDE drive to. Which means that Xbox modding has gotten more reliable for the coming years. Which is good news in my book.
I felt like a warlock when I could rip my games after that.
Great memories.
And my mate at school saying there is no such thing as a soft mod! Haha
So I suppose for the users affected their connection is slower than pulling off the disc.
As well as my intel apps. Was pretty smooth and the speed and power efficiency gains are obvious. My mac book air draws about 5w total while the DAW is cool as a cucumber.
I have a feeling that "solutions" like this are part of why an increasing number of my computing problems take the form of, "I tried to take an action, nothing happened. No error, no activity, nothing.", and are impossible to debug or diagnose. UX designers made themselves terrified of ever showing an error code to a user, but they took that and replaced it with a world where your shit just doesn't work, and when you try to figure out why, all the OS does is shrug.
Now when something goes wrong the system just kinda gets lazy and stops working. But it won’t crash.
I’ve had my mac pinwheel on the login screen. I can still access the shell and file shares remotely, and even screen share to a logged in user.
But login.app refuses to crash so it’ll just pinwheel.
I’m glad I never forgot to turn things off and on for troubleshooting :(
Autosave also has versioning. You can always go back through the auto save history. You can also revert to the original opened file. This is done from the file menu.
Also, if like a good mac user you have Time Machine configured and on, you can browse your versions further into the past.
Heavy iWork user, I don’t know about Xcode though.
[0] https://www.facebook.com/watch/?v=766810966790684 (This seems to be the only place to find it online).