Well, David's solution works as expected. It copies the the pristine .lnk file from the startup menu to the desktop.
This .lnk file will start only the operator interface testexec.exe without loading any sequence.
Now I did try a modification. I did create a .lnk file, which loads the sequence file automagically by providing the right commandline arguments to testexec.exe. This .lnk file works on the development system either I start it from desktop or from some normal directory with the explorer.
And now I try to add that .lnk file to the deployed files like all other deployed files by adding it to some project in the workspace, which is configured to be used in the deployment wizard. That doesn't work.
If there is a 2kb "MySequence.lnk" in t
he development tree,you will also find a "MySequence.lnk" in the Image tree at the expected position. But this is 1396 kb big, which is just the size of testexec.exe ( Labwindows/CVI version) where the .lnk file did point to. And the properties (commandline) of that .lnk file became empty.
Other "normal" files in the same directory, which are also included in the deployment, are copied without any coruption into the Image tree into the same directory as the corupted .lnk file.
The installer will install the corupted .lnk file to the desired position without problems. And copying it with post.bat to the desktop is also no problem.
