compile "boot.asm" ; result in boot.bin file, will seek kernel.bin in the root
compile "startup.asm" ; result in startup.html file
compile "kernel.asm" ; result in the kernel executable file
compile "browser.asm" ; result in the stand alone browser

BOOT:
file "boot.bin";assume it fits in 512 bytes
BOOTDIR=512;the bootdir starts at DS:512
bootdir:;the boot drive root directory, contain offsets to files
dd @f-$-4;size of dir
dd boot
dd startupPage
dd browser
dd kernel
dd script
@@:
boot:
dd BOOT
db boot",0
kernel:
dd KERNEL
db "kernel",0
startPage:
dd STARTPAGE
db "startup",0
script:
dd SCRIPT
db "script",0
KERNEL:
file "kernel.bin";assume the image is mounted in a linear adress space
BROWSER:
file "browser.bin";the browser
STARTPAGE:
file "start.html";the startup page
SCRIPT:
db "kernel browser start.html",0;assume that boot will read script to know that it should open kernel with brower start.html in parameter, inducing the launch of the browser with the startup page
    

compile "errormsg.asm";compile the dll

format PE GUI 4.0
entry start

include 'win32a.inc'

section '.text' code readable executable

  start:
        invoke  ShowLastError,HWND_DESKTOP
        invoke  ExitProcess,0

section '.idata' import data readable writeable

  library kernel,'KERNEL32.DLL',\
          errormsg,'ERRORMSG.DLL'

  import kernel,\
         ExitProcess,'ExitProcess'

  import errormsg,\
         ShowLastError,'ShowLastError'
                                                      
    

compile "file.bin" {;create a binary file from another source code
include "file.asm"
}

compile "file1.bin" {;create a binary file from code
mov eax,ebx
}

myfile = "file2.bin"

compile myfile {;create an empty binary file
}

    

hem, in fact, only a sort of compile block could be interresting cause it can cover all usecases

Code:

compile "file.bin" {;create a binary file from another source code
include "file.asm"
}

compile "file1.bin" {;create a binary file from code
mov eax,ebx
}

myfile = "file2.bin"

compile myfile {;create an empty binary file
}

    

file 'LOL.BIN'     

This would help us have two ORGs in one program without specifically compiling each part.

Why not have multiple modules in source, each with its own ORG / adressing space setup?

org 9000h

Set the address to assemble to 0x9000.

phase address

Continue to produce code and data for loading at the current address but assemble instructions and define labels as if they originated at the given address. Useful when producing code that will be copied to a different location before being executed (e.g., an overlay).

dephase

End phase mode assembly.

Code:

file "kernel.bin";assume the image is mounted in a linear adress space
BROWSER:
file "browser.bin";the browser    

include "kernel.asm"
BROWSER:
include "browser.asm"    

This would help us have two ORGs in one program without specifically compiling each part.

virtual at 0 ;offset
; code ...
end virtual
    

we wouldn't need Windows and Gates