making a distribution disk

[oultramc]

Hello
I am using labview 7.0 to make a distribution disk.
I have followed the steps in the guides and I have created the installer and all its related files.
I can run the installer and create a single *.exe file, and a *.ini file in my Installation sub dir.
When I run the *.exe my PC just gets swamped with VI's, about 256 all opening up at the same time.
Can anyone explain what is happening, whether this is the norm - though I would say not. And most importantly what I need to do to get a sensible outcome
Thank You
Chris

[Dennis_Knutson]

It's certainly not normal. When you did the build, did you add a single Top-Level VI or do you have multiple top level VIs? If you can reproduce the problem you're having with a just a main and a couple subVIs, can you attach those and the .bld file?

[oultramc]

Hi Dennis
Thanks for the reply.
I had all my VI's as top level VI's, which may have been the cause of the problem.
The reason behind this selection was I don't really have one top level VI. The VI's are Labview versions of individual GPIB commands, all of which need to be visible to update and query the instrument configuration through Labview
I also have VI's that are designed to set up and take measurements, I built an "exe" for one of these and got a result that I was expecting, ie when I installed and ran the exe, only the one VI was opened, and was executable.
It would appear that I will have to create lots of "exe's", or I will have some redesigning to do to be able to distribute all the configuration commands.

Thank You

[Dennis_Knutson]

Naming all VIs as top level is certainly the cause of your problem. I think you can create a single top level VI that will call your GPIB functions as required. Can't you have a menu of options that the user selects and shows them on demand? What about doing some sort of plug-in architecture? There's a shipping example called Plug In Example that might serve as a model.

[Steven Bird]

Hello Oultramc,

The comments below is most probably what is cauing the problem, however another thought is that the SubVI node setup for each VI could also be set to Open when called. Right click each VI to ensure this is not the case.