PDA

View Full Version : HASP HL Under Vista 64


Bach911
02-09-2009, 11:05 AM
I have been searching this forum for about two months and decided I have valid questions not found by searching. I using the following for HASP HL on Vista 64 OS decribed by fejkus

dumper – h5dmp.exe
TORO hasp monitor
Sataron’s UniDMP2reg convertor
emulator – Chingachguk vusb emulator

I belive I read Chingachguk vusb emulator will work for 64 bit OS. However, TORO hasp monitor gives error code 2 when accessing HARDLOCKFILTER.SYS. I tried installing USBFilter and get "The INF file you selected does not support this method of installation". I tried starting the system without driver signatures with the same results. I also tried installing the inf in DOS. The command worked without error, however the monitor still does not work. I don't think the inf file has the proper headers for 64 bit.

I need the speed of Vista 64 to make the protected program work efficiently. I think a better thread on Vista 64 OS is needed. Not even the guys who charge can handle this.

I would appeciate any help. Let me know if I am asking too much.

benito
02-09-2009, 11:25 AM
I think TORO hasp monitor cant work under 64bit

Bach911
02-11-2009, 09:50 AM
OK, Thanks. Head feels better when not banging on wall.

Will try to dump and create reg on pls in 32 XP and Vista. If successful, will try reg and emulator in 64 Vista.

May take some time. Will inform results

Git
02-11-2009, 06:35 PM
64 bit OS requires emulator driver specifically designed for and compiled for 64 bit OS. A 32 bit *.sys will *not* work.

Git

Bach911
02-12-2009, 02:31 PM
I thought vusbbus.sys emulator from Chingachguk & Denger2k will run in 64 bit? Can't I dump in 32 and modify the reg in 64 and use vusbbus.sys?

If not, is there a 64 bit monitor and dumper? All I have found are Toro and Haspmons monitor and dumpers for HASP HL. They appear to be 32 bit.

If you know there are no current solutions, you will save me a lot of time searching. However, it is fun to read many of these threads. The thread \Reverse Code Engineering\Emulating Hasp HL max\ started by fejkus reads like a novel. I am only on page 17 of 28.

Thanks for responding. Any additional help, even if you charge, is appreciated. I see from threads you are very kind to newbies.

Git
02-12-2009, 06:58 PM
> Can't I dump in 32 and modify the reg in 64
> and use vusbbus.sys?

Yes, as long as you use a specific 64 bit version of vusbbus.sys. Or, a 32bit app can talk to a 64bit device driver, so a 32 bit dumper should work OK on X64 to dump a dongle as long as the dongle is fully working with 64bit drivers. (and that the driver is correctly written to talk to 32 bit apps - there are a lot of pitfalls).

I have a version of vusb working under XP64 handling 11 dongles of 4 different types, so I can assure you it all works just fine.

> Any additional help, even if you charge, is appreciated

Not sure if that was aimed at an individual or the audience in general, but just for the record, I do not, and will not ever, charge for any help I give.

Git

diegotorres
02-12-2009, 07:35 PM
@Git

Hello Git,

Can I know which version of vusb works fine with sentinel in 64Bits?, Thanks for your response

Regards

Git
02-13-2009, 07:36 AM
My own private version, but the ru-board version and the 64 bit Multikey both work just fine, despite a couple of naysayers here.

Git

sebhag
02-17-2009, 07:56 PM
Hi Git, i guess the naysayin was aimed at me and Diego. I've only tried Multikey, but would very much like to try a 64bit ru-board version since the 32bit version is working very well for me under XP32.

Also, on reading your previous posts more closely could you please confirm a few things? Are you sayin it'll make a difference if i dump under 32 or 64 bit? I'm just using the reg's from XP32 and change the path to match multikey. This works well for Hasp but crashes on Sentinel. Would it make a difference that i got my pva dump from an emulated dongle (via sentemul)? Like i said, works 100% in 32bit and Hasp works well in 64bit, too.

Any further insight would be much appreciated.

Git
02-18-2009, 07:05 AM
Why keep asking me and not the author?. You haven't yet posted a detailed bug report as I suggested, and I also suggested on more than one occasion that you send that bug report to the author. Have you done that?. When a driver crashes with blue screen, the system writes a "minidump" containing loads of debugging info. I suggested you send that to the author. Have you done so?.

Look at the Multikey distribution. There are directories for the 32bit and 64bit binaries, and one common directory for the example reg files. So the 32bit and 64bit versions use identical reg files. So why are you changing the path?.

If your 32bit reg files are from Multikey then you don't need to change a thing.

If your 32bit reg files are NOT from Multikey, but from another emulator, then there is usually more to do than just changing the path. Double check the required format for each of the emulators and make sure you are converting them correctly. Some emulators even use different byte order for 16bit words, and most use some different Key words or have additional Keys.

