Build Installer with add-ons

[biographie]

I have recently been building some applications and building installers as well.  I have to include other pieces other than the run-time engine (max, visa, etc.).  When I check those installers I noticed that it calls out for the device driver discs from Feb 2006 (that is when I got the developer's suite).  So, I blow it off thinking that I have the last discs from May 2006 (which I noticed grew from 2 sets of discs to 3).  I start the build, and it pops up a window asking for the Feb. 2006 disc 1.  I put in disc 1 from May, it doesn't like it.  I hunt down the Feb. 2006 discs, and all is well.  Why does it need the old discs?  Shouldn't the installer be able to run off the latest quaterly update discs?  It causes a real headache to keep around multipule copies as I get my quaterly updates.  To solve my problem for now, I copied the two device driver discs on my hard drive, and point the installer to those directories when it asks.  It likes that just fine, but I would perfer that it work with the newer stuff as it comes out.

[Kenny_K]

I know that this seems obvious, but did you install everything (max, visa, etc) from the MAy 2006 discs (or at elast update) ???

It may be that one of the item was not updated and it defaults to the old version.

Kenny

[biographie]

I have not run the new quaterly update discs.  I didn't even think about the fact that minor changes may have been made to each of these components.  I typically only keep an eye out for the bigger updates (i.e. - labview 8 to 8.0.1).  I guess I will pop those discs in the machine and let them run.  I guess it does this a method of source code and version control.

[Charlie S.]

Hello,

LabVIEW 8.0 does not automatically cache the drivers when you install them on your machine; thus, when you create an installer that includes additional installers the application builder will prompt you for the source from which you installed the drivers. The way the MSI meta installation works means that it will prompt you for the original source of the install. Each of the driver CD's contains new, updated versions of the NI drivers and the application builder recognizes this. You can find more information about this here:

http://ae.natinst.com/operations/ae/public.nsf/web/searchinternal/7F7744CE38526485862571B9006C181C?O...

To solve your problem, you'll have to install the May version of the CD if that's all you have to build your installer....or you can revert to your Feb. version.

Hope this help!

[Kennon_Cotton]

FYI, In LabVIEW 8.2 when you are prompted for the source of an installer the is a check box to optionally cache the installer on your local hard drive.  This does mean copying everything needed to your <National Instruments>\Shared\ProductCache folder, so it takes some disk space but it does remove future prompts for that particular source installer.  It doesn't copy the entire CD just the pieces that are needed from the CD.

Kennon