Distribution Kit with User-Decisions and User-Inputs

[jumbojetjames]

hallo group,

I know: the CVI-distribution-kit-builder has only basic functionallity.

-->but: is there a possibility to include some one-time-user-decisions or user-inputs into the running installation process?

-->now I use the following workarround:

at every start the INSTALLED software searches for a certain registry-entry and if this is not found the user is asked for the interesting things (company-name etc.) and decisions. at the end of the "interview" the registry-entry is setted.

-->this works but isnt very nice. any idea or experience?

best regards

Simon

[jr_2005]

I use CVI 7.0. As part of the distribution kit build process (click the Advanced button), you can specify a file to be executed (.exe or .bat) after installation completes. I have used this in the past to customise an installation in a similar manner to your description.

JR

[jumbojetjames]

JR,

yes, think I saw this in previous versions of CVI, but I cant find such a possibility in 8.0 ? or am I blind ?

best regards

Simon

[menchar]

Add the file you want to launch into the distribution using the installation editor, then right click on the file name in the lower right pane of the installation editor  and it'll bring up a context menu with an Options selection that you can use to specify the launch.

Menchar

[Mert_A.]

The file options dialog also comes up on a double-click or by pressing Enter, just for those with aversions to right-click menus. 🙂

Mert A.
National Instruments

[jumbojetjames]

thanks, I' ve found it. is there a possinility to set the order of running the various programs (or pack them in a bat-file) ?

best regards

Simon

[jr_2005]

My approach was to include all actions required into a single batch file which CVI could call after installation. This in turn ran whatever other programs, batch files, system commands etc that are required for the customisation.

You need to be just a little careful if any of these actions results in modifying any files that CVI has just installed - it can be the case that CVI has not released the file handles by the time it calls your application. There was a thread here which discussed this problem.

JR