From: Alfonso <a.martone@retepnet.it>
To: linux-8086@vger.kernel.org
Subject: Re: please help this newbie running asm programs!!!
Date: Thu, 6 Feb 2003 00:16:45 +0100 [thread overview]
Message-ID: <200302060016.28257.a.martone@retepnet.it> (raw)
In-Reply-To: <200301301341.h0UDf5Z25323@preshak.recjai.ac.in>
> i am a newbie trying to port and run dos based 8086 programs under
> linux using as86, ld86 and elksemu. i have written a simple program
Under ELKS, you should use ELKS system calls (via INT 80h), instead of
DOS calls (via INT 21h)...! :-)
If you want to port some DOS program, you must take into account that
almost any program has to be modified and recompiled because:
- they assume DOS memory structures and interrupts (int 20h, int 21h,
PSP, environment variables, etc)... ELKS programs are definitely
*clean* with memory, hardware I/O, etc
- they assume DOS memory handling (i.e.: every program can use all
remaining RAM upto 640k)... in ELKS, as in any Unix, a process cannot
say "let's get all available RAM";
- they assume the can do everything with hardware; ELKS programs use
the canonical "/dev/..." special files, and do not require special
handling; i.e.: a screen terminal, a pipe, a disk file, a serial port,
etc, everything uses the canonical open/read/write/close scheme (while
DOS world uses a library for soundcard, the open/close for files; BIOS
or write to screen-memory for terminal I/O, etc).
alf
next prev parent reply other threads:[~2003-02-05 23:16 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 ` writing programs for elks Alfonso
[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 ` Alfonso [this message]
2003-02-11 5:52 ` please help this newbie running asm programs!!! 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=200302060016.28257.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