Look in Safari preferences.
Unselect the one that says Safari opens with "All windows from last session"
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Unselect the one that says Safari opens with "All windows from last session"
Motivated by your tests, tried FireWire install/boot also on my MBP5,2.
There is a small logic error in OCLP which prevents FireWire boot support for MacBookPros (reported it via Discord). Booting stopped in the middle of the progress bar.
After fixing it locally, I am now working from a FireWire disk.
It is only for testing really as it is a slow, spinning disk, but it works.
Yet to test if installation to FireWire also works after the fix; it didn't before and the installer said "can't install to FireWire". I guess it won't, but will report back.
Installation method used
- the EFI with the fix is on the FireWire disk, from where it could be booted already before the fix
- the installer in on a USB2 SSD (an old Kingston 120GB, which contains several installers in different partitions)
- it wasn't really a clean install, but the target disk was a CCC data-only clone from another MR installation, and the 12.1 installed over it (always worked reliably for me, while Migration Assistant didn't).
If only it were that simple.
Look what I have got in Safari prefs: choice between rock and hard place a.k.a. all windows or all private windows from last session.
So the matter stays unresolved?
Attachments
Thanks for taking the time and applying much work into the FW-fix.
I will eagerly look out for your further comments and findings on the FW-issue.
Hopefully, a future release will allow FW-installation to work as intended. If it will bring with it the full FW800-speed, that'd be my first choice over USB2.0. Alone the setup assistant took me 2hrs+ to complete, the preceding Monterey installation between 1.5 and 2hrs via USB2.0. I found the speed advantage of FW800 vs. USB2.0 around factor 2.
Keep me posted, please hvds
I would not know, sorry. I don't do beta OS.
Still on Big Sur. No Monterey on any machines.
Still, thanks, mwidjaya.
there is a workaround, a little annoying though.
Shift-click on Safari in the Dock will open Safari with a blank page.
Before, there was a dedicated Safari pref for that.
Merry Christmas to you!
Btw, I upgraded my 2008 MBP4,1 from Catalina to Big Sur, stayed on Big Sur for 1 day, then I immediately upgraded to Monterey. Monterey is even better than Big Sur. Just in case, you are wondering, if you should upgrade. Your machine is 4 yrs. younger, she would perform way better than my MBP.
I tried to install to the FW drive again, with the USB installer booted via the fixed OCLP.
Same result: can't install to the drive when it is connected via FW. As it has a USB2 interface as well, I can install to it this way.
Anyway booting it and running it via FW works well.
Probably the fix will be in one of the coming 0.3.4 nightlies.
It is also appended as zip here if you want to try it. Just run the OpenCore-Patcher.command which should open in Terminal when double-clicking. It is the TUI version.
The change is in resources/build.py, check_firewire().
EDIT: the zip file was too large for upload. Please find it here instead: https://www.dropbox.com/s/jgd0ye5z5q719j8/OpenCore-Legacy-Patcher-main034n-211222.zip?dl=0
Attachments
Last edited:
For Catalina machines it will be 2021-008. Again it is in the link. You just need to find the right version for your machine on M-r Macintosh' s page. Also look at Apple:Did not know that.
Learn something new. Thank you.
=========
Edit:
Thought about it more. Something was nagging at me.
- Method seems ok but it is a little more complicated than that
- Firmware update can be coming from full installer (like 11.6.2 which does not contain MM61.scap) or
- in 2012 mini's case it is a security update to 10.15.7
Security Update 2021-007 (Catalina) – Apple Support (AU)
This update is recommended for all users and improves the security of macOS.support.apple.com
- Went unpacking though the contents of Security Update 2021-007 (Catalina)
- Found the correct EFI payload for 2012 mini, file called MM61.scap
- File identifier says 424.0.0.0.0
But my method of applying all software updates, got me to 425.0.0.0.0
Maybe some other update is getting EFI payload that gets it to 425.0.0.0.0
Hmnn, manual method remains tricky. Think will stick with applying all software updates to officially supported OS partition.
Apple security releases - Apple Support
This document lists security updates and Rapid Security Responses for Apple software.
Last edited:
Yep, figured out later that there must be a newer update for Catalina that gets to firmware 425.0.0.0.0.
Thanks for providing manual method. Good to have alternatives.
I downloaded the .zip of the 0.3.4 build from your dropbox and read the respective lines of code.
If that does the trick, that'd be great.
However, I cannot judge from these few lines of code, if that will allow to install FROM external FireWire drive TO internal Macintosh HD.
I only intend to use the external FireWire drive for installing Monterey onto my MacBookPro4,1 , in order to profit from the FireWire800 speed.
Do your code mods provide THIS? If so, I will definitely try and run a clean install again.
Please let me know.
Hello I managed to install Monterey on a macbook pro 17 "from 2009, but I think I have no graphic acceleration, I deduce it from the fact that when the mouse arrow scrolls on the menus you see shadows and staggered colors, I ask for a solution to the problem because the VIRTUAL DJ application not starting that I mainly use, this problem has plagued me since the Catalina patch, the program is installed regularly, when I start I do not have its main screen but only the program menu that I do not does it does practically nothing, the mac has two video cards Nvidia 9400M / 9400M Gt. I ask you to help me solve this problem Thanks
That seems to work -
For a test I‘ve put the Kingston SSD which contains the installer, into the enclosure which has the FW port (plus unused USB). The target disk in on a USB2 adaptor.
Stage1 of installing 12.1 again to the target spinning disk is completed, thus most (all?) accesses to the installer; stage2 running.
The fix to OCLP is already in the 0.3.4 nightly.
Differences to your intended setup are:
- I‘m using FW400 with 400-800 connector on the Mac side
-installing to a USB target
but I don‘t think that matters.
Attachments
The second #=8.0 is the important number. No threat, otherwise. Perhaps a new macOS version yet unreleased will change in the future?
The fix is not working from external FW800/400 spinning drive to internal SATA connected Macintosh HD SSD.
Still the same Ø message on the screen.
I attempted the clean install from 3 FW disks with 3 different FW cables, the internal drive within the MPB seems to be addressed differently by Apple.
Where can the nightly builds of OCLP be obtained please?
Can you look further into the FW issue?
Explanation by Silent Knight author here:The second #=8.0 is the important number. No threat, otherwise. Perhaps a new macOS version yet unreleased will change in the future?
https://eclecticlight.co/2021/03/06/why-is-my-macs-gatekeeper-data-so-out-of-date/
The current build is available for download here (that link is only valid for some time and will not be updated) - you might need a GitHub account for accessing it.
My FireWire enclosures seem to have the chipsets from Oxford Semiconductor - but I think that shouldn't matter for Intel Macs.
In my setup here, I get the Ø message when trying to boot a FW disk WITHOUT enabling the FW boot in OCLP. That is the case with OCLPs which dont't have the fix, or if the FW boot isn't enabled even in the version with the fix.
Make sure it is enabled in the OCLP with the fix: do
5. Patcher Settings, 4. Boot Volume Settings, 1. Set FireWire Boot, y, Q, Q.
Then 1. Build OpenCore. The build protocol should mention FireWire.
Then 2. Install OpenCore to USB/internal drive.
Sorry if I haven't made clear that setting FW boot is required despite the fix. The bug had just prevented setting FW boot to take effect.
As for access to the nightly builds, on the OCLP Github https://github.com/dortania/OpenCore-Legacy-Patcher, click the green Code button and Download ZIP.
Attachments
Last edited:
Ecleticlight is on the menubar, has been for years, before SilentKnight was LockRattler, also useful, as is SysHist. Also, a free course in Art History.👀
? Apply the root patches, OCLP_033RTUI Offline Variant Step #3 if not on ethernet.
Thank you for the link, which is indeed no longer available for download. I do not have a Github account, unfortunately.
Thank you, hvds, for taking the time to look into the issue once more.
I indeed was looking for the FW prompts in the build protocol and it wasn't there, which was entirely my fault.
So, I built everything again as per your detailed instructions, and it executed as you described.
Thus, the FW issue looks resolved. I hope, it will be in the next OCLP 0.3.4 release.
Thank you for the tip on how to get the n builds via clicking on "Code">download .zip on the Github OCLP page.
Awesome, hvds. You made my day.
Merry Christmas to you.
Last edited:
?️ Mike Bombich compiled a vast but somewhat random pile of useful info regarding external drive enclosures, an interesting read. Scroll down to the Prohibited symbol and start there - https://bombich.com/kb/ccc6/help-my-clone-wont-boot ?
Last edited:
