Manage Distribution Edit Installer problem

[jwinterb]

I am using Labwindows 8.1

I have a small project that I am having problems building. When I go into the Manage Distributions, click edit and then go to Drivers & Components, there are several components checked that are not needed . I am not sure how they got checked. I am unable to uncheck them.

For example the:

NI LabView Run-Time Engine 2009 SP1 has a gray check mark in the checkbox. I am unable to uncheck it.

Nothing in my project uses this so I am not sure how it got checked.

How do I uncheck the unwanted components?

How did they get checked in the 1st place?

On a few of the checked components, the path it expects is a bogus path, I have no idea why it wants to point to the path.

Example: NI I/O Trace 3.0.2 is pointing to a directory on our company share drive: F:Groups\Engineering Transfer\Software Release\VATS which is for a totally separate release for another labwindows project.

Please help!

Thanks!
John W.

[Frank_L.]

Hi John,

Thanks for posting on the NI Discussion Forums.

In response to your question about how your these components became selected/checked in the first place, LabWindows/CVI checks for these dependencies when you open or edit distribution settings. One thing I have seen in the past is that rebuilding the whole project can reset the dependencies that LabWindows/CVI finds. You've probably tried this already, but please give it another shot just in case.

Supposing nothing changes after rebuilding, could you tell me more about your application? Is it DAQ, Serial or GPIB oriented? Does it involve any real-time components? Would it be possible for you to include a screenshot of the Drivers & Components window? Also, could you tell us your:

LabWindows/CVI version

Operating system

Any other NI software (especially LabVIEW-related) installed on your system

Looking forward to hearing back from you!

[jwinterb]

Thanks for the reply,

Attached are screen shots of the Drivers and Componenets and also my project tree and the only file that has external include files.

The project is fairly simple. The application chooses a particular board to communicate with. It sends test commands via either serial port, parrallel port, gpib, or usb/serial to the board and the board does the test commanded and then returns status.

The path for the NI LabView components is now C:\program Files\National Instruments\Shared\ProductCache

They were pointing to a folder on our shared drive, but I changed the path to the above. I was able to build the project successfully.

It seems the paths changed to the bogus path when I created a project folder for a completely different project and ran the setup. The path for this new project is what this projects NI LabView components were pointing to.

The C:\program Files\National Instruments\Shared folder is the only area I know of on my computer that any Labview related files reside.

It works but I still would like to understand why these LabView components are checked.

I am using Labwindows 8.1, windows XP

Thanks!

John W.

[Frank_L.]

Thanks for the screenshots, John.

In response to your question about the process that LabWindows/CVI uses for including dependencies: whenever you open the Edit Installer window from Manage Distributions, LabWindows/CVI checks which libraries your application calls into and selects them automatically in the Drivers & Components tab. The only dependency that LabWindows/CVI has on the LabVIEW Run-Time Engine that I know of for sure is for Network Variables (including the Shared Variable Engine). I can't see all of your project files, but it doesn't sound like your project uses these.

Have you tried de-selecting the other components to see what effect they have on the LabVIEW Run-Time Engine being grayed-out? Perhaps one of the other components depends on this.

Finally, let's take a look at the actual installer files after they're built. Do you see the LabVIEW Run-Time Engine included in those? Its possible that the LabWindows/CVI interface is just letting you know that these files are not available to include in your installer.

I look forward to hearing back from you.