Carbide Motion download page states compatibility with Windows and Mac computers, but doesn’t mention processor architecture for either. I learned the hard way that some vendors assume “Windows is Windows” and end up having driver or other issues prevent the software from being usable on ARM64 Windows installations (like Surface Go tablet and some mini PCs). Is anyone using an ARM64 Windows machine as their “daily driver” for Carbide Motion?
Per:
Other apps that aren’t built for Windows Arm-based PCs run seamlessly using emulation. Windows 11 Arm-based PCs running Windows 11, version 24H2 include the Prism emulator for improved performance for emulated applications.
That’s often the case, but things can fall apart when drivers come into play. Since hardware that’s unfamiliar to me is on play I figured the best way to find out if it works is to look for the benefit of others’ experience with the combination.
We’ve tested it on the latest Surface Pro with Arm (the SQ3 chip?) and it works well. The x64-to-ARM system that Microsoft added has been completely trouble-free for us.
I’m not sure the original Surface X devices with the first generation of Arm chips have the ability to run x64 code, so I’d stick to the more modern devices.
1 Like
Thanks Rob. That’s good to know. I’m working on getting my workspace planned and that helps a lot. I may just go with a low(ish) powered PC built for industrial environments and touch screen.
This topic was automatically closed after 30 days. New replies are no longer allowed.