icebreaker
October 18th, 2005, 14:46
how is the best method for removing shitty nag from vb app? I am currently trying to do it with olly, w32dasm and VBDebugger + pcode support but still i am penetrating this shitty vbrun**.dll, and all application calls is invoking this library. Is there any method to determine which part of exe code is calling nag-screen procedure? thanks for help & stay cool. 
