From: Harry Kalogirou <harkal@gmx.net>
To: Michael Kallas <michael.kallas@web.de>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: DOS .exe file support
Date: 03 May 2002 19:59:19 +0300 [thread overview]
Message-ID: <1020421999.662.15.camel@cool> (raw)
In-Reply-To: <200205030637.g436bBX20072@mailgate5.cinetic.de>
Την Παρ, 03-05-2002 στις 09:37, ο/η Michael Kallas έγραψε:
> Hi,
>
> Harry Kalogirou <harkal@gmx.net> schrieb am 29.04.02:
> > Hi,
> > I wonder from the first time I let my eyes on this project, what the
> > EXE file support in the kernel configuration means? I simply don't see
> > any way of running a DOS .EXE executable in ELKS. Maybe if it was a COM
> > file but even then we should emulate all the DOS _system_ calls. Am I
> > missing something bigger here, or we should just remove it from the
> > tree?
>
> If this should be considered for being implemented any time, I suggest
> having a look at http://www.freedos.org because FreeDOS is in beta stage
> now already for quite a while and is quite advanced.
> They even have FAT32 support now (but no LFN yet) and they also
> support swapping.
> Maybe ELKS could be something like a multitasking environment able to
> execute linux/elks and DOS programs?
>
ELKS will never be able to run .EXE files. Even if we emulate all the
DOS system calls, the memory model is different. To that add that most
of DOS programs - if not all - use directly the hardware and that is
imposible to multitask on an 8086. DOS programs do all sorts of _wild_
things with the machine (from hooking to interupts, to reprogramming
timers chips, etc) , that require the program be the only thing running.
About the swap thing you say, I don't see how they can swap out. Maybe
they implement it in a _might work, might crash_ way.
Harry
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-05-03 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 6:37 DOS .exe file support Michael Kallas
2002-05-03 13:25 ` Alan Cox
2002-05-03 15:13 ` Hard drive problems? Dan Olson
2002-05-03 15:54 ` pauln
2002-05-03 17:05 ` Harry Kalogirou
2002-05-03 17:49 ` Dan Olson
2002-05-04 6:25 ` Harry Kalogirou
2002-05-04 15:35 ` Blaz Antonic
2002-05-04 18:32 ` Riley Williams
2002-05-06 23:24 ` Dan Olson
2002-05-03 18:20 ` pauln
2002-05-03 16:59 ` Harry Kalogirou [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 16:17 DOS .exe file support Harry Kalogirou
2002-04-29 21:27 ` Riley Williams
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=1020421999.662.15.camel@cool \
--to=harkal@gmx.net \
--cc=linux-8086@vger.kernel.org \
--cc=michael.kallas@web.de \
/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