If your firmware is v.3.2.x then your situation is same as point 3. Let us know what version of your hasp dongle firmware ? :) Chicco85 - Use USBDeview to know your hasp dongle firmware. As i know, there are additional parameter which should be define under SRM emulator such as unique vendor id, unique feature id, etc.Ĭorrect me if i was wrong.

Consequently, emulating in 100% haspHL enviroment would not enough because we need to emulate the part of haspSRM functions. In the point number 3, Of course Toro hasp monitor 3.2 could log it because haspmon 3.2 monitored the part of haspHL functions. The dongle must be firmwared by v.3.2.x (SRM firm) & the aplication could be implement both haspHL & haspSRM function. > It doesn't matter if the hardware revision is still old v5.x.x or the new v. The dongle must be firmwared by v.3.2.x (SRM firm) & The application must used only haspSRM functions. 6.x.x (haspSRM hardware reference design). > It usually a new brand haspSRM dongle which had hardware revision v. The application still use 100% haspHL functions.

> The dongle (hardware rev v.5.x.x or v6.x.x) could be firmwared by v.3.2.x (SRM firm) but the application do not implement haspSRM function. The dongle is not be firmwared by v.3.2.x (SRM firm) & The application implements only haspHL function. > It usually the dongle hardware revision is the old v5.x.x (haspHL hardware reference design). INSTALL: E-Prime 2.If toro monitor can log it that means it is 100% not - but it could not be 100% emulated by haspHL emulator. INSTALL: E-Prime 3.0 Prerequisites required for installation You can verify the Provisional License is installed by navigating to and checking that a HASP SL AdminMode key exists with a Location of Local and a Vendor Number of 50978. To do so, copy the ep3lm.v2c, haspds_windows.dll, and haspvlib_50978.dll from the Support folder of the extracted EP3.0.3.214.exe to the location of the Command Line Run-time Installer (haspdinst.exe). NOTE: If deploying E-Prime 3.0 Update 3 via msi or lowercase setup.exe, you must use a command line installer to install the Provisional License. Sentinel HASP/LDK Windows Command Line Run-time Installer The latest Command Line HASP driver, can be found on the following page: NOTE: A reboot of the machine may be required after installation and is recommended after any installation affecting the HASP driver.

You can update to this version after the E-Prime 2.0 installation is complete. NOTE: The E-Prime 2.0 installer is incompatible with GUI HASP Driver Version 8.31 or later ( ERROR: HASP Driver Version 8.31 or later causes E-Prime 2.0 installation error 2753 ). Navigate to the webpage, download the file, and install the latest Sentinel HASP/LDK driver.

Sentinel HASP/LDK Windows GUI Run-time Installer To download the latest GUI HASP driver, you need to visit the following page: E-Prime requires Sentinel HASP drivers in order for your license to work properly.

Hasp hl 3.25 no driver found