Bandit

Right.

Job done. Driver mismatch was the problem. Installations on NT and XP now work.

But I'm getting the NT target replaced with another XP target to ease deployment of the next release , and enable me to use latest vision dev tools and drivers.

Thanks to Jacemdom and Crelf :thumbup:

Bandit

Did you install the NI-IMAQ drivers on the target PC?

Yes, but since my post I noted this...

On my development machine IMAQ is at 3.5.0, but on the target machine it's at 3.1.0.

I don't actually want to go as far as 3.5.0 as it doesn't support Win NT. In the end one of the targets for my app is an NT4.0 machine.

I don't know why my development machine has IMAQ 3.5.0, as the vision development module 7.1.1 CD installed to it only has IMAQ 3.1.0.

I think I should roll back the development machine, but I'm not sure if this could cause a further problem. These are just the hardware drivers, right?

Hi,

I'm deploying a vision application (LabVIEW 7.1.1, Vision development module 7.1.1)

I have both the LabVIEW and Vision run time engines at 7.1.1

When running the installed application on the target PC many NI vision vi's used are not found.

Most are solved by including libraries in the build, but one isn't.

imgCopyAreaWithOccur.vi (used in IMAQGrabAcquire.vi) can be found in DLLcalls.llb.

However, if I include either imgCopyAreaWithOccur.vi or the full library DLLcalls.llb in the installer, the vi is still listed as missing.

Any ideas where I'm going wrong? :headbang:

(As you may have spotted by now this is a duplicate of a post on the NI discussion forums.)

Its my first deployment of a vision application, though I have successfully deployed non-vision LabVIEW apps before.

Thanks

Bandit.