09-24-2018 08:12 AM
I just upgraded from LV2016 to LV2018, and now my exe requires the NI-488.2 runtime. In LV2016, I only needed the NI-VISA runtime. Any ideas why? Any tips on what functions in my code are causing this requirement? I'd like to know so that I can try to remove/replace those functions.
The problem is that NI-488.2 runtime not only bloats my installer, but it installs some junk into Windows programs shortcuts which my customers will complain about. I am not using GPIB in my application. I am just doing some basic RS232 communication using NI-VISA.
Thanks, John
09-24-2018 08:20 AM
That would be a whole lot easier to answer if you posted some code.
09-24-2018 09:09 AM
Don't think you will see the code, @JeffB, look at the website, it is a commercial product for recording medical information.
I think you need to shake that 8-ball and see what pops up. 🙂
mcduff
09-24-2018 09:16 AM
Yes, I can't upload code. Not only is it a commercial app, but the codebase is gigantic.
But I may have jumped the gun here. I suspect NI-488.2 is not required. Even though the application builder is "recommending" it when I select "automatically select recommended installers". It seems NI's routine for recommending installers is a bit lacking. It is recommending NI-488.2 Runtime, but not recommending other things which actually are required (such as NI TDM Streaming).
I'll keep this updated. I am still struggling to get my code to properly distribute after upgrading to LV2018.
09-24-2018 12:02 PM
OK. This is really shaky
488.2 is a normal, core interface for VISA. Like ethernet or serial. I would have expected it to always be installed with VISA Runtime. It may just be that the specific 488.2 driver was split out from VISA Runtime as a potential optimization.
Can you compare the size of both installers?