01-22-2024, 09:29 AM
RE: Mac Sonoma 14.2.1
I’m running Sonoma 14.2.1 on a ten year old iMac and it’s been running fine to date, though I’d only added OSCAR and for the first time after the machine was upgraded to Sonoma. Others here seem to be running OSCAR on Sonoma too, which might suggest that there is possibly some file corruption somewhere on your system (macOS or OSCAR).
Upgrading to Sonoma has not been a very smooth transition for a lot of mac users and a lot of issues still seem to persist - we’re all waiting for it to get a bit less buggy - maybe round it’s 14.3.x incarnation.
I more just muddle through when confronted by macOS issues. But some basic Apple / macOS housekeeping things you could try -
Of the above, steps 2 and 3 are easy to do and with little effort, pain or input. So I’d try these first. Then consider step 1 …just on the odd chance! Then take a deep breath and look at doing step 3 (in realty it’s not that daunting, just that bit closer to the nuts and bolts than users normally venture).
Beyond this, options seem to be. Rollback to previous version of macOS (quite difficult from Sonoma); reinstall Sonoma over the current version; (doable and without having to reinstalling apps); wiping hard disk and reinstalling macOS and apps (extreeeme!); Waiting to see if Sonoma sorts itself out and gets more stable on the next release.
Upgrading to Sonoma has not been a very smooth transition for a lot of mac users and a lot of issues still seem to persist - we’re all waiting for it to get a bit less buggy - maybe round it’s 14.3.x incarnation.
I more just muddle through when confronted by macOS issues. But some basic Apple / macOS housekeeping things you could try -
- Possibly work with a fresh download of the OSCAR dmg file from Apnea Board - it might have become corrupt along the way?
- Check to make sure your Apple user account has rights to administer the computer (System Settings > Users & Groups > User Name > Allow this user to administer this computer = ON) . That might help to establish if it’s a simple ‘user rights’ issue. Reboot if changed, then retry OSCAR.
- Reboot your mac in Apple’s ‘Safe Mode’. This loads a paired-down version of your macOS, so login items, system extensions, third-party fonts, etc., are not loaded; system caches are cleared and checks are run on your startup disk.
To initiate Safe Mode - start or restart your Mac while holding down the Shift key. Release the Shift key when you see the login screen, (you should see ‘Safe Boot’ indicated in the screen’ top-right corner). Login and try loading OSCAR. If OSCAR then runs, it suggests there is something cached or running in the background that’s stopping OSCAR loading properly. If it doesn’t load, then try the next step (following a reboot of your machine to get back to normal mode).
- There might be that some stubs or orphans have been left behind from the previous macOS / OSCAR combination you were running - macOS leaves redundant stuff lying around everywhere following upgrades or removals. So thoroughly removing OSCAR, then rebooting your machine and reinstalling OSCAR might fix your problem.
To thoroughly find and remove applications and their stubs/orphans etc, I usually use a small app called AppDelete (v.4.3.3) written by the late Reggie Ashworth (online search will find it). Warning! AppDelete is brutally effective! So usual caveats here - backup your system and data before attempting this and copy all your existing OSCAR data and structure to an external device …twice! - it’s not data you can recreate!
- I would then revisit the links supplied by Red, in case I’d missed some of the minutia.
- If it turns out that it’s a ‘file rights’ issue, then that will need to be resolved at Unix level through something like macOS Terminal app. This step is a bit above my pay grade these days …and I could do without the revisit to earlier career traumas!
Of the above, steps 2 and 3 are easy to do and with little effort, pain or input. So I’d try these first. Then consider step 1 …just on the odd chance! Then take a deep breath and look at doing step 3 (in realty it’s not that daunting, just that bit closer to the nuts and bolts than users normally venture).
Beyond this, options seem to be. Rollback to previous version of macOS (quite difficult from Sonoma); reinstall Sonoma over the current version; (doable and without having to reinstalling apps); wiping hard disk and reinstalling macOS and apps (extreeeme!); Waiting to see if Sonoma sorts itself out and gets more stable on the next release.
