this post was submitted on 30 Mar 2025
10 points (100.0% liked)
retrocomputing
4630 readers
53 users here now
Discussions on vintage and retrocomputing
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"UEFI does have a legacy compatibility layer" And this is how one may have a "system firmware" that allows both. Could DOS be made UEFI compatible maybe by loading a .sys driver or maybe by replacing io.sys with one that made use of UEFI?
In the early days (before everyone started cloning the IBM PC) replacing IO.SYS was indeed how MS-DOS was ported to other platforms, and so I suppose in theory that could work. However:
Honestly, if I were trying to do something like this I'd probably shoot for a very minimal Linux image that boots directly into something like QEMU/KVM running directly against the Linux framebuffer/KMS API, since the kernel would then presumably provide drivers for the real hardware (instead of using the more limited drivers in the UEFI firmware) and QEMU can already emulate various legacy hardware that software of the DOS era tends to expect to directly communicate with.
Of course, that's not nearly as satisfying a solution as running directly as a UEFI application! I'm just concerned that UEFI isn't really designed to provide equivalent services to IBM-style BIOS, so it would be an uphill struggle.
I think I read this is how HP supplies their "no OS" machines - a very thin Linux with a VM running the FreeDOS fullscreen.