Labview is constantly requesting the device driver cds

[JLS]

Hello,

I am still wondering about the question: "When you select Measurement and Automation Explorer, where does it point you by default?"  I am interested to know by default, what is being looked for - I wonder if this is the problem, that you don't have the component it is looking for.

Can you try simply creating a new distribution and taking a screenshot of the same additional installers page while having the Measurement and Automation Explorer item checked and highlighted - this should show the location it looks for by default.

I hope we're getting closer to the solution!

Best Regards,

JLS

[Joseph_Loo]

I am using an existing project that has no problems on the disk requirements. This just uses the labview run time version. I just added MAX as part of the additional installer.

[JLS]

Hello,

I think that's the problem - you have pointed the driver to look into a folder C:\Program Files\National Instruments\Drivers\all which is a copy of the driver CD files I believe.  What you need to do is install the entire driver CD so that all components are installed locally on your machine in the appropriate places (not just copied to the directory of your choice).  This way the installer will know where to find the appropriate components - simply pointing it to an image of the driver CD is insufficient.

Does this make sense?  I don't think your C:\Program Files\National Instruments\Drivers\all directory is going to do the trick - you'll need to install the driver CD on your machine, and not just copy it.

I hope this helps!

Best Regards,

JLS

[Joseph_Loo]

The drivers are already installed. I have to use them to examine various fieldpoint devices that are remotely attached to this computer. If they were not installed, I would not be able to use the fieldpoint devices. In addition, when it was pointing to the CD drive, I was prompted for the CD a lot more.

[JLS]

Hello,

I would really like to help you, so I am trying things in parallel to see similar behavior.  If put an incorrect path to the installer location I get a message indicating I need to indicate the correct path - this was expected since there wasn't anything at that path.  Then, I was able to fix the problem by pointing it to the folder containing the installer - more specifically containing the nidist.id file (which should be at the same level as the setup.exe file).  I tried all of this with NI-DAQ 8.0.1 and was able to successfully build the installer.  Let's try pointing your additional fieldpoint installer to the location of the fieldpoint installation files you copied to your hard drive - specifically to the folder which contains the nidist.id file (there should also be the setup.exe file there as well).  If that works, then you can try backing the hierarchy of the path you point to backwards until it fails.  In the worst case, you would have to point the couple installers you want to include to their respective nidist.id owning-folder locations.

I hope this helps us make some progress!

Best Regards,

JLS

[Joseph_Loo]

The location where I am point the directory for the additional installer already contains the cdrom identifier. It seems there is an additional dependency that is causing the problem. Unfortunately, there does not seem to have any kind of information to point to the location. Whatever the dependency is causing the issue, it is partially taken care of. When I have both MAX and Fieldpoint, it only responds for the drive once. If you use them separately each will prompt once. It seems there are extra dependencies that is causing the issue.

[JLS]

Hello,

I'm still not clear on the default location, but were you able to point it directly to the folder containing the nidist.di file?  Did this work for you?  After I caused the prompt to occur by pointing to an incorrect location, I was able to stop the prompt by changing the path to that of the relevant nidist.id file.  If that doesn't work, please let me know, and be as specific as possible about what happens (scfeenshots are great, showing where the nidist.id file is, and that you've pointed to that directory in the additional installers page, as well as the resulting prompt or error).

Thank you,

JLS

[Joseph_Loo]

I have had my stuff pointed to the ndist.ini directory from the beginning. It is requesting for some kind of dependency that is not listed.

As you can see from the picture it is providing no information with regard to the requirement.

The second picture contains the directory where I have my helpers pointing to. It turns out some of them will only point to the device driver disk.

[Tyler]

Have you tried navigating to the original CDs that it is asking for. Not copies, but putting the CDs in the drive and navigating to them? I have seen a couple of times where copying the CD contents was not enogh. Let us know.

Tyler H.

[Joseph_Loo]

The whole point is not to use the CDs. We keep the CDs in a cabinet a distance away. Keeping the CD at the work area is not an option.