Hi all,

This is dipeshrestha again. I have installed a program called "Itweaku.exe" and it was limited version. I never intended to crack that program thinking that the limited version was programmed seperately and the full version of program is seperately coded. But when i loaded that program in EXESCOPE , i find out that there is a form (number: 166) that have textbox for name and registration code.

i am amazed that the author had hide that form. but it cant be viewed when i run that program. Is that possible to hide that form in such way? Can i used this form for registering program?

program can be found from: www.snet.com.np/dipesh/Itweaku.exe

PLS somebody help me

dipeshrestha
still beginner

Just because the form is there, doesn't mean the code to handle it is. It's much easier to remove the code only.

Also, please don't post direct links to targets on this board. You could be flamed, or worse, banned.

Actually, the link is pointing to his personal Site, not to the software maker's

Hi.
>Actually, the link is pointing to his personal Site, not to the >software maker's

Dunno let the Mod's decide

Btw Post More of your findings,else be prepared to be delete

Regards

Like squidge says there's likely code missing, a smart move but not necessarily that effective unless a *lot* of code has been removed. Let's take a look in W32Dasm for clues...

The DialogID for the reg box in Exescope is 166, A6 in hex. Use the DlgRef in W32Dasm and you can find what looks like complete handling code for all the edit entry controls. Oh oh. Compare the complete structure of this MFC code with working dialog boxes, and you notice it looks to be in OK shape. Especially compare how the procs for all the other dialog boxes begins and you notice one glaring difference - there's no
* Referenced by a CALL at Address:
to begin the proc. Aha. Perhaps all that is missing is the code that calls it after handling the OK button. I'm not sure why there are 4 separate procs but they're all similar in that they seem to be needing a direct call reference. You should get hold of some MFC documentation and find out what all those ordinal calls do, you might be able to narrow down your choices of which is the proper proc to call.

Finding this code which handles the OK button, if it exists, is a little tricky at this point. If you're lucky all that is missing is the call to the proc that you've already found. The other problem is that the dialog isn't actually on screen so you can't do any live tracing. Here you may only be missing a menu item to call it. You can add your own menu item easily enough but what is the proper ID for it that is handled? I suspect the handling code may be there (it's easier just to delete the menuitem), so what you could do is search for any unused menuitem IDs that might be the one you want. Most of them are numbered sequentially so you might be able to find a reference in the deadlisting or a live trace that is handled but "doesn't seem to go anywhere". This might lead to the code which loads the registration dialog resource.

Worse comes to worse this is all code you could create yourself, menu item -> FindResource, LoadResource and you've got the dialog on screen. THEN you can trace the OK button and see if you can join it up with the proc that needs to be called.

None of this means you can register it or the s/n checking routine is actually there, but I suspect you could get a working version of the reg box which (apparently) handles all the input, and go from there. The other way to look at it is how does the demo differ? It seems that 4 or 5 of the dozen or so tab dialogs are "Pro version only" and the only difference seems to be that the "Apply" button doesn't respond when you make a change. What you could do is find out how clicking a checkbox in one of the 'good' dialogs immediately enables the Apply button, while clicking a checkbox in a 'Pro' dialog does nothing.

It may even be lamer than that and all you have to do is permanently enable the 'Apply' button and all changes you make will take effect. That's pretty easy to check and if that's the case the programmer has created a "weakest link". The fact that they didn't remove the registration dialog resource or apparently much of the handling code except maybe commenting out a few linking elements should be a warning to shareware programmers that a little more is needed.

Hope this gave you some ideas,
Kayaker

Thank you Kayaker,

thank u very much for your nice explanation. Now it is all clear to me. B y the way, i am very much sorry to post the DIRECT LINK in this forum. i am thinking that the program is very old and also i have forgotten the site from where i have download that program. I think that it is better to have a look at the program itself, rather than writing all the explanation about that program.....

anyway once again lots of thanks goes to kayaker guru for his nice explanation...

dipeshrestha
Still Beginner