VB Unpacking

Trying to unpack VB application I exprienced that I have th dump allright. While in debugger it would show call vb dll however in dump the direct call to api is reduced to indirect calls and most of the reversing tools fails to acknowledge it as aVB application and so refuses to work. I tried import rebuilding usinfg ImpRec but without any success.
Can i have some suggestion how to unpack VB properly with proper api calls

[JMI]

The Windows Crack Tutorials Forum is NOT the place to post this type of Discussion/Request. It certainly is NOT the place to ASK for a tutorial.

Regards,

"I tried import rebuilding usinfg ImpRec but without any success"

it sounds like one of these recent packers who put IAT in a memory place away from the executable sections. You dump it.....but some calls are refering to a distant place in memory (call [13xxxxxx], not to an adress inside the exe (call [40xxxx]). Imprec isn't able to solve this. If this is the case, you should fool the packer and force it to call [someplaceinsidetheexe].
Some aspr 2.0 have been unpacked using this technique....
(sorry for my english)

To JMI
I am not asking for a tutorial.I have enough of them. I did have a practical problem and thought other members may have a suggestion.BTW if this is not the right you may shift to any other appropriate topic.
Thnkx crkl
But its not the long call. VB generally have the IT at 400000 and the EP would be at the end of the IT. But the thing is in debugger it would show the appropriate API but the dump have the same call to a static call to same memory address and thats why most of the reversing vb tools fails to detect it as a VB application.

[JMI]

The "Suggestions" forun is a place to MAKE SUGGESTIONS about the operation of the Forums. Not a place to ASK for "Suggestions." If you had looked at the other threads in the Forum before you had posted you would have realized this.

Regards,