2560 bytes of FASM

[staticgerbil]

I've finally broken out FASM and WinAsm and started to tinker.

The first thing I've noticed that I haven't worked out is that my .exe has been generating at 2560 bytes since the first compile.

I keep adding code and the .exe is still sitting at 2560b.

Can anyone tell me why this is?

If options may make a difference, I'm using the WinAsm version that has all of the FASM bits and pieces built in and to my knowledge the only options I've changed are the paths so that they match my FASM and OllyDbg folders.

So far I've found the WinAsm / FASM combo really nice to use so thankyou to whoever it was that recommended it to me a long while ago

[hellfire]

I keep adding code and the .exe is still sitting at 2560b.
Can anyone tell me why this is?

Probably padding between the pe sections - for details check this.

[rain_storm]

How many sections does your exe have, and what are they named? You can get the size down by merging all sections into a single ".flat" section.