virtual at 0 as 'tbl'
    times 256 db %-1
end virtual    

    virtual at 0 as 'log'
        Log::
    end virtual

    virtual Log
        db 'Hello!',13,10
    end virtual    

virtual at 0 as 'buffers'
  buffer1 rb 1 shl 26
  buffer2 rb 1 shl 26
  buffer3 rb 1 shl 26
end virtual    

virtual at 0 as 'exe'
        include 'g:/fasmw/source/ide/fasmw/fasmw.asm'
end virtual

    

apparentlly, it cannot be used to compile auxilary executable files.

There is one known issue - fasm 1 unlike fasmg is not able to track the uninitialized data inside VIRTUAL blocks, so any data declared with "?" is going to be stored in the auxiliary file anyway. But I don't know if fixing this is really worth pursuing.

... such pieces might use uninitialized data at the end of the block (especially beyond the 512 bytes that must be put into the image).

DimonSoft wrote:

... such pieces might use uninitialized data at the end of the block (especially beyond the 512 bytes that must be put into the image).

If you need padding data then you shouldn't use the uninitialised data definition for that. It it has to be included then you should be initialising it just to make sure you get what you intend.

Offset   0  Up to 510 bytes of code and initialized data
            Some padding (optionally)
            db 0x55, 0xAA

Offset 512  Uninitialized data goes here    

This version adds the feature of storing VIRTUAL blocks as auxiliary output files, backported from fasmg. It works more or less the same as there:

Code:

virtual at 0 as 'tbl'
    times 256 db %-1
end virtual    

Could you provide a little more info on the environment, file paths and command line arguments?

Edit: I think I found it. The bug shows up when the "-s" switch is used.