How can I do section align with format PE?

fasm chooses most minimal amount for you (512-bytes for PE EXE/DLL, 32-bytes for .SYS drivers)
there is no way to set an arbitrary amount

May be Privalov will do it in next version? PE with sections aligned 32-bytes would be nice.

ps. sorry for my english

And wouldn't run on all windows versions

it's not important

Certainly depends what you're doing, and who you are targetting! Sure, would be a nice feature to have (and I can't see any reason not to do it, except avoiding "red tape").

I just hope that people using such a feature will know that their program won't work everywhere - just like executables without imports.

I've never really understood why people say executables without imports don't work. In my experience, and tonight even I tested out a quick one, on the win9x/me and xp windows platform and it worked perfectly fine.

Are there specifics to this?

Try windows 2000, and possible NT4 as well. It's not even "no imports", it's "importing from kernel32.dll". Or rather, "ending up importing from kernel32.dll", it's enough importing say GDI32.DLL since it imports from kernel32. (Could be that the required import is really NTDLL, but I think it's KERNEL32). It "most likely" has to do with how and where the initial thread is started in your process...

My progs writen in FASM dont work under XP (actually don't work as they must do) did you know why ?

Ooops... sorry i fix it =)

its important to have control

Yes. But why this feauture not implemented in FASM? =(

Privalov?

Would be nice if i can switch between 512 and 4096 section alignment for XP and 98.

The 512 alignment for sections in file is a requirement and it should not be changed. The 4096 alignment of sections in memory is needed to allow correct setting of permission flags for section pages, the exception are drivers, which don't utilize the paging mechanism and require memory offsets to reflect the ones in file. So FASM uses 512 memory alignment for drivers (with "PE native" setting) and 4096 for any other file.

The limitation to use only standard alignment in general PE files is needed to keep FASM able to be literal in generating what you've specified (which was always the priority in the FASM's design) - to make the permission flags you specify for the section be correctly set, section needs to be page-aligned.

If you want to hack more into PE structure, you may use a binary output mode of fasm for this purpose - there were some examples floating around.

Do you mean file alignment?
Im sorry on a bit obscured because of my English. My 'section' meant file alignment like specifing at linking time by using the /align:0x200 or /align:0x1000 and /opt:nowin98 to select 0x200 bytes or /opt:win98 to select 0x1000 bytes switchs if you ever use link.exe of MS.



Do you guys talking about this or am i just misunderstood something?

> Do you guys talking about this?
Yes.

But, Privalov: The filealignment could be discarded for the last section right? (Maybe this could be an option?)