aladdin hardlock and LabVIEW?

[Steve257]

Does anyone have a VI to allow a LabVIEW VI to look for the presence of a correct Aladdin Hardlock?  We're about to distribute some compiled VI's as products, and we'd like to protect them from unauthorized use/copying utilizing our existing Aladdin Hardlock system.

[muks]

This is what i got searching the forum

[Britoa]

If you haven't already yet, contact the people at aladin about it and get a dev kit.  There are examples (in C++/#) that are pretty easy to follow for learning what to do and in what order.  The DLL they give you is .NET based, so if you use a .NET constructor, you can access most of the functionallity.   

I sadly can't post our code (it's too embeded in our work right now) but that should get you going pretty well.

Also: The DLL "hasp_windows_demo_master.dll" NEEDS to be in with the VI/EXE for it to function correctly. 
Otherwise the error 400: HASP_NO_API_DY_LIB happens during login.   (this is a comment in my VI, I guess that when we get our own hasp master dll, that will need to be there instead.)

[Steve257]

Well, on the Aladdin site, there is  a zip file for "LabWindows Demo".  I'm guessing that this is where the DLL's that Britoa mentions.

But, I'm somewhat inexperienced with LabView, and am not sure how to call DLL functions from inside a VI?  Anyone want to point me in the correct direction (sample code - hint hint)?

Steve

Message Edited by Steve257 on 09-16-2008 01:58 PM

[Kevin_S]

Hi Steve257,

In order to call methods from a DLL in LabVIEW, I would point you in the direction of the Call Library Function VI. 

If there is a header file along with the DLL, you can import the DLL into LabVIEW for even easier access to the methods.  (Tools » Import » Shared Library (.dll))

I hope this helps,

Kevin S.

Applications Engineer

National Instruments

[Steve257]

That 'sounds' easy enough...I'll give it a try and let you know how well I do.

[Britoa]

The dll that I have is .net based, so if you go to connectivity-->.NET, put down a constructor node, and select 'browse' when asked, selecting the dll, it should give you a much easier interface.