Like me, If you have recently upgraded to Apple's latest Mac OS Mojave 10.14. 1) Try restarting your mac, and trying to open the.DMG again. 2) Hold down the Control key when you click on the.dmg then select Open from the context menu. Theis should give you a window to 'allow anyway'. If neither of these options solves the probelm for you, please make a Technical Support Request and let us know.
![]()
When a 'corrupt' disk image file really isn't corrupt | 6 comments | Create New Account
The following comments are owned by whoever posted them. This site is not responsible for what they say.
When a 'corrupt' disk image file really isn't corrupt
I'll definitely keep this information in mind...
btw, it's 'hdiutil', not 'hdutil' (obviously just a typo, otherwise there wouldn't have been any output from the 'attach' or 'imageinfo' subcommands).
When a 'corrupt' disk image file really isn't corrupt
Not the same problem but this may help a few users out there. Once in a blue moon I will download a file which should be an installer, it could be any kind of file however, and when I click on it it usually opens in script editor.
Often this files are named like 'Worlds Greatest program 1' Changing them to 'Worlds Greatest program 1.0' will usually make the program work. Sometimes just adding any dot and number will work. You will be asked if you want to add the extension, just say yes. I don't know why this happens but the fix is easy.
When a 'corrupt' disk image file really isn't corrupt
I just checked on a computer running Panther, and it has 'bunzip2' installed as a part of the BSD.pkg - I think the BSD subsystem was included in the standard install and would normally have been installed unless explicitly excluded. So if attempting to open a disk image in 10.3 gives a corrupt image error, use and if the output indicates 'bzip2 compressed data', then try something like to see if it can be converted to something that can be opened normally. I get some 'trailing garbage' error during the process, but the output file seems to work ok.
Some preliminary observations:
Disk images created directly using hdiutil create -format UDBZ don't bunzip properly. Those converted to UDBZ (originally created using 'Disk Utility' or hdiutil without specifying a format) seem to work after bunzip2, but only using Panther's bunzip2 - Tiger's bunzip2 doesn't unzip them properly. Anyone have any ideas to account for the differences in the UDBZ images created by the two methods, and the different behaviours of bunzip2 under 10.3 and 10.4? ![]()
Developers: When you do make a UDBZ image, put 'Requires OS X 10.4 or later' immediately under your download link/button. Leave no doubt as to the minimum requirement of your app.
Recently stuck with the following error message when in installing third party apps on macOS Sierra. 'Application' is damaged and can't be opened!
Apparently, the issue lies with 'Gatekeeper'
The Gatekeeper settings can be found in System Preferences > Security & Privacy > General. The Gatekeeper options are located beneath “All apps downloaded from:” with the choice of “Anywhere” missing.
Thankfully, the “Anywhere” setting can be restored to Gatekeeper in Sierra with a Terminal command. First, quit System Preferences if it’s open and then open a new Terminal window. Enter the following command, followed by your admin password when prompted:
sudo spctl --master-disable
Now, relaunch System Preferences and head back to the Gatekeeper settings. You’ll now see that “Anywhere” has been restored. Click the padlock in the lower-left corner to enter your password and make changes, then select “Anywhere” from the list of Gatekeeper options. The security feature will no longer bug you about apps from unidentified developers.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |