I had Brstudio Hasp Emulator working perfectly on a HASP protected programe.

I opened P32Dasm 2.0 nothing else was open and The software detected it and initialized Install repair or something of that nature.

Then i went to open the software and i got HASP PROTECTION SYSTEM -3

Dont care about p32Dams 2.0 just want to get around HASP PROTECTION SYSTEM -3

Is there a work around for this.

Uninstall the software perhaps.

This answer a little late. . .

It is not completely clear in your post, but it appears if I read your words right, that the HASP drivers or dll have detected and shitlisted P32DASM.
if that is the case you need to work on the detection system (P32 is a static decompiler, which is not very invasive in its install. I doubt it is very difficult).

Much less likely, P32 overwrote some file used by the HASP protected software and driver. Without knowing the intimate details of P32, it is difficult to know if that is the case (Perhaps the VB modules???) Once again, P32 does not strike me as a very invasive program, but if you install it under filemon and regmon surveilance you may have an idea of the files it installs and modifies, then clue you in a correct solution

Hiya,

I really doubt P32dasm did anything at all. Its much more likely your install repair simply re-installed the original Hardlock driver and now thats whats running instead of the emulator.

-3 is the most basic HASP error.

Regards

CrackZ.

What happend was the Emulator Driver was installed for a long time. The Hasp protection system would have picked it up right away.

The software is also protected by Code-Lock which i think detects any change in the software.

I spoke to Darker who created P32Dasm. He said i just had to register a phew OCX files for the software not to list my debuger.