ASM Community

NASMX has to do some macro magic to wrap up those external function calls that have extra formatting symbols and whatnot.

What you are looking for is to use invoke for those particular calls, not call...

invoke ExitProcess, DWORD 0

HtH ;)

Nice catch jakor, as "global start" would solve the other half of his problem by satisfy liking requirements.

However, invoke is still needed, so take a look at the following code and adapt accordingly...

%include "C:\nasmx\inc\nasmx.inc"
%include "C:\nasmx\inc\win32\windows.inc"
%include "C:\nasmx\inc\win32\kernel32.inc"
%include "C:\nasmx\inc\win32\user32.inc"

global start


	var db "OMG", 0


	uvar resb 256


	start:
	mov eax, DWORD
	invoke ExitProcess, DWORD 0

HtH ;)

To what extent are you familiar with the actual invoke macro? Handling the parameters is only half of what invoke does.

If you look at the naming (mangling) conventions in Kernel32.dll, you will notice that ExitProcess is actually _ExitProcess@4. This, or something like this, is the case for almost every other function/variable found in the DLLs... and really most other linked code developed/used in a higher level language.

Invoke encapsulates the full symbolic library name so that you don't have to deal with junk symbols. Secondly, invoke tracks library call declarations and ensures EXTERN is issued appropriately, only once, and only if needed.

If you want to use CALL with the new NASMX system (since things have changed from NASM32) you can use this new CALL macro.

%imacro CALL 1
%push call
	%ifdef __imp_defined_%1
		%ifndef __imp_declared_%1
			EXTERN	__imp_defined_%1
			%define	__imp_declared_%1
		%endif
		call __imp_defined_%1
	%else
		call	%1
	%endif
%pop
%endmacro

I've put it in my BKMACROS.INC file for when I use my "NASMX_COMPATIBLITY" mode, but you could add it straight to your NASMX.INC file so you wouldn't have to add any extra includes later on. Below is a rewrite of DEMO1.ASM using the above macro located in NASMX.INC

%include '..\..\..\inc\nasmx.inc'
%include '..\..\..\inc\win32\windows.inc'
%include '..\..\..\inc\win32\kernel32.inc'
%include '..\..\..\inc\win32\user32.inc'

entry    demo1


proc     demo1

    push      dword szTitleTwo
    push      dword szContentTwo
    call      my_p

    push      dword MB_OK
    push      dword szTitle
    push      dword szContent
    push      dword NULL
    call      MessageBoxA

    xor       EAX, EAX
    push      EAX
    call      ExitProcess
    ret

endproc

proc     my_p
sz_Content    argd
sz_Title      argd

    push      dword MB_OK
    push      dword argv(sz_Title)
    push      dword argv(sz_Content)
    push      dword NULL
    call      MessageBoxA
    ret

endproc

_data
    szTitle:       db   'Demo1', 0x0
    szTitleTwo:    db   'Demo1 Procedure', 0x0
    szContent:     db   'Hello from the Application!', 0x0
    szContentTwo:  db   'Hello from the Procedure!', 0x0

Hopefully this helps you do what you want with NASMX. This wasn't added to NASM32 because there wasn't a high enough demand for it and we wanted to keep overloading of opcodes to a minimum. IIRC there was also one or two bugs that occured due to how the old system worked with doing this (I think it was the argument counting or something like that) it's been a while.. that doesn't apply anymore with the NASMX versions.

Regards,
Bryant Keller