Hello. I'm still writing my on OS (for real mode). To make larger Applications, it is necessary to define segments in a source-code. For example:

mov ax,gfx
mov es,ax
.
.
.
.
gfx: <- own segment
include "picture.dat"

txt: <- another segment
.
.
.


How can i solve this with Flatasm?
(I still use compat.inc to create 80286-code)

Meister,

This depends on executable format your OS supports. For MZ exe there is segment directive.

Mhh..there is no special format. every application starts with a header:

.include "compat.inc"
.286

org $0000

db "APL"
db 0 ; class
db 1,19 ; Min. OS-Version
start:
....code...

The OS loads an Application until a) the end of file is reached or b) the current Sector-buffer > Himem (himem is the last segment available for Apl-files - above himem there are residents/drivers).

Meister,

Are programs loaded at fixed address (or they should be self-relocatable)?

The APL-Files always starts at $0800:$0000 (residents also start at offset $0000, but with another segment)

Meister,

In this case linear address for (probably 16-byte aligned) label gfx will be $8000+gfx and logical will be ($800+gfx/16):0.

How can i align labels with Fasm? And how can i load this "label-segment" ? I'm thinking about writing different 64K-Binarys and joined them to a big file. But then "File A" do not know where in "file B" is the address of label xy....

Meister,

As you might guess, "align directive aligns code or data to the specified boundary".

Good way to learn how to do something is to examine how it's done already. Are you familiar with executable formats (DOS COM/MZ-EXE, for example)?

COM yes, EXE no Thank you for your help. I think i will solve this problem by looking to other formats at the moment, 64K is enough (the largest application is about 10K, a harddrive test program)