In 2001, we migrated Virtual TimeClock from running on Apple's original OS to their new Unix based OS X operating system. About a decade ago we again migrated Virtual TimeClock from running on Apple PowerPC chips to their new Intel based chips.
#This file is not optimized for mac software#
At this point, the majority of our work is thorough testing to ensure 100% compatibility and reliability of all our 64-bit applications and components.Īs a software company with over 3 decades of Mac development, this isn't the first major technology transition with Apple. We will be updating all of our Virtual TimeClock applications (for both Mac and Windows) to a 64-bit architecture. This has been a tremendous help for memory intensive programs like video editing and computer games. On the other hand, Virtual TimeClock, like most business software, runs without any noticible change as a 32-bit or 64-bit program. The 64-bit architecture was developed primarily as a way to allow programs to use the huge amount of memory available on modern computers. Over the last several years, Apple has been transitioning their operating system and applications from a 32-bit to 64-bit platform. Read more about the message from Apple's website.įor decades, all computer programs used a 32-bit architecture. This message is informational and does not indicate any change in how your TimeClock software is performing. Apple says this message gives users "advance notice that they are running 32-bit software which will not be compatible with macOS in the future." This is Apple's not-so-subtle way of encouraging software developers to migrate their 32-bit applications to the new 64-bit architecture. What does Apple's "not optimized" message mean?