HOME \ Link \ Download  \  Legal notes \  Contact \ Site map

The most frequent Questions  & Answers
1	Can I protect only the executable version of the software?
2	What's the difference between  HASP4 STD and HASP4 M1?
3	Can I change the password of my  HASP keys?
4	Can  another company product has the same passwords as mine?
5	Can several HASP keys be connected between them ?
6	What happens if the keys are of different trade marks?
7	Can I protect also data files or software developed with non-compiling products  such as Autolisp?
8	Is a NetHASP enough to protect my software in the network?
9	Does the  Envelope utility verifies the presence of a key while using the  protected software?
10	What's the  TimeHASP battery life?
11	How can I modify the memory of an  HASP when it is given to my customer together with the protected software ?
12	How long does the verification of a key last?
13	The language or the compiler I'm using are not supported  by  HASP. How can I protect my software?
14	What is  PCS
15	How can I maximize my protection ?
16	Can I distinguish a single key among those with the same code?
1	Can I protect only the executable version of the software?
	Of course. Thanks to the  Envelope utility,  you can protect your executable file with a high security level in few seconds: Envelope besides automatically verify the presence of a key , ciphers and creates a series of protecting layers   around your software and ciphers it all , avoiding the attacks from possible  hackers
2	What's the difference between HASP4 STD and HASP4 M1 Unlike HASP4 STD, HASP4 M1 has 112 or 496 byte where you can store your data, to personalize the key: for example if you have to protect several software, the same key differentiated by a code in memory  only enables the software corresponding to that code; or, your software is sold with different options: the exe file, equal for all,  only enables those functions which codes are stored in the memory.  If the customer requires further functions ,you can remotely modify  the memory of his key (see point 11).
3	Can I change the password of my  HASP keys? No. To assure the maximum protection  and avoiding the reverse engineering of the hw key, HASP passwords  are  indelibly stored inside the  ASIC component of HASP during it production . No one can read or change these passwords. Other competing products permit you to insert the password: this reduces the security because the passwords can be read and modified by an   hacker; or they can be illegally copied .
4	Can another company product has the same passwords as mine? NO. The password s are assigned in an univocal  way in the world .
5	Can several HASP keys be connected between them? Yes, several HASP can be inserted one inside the other, without particular devices..
6	What happens if the keys are of different trade marks? HASPs are completely transparent. You can insert them before or after other ones  as long as they are transparent too .
7	Can I protect also the data files or software developed with non-compiling products  such as   Autolisp? Yes.  DataHASP permits the ciphering  of data archives.  DataHASP protects the files by ciphering them and enabling only the  software authorized to access them in clear . DataHASP works with all the  HASP keys.
8	Is a NetHASP  enough to protect my software in the network? Yes. NetHASP permit to limit the number of the connected users: you can differentiate the cost of your software according to the number of admitted users .
9	Does the Envelope utility verify the presence of the key while using the protected software?  Yes. During  the producing phase you can define the interval between each verification of the key.
10	What's the  TimeHASP battery life? Up to 3 years if the key is not used. Everlasting when the key is inserted in the parallel port that supplies  and charges the key.
11	How can I modify the memory of an HASP when it is given to my customer together with the protected software?  The RUS tool  (Remote Update System), included in the HASP  sw, permits the remote updating of a key once it is given to the customer. The modification is carried out through ciphered codes (see point 16) that you can communicate to the customer  via phone, fax, email. In this way you can enable other software or functions not activated before?
12	How long does the verification of the key last? For a  stand alone key the verification routine takes  about 20 milliseconds. With the NetHASP, the NetHASP LOGIN takes about  2 seconds, according to the network traffic. Calls to other  NetHASP services take about half a second  .
13	The language or the compiler I'm using is not supported by  HASP. how can I protect my software? Try these alternatives : use the same  instruction of a compiler with the same object file type as yours  use the DLL (for  Windows or OS/2 software)  use  HASP Resident Drive ( DOS software) use  Envelope utility  contact us:  new interfaces   are continuously added to the  250 already supported by HASP.
14	What is  PCS The Pattern Security Code is a function that permit to automatically insert in your software a series of false calls to the key; this creates a  "background noise" that covers  the true ones making things difficult for the  hacker: it will be hard to distinguish the true call from the false ones .
15	How can I maximize my protection? PCS (Pattern Code Security) increases  the security level of your protection. An entire chapter of the " Guide to the use of HASP" answers this question.
16	Can I distinguish a single key among those with the same code?
	Yes. All the memory keys have an univocal identifying code  (ID) that permits to address them individually. This  ID is essential for the RUS (point 11) as the codes to update the memory  of the keys are ciphered  with ciphering key function of ID