Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I only updated the OCLP and applied patches to root and EFI. All seems to work fine. There has been some problems for Surfshark to connect to servers couple of times today but that can be unrelated.

Somebody noticed that the installer can get stuck and cause problems and solution was to boot in safe mode like Mike said above. There is already a video about it.
Aah, MrMachintosh was a nice tweeter friend and i miss his update posts!
but not twitterz,
 
Done! I've replaced MBA 11" Mid 2012 CPU again. Now it has a quad-core i7 3612QE with lower TDP. Also RAM had been updated to 16 GB with @dosdude1 video guide and I've even changed UEFI to support PCIe 3.0 so the NVMe speed had doubled!

Now this is a nice small performance machine! Geekbench score is even higher than with 2.3 GHz CPU as long as new processor is not throttling.

Oh, almost forgot. I've also upgraded AirPort module so now I can use Universal Control with my iPad mini.
Wow! How on Earth did you manage to replace the CPU? Isn't it soldered in? Did you perform a surgery?
 
Wow! How on Earth did you manage to replace the CPU? Isn't it soldered in? Did you perform a surgery?
Yes, it soldered. See the dosdude1 videos for more details. You need to resolder both the CPU and RAM for the upgrade. TBH I didn't make it myself - I've payed a guy who can do the mechanical work. While I did all software stuff with UEFITool.
 
Well my great macbook air 2010 will stay on Mountain lion and everyday i will watch either an episode of benny hill or Addams family videos because i can get that to play on an hdmi tv and bluetooth speaker.

nothing else i can really do beside improve art work using cs4.
 
Using that b-b-base A1224 iMac I mentioned in another recent thread, I set up a needlessly complicated sound studio, in which two computers — the A1224 and my A1278, both running Snow Leopard — a lot of audio cables, Audio Hijack, LineIn and Noisy were all wrangled into the creation of replicating an FM analogue broadcast, broadcast compression included, for a test DJing set (using my old, cheap, but extremely reliable USB DJing console made by Behringer).

Setting it up as I’d envisioned ended up being more of a technical challenge than I thought it would be, but I just managed to churn out hopefully the first for a series of period-precise, FM radio broadcast-mimicking music sets, accurate to the specific month chosen for the set‘s theme (and not confined to any geographic region of that moment). Why? Because I’m weird.

Adding on the above, I neglected to note how part of what made this needlessly complicated was the step to include analogue floor noise — unprocessed — to mimic the sound of a nearby-but-not-too-nearby FM stereo signal to be there at all times, and something I could alter manually (mercurially, whimsically) whilst the live set was underway. That’s where Noisy comes into play. (If I had a PowerMate of any vintage, I could probably also manage that variable control without dealing with a screen.)

I’ve done a couple of these sets so far. I’ve also undertaken the very unnecessary step of using the A1278, in High Sierra, relying on a combination of various Adobe CS6 tools, along with one CS4 tool, to produce visual pieces for each set. These constitute, basically, the “remix”.

I think I may try to exhaust everything within this time period, then try to do the same for another time period — mostly to see whether I still have motivation, interest, desire, and/or time to keep at it after one moment in time (noooo, not the Narada Michael Walden/Whitney Houston song from the 1988 summer olympics — though, if I were trying for the Zeitgeist of September 1988… 🤔).
 
im typing on a my beloved 2010 macbook air i might box for a while,
somehow opera and mountain lion still works!
well with macrumors, must be the developers...
i took a screen shot after several attempts, we need to press the 3 with option.
the macbook still responsive and functional and very light
i used this everyday this october but will box this since a risk of damage might occur
if a guest knocks into the table in the garage room.

have fun with your early intel mac, my friends!

Screen Shot 2023-11-01 at 8.10.13 PM.png
 
I just used my 2007 MacBookPro to rip a DVD. The DVD drive still works perfectly!

But I wonder if it is better to use it regularly, to keep it "loosened up", or only use it when needed, to minimize wear, risk of jamming, etc?

IB
 
I just used my 2007 MacBookPro to rip a DVD. The DVD drive still works perfectly!

But I wonder if it is better to use it regularly, to keep it "loosened up", or only use it when needed, to minimize wear, risk of jamming, etc?
In my experience most things like to be used occasionally. Most electronics do not wear out due too much use but break due lack of use. Oils harden, capacitors dry out or leak, rubber parts deteriorate, read heads or lenses get dirty etc.

So, yes - I would recommend using every computer and peripheral every now and then.
 
For most of the last two weeks, have been away house-sitting. So the MacBook Pro has had to be the daily driver. There was a Windows laptop as backup. You can never have too much backup. But the Mac did the work. I still fiddled with it, knowing I had that backup if I screwed it all up, but me and it managed to coexist as working partners.
Result.
So, home today, and the iMac 12,1 wants me to upgrade to Ventura 13.6.1. I've not let any of my OCLP installs do any OTA upgrades, for fear of what might break. But with the MBP a competent backup to the big Windows machine, and another iMac and two Asus laptops in reserve, I thought, 'go for it'. So I hit the update button and let it do its thing.
After the usual lengthy download and install process, there it was. OCLP popped up to prompt a re-install of the root patches, and it's all working just fine.

The question is: would the upgrade to Sonoma work as well?
Edit: also nice to be back to 70Mbps after two weeks of 6.5...
 
There has been some problems with the Sonoma 14.1 upgrade. It was discussed in this thread too. Read some previous posts to learn more. I'll wait for awhile before I do it. Maybe some fixes appear and no need for safe boots etc.

Couldn't agree more: Ventura is working out for me 100% on my 13" 2012 MBP whereas Sonoma suffered from deal-breaking glitches.
 
  • Like
Reactions: DCBassman
There has been some problems with the Sonoma 14.1 upgrade. It was discussed in this thread too. Read some previous posts to learn more. I'll wait for awhile before I do it. Maybe some fixes appear and no need for safe boots etc.

Couldn't agree more: Ventura is working out for me 100% on my 13" 2012 MBP whereas Sonoma suffered from deal-breaking glitches.
More than enough information to say: wait. Thanks to both of you.
 
  • Like
Reactions: TheShortTimer
Couldn't agree more: Ventura is working out for me 100% on my 13" 2012 MBP whereas Sonoma suffered from deal-breaking glitches.
Hmmm. I've been running 14.1 on my 2015 rMBP since it was released (I always update to the newest OS at .1, learned my lesson with Catalina back in 2019). Comparing my 14.1 experience to my 13.1 (Ventura) experience last year, 14.1 is much faster with a lot less glitches/bugs.

It could simply be that a 2015 15" works better than a 2012 13" on newer macOS releases, given it has a quad-core i7, plus my MBP has been upgraded with a third-party NVMe SSD that is way faster than the SSUBX.

I'm running OCLP 1.2.0 nightly, if that makes any difference.

I may try Sonoma on my A1342, see how that goes.
 
Last edited:
Hmmm. I've been running 14.1 on my 2015 rMBP since it was released (I always update to the newest OS at .1, learned my lesson with Catalina back in 2019). Comparing my 14.1 experience to my 13.1 (Ventura) experience last year, 14.1 is much faster with a lot less glitches/bugs.

It could simply be that a 2015 15" works better than a 2012 13" on newer macOS releases, given it has a quad-core i7, plus my MBP has been upgraded with a third-party NVMe SSD that is way faster than the SSUBX.

I'm running OCLP 1.2.0 nightly, if that makes any difference.

I may try Sonoma on my A1342, see how that goes.
I have 14.1 running on my 2010 A1342. It works surprisingly well and is my new default OS on that machine.
 
14.1 is running better on my MacBook Air, M1 though
much better than 14.0!
The .1 releases have always been much better than the initial release.

Not sure how many people remember this, but High Sierra had a massive bug at launch where you could gain full root access by entering "root" as username with no password on any authorization window. That was still in the OS until a security patch for .1.
 
More than enough information to say: wait. Thanks to both of you.

You're welcome and Sonoma isn't going anywhere - so you can enjoy Ventura till the bugs are ironed out. ;)

