![]() |
|
|
|
#1
|
|||
|
|||
|
Quote:
I do not know anything about decompiling Visual Basic, but heard that the native code are difficult to decompile than p-code; isn't it true? And which toold is better for vb-screwing: w32dasm or ida-pro? |
|
#2
|
||||
|
||||
|
for p-code try to use WKTVB debugger, it's the best. (and it's from my country)
|
|
#3
|
|||
|
|||
|
Quote:
but what for the "native-code compiled vb5 app"? raja |
|
#4
|
||||
|
||||
|
then do it like a EXE compiled by other compiler, but you must know that the API funcs are not used else Visual Basic funcs (for example: strings use Visual Basic funcs not the API SO strings funcs).
Use SICE or IDA,etc... WDASM work very good with VB programs, search for string references and get a doc that show how the VB funcs works (there're several in the net). In SICE make a reference to MSVB400.dll or the DLL that uses your VB version. Good luck |
|
#5
|
|||
|
|||
|
Thanks Mates!
Last edited by raja; 09-17-2004 at 21:30. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Anyone distributing any .NET applications using obfuscation or native linking? | JCB | General Discussion | 6 | 10-30-2005 07:03 |