Dumps from emulated dongles depend entirely on the emulator. A well written emulator should look identical to a real dongle and mak identical dumps. Some commercial emulators will deliberately try to stop dumps being taken. Like the rest of this hobby, the knowledge is gained by doing and searching and trying, not by asking.

Git

sebhag
02-18-2009, 08:04 AM
Hi Git, thanks for getting back to me. I would be more than happy to get in touch with the author directly if i had a contact. Benito pointed out that EliteR is the author of multikey and as far as i know he's not a member of this forum. I tried to describe the problem as detailed as i can in various threads, i'm not clear on what other information i should include - what's your definition of a detailed bug report? With regards to minidump, if you remember i tried to analyze it myself without much luck and would have send it to the author a long time ago if i had any contact.

I was changing the reg path because i was using ru-board vusb for 32 bit and NOT multikey. I did double check the format and compared with the multikey samples. In fact the same thing happens with the supplied sample reg so i know for sure it's not a problem with my dump.

Again, here's what happens:

1) add sample sentinel reg
2) install multikey64
3) new device found and sentinel driver installs correctly
4) launch target - BANG!

You mentioned a ru-board version, but all i could find on ru-board was multikey. Any pointers?

benito
02-18-2009, 08:16 AM
Hi Git, thanks for getting back to me. I would be more than happy to get in touch with the author directly if i had a contact. Benito pointed out that EliteR is the author of multikey and as far as i know he's not a member of this forum. I tried to describe the problem as detailed as i can in various threads, i'm not clear on what other information i should include - what's your definition of a detailed bug report? With regards to minidump, if you remember i tried to analyze it myself without much luck and would have send it to the author a long time ago if i had any contact.

I was changing the reg path because i was using ru-board vusb for 32 bit and NOT multikey. I did double check the format and compared with the multikey samples. In fact the same thing happens with the supplied sample reg so i know for sure it's not a problem with my dump.

Again, here's what happens:

1) add sample sentinel reg
2) install multikey64
3) new device found and sentinel driver installs correctly
4) launch target - BANG!

You mentioned a ru-board version, but all i could find on ru-board was multikey. Any pointers?

Simply post the minidump here, he will read it!

sebhag
02-18-2009, 09:47 AM
Ok, here's the minidump (http://rapidshare.com/files/199580060/Mini021809-01.rar.html) and debug information:

FAULTING_MODULE: fffff80001c1e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48f9ec37

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
multikey+1c3f
fffffa60`09ef3c3f ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000096

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000096

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001c4ce47 to fffff80001c73350

STACK_TEXT:
fffffa60`0b4d6a88 fffff800`01c4ce47 : 00000000`0000001e ffffffff`c0000005 fffffa60`09ef3c3f 00000000`00000000 : nt+0x55350
fffffa60`0b4d6a90 00000000`0000001e : ffffffff`c0000005 fffffa60`09ef3c3f 00000000`00000000 00000000`00000096 : nt+0x2ee47
fffffa60`0b4d6a98 ffffffff`c0000005 : fffffa60`09ef3c3f 00000000`00000000 00000000`00000096 fffff6fb`00000001 : 0x1e
fffffa60`0b4d6aa0 fffffa60`09ef3c3f : 00000000`00000000 00000000`00000096 fffff6fb`00000001 fffffa80`0489030c : 0xffffffff`c0000005
fffffa60`0b4d6aa8 00000000`00000000 : 00000000`00000096 fffff6fb`00000001 fffffa80`0489030c fffff6fb`00000001 : multikey+0x1c3f


STACK_COMMAND: kb

