Where to install LV6 VI Library?

[Ed Thompson]

I am working on an installation program for my LV6 I2C Bus host adapter VI
library. I was going to install my library folder in the path Program
Files\National Instruments\LabVIEW 6\instr.lib, but this might not be the
correct path on every machine or correct for future versions of LV. I'm
using InstallShield, and it needs an installation path. Is there a better
place or technique.

Thanks...Ed

[JeanPierre]

If the installation is not too involved (copying few files), you can put in the VI Library a Top Level VI that will copy the LLB and installation files in the right place. All the end-user has to do is to double-click on the distributed LLB. You set the Top Level VI to run when opened and to display a splash screen for your product and offer to install it in the LabVIEW directory. You know the LabVIEW directory reading the "VI Library" file constant.
I use this technique to distribute plug-ins LLB since LabVIEW 4.1.
Jean-Pierre

[Dennis_Knutson]

Doesn't InstallShield have the ability to read the registry and determine the current version (HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW\CurrentVersion). You can then make the default install path relative to that.

[MichaelAivaliotis]

I've used Installshield Express to do this but I assume Installshield (IS) has this same functionality. You can tell IS to take the INSTALLDIR path from the registry. Specify: "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW\CurrentVersion\Path" as the registry entry for LV6.0. However, you should give the user the option of confirming this in case something goes wrong. I've been using IS Express for several months to install LV drivers and LV applications so if you need more info let me know...

[Ed Thompson]

Hello Michael,

Thanks for your help. I am using IS Express V2.12. You have described
exactly what I want to do. However, I cannot find a place to tell IS to take
the INSTALLDIR path from the registry. When working with IS, I sometimes
switch back and forth between the IS Express app and just editing the .iwz
file in notepad, so I am pretty familar with it. But this has got me
stumped. Can you help?

Thanks...Ed


"Michael Aivaliotis" wrote in message
news:5065000000050000004F4D0000-1004225886000@exchange.ni.com...
> I've used Installshield Express to do this but I assume Installshield
> (IS) has this same functionality. You can tell IS to take the
> INSTALLDIR path from the registry. Specify:
> "HKEY_LOCAL_MACHINE\SOFTWARE\National
> Instrum
ents\LabVIEW\CurrentVersion\Path" as the registry entry for
> LV6.0. However, you should give the user the option of confirming this
> in case something goes wrong. I've been using IS Express for several
> months to install LV drivers and LV applications so if you need more
> info let me know...

[MichaelAivaliotis]

OK, well I've attached a BMP image of my IS Express screen. I've narrowed it down to the field of interest. I'm using V3.5 but I don't think it's that different.

I can't show you anymore of the screen due to confidentiality issues but I hope this clarifies it.

[Ed Thompson]

Hello Michael,

I found the (undocumented) information on the InstallShield Knowledge Base
(Q101697). Works great.

Thanks...Ed

"Michael Aivaliotis" wrote in message
news:5065000000050000004F4D0000-1004225886000@exchange.ni.com...
> I've used Installshield Express to do this but I assume Installshield
> (IS) has this same functionality. You can tell IS to take the
> INSTALLDIR path from the registry. Specify:
> "HKEY_LOCAL_MACHINE\SOFTWARE\National
> Instruments\LabVIEW\CurrentVersion\Path" as the registry entry for
> LV6.0. However, you should give the user the option of confirming this
> in case something goes wrong. I've been using IS Express for several
> months to install LV drivers and LV applications so if you need more
> info let me k
now...