Include path issues with CVI 8.0.1

[Double_D]

I just upgraded my computer from Windows 2000 to Windows XP.  The previous CVI installation was on drive D:.  It is now installed on drive C:.  I have noticed two problems since the reinstallation.  The first problem is related to include file search paths.  I have set the include paths under the Options>Environment menu to point to a directory containing nidaqmx.h.  Compiling the file with #include <nidaqmx.h> gives a "File not found" error.  If I try to open nidaqmx.h, the file cannot be opened because it is looking for it on the 😧 drive.

The second problem is seen when running the debugger.  When I run the debugger on a different application, it behaves strangely.  Pressing the F10 key (step over) sometimes runs multiple lines of code in succession.  At other times, pressing F10 doesn't appear to do anything (i.e., the cursor does not move to subsequent lines), but following lines of code are actually executed.  It is hard to tell where the program is, though.

[Jon_M]

Hi Double_D,

CVI searches for Include files in this order on whatever drive is installed to:

   1. Project list
   2. Project-specific include paths
   3. Non-project-specific include paths
   4. The paths listed in the Instrument Directories dialog box
   5. The subdirectories under the cvi\toolslib directory
   6. The cvi\instr directory
   7. The cvi\include directory
   8. The cvi\include\ansi directory
   9. The VXIplug&play include directory
  10. The cvi\sdk\include directory

If the nidaqmx.h file is located on the 😧 drive then the program is unable to locate it unless you specify it explicity in the include path (as you've already tried). From what it sounds like because you're unable to even open the file on your 😧 drive you'll probably want to reinstall the DAQmx driver to the C: drive. Also, after upgrading your operating system it is highly recommended that you reinstall the NI-DAQmx driver to the same drive as CVI.

Regarding the debugger issue, I've never heard of the CVI debugger behaving in that manner. Does it step over multiple lines of code that are the same type every time (i.e. an if statement, case statement, etc)?

[Double_D]

Thanks for the assistance.  I have been able to resolve both problems.  I had nidaqmx.h as an include file in my project.  When I looked at the full path of this file, however, CVI was still looking for the non-existent file on D:.  Since the project file list has search order precedence over the include file search paths, changing the paths didn't have any effect on the "File not found" error.

The debugger problem was related to another program running in the background.  I recently installed System Mechanic 7 for evaluation.  After uninstalling this program, the debugger functions properly.