public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Alfonso <a.martone@retepnet.it>
To: linux-8086@vger.kernel.org
Subject: writing programs for elks
Date: Thu, 6 Feb 2003 00:13:08 +0100	[thread overview]
Message-ID: <200302011118.58025.a.martone@retepnet.it> (raw)
In-Reply-To: <200301301341.h0UDf5Z25323@preshak.recjai.ac.in>

Almost any 8086 language compiler can be used to write ELKS programs: 
nasm, dev86 (bcc or as86), Borland's Turbo C or Turbo Assembler (the 
TC 2.01 and Tasm 2.0 were made freeware on their site), etc.

I am writing a more complete article about this; I will place it here 
in some days. The only documentation I needed is found in these files:

  elks/fs/exec.c
  elks/Documentation/Text/memory.txt
  elks/Documentation/Text/bin_formats.txt

While DOS functions are accessed via INT 21h, the ELKS uses INT 80h 
(see the sources containing its definitions, e.g. strace.c)

Without using any strange tool, one can easily build an ELKS executable 
with up to 64k of code and up to 64k of data+heap (like the DOS 
"small" EXE model) just prepending a 32-byte header containing code 
and data segment sizes and other minimum information (see exec.c).

hi from south Italy!!
alf



  parent reply	other threads:[~2003-02-05 23:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30 13:41 please help this newbie running asm programs!!! Seemanta Dutta
2003-01-30 16:06 ` Gábor Lénárt
2003-02-05 23:13 ` Alfonso [this message]
     [not found]   ` <1044556130.1597.23.camel@Castle.goembel>
2003-02-07 12:22     ` writing programs for ELKS Alfonso
2003-02-07 21:05       ` Dan Olson
2003-02-05 23:16 ` please help this newbie running asm programs!!! Alfonso
2003-02-11  5:52   ` Phil Goembel
2003-02-12 11:15     ` _main and startup code Alfonso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200302011118.58025.a.martone@retepnet.it \
    --to=a.martone@retepnet.it \
    --cc=linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox