09-26-2017 09:34 AM
Are there any compatibility issues with using LabWindows/CVI 2017 to develop applications for Windows XP, Service Pack 2 or 3? If so, what is the latest LabWindows/CVI version I can use? I currently am using 2013 SP2, but I'd like something more current.
Thanks
09-27-2017 12:59 AM
Based on my experience and tests, the latest version you can use is CVI 2015.
You can use CVI 2015 SP1 only if you don't use VISA and/or DAQmx (maybe other components too, I don't know) but you have to follow this steps.
I know very wellthat this can be an issue, but the best thing is to leave XP (and force the final customer to do the same). Sometimes a hardware change is necessary too, but on the long period is the cheaper solution.
09-27-2017 08:45 AM
To expand on Vix's comment, you will also need to make sure you're using the 2015 SP1 f1 environment if you'd like to build a distribution that can install on XP. Before that version, the minimum OS requirement was also built into the distribution binaries, so the steps in that KB will not help.
09-27-2017 08:52 AM - edited 09-27-2017 08:53 AM
Hmm, unfortunately, I think the application does use VISA, so I guess that option is out.
09-27-2017 08:58 AM
Could I use LabWindows/CVI 2017 to develop the application, and then build it with 2013 so it runs on XP?
09-27-2017 09:25 AM
If you are not using any command that do not exist in 2013 you should be able to do this.
But if you keep a 2013 install alive to compile the application, couldn't you use it for development as well?
09-27-2017 10:12 AM
I could use 2013, but the IDE features are lacking significantly.