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.
My system now is 11.2.2 patched with @Ausdauersportler micropatcher.
Is it possible to use OpenCore only for OTA and then patch the system again to be able to boot without using OC? Is this the hybrid method described above?
...(omissis...)...
Is it possible to build an OpenCore USB or SD without using the Mac OS installer? I want to have that OC USB only for applying OTA updates and then remove it. Should I always unpatch before booting with OC?
I think it absolutely cannot be done, as OpenCore requires a clean installation.
I copy what is written at the beginning of the clear and excellent --> OpenCore Patcher Instructions:
<<Notes: Only clean-installs and upgrades are supported, installs already patched with Patched-Sur or bigmac cannot be used due to broken file integrity with APFS snapshots and SIP.>>
I decided to switch to OpenCore, via the patcher, at the encouragement of Ausdauersportler and so far I am delighted to have done so.
Do you think that in addition to have the all Boot options working, as for a real Mac, now the system allows me not only to install updates via OTA, but (finally ...) I can even download the original copy of Big Sur directly from the App Store, as a Big Sur supported Mac!!!
 
  • Like
Reactions: AlexSakha67

Attachments

  • 20210311_141522.jpg
    20210311_141522.jpg
    334 KB · Views: 185
  • Screen Shot 2021-03-11 at 14.21.43.png
    Screen Shot 2021-03-11 at 14.21.43.png
    92.7 KB · Views: 201
  • Screen Shot 2021-03-11 at 20.39.59.png
    Screen Shot 2021-03-11 at 20.39.59.png
    278.2 KB · Views: 158
  • Screen Shot 2021-03-11 at 20.41.47.png
    Screen Shot 2021-03-11 at 20.41.47.png
    149.8 KB · Views: 154
  • Screen Shot 2021-03-11 at 20.43.58.png
    Screen Shot 2021-03-11 at 20.43.58.png
    331.5 KB · Views: 156
  • TDM.png
    TDM.png
    71 KB · Views: 151
  • NightShift.png
    NightShift.png
    58.9 KB · Views: 153
  • customized OCLP icons.jpg
    customized OCLP icons.jpg
    263.3 KB · Views: 199
Last edited:
OCLP please @Ausdauersportler, migrate or transfer your work in your patcher into fully OCLP way! Best of Luck 👍❤️

1-Audio Applealc.kext I'm playing to find out right layout-id...(for now I'm using usbaudio speaker)

2-Ethernet needless for me, I had workful wifi network by atheros40.kext instead.

3-For now im playing to inject legacy Ati 4670 frambuffer.kext & all relative kexts to see if will give some more snappiness...
Currently we are exploring the optimal OpenCore spoofing settings. When this is done I will publish the EFI folder for the iMac11,x and 12,x probably on the iMac GPU thread.

Reading the alcid from the boot-args is broken. For AppleALC you need to create this entry in DeviceProperties->Add:

Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PciRoot(0x0)/Pci(0x1B,0x0)</key>
    <dict>
        <key>layout-id</key>
        <integer>24</integer>
    </dict>
</dict>
</plist>

The proper layout-id is:

For iMac11,1: 81
For iMac11,2: 18
For iMac11,3: 24
For iMac12,1: 9
For iMac12,2: 32

You will get the hardware just recognised and according to former experiments just he chinch head set port will work in and out, i.e. using it with an iPhone head set with a microphone.

Load AppleALC v1.5.9 from here...
 
Last edited:
I think it absolutely cannot be done, as OpenCore requires a clean installation.
I copy what is written at the beginning of the clear and excellent --> OpenCore Patcher Instructions:
<<Notes: Only clean-installs and upgrades are supported, installs already patched with Patched-Sur or bigmac cannot be used due to broken file integrity with APFS snapshots and SIP.>>
I decided to switch to OpenCore, via the patcher, at the encouragement of Ausdauersportler and so far I am delighted to have done so.
Do you think that in addition to have the all Boot options working, as for a real Mac, now the system allows me not only to install updates via OTA, but (finally ...) I can even download the original copy of Big Sur directly from the App Store, as a Big Sur supported Mac!!!
Long story, short:

