I received the below PM and figured I'd reply here so that it can help more people from the future.
Serial was trickier because while Windows ARM can emulate x64 software it can't emulate x64 drivers. So if your USB-serial adaptor doesn't have an ARM driver available for download, you're out of luck. In the end I found one of these. I had to download the drivers manually from the FTDI website as they wouldn't install automatically, and when trying to install them I had to install twice because the first time it would fail (across multiple VM's). On the second install it worked and the COM port now appears. That said, I've not yet had a chance to actually try making it talk to a serial device, I've only proven that it shows up correctly (which is more than any other device did). Oh, and a random guy on the parallels forum says that he has successfully used it in this exact scenario, so given my experience and the word of a stranger on the internet, I'm at least 90% confident that it will work when I do stumble across a serial device next.
No, I don't use VMWare. Mac OS runs Parallels, and parallels runs several Windows 11 ARM VM's. My automation software is installed in those VM's.Hi Mate, saw your post about using M1 Macs as your workhorse and thought I'd reach out.
I have been contemplating this for a while but haven't been able to take the plunge. I read your post regarding the RA software suite, and that has given me much more confidence.
However, can I please ask if this is how you run your system?
Mac OS -> Parallel 17 to run Win 11 ARM, and then you've installed VMWare on Win11 to run your work VMs?
Ethernet adaptors, not really. I have one sporadic issue where a network adaptor that is set to bridged will appear but simply not talk to anything. Removing and re-adding the adaptor (setting to from "Bridged" to "None" and then back again) resolves the problem in a few seconds. Other than that, no, ethernet comms are very straightforward (and come to think of it I haven't experienced that issue in a while either, so maybe it got fixed in a parallels update).Furthermore, have you found difficulty using ethernet /serial adapters through all these layers?
Serial was trickier because while Windows ARM can emulate x64 software it can't emulate x64 drivers. So if your USB-serial adaptor doesn't have an ARM driver available for download, you're out of luck. In the end I found one of these. I had to download the drivers manually from the FTDI website as they wouldn't install automatically, and when trying to install them I had to install twice because the first time it would fail (across multiple VM's). On the second install it worked and the COM port now appears. That said, I've not yet had a chance to actually try making it talk to a serial device, I've only proven that it shows up correctly (which is more than any other device did). Oh, and a random guy on the parallels forum says that he has successfully used it in this exact scenario, so given my experience and the word of a stranger on the internet, I'm at least 90% confident that it will work when I do stumble across a serial device next.
I've used Schneider software before, but not really on my new laptop. I have installed the SoMove drive software and it seems to launch correctly, and opens all my old files, so I have no reason to believe it wouldn't work. But no, I've not actually used it in anger on this machine, nor have I tried installing any Schneider software beyond SoMove. Given my experience with every other software package I have installed, I'd be fairly optimistic that it can be made to work with some cajoling.Lastly, do you also use Schneider software? Do they work well in similar environments?
Thank you very much for your help.
Cheers