HASP device driver not installed (-101)

[kamil00110]

my app is giving me this error after installing the driver. normaly the error is -100 if the driver is missing. But after installing the drivers im getting this error -101. I can see the driver did something. But nothing that can be used. When the dongle is missing or has wrong data it should give error 0 or 3

[leecher1337]

HASPERR_CANT_READ_HDD = -101, /* Cannot read the HASP Device Driver

As this intermediate driver doesn't spit out this error code, it must come from the downlevel HASP driver.
There is too few information about your exact configuration to make any assumptions about the cause.
As you are using the driver, I guess that you are operating a real dongle via the driver (or are not using a MEmoHasp), otherwise it would be unclear why you didn't just use the emulator DLL.
But as said, it would be good to describe the setup you choose in full detail, as there are many configuration possibilities, including (if possible) the name of the DOS application you are trying to run.

[kamil00110]

Sorry that im answering so late. I personly gave up and started to use an heavely optimized vm. But i wantet to start again. My program uses an speciffic version of hdd32.exe HASPHL2007.exe which im using has compatible emulator drivers that work fine in win xp 32bit but can get installed there. hdd32.exe allso fails to install. Your drivers do something but arent somehow accepted by my program. when the driver is not installed it has the error -100 with your drivers its giving the error -101. It sees somehow the drivers but has problems with them. Is there any recomenden way of you in which I could share the files with you when you want to help?

[leecher1337]

Hi,
You can drop me a private e-mail at [email protected] and I can give you an FTP account to upload the constellation of files that works for you on Win XP. I can then try to find the problem with your DOS-application (i.e. by installing it on Win XP first, verifying that it works there and then tracing down the problem on later Windows releases).