![]() |
|
|
|
#1
|
|||
|
|||
|
hi,
just a idea - take a look if there is a cmp eax,ebx or a compare against 0/1 and try to change this... maybe this helps greets grashalm_ |
|
#2
|
|||
|
|||
|
RAND is a very uncomon routine, unless the application is a game. What if RAND where to always return an obscenly large value? That would enable your app to run for a month or so continiously...
![]() Seriously, I would just nuke the VMT entry for On Timer or whatever it is (been a while since I've messed with Delphi code). |
|
#3
|
|||
|
|||
|
i'm sorry but i don't understand what you want to do
it's your application and you want patch it. For break, you can try Settimer to know identifier of the timer and sometimes the address of the function called and after with ontimer you know when it is called. Otherwise with ExitProcess, you will land at the end of the function. |
|
#4
|
|||
|
|||
|
i just code it by myself, to test my skill, but
thats why i make alot TTimer classes, i think if we put on SetTimer/OnTimer it will break in all execution of TTimer not in the specific class that execute a function that call Form.Close, i just want to break at Form.Close when TTimer call this |
|
#5
|
|||
|
|||
|
First, not clearly know your meaning.
Secnod, What's your coding language? Third, if you can't use FORM.CLOSE event to stop the App Close. Try HOOK MSG of your App. WM_CLOSE |
|
#6
|
|||
|
|||
|
Well... if djneo's or grashalm_'s solution don't work, then I don't know what.
Try their solutions first, then come tell us the good news. The key to kill the timer is in the cmp. (nop the call to exit) Last edited by FrmrV; 09-07-2004 at 02:17. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Timer Functions | bedrock | General Discussion | 9 | 05-24-2005 23:09 |
| Good App to kill Spyware | wizkid0109 | General Discussion | 13 | 08-15-2004 10:36 |