RTT - Missing .dll?
-
Hmm, well I’m out of ideas for you…this needs the big guns apparently. Standby and I’ll see if I can whistle some of that up.
Odd, this ought not to be a hard issue to sort I’d have guessed.
-
Ok…I think I sorted it - you need this one to fix it:
https://aka.ms/vs/16/release/vc_redist.x64.exe
After uninstalling the others I’d tried (which i key, from what I’ve Googled) and installing this one I got RTT Client and Server to launch!
Thanks for listening…
-
I had the same problem with it on a network computer. I just used the 32bit version client (RTTClient32) instead and it worked fine.
-
I had/have the 32 bit version installed, and for some reason it didn’t go find that one.
-
The ABI’s for the exe and the lib have to match or it won’t work. Can’t cross the 32-bit and 64-bit streams for this kind of thing.
-
I use the 64bit server on my gaming rig (win10). and i use the 32 bit client on my network computer (win7) and it works just fine. I only use it for MFDs. MFDE is stillworking for all other gauges.
-
Hah – OK I should be more clear. The ABI must match between the app, be it server or client, and the lib on the system on which that app is run. So if you have the server or client running on one machine and it’s 64-bit then you need the 64-bit runtime libs on that same system. If you use the 32-bit client or server app on a system then that system must have the 32-bit libs installed on it. Now two systems talking across the network do not have to have matching ABIs – it’s perfectly fine for a 32-bit client to talk over the wire to a 64-bit server or vice versa.
-
Would you be surprised if it’s all written down in the README.TXT inside the RTTRemote directory?
- You need to have the latest Visual C++ 2019 x86/x64 runtimes installed:
x64: https://aka.ms/vs/16/release/vc_redist.x64.exe
x86: https://aka.ms/vs/16/release/vc_redist.x86.exe
Summary: it just needs the latest combined 2015/17/19 runtimes, not some older standalone stuff.
If you don’t like using the direct links mentioned above, the MS entry page for these is:
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads - You need to have the latest Visual C++ 2019 x86/x64 runtimes installed:
-
Note also that if you have any earlier 2015 version installed you need to uninstall it prior to installing this one. There is a documented bug in the earlier 2015/2017 distro that causes this problem.
None of this is in the readme - I had to do some furious Googe-ling!
-
I was having this issue with IVC in the past. One thing to check on for this would be your anti-virus. I had my Anti-virus quarantining both the IVC.exe and .dll’s for it. I’m not sure if that’s the same issue here but it could be and sounds like it’s worth a shot. I hope that helps.
-
I only use Windows Defender and generally don’t have any issues with it…
…interestingly enough, I did a BMS 3.45 install on another machine I have running Win 7 and didn’t see this… the install and launches went smoothly. So now I’m a bit curious as to what would happen if I upgraded this machine to Win 10 - that was where I was having this issue.