PDA

View Full Version : adjusting UCL HASP emulator


eXe
August 22nd, 2001, 17:27
hi,
I find this commercial emulator but it has to be changed for
use on each prog.
Prog. without dongle popup:
HASP
The specificed key is not connected. (1000)

prog have Nslms32.dll
NetSentinel Win32 Client DLL.

How to do it.
I have dongle to if it is necessary.
eXe

NchantA
August 22nd, 2001, 21:35
im not exactly sure what your post means, but i think you should be looking more for help on cracking the actual dongle protection here, instead of using a 'generic' dongle emulator.

learning to emulate the dongle within its own code, brings many rewards.

NchantA

CrackZ
August 23rd, 2001, 12:43
Hiya,

There seems to be a screw loose with your logic.

UCL's HASP emulator is for HASP keys, the dll you mention is for NetSentinel (made by Rainbow), these are 2 *competing* dongles, therefore I can't imagine for one minute that the dll you have found supports HASP keys.

The error you get doesn't match any of the API status codes I know for either dongle (probably developer defined), so no clue there, you'd better work out which it is you have HASP or Sentinel before proceeding any further with this ;-).

Regards

CrackZ.

eXe
August 24th, 2001, 12:15
ok
1. hardware is labeled "HASP 119"
2. when it is removed apears message box
+------------------------------------------+
|error
|-------------------------------------------|
|HASP
|The specificed key is not connected. (1000) |
|
| +----+
| | OK |
| +----+
+------------------------------------------+
3. I find juist NetSentinel Win32 Client DLL.
Nslms32.dll

so, where to look ,
how to identify dongle ?

assume that is HASP, do you know how to adjust
UCL HASP emulator ? ? ? that was my 1th Q

Kythen
August 24th, 2001, 13:22
It would appear this app can work with either type of dongle (I've run across such apps before). I would assume that the HASP code is statically linked inside the exe, so to find it you'll have to do some disassembly and searching. Personally, I agree with NChanta that emulating the dongle yourself is a better path to follow. After all, getting something to work is nice... but understanding how and why it works is far better

If you really want to mess with the UCL emulator, I would guess that you need to know the seeds,passwords,id, and the memory contents. I think the info is stored in the registry, but not sure as I don't use the util.

Regards,
Kythen