Exetools  

Go Back   Exetools > General > General Discussion

Notices

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #4  
Old 03-05-2004, 15:42
Nilrem
 
Posts: n/a
Set a breakpoint on lstrcmp and you just might lucky (hopefully the number you entered will be compared to the true number).

Also, about your isdebuggerpresent, if it's an easy protection you can (in Olly), right click in the CPU window (after loading your program but not starting it), press 'Alt+E' then select 'kernel32.dll', and click 'View names', and type isdebuggerpresent, then double click the line you land on, when you get there press 'F2' to set a breakpoint, hit F9 to execute the program, once you land there press 'F8' until you see a '01' just below the CPU window and just above the hex dump view, when you see it select and right click that line and choose 'Follow in dump->Selected', highlight the 01 (in the hex dump view) and type 00 to change it from 01 to 00, this will disable the debugger check.

Thought I'd tell you this to at least try something once before defeating the protection automatically.

Last edited by Nilrem; 03-05-2004 at 15:52.
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
vmprotect v3 debugger detected 1ST General Discussion 13 09-25-2018 23:28
Best debugger for DOS? Taitch General Discussion 13 10-21-2010 13:46


All times are GMT +8. The time now is 20:10.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX, chessgod101
( Since 1998 )