Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
But what has happened to the screencap - SHIFT + CMD + 4 + SPACE BAR - feature in macOS 12.7.1? Again a very weird rendering of a basic function not working the way it supposed to.
Genuinely curious about what you are referring to here? I'm using 12.7.1 and the SHIFT + CMD + 4 + SPACE BAR is working the same for me as it ever has...

Hmm just noticed you are using OCLP 0.6.8 and I'm using 1.1.0, so maybe that matters? But it was working okay for me with 12.7.0 and 0.6.8, too.

I'm using a wired keyboard, if maybe that makes a subtle difference in config.
 
Last edited:
  • Like
Reactions: m4v3r1ck
I installed Monterey to a USB SSD on mac mini late 2009, when I tried Migration Assistant from original HDD, it has been running more than 24 hours and access light in working, what can I do next? may I power off and reboot mac mini again?
 
Last edited:
I installed Monterey to a USB SSD on mac mini late 2009, when I tried Migration Assistant from original HDD, it has been running more than 24 hours and access light in working, what can I do next? may I power off and reboot mac mini again?
What else can you do? The install to the USB disk may be OK, or maybe borked. Try to reboot holding down the Option key and see if the macOS Install icon shows up (if so click on it to continue the install). The installer may have errored out and just needed to reboot. If you do not see anything but your internal disk, the install was probably bad. In that case open up Disk Utility and see if the USB drive is OK. If you see the internal Disk and the external, select the external and see if it boots up. If it boots you are OK, the install was good.
 
What else can you do? The install to the USB disk may be OK, or maybe borked. Try to reboot holding down the Option key and see if the macOS Install icon shows up (if so click on it to continue the install). The installer may have errored out and just needed to reboot.
The installation is OK, I can use Monterey but settings is default, so I want to copy settings from orginal El Capitan HDD, now the SSD is still accessed, do I have to wait until the SSD not updated data?
 
