can i discuss about PE file structure here?

[hutch--]

I think Bogdan is very much on the money here, while most old timers can in fact edit binary code in hex, it is not a viable method to create working executable files from scratch and the suggestion that it is from a person who is not experienced in assembler programming is simply nonsense.

Discussions about the structure of PE files are in fact reasonable but re-interpreting them in the context of manually editing existing binary files has little to do with PE specs and much more to do with activities that are closer to cracking than programming.

This topic is dead if it even hints in that direction.

[supercoollee]

ok, i have tried to read some example source codes and start to understand the codes in the "low level mnemonics" way.
now what i need is the explanations of the functions in DLLs, starting with creating a window. where should i find them? i prefer CHM files or PDF files if there is any.

BTW: i did successfully bloat up opengl.exe in /examples/ folder to 4Mbytes in size, in case i want to program in that way. but now it's not necessary.

[dedndave]

there are a variety of ways to get info about API functions
a good starting point is MSDN online library

http://msdn.microsoft.com/en-us/library/ms123401(v=MSDN.10).aspx

which, btw, i don't care for their new format because i was used to the old one
you won't have that problem   :P

you can plug an API function name into google and usually the MSDN library entry will be first in the list
for example, try typing "ExitiProcess" into google
this is also true for most structure and lib equate names

[BogdanOntanu]

ok, i have tried to read some example source codes and start to understand the codes in the "low level mnemonics" way.
now what i need is the explanations of the functions in DLLs, starting with creating a window. where should i find them? i prefer CHM files or PDF files if there is any.

You can also check Iczelion's tutorials for creating a simple window and other simple API examples. This should get you started and familiar with the Windows API and basic concepts of Windows programming. You need to understand this basic API stuff very well before moving into more advanced topics like OpenGL or DirectX.

BTW: i did successfully bloat up opengl.exe in /examples/ folder to 4Mbytes in size, in case i want to program in that way. but now it's not necessary.

Adding null bloatware to an PE is usually not a problem but things will get out of control fast when you try to fix labels and jumps and code references and/or when you insert new code in complex algorithms.