Installer wrapping NI-DAQ and MAX config

[fungiscience]

Hello,

I want to distribute a LV 7.0 Express application for a customer.

It uses a PCI-6036E card for Data Acquisition together with MAX 3.0.2.3005

on

some computers and MAX 3.2 on others.

All target computers uses Windows 2000.

I need to install the customer application, together with LabVIEW Runtime,

NI-DAQ (supporting Traditional DAQ), the PCI-6036E drivers and import

Traditional DAQ virtual Channels in MAX. The customer want the installation

to

be automatic, so he would like a single installer wrapping all those

functions.

I looked at many tutorial and stuff on www.ni.com and tried some tricks,

but

doesn't seem to work well.

The last installer I manage to build (with LabVIEW 7.1 Development Build

Application and Shared Library) could :

1) Install the customer application

2) Install LabVIEW Run Time

3) Launch the NI-DAQ 7.4 installer (but the installer couldn't function :

either I had a Windows error telling me that the installer couldn't load

everything or either It started sucessfully, but the progress bar was

coming

back and forth, with no progression...but no particular failure)

My last application build is attached to this message. I used a batch file

to

launch the NI-DAQ installer. I included all NI-DAQ 7.4 installer files in

/drivers directory under the main installer directory.

Is it possible to build a complete installer wrapping al of those function

with

LabVIEW 7.1. Can I define Traditional DAQ Virtual Channel with MAX 4.2 on

my

computer even if I don't have the proper hardware and export it to target

computers with the real thing (MAX 3.0.2 or 3.2 with the real PCI device)!

And

can I export those channels automatically within the installer itself.

Thank you,

Sebastien Gelinas

[Neville D]

Don't know if this will help, but if you can upgrade to LV 8x, you can automatically add NI components to the installer for your application like MAX, DAQmx etc.

will save you the hassle of trying to build a global installer with all these components yourself. And why do you have two different versions of MAX? Just upgrade one to match the other.

Also, if you use DAQmx you have the ability to programmatically define channels, so you wouldn't need the virtual channels of the old-style DAQ.

You can also convert old-style virtual channels to equivalent objects in DAQmx called "global chans" or something like that (in NI-MAX).

Neville.