Using LabVIEW application builder on Win 10 (LabVIEW 2017) for use on XP machine

[TomFryFlann]

Hi,

I have built a (.exe) file using application builder which works as intended on my windows 10 machine (32 bit) but when i run the same file on my xp machine it comes up with the error "(file location).exe is not a valid win32 application". As i have built this on a 32bit machine and the files for labVIEW are in the 32bit directory i assume that it is a 32bit version of labVIEW (as you cannot build 32bit applications on the 64bit version).

I then learnt that labVIEW 2017 is not compatible with windows XP machines so could this be the problem?

Also a previous version of the program works with XP but i dont know how that was built (e.g it could have been built on labVIEW 2015 which is why it works)

And is there an easy way of getting the 2015 version back so i can build it using that?

Thanks in advance

[Bob_Schor]

My advice would be to find a Windows 7 machine that doesn't have a recent version of LabVIEW already installed and to install LabVIEW 2015 on it.

If you want to install LabVIEW 2015 on Windows 10, you must not have any more recent versions of LabVIEW (in particular, you must not have LabVIEW 2017) installed, as you cannot install previous versions "on top of" a more recent version of LabVIEW.  Uninstalling LabVIEW once you cross the barrier of LabVIEW 2017 (which uses the new NI Package Manager) is definitely more difficult than uninstalling LabVIEW 2016 and earlier versions.  If you have a "spare" Windows 10 machine without LabVIEW, you could try installing LabVIEW 2015 on that, but I'd find out first if they are compatible.  [I just did a Google search, and it looks like LabVIEW 2015 SP1 is compatible with Windows 10 -- by inference, LabVIEW 2015, the fall release, is not].

Bob Schor

[pincpanter]

I had a similar issue. When I installed LV 2017 in addition to LV 2011, I found that newly generated LV 2011 installers could not be installed to XP machines. In fact, LV 2017 updated the installer component, which is shared among different LV versions.

My solution was to create on the same computer an XP Virtual Machine with LV 2011 installed.

[altenbach]

Are you just building an executable or also an installer? Note that you can specify the min windows version when building an installer and in LabVIEW 2018 it's windows 7.

LabVIEW 2015 allow building for Windows XP SP3 so you could use that. What is the service pack level of the XP machine?

[TomFryFlann · Accepted solution]

Someone else has picked up the job and fixed the problem, I saw that when he built the installer he ticked the additional installers box, (i think) and then selected the labVIEW 2015 installer as well as the 2017 one.

I think this is what enabled it to be installed onto the XP machine as it makes sense with the compatability listed on the labVIEW website.

Thanks for all the answers

Tom

[pincpanter]

What exactly did he tick and where? I cannot see any "LabVIEW installer" item in the additional installers.

[TomFryFlann]

So when you build the "installer" type in the build specifications.

go into the "Additional installers" menu and untick the "automatically select installers" box (i cant remember the exact name)

And it will come up with a few more installers

Scroll up a little and you will see the LabVIEW 2015 SP1 installer, tick that

then finish and it should work

Good luck!

Tom

[pincpanter]

My LabVIEW versions are 2011 and 2017. Probably, 2011 does not support a specific component for the installer.

Thank you anyway.

[altenbach]

---

@TomFryFlann wrote:

Someone else has picked up the job and fixed the problem, I saw that when he built the installer he ticked the additional installers box, (i think) and then selected the labVIEW 2015 installer as well as the 2017 one.

---

I assume you are talking about the LabVIEW runtime engine, not the full blown development environment, right?

[vicky1]

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001Hvc3CAC&l=en-IN

this was an useful information for me to solve this issue