View Single Post
  #6  
Old 09-23-2014, 23:05
0xd4d 0xd4d is offline
Lo*eXeTools*rd
 
Join Date: Mar 2012
Posts: 78
Rept. Given: 12
Rept. Rcvd 308 Times in 44 Posts
Thanks Given: 2
Thanks Rcvd at 175 Times in 24 Posts
0xd4d Reputation: 300-399 0xd4d Reputation: 300-399 0xd4d Reputation: 300-399 0xd4d Reputation: 300-399
@git:

1. I just manually fix it when I enter an interesting function. Copy real end address then ALT+P.

2. Change low/high suspicious limit in options to some invalid address (eg. 0), then mark all unicode strings that haven't been fully detected and press c. Choose "analyze", choose "Yes, convert to code" and it should fix your unicode strings. You can use a regular expression and search for them:

"dd offset [^ ]+00" (dd offset loc_490021)

"dd offset [^ ]+\+" (dd offset aSomeString_7+18Bh)

Could take a couple of minutes to fix all unicode strings depending on the size of your exe.
Reply With Quote