Why did the Mac not realize the Librarian file was an executable? Why did it think it ‘belonged’ to TextEdit? It seems that MacOS only ‘knows’ a file is an executable if it has the ‘execute’ bit set and it would appear that my Librarian file had not got this bit set. When I did this with the corrupted Librarian package the executable file did not have that ‘exec’ icon and the Get Info reported it as a TextEdit file – so it’s no wonder it wouldn’t run! You can see the Filer icon says ‘exec’ but right-click and choose Get Info to confirm that this is a Unix Executable file: The executable file is inside the MacOS folder: On a Mac if you right-click on an application in the Finder and choose Show Package Contents you can see the various folders and files that make up an ‘app’ on macOS, starting with a folder called Contents.įor example, if we do this with the Firmware Updater app (which was working) and open the Contents folder we see this:
#Nebula 3 bug fix windows 10#
The file corruption occurred in the Unix Executable file for the Librarian and was caused when the package was compressed on a Windows 10 machine before being uploaded to the website. Please let me know in the comments below if it works for you and what macOS version you are running. This has been tested on macOS 10.15.7 Catalina and macOS Big Sur 11.5.2. Click the image or the link below for the YouTube Video Once you have authorised the apps as the video explains, you do not need to go through these security checks again when you next run the apps.
#Nebula 3 bug fix how to#
I have put together a video on YouTube which shows how to download the update package and how to deal with the security checks that macOS uses to protect your Mac as you install the BN apps.
#Nebula 3 bug fix mac osx#
This damaged file has now been replaced so if you have previously downloaded the Mac OSX update package you should delete the old package and download the new version which is now on the Stanley Audio website. I have finally succeeded – hip hip hooray!ĭuring this work I discovered that a file in the Librarian part of the update package had been corrupted so it prevented the Librarian from being opened on a Mac – see technical note below.
I have been trying to find a way to get the Blue Nebula Firmware Updater and Librarian apps to work ‘natively’ on macOS as they should. Blue Nebula apps now work on macOS Catalina and Big Sur
0 kommentar(er)
