Jump to content

Gribo

Members
  • Posts

    237
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by Gribo

  1. Neil, While LV is not used in any financial role that I know of, it is used in many industrial applications. You don't want to be the one that enabled the next Flame/Doku, the same as Siemens didn't want to be the first, when their engineers said it is not their problem.

  2. There is also an .INI file which directs to the API install path. It has just one line. C:\program files (x86)\signal hound\spike\api. I verified that the generated path is ok. Rolfk, this might explain why the same code works with the invoke nodes having the DLL path predefined. It should have behaved the same in both cases, or, at least report a file not found error (#7). I even tried placing the DLL in the same directory as the executable, which is one of the location windows searches for them, and got the same error.

  3. Hello,

     I wrote an application which can use either a 32 bit or a 64 bit dll, it loads the dll from a path specified in an INI file. This code works properly on the development machine (LV2013, both 32 and 64 bit, both with a debugger and as an EXE) but doesn't work on the tester machine as an executable. It throws error code 13 (in LV2013 - file is not a resource, in LV2014 - Failed to load DLL due to invalid format or missing dependencies). 

    However, when I change all the Invoke nodes to use a static predefined path, everything is OK.

    What am I doing wrong here? I rather maintain one code base and build for each target than maintain a code for each target.

     

    The API dll is from signalhound.com http://signalhound.com/spike

    post-46572-0-18482600-1440600902.png

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.