It is the changing interface to system libraries - the API - that causes most of the headaches, not the 32-bit to 64-bit change. Say the driver makes use of a function "foo" contained in a system library. On the other hand the driver may have been initially designed many years ago and still use APIs that have long been deprecated.
The process can be as simple as re-compiling the code. I haven't seen anything worthwhile, for me, in the last 3 or 4 upgrades anyway.Ĭan someone explain to me what is so hard about modifying a driver from 32 bit to 64 bit? Since I have no intention whatsoever to upgrade to 10.15 before end of summer 2020 anyway, I still have some time to decide. So, If you want to upgrade to 10.15, you will need to buy another solution for calibrating your screen.ĭatacolor has the current spiderX that is already using 64 bit software or a spider5 that will get an update anytime now. Please keep in mind that the Spyder4ELITE was released in the beginning of 2012. The 64-Bit message is related to the next macOS 10.15 Catalina that will be released this autumn.Īs there will be no 64-Bit software for the Spyder4ELITE, you will be not able to run on a 10.15 Catalina system. So also on macOS Mojave 10.14 the Spyder4 software is not officially compatible but works on most configurations too.Īs you are currently on 10.13 High Sierra and if the Spyder4ELITE software is working on your system - apart from the Apple message about 64-bit, you can use the Spyder4ELITE on your system.Īnd properly you can also use the Spyder4ELITE if you upgrade to 10.14 Mojave on this computer. The Spyder4 software was not officially compatible with macOS High Sierra 10.13 but works on most configurations. I've asked support. This is their answer:
0 kommentar(er)
