Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Also, of all the OEM HDDs my Macs have been bundled (2007 A1226, 2009 A1278, 2011 A1278, etc.), none was labelled in all-black as that example is.
Intersting. I think the last HDD I pulled out of a Mac that didn't have the black label was the one in my iBook G4 that failed in 2007 or so.
 
What do I WANT to do with an early Intel Mac? Do a Macbook Pro keyboard swap. From a 2011 into a 2008, so the shell is different. Not going to be easy, methinks.
 
Was hoping to use a keyboard from one of the 2011s, but sod's law says they both have different enter keys to the 2008. Annoyingly, the 2011 that works well also has the correct keyboard! Anyhow, replacement incoming.
 
  • Like
Reactions: TheShortTimer

Attachments

  • apple-toshiba-ssd.png
    apple-toshiba-ssd.png
    518.8 KB · Views: 39
  • Like
Reactions: Amethyst1
A little way up there ^^^, I mentioned upgrading BiL's MBP 5,2 and that he'd disabled it by letting it update from Monterey to Sonoma. Well, I thought I'd reproduce that on the 2008 15", so I did. I remembered reading that the way out of this trap (no trackpad and keyboard) was to plug in a USB 2.0 or greater hub, connect wired devices, and continue to get the thing properly patched. But, no matter what I plug in, nothing. It will not ask for or see Bluetooth devices. So I'm now as stuck as he is, if you will. I'd hoped to be able to give him some idea of how to do this without couriering it back to me to start from scratch.
Any ideas?
 
A little way up there ^^^, I mentioned upgrading BiL's MBP 5,2 and that he'd disabled it by letting it update from Monterey to Sonoma. Well, I thought I'd reproduce that on the 2008 15", so I did. I remembered reading that the way out of this trap (no trackpad and keyboard) was to plug in a USB 2.0 or greater hub, connect wired devices, and continue to get the thing properly patched. But, no matter what I plug in, nothing. It will not ask for or see Bluetooth devices. So I'm now as stuck as he is, if you will. I'd hoped to be able to give him some idea of how to do this without couriering it back to me to start from scratch.
Any ideas?

The only idea I have is to look further afield for anyone else who’s run into something like this.

I found one discussion which comes very close to what you‘re describing — a late 2008 unibody MB5,1 having issues with Sonoma on OCLP. It required removing the boot patches and installing a slightly older version of OCLP.
 
Speaking of OCLP, I updated Ventura on my 13" 2012 MBP and that was a terrible decision because the display settings appear to have been corrupted as a result. Hardware acceleration has been disabled, everything tears, the mirroring icon is active even though mirroring is not in use and the DisplayPort function has stopped working.

Resetting the NVRAM and SMC hasn't made a difference.

Ordinarily I would just repair the installation with a reinstall but I can't find any option for anything similar with OCLP. :(

I suppose I could run the installer and see what happens...
 
Speaking of OCLP, I updated Ventura on my 13" 2012 MBP and that was a terrible decision because the display settings appear to have been corrupted as a result. Hardware acceleration has been disabled, everything tears, the mirroring icon is active even though mirroring is not in use and the DisplayPort function has stopped working.

Resetting the NVRAM and SMC hasn't made a difference.

Ordinarily I would just repair the installation with a reinstall but I can't find any option for anything similar with OCLP. :(

I suppose I could run the installer and see what happens...
You'd just boot from the installer and reinstall right? Just like you would on a Mac with a supported OS from the Recovery Partition.

That's what I'd try anyway. The OCLP boot USB stick you'd have made would have the older version.

This is why I have such trepidation for updating anymore. It's never been (always) an easy, error-free process but when we start adding in stuff like patchers and OCLP it can get screwy.
 
  • Like
Reactions: TheShortTimer
You'd just boot from the installer and reinstall right? Just like you would on a Mac with a supported OS from the Recovery Partition.

That's what I'd try anyway. The OCLP boot USB stick you'd have made would have the older version.

Ok, let me give this a go and report back.

Thanks. :)

This is why I have such trepidation for updating anymore. It's never been (always) an easy, error-free process but when we start adding in stuff like patchers and OCLP it can get screwy.

Yeah! You took the words right out of my mouth.

Everything was fine till I downloaded the update. I'm leaving that well alone in future!
 
  • Like
Reactions: eyoungren
Great idea for a thread! I’ve got a 2006 MacBook that I’ve repurposed as a dedicated music player and web browser. It’s amazing how well these old machines can hold up with a little love. I even put a lightweight Linux distro on it, and it runs surprisingly well. What’s your plan for the Mac Mini?
 
Speaking of OCLP, I updated Ventura on my 13" 2012 MBP and that was a terrible decision because the display settings appear to have been corrupted as a result.
Does OCLP have an option to reapply patches? If so, I’d try this with anything related to graphics. Did you update OCLP (if possible) before updating Ventura?

Wow. That serial really was buried deep in there. I totally missed it. Cheers!
Continuing with the Apple OEM SSD story, 2012 had SanDisk join the game. All examples I've seen share the F1 prefix.
 
Last edited:
got Pokemon diamond running under Crossover 9 on a 1.83ghz mini running tiger with No$GBA runs at full speed unlike desmume heck on a 2002 optiplex gx 260 with a 2.26ghz P4 it was playble wish there was a ppc port
 

Attachments

  • Picture 2.png
    Picture 2.png
    361.4 KB · Views: 48
  • Like
Reactions: DouglasCarroll
You'd just boot from the installer and reinstall right? Just like you would on a Mac with a supported OS from the Recovery Partition.

That's what I'd try anyway. The OCLP boot USB stick you'd have made would have the older version.

QsYACVZ.jpeg


I rebooted and held down ALT and as you can see, the installer appeared.

oJ5I7W9.jpeg


It refused to proceed because the version present on the drive is newer than that of the installer's. :(

As ever, Google is my friend because I found the solution in this Reddit post:

So maybe this thread is too old to matter but I may have found a solution, given my issue exists with the new Ventura update.

  1. Boot into disk utility
  2. Select the HD and up on the top left bar (I forget which option) click the drop down and select "New APFS Volume"
  3. Go back to reinstall OS on the new APFS volume you created

That did the trick! Venture installed onto the new APFS volume and I ran the Migration Assistant to import all of my data, programs and settings from the original APFS volume with the problematic installation. :D

Not before long I was back to my place of happiness before calamity struck with the update.

gPVtGse.png


I deleted the old volume, renamed the new one to my liking and had some fun. :)

AqRanpv.png


This is why I have such trepidation for updating anymore. It's never been (always) an easy, error-free process but when we start adding in stuff like patchers and OCLP it can get screwy.

I'm steering clear of installing these ever again...

8KrYPkY.png


...there'll be no more worries on that front. ;)

ygqR38E.png


Does OCLP have an option to reapply patches? If so, I’d try this with anything related to graphics.

This is a good point - I didn't check and really should have. That's a lesson for the future.

Did you update OCLP (if possible) before updating Ventura?

Another good point. I completely forgot about checking that - which is something that I would've done with the DosDude patchers.
 
Does OCLP have an option to reapply patches? If so, I’d try this with anything related to graphics.
Yes, it's right on the OCLP control panel. The button says "Post install root patch". You are supposed to reinstall the patches after updating the OS as the OS installer overwrites any patches that were previously installed.
 

Attachments

  • OCLP control panel.jpg
    OCLP control panel.jpg
    60.2 KB · Views: 47
Does OCLP have an option to reapply patches? If so, I’d try this with anything related to graphics.

The frame tearing and sluggishness returned so I had a look at the options.

m2OvgEY.png


ZQf0chY.png


UcyaxSv.png


pn63Rx1.png


After rebooting the frame tearing and other visual problems were resolved. There's a niggle with the patcher displaying this message on reboots:

b4d6e62.png


No matter how many times I update the bootloader and select the USB installer's EFI partition so that the update will go ahead, the message reappears. I gave up and clicked cancel. The main thing is that Ventura works properly. :)
 
Last night, in little a test, as a treat, I brought over the two SSDs and 2x8GB sticks from my A1278 to try in the A1286.

This is the operating environment I named morfologia back in 2009. (My system names aren’t perma-tied to hardware, but to the data on that hardware.) If I keep it on the A1286, this would be the fourth laptop on which morfologia has run as a long-term setup.

I’m on the fence about a permanent migration. I wanted to try out this setup for maybe a week or two and also to get a sense of any noteworthy UI differences or residual issues with the dGPU resistor removal last weekend. One I‘ve noticed is the keyboard on this unit is slightly stiffer and a tad less sensitive than my late 2011’s, but I’ve also taken note how the keys haven’t picked up that shiny sheen of heavy usage.

Without a proper carrying case for it, it’s not as portable as the 13-inch for daily use. It’s also heavier and — shocker — has a bigger footprint.

There were a couple of minor, expected adjustments to make, but it’s seeming to do OK and without untoward surprises — both when booting into Mojave (in moving the system to different hardware, dosdude1’s patcher update needed to update one patch) and when booting into my heavily modified Snow Leopard I’ve used since, well, this very day 15 years ago when 10.6.0 was about one week old and was shipping with new Macs.

[That day was noteworthy for being the very last time I walked inside an Apple Store to buy a new system; subsequent Macs were bought online from Apple, purchased used from other sellers or, literally, given to me to fix and keep.]

I may need to replace the left speaker, as it’s much quieter than its dextral counterpart. It works, but having audio balance skewed about 40 per cent to the left isn’t a long-term fix. Try-out/test drive things, I guess.

1725562835908.png


Once a proper case arrives, I’ll showcase it on here and maybe even on Club 15. :) The only apparent wear on the exterior are a couple of scratches on the bottom plate and a missing foot — not a big deal.

Oh — one last bit:

I finally solved why my one 8GB SO-DIMM from Corsair registered only as 4GB on this system, no matter what I tried, despite showing up as 8GB on my early and late 2011 13-inch MBPs. The stick is 1066MHz, not 1333MHz. All of the 2011 MacBook Pros shipped with 1333MHz sticks. The 13-inch models, for whatever reason, accept that slower RAM at full, 8GB capacity; the 15-inch (and, I’m guessing, the 17-inch) are less forgiving.
 
After rebooting the frame tearing and other visual problems were resolved. There's a niggle with the patcher displaying this message on reboots:

b4d6e62.png


No matter how many times I update the bootloader and select the USB installer's EFI partition so that the update will go ahead, the message reappears. I gave up and clicked cancel. The main thing is that Ventura works properly. :)

Hurrah on undoing the bad patch!

I’m surprised there isn’t a prefs toggle to quiet the modal nag — particularly after the first time it’s displayed after a patching change. I could mumble something about rolling releases always insisting on being the most current revision possible and the pressure therewith, but nah. The sun is out. ☀️
 
  • Like
Reactions: TheShortTimer
No matter how many times I update the bootloader and select the USB installer's EFI partition so that the update will go ahead, the message reappears. I gave up and clicked cancel. The main thing is that Ventura works properly. :)
Select USB installer's EFI? 🧐 That makes only sense if you will always keep the USB stick in and that is the only EFI that is used. You should choose the internal drive's EFI and update that. And remove first that usb stick so you can be sure it boots successfully from the internal drive.

Edit: autocorrect typo
 
Last edited:
  • Like
Reactions: TheShortTimer
Hurrah on undoing the bad patch!

Thanks. :)

I’m surprised there isn’t a prefs toggle to quiet the modal nag — particularly after the first time it’s displayed after a patching change. I could mumble something about rolling releases always insisting on being the most current revision possible and the pressure therewith, but nah. The sun is out. ☀️

The sun's out for you and your fellow North Americans. :p

Over here in Northern Europe it's pitch-black so perhaps I should grumble/mumble on your behalf. :D

Or perhaps not...

Select USB installer's EFI? 🧐 That makes only se se if you will always keep the USB stick in and that is the only EFI that is used. You should choose the internal drive's EFI and update that. And remove first that usb stick so you can be sure it boots successfully from the internal drive.

Further evidence that my brain has not been working at 100% this week. :oops:

I selected the internal SSD EFI for the update. Somehow I got confused from what I'd read online about booting from the external EFI for the update. Anyhow it's sorted. Thanks.
 
The sun's out for you and your fellow North Americans. :p

Wellllll, I think that depends greatly on where one is around here. Around here, it’s warm, but clear — perfect for releasing migratory monarch butterflies (already three today!)

Apparently folks down in the southern U.S. are being trounced by heavy, heavy rains, whereas out west, after an unusually early winter storm in the High Sierra (see what I did there?), everything’s on fire because we (the colonial ‘we’) made this happen.

Over here in Northern Europe it's pitch-black so perhaps I should grumble/mumble on your behalf. :D

Oh yah… we’ve also sent the AMOC — the Atlantic Meridional Oscillating Circulation — into intensive care.

Which is to say: the Gulf Stream, as we’ve known it, is dying before our eyes and letting Arctic storms through the back door during summertime (no idea what winter might be like).

We’re an awesome species.

We Did It! Leia Chewie.gif
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.