So you're confident that even though an OS two generations on shows up in Updates that ordinary updates to MontereyYes but I don't think it's recommended to install major updates through System Preferences as it can brick your install. You can always create a fresh installer USB / partition and do a major update using that. Minor updates are usually fine to do through System Preferences and just require the patch to be run again on the desktop afterward.
Thank you for the detailed response; it would take some time to research the meanings of such terminology as "full installer" i.e. where commonly it seems that there are different terms for the same thing. At this point and in the absence of other advice it looks like I'll take a guess as to when an update has been released and see if there is a way to temporarily disable OCLP (again don't know what that means ie whether uninstalling "it" doesn't leave other elements intact) it and see whether the OTA update appears; logic suggests that it should but it took me about 4 hours to reformat a USB drive so I don't expect anything to be straightforward.OTA reliability depends on the system. On CMPro 5,1 it has never worked for me. The process for me is:
Lately, the latter portion has been an issue on my CMPro with Ventura & Sonoma, most likely due to some driver installed—the login screen crashes. I have yet to try setting auto-login. My approach so far has been to install the installer from another boot (I have Monterey, Ventura, and Sonoma installed) and then do the root patch from SSH from another system as the login screen keeps cycling.
- Download the full installer/Install Assistant. I use the MrMacintosh links. Install in /Application in case of the Assistant.
- Remove the RootPatch using the OCLP app. Due to my updated video and WIFi/BLE card, my system does not have one for Monterey. But it does for Ventura and Sonoma. Reboot,
- Plug in a USB keyboard/mouse if needed. Install the full new version of macOS.
- Reboot and update the Root Patch with OCLP. It should be nagging you.
The whole thing is tedious and takes hours since the installation is slow, and I have to do it on three OSs.
Are they on different disks? If so they should remain completely separate with their own update processes - as well as distinct booting.Dual boot set up incl. OCLP Sonoma and Monterey
"Google Bard" (which seems unaware that OS Ventura has been released) stated that updating the supported OS was as easy as running a short terminal command to disable OCLP and then doing a normal OTA update; since no one else on earth has ever tried this (if internet searches are any guide) then I'll try it (with low - medium expectations).Are they on different disks? If so they should remain completely separate with their own update processes - as well as distinct booting.
If mixed up on the same disk then you will have a "learning experience" when managing updates for each - this is because OCLP modifies the EFI partition which controls the boot process as well as injecting software and settings into macOS. OCLP is designed to make install easy and booting reliable, but this starts to fall down if you have multiple macOS on same disk.
Update of supported OS worked fairly normally; EFI option appeared briefly and was auto selected."Google Bard" (which seems unaware that OS Ventura has been released) stated that updating the supported OS was as easy as running a short terminal command to disable OCLP and then doing a normal OTA update; since no one else on earth has ever tried this (if internet searches are any guide) then I'll try it (with low - medium expectations).
The learning process has commenced; the EFI option (whatever that was) didn't appear on the most recent update and significant oddities have occurred; one question if you get notified about this thread: What do you mean by "different disks"; the obvious meaning is that one or the other would need to be on an external drive; I had hoped that getting the supported OS into it's own Container or Volume would work. I'd completely forgotten about the "disable OCLP via a command line" option after the success (apparently) of the first post OCLP update.Are they on different disks? If so they should remain completely separate with their own update processes - as well as distinct booting.
If mixed up on the same disk then you will have a "learning experience" when managing updates for each - this is because OCLP modifies the EFI partition which controls the boot process as well as injecting software and settings into macOS. OCLP is designed to make install easy and booting reliable, but this starts to fall down if you have multiple macOS on same disk.