FOLLOWUP_IP:
multikey+1c3f
fffffa60`09ef3c3f ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: multikey+1c3f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: multikey

IMAGE_NAME: multikey.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

y8y8y8y
02-18-2009, 10:09 AM
There is new ver of multikey that solve Sentinel on 64bit support.

Git
02-18-2009, 10:33 AM
V17.1 isn't released yet, it's a test version.

I can't do anything with the minidump if that is what was being suggested. It is 100x more useful if you have the source code so you can then see where the error is and, of course, fix it.

As for contacting him, go to ru-board and PM user "elite r"

Git

sebhag
02-18-2009, 10:38 AM
Yes, found Elite_R earlier today, but it's been about 25 years since i've learned Russian. :) Anyway, i'll send him a post and see what happens.

sebhag
02-18-2009, 01:07 PM
:D Test version or not, v17.1 DOES fix the problem!

10x to y8y8y8y (and Elite_R obviously)!

Thanks guys!!!

sebhag
02-18-2009, 01:27 PM
Just as a note, i did have a lot of problems with devcon on this version and had to install the driver manually. Not sure if this is a problem with Vista64 or this driver version but MS say that devcon doesn't work fully under 64bit.

Oh, and had to sign the driver too...

Git
02-18-2009, 06:51 PM
You were using the 64bit version of Devcon, yes?.

And I'm quite sure MS do not say any such thing, it's not in their character!.

Git

Landogar
02-18-2009, 11:06 PM
Hi All

use Devcon.exe for 64bit i386 (intel) or for ia64 (AMD)

Installing an Unsigned Driver (only for 64bit) info from MS

In order to facilitate debugging these situations, the kernel-mode code signing policy supports the following registry value:

HKLM\
\SYSTEM\CurrentControlSet\Control\CI\DebugFlags

This registry value is of type REG_DWORD.

If this value does not exist in the registry or has a value other than one of the following, the kernel always loads a driver in kernel debugging mode regardless of whether the driver is signed:

0x00000001
This flag value configures the kernel to break into the debugger if a driver is unsigned. The developer or tester can then choose to load the unsigned driver by entering g at the debugger prompt.

0x00000010
This flag value configures the kernel to ignore the presence of the debugger and to always block an unsigned driver from loading.

i hope this help

benito
02-19-2009, 04:00 AM
This looks useful, will try.
Thanks for tip!

BR

Git
02-19-2009, 08:39 AM
Landogar - if you are going to give information to people, try checking it before you post :). For clarification, MS use the following conventions :

i386 : 32 bit Windows XP, Vista etc
amd64 : 64 bit Windows XP, Vista etc
ia64 : special version for 64 bit Itanium processor

The Itanium is a specialist number crunching processor and is very rare, seen mainly only in research institutes and is not compatible with Pentium, Core 2, etc.

Git

Landogar
02-19-2009, 01:24 PM
@Git yes correct....sorry

sebhag
02-20-2009, 10:28 AM
@Git: I used the version that came with multikey in the 64bit folder (6.0.6001.18000) which seems to be the same as in the 32bit folder. And the only official reference i could find was here (http://support.microsoft.com/kb/311272/en-us) which is an older version and only comes in x86 and ia64 flavours.

Is the new version part of an sdk? Anyway, had loads of problems with it, not just in Vista - kept freezing and ultimately crashing my system, but i'm sure it's due to lack of knowledge.

Would like to know what the cause is though...

Git
02-20-2009, 02:42 PM
That's a mistake by the author, you should let him know.

Devcon is part of the DDK, or WDK as it is called now. AMD64 version attached, for Windows XP X64 or Vista X64 on Intel Pentium/Core and AMD CPU's.

Git

diden
02-20-2009, 10:25 PM
That's a mistake by the author, you should let him know.

Devcon is part of the DDK, or WDK as it is called now. AMD64 version attached, for Windows XP X64 or Vista X64 on Intel Pentium/Core and AMD CPU's.

Git

no working under vista64 i tried devcon...sometimes blue screen
maybe the pbm is multikey.sys under 64

Git
02-21-2009, 07:48 AM
Devcon.exe is working fine, an ordinary application will never cause a blue screen crash. The prblem has to lay with the device driver. Email the author and let him know details of the problem and attach the minidump. If you want the free stuff to get better and be developed this is the part you can play.

Git

diden
02-21-2009, 12:12 PM
I used dmp of sentinel SPRO in emulator vusb17 multikey under vista32 and it worked perfectly .

under vista64, I even replaced the devcon.exe (64) attached above to the folder multikey64 (vusbbus v17), ==> blue screen!!!.
have you a proposal for the solution?

Git
02-21-2009, 01:20 PM
A proposal?. Yes, I've proposed it already several times. Tell the author. Send him the minidump.

Git

diden
02-21-2009, 01:47 PM
A proposal?. Yes, I've proposed it already several times. Tell the author. Send him the minidump.

Git

I know that you have not understood me. I have a bad English ...
I use VUSBUS v17 and not minidump

thank you

LUCHOJEDA
06-17-2009, 07:36 PM
Hi
I am new to this, so please be understanding.
I got the HASPHL2009_x64, but it is unlicensed,
Does anyone have the license or a crack for this program?

when I run it in vista 64 bit, I can get the password from the HASP HL but the program crashes, then when I try to create a dump file, it crashes and I get no dmp file. Any ideas what to do? Also can anyone send me the link to download software that will solve the dmp file to a dng file that will work with HASPHL2009_x64 under VISTA 64 bit.
Any help will be appreciated

stevanoski
06-18-2009, 05:21 AM
No, don't exist crack or license.
If you want to make dump with HASPHL2009 work on the x32 Windows, but solution for this is not free, send dump to http://www.dongleservice.com.
Exist only free solution for HASPHL2007, but not for HASP HL.
Also free solution is Vusbbus or Multikey emulator, search in this forum, you will find answers.