Dongle device driver
In order for Orcina programs to connect to the dongle, a device driver for the dongle needs to be installed. This is done as part of the Orcina software installation (should you choose the local access dongle option in the installer) and so most users do not need to know anything about this device driver. However, if you are using a version of Windows that was released after your Orcina software then you may need to upgrade this device driver. The dongle driver is available here: Sentinel_HASP_LDK_Runtime_Setup.zip. Alternatively, the very latest driver can be obtained from the Thales (Sentinel) website: click on “Sentinel LDK RunTime & Drivers”, and select “Sentinel HASP/LDK Windows GUI Run-time Installer ..” (you might need to go beyond the first page to find this).
OrcaDongle is a utility program that is required to configure your Orcina dongle, for example to switch it from local to network access mode or to query the dongle information. You can download OrcaDongle here: OrcaDongle.zip
Extract the zip file to a temporary folder and then run the file OrcaDongle.msi to install OrcaDongle onto your machine. This will create a shortcut to OrcaDongle in your start menu under “Orcina Software”. The OrcaDongle documentation can be viewed online. Note, to access the dongle, OrcaDongle requires that the dongle device driver is present. Updates to the dongle using OrcaDongle can only be done in a local session on the computer to which the dongle is connected, it cannot be done remotely.
Network dongle support
Full details on setting up a dongle for use over a network are in the Networked Dongles topic of the OrcaDongle documentation. To use a dongle in this way, you will need a licence manager and configuration file. The licence manager must run on a Windows machine, which hosts the dongle. OrcaFlex discovers the licence manager using a configuration file on the user’s computer. The OrcaFlex installation must have a licence file for the dongle in the OrcaFlex installation folder. Note, the licence manager is not tested or supported for use on a virtual machine. If you wish to use this configuration then we recommend testing first and having a back physical server option available.
The licence manager is installed by extracting and running the file in the following zip file: LMSetup.zip. The dongle device driver must also be installed (as above).
The licence manager runs as a Windows service called ‘HASP Loader’, this listens on port 475 using TCP and UDP. If the connection to the licence manager is over a WAN or VPN then you may need to explicitly open this port to allow access.
A configuration file template for a TCP/IP network is in the following zip file: Nethasp.zip
You will need to modify this to specify the IP address of your dongle server. In the template file modify the line ‘NH_SERVER_ADDR = xx.xx.xx.xx;’ to replace the ‘xx.xx.xx.xx’ placeholder with the IP address or hostname of your licence server. Save the file as
nethasp.ini file in the folder ‘C:\ProgramData\Orcina\’ on each computer requiring access to OrcaFlex (C:\ProgramData\ is a hidden folder in Windows).
You may also download from here an installer for the Aladdin Monitor: aksmon32-setup.zip
This program will give some diagnostic information on the HASP licence manager and dongle on your network and instantaneous details of which machines have claimed which licences. When run on a computer on the same network, the licence manager is detected by broadcast and displayed in a sidebar. OrcaFlex is listed as ‘Program 26’ in a program table, and a login table lists any IP addresses holding licences.
Alternatively, you can use our own licence monitor which takes some more configuration but can provide more usage information.