"ian.f" wrote in message news:<506500000008000000B8640000-1031838699000@exchange.ni.com>... > Dear all, > > Have you worked/ come across any programming on software authorisation > using Hardware lock & serial number of PCMCIA card? > > I would really appreciate if you can share your experience here with > me. And, I believe your experience will in turn benefits many others.
The only experience that I have with it is that customers get terribly upset when an entire production line goes down because the PCMCIA card broke and can't be replaced because the software locks them out.
Hi, There is a knowledge base about this entitled "How Can I Read the Serial Number of a GPIB Card programmatically?" That will enable you to read the serial number programatically. The only caveat is that this only works with ni488 1.7 and earlier.
Best Regards, Aaron K. Application Engineer National Instruments
My company uses the volume serial number XORed with a couple of secret numbers to make keys that get stored as a file on PCMCIA cards for customer use. I can't tell you the details because of confidentality, but it is relatively reliable. The only problem you face is training the user to use your special erase function to clean the disk, instead of formatting it, which would erase the file. You can use Labview to read the volume serial number, and then calculate the key file for you, then write the key to a file on that card.
Thanks for putting in your time for this. Actually, I am looking for a sample code which Acquire the Serial Number of a DAQ Card (PCMCIA) and of which way would be the best to use this number for locking purpose.
Do I need to programme it as a constant to check with the acquired s.num?
Basically, I do not intend to create a file and write into the card but to acquire the card's Serial Num and compare it with a constant value (could be read from file) to ensire that the software is use in conjuction with the particular PCMCIA card.
I have simple idea about how to do this. However, any better, if not the best, solution(s) is always welcome.