format PE GUI 4.0

include 'win32ax.inc'

message db 'Hello!',0

.code

        start:

               invoke  MessageBox,HWND_DESKTOP,message,'Message',MB_OK
               invoke  ShellAbout,HWND_DESKTOP,'mrowek still testing # Flat Assembler','Do you like it?',0
               jmp exit
        exit:
              invoke  ExitProcess,0
.end start
    

You really should just adjust your mindset wrt. windows programming :P

616kb of private data? Not really a problem IMHO. Most of this is one-time overhead.

the task manager is very unaccurate like one of the other users said (it includes all the dll's and resources n stuff the program is using or something like that ), use something like process explorer to find out the real usage.

calpol2004 wrote:

the task manager is very unaccurate like one of the other users said (it includes all the dll's and resources n stuff the program is using or something like that ), use something like process explorer to find out the real usage.

Actually... What it calls from DLLs is basically what i uses in the RAM and such. So if you're worried how much space it takes, you should rely on it. If you go by how much bytes it uses (excluding DLLs and all the things it includes) you're gonna expect it to run in really really poor conditions. Not like it really matters in a small project like the hello programs, but let's say you're coding something as power dependant as halo1 pc. imagin if they only recorded what the exe itself and it's DLLs took of the RAM not including what the OS requires with it... I could see it now... "Only 64 MB of ram needed." Then when the OS takes the other 64 that dosn't exist and the computer crashes, you got a major complaint. So i really don't see the point in getting what the EXE alone uses. One would think, anyway, that the EXE would only use the amount of space that the exe is if you don't include the space of the DLLs. At least that's what i think...

kohlrak wrote:

calpol2004 wrote:

the task manager is very unaccurate like one of the other users said (it includes all the dll's and resources n stuff the program is using or something like that ), use something like process explorer to find out the real usage.

Actually... What it calls from DLLs is basically what i uses in the RAM and such. So if you're worried how much space it takes, you should rely on it. If you go by how much bytes it uses (excluding DLLs and all the things it includes) you're gonna expect it to run in really really poor conditions. Not like it really matters in a small project like the hello programs, but let's say you're coding something as power dependant as halo1 pc. imagin if they only recorded what the exe itself and it's DLLs took of the RAM not including what the OS requires with it... I could see it now... "Only 64 MB of ram needed." Then when the OS takes the other 64 that dosn't exist and the computer crashes, you got a major complaint. So i really don't see the point in getting what the EXE alone uses. One would think, anyway, that the EXE would only use the amount of space that the exe is if you don't include the space of the DLLs. At least that's what i think...

Wrong again

The reason you don't "count in DLLs" is that their code and data is shared between processes. What you need to do is get hold of Process Explorer (or use perfmon.msc which is included with 2k and XP), and look at the memory statistics counter called "Private Bytes".

This figure is the amount of, well, private bytes in your process. Memory not shared with other processes, memory that in low-memory situations will have to be paged out to disk and re-read, rather than discarded and re-read from .exe/.dll.

You make it as if everything not shared is paged to disk... This alone isn't true, last time i check. I was always told that information is only paged to disk when the programs with the highest priority at the time (the ones visible on the screen have second, first is the one on top, and third is the one who's not visible on the screen while the one with higher priority in the processes part of task manager gets higher than them. But i have a feelingthat which is in the parenthesis isn't 100% true but it's what i go on lol) are in the RAM and the paged programs go in order of lowest to highest priority.

Where does the CHM work?

Where does the CHM work?

i mean "live" not work. I musta been in some kinda hurry when typign ti. I know their format, there are lots of them included with fasm... o.O

He probably means where he can leech a warez copy of inwin2k.chm... I bought the book