LOW LEVEL C - What else?

[frktons]

Ok I think I found something, with a little flaw:

After compiling, I used Polink with

Code Select Expand

/SUBSYSTEM:console /ALIGN:4096 Console1kRed
and the size is now  1,536 bytes, and it runs.
The flaw is it doesn't allocate a new console, and it writes on previous console stuff.
Strange enough the source code has got the:

Code Select Expand

invoke AllocConsole
to allocate the new one  ::)

The two examples you posted work fine both of them. What option did you use?

P.S. Well I forgot to use /SUBSYSTEM:windows, so when I start from the command
line it doesn't create a new console.

[Vortex]

Merging the sections with the linker option /MERGE can produce smaller executables :

Code Select Expand

\masm32\bin\polink /SUBSYSTEM:WINDOWS /MERGE:.data=.text Demo.obj

[frktons]

Merging the sections with the linker option /MERGE can produce smaller executables :

Code Select Expand

\masm32\bin\polink /SUBSYSTEM:WINDOWS /MERGE:.data=.text Demo.obj

Thanks Vortex. One more to try.  :P

JJ posted this code in his Console1kRed  example:

Code Select Expand


end start
OPT_Res 0
OPT_DebugL /Subsystem:CONSOLE /merge:.text=.data /align:512
OPT_Linker polink
OPT_tmp2asm 1


after the end of the program.

It is the same thing I suppose  ::)

[jj2007]

JJ posted this code in his Console1kRed  example:

Code Select Expand


end start
OPT_Res 0
OPT_DebugL /Subsystem:CONSOLE /merge:.text=.data /align:512
OPT_Linker polink
OPT_tmp2asm 1


after the end of the program.

It is the same thing I suppose  ::)

Sorry, I forgot to take away the RichMasm options. They do the same thing indeed.
I wonder whether /merge:.text=.data is the same as /merge:.data=.text ::)

[frktons]

Sorry, I forgot to take away the RichMasm options. They do the same thing indeed.

OK, thanks  :U