Programming Forums - 32 bit assembler on x64 windows

Programming Forums (http://www.programmingforums.org/forumindex.php)

- Assembly (http://www.programmingforums.org/forum20.html)

- - 32 bit assembler on x64 windows (http://www.programmingforums.org/showthread.php?t=11147)

32 bit assembler on x64 windows

I guess I'm looking for an environment that allows me to code in 32 bit assembly on my x64 bit version of windows. I know that I should probably dual boot into x86 windows but I'd rather keep that space for more important things. And besides, it's a lot easier to use a program than a new OS. Any help would be most appreciated.

Well your xp x64 windows can still run 32 bit code so you wont need a special assembler for x64 just any x86 one will do.

The one i used is MASM32

http://www.masm32.com/

the website is bad on the eyes, but its meant be compatible with MASM. You can use any editor to write the source and then just assemble it with MASM32. Its still only 32-bit, but unless you really need to program in 64 bits it is all you will need.

edit:- there is also NASM which is good too.

http://sourceforge.net/projects/nasm

I'd recommend FASM. With that you'd be able to write 32bit or 64bit programs as you please.

Eoin that looks great. I never heard of FASM before. Thanks.

FASM is pretty good, you can even write 64-bit device drivers in it.

Another 64-bit assembler is GoAsm, and it's pretty slick but from what I hear, it has a week macro system (especially compared to systems like MASM.)

Quote:

Originally Posted by Mad_guy

...it has a week macro system (especially compared to systems like MASM.)

FASM's macro system is also weak, but you can do some fancy things with it once you get to grips with it. I point to my own inlineable procedures as a shameless plug :rolleyes: .

Which one is best for beginners?

I can't say something about FASM or NASM. I have only been using TASM and MASM. I should recommend MASM to a beginner. You can almost write code as you were writing C code using MASM. It is very simple thanks to its macro system. You will also get a lot of tutorials and sample applications with the assembler.

FASM mixed with the Win32 API is pretty easy to pick up. I'd had a go with MASM and not really gotten anywhere, tried FASM and had a working GUI'd Win32 app running within a few hours.

This is what I came up with. It's laughable in just about every respect, but it's a start. I call it 'FDelete' because it's made with FASM and it deletes things:

format PE GUI 4.0
entry start
 
include '%fasminc%\win32a.inc'
 
ID_EDIT      = 101
ID_DIALOG    = 50
MB_INFO      = MB_OK+MB_ICONINFORMATION+MB_SETFOREGROUND
MAX_PATH     = 100h
 
section '.data' data readable writeable
 
  _edittext   rb MAX_PATH
  _strbuff    rb 1024
 
  _progname   db 'FDelete',0
  _cnd          db 'Could not delete: %s',0
  _fsd          db '"%s" successfuly deleted',0
 
section '.code' code readable executable
 
  start:
    invoke    GetModuleHandle,0
    invoke    DialogBoxParam,eax,ID_DIALOG,HWND_DESKTOP,DialogProc,0
    invoke    ExitProcess,0
 
proc DialogProc uses ebx esi edi,hwnddlg,msg,wparam,lparam
    cmp    [msg],WM_COMMAND
    je    wmcommand
    cmp    [msg],WM_CLOSE
    je    wmclose
    xor    eax,eax
    jmp    finish
  wmcommand:
    cmp    [wparam],BN_CLICKED shl 16 + IDOK
    jne    processed
    invoke    GetDlgItemText,[hwnddlg],ID_EDIT,_edittext,MAX_PATH
    cmp    eax,0
    jbe    processed
    invoke    DeleteFile,_edittext
    cmp    eax,0
    jne    success
    jmp    failure
  success:
    cinvoke wsprintf,_strbuff,_fsd,_edittext
    jmp    show
  failure:
    cinvoke wsprintf,_strbuff,_cnd,_edittext
  show:
    invoke    MessageBox,[hwnddlg],_strbuff,_progname,MB_INFO
    jmp    processed
  wmclose:
    invoke    EndDialog,[hwnddlg],0
  processed:
    mov    eax,1
  finish:
    ret
endp
 
section '.idata' import data readable writeable
 
  library KERNEL32,'KERNEL32.DLL',\
      USER32,'USER32.DLL'
 
  import KERNEL32,\
     GetModuleHandle,'GetModuleHandleA',\
     ExitProcess,'ExitProcess',\
     DeleteFile,'DeleteFileA'
 
  import USER32,\
     DialogBoxParam,'DialogBoxParamA',\
     GetDlgItemText,'GetDlgItemTextA',\
     MessageBox,'MessageBoxA',\
     EndDialog,'EndDialog',\
     wsprintf,'wsprintfA'
 
section '.rsrc' resource data readable
 
  directory RT_DIALOG,dialogs
 
  resource dialogs,ID_DIALOG,LANG_ENGLISH+SUBLANG_DEFAULT,fdeldialog
 
  dialog fdeldialog,'FDelete',0,0,190,65,WS_CAPTION+WS_POPUP+WS_SYSMENU+DS_MODALFRAME+DS_CENTER
    dialogitem 'STATIC','File Path:',-1,10,10,70,8,WS_VISIBLE
    dialogitem 'EDIT','',ID_EDIT,10,20,170,13,WS_VISIBLE+WS_BORDER+WS_TABSTOP
    dialogitem 'BUTTON','OK',IDOK,130,40,45,15,WS_VISIBLE+WS_TABSTOP+BS_DEFPUSHBUTTON
  enddialog

BTW, the odd indentation is caused by the forum.