Deployed Application requiring lksock.dll?

[bob_miller]

I have developed an application for deployment on Windows XP(pro/home)machines which provides a
remote front panel interface and analysis package to another application running on a fieldpoint
on the local network or on a remote dial-up network. This application works fine (as a standalone
application) on a machine which also has a LabVIEW development system installed, but I get a run-
time error indicating "missing lksock.dll" on a non-LV-equipped XP box.

Searching for lksock.dll on the LV machine reveals the file in C:\WINDOWS\system32\ and the
pop-up file description indicates "part of Logos 4.0" and "National Instruments".

How should I solve this problem? The application uses (to my knowledge) only those DSC features
which require no additional run-time license. It communicates with the server application via
TCP and FTP VIs and also employs the DSC security features not requiring the DSC run-time engine.

I am worried that if I simply add this dll file to the installer list I will only fix the "first"
problem, or worse, I will mess up something else in the target computer, contravene my Labview
license agreement, or otherwise end up in "a maze of twisty little passages, all alike"...

Please help!

Bob

[bob_miller]

A few additional comments/corrections:

The dll mentioned is apparently part of Logos 4.5.1.601, not "4.0".

By trial and error (on a LV machine) moving all lk* files out of the
system32 directory and back in as they were complained
about, I have identified lksock.dll, lkdynam.dll and lksec.dll
as the required dlls for this deployed application.

So, unless I violate the LabVIEW DSC license agreement by doing so,
what is the best way to bundle these dlls into an installed application?
As I indicated earlier, I don't think I'm trying to use any DSC features
not deployable w/o a DSC run-time engine license.

[bob_miller]

To follow up here for posterity (gee its lonely responding to my own
posts!): NI support contacted me and indicated it was OK for me to
include the DLLs as support files in the installer. But something
else they said made me realize the source of the problem.

Turns out I had probably gotten too ruthless in the installer build
configuration and, along with a host of stuff like report generation
support had possibly excluded some pieces of DSC that my app needed.
Since the Logos dlls were installed on the machine I originally tested
the deployed application on, I discovered no problem until attempting
to deploy to a non-LV_DSC-equipped machine.

So the moral is: Don't assume your deployed application is self-sufficient
until it installs and runs on a machine that has never seen LabVIEW
before, and don't get too ruthless in trimming stuff out of the build
you don't think you use (and the forget you did it!!!).

Bob