How to build application installer for windows xp from a windows 7 PC with both labview 2011 and 2016

[Kranaq]

I have a windows 7 machine with two versions of LabView (2011, 32bit and 2016, 32bit).

In LabView 2011 I made a program which before I installed 2016 could be build into an installer and installed on a windows xp machine without problems. However, after installing 2016 I can no longer build an installer that works on windows xp from LabView 2011. Even if I do not include any "Additional installers" the installation gives a pop-up saying windows 7 is needed. If I only build executables without any installer it works perfectly.

Is there no way to build an installation for a windows xp machine from a machine which has a newer version of labview installed, even if it is build using an older version of LabView?

[UliB]

See

Why Does My LabVIEW, LabWindows™/CVI™, Measurement Studio, or TestStand Built Installer Fail on Wind...

[stockson]

When you install a newer version of LabVIEW on a PC that already has an older one, a lot of shared components are overwritten/upgraded (having more than one LV version is not recommended by NI). I believe in this case the NI Installer got updated and that's why you are experiencing this behavior.

When you go to Advanced tab of the installer properties, can you choose anything lower than Windows 7 in "System Requirements" field?

[stockson]

It seems I was late 🙂

[Kranaq]

Yes I have the option to set it to Windows XP, which I have done. It seems strange to give me this option if the shared components simply makes it impossible to build an installer for XP as it said in the link posted by UliB.

[CMJ-1969]

in reference to:  (having more than one LV version is not recommended by NI)

I'm curious why NI doesn't make this suggestion during an upgrade.  I was surprised to find that upgrading my LV2011 to LV2016 left LV2011 on my system.  Not only left it on, but made no suggestion to uninstall 2011 before installing 2016.  Furthermore, it even left ALL of my file associations (.vi, .lvproj, etc) connected to 2011.   I ended up uninstalling 2011 manually, which then left me with no file associations.  Easy enough to correct.  But I think my 2016 version is not working correctly now. I'll try a "repair" install of 2016 to see if that helps.

[RTSLVU]

I know it's not as clean as making an installer but I would assume you can still download the appropriate support libraries like VISA and the LabVIEW runtime, and install them individually.

Once you have them installed you only need to compile your LabVIEW program into an executable and copy it over to the target machine.   

[billko]

---

@CMJ-1969 wrote:

in reference to:  (having more than one LV version is not recommended by NI)

I'm curious why NI doesn't make this suggestion during an upgrade.  I was surprised to find that upgrading my LV2011 to LV2016 left LV2011 on my system.  Not only left it on, but made no suggestion to uninstall 2011 before installing 2016.  Furthermore, it even left ALL of my file associations (.vi, .lvproj, etc) connected to 2011.   I ended up uninstalling 2011 manually, which then left me with no file associations.  Easy enough to correct.  But I think my 2016 version is not working correctly now. I'll try a "repair" install of 2016 to see if that helps.

---

Multiple versions of LabVIEW live happily side by side, though you will probably have to make sure to reload any drivers you have so they can install the drivers for the new LabVIEW also.

THANK GOD LV doesn't point the old projects to the new LV version automatically.  Every time a new version came out, their mailboxes would be full of complaints as stuff broke in unexpected ways.

In conclusion, I think you decided to fling LV 2016 willy-nilly onto your computer, damn the torpedoes, full speed ahead.  If there's no good reason to upgrade in the middle of a project, DON'T.

[Kranaq]

We tried this but no matter what it refused to install or run the compiled program. It just gave a message saying you needed to run win 7 or higher and then closed the installer or .exe

[CMJ-1969]

Thank you for your input Bill.  It's good to know different versions can run side by side on the same machine.  But, due to driver conflicts you should certainly do your homework first to ensure your new version will function with your hardware - which I did, and it does.  I just couldn't decide if I should un-install LV2011 first.  

Not so sure about your conclusion tho...  with the cost of a new version, I don't think anyone makes that decision lightly.  🙂

Thanks again.