> > I was thinking that it could become necessary to start implementing a
> > FreeDOS version that included natively its own BIOS, and that this
> > combination of FreeDOS/BIOS is implemented entirely native as 32 or
> > 64-bit code...
> In my opinion: 1. is a very good idea. Something which boots
> via UEFI and supports GPT and loads Coreboot / Seabios / other
> BEFORE DOS, so DOS can enjoy a BIOS! I think support for common
> motherboards is somewhat limited yet, but you could check the
> current status. Maybe there is generic support for a wider range
> of boards, given that DOS only needs a limited set of devices?

Sounds like you're suggesting running FreeDOS inside a "box" so that
it can access a BIOS. This sounds similar to an idea posted on our
blog a while back:


Create a very lightweight Linux system that boots, run DOSEmu on
virtual console #1, which immediately boots. The other virtual
consoles provide an ability to run DOSEmu, which also can boot

There should be a simple method to direct the Linux host system to
"shutdown" or "reboot" from within the DOSEmu - but it could be as
simple as: when DOSEmu exits on virtual console #1, present a quick
menu to do a "soft reboot" (restart DOSEmu) or "hard reboot" or
"shutdown" (both affect the Linux host system.)

In this way, a certain level of abstraction or virtualization is realized. [..]

Creating a lightweight Linux distro that boots dosemu instead of getty
would be an interesting experiment. Linux can boot on a purely UEFI
system, but dosemu provides the BIOS to the "guest" FreeDOS.

The host Linux environment wouldn't need to load many (any?) services,
just enough to bring up Linux in console mode and launch dosemu. And
the dosemu process automatically boots FreeDOS.

Basically, you'd see two boot-up processes: a minimal Linux comes up
first, then FreeDOS starts.

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Freedos-user mailing list

Reply via email to