USB Key Driver Installation

USBs Are No Longer Supported

Fathom 14, Arrow 11, Impulse 11, and xStream 4 are the last versions that will be compatible with USB Keys. Future versions (fall 2026) will require using an eLicense or offline activation certificate for air-gapped systems. Research is being done to develop a Local License Server offering which would replace the functionality of Network USB Keys. USB Keys will continue to function on past versions of the software; however, technical support will no longer be provided. The information below is available for reference.

Information on switching from USB Key to eLicense is listed on our USB to eLicense Transitions page.

 

Driver & Utilities Installation

Licenses from USB hardware keys require drivers from the vendor to work and interact with our applications. The drivers and associated utilities are packaged into the AFTCopyProtectionSetup.exe installer.

For Green Standalone USB Key Licenses:

  • Copy Protection must be installed on every client computer which has the software installed that will be accessing the standalone license from a green Standalone USB key.

For Red Network USB Key Licenses:

  • Copy Protection must be installed on a computer or server that will host the red Network USB key and network license manager.

  • Client computers will need to be able to see this machine over the network or use the nethasp.ini file to contact the server.

Follow the instructions below for driver installation.

  1. Download the AFTCopyProtectionSetup.exe installer.

  2. Right-click AFTCopyProtectionSetup.exe and select Run as administrator.

  3. Click Next to begin the installation.

  4. Select the type of USB.

  5. Several separate components can be selected for install, all of which are bundled into the AFTCopyProtectionSetup.exe. The USB Key Driver is required for both standalone and network keys. The License Manager is required on the server hosting network keys. Click Yes to start the component installations which will launch separate pop-ups. Follow the prompts, accepting the default values except for the License Manager detailed in the next step:

    Component Required? Name Executable
    USB Key Driver Yes Sentinel Runtime Setup HASPUserSetup.exe
    Support Diagnostics No Aladdin DiagnostiX 1.10 aksdiag32.exe
    License Manager Yes, on the server for red network keys HASP License Manager 8.32 lmsetup.exe
    License Monitor No Aladdin Monitor 1.4.2 aksmon32.exe

  6. For Red Network Keys only: When the HASP License Manager is installed on the hosting server, choose the option to install it as a service (nhservice.exe). After it has been successfully installed it will ask if you want to start it now. Click Yes (requires the USB Key to be plugged in).

    1. This component will create Firewall rules that allow inbound/outbound connections over port 475 TCP/UDP.

    2. This component will install the license manager driver called akshasp.sys.

  7. Once the installation of the various components are finished, you will return to the AFTCopyProtectionSetup.exe. Click Finish.

    1. For Green Standalone Keys: The installation is complete. Plug in the key and run the software when desired.

    2. For Red Network Keys: Configure the nethasp.ini file described below.

 

Configuring the nethasp.ini file for Red Network Keys

When using a red network USB Key, if all client machines are on the same subnet as where the USB is physically plugged in, then usually no additional configuration is needed. However, if clients from other networks (i.e. other buildings, other office locations, etc) need to connect to the USB Key, then the nethasp.ini file must be configured with the appropriate server IP address. Port 475 will be used to connect and check seats in/out of the USB key.

  1. Find the nethasp.ini file located in C:\AFT Products. The file should exist here if you ran the AFTCopyProtectionSetup.exe from the steps above. You can also download a copy here if needed.

  2. Determine the IP address of the server that is hosting the network USB key (physically plugged in).

  3. Open the nethasp.ini file with a text editor.

  4. Locate the [NH_TCPIP] section header.

  5. Un-comment the line for NH_SERVER_ADDR by removing the two preceding semicolons.

  6. Set the line equal to the server IP address (replacing "<Addr1>, <Addr2>") and save the file.

  7. Copy the modified nethasp.ini and distribute it to each client machine in the application installation folder which varies depending on which products and versions you are using.

    1. For Fathom 14, Arrow 11, Impulse 11, and xStream 4:

      C:\Program Files (x86)\Datacor\Product

    2. For Fathom 13, Arrow 10, Impulse 10, xStream 3, and other prior versions:

      C:\AFT Products\Product