On that note...

It could simply be that a 2015 15" works better than a 2012 13" on newer macOS releases, given it has a quad-core i7, plus my MBP has been upgraded with a third-party NVMe SSD that is way faster than the SSUBX.

In my case it's a power management bug in macOS that ironically, I've experienced on Catalina and a variation of it on Sonoma but not Ventura.

Not sure how many people remember this, but High Sierra had a massive bug at launch where you could gain full root access by entering "root" as username with no password on any authorization window. That was still in the OS until a security patch for .1.

Wow, I wasn't even aware of this!
 
Wow, I wasn't even aware of this!
Yeah, no idea how an exploit that big made its way into a public release of macOS. I recall it got fixed very quickly once knowledge of it became widespread (in the tech media and such). I guess that's one good thing about the new Rapid Security Responses, they can get these kinds of issues fixed immediately.

Sonoma isn't going anywhere - so you can enjoy Ventura till the bugs are ironed out. ;)
Precisely! Ventura isn't suddenly no longer supported now that Sonoma is out, so you can hold off if there are bugs. In my personal experience, I'd actually go as far as saying Sonoma is the least buggy OS release since Mojave, however of course that is from what I've experienced with 14.1 on my 2015 rMBP, using the latest nightly build of OCLP. YMMV.
 
Last edited:
  • Like
Reactions: TheShortTimer
Crossed my fingers and waited. OTA update worked fine from patched 13.6.1 until final reboot where it got stuck. Simply booting in to safe mode and manually starting OCLP to re-run the root patches was all that was needed to get 14.1 on this 2015 iMac. :)

2015-imac-14.1.png

 
  • Like
Reactions: TheShortTimer
I'll give it a go then. How much RAM do you have in your A1342? I've got 10GB in mine at the moment (8GB 1600MHz + 2GB 1066MHz thanks to the picky MCP89 chipset), but I did run Big Sur on 4GB a year or two ago.
Mine's decked out with 16 GB. It had the original 2 GB until recently when I found a cheep pair of 8 GB sticks from OWC that were guaranteed to work with this model. It's completely overkill for what I do with this computer, but cool to have. In my experience, Sonoma runs a bit better than Big Sur does on this machine, to give you an idea of what to expect.

Screenshot 2023-11-03 at 7.42.05 AM.png


Sonoma 14.0 was hassle-free to install with OCLP. 14.1 required me to first install the OS, then using the recovery partition I had to remove the patches installed by OCLP (there's a guide for this), boot into the unpatched system and install the correct KDK for 14.1, and then apply the post-install patches. Now it works fine, but these extra steps weren't immediately clear at first and were required because my computer had the KDK for 14.0 installed that caused 14.1 to hang on boot when it clashed with the OCLP patches.
 
by implication "on the same hardware" I always use the same install, and it hasn't slowed down.

I had to remove the patches installed by OCLP (there's a guide for this), boot into the unpatched system and install the correct KDK for 14.1, and then apply the post-install patches. Now it works fine, but these extra steps weren't immediately clear at first and were required because my computer had the KDK for 14.0 installed that caused 14.1 to hang on boot when it clashed with the OCLP patches.
That's interesting, because OCLP did that for me. After installing 13.6.1, it went through a whole long sequence sorting out KDK, then reinstalled the boot patches, reboot, and voila. It was observation of this process that prompted me to ask how likely a good Sonoma install would be.
 
That's interesting, because OCLP did that for me. After installing 13.6.1, it went through a whole long sequence sorting out KDK, then reinstalled the boot patches, reboot, and voila. It was observation of this process that prompted me to ask how likely a good Sonoma install would be.
OCLP does it for me too. But it requires an internet connection to download the latest KDK. Since I needed to apply the patches to regain network access and couldn't download the correct version, it just reused the already present 14.0 KDK, which caused the system to hang on the next boot. On a fresh system without the KDK already present, things might go more smoothly. But I was upgrading from 14.0 using a USB installer and ran into the issues I mentioned.
 
  • Like
Reactions: DCBassman
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.