Has anyone an idea how to prolong the 30 day demoversion of <name and link deleted for the second time - get the point yet?>

1. 30 dec = 1Eh

2. 1Eh is either getting pushed, or compared

3. Load IDA, disassemble all necessary files, save as .LST

4. Search for 001Eh with ONLY push or cmp instructions (hope you know regex)

5. 9/10 times simply changing 001E to something like FFFE etc OR taking/nottaking the subsequent jump (conditional, of course) will work.

Hope you know enough ZEN to pick up from a few hundred 001E matches...

As someone once said: A lot of broken arrows, though.

Have PHun

I tryed this, but without success. But i've seen, that always when i install the demoversion to a new pc it generates a new license.dat file in its installation folder.

Sigh...

Have you taken the steps you need to see how your application handles this (.dat) file?

Have you checked to see if your application relies only on that specific file to calculate the expiration time? Could it be possible that it is placing something in the registry or dropping some hidden files elsewhere as a contingency measure for a possible reversing attempt to workaround the demo period?

Have you checked to see if your application is putting/reading some foot/fingerprints on your system?

Have you checked to see if your application is calling home to exchange some data related with installation specifics?

?...

at the beginning and at runntime the App is reading the .dat file, becaus if i remove it and do for example compiling he stops and say "no valid license found", in the registry there is anything. It could be that there is also a dll (lmgr8c.dll) involved.

Oh, it COULD be. Really?
Did you even consider debugging the application? It seems that your first post was deleted (for a good reason) and you learned not much from that fact. We are willing to help you (although you may think we're not) but you need to provide some effort of your own. Aimless posted you some basics of what you can possibly do, but I fear you are looking for some ready-made solution. Did you look for the error message in IDA/Olly/whatever? Is it conditional? Can you bias it? Which API is used to load/read the .dat file? Do you even have the slightest clue to debugging?
Sorry if I sound rude but we're no Warezboard. Give some information about what you did, where you stuck and what YOU think about the problem. That's the road to salvation

Best regards
Darkelf

"That's Me"

PAY ATTENTION!

STOP POSTING THE NAME OF YOUR SOFTWARE AND ASKING SOMEONE TO "CRACK" IT FOR YOU. WE DON'T DO THAT HERE!!!

GO ACTUALLY READ THE FAQ AND DO NOT POST AGAIN UNTIL YOU HAVE!!!

THIS IS NOT THE PLACE TO COME WHEN YOU DON'T KNOW WHAT YOU ARE DOING AND YOU WANT SOMEONE ELSE TO DO THE WORK FOR YOU!!!

It takes time and a great deal of personal effort and study to learn how to reverse engineer software.

If you don't have the time and/or you don't have the interest in personal study and effort, you are at the wrong place!!!

This will be your last warning!



Regards,

I probably shouldn't humor this, but...



Yes. If you had entered this file name into google, you would have discovered that this file is part of the FlexLM license manager (version 8), which is a well-known commercial protection system. This is a fairly old version (~2001); the current version is 11, I believe. If you look around, you might find some some useful places concerning FlexLM crackZ.

I still not belive that a topic like "crack request" receives more replies than another that has really something interesting.

Not everything is always what it seems.

That post made me laugh just a teeny bit. I just think that most of us are sick of crack requests we give in just a tiny bit just to get them off our case.

I liked the "temporary" title better, but then I was the one who originally changed it. Someone took pity on the poor guy and changed it back to what it reads now.

Regards,