When mixing object code generated by fasm and cl compilers for:
'section ".data" data readable writeable' fasm generate section with characteristics: 0xC03000C0(in exe file -> result is 0xC00000C0)
but characteristics of the 'standart' data section are: 0xC0000040
When linking the object files linker display the warning:
... warning LNK4078: multiple '.data' sections found with different attributes (C03000C0), and in exe file has two '.data' sections.
Is it possible to solve the problem without using methods similar to this:
section ".adata" data readable writeable
...
fasm ...
cl ...
Link ... /MERGE:.adata=.data ...

The value 0xC03000C0 consists of the following flags (check out the PE/COFF format specification):

• 0x80000000 IMAGE_SCN_MEM_WRITE - generated by keyword "writeable"
  
• 0x40000000 IMAGE_SCN_MEM_READ - generated by keyword "readable"
  
• 0x00000080 IMAGE_SCN_CNT_UNINITIALIZED_ DATA - generated by fasm automatically when the given section contains no initialized data
  
• 0x00000040 IMAGE_SCN_CNT_INITIALIZED_DATA - generated by keyword "data" (you should notice the contradiction that is generated by the fact that you mark the section as containing initialized data, but put the uninitialized data inside)
  
• 0x00300000 IMAGE_SCN_ALIGN_4BYTES - the default data alignment generated by fasm when no other alignment is specified (use "align" keyword in section declaration to specify a different alignment)
  

As you can see, all the flags that are generated can be controlled from the source.

Perfect! So what should follow code after 'section ".data" ' to contain only the following flags:
IMAGE_SCN_MEM_WRITE + IMAGE_SCN_MEM_READ + IMAGE_SCN_CNT_INITIALIZED_DATA

I guess that solve me the problem of two '.data' sections in final executable program.

..would work if there wasn't a default alignment (IMAGE_SCN_ALIGN_4BYTES), and if initialized data is present.

Does the section name ".data$0" prevent the warning?

The linker merges sections automatically based on the "name$order". If there is no default alignment then sections merge as expected. Whereas the alignment can create a gap between parts of the same section. Ideally, only one section would specify section alignment while others are merged bytewise.

How to support this without breaking the ALIGN directive? Doesn't seem possible.

Ideally every fragment of data you create should be aligned appropriately for the given data size. Those "gaps" you're talking about are there for a reason.

Anyway, to get rid of the default alignment, just use "align 1" command in the section directive.

For more clarity on the issue I send a simple example.
p.s.
versions of the microsoft compilers:
Microsoft (R) Macro Assembler Version 7.10.4035
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.4035 for 80x86 - Window DDK package

So either use a right kind of section for uninitialized data (.bss), or put some initialized data into the .data section to stop fasm from generating the uninitialized data flag.

Flat assembler has many advantages over Microsoft assembler. That's why is preferred by me in the case of mixing 'c' and 'asm' code.
In my practice I solve the 'problem' by defining the variables in 'c' file, merge the sections with diffrent names(is not very correct) and in other ways depending on the specifically, but is a elegant solution.
Thanks.