format PE GUI 4.0
entry start
Include 'win32a.inc'

;;;;;;;;;;;;;;;;;;;;;;;;;
;    Data Section       ;
;;;;;;;;;;;;;;;;;;;;;;;;;

section '.data' data readable writeable
_title db 'Basic Web Browser By Calpol2004',0
_class db 'MyWindowClass',0
browserclassname db 'AtlAxWin',0                      ;class name of browser control
browserhome      db 'http://www.google.com/',0        ;page to go to
wc WNDCLASS 0,WindowProc,0,0,NULL,NULL,NULL,COLOR_BTNFACE+1,NULL,_class
msg MSG
edithwnd dd ?
client RECT

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;             Start               ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

section '.code' code readable executable
start:
invoke  GetModuleHandle,0
mov     [wc.hInstance],eax
invoke  LoadIcon,0,IDI_APPLICATION
mov     [wc.hIcon],eax
invoke  LoadCursor,0,IDC_ARROW
mov     [wc.hCursor],eax
invoke  RegisterClass,wc
invoke  CreateWindowEx,0,_class,_title,WS_VISIBLE+WS_SYSMENU+WS_MAXIMIZEBOX+WS_MINIMIZEBOX+WS_SIZEBOX,50,30,700,500,NULL,NULL,[wc.hInstance],NULL
msg_loop:
invoke  GetMessage,msg,NULL,0,0
or      eax,eax
jz      end_loop
invoke  TranslateMessage,msg
invoke  DispatchMessage,msg
jmp     msg_loop
end_loop:
invoke  ExitProcess,[msg.wParam]
;end message loop

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;        Window Procedure           ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

proc WindowProc hwnd,wmsg,wparam,lparam
push    ebx esi edi
cmp     [wmsg],WM_CLOSE
je      wmclose
cmp     [wmsg],WM_DESTROY
je      wmdestroy
cmp     [wmsg],WM_CREATE
je      wmcreate
cmp     [wmsg],WM_SIZE
je      wmsize
defwndproc:
invoke  DefWindowProc,[hwnd],[wmsg],[wparam],[lparam]
jmp     finish
        wmdestroy:
                invoke  PostQuitMessage,0
                xor     eax,eax
        jmp     finish
        wmclose:

                invoke  DestroyWindow,[hwnd]
        jmp     finish
        wmcreate:
                invoke  AtlAxWinInit         ;make class available
                invoke  GetClientRect,[hwnd],client      ;get size of window so browser control is set to the same size
                invoke  GetModuleHandle,0
                invoke  CreateWindowEx,WS_EX_CLIENTEDGE,browserclassname,browserhome,WS_CHILD+WS_VISIBLE+WS_VSCROLL+WS_HSCROLL,[client.left],[client.top],[client.right],[client.bottom],[hwnd],eax,0
                mov     [edithwnd],eax          ;hwnd returned by CreateWindowEx is moved onto edithwnd variable as its a parameter for MoveWindow()
        jmp     finish
        wmsize:
                invoke  GetClientRect,[hwnd],client       ;re-retrieve the window size
                invoke  MoveWindow,[edithwnd],[client.left],[client.top],[client.right],[client.bottom],TRUE        ;adjust size of control
        jmp     finish
finish:
pop     edi esi ebx
ret
endp
;end of window procedure

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;       Import Data           ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

section '.idata' import data readable writeable
library kernel32,'KERNEL32.DLL',user32,'USER32.DLL',atl,'ATL.dll'
include 'apia\kernel32.inc'
include 'apia\user32.inc'
import  atl,AtlAxWinInit,'AtlAxWinInit'
;end of imports            
    

;oWb being an "object pointer"
oWb.Navigate(url)
    

You can check out the DDRAW example that comes with FASM for how to use com objects.

if you don't know the function pointer you can reverse it from the a compilation in c++.

-Write the code in C++
-Put a rarely used inline "__asm RDTSC" write before/after the line you want
-Have c++ compile the exe and open it up in a debugger
-By looking for RDTSC you'll be able to easily find the code C++ generated for say "oWb.Navigate(url)"

r22 wrote:

You can check out the DDRAW example that comes with FASM for how to use com objects.

if you don't know the function pointer you can reverse it from the a compilation in c++.

-Write the code in C++
-Put a rarely used inline "__asm RDTSC" write before/after the line you want
-Have c++ compile the exe and open it up in a debugger
-By looking for RDTSC you'll be able to easily find the code C++ generated for say "oWb.Navigate(url)"

Or just use int 3.

Kenneth wrote:

r22 wrote:

You can check out the DDRAW example that comes with FASM for how to use com objects.

if you don't know the function pointer you can reverse it from the a compilation in c++.

-Write the code in C++
-Put a rarely used inline "__asm RDTSC" write before/after the line you want
-Have c++ compile the exe and open it up in a debugger
-By looking for RDTSC you'll be able to easily find the code C++ generated for say "oWb.Navigate(url)"

Or just use int 3.

Fine if you want to break in a debugger, but useless if you want to locate it in a disassembler, since INT3 is generally used for padding...

So what would you guys suggest? I'm a newb and it would take forever for me to learn what I'm seeing on the debugger.

BigVent wrote:

So what would you guys suggest? I'm a newb and it would take forever for me to learn what I'm seeing on the debugger.

If you start today, it would be forever minus a day.

I don't know where to start.

Cannot pull up your www (gfgidude)

Thanks, I'll start doing searches & such.

~BigVent

BroadcastSystemMessage
PostMessage
PostQuitMessage
PostThreadMessage
SendMessage
SendMessageCallback
SendMessageTimeout
SendNotifyMessage
SetMessageExtraInfo    

I've searched several times for literature regarding keybd_event. I just cannot quite seem to grasp this.

The keybd_event function synthesizes a keystroke. The system can use such a synthesized keystroke to generate a WM_KEYUP or WM_KEYDOWN message. The keyboard driver's interrupt handler calls the keybd_event function.

VOID keybd_event(

BYTE bVk, // virtual-key code
BYTE bScan, // hardware scan code
DWORD dwFlags, // flags specifying various function options
DWORD dwExtraInfo // additional data associated with keystroke
);


Parameters

bVk

Specifies a virtual-key code. The code must be a value in the range 1 to 254.

bScan

Specifies a hardware scan code for the key.

dwFlags

A set of flag bits that specify various aspects of function operation. An application can use any combination of the following predefined constant values to set the flags:

Value Meaning
KEYEVENTF_EXTENDEDKEY If specified, the scan code was preceded by a prefix byte having the value 0xE0 (224).
KEYEVENTF_KEYUP If specified, the key is being released. If not specified, the key is being depressed.


dwExtraInfo

Specifies an additional 32-bit value associated with the key stroke.



Return Values

This function has no return value.

Remarks

Although keybd_event passes an OEM-dependent hardware scan code to Windows, applications should not use the scan code. Windows converts scan codes to virtual-key codes internally and clears the up/down bit in the scan code before passing it to applications.
An application can simulate a press of the PRINTSCREEN key in order to obtain a screen snapshot and save it to the Windows clipboard. To do this, call keybd_event with the bVk parameter set to VK_SNAPSHOT, and the bScan parameter set to 0 for a snapshot of the full screen or set bScan to 1 for a snapshot of the active window.