Well...that....makes me cry.With the 2011 early Intels I've decided to keep, this is how they're set:
iMac: Sonoma, via OCLP.
Early MBP: Catalina. It will not run any other macOS, so I'll be here asking how best to set this up.
Late MBP: MX Linux. This one will also only run Catalina, but no sense in two, so it gets MX, and it runs it beautifully.
Everything else gotta go!
Huh? (I have almost non-existent memory-retention for acronyms, especially short ones that could be anything.)Why they didn't made it for SL... ?![]()
If it were possible to run other versions, I would do it. It just so happens that patched Catalina is all that works. Both machines are also fairly limited in the Linuxes they will run. So basically, one runs the only viable macOS, the other runs the Linux that they are happiest with. Both have broken AMD Graphics.Well...that....makes me cry.
No Peggle Nights or Angry Birds for your kids (or, frankly, anything nice, since Apple murdered everything nice about Macs with Catalina in its deal-with-the-devil that everyone seems to be cheerfully embracing as if nothing is amiss).
Thanks, i have that installed, the realized my macbook pro's
Also, @Minghold , I read that article. Not nice. Yet another reason to switch *everything* to Linux...
TL;DR
- No, macOS does not send Apple a hash of your apps each time you run them.
- You should be aware that macOS might transmit some opaque3 information about the developer certificate of the apps you run. This information is sent out in clear text on your network.
- You shouldn’t probably block ocsp.apple.com with Little Snitch or in your hosts file.
Well...that....makes me cry.
No Peggle Nights or Angry Birds for your kids (or, frankly, anything nice, since Apple murdered everything nice about Macs with Catalina in its deal-with-the-devil that everyone seems to be cheerfully embracing as if nothing is amiss).
Also, @Minghold , I read that article. Not nice. Yet another reason to switch *everything* to Linux...
That blog was refuted years ago in several places, including discussions within this very forum but misinformation travels to every corner of the world whilst the truth lags behind.
yes, i feel like a blind (ooops visually impaired) personSometimes here I feel like a member of Bilbo's company from The Hobbit, caught in a thunderstorm on the Misty Mountains while the stone giants battle each other (apropos I suppose, given my avatar's character was there).
I kind of understand the excitement. Going from a 2020 Intel MacBook Pro to even an M1 like I did was a night and day difference in terms of performance and efficiency. Even a few years on I am constantly impressed by how good my ARM Macs are.yes, i feel like a blind (ooops visually impaired) person
explaining a recent traffic accident to a police officer
when i defend the recent greatness of my MBP 2012 on these "M silicon...or else!" forums.
the police officer will never take my statement seriously.
I know exactly what's going on, and how to solve it: These machines have busted hardward-acceleration, but the OS doesn't know that. So, whatever OCLP trick you used with Catalina on a 2011 will also work with Mojave (I know, because I've done it recently on a few iMacs with the same problem). With Mojave, you build in into an HFS+ partition (also getting 32bit app support back) and clone it to an external master, so you can then boot and clone it onto any similar machines with that problem in the future. (Probably it also works with High Sierra, but never got around to it.)If it were possible to run other versions, I would do it. It just so happens that patched Catalina is all that works. Both machines are also fairly limited in the Linuxes they will run. So basically, one runs the only viable macOS, the other runs the Linux that they are happiest with. Both have broken AMD Graphics
Given the rapid extinction of the very concept of privacy everywhere there is electricity these days, whatever was mangled "years ago" is tomorrow's (if not today's) predictive-programming reality.That blog was refuted years ago in several places, including discussions within this very forum but misinformation travels to every corner of the world whilst the truth lags behind.
"...Personally, I wouldn’t suggest doing that as it prevents an important security feature from working...."
These kinds of statements are calorie-free without the specs of the machines in question. For example, if you had a "consumer-grade" 2020MBP 13", you got a 2ghz i5 running Catalina (boo!). Yeah, the M1 is faster. But so is an i9 (which has been maintaining benchmark parity, if not occasional leads, over same-year Apple silicon).I kind of understand the excitement. Going from a 2020 Intel MacBook Pro to even an M1 like I did was a night and day
For one of the most failure-prone Mac in history?It doesn’t, no, but $200 is a fantastic bargain!
I went from the mid-range 10th gen quad core i5 to the base M1, both with 16GB of ram. I know that the high end Intel CPUs are keeping up in benchmarks but it’s the combination of performance and efficiency that is truly remarkable with the Mx chips. My M1 never goes above 50C under load whereas my Intel machine with the same chassis would be pegged at over 100C with similar tasks (e.g. remote teaching with concurrent recording or rendering graphics for scientific publications). This is getting off topic for this thread though. As mentioned I still regularly use my Core 2 Duo MacBook for different tasks and it still does well given its age.These kinds of statements are calorie-free without the specs of the machines in question. For example, if you had a "consumer-grade" 2020MBP 13", you got a 2ghz i5 running Catalina (boo!). Yeah, the M1 is faster. But so is an i9 (which has been maintaining benchmark parity, if not occasional leads, over same-year Apple silicon).
Hold on while I grab some Apple "longevity"-pumpers and strap them to chairs with their eyelids taped open.For one of the most failure-prone Mac in history?
Of course your intel machine is going to run like crap with Catalina+ (to say nothing of you-are-an-unpaid-betatester Sonoma) -- Apple designed its post-Mojae OSes to run like dogshat on intel for perfectly obvious reasons (and to add insult, killed off 32bit to drive everyone onto the bloated-sows subscription-model accelerating automatic-"update" artificial-obsolescence merrygoround). Fortunately, 98% of intel Macs don't have to run Apple's recent OSes.I went from the mid-range 10th gen quad core i5 to the base M1, both with 16GB of ram. I know that the high end Intel CPUs are keeping up in benchmarks but it’s the combination of performance and efficiency that is truly remarkable with the Mx chips. My M1 never goes above 50C under load whereas my Intel machine with the same chassis would be pegged at over 100C with similar tasks (e.g. remote teaching with concurrent recording or rendering graphics for scientific publications).
That poor MacBook is longing for microchip heaven, where it'll finally get to play Peggle Nights again (which ran on eleven successive versions of the OS from Tiger to Mojave, and still is arguably the best puzzle game ever made).This is getting off topic for this thread though. As mentioned I still regularly use my Core 2 Duo MacBook for different tasks and it still does well given its age.
Had it done so before?Kinda weird experience with my MacBook Air 2010 would not read or accept
the Snow Leopard usb drive while restarting in option mode.
1. Restart while holding down Command-Option-P-R through three successive chimes, then....even their Internets option wanted Lion instead of the orig OSX Snow Leopard
Therefore, I need to make a snow leopard time machine from a 64GB then install that on a 128GB.
so much for that joyous Snow Leopard start up video and a clean install.
Kinda weird experience with my MacBook Air 2010 would not read or accept
the Snow Leopard usb drive while restarting in option mode.
even their Internets option wanted Lion instead of the orig OSX Snow Leopard
Had it done so before?
1. Restart while holding down Command-Option-P-R through three successive chimes, then....
2. Hold down option and boot into a Recovery partition (on the internal drive or external drive). If this doesn't work, hold down Command-R, and boot into it that way (requires a wireless connection). Take note if you're still on Lion minimum.
3. In the Recovery screen, select language (if it bugs you about that), then open Utilities > Startup Security, and turn it OFF if it is on (requires a paassword). Then close that and go to Utilities > Terminal. Enter "csrutil disable" (without quotes) and hit return.
4. Close Terminal and open Disk Utility. Repair-scan the Snow Leopard USB for errors. While you're in Disk Utility, observe whether or not the internal drive is formatted to MacOS Extended or to APFS (it's possible that you won't be able to do this depending on the version of your Recovery partition).
For one of the most failure-prone Mac in history?
<nod> This is why bootable backups (courtesy of CCC) are king and why TM is worthless. IIRC, Snow Leopard went to 10.6.8, so if you've a backup of that, you're covered.Good advice and it certainly can't hurt to try this but I strongly suspect that @MBAir2010's difficulties stem from trying to install 10.6/10.6.3 when the the 2010 C2D MBA requires 10.6.4.