I had problems like that once using a similar hardware security key. The problem as I understand it is that a LabVIEW executable is not a 'true' executable (people who know better are invited to clarify). My solution was to use calls to the key from within my (LabVIEW) code to check for the presence of the key.
Johann Junginger. -----Original Message----- From: Reed, Christopher [mailto:[EMAIL PROTECTED] Sent: Monday, March 22, 2004 01:42 To: LabVIEW Mailing List (E-mail) Subject: [W] Sentinel SupePro Automatic Protection Dear List, A while back there was some talk about using LabVIEW drivers for Integrated Protection with the Sentinel Security Key from Rainbow Technologies. But has anyone managed to use Automatic Protection (ie. wraps a security shell around the LabVIEW executable) on a LabVIEW program? Everytime I try to run a "protected" LabVIEW application it just displays the message..... "This is the application template and cannot be run alone" Technical support from Rainbow are a bit baffled with this since they have not heard of a programming language called LabVIEW and so are not really sure what the problem is. Chris Reed Development Engineer Department of Engineering & Medical Physics Royal Perth Hospital Tel: 61 08 9224 2953 Fax: 61 08 9224 1138
