Hello,
I've got some Fasm questions:
(DOS + Fasm 1.51 + command line usage + .com or .exe OUTfiles)

Is EQU the same as = sign ?
I get two different values when creating an absolute LABEL addr using them.

When an EXE starts up:
format MZ
sets CS:0 as CS:IP start up
can I change that to a floating IP entery point defined with
start:
or some other label?

AND, DS - 10h less than CS, so DS:80h = my ARGC command line input count, then ARGV following.
IS it always this way? IS this a given er constant fact ?
DOES Fasm allow a definable .exe header ? and HOW?

IS CS - 30h my environment for an EXE at run time ?
IS string search for CMNDLINE= PATH= BLASTER= CMNDENV=
the proper method? or are they set at a prefixed offset of CS-30h
or even DS-20h ?

DOES Fasm have an INCBIN "filename.ext"
that dumps in a RAW file to the executable like Nasm does?

DOES Fasm have a thingie like

RAW LABELname {
Just write some text in here and refer to it via MOV SI,LABELname
This would be the second line inserted into the OUTfile
This ending would have no CRLF on the end.} sizeofLABELname
This ending would have a CRLF on the end.
} sizeofLABELname
That would be easy to make messages
that have a label and an SIZE EQU $-LABELname

I suspose I could read the manual.doc
But a little help could save me some wasted nights.
Any help would be appreciated.
Thankx in advance.

Bitdog

EQU is text equate, and is substituted before assembly stage, so conditional ifs do not play a role. = is what you would use to define numerical constants, which can be worked with. INCBIN is "file" directive in FASM.

defines data label "mymusic" with contents of file tune.mod

No, they are not equal. Actually in 99% of time you should use "=" to define numeric constants. "equ" defines not numeric but symbol constants at preprocessing time. Read the manual for details.



There are few directives that you can use with MZ format:
segment - define segment
entry - define entry point
stack - sets up the stack size
heap - sets up heap maximum size

Refer in manual: "2.4.1 MZ executable" for details. And I am sure there was example in the DOS package.



Yes, it is "file" directive, I don't know what is NASM syntax of this, but "file" may include in raw form entire file or only part of it.

Refer in manual: "1.2.2 Data definitions" for syntax description.



No, unfortunately. Maybe in some of next versions.

Regards