Leaderboard

Awesome!

Well, for what it's worth, Tom and I both used Actor Framework, so thanks for that.

I recall this code from the NI forums. https://decibel.ni.com/content/docs/DOC-19720 I downloaded the example and noticed that the DLL call includes the path to the file user32.dll Check the locations of the shared library in your VI. It may incorrectly include the path... From the NI help: ( http://zone.ni.com/reference/en-XX/help/371361J-01/lvexcodeconcepts/locations_for_shared_libraries/ ) To specify the location of a shared library, you can enter the name or path in the Library name or path text box of the Call Library Function dialog box. You can also wire the name or path to the path in input of the Call Library Function Node. Caution Do not specify the location of a system shared library, such as kernel32.dll, by path. Because LabVIEW automatically includes by-path shared libraries in build specifications, you might distribute a system shared library to another computer inadvertently. Redistributing some shared libraries, such as kernel32.dll, might cause the target computer to crash. Therefore, always specify system shared libraries by name.

PSY may have just been de-throned !!!

I'm going to learn LabVIEW. So I can come to NIWeek with you.

ไม่หึง.ไม่รัก

I thought you were referring to the network term CLNS (Connectionless Network Service), but you mean of course Call Library Function :-) I'm avoiding those since I want it to be platform independent. Shaun, I owe you a beer :-) Come by Symbio’s booth at NI-week or catch me at NI-week. You did put me in the right direction to solve the problem. I'm not using any DLLs directly, but I'm using the Mouse Vis in the inputDevices.llb Since These VIs don't work/exists on Mac or Linux, I have to create a wrapper around then and load then dynamically. And just by disabling the code in this VI it worked. I’ll see if I can figure out a different way of solving this.

I've always found the TCPIP to be rock solid (at least as far as crashes). Look for CLNs.