How does the Distribution Kit work?

[Farside]

I am trying to install a D-Kit on a Target PC that will only receive the RunTimeEngine. The only Interface card installed in my PC is a PCI-DIO-96. When I enter the T&M Explorer via the Test Panel, I can successfully Write to the DIO ports. However, I have been unable to get a Release Executable to run on the Target PC. The RS232 communication works but the DIO card appears not to respond. I have lengthened the Delays between the "WriteToDigitalPort" calls but that has not helped. I have also tried adding the "easyio.lib" under the Target Settings for the LoadExtModules but this does not make any difference. I have also added the "easyio" file to the support executable File Group under Create Distribution Kit. Somehow I am missing s
omething in the build. What makes the Release Executable so different? Could I be missing a ".dll"?

[AaronK]

Hi Farside,

When you say that you have been unable to get a Release executable to run on the Target PC, do you mean any release executable? If you were to create the standard �hello world� program and package it into a distribution kit, would that crash or not start? If so what error message does it give you? One last question: Does the release executable run correctly on the development machine?

Debugging information is the main difference between a release executable and a debug executable. In a release executable, no debugging information is included in the exe. The debugging information allows you to set breakpoints and help you locate where your program may have crashed among other things. Debuggable executables are much larger than release executables du
e to the extra information they store.

Best Regards,
Aaron Kobayashi
Applications Engineer
National Instruments
http://www.ni.com/ask

[Farside]

My Release executable does run. However, I receive an Error message whenever I perform a "WriteToDigitalPort" command. This command is supported through the "EasyIO" library. I have tried adding both the "easyio.lib" as well as the "easyio.lfp" files to the File Group during the D Kit build. I have also included, as well as excluded, the easyio in the Library Options during a build. It does not seem to matter though. The error message: " -10240   noDriverError   The driver interface could not locate or open the driver.." continues to appear. I have also looked through the CVI manuals tryinig to find a description of how a DLL file should be added but have not found much. Any suggestions?

[WesW]

Greetings,

Another possibility is that you have a missing or damaged NI-DAQ or MAX on your target machine. Currently, the CVI distribution kit does not install your NI-DAQ drivers or configuration on the target machine - you have to do it manually. I would recommend reinstalling NI-DAQ and make sure the device configuration in MAX is the same on both machines.

Regards,
- Wes / NI

[Farside]

Wes:

That was part of my original problem. I had installed the entire development suite on the Target PC. NI-DAQ had been initially installed prior to the CVI install. I then debugged my code, then removed the Development Suite. In the process, not realizing Folders were shared, I deleted portions of the NI-DAQ SW. I have since restarted from scratch. I reformatted the HardDrive, reinstalled all of my Hardware drivers for the PC. NI-DAQ was then installed without the CVI SW. When I go to the Test Panel in MAX, the DIO card performs satisfactorily. It is only when I go to a release executable that I receive the -10240 NoDriverError during the "WriteToDigitalPort" command. This particular command is part of the EasyIO library. I have tried adding the
".lib" as well as the ".lfp" files to the same folder as the executable but with no success. Any additional suggestions?

[Farside]

I discovered the error to my problem. It was as simple as adding the correct DLL file to the File Group that my executable was in. Thanks for all of the assistance!

[AaronK]

Great! What DLL did you have to add?

[Farside]

AaronK:

The specific file was "niezio.dll". Although I had tried several different searches for 'dll' files, I inadvertently limited the search criteria to "easyio" since the library and function panel both used "easy" instead of "ez".