02-21-2006 07:58 AM
02-21-2006 08:33 AM
If I provide the installer with a directory for an old installer, this seems to be OK. But why should my old installer interfere with a brand new one? What if I didn't have a backup copy of this old installer?
-Christian
02-21-2006 09:26 AM
02-21-2006 09:34 AM
Thanx.
I have tried that one. I have tried to provide it's location on the driver cd and I have downloaded the latest driver to C:\National Instruments Downloads\NI-CAN\2.3.2 and given that path. This should work, but it doesn't. Something else I am missing?
02-21-2006 09:38 AM
02-23-2006 06:12 PM
Christian,
I think I know the root of the problem you're seeing, but it is a little lengthy to explain so bear with me. When you include additional installers (like DAQmx or CAN) through the Application Builder, LabVIEW \ CV \ TestStand looks for the original source of that driver. When you installed your drivers initially, your computer "learned" and "remembers" that the source is on the Driver CDs. The Application Builder requires the original (not the installed) files on those CDs so that they can be wrapped up into the new installer you're building.
So when you create your installer and provide the source CD (the last know location of the driver source) everything is grand. The problem arises when you install your installer on the computer you did your development on. When you install your new installer, it reinstalls the drivers you've included in that installer. So now your computer "learns" and "remembers" that the source of your installed drivers is from the installer you just made, in your case "Setup.exe". (I think I've used the word installer 50 times so far....).
So now when you try to create a new installer, the Application builder is going to look for the last, known source of the drivers, which is in your case "Setup.exe". Well of course, you don't want that! You want your computer to know that the source files for your drivers are in a CD, not in some installer you've made. To "reteach" your computer to look on the Driver CD, you'll need to uninstall the NI-CAN driver (and any other drivers you included in the installer you made) and then reinstall them from your Driver CD.
Further more, if you had created a new installer and overwritten your first installer, you would have been in a real pickle! Your computer would have tried to look for the first installer as the source of your drivers to include in the second installer, but you would have overwritten it and been up the creek!
To avoid this problem NEVER
02-23-2006 06:20 PM
02-24-2006 02:38 AM
02-24-2006 02:49 AM
03-16-2007 09:03 AM
Hi again,
I obviously still have this problem and LV asks for an old installer which I have overwritten. What can I do? I have tried to uninstall and reinstall the NI CAN driver, but application builder still asks for the old selfmade installer. (which I don\t have anymore!!!!)
Please help...