LabVIEW
how to create a labview interface to simulate a key hasp
From what you described, you will need more information on the HASP key that you have to communicate with (if you don't have information on that HASP key, first you'd have to find that out from someone or look it up on the internet and see if manufacturer has any information). I say that because as Rolf mentioned, you'll need DLL files (or some sort of API library which allow communication with that HASP key). Once you have such library files (or any information on how that HASP key requires communication), you can use LabVIEW to communicate with them using "Library calls". If the HASP key manufacturer provided you with information on how to communicate (for example, if it is a USB key, you can use VISA drivers in LabVIEW to communicate as long as they provide you communication protocol - that is, what you send to the key and what it responds back with, etc).
It's like using a special video card with your computer- once you plug in the card inside your computer, you'd have to load software drivers so that your operating system can "communicate" with that video card to get its full features benefit. Same way, you need "software driver" (DLL or API calls library, etc) of your HASP key for LabVIEW to be able to communicate with it.
In any case, your first step would be to get all details on your HASP key itself.
-DP
As I already told you Hasp delivers an untility with which you can wrap an executable so it is protected from execution with the hasp Key. This is simple and does not stand much of hacking so if you want to go further than that, Hasp delivers an API SDK with DLL (and nowadays possibiliy ActiveX/.Net interface) to integrate into your application. I have only looked into the DLL API interface many years ago, and am sure that that API has since been superseded by many new versions and key technologies, so even if I had done something to post, it would certainly not work with actual keys they sell.
So you have to get from Hasp the API SDK that matches with the key family you want to use. And be prepared that future key families might require an entirely new SDK to interface to.
The API SDK contains informations on what functions you can call and how and that is where you will need to look at. If they have an ActiveX or .Net interface that would be certainly easier to interface. If you decide to use the DLL interface then you should know some C programming basics and be prepared to crash your system quite a few times until you get something working. I can't really give you more information than this as I have never really interface to either Hasp or any other similar hardware key, only ordered the SDK from Hasp some 10 years ago and studied what would be required to use their keys.
