FieldPoint Family

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview is constantly requesting the device driver cds

Hello,
 
I understand you don't want to use the CDs.  After seeing what you attached, it looks like you have more than one nidist.id file at the same level.  Furthermore, the setup.exe file actually uses that nidist.id file for a given installer, in fact you'll see an entry in the setup.ini file for the path to it, which usually is just nidist.id since it's at the same level, and the path reference is relative.  If you want to put everything in one folder, I think what you should do is create a folder hierarchy like the following:
 
Additional Installers
- fieldpoint
     - setup.ini, setup.exe, nidist.id, etc...
- nidaq
     - setup.ini, setup.exe, nidist.id, etc...
.
.
.
 
Then, in the installer builder application, you can point each individual installer to the folder which contains the nidist.id file for THAT SPECIFIC installer.  This works on my machine, in fact it works even if I have those separate installers in different places (one on my desktop, and another on the network for example).  On problem I DO have, is that when I attempt to build the installer, I am prompted for the path (it seems to default to the old path), and I have to past the actual path to each specific installer in.  When I do this, it completes without problems.  I think your troubles are coming from the installer builder not finding what it needs due to the directory structure you have, and where you have put the nidist.id files relative to the setup.exe (and setup.ini) files which looks for them.
 
I hope this gets us closer!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 21 of 22
(1,587 Views)

The second ndist.id actuall is copied from the second cd. I was hoping that the installer would pick up the second ID and note that the location contains all the drivers.

By point to the top leve location, it seems to work for most of the installers. At this time, I am pretty sure that there is a dependency on occuring with MAX or Fieldpoint. If you build it with the additional installer it will request the CD in the CD location if you only use either MAX or Fieldpoint. If you combine them together, it still request for the CD once again but only once. So I suspect it is finding the isntallers I told it to get. It seems to me, you have the same problem I have. It constantly request the old lcoation regardless if you update the installer lcoation.

From the forum, there is a hint that might work. I amy do this in when I do another install. Copy the Cds to a location where you can access. When labview request the installation, point to this area instead of the CDs. Then the system will know where it is and have the additional installer may now point to this location instead of the CD. I also found out, if you have a more updated driver, you need to install the driver on yur development machine. It will add the driver into the additional installer and point it to your installation directory (where it unzipped the file default National Instrument\Download). then it will fetch it without any problem.

0 Kudos
Message 22 of 22
(1,579 Views)