hi, im trying to crack one program but I tryied to figure out a lot of times, but still nothing...
Ill explain how this trial works: start with a pop-up asking register or run(wait 4 seconds to reveal button) just the first one hour. Run for just one hours.On the last 15 minutes appear one pop-up warning, so i think it should have a countdown., because there is a "time left".
I'm trying but there is a lot of GetTime functions and there is no string like "registering failed".
hhellp

A few questions... How do you measure the weight of a planet? What came after the permean era? Is global warming a result of mankind's interferance with nature, or is it simply another peak in the planet's natural cycle?

Oh. About the crack. Right.

What happens if you start the app then set your system clock forward by 44mins, then wait for the popup, then set the system clock back to normal time? Does it give you extra time or do the popups still appear at the right time?

Can you break on the popup? ShowWindow/MessageBox?

hehehe,
its happen a strange thing... if I forward the time like to + 10 hours, the timeleft increase and if i decreade + 10 hours the timeleft be negative, and nothing of pop-ups, so i think the trial time (1 hours) is a separated countdown and im trying to find it inside of the code. I'll wait 1 hour and see what happen

Well I was just following the Boss' adminition to:

"Ask a few questions" - "Before you all slaughter this poor lamb..........."


So flp: Have you actually READ THE FRIGGIN FAQ? If you have, how come YOU have not told US what research YOU have done attempting to find the answer to YOUR question?

What searching here have YOU done on the net or here about methods of keeping track of time and/or countdown timers?

YOU tell US the answer to THAT question BEFORE YOU ASK ANOTHER QUESTION!


Regards,

how rude, I already did research about cracking trials programs which use time system and normal programs all they had just one GetTime function. ON mine there is a lot of them, so im asking another ways to crack, as i gave the program information

well obviously you got something measuring time. I would start by searching google for all time api's. You will getfrequency, get systemfile time , getlocal time, etc etc. Your best bet is simply decompile the program in ida, go to the imports section, and search for every instance of "time" in the iiat, and surely you will have a good chance of finding it. If you do not, my next suggestion would be to run olly, attach to the app you are debugging. Let it run completely. Once it is running by itself and olly is also running coexistance, simply go to alt+m (memory viewer), and click F2 over the .text (code) section of the application running in memory. The program will automatically break on the location of the code running.Given it does not constantly do any tasks, there is a high probability you are going to land right smack on the countdown function and its update window api which makes the countdown show up. Also you could dig out the window handle of the popup and try to find it in the decompiled app and work from there. Live long and propser, may god be with you, look the east, yadda yadda <nickhere> + some faggot saying.

Regards

Thanks, i'll try use this olly to get the certain place. I tried the SoftIce but i didnt understand how it works

Howdy,

It must be this warm weather that has got me in a good mood.

Lets try this again BUT, let him/her reply with some useful info that shows
some basic understanding of the task that is at hand.

If a crack is what this person desires, you could all take the time to post some links .

Posts have of course been edited by me.

Uncle OBC.

Why don't you learn? You do have a brain, do you?

OK.
In OBC's spirit. . .

The detail you tell us about: more than 10 hours time left increases
less than 10 hours you get a negative number. . .

Suggests that time is being kept on a signed variable, perhaps a signed word size integer, and being read from the system time in a regular fashion.

Also: 10 hours equals 36000 seconds. In hex 8CA0. this would be, read as a signed word -3233.
actually the biggest number of seconds you can hold in a positive signed word is hex 7FFF, decimal 32767 seconds meaning 9 hours 6 mins and 7 seconds.

So: Your application reads the system time and turns it into seconds. time left is stored in a signed word variable, which is calculated by subtracting current time in seconds minus start time in seconds and displaying it for you as time left. When that number reaches 0 Cinderella's pussy turns into a pumpkin and your app quits.

Now, look for code that read the system time in seconds and do these sort calculations calculations with word size operands. you hit near the time keeping mechanism.

Clue 2: If the software authors are not savvy enough to detect with tampering with the system clock. . . This protection sounds rather primitive.

I've recently worked with another program that uses similar protection to this - when it starts up you can either enter license code, or use the evaluation version which has certain limitations. The program obviously had /some/ thought gone into it, as entering invalid text into the registration dialog was just ignored (no message dialog), and when the time was up the program just quit without warning.

I couldn't find out how the program was measuring the time, but placing a breakpoint on the usual GetDlgItemText, and I could easily see the program extract the registration key, and validate it shortly afterwards. It didn't take long to create a working key after that (and naturally, a keygen for future use )

So, before you end up bashing your head against a wall because you can't figure out how to bypass the time check, try and look for other ways into the software

naides said pussy. hehe hehehe hehe

Woodmann

No. . .
I said calculations calculations

I think he was referring to this part:

"When that number reaches 0 Cinderella's pussy turns into a pumpkin and your app quits."



Regards,