fileselectpopup not finding files after a a Hard drive replacement

[Alan Perry]

After a harddrive failure on a test rig we replaced the hard drive, installed Windows NT, Service Pack 6a and then copied the development directory for our program to the new drive from a back up.

When FileSelectPopup tries to show some input files it returns "No Files Found".

CVI had been removed from the drive years ago so I believe some critical part of CVI that get's left behind normally has not been carried over to the new drive.

On trying to get a proper install package out of CVI on the only Dev PC with Measurement Studio still installed on it we find it fails to compile with "undefined symbol _AO_Configure" errors (and DIG_In_Line, DIG_Out_Line etc)

What needs installing on our Dev PC to over come this?

Thanks

[baker_matt]

I seem to rember that the functions you are referring to are in the easio library which as far as i can tell somwhere along the the line got killed in leu of the DAQmx stuff. See if you have easio.fp (or easyio.lib) included in your project. Note that this library uses niezio.dll (I think, well its close to that anyway) and not easyio.dll (which does not exist. If not repost and I can get them to you, my app still uses these libraries so I have had to carry them along.

[bilalD]

Those functions look like Traditional DAQ functions. Make sure you download the NI-DAQ driver and install Traditional DAQ with support for CVI.

Hope this helps

[Tristan_J]

Alan,

If you are performing data acquisition on the Rig, you will need to ensure that you have re-installed the Traditional DAQ or NI-DAQmx drivers back onto the new harddrive (depending on how your application was written).

If you do not have the drivers on CD, the latest ones can be down loaded from the link Below: http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/2473339b54f5b34286256f380059d35b?OpenDocument

Please re-post if you have already done this.

Kind Regards

Tristan
Applications Engineer
National Instruments UK & Ireland

[Alan Perry]

Thank you all for your quick replies.

I believe it could be as simple as not seeing the required DLL on the Test Rig

The drivers (NI-DAQ) will be removed and installed again on the Test Rig.

I will do the same on the Dev PC.

In both cases making sure support etc for CVI is installed etc...


Thanks