![]() |
|
|
|
#1
|
|||
|
|||
|
Hi
i have done that once... the problem is that FSG is optimized a max... the only solution a come out is adding my own code in the third section... but i'm sure there is another way... Regards |
|
#2
|
|||
|
|||
|
Using "FSG + tut*" I found a short comment on unpacking FSG 1.33 in English at:
http://www.geocities.com/r_etarded/ollydump.html Essentially, it says: You can analyst the decompression routine to find the OEP or simply just using OllyDump Tracing feature. Just load keygenme.fsg.exe (4,288 bytes). small enough eh ;-). Dont press anything yet, choose 'Find OEP by Section Hop (Trace Over)' or (Trace Into). I think Trace Over is faster but Trace Into is safer. Am i right? Just wait and see. Module entrypoint After the tracer found the OEP, Olly will break and this time you may dump it succesfully, using OLLYDUMP. FSG 1.33 was written back in 2002 and I doubt you will find much discussing earlier versions of the software, but who knows what through searching might find. I only spend a few minutes. Regards,
__________________
JMI |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Inline Patching | MaRKuS-DJM | General Discussion | 1 | 01-24-2004 23:03 |