10-19-2016 11:39 AM
Hi,
I discussed this with the NI support. After the traditional run around the block I was given a "solution":
If you absolutely need to run your deployment installer on Windows XP, Windows Vista or Windows Server 2003, you can complete the following steps. NI doesn't guarantee that your deployment installer will always successfully run upon the following modification.
Note: You will need to repeat these steps every time you build a new deployment installer.
This did not work in my case.
Here is the full explanation in case it might be useful for someone:
"Microsoft dropped support for Windows XP, so it’s unrealistic for us to maintain XP support in new releases.
This issue actually isn’t specific to CVI, but rather an underlying component of all NI Installers called the Meta Deployment Framework (MDF). The following KB offers some details that you can share with your customer. Please be sure to reiterate that this is not a fool proof solution, and it’s not guaranteed by NI.
http://digital.ni.com/public.nsf/allkb/F73E807066D3309086257FC40063DD50?OpenDocument
That page also brings up another point that is also likely to affect this customer. Even if they keep a machine around with 2013 to build installers, the installer will not run on XP if it includes any new runtime or driver packages.”
After a few more emails the local NI engineer paid us a visit. He had a look at the problem and said that it will try to escalade it to the development team but insisted on the fact that he does not promise a solution.
I have been developing in LabWindows for more than 8 years….but if NI does not solve this I am seriously considering changing the tools….Their field/support engineers don’t seem to take the issue seriously and refuse to put me in contact with the development team. Maybe there are not enough complains for them to take this serious…
I will come back with more details after I get an official answer form NI…
11-04-2016 11:23 AM
Hi,
The reason this workaround isn't working is because CVI distributions enforce minimum version in both setup.ini and merged.bin (Installer dir » supportfiles » merged.cab » merged.bin).
CAR 612692 has been created for this. As a separate workaround, you could use Orca to edit the condition in merged.bin
You can then use MakeCab to recreate merged.cab and replace the one in the installer.
I want to reiterate that we do not recommend using software in unsupported configurations since it may not have been tested.
Hope this helps!
Trent
NI Automated Test Software PSE