| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| 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. |
|
#2
| |||
| |||
| <a href="http://forums.ni.com/ni/board/message?board.id=170&thread.id=125838" target="_blank">This</a> is what i got searching the forum |
|
#3
| |||
| |||
| 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.) |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.