LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can't find nidist.id while building executable

This is a reference to the problem that I copied once I gave up my search fior the file:nidist.id
 
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> CDK_Engine_PromptForMissingDist.vi
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'National Instruments Device Drivers - November 2006, Disk 1' from: D:\ to: C:\Program Files\National Instruments\Shared\ProductCache\
Copying distribution 'National Instruments Device Drivers - November 2006, Disk 2' from: D:\ to: C:\Program Files\National Instruments\Shared\ProductCache\
Done building deployment
/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 1 of 2
(4,248 Views)
Hi BCU002,

LabVIEW has the ability to create a very detailed log of the events that occur when building an application or installer. To enable this feature, open up the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom of the file. Save the changes and close the ini file. The LabVIEW.ini file is usually located in C:\Program Files\National Instruments\LabVIEW 8.0.

Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) . To find out where this temp directory is located, go to Start>>Run. Type in "cmd". Then type "set". This will return all of your computer's variable names. Look for TEMP. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp". Navigate to this directory using Windows Explorer. You should see a file named "name.log" where "name" is the name of your build specification. For example, you might see "My Installer.log" if the name of your build specification is "My Installer".

Usually the problem is related to registry entries pointing to invalid distribution locations. I assume 😧 is your CD-ROM drive. In this case, the registry identifies the distribution location in the 😧 drive. Your best solution is to copy the Device Drivers CD to your local drive and reinstall from that location. You may also need to update the registry information.

Cheers.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

0 Kudos
Message 2 of 2
(4,236 Views)