hwnd
September 19th, 2009, 01:52
hey guys, i'm a bit of a lurker on the forums and site, mostly reading in my spare time on a project i'm starting.
I'm working on VB3 application with HASP3 protection. I do not have the dongle anymore. My problem is, the software company isn't offering dongle replacements - only $6k upgrade packages to their current software (this new stuff is HASP5 protected). While it would be nice to have the latest and greatest - it wouldn't honestly benefit to the tune of $6k.
So here I am with questions that were not directly answered in CrackZ's page.
- any pointers on double checking the HASP protection version?
- without the dongle, am I out of luck removing the HASP protection?
I generally assumed its protected with v3 due to the age of the application itself and noting files like hasp.386, haspmsw3.dll, etc. If this isn't correct I would gladly love to learn how to identify the correct version.
I did open the application binary in my fav hex editor and noticed the typed control names, font names, strings within the app, etc were not encrypted.
anyhow, i'm wondering if there might be someone who can shine a bit of light on this.
I'm working on VB3 application with HASP3 protection. I do not have the dongle anymore. My problem is, the software company isn't offering dongle replacements - only $6k upgrade packages to their current software (this new stuff is HASP5 protected). While it would be nice to have the latest and greatest - it wouldn't honestly benefit to the tune of $6k.
So here I am with questions that were not directly answered in CrackZ's page.
- any pointers on double checking the HASP protection version?
- without the dongle, am I out of luck removing the HASP protection?
I generally assumed its protected with v3 due to the age of the application itself and noting files like hasp.386, haspmsw3.dll, etc. If this isn't correct I would gladly love to learn how to identify the correct version.
I did open the application binary in my fav hex editor and noticed the typed control names, font names, strings within the app, etc were not encrypted.
anyhow, i'm wondering if there might be someone who can shine a bit of light on this.