OpenHASP Return codes:

Unix HASP Installation

This document is of interest to customers installing APPX on an Intel/Unix platform, such as Linux, SCO, and NCR Unix.

Because Intel/Unix systems don't enforce unique CPU serial numbers, it is necessary to install an OpenHasp on a serial port by itself, identify the port's address, and set an environment variable to identify that port address. Note that as of Release 4.1.8, APPX for Linux licenses may be registered by Ethernet card MAC address.

(If you are installing a HASP on a Windows system, see this document.)

HASP Installation:

1. Make sure that the serial number printed on the HASP label matches the serial number on your registration document.

   If they do not, please call APPX Software for a new registration. If APPX is run with mismatching serial numbers, it will fail the license check and generate an error message.

2. Install the HASP on the APPX license server:

   Use a 25 to 9-pin serial port adapter to connect the HASP to a parallel port on the back of the Intel box.

   If a printer is already connected to that port, disconnect it, attach the HASP to that port, and then connect the printer cable to the rear connector on the HASP hardware.

3. Identify the device port address:

   In an environment variable (in $APPXPATH/appx.env, in a batch file that runs 'appx -l=logfile', or in /etc/profile), set HASPTTY to point to the parallel port. For example:

   Under Linux: 
   HASPTTY=/dev/cua0 
   HASPTTY=/dev/cua1 (if 2 parallel ports)
   
   Under SCO: 
   HASPTTY=/dev/tty1a 
   HASPTTY=/dev/tty1b 
   
   Other possibilities: 
   HASPTTY=/dev/tty01 or ... 
   HASPTTY=/dev/term/001

4. To determine possible port addresses, look in your /dev directory for devices matching the above addresses.

5. Run APPX.

   No driver is needed. The serial number in the upper right hand box of the registration screen should match the serial number in the lower left hand corner, both of which should match the Hasp ID.

Debugging:

To debug HASP problems, export the following two variables, and then look at and/or email us the resulting logfile:

export APPX_SS_LOG=</tmp/hasp.log>   # location of hasp log file
export APPX_SS_CODE=0xFFFFFFFF       # turns on full debugging

A result of "Calling for GET_HASP_ID...returned 32" means that APPX couldn't find the hasp. A '129' means "OpenHASP key not found". See below for a full listing of OpenHASP return codes.

Check that the HASP is physically connected, and that you've properly identified the port to which it is connected.

Check that HASPTTY is properly defined at the point immediately before you enter APPX.

See ECR #4497 for additional Debugging information.

OpenHASP Return codes:

-1  Unknown error
1   Invalid service
2   Invalid passwords
3   Invalid r/w address
4   Data size is out of range
5   Internal error
6   The key detected a CRC error
7   Invalid PassType parameter
8   Random bits mismatched
32  You did not define theHASPTTY environment variable
33  Invalid service
34  Cannot open the communication channel
35  Cannot close the communication channel
36  Cannot open a communication   channel that is already open
37  Cannot close a communication channel that is already closed
38  Cannot restore the ctrl-break signal handler
39  The read/write address is out of range
40  The size of the data is out of range
41  Internal error
42  The API detected a CRC error
43  IsHasp failed
44  cannot disable default Ctrl-break signal handler
64  Internal error (DOS only)
65  Specified a serial port that doesn't exist in system (DOS only)
66  Specified an invalid serial port (DOS only)
67  API failed to detect an active IRQ line.
129 OpenHASP key not found
130 The API did not receive enough bytes from the key
131 The API received too many bytes from the key

Note: An older document concerning installation of OpenHASPs is provided here . Note that its contents are considered obsolete, but may be of interest to customers running older versions of APPX.

Comments:

Read what other users have said about this page or add your own comments.

<--/commentPlugin-->

-- ChrisBrower - 2011-06-08