There are two available OTA upgrades Apple provides from time to time:

a) OTA delta installers, i.e. from 11.2.2 to 11.2.3, usually of a size less than 3GB
b) OTA full installers (approximately over 12GB size)

The latter ones can be applied even to (micro)patched Big Sur systems because it replaces the root volume completely, the former ones only to systems with unchanged root file system, aka unpatched, i.e. never patched. Changing the root file system by patching break a seal which cannot be restored.

But in late summer 2021 we will get possible the last full installers and then we are forced to install this one using OpenCore, applying all type a) delta updates and finally (micro)patch.

The same happens right now with Catalina.
 
Last edited:
I just upgraded to 11.2.3 using OpenCore. Everything work perfect but on boot and on shut off the screen appears many white letters on black font goes down, no the  logo with the progressive bar. Is it normal?
 
...(omissis...)... But in late summer 2021 we will get possible the last full installers and then we are forced to install this one using OpenCore, applying all type a) delta updates and finally (micro)patch. The same happens right now with Catalina.
I know, dear friend ... they are leading us to total System's closure and possibly to full Apple's control...
For example: today I tried the new option (the 6) of the OpenCore patcher which allows you to choose <Set SMBIOS mode> and I chose <: Currently moderate> instead of the original setting <Currently minimal>
Well, when I rebooted the system, iCloud asked me to log-in again and Time Machine, instead, told me I had switched machines.
Apple monitors every step we take... Just use LittleSnitch or other utilities that examine network traffic to see that Apple always intervenes in our devices and checks everything, to authorize or not, even if it does so in background and absolutely silence. Bye :)
 
Listed of successes:

MacBook Pro 2012 (i7 Nvidia video card) Patched Sur - super easy did two partitions. One Catalina,One BigSur on two separate APFS containers.

2013 27 busted iMac from eBay. After adding nvme drive to the pci-e ssd slot, had one Catalina on the SATA PORT, one Patched Sur anon pci-e port. Blessed EFI on SATA SSD filled with OpenCore. Updated naturally from Catalina.

2009 4,1 12 Core flashed to 5,1, Using Big Mac by StarPlayerX Using OpenCore Boot Picker on a rx580, had to sell the 5700 XT, too much of a market. Kept Dosdude1 Catalina and Big Sur running Big Mac GUI.
NOTE: Bless OpenCore from Catalina, blessing from Big Sur will break Big Mac.
 
Finally I tested the behavior of my iMac with Filevault (see attached screenshot, with model information).
The EFI was created this morning and replaced the previous version (0.0.16).
I used the main build of OpenCore Patcher 0.0.18.
I never expected that with Filevault running the Mac could fly better than before! Was it because the encryption reorganised the file system?... :)

Note 1 to sick nerds ;)
From OpenCore Legacy Patcher Option #4, I always disable Verbose Mode and also the ShowPicker. This way the behavior of my iMac on startup is perfectly the same as the Macs on which Big Sur is supported.
Using BBEdit, I also always reduce the boot timeout from 5 seconds to 2 seconds. To do this, I edit the <<Big-Sur-OpenCore-Legacy-Patcher-main/payloads/Config/v0.6.8/config.plist>> file, before transferring the EFI to the EFI partition of internal disk or to the EFI partition of USB Installation Key.

Of course, when your Mac starts up and you hear the sound of the Gong, you can always access OpenCore by holding down the Alt-Option key.

But be careful (important!). After disabled the ShowPicker option, to access the list of disks you need to follow this procedure:
1) Click and hold the Alt-Option key as the Mac starts up
2) Click the OpenCore icon
3) Click on OpenCore.efi and IMMEDIATELY AFTER press and hold the ESC key.
4) When the mouse cursor appears in the upper left corner and you can release the ESC key.
5) The bootable system disk is displayed.
At this point, if you want to view all drives, including the Recovery Disk, you can press the SPACE key.
Enjoy

Note 2:
I do not explain why if instead of BBEdit I use Xcode to change the Timeout directly in the config file contained in the EFI partition, the Mac hangs at startup and I am forced to use the USB Key to restart the system.

