hello everibody im trying abaout one week to guet a serial to appforge mobilevb 3.5 its a visualbasic pluguin (run inside visual basic 6) if anyone can help plzz.


thanks

you can found at hxxp://www.appforge.com

its a big file about 29 Mo and you need to ave visual basic 6 installed but plz help

ps : sorry for my english

NLZ:

You need to read the FAQ. At the moment, your post looks like a cr*ck request, and that is not permitted here. If you want help, you need to follow the posting guidelines. You need to explain what you have already attempted to help yourself and where you are stuck. Also you need to include some information about your OS and which tools you are using. These are all explained in the FAQ.

Generally you need to know how to catch the entry of "your" serial in the dialogbox or where ever you input it. You need to know the API's that do that and how to "break" at this location in the debugger. Have you actually read anything about how to do this? Have you looked around here and actually read any other threads? Since your target is a vb program, do you know about vb debugging, which is different, to some extent ? Is it in vb code or p-code ? All things you need to identify.

Regards.

sorry

im using win98 se
softice 4.0.5
smartcheck 6.20 rc 2
windasm vb patched
i ave loged it smartcheck i see my wrong serial but nothing
i ave oppened it windasm i see all strings i tryed to redirect to good boy but ave bad boy all time
i ave tryed to follow step by step all the reg process it softice
and i dont understand

and the prog is not p-code protect, simple vb6
but is launched by the visualstudio 6 like a VS project
i d'ont want the crack or serial but just help how to find it

excuse for the short description but it mi poor english its hard to explain
and sorry again

NLZ:

No need to be sorry. Just trying to have you give the information needed for someone here to actually help you. Perhaps you could post some of the code from the area where it checks if your serial is correct or incorrect and someone here can probably give you better directions on where to look next.

Regards.

With VisualBasic coded apps you could try breaking on MultiByteToWideChar. VB handle the serial in wide char, that means that if you search for your fake entered serial, let's say 12121212, you'll have to search on "31 00 32 00 31 00 32 00 31 00 32 00 31 00 32".

Also if the app gives you "Bad Serial" message, then break on it with MessageBoxIndirectA or RCTMsgBox(i can't remember if "rctmsgbox" is correct). When you break on the message, then return to apps code and scroll back in code window and set breakpoints on all suspecious CALL's like _VbaCmpStr and similiars, and then trace into them. Often you'll have to look far back in code.

JohnWho.