This software will be installed together with EOS Utility 2, EOS Lens Registration Tool, and EOS Web Service Registration Tool. Follow the on-screen instructions to complete the installation. Double-click the 'eum3.11.1-installer' file in the 'EU3.11.1'. I'm going to try to call Canon today and see if I can resolve this. After the file is decompressed, the disc image 'EU3.11.1' is mounted. I have no proof that this is what's causing the installer to not work - it could be some other issue - but this is not a good sign nonetheless. Which one it picks will depend on lots of factors such as the version of OSX and other things. As explained in the link, when you compile an app for Mac OS, you have to make sure you have one implementation for each class or the osx runtime doesn't know which one to use and will arbitrarily pick one. This is a clear indication that there are problems with the installer itself. Shop Digital Cameras, 35MM Camera Equipment, Photography, Photo Printers, Computers, Home Theater, Authorized Dealer Canon, Sony, Nikon, Apple, Olympus. That aims to provide Canon EOS camera owners. I did a bit of digging and found that this results from the executable having two different classes with the same name, see: EOS Utility is a straightforward macOS application developed by Canon Inc. Objc: Class CmdUtil is implemented in both /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/CanonOFI_TEMP/Data/Software/Install/UniversalInstaller.app/Contents/MacOS/UniversalInstaller and /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/CanonOFI_TEMP/Data/Software/Install/UniversalInstaller.app/Contents/Frameworks/UIx.framework/UIx. When you launch the app from the command line, the following error message is generated: This did not help, so I doubt it is a permissions issue since the "sudo" command should allow you to do anything at all on the computer (it is the equivalent of giving the command "root access") First of all, I went into the app bundle directory and tried launching OFICore directly with the "sudo" command (OFICore is the actual executable program that runs when you launch the installer). Since I'm a software developer and I know a bit about how Mac OS X apps work I was able to try a few more things. However the user account I'm on right now has admin permissions so I'm not sure what is wrong. Other users (on 10.9) say that it is related to permissions: they logged out and logged in under a user account with admin permissions and it worked fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |