Problem after a build application and "missing" *.DLL file...??

[keng]

Hi all,
I believe that this problem has been discussed before in this forum. Does anyone knows how can I make it right?
Obviously my codes work all right in the Labview environment (developer machine) but when I have build and created an EXE and setup it up in another PC, it gives me these errors.

To demonstrate my problem, please view my attached error messages.

[asimpleman]

I would open up these vis and see what dll's they are calling. Then fully
search both machines for that filename. Hopefully there will only be one
version on the machine that is working. Make sure that the one(s) on the
machine that isn't working is the same size and date. And if there is more
than one delete the extras (back them up though).

"Juni76" wrote in message
news:50650000000800000079620000-1031838699000@exchange.ni.com...
> Hi all,
> I believe that this problem has been discussed before in this forum.
> Does anyone knows how can I make it right?
> Obviously my codes work all right in the Labview environment
> (developer machine) but when I have build and created an EXE and setup
> it up in another PC, it gives me these errors.
>
>
To demonstrate my problem, please view my attached error messages.

[keng]

Hi Adam,
Thanks for answering my problem.
I have checked many times the build path, vis and also the DLL files. I have included them in my build directory.
Unfortunately, I can't load my program properly in another PC. For your information, the PC is running OS Windows 95.

My program consists of 2 top level Vis. They are the Main.vi and Capture reading.vi. The capture reading.vi consists of initialization.vis (which uses the CaLL Library Function = fl8840a_32.dll , which is my error) and they are running linked to the Main.vi under an environment called "thread.vi".

My problem is that, the OS can't read the DLL file even though I have build them in C:\windows\system\ *.dll or C:\Program files\Folder name\data\ *.DLL

I am still not sure why it c
an't read the *.DLL??

Any idea?

Thanks,
juni

[Matt_K]

In your call library node path box, don't specify any path but rather just the name of the dll. Then on the target machine, make sure the dll is located in the windows system directory. LabVIEW should then look in the OS search path for the dll and it should be found.

[asimpleman]

"Juni76" wrote in message
news:5065000000050000002EAD0000-1031838699000@exchange.ni.com...
> Hi Adam,
> Thanks for answering my problem.
> I have checked many times the build path, vis and also the DLL files.
> I have included them in my build directory.
> Unfortunately, I can't load my program properly in another PC. For
> your information, the PC is running OS Windows 95.
>
> My program consists of 2 top level Vis. They are the Main.vi and
> Capture reading.vi. The capture reading.vi consists of
> initialization.vis (which uses the CaLL Library Function =
> fl8840a_32.dll , which is my error) and they are running linked to the
> Main.vi under an environment called "thread.vi".
>
> My problem is that, the OS can't read the DLL fil
e even though I have
> build them in C:\windows\system\ *.dll or C:\Program files\Folder
> name\data\ *.DLL
>
> I am still not sure why it can't read the *.DLL??

Try checking with the manufacturer to see if there is a dll specific to
win95.

[asimpleman]

"Juni76" wrote in message
news:5065000000050000002EAD0000-1031838699000@exchange.ni.com...
> Hi Adam,
> Thanks for answering my problem.
> I have checked many times the build path, vis and also the DLL files.
> I have included them in my build directory.
> Unfortunately, I can't load my program properly in another PC. For
> your information, the PC is running OS Windows 95.
>
> My program consists of 2 top level Vis. They are the Main.vi and
> Capture reading.vi. The capture reading.vi consists of
> initialization.vis (which uses the CaLL Library Function =
> fl8840a_32.dll , which is my error) and they are running linked to the
> Main.vi under an environment called "thread.vi".
>
> My problem is that, the OS can't read the DLL fi
le even though I have
> build them in C:\windows\system\ *.dll or C:\Program files\Folder
> name\data\ *.DLL
>
> I am still not sure why it can't read the *.DLL??

I can't read previous messages so I can't see if this might already have
been covered. When installing on a new machine you may also need to install
gpib driver, visa engine, and daq drivers depending on the application.
This is the kind of thing that's easy to forget if you don't do a new
machine installation for a long time.

[keng]

Hi Adam,

I am writing to program to make use of some instrument devices which are used for measuring data. I have installed most of the drivers such as the NI 488.2 and the VISA v2.5 on the target machine. I have also installed LabView Run Time Engine 6.02 on my target machine

I have tried to delete all other similar size and date of the missing DLL file (back up). Actually the file is not missing and it is there in the windows\systems\ directory, but somehow the target machine doesn't want to read it.

Having said that, I tried not to include the file.dll in my build and manually set it when installed on the target machine. At first the target machine tried to locate it. I would have to manually direct the PC to the file. When the
file is located, but the Load error 21 still occurred.

When I was finally to give up, I tried again this time by having installed the Labview v6.02 on the target machine. To my delight, the error was no more. I checked the installation file and I found out that, the target machine have now a LabView Run time engine v6.0. I believe some of the setup files in Labview could have provide the solution in my program on the traget machine. This is the best bet of my diagnosed of my problem.

Anyway, I would like to thank you for participating in solving my problem.

Regards,
juni76

[keng]

Hi Matt,

Thank you for participating in my problem. I have done what you have suggested. I put all my file in the folder project (on a network drive - build PC). I tried to remove the path to the file.dll in the path section. But on my build PC doesn't let me do it. It always return to the folder project path.

Then, I tried to relocate the file.dll to my build PC ( C:\windows\systems\). To my delight, the path is now only set to the file.dll and no path is specified. Then I tried to build the codes and install the exe file on the target machine. Unfortunately, it doesn't work.

Anyway, my problem has been "solved" when I installed the full LabView program on the target machine.

I have posted my finds to this site, you may read it on my reply to Ada
m's comment.

Anyway, I appreaciate for you help into my problem.

Regards,
juni

[CoryJCI]

I actually encountered the same problems you did with creating an application from Fluke 8840A instrument drivers.

I got my application to work on a target computer by installing NI-VISA, NI-488.2, LabVIEW Run Time Engine, and the IVI Engine. I was getting LabVIEW load error code 21 when the IVI engine was not installed on the target computer as it was on the machine used to build the application. After installing the IVI engine on the target machine, the VI application finally worked.

So it is possible to use NI instrument drivers in an application on a target computer without installing the full LabVIEW package.

Hope this help even though it is 6 moonths later.

Regards,
Cory.