Sentinel HL USB Key

Hi,

The sentinel USB keys for a software package we use (PLSCADD) aren't being recognised.

We are running the server on our QNAP TVS-473 and our clients are running on Win 7 machines, all on a local network.

What I can tell so far:
1. The keys are recognised by the server,
2. The clients can connect to them (it says "In use by you").
3. The device drivers install successfully.
4. When we then run PLSCADD, it says "Hardware key not found".

Can anyone recommend what the next step should be to isolate the issue?

Thanks,
Kym

#2

Try this

1. Right click on the Sentinal HL and select "Custom Event Handler..." and put in this

onReset.$VENDOR_ID$.$PRODUCT_ID$=

then press OK.

2. Now unplug and replug the hasp key.

3. Try using it via virtualhere again.

#3

We followed those steps (a few times and on different computers) but unfortunately PLSCADD is still not recognising the key.

Out of curiosity, we ran Sentinel Advanced Medic with the key plugged directly into the machine and again via our Virtualhere server, and both results show the key installed correctly. They key appears as a 'SuperPro' type.

The Sentinel help guide for PLSCADD is here: http://www.powline.com/products/ntdriver.html although I think it is a little old.

Is there any way the software provider can program their keys not to work on your server?

Is there anything else we can try?

#4

OK unfortunately that key wont work then, im not sure of the issue. You could try running the virtualhere client on windows 10. It might provide better compatibility because win10 uses a new driver system.

#5

You're right. I just tried it on my Win 10 laptop and it worked perfectly, even without the event handler. Thanks.

#6

Our Sentinel HL USB keys have stopped working.

They appear in the client, are we're able to select them, however our software package PLSCADD no longer finds them.

Other types of USB keys seem to work.

I tried adding the custom event handler but they didn't fix it.

Is this an issue with Sentinel?

Anyone know how to resolve this?

#7

Do you remember if anything changed recently on your computer, e.g some sort of driver update or windows update?

#8

We feel it all happened around the time of a major update of Windows 10 Pro.

#9

We just updated every bit of software we could think of that's related to this and now it works. So all good. Cheers.