My mac is 13inch Mid 2012. Its the really old fat mac book that still supports disc inputs. Im on OS High Siera now, is it a good idea to upgrade to Mojave (cant find it in apple store) or Catalina? 8GB Ram btw, I dont want to do it if my mac will become slower and bugy. Nov 08, 2019 Catalina on (3) Late 2009 Mac mini’s, buttery smoothly. Catalina on (1) Late 2009 iMac, buttery smoothly. Catalina on (1) 2011 MacBook Air 13″, buttery smoothly. Only 4GB’s but works buttery smoothly. Catalina on (1) 2008 iMac 24″, internet, mail photo’s, and all default apps work fine, but only 4GB ram so it can be a tad slow. APFS BootROM Support: If you have a machine that supports High Sierra natively, you MUST ensure you have the latest version of the system's BootROM installed. If you have NOT previously installed High Sierra, you can download and install this package (if running OS X 10.10 Yosemite or later) to install the latest BootROM version (you MUST reboot after installing the package to apply the. Dec 06, 2019 Each year that Apple releases a major new version of macOS, a few older Mac models that ran the previous version usually fail to make the new list of officially supported Macs. In the case of.
While I have older hardware (a 2013 MacBook Pro) that I use for testing macOS betas—it's now running Catalina—it's often handy to have the latest macOS beta running in VMware Fusion on my iMac. With past OS releases, this has been a relatively easy process. With Catalina, however, attempting the install results in a black screen.
Thankfully, some enterprising Fusion users (Bogdam and intel008) have figured out a workaround. I tried it, and while it did work for me, I had to change the instructions just a bit (read on for the details).
I'm not going to replicate the entire blog post here, as it's quite involved (and includes lots of helpful screenshots), but the short version is that it requires setting up a new VM (upgrading will not work!) as a macOS 10.14 guest, customizing the settings to change it to a Windows 10 x64 (yes, really) guest, launching the VM setup tool by dropping the Catalina installer app on it, interacting with the Windows 10 boot controller a couple times, then finally changing the VM back to a Mac guest OS.
That all sounds great, so I set to work, and all was progressing well…until I reached the part that reads… Dsm hyper backup explorer app for macos.
Select “Boot normally” and press Enter.
This should then give you the normal boot progress screen:
But for me, it didn't provide the boot progress screen. Instead, I saw a few boot failed messages—it looked like it couldn't find a boot volume—and I wound up back at the same screen.
Os Catalina For Older Macs Men
After a few cycles of this, and not sure what to do about it, I tried something on a lark, and it worked: I shut down the VM, then opened its settings, went to General, and changed the OS type back to macOS 10.14 from Windows 10 x64.
When I then restarted the VM, macOS booted to the initial setup screen (select a region, etc.), and everything worked.
As it turns out, it seems that my installer had run all the way through before getting to the Windows controller boot screen for the first time, because what I did as a fix is listed as the next steps after the installer finishes, which the instructions describe as hapening after the first visit to the Windows controller boot screen. I have no idea why mine worked in a different manner.
One thing that may not be obvious from the instructions is how to actually get the macOS Catalina installer app you need to proceed. To do that, you need to install the Catalina profile from Apple's developer download page (login required). Then open System Preferences > Update, and let the installer download. When it's fully downloaded, quit System Preferences, and you'll find 'Install macOS 10.15 Beta.app' in your Applications folder.
If you don't want to install the profile on your actual Mac, you can follow the above steps in an existing virtual machine, then copy the installer to your actual Mac via drag-from-VM or via file sharing. You then drag this image into the new VM's setup screen to start the process.
Final note: I had to run the Install VMware Tools command twice. Run it once and then approve all the security requests and allow the extension, reboot, then run the Tools installer again, and it should work.
Great thanks to those who figured this out—having a virtualized beta to test with is incredibly convenient. Macs from the minimum specifications for mojave.