The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Hi,
It is not clear how you tell your software what is the Parallel port I/O address used, once you changed your LPT1 settings to I/O port 378.
For Hardlock dongles it is usually done using System environment variable HL_SEARCH
The Hardlock supported I/O addresses are: 278, 378 and 3BC
So, you can use the following command to add the Environment variable:
Set HL_SEARCH = 278p, 378p, 3BCp
if problems with bi-directional printer, try:
Set HL_SEARCH = 278e, 378e, 3BCe
Also, could you confirm that your Parallel Hardlock has the following shape ?
If yes, then install our « Sentinel Runtime Installer version 7.32 »
http://www.sentinelcustomer.safenet-inc.com/DownloadNotice.aspx?dID=8589947119
reboot and try again.
Regards,
Olivier
Hi,
The general issue will be that parallel Hardlocks are supported up to Windows XP only and not later. It might work with Windows 8.1, but we can’t guarantee this.
The usage of LPT-to-USB converter will fail and is
not supported, even with Windows XP. It’s mandatory to use a native
parallel port, e.g. an ExpressCard Laptop Parallel Adapter Card as
described by Olivier.
Best Regards
Sven
-Client Services
Engineer-
haspdinst.exe -r -fr -kp -fss -purge (Remove Existing RunTime )
Followed by
haspdinst.exe -i -fi -kp -fss (For install Runtime )
Thank You,
Anubhav
Dear Ilaria
Thanks for your answer
Through our Argentina´s Vendor, we have also entered in contact with the Sentinel-Hasp Support team, but until now they neither could give us an answer or solution
At the moment we have about 2000 customers that use our tool protected with Hardlock key
As our software is a control tool that has to do with the people's safety area , for most of our customers, this tool is critical for its business
Due to the Microsoft policies, for upgrading Windows 10 in an automatic way, without requesting the approval of the users, we begin to receive daily an important number of users' incidents , because the tool stopped them to work when they were upgraded to Windows 10 on its computers.
We cannot wait until August to give answers to our customers.
Until is available the new driver versión, we would need to have some workaround , although in a temporary way, that allow us to solve the problema to our customers
we will thank your help
Sergio