![]() |
Ah, I see your mistake.
You're confusing job- and vendorcode-structure! The vendor-struct is the block you marked JOB and vice-versa. Your data is consistent with my encseeds :D Dirk |
omg *me dies* thanks man!, worked like a charm, what a silly mistake, my 1000 sorrys :)
JMI, if any of the previous posts need editing for something removing plz do! or just tell me and i will, sorry to waste peoples time :) |
hehe another day, another problem :)
today i try to build lmcrypt for my own amusement, so i edit lm_code.h with: (i got it from lmv8gen) Code:
#define VENDOR_KEY1 0x6cfe8c94"Build", i get the following: Code:
Microsoft (R) Program Maintenance Utility Version 6.00.9782.0 |
First thing to do is RTFM.
-44 LM_BADKEYDATA "Invalid key data supplied." Invalid FLEXnet Licensing key data was supplied to the lc_new_job() call. Some FLEXnet Licensing functions will be disabled. Seems your VENDOR_KEYx and/or CRO_KEYn are not correct for vendor "testabc" Tom |
tom: sorry i shoulda said that i did read thru, it and i knew what -44 was.
how would one generate such vendor keys then ? Thanks. |
Hi again!
As you should probably know vendor-keys are changing with each major revision of flexlm. And what does this tell us: Code:
$ ./lmv8genDirk |
yea i understand they change, and i have 0 intrest in playing with the cro versions atm, however i did try lmv8gen, found at CrackZ website, on v7, v8, v9.2 of the sdk's with differnt vendor names, all report back -44 during build time, again iam prolly missing something silly.
*edit* got v7.2 SDK working, by using PGC FlexLM Vendor Kegen, must be the lmv8gen, that just didnt worked for me in the 8+ SDK. Thanks as always. -Peter |
| All times are GMT +8. The time now is 15:36. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2026, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX