Just wondering if this is something for me or not

[Sorex]

Cool, that solved the error  :U

That's why I asked for such list before as I don't have a clue what I need to include to get some stuff working

[jj2007]

For the lazy programmer:

include \masm32\include\masm32rt.inc

.data
AppName db "Hi", 0

.code
start:   push esi
....
end start

This will slow down assembly by at least 0.2 seconds, but you don't have to worry any more which libraries are needed for a particular project. If you want to understand masm32rt.inc, just go to its location and read the intro.

[MichaelW]

That's why I asked for such list before as I don't have a clue what I need to include to get some stuff working

I don't try to maintain a list of what functions require what libraries and include files, even in my head. For my code I do as jj2007 suggested, so my source effectively includes all of the MASM32 libraries and include files, and all of the Windows API libraries and include files that are normally required, but I'm not sure that this solution will work with WinAsm Studio. What I did in this case is look at the source code for OpenFileDialog (masm32\m32lib\opendlg.asm). When I encounter a problem with an API function not being recognized I look in my local copy of the PSDK. Using GetOpenFileName as an example, at the bottom of the PSDK page under Function Information:

Header      Declared in Commdlg.h
Import library   Comdlg32.lib

The library name matches the name that MASM32 uses, but to determine the correct header (include) file you would need to know that MASM32, at least generally, uses the same base name for both. This same information is available here:

http://msdn.microsoft.com/library/

And for the PSDK you can download any of multiple versions, try searching microsoft.com for PSDK. The version that I use, which BTW is the last one that will install on Windows 98/ME AFAIK, is available here:

http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm

Note that this is effectively an on-line install that uses local files - setup must connect to Microsoft.

[jj2007]

Alternatively, go to \masm32\include and search the whole folder for GetOpenFileName (or whatever function was not recognised).

[Jimg]

masm32rt will work just fine with WinAsm Studio.

[Sorex]

nice tip JJ, I guess I'll use that to start with otherwise I'll lose even more time to figure it all out  :thumbu

btw, it seems that winasm studio is not popular, what do you use instead?

I used ALAB for years (when coding dos stuff) but that was for TASM only, this winasm is nice with it's resource/forms editor

[jj2007]

btw, it seems that winasm studio is not popular, what do you use instead?

Everybody here in the forum uses the famous RollYourOwn Studio (see attachment - drag an asc doc over richmasm.exe and press F6).

[attachment deleted by admin]

[hutch--]

Sorex,

Editors/IDEs are like girlfriends, everyones choice is different. Just pick the one you feel most comfortable with and use it. Keep in mind that the more a project is dedicated to one particular IDE, the less help you can get with a complete project as less people know the details of how it works.

jj has an interesting point, don't be afraid to roll your own, many people have done that and get exactly what they want to code with.