HASP dongles and licenses
Trial Licenses
Your distributor can provide you with a dBSea trial license. If dBSea opens without a valid HASP dongle connected, it will request a trial license file. Choose the file, and dBSea will import the license and be available in trial mode until the trial period is over, or a valid HASP dongle is connected.
Trial mode allows full use of dBSea; however, export of levels or bathymetry is disabled. In addition, exported images will have an overlaid watermark.
Projects created and saved in the trial version of dBSea can be opened in the full version, so if you start working on a project and then decide to purchase the full version, your work will carry over.
HASP Dongles
The full version of dBSea is secured using Sentinel HASP licensing. Your HASP dongle will be sent to you by your distributor when you purchase dBSea. The first time you insert the dongle, it will install the required drivers, which may take some time. If the driver install fails, drivers may be downloaded from Safenet. Once the drivers are installed, your HASP dongle will be ready to use whenever inserted.
To use dBSea on a different computer, simply install dBSea and insert the HASP dongle as before.
Demo Version
If neither a HASP dongle nor a trial license is found, dBSea will open in demo mode. In this mode, import and export functions are disabled, as are opening and saving of projects. Other functions are activated, so you will be able to explore the program, work on, and solve problems using the default bathymetry.
Troubleshooting
Occasionally, there can be problems with installation of a trial license or using the HASP dongle. In most cases, these can be solved by uninstalling and reinstalling dBSea. If dBSea will not open after this step, please contact your distributor, quoting any error messages displayed, including the error code (e.g. "1160: License file could not be decoded").
For network keys, sometimes manual specification of IP addresses is necessary. The network HASP Key can be situated on a computer outside the subnet range of the local client machines accessing the HASP Key. However, the IP address of the remote computer with the HASP key must be manually entered on the client machines using the HASP License Manager as follows:
- On each of the client machines, type
http://localhost:1947
in the address bar of a web browser (e.g., Internet Explorer, Chrome, or Mozilla) on the local machine that is to access the HASP key located on a different subnet. This starts the HASP License Manager interface. - Click the
Configuration
tab on the left-hand side menu. - Select the
Access to Remote License Managers
tab across the top of the window. - Click the box next to
Aggressive Search for Remote Licenses
. - In the clear window next to
Remote License Search Parameters
, type in the IP address of the server that holds the HASP key and press theSubmit
button. - Click the
Sentinel Keys
button on the left-hand side menu and wait for the remote HASP key to appear in the list of keys. - It may take some time, but the remote HASP key should be found within 2 minutes.
- Once the HASP key appears in the list, you will be able to run dBSea.
- You only have to do this setup once, as the settings are stored in the HASP License Manager on the local machine when the browser is closed.
If this search fails, it's likely you do not have access to the computer with the HASP key. To confirm this, open a Command Prompt
, then press 'Windows-button' + 'R', type cmd
, and hit "Enter". Type either ping
or tracert
followed by a space and the IP address of the machine with the key. If the above does not return either "reply" or "trace complete", your machine is not connected to the requested IP. A firewall, faulty network setup, or hardware issues (e.g., not connected cables) could be the cause.