A final treat for super crazy nerds as me :)
Inserting OpenCore EFI into the EFI partition creates several duplicate files preceded by ._ (dot - underscore), as EFI partitions are formatted in FAT32.
To clean them, mount the EFI partition using the command
sudo diskutil disk0s1 (OR the name of EFI disk that you discover using the command "diskutil list"; for example disk1s1 or disk2s1, etc... It's up to you to check which one)
So! The EFI disk containing OpenCore EFI will appear on the Desktop.
Then with the Terminal do the command
dot_clean -v /Volumes/EFI
or better still, after typing dot_clean -v (and a space!) drag EFI disk that appeared on the Desktop into the Terminal.
Press Enter and enjoy: all unnecessary files named, e.g., ._abcdefg.abc will desappear into your EFI partition.


Mac_Info.jpg


Code:
Vincent@iMac ~ % diskutil apfs list
APFS Containers (3 found)
For safe, I REPLACED all disk UUIDs with: ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
+-- Container disk2 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|   ==============================================
|   APFS Container Reference:     disk2
|   Size (Capacity Ceiling):      2000189177856 B (2.0 TB)
|   Capacity In Use By Volumes:   560957927424 B (561.0 GB) (28.0% used)
|   Capacity Not Allocated:       1439231250432 B (1.4 TB) (72.0% free)
|   |
|   +-< Physical Store disk1s2 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|   |   -----------------------------------------------------------
|   |   APFS Physical Store Disk:   disk1s2
|   |   Size:                       2000189177856 B (2.0 TB)
|   |
|   +-> Volume disk2s1 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk2s1 (Data)
|   |   Name:                      Macintosh HD - Dati (Case-insensitive)
|   |   Mount Point:               /System/Volumes/Data
|   |   Capacity Consumed:         544529133568 B (544.5 GB)
|   |   Sealed:                    No
|   |   FileVault:                 Yes (Unlocked)
|   |
|   +-> Volume disk2s2 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk2s2 (Preboot)
|   | |   |...(omissis data...)...
|   +-> Volume disk2s3 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk2s3 (Recovery)
|   | |   |...(omissis data...)...
|   +-> Volume disk2s4 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk2s4 (VM)
|   |  |   |...(omissis data...)...
|   +-> Volume disk2s5 ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|       ---------------------------------------------------
|       APFS Volume Disk (Role):   disk2s5 (System)
|       Name:                      Macintosh HD (Case-insensitive)
|       Mount Point:               Not Mounted
|       Capacity Consumed:         15050813440 B (15.1 GB)
|       Sealed:                    Broken
|       FileVault:                 Yes (Unlocked)
|       Encrypted:                 No
|       |
|       Snapshot:                  ABCDEFGH-ILMN-OPQR-STUV-XYWZ12345678
|       Snapshot Disk:             disk2s5s1
|       Snapshot Mount Point:      /
|       Snapshot Sealed:           Yes
 
Hi everyone! I haven't got to the point when I'll finally switch from Barry's micropatcher to the openCore, but I guess I am getting there eventually... I am still on Big Sur 11.2 Beta 1 on my MBP mid 2012 - 13" and I have tried installing the Beta 2 without any good results. Does anyone managed to upgrade through the micropatcher to BS 11.3 Beta 3? Thank you in advance! Have a good one!
 
Last edited:
This is a short list of users and theirs systems running Big Sur with some of the patcher options listed on page #1 and post #1. This list is not complete, does not represent a ranking, is just meant to answer the "is my system supported" question.

I gathered this list from the signatures the particular users added to their account here, just searching through the last 10 pages of post.

If you want to see a longer list please just add a signature to your own account showing the data I need to fill the columns here in the table.

Thanks in advance!

usersystemhardware changesBig Sur versionpatcher
@buckrockMacBookPro10,1BCM94360CSAX11.2.2@Barry K. Nathan yp 0.5.1
@whgmkellerMacBookPro9,211.2.2OCLP 0.0.11
@woefiMacBookPro9,2BCM94331PCIEBT4CAX11.2.2OCLP 0.0.13
@vincenzo79MacBookPro10,111.2.1?
@contacosMacBookPro10,111.2.1Patched Sur
@il-rollinoMacBookPro10,1BCM94360CSAX11.2.2@Barry K. Nathan yp 0.5.1
@BmjuMacBookPro10,1BCM94360CSAX11.2.1OC 0.6.7
@adam25255MacBookPro9,211.3 beta 1@Ausdauersportler yp 0.5.5
@MacdctrMacPro5,111.2.1,OC 0.6.6
@Pri-estMacPro4,111.2.2/11.3 beta 2OCLP 0.0.9
@Pri-estMacPro3,111.2.2/11.3 beta 2OCLP 0.0.9
@alphascorpMacPro5,1RX58011.2@Barry K. Nathan yp 0.5.1
@hvdsMacBookPro5,111.2.1/11.3 beta 2,@jackluke (BigSurFixes)
@air.manMacBookPro5,111.2@jackluke (BigSurFixes)
@air.manMacBookPro8,211.2.1@Barry K. Nathan yp 0.4.4
@webg3MacBookAir5,111.2.2OCLP ?
@AusdauersportlerMacBookAir5,111.2.2OCLP 0.0.9
@clarosiMac14,211.2.2@Barry K. Nathan yp 0.5.1
@iMac-OldschooliMac13,111.2@Barry K. Nathan yp 0.5.1
@TockmaniMac13,211.2@Barry K. Nathan yp 0.5.1
@n0rt0nthecatiMac14,211.2.2@Barry K. Nathan yp 0.5.1
@Will350iMac14,211.3 beta3@Barry K. Nathan yp 0.5.1
@Ben NaamboiMac12,1K610M11.1@Barry K. Nathan yp 0.5.1
@AusdauersportleriMac11,1WX4150, BCM943602CDP11.2.2@Ausdauersportler yp dev-v0.5.5
@AusdauersportleriMac11,3RX480, BCM943602CDP11.2.2@Ausdauersportler yp dev-v0.5.5
@AusdauersportleriMac12,2WX4170, BCM943602CDP11.2.2@Ausdauersportler yp dev-v0.5.5
@StephN999iMac12,1WX415011.3 beta 2@Ausdauersportler yp dev-v0.5.5

Glossary:
yp micropatcher
OC OpenCore
OCLP OpenCore Legacy Patcher
K610M, RX480, RX580, WX4150, WX4170: GPU types
BCM943602CDP, BCM94360CSAX: BT 4.0/4.2 and WiFi combo cards
Hello sir! You can add me with the details from my signature. Have a great one!
 
Hi everyone! I haven't got to the point when I'll finally switch from Barry's micropatcher to the openCore, but I guess I am getting there eventually... I am still on Big Sur 11.2 Beta 1 on my MBP mid 2012 - 13" and I have tried installing the Beta 2 without any good results. Does anyone managed to upgrade through the micropatcher to BS 11.3 Beta 3? Thank you in advance! Have a good one!
I too am still using BarryKN's micropatcher 0.5.1 for installations to my 15" mid-2012 rMBP. No one has reported a successful install of 11.3 beta 2 (build 20E5186e) using the InstallAssistant.pkg and micropatcher 0.5.1 (at least that I know of!). I had no trouble at all installing 11.2.3 (build 20D91) with micropatcher 0.5.1; plus I think 11.3 beta 3 also works. I'd recommend installing 11.2.3 rather than the beta anyway. Good luck!
 
  • Like
Reactions: macinfo
I'm back! Just finished installing Big Sur 11.3 Beta 3 on my MBP 9,2 mid 2012, 13 inch, using Barry's micropatcher v 0.5.1! Everything works perfect, Wi-Fi, handoff, airdrop. Have a good one!
 

Attachments

  • Screen Shot 2021-03-13 at 18.43.43.png
    Screen Shot 2021-03-13 at 18.43.43.png
    1.5 MB · Views: 138
Last edited:
Hi all,

It's been a while since I stopped by, and I can see there has been continued progress :D

I have not been tinkering with my installation very much, however I'm stuck on 11.0.1 and it's very stable, but missing two features: Ethernet support and on-board audio. I get around those with Wi-Fi and using an external USB->3.5mm audio output, but it's still a bit more clunky than having everything function correctly.

So my question, should I risk some stability, wipe and re-install with a newer method?

My successful installation on my 11,1 iMac (Late 2009) 27" with a K2100M and Broadcom BCM943602CDP for BT/Wi-Fi includes using Catalinaloader/Open Core, otherwise I don't get native Brightness.

I also had most success for installation using the @jackluke method, booting from OpenCoreAPFSloader4b1 and use Hax3 patching. I also had to use the BarryKN Micropatcher to get my BT card working.

It would be great to get OTA updates, and fix my audio, do you guys recommend I try a different patcher method for particular hardware?
 
  • Like
Reactions: macinfo
Hello
My Mac Pro (Early 2008) and my hobby.
Booted from USB OCLP v0.0.18 made a clean installation from macOS Big Sur, in apfs format, modified MacPro7,1 model with nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82 csr-active-config FF0F0000 disabled.
Then, at the post-installation, it booted from the computer OCLP 0.0.15 MacPro3,1 with SIP enabled and installed macOS Big Sur beta v.16.5.03
After that, I reinstalled OpenCore Legacy Patcher v0.0.18 on the EFI section, registered the necessary information in the platforms info and smbios version.USB AUDIO(C-Media Electronics)
And even with new OCLP releases, MacBook7,1 starts to work faster🙂
Thank you very much khronokernel and all the other developers, the world is getting better with you😊👍
 

Attachments

  • Screenshot 2021-03-14 at 02.16.42.png
    Screenshot 2021-03-14 at 02.16.42.png
    122.1 KB · Views: 131
  • Screenshot 2021-03-13 at 15.01.33.png
    Screenshot 2021-03-13 at 15.01.33.png
    105.1 KB · Views: 126
  • Снимок экрана 2021-03-14 в 00.52.35.png
    Снимок экрана 2021-03-14 в 00.52.35.png
    88 KB · Views: 124
Hi everyone, I also switched from micropatcher to OCLP (v 0.0.17)
Must say that micropatcher worked great for me, just wanted to try something else and get the benefit of delta updates.

Didn't notice any difference in the regular use, apart from iCloud that once somewhat got stuck, so Messages and iCloud preferences won't open, solved rebooting the Mac. Now the system works regularly, I rebooted several times and no issues have happened again.

Nevertheless I wasn't able to use FileVault: when I try to activate it I get an error that says that the password is not correct. I tried using both iCloud or generating recovery a key, but neither of those worked. Noticed that SIP and SSV are not enabled despite I DID chose to enable them while creating the EFI with OCLP. guess the problem is related to that but I didn't figure how to overcome it.

Before opening an issue on OCLP GitHub page I want to make sure that I'm following the procedure correctly.
1615658610145.png

This are the settings I used, I put the EFI folder into a removable drive, booted from it, wiped all the data on the internal SSD, installed BS on it, imported my data from Time Machine, moved the EFI folder into the EFI partition on the internal SSD. Is it correct?
1615658983323.png


Diskutil says that the volume seal is broken.
 
Last edited:
Hi everyone, I also switched from micropatcher to OCLP (v 0.0.17)
Must say that micropatcher worked great for me, just wanted to try something else and get the benefit of delta updates.

Didn't notice any difference in the regular use, apart from iCloud that once somewhat got stuck, so Messages and iCloud preferences won't open, solved rebooting the Mac. Now the system works regularly, I rebooted several times and no issues have happened again.

Nevertheless I wasn't able to use FileVault: when I try to activate it I get an error that says that the password is not correct. I tried using both iCloud or generating recovery a key, but neither of those worked. Noticed that SIP and SSV are not enabled despite I DID chose to enable them while creating the EFI with OCLP. guess the problem is related to that but I didn't figure how to overcome it.

Before opening an issue on OCLP GitHub page I want to make sure that I'm following the procedure correctly.
View attachment 1743297
This are the settings I used, I put the EFI folder into a removable drive, booted from it, wiped all the data on the internal SSD, installed BS on it, imported my data from Time Machine, moved the EFI folder into the EFI partition on the internal SSD. Is it correct?
View attachment 1743299

Diskutil says that the volume seal is broken.
If you once have patched the Big Sur with micropatcher your seal is broken and it remains broken. Only a complete new installation will change this. About the NVRAM settings I cannot tell you anything unless you pull the config.plist out of your EFI folder an check the boot-args yourself.

Do not rely on graphical tools. The truth is hidden in the config files of your OpenCore and your Unix installation.

Changing to OCLP means new installation or updating a full installer to get an untouched sealed new root files system.
 
If you once have patched the Big Sur with micropatcher your seal is broken and it remains broken. Only a complete new installation will change this. [...]

Changing to OCLP means new installation or updating a full installer to get an untouched sealed new root files system.
But I did it! I wiped the internal drive, installed from scratch from a brand new USB drive installer generated with createinstallmedia: SIP disabled, broken volume seal.

About the NVRAM settings I cannot tell you anything unless you pull the config.plist out of your EFI folder an check the boot-args yourself.
I checked the config.plist and it looked correct, as far as I can understand it.

Changing to OCLP means new installation or updating a full installer to get an untouched sealed new root files system.
I just gave it another try, the only difference this time was that I set the SMBIOS Mode as Moderate instead of Minimal.
Generated a new EFI folder, installed BS again OVER the existing installation and now SIP is enabled and the volume is sealed.
 
I just upgraded to 11.2.3 using OpenCore. Everything work perfect but on boot and on shut off the screen appears many white letters on black font goes down, no the  logo with the progressive bar. Is it normal?
I mean this:
 

Attachments

  • C58D5AB9-68A7-4155-B11E-2CA277E35434.jpeg
    C58D5AB9-68A7-4155-B11E-2CA277E35434.jpeg
    394.7 KB · Views: 111
  • 1D451758-FD3B-4E61-9BDC-9301DEBE4D17.jpeg
    1D451758-FD3B-4E61-9BDC-9301DEBE4D17.jpeg
    1,020.8 KB · Views: 121
  • 96862418-66F3-438C-93D6-4044DA911054.jpeg
    96862418-66F3-438C-93D6-4044DA911054.jpeg
    918 KB · Views: 129
  • 8D02E722-9FE6-49F5-9313-5C06D71F5D22.jpeg
    8D02E722-9FE6-49F5-9313-5C06D71F5D22.jpeg
    524.9 KB · Views: 104
  • 68C92A79-1657-4B81-AACD-B88550801789.jpeg
    68C92A79-1657-4B81-AACD-B88550801789.jpeg
    551.3 KB · Views: 85
Got a system alert today that my Mac was at the potential of a great danger ;-) and if I was will to share the log with Apple. The log was EFIdump.
 
Got a system alert today that my Mac was at the potential of a great danger ;-) and if I was will to share the log with Apple. The log was EFIdump.
Wow! What's going to happen now? Will they report you to Apple's Legal Department? Do they send you the NSA?... Are the Federals coming?... General Custer is back and "Our soldiers are coming! Charge!!!"? Ta-da, ta-da, ta-da-ta-da-ta-daaa!… Or will they remotely block all unsupported Macs?... :)
Hopefully in the future they don't really want to prevent the development and use of these nice Patches... That would be sad and a nasty verse that would make me migrate to Linux or even Winzozz forever :)
 
Last edited:
Wow! What's going to happen now? Will they report you to Apple's Legal Department? Do they send you the NSA?... Are the Federals coming?... General Custer is back and "Charge!!! Our soldiers are coming!"? Ta-Ta, ta-ta, ta-ta-ta-ta-ta-taaa!… Or will they remotely block all unsupported Macs?... :)
Hopefully in the future they don't really want to prevent the development and use of these nice Patches... That would be sad and a nasty verse that would make me migrate to Linux or even Winzozz forever :)
At least you understood my joke 🥳
 
  • Like
Reactions: OKonnel
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.