the xxxx is of course the hwnd value, but important info:
assuming you are using wm_command to try to locate the button push,
you hwnd the result and see the hwnd of the button is 0324 and the
hwnd of the window is 0129
to find the button, use the window value, not the button value to bmsg on
(the other just won't work)
so for the example here, to find our button push we would
BMSG 0129 WM_COMMAND
Note *from the original author*
------------------------------
These aren't the only win32 api calls you need to know in order to crack windows.There are many many more that programs will use, many are derivatives of these calls.
Try substituting a W for the A at the end of some calls, or placingan Ex right before the A. Also, in SoftIce, typing 'EXP GETPRIVATEPROFILE'will give you a list of all of the procs to read from .ini files, and thereare more than the ones i have listed.
- - -
The above statement referring to many many calls is actually an uderstatement
Windows being as overbloated a mess of code as it is, the lists of calls is rather insane.
in one of my OrcPaks, i released a list of wm_* calls
(shamelessly grep'ped from the windows header files)
and if you have seen the DOS interrupt files as well, you have only seen the tip of the iceberg.
At one point I found it useful to go through the intlist and make a file full of all references
to CD-ROM and MSCDEX calls alone (why do I mention these DOS interrupts in this file? SIMPLE:
16-bit windows - which many programs still are written in and use today use mostly DOS calls to
handle protection schemes - like file times, etc... but that is another file ;)
+gthorne'97
ps - anything you think I should have added but left out?
