10-11-2006 03:27 PM
10-11-2006 03:44 PM
10-12-2006 06:43 PM
01-15-2007 10:42 PM
01-17-2007 03:50 PM
01-18-2007 05:07 PM - edited 01-18-2007 05:07 PM
Hi Lorielle P, Thanks for your reply, I upgraded from LV7.1 to 8.2. I don't think I've ever had DAQmx 8.1. I did a mass compile as soon as I upgraded to LV8.2. DAQmx 8.3 was on the hard drive when I tried it. Still no good.
I ended up copying my project to another pc that only ever had LV8.2 on it. After rebuilding the project on the new pc (all the dynamic vi paths and support file paths were broken) The installer used DAQmx 8.3 quite happily.
The only problem is the exe wouldn't work on the new pc. Something to do with the excel vis I was using. They only compile when the App Builder is in debug mode, but the exe is broken. I don't know if it was because they're built using the old GOOP toolkit, or because they were made for LV6i or because they are made for Excel97 ActiveX controls and I've got Excel2003 (different ActiveX, thanks Microsoft )
Anyway, I think that's getting off topic. I spent 2 days trying to fix these installer problems and now I've given up! Because of pressure to get the project distributed I reinstalled LV7.1, restored the backup I made before upgrading to 8.2 and built the exe and installer. When things quieten down here I might try again. Very frustrating.
Troy
Message Edited by Troy Kujawski on 01-19-2007 09:09 AM
09-10-2008 04:29 PM
I am having a similar problem. I am attempting to build an installer that contains the NI-VISA Runtime Engine. I am using a computer that has had several versions of LabVIEW installed (6.1, 8.0, 8.20, 8.21, 8.5, 8.5.1). While building the installer, I was prompted to insert the February 2007 NI Device Driver Disc 3. I went through all of my LabVIEW installation discs. None was the correct disc. After hours of searching, I finally found the correct driver disc - one that was included with some NI hardware that we purchased.
This is unacceptable. I shouldn't be required to insert the exact NI device driver disc that was inserted in my computer at some point in the past. If the current device driver on my development computer is compatible with the source code that I have compiled, executed, and for which I am building an installer, then I should be able to use the device driver disc that I used to install the current version of LabVIEW that is on my development computer.
Ryan Frisch
09-10-2008 06:13 PM - edited 09-10-2008 06:14 PM
Have a look at this thread. It explains what is happening and some suggestions on how to get around it.
http://forums.ni.com/ni/board/message?board.id=170&message.id=329378#M329378
11-14-2013 06:03 AM
I am having the same problem. When creating the installer (with VISA resource), is asked to insert an specific driver disc that no longer exist.
Even with the runtime engine available on internet is no possible to execute serial communications ( that is the pourpose of my VI).
Still looking fo a solution..
Flávio Puhl
11-15-2013 01:30 PM
Hi Flavio,
When you install VISA from a disk, the VISA installer runs from the disk without putting the installer on your computer. To build an installer with the VISA installer in it, you will need to either insert the disk or download a copy of VISA from online (which will include the installer) and point it to that location. I would recommend downlaoding VISA and rebuilding your installer to include it.
If your installer doesn't include VISA, you can install VISA individually on the target machine with your executable but you need to make sure that the version of VISA you install is the version that the executable is expecting.