The installation is OK, I can use Monterey but settings is default, so I want to copy settings from orginal El Capitan HDD, now the SSD is still accessed, do I have to wait until the SSD not updated data?
I can't understand this phrase, "do I have to wait until the SSD not updated data?"
If your Monterey install is working and you need to mport your settings, you can try to use the migration assistant (in the Applications/Utilities folder. It may work, but sometimes you have to set up a new user to do that, I am not sure how that works. I have always used Migration Assistant during the os install, at the end, and never afterwards. So I am not sure. You are on your own now.
 
The installation is OK, I can use Monterey but settings is default, so I want to copy settings from orginal El Capitan HDD, now the SSD is still accessed, do I have to wait until the SSD not updated data?
Neither MA not TM restore will work properly on root any root patched Macs (i.e. on any non metal Mac). To get it working you need to revert the patches, boot without patches, run MA or TM restore, reboot and re-apply patches, again. Creating TM backups from patched systems seem to work.
 
Genuinely curious about what you are referring to here? I'm using 12.7.1 and the SHIFT + CMD + 4 + SPACE BAR is working the same for me as it ever has...

Hmm just noticed you are using OCLP 0.6.8 and I'm using 1.1.0, so maybe that matters? But it was working okay for me with 12.7.0 and 0.6.8, too.

I'm using a wired keyboard, if maybe that makes a subtle difference in config.

Thanks for chiming in.

My output for the key-combo screencap, an ugly black fat border. This 'bug' occurred right after updating to 12.7.1 / OCLP 0.6.8. I had no issues on 12.7.0 too.

Screenshot 2023-11-08 at 11.49.28.jpg


Both keyboard and mouse are wired.

Cheers
 
Thanks for chiming in.

My output for the key-combo screencap, an ugly black fat border. This 'bug' occurred right after updating to 12.7.1 / OCLP 0.6.8. I had no issues on 12.7.0 too.

View attachment 2309195

Both keyboard and mouse are wired.

Cheers
I wonder if your com.apple.screencapture defaults are playing into this?

Mine screenshots save in PNG format (system default) but if yours are set to save in JPG or another format that doesn't support transparency then perhaps that contributes to the black background. I'm thinking the "shadow" added by screencapture, which involves transparency, is getting flattened into black on your system. Why black and not some other color? Maybe something to do with a dark mode setting somewhere? I don't really know how such things interact under the hood!

If your files are automatically being saved as JPG you can change this using

defaults write com.apple.screencapture type PNG && killall SystemUIServer

Be interesting to know if that replaces the black border with the transparency shadow -- but if your screenshots are already saved as PNG then obviously that's not the culprit.

You could try this command in Terminal to eliminate shadows from all screenshots and see if your black border goes away:

defaults write com.apple.screencapture disable-shadow -bool TRUE && killall SystemUIServer

Replacing TRUE with FALSE will bring it back.

If you want to read what else might be going on with com.apple.screencapture use the command

defaults read com.apple.screencapture

and there might be some additional clues.

Last thought is I wonder if it has something to do with the GTX 680? I was using a GTX 680 Mac-EFI version until recently. I swapped it for an RX 580 at the same time as upgrading from 12.6.8 to 12.7.1, so would have just missed noticing if it were going to happen to me using the GTX 680. Using the RX 580, OCLP does not have any post-root patches to install on my system, which might indicate something going on between 12.7.1 and the OC Kepler patch? Maybe as a test try uninstalling the root patches and taking a screenshot to see if your output looks any different?

(BTW your signature says macOS 13.7.1 -- pretty sure that's not out yet 😉)
 
  • Like
Reactions: m4v3r1ck
Hi - need a bit of help here. Installed OCLP on a friends MacbookPro 9,2 (mid 2012). Installation and everything seemed to go fine but when booting next day he got a flashing ? folder icon. When the install USB was inserted the macbook booted just fine.

Now to me (running self made OC on MacPro 5,1) that would seem to imply there is no EFI folder present with Opencore in it. Sure enough, the only EFI partition with an Opencore folder is the USB.

Is this normal? Why wouldnt OC EFI be on one of the wto internal drives? Is the USB drive now necessary for every boot or is tere a way to get the Opencore EFI folder onto the macbook so it doesn't need the USB?

Thanks

EDIT - OK I have got it solved. The original installer was not created on this Macbook and running the patcher/install opencore on it put a new EFI folder on the startup drive and it boots as expected now.
 
Last edited:
Hi - need a bit of help here. Installed OCLP on a friends MacbookPro 9,2 (mid 2012). Installation and everything seemed to go fine but when booting next day he got a flashing ? folder icon. When the install USB was inserted the macbook booted just fine.

Now to me (running self made OC on MacPro 5,1) that would seem to imply there is no EFI folder present with Opencore in it. Sure enough, the only EFI partition with an Opencore folder is the USB.

Is this normal? Why wouldnt OC EFI be on one of the wto internal drives? Is the USB drive now necessary for every boot or is tere a way to get the Opencore EFI folder onto the macbook so it doesn't need the USB?

Thanks
If you don't intentionally install OCLP to the internal disk, or if OCLP doesn't prompt you to do so, of course it won't be installed. Boot up from the USB, and start up the OCLP app, on the MBP 9,2, and select the Build and Install Open Core icon. Reboot. On reboot, hold down the Option key. You will see the EFI icon for the EFI installed to the internal disk on the left
Hold the Control Key and click on that EFI icon (makes that the default so you don't need the USB connected from now on), then click on the internal disk.
Bon Voyage
 
Last edited:
  • Like
Reactions: kkinto
I wonder if your com.apple.screencapture defaults are playing into this?

Mine screenshots save in PNG format (system default) but if yours are set to save in JPG or another format that doesn't support transparency then perhaps that contributes to the black background. I'm thinking the "shadow" added by screencapture, which involves transparency, is getting flattened into black on your system. Why black and not some other color? Maybe something to do with a dark mode setting somewhere? I don't really know how such things interact under the hood!

If your files are automatically being saved as JPG you can change this using

defaults write com.apple.screencapture type PNG && killall SystemUIServer

Be interesting to know if that replaces the black border with the transparency shadow -- but if your screenshots are already saved as PNG then obviously that's not the culprit.

You could try this command in Terminal to eliminate shadows from all screenshots and see if your black border goes away:

defaults write com.apple.screencapture disable-shadow -bool TRUE && killall SystemUIServer

Replacing TRUE with FALSE will bring it back.

If you want to read what else might be going on with com.apple.screencapture use the command

defaults read com.apple.screencapture

and there might be some additional clues.

Last thought is I wonder if it has something to do with the GTX 680? I was using a GTX 680 Mac-EFI version until recently. I swapped it for an RX 580 at the same time as upgrading from 12.6.8 to 12.7.1, so would have just missed noticing if it were going to happen to me using the GTX 680. Using the RX 580, OCLP does not have any post-root patches to install on my system, which might indicate something going on between 12.7.1 and the OC Kepler patch? Maybe as a test try uninstalling the root patches and taking a screenshot to see if your output looks any different?

(BTW your signature says macOS 13.7.1 -- pretty sure that's not out yet 😉)

Thank you very much for your detailed reply and troubleshooting directions:

- Toggled the shadow TRUE/FALSE
- changed JPG/JPEG to PNG

Light mode:
Screenshot 2023-11-10 at 14.42.05.png

Dark mode:
Screenshot 2023-11-10 at 14.42.23.png


JPG:

Screenshot 2023-11-10 at 14.45.04.jpg


Problem solved, thanks for your help. Very much appreciated! :cool:


(BTW signature changed to macOS 12.7.1, thanks 😉)
 
  • Like
Reactions: sailmac
Hi Guys !
Could you be so kind please and check if you can "ssh" from other local device to mac you have installed this version of macOS via OCLP ? I have successfully installed Monterey to my MacMini 6,2, but im sadly unable to connect to it via ssh even if Remote Login is On (ssh_exchange_identification: read: Connection reset by peer). Other Sharing options seems to be working.

Thank you very much
Not sure if this helps. I have three Macs, cMP 5,1 OCLP 0.4.11 with Monterey, M1 mini Montery and M2 Pro Mini Ventura. I can ssh to and from the Monterey Macs on my LAN. Nothing works, ssh hangs, from Ventura to either Monterey Macs. HTH

Edit: New version of Openssh in Ventura
 
Last edited:
I installed Monsterey 12.7.1 to mac mini Late 2009, now I found there is problem to use Japanese IME.
I am using ELECOM TK-FCM084BK Japanese keyboard, that was no any problems when I use El Capitan, now the symbol is not correct, I have to use Shift + 2 to input @, and so on...., what can I do?

TK-FCM084BK_01.jpg
 
I installed Monsterey 12.7.1 to mac mini Late 2009, now I found there is problem to use Japanese IME.
I am using ELECOM TK-FCM084BK Japanese keyboard, that was no any problems when I use El Capitan, now the symbol is not correct, I have to use Shift + 2 to input @, and so on...., what can I do?

View attachment 2311093
Did you look on the Elecom HP? It seems the keyboard only supports Windows.
So what can you do? Buy an Apple wireless keyboard, from Apple or Mericari
Mericari - https://jp.mercari.com/item/m69502503336
or - https://jp.mercari.com/item/m59454186730
Elecom - https://www.elecom.co.jp/products/detail/TK-FCM084BK.html
 
Thanks for your reply. Can you explain to me about the difference between El Capitan and Monterey?
Look it up on Google, I don't really know. I used Monterey and it was OK, but I don't have it installed now.
I am nit interested in the older macOS versions, as they no longer get security updates and the only reason to use them is older 32-bit applications, which I don't need.
Of those old systems, I have heard that Mojave is the best, most modern but still supported 32-bit apps.
Search for knowledge about El Capitan. I don't know much about it.
 
After Installed Monterey by OCLP 1.3.0 to mac mini Late 2009, I found there is MacOS upgrade to Sonoma in Software Update, can I use this to upgrade Monterey to Sonoma directly?
 
I installed to a external SSD and it works perfect without any problems.
By the way, can I upgrade to macOS Sonoma 14.1.1 directly in Software Update of system preferences without OCLP?
 
Advice on which OCLP OS to run on a Late 2013 MBP 15" (11,3).
Local repair shop says he sees alot of these models with GPU problems and fears that Ventura and Sonoma will be too demanding on the chip and "He doesn't recommend anything more than 12.7.1 Monterey"
The info seems legit but I am currently running Sonoma and it is running fine. Do you think with these words of wisdom it is worth it to stay on Sonoma or downgrade to Monterey for chip preservation?
 

Attachments

  • Screenshot 2023-11-15 at 9.34.54 AM.png
    Screenshot 2023-11-15 at 9.34.54 AM.png
    150.8 KB · Views: 58
  • Screenshot 2023-11-15 at 9.29.27 AM.png
    Screenshot 2023-11-15 at 9.29.27 AM.png
    613.1 KB · Views: 63
Last edited:
Advice on which OCLP OS to run on a Late 2013 MBP 15" (11,3).
Local repair shop says he sees a lot of these models with GPU problems and fears that Ventura and Sonoma will be too demanding on the chip and "He doesn't recommend anything more than 12.7.1 Monterey"
The info seems legit but I am currently running Sonoma and it is running fine. Do you think with these words of wisdom it is worth it to stay on Sonoma or downgrade to Monterey for chip preservation?
That phrase "too demanding on the chip" is, first, not specific, i.e., what chip? the CPU? or the integrated or discrete GPU? Second, the whole OS, either Ventura or Sonoma, is more complex and thus will put more stress on the hardware, especially the GPU (either). I have found Monterey to be a little more responsive than either Ventura or Sonoma, but not by much, especially using the latest OCLP release version. If you feel comfortable with Sonoma, use it.
Consider upgrading your OCLP version.
The real situation is that sooner or later, the older machines like that MBP from 2013 will not be sufficient for your usage pattern and you should look into getting the first M1 MBA or MBP, or if your funds are sufficient, get an M2 MBA, great computer in my opinion.
The M1 MBA can be found very cheap if you look around.
 
  • Like
Reactions: 13R41N
Now I installed to External SSD for Monterey 12.7.1 successfully, that is wonderful!
Next I want to upgrade 4G memory to 8G for good performance.
 
The 1.2 and 1.3 nightly OCLP root patch function does not work correctly with the November 13 Monterey 12.7.2 (21G1967) beta. The patcher finds that a nVidia Kepler root patch is required (screenshot) but fails with the following message (screenshot) and the internal display has a white line around dock. (On an iMac 12,2 with K2100M GPU).
 

Attachments

  • IMG_3053.JPG
    IMG_3053.JPG
    780.6 KB · Views: 59
  • IMG_3054.JPG
    IMG_3054.JPG
    608.5 KB · Views: 52
  • Like
Reactions: jmp473
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.