Hi Tom M.!
> How is that done? Where does one obtain the BIOS layer,
> and how would it be applied?
I expect others to have better answers, but I was thinking
in the direction of SeaBIOS / coreboot, which can provide
open source BIOS. After all, a BIOS is just software. You
can load SeaBIOS as
On Sat, Nov 10, 2018 at 6:27 AM Tom Ehlert wrote:
> > Not sure how to fold in the "16bit v 32bit" section or the "UEFI"
> > section, but I may add a section at the bottom of "Releases" that
> > talks about this (probably "Features" or "Assumptions") just to have
> > everything in one page.
>
> "16
I'm running QEMU 3.0.0 on Fedora 29. Works fine over here.
This is the command line I use to launch QEMU:
qemu-system-i386 -m 32 -k en-us -rtc base=localtime -soundhw
sb16,adlib,pcspk -device cirrus-vga -display gtk -hda
/home/jhall/lib/qemu/drive_c.img -cdrom
/home/jhall/lib/qemu/FD12CD.iso -dri
On Sat, Nov 10, 2018 at 8:15 AM Eric Auer wrote:
[NightDOS]
> > my vote: remove from road map.
>
> My vote: Treat as a friendly project, not part of a DOS distro.
>
I do consider NightDOS a friendly project. I'm very interested to
watch their progress. You can watch their Milestones via their Goo
> My vote: Treat as a friendly project, not part of a DOS distro.
> About the UEFI thing: The method of choice would indeed be to
> load a BIOS layer as UEFI module and then load a normal DOS.
> Regards, Eric
How is that done? Where does one obtain the BIOS layer, and how would it be
applied?
Hi Eric,
>> I took the time to look into what the night dos kernel...
>> what they describe as goal is some sort of OS/2, WINDOWS 3.11
> While their goals are noble, I doubt that they will achieve good
> compatibility with most DOS stuff. And I agree that they should
> use more C in their code t
Thanks for giving it straight. I was thinking TRIM was a kind
of screen saver for hard drives, keeping over worked cells
from being burned out. I never though about speed since
all cells in solid state devices are accessed at the same speed
no matter where they are on the drive, but they can be dam
Hi Tom,
> I took the time to look into what the night dos kernel...
> what they describe as goal is some sort of OS/2, WINDOWS 3.11
While their goals are noble, I doubt that they will achieve good
compatibility with most DOS stuff. And I agree that they should
use more C in their code to avoid
> Not sure how to fold in the "16bit v 32bit" section or the "UEFI"
> section, but I may add a section at the bottom of "Releases" that
> talks about this (probably "Features" or "Assumptions") just to have
> everything in one page.
"16bit v 32bit":
I took the time to look into what the night d
