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.
No real solution. Since not everybody in the non-metal community has seen these gray boxes: Do all your machines act like that? I've tested very much with Big Sur and Monterey on my MBP8,1 and different versions of Word - without success. Then yesterday Jazzzny suggested on Discord to try Word 16.43 (November 2020, I guess). That works for me! But of course it would be great if this issue could be solved at some stage.

EDIT: I testet a bit today. I got as far as 16.49. 16.50 is the first version to produce gray boxes. I know that older versions do that as well. But I won't bother testing when the good times started. I'm satisfied to have found the most recent version that works for the time being.
Wonderfull! Thank you so much!
 
  • Like
Reactions: TimothyR734
Thanks for the response. Sorry if this is a stupid question, but doesn't this just enable the computer to receive beta releases? Or does it work another way when used in conjunction with OCLP?
Primary purpose is to receive developer betas. On my machine full 12GB-OTA updates are provided, no delta. Otherwise with reference to OCLP, I can't say.
 
  • Like
Reactions: TimothyR734
Nope. But it does help those w/cMPs. Something is trying to run PlayKit for 4 minutes straight upon cold boot or wake from sleep. Suspect new features in 12.3b1 cause this. Killing the replayd process is the temp. fix. ?
No matter how often I kill the replays process in Activity Monitor, it keeps coming up, still, after some minutes, the machine goes back to normal while still feeling slower than 12.2 and betas before.

I will now move to test latest OCLP 0.4.2n, as release notes say it applies to all Sandy bridge and older processors, which is the case with my MBP4,1. I' ll report the results.
 
  • Like
Reactions: TimothyR734
Primary purpose is to receive developer betas. On my machine full 12GB-OTA updates are provided, no delta. Otherwise with reference to OCLP, I can't say.
Ah ok, well I was wondering how to fully stop receiving updates, at least for the major OS versions, and it seems like it's not actually possible, at least not with this command.
 
  • Like
Reactions: TimothyR734
Most of the time is used by the computer to test RAM and CPU. Not much to do here, however you can save a few seconds looking in the <key>Boot</key> section for:

Code:
<key>Timeout</key>
<integer>5</integer>

This is how long the disks are displayed before Mac OS takes off, in seconds. Range 0...whatever.

Also, if you are not booting anything else and have your boot settings edited properly for booting OTA updates, you may even set
Code:
<key>ShowPicker</key>
<false/>

With this set to false/ (note the slash), you will need to hold down OPT or ESC before boot in order to show the bootpicker.
 
After applying the latest OCLP 0.4.2n (GUI) overall performance is significantly better. Time until the applications are responsive is substantially reduced, while replayd is still active after startup for some time.

I'll give it 8/10 in performance, while 12.2 and the 12.2 beta versions were a 10/10 in speed.
 
Last edited:
Hi all, I have an iMac14,1 which only has the iGPU (intel iris Pro, Haswell) so no Kepler.
Although this machine was dropped with BigSur, iirc this graphics chip should still be supported by Monterey as it's also used by the mini2014 and mbp2015.

If I use OCLP, its default settings are with disabled SIP and Secureboot.
Is it really necessary to patch the root with this configuration?
Could I simply skip the patching and enable SIP/SB afterwards?


Output of OCLPv042

Building Configuration on model: iMac14,1
Created build folder
- Adding OpenCore v0.7.7 RELEASE
- Adding config.plist for OpenCore
- Adding Lilu.kext 1.5.9
- Enabling VMM exemption patch
- Enabling HW_BID reroute
- Adding FeatureUnlock.kext 1.0.6
- Found 3rd Party NVMe SSD (1): C0A9:2263
- Found NVMe (0) at PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)
- Adding NVMeFix.kext 1.0.9
- Found Wireless Device 14E4:43A0
- Adding AirportBrcmFixup.kext 2.1.3
- Setting Wireless Card's Country Code: AT
- Found ARPT device at PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)
- Adding OpenCanopy GUI
- Adding SATA Hibernation Patch
- Enabling ShowPicker
- Set SIP to allow Root Volume patching
- Disabling SecureBootModel

- Adding bootmgfw.efi BlessOverride
- Allowing FileVault on Root Patched systems
- Fixing Content Caching support
- Adding RestrictEvents.kext 1.0.6
- Using Model ID: iMac14,1
- Using Board ID: Mac-031B6874CF7F642A

- Cleaning up files
 
  • Like
Reactions: TimothyR734
I would like to reduce the time from switching on to the appearance of the logo
The 30 second delay you are seeing is because you do not have a default startup disk chosen. Open system preferences, choose Startup, unlock the padlock in the bottom left corner, then choose your startup disk. Reboot when prompted and the boot will be instant.
 
Monterey12.3beta.png

Thanks to @khronokernel for his incredible support of this community!
 
Last edited:
Computer ART.png


And this about (Monterey) Computer Art:

Using zwei iMacs A and B with Monterey I started

1. screen sharing on A to see the contents of B
2. AirPlay to Mac B from Mac A and got this

While active you can move windows and get a time delayed movement of the deeper mirrored pictures....
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.