cannot find distribution "National Instruments Device Drivers - May 2006"

[qsa301]

I am unable to build the distribution file. Whenever I try to build a dictribution, LabWin/CVI gives me the following message:

cannot find distribution "National Instruments Device Drivers - May 2006". The location does not contain the correct distribution. If you would like to specify a different path where the distribution can be found, enter it below.

And then it prompts me to put the device driver CD, which I did, but it does not take it. I have attached a screen shot for the error message. If someone can help me with this, I will be grateful. Here is the build log:

Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: National Instruments Device Drivers - May 2006
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: National Instruments Device Drivers - May 2006
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0 Full Development System
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0.1 Full Development System
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0 Full Development System
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0.1 Full Development System
 
**************
*** Error: Input data from a source data file has errors. (Error code -33)
*** End Error Report
**************
 
 
**************
*** Error: Input data from a source data file has errors. (Error code -33)
*** End Error Report
**************
 
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0 Full Development System
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0.1 Full Development System
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0 Full Development System
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0.1 Full Development System
Warning: Information about the distribution could not be found on the system.
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0 Full Development System
Found a related distribution which does not match exactly: NI LabWindows/CVI 8.0.1 Full Development System

[Mert_A.]

If you could follow the steps described in this post to obtain a debug log of your build, it may shed some light on just what is going wrong.  Post the log back to this thread, and I'll look into it.

Mert A.
National Instruments

[qsa301]

Hi Mert,

Thank for your reply. Please see the attached log.

[Mert_A.]

Hi,

I don't see any errors in the debug log you posted, though I would expect to see the error and warning messages that you copied into your first post.  Is it possible that the contents of the log you posted are from other distribution builds?  If there might have been some confusion, just delete the file from your temp directory, open CVI, enable the logging, then build the problem distribution once and close CVI.

Also, I want to confirm that the CD you insert when prompted is the May 2006 Device Driver CD (disk 1).  If it is another version (even a newer version, like the November 2006 Driver CD), CVI will correctly reject that CD.  The (often complex) component dependency chain results in the need to provide exactly the distributions asked for.

If you've confirmed that you are providing CD 1 of the May 2006 Device Driver distribution, also double check that the file E:\nidist.id exists on that CD.

If you can post a debug log containing the error information or find anything else, please post back.

Mert A.
National Instruments

[qsa301]

Hi Mert,

Thanks for your reply. I tried with May 2006 CD and it worked. Before, I think, I was trying with more recent version. Thank you for your help.

[Mert_A.]

Great. Glad to hear it's in working order.

Mert A.
National Instruments

[hotshot]

I am in the same boat. I downloaded the drivers (Aug 2009), but my CD is an older version (Feb 2009). So when the installer asks for the distribution for CD1, it is in the file that I downloaded from the NI site. But then it asks me for the distribution from CD2, which is not in the Aug09-2 folder. There could be a distribution in the "Products" folder (which is one layer within the Aug09-2 folder), but there are ~400 folders within this "Products" folder. This seems like a very simple task to accomplish, yet it is turning into a nightmare!!! If this doesn't make sense I will gladly post some screenshots of the folders.

[Jake_G]

Hey hotshot,

It looks like the version of the drivers you are downloading are more recent than the CD you are using. 

Based on the posts before, I would say try downloading the drivers from the same release.

They can be located here.

[Mert_A.]

You certainly don't need to navigate to the specific product directory. When you are prompted for a distribution/disk, you only need to make sure that distribution/disk is accessible. This may mean inserting a disk, or it might mean pointing CVI to that volume by updating the path in the prompt dialog. In either case, you only need to make sure CVI can access the root directory of that volume (e.g. Aug09-2).

If you're providing the requested volume, and it is still not finding the product it is looking for, I would double check that you are giving it the exact volume it is asking you for (i.e. Feb vs Aug drivers). In some cases you may be prompted for volumes from multiple versions of the Device Drivers distribution. If you're still having problems, reply back with the debug log, and we'll see what's going on.

Mert A.

National Instruments