A couple of years ago I posted about my exploits getting as much rockwell software as possible installed on Windows Server 2019.
I've taken the plunge and bought myself a shiny new MacBook Pro with apple silicon, which means that I can no longer run VMWare and was back to square one. So now I've been going through the same process of trying to install the same software on Windows 11 ARM, using parallels. To assist future me if I ever have to go through this process again, and hopefully a few other people who stumble in here, here's how it went.
RSLogix 5 v10.00.00: installed and launches successfully
RSLogix 500 v12.00.00: installed and launches successfully
RSLogix 5000 v8 & v9: would not install. Not devastated about this.
RSLogix 5000 v10 through v20: installed and launches successfully, after some fun with .NET 1.1 and v17. Refer below.
Studio 5000 v21 through v33: installed and Logix Designer launches successfully, with some caveats around v26 and 27 (see below). Did not test View Designer.
FTView Studio v12: installed and launches successfully
RSNetworx v28.01: would not install. Not a show stopper, but would be good to get working.
RSLogix 5000 v10-???
Same as the last time I tried this, I had to side-load .NET 1.1 (refer this website) to get some of the earlier versions working.
RSLogix 5000 v17
I downloaded the latest minor revision of RSLogix 5000 v17, but the installer kept crashing. I tried to download the second-most recent minor revision, but the download was 0kB. In the end, I found a slightly older version contained on a multi-version installation disk, which got it successfully installed.
Studio 5000 v26
This one installed correctly but would crash immediately upon opening. The solution was:
- Locate the Logix Designer v26 .exe file (for me it was at C:\Program Files (x86)\Rockwell Software\Studio 5000\Logix Designer\ENU\v26\Bin)
- Right click > Properties > Compatibility Tab
- Check the box for "Run this program in compatibility mode for:" and select "Windows XP (Service Pack 3)"
- Click the "Change emulation settings" button and select "Safe emulation" from the dropdown list
Having done this, I still can't launch v26 by double-clicking on a v26 file, or by creating a new v26 file from the Studio 5000 launcher. It gives an error message about requiring elevation. Even if I set the .exe file to run as an administrator, or set UAC to "never notify", it doesn't work. The only way I've found to create or open a v26 file is to run the v26 .exe file directly, and then use File>New or File>Open once it's launched. It's a pain, but I don't use v26 all that often, so I can live with it.
Studio 5000 v27
Same as last time, v27 has a compatibility check built in that stops it letting you try to install it. It's easily overcome. I used Notepad++ to open the Logix_V27.xml file that's in the Config folder on the installation media, and did a find and replace to change all instances of Unsupported="yes" to Unsupported="no" and then it installed successfully. Once installed, v27 has the same issues as described above for 26, and the same solutions apply.
I'm going to keep trying on RSNetworx, so if anyone has any ideas, let me know!
I've taken the plunge and bought myself a shiny new MacBook Pro with apple silicon, which means that I can no longer run VMWare and was back to square one. So now I've been going through the same process of trying to install the same software on Windows 11 ARM, using parallels. To assist future me if I ever have to go through this process again, and hopefully a few other people who stumble in here, here's how it went.
RSLogix 5 v10.00.00: installed and launches successfully
RSLogix 500 v12.00.00: installed and launches successfully
RSLogix 5000 v8 & v9: would not install. Not devastated about this.
RSLogix 5000 v10 through v20: installed and launches successfully, after some fun with .NET 1.1 and v17. Refer below.
Studio 5000 v21 through v33: installed and Logix Designer launches successfully, with some caveats around v26 and 27 (see below). Did not test View Designer.
FTView Studio v12: installed and launches successfully
RSNetworx v28.01: would not install. Not a show stopper, but would be good to get working.
RSLogix 5000 v10-???
Same as the last time I tried this, I had to side-load .NET 1.1 (refer this website) to get some of the earlier versions working.
RSLogix 5000 v17
I downloaded the latest minor revision of RSLogix 5000 v17, but the installer kept crashing. I tried to download the second-most recent minor revision, but the download was 0kB. In the end, I found a slightly older version contained on a multi-version installation disk, which got it successfully installed.
Studio 5000 v26
This one installed correctly but would crash immediately upon opening. The solution was:
- Locate the Logix Designer v26 .exe file (for me it was at C:\Program Files (x86)\Rockwell Software\Studio 5000\Logix Designer\ENU\v26\Bin)
- Right click > Properties > Compatibility Tab
- Check the box for "Run this program in compatibility mode for:" and select "Windows XP (Service Pack 3)"
- Click the "Change emulation settings" button and select "Safe emulation" from the dropdown list
Having done this, I still can't launch v26 by double-clicking on a v26 file, or by creating a new v26 file from the Studio 5000 launcher. It gives an error message about requiring elevation. Even if I set the .exe file to run as an administrator, or set UAC to "never notify", it doesn't work. The only way I've found to create or open a v26 file is to run the v26 .exe file directly, and then use File>New or File>Open once it's launched. It's a pain, but I don't use v26 all that often, so I can live with it.
Studio 5000 v27
Same as last time, v27 has a compatibility check built in that stops it letting you try to install it. It's easily overcome. I used Notepad++ to open the Logix_V27.xml file that's in the Config folder on the installation media, and did a find and replace to change all instances of Unsupported="yes" to Unsupported="no" and then it installed successfully. Once installed, v27 has the same issues as described above for 26, and the same solutions apply.
I'm going to keep trying on RSNetworx, so if anyone has any ideas, let me know!