LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Copy protection with Sentinel UltraPro

Hi,
i'm looking to protect the program I am enveloping with the Rainbow
(SafeNet) Sentinel UltraPro hardware key.
I've found the following problem: if I protect the .exe builded with
LabView, the execution crashes immediatly when I launch the shelled
application.
There's anyone that knows the reason?


Other question: I've read in old newsgroup posts that Rainbow provides with the
drivers some examples to read the key codes... I did find nothing in
my package. THere's anyone that can help me (eventually sending me
these documents)?

Thanks a lot / Mynock
0 Kudos
Message 1 of 6
(4,830 Views)
Hi,

answering to your second question, I did a search on the Rainbow website but was not able to find any reference to LabVIEW examples. PRobably you should better ask Rainbow if they provide any examples for LabVIEW.

As for the LabVIEW .EXE crashing, we need a little bit more info.
- Is your application using any network function?
- Did you try to compile a very simple EXE (adding 2 numbers) and shell it with the Hardware key to see if it encounters the same problem?
- Could you provide a little more detail on what options you use when building the Exe with labview?

Regards,
AlessioD
National Instruments
0 Kudos
Message 2 of 6
(4,815 Views)
Hi Alessio,
my application is not using any network function. I tried to realize the example that you suggest (sum of 2 number) and shell with the HW key. I don't have a crash but the shelled application returns this message: "this is the application template and cannot be run alone". The not-shelled application works properly.
To build .exe i've used the tool Build application or shared library and options are Single target file containing all VIs and Do not compress target file is un-checked.
0 Kudos
Message 3 of 6
(4,804 Views)
I've contacted SafeNet Support about drivers and examples that i did non found in my package.
this is the answer:

We did provide an interface for LabView for our SuperPro hardware product, but there were some instability problems, so the interface was withdrawn. However, we have found that with LabView 7.1, our standard SuperPro 6.3 'C' DLL was able to link seamlessly, provided that _MSC_VER flag is defined in the source code before the include statement for the SuperPro header (spromeps.h). Although it is untested, the same principles should apply for UltraPro. Currently, there are no plans to provide a formal interface for UltraPro in Labview.
Best Regards
0 Kudos
Message 4 of 6
(4,797 Views)

this is the easiest and safest way, to protect labview software:

www.labview-security.com

0 Kudos
Message 5 of 6
(4,046 Views)

You are violating the Terms of Use. Advertise in the appropriate place.

0 Kudos
Message 6 of 6
(4,038 Views)