Yup. This is exactly what I was thinking, except you're a good one or
two steps ahead having a better understanding of EFI/UEFI structure than
I.
I was thinking, booting into a stripped down or minimal Linux kernel,
and if required runit environment, then into qemu. With the NesUEFI
method likely
There is no need to clone an 8086.
You can run the entire system or just a CPU in an FPGA.
There are versions for several of the older CPUs out there. Even 486 equvilants.
Just google ‘FPGA 8086 CPU” or similar.
For example, https://hackaday.com/2017/11/03/386-too-much-try-a-186-in-an-fpga/
<
Greetings,thanks for the replay.
I even know,some guy in New Zealand is making XT-clones including new MoBos,but
as U pointed,i am afraid,that project is also dependent on using original
CPUs,which survived.
So do U think,even cloning a 086/088 CPU is impossible?
BTW x86 CPUs was already revers
Greetings.I would most appreciate,if someone would be willing to assemble a team for restoring Legacy HW,mainly Legacy MoBo & CPUs production.If someone would be willing to create a plant for Legacy HW production
On 10/30/24 06:00 pm, Sabina Zelená. via Freedos-user wrote:
Greetings.
I would most appreciate,if someone would be willing to assemble a team
for restoring Legacy HW,mainly Legacy MoBo & CPUs production.
If someone would be willing to create a plant for Legacy HW production,I
would offer my h
Hi Eric,
>>> Is it possible to know if the next FreeDOS release will be compatible
>>> with Windows 3.1, please? I read an article a few months ago and if
>>> I am not wrong, I remember that it talked about this feature.
>> From the email that started this thread: no, this 1.4 release will not
>
I modified the subject of the thread. First of all I am not a software
developer. I started out using MS-DOS
and later moved to OS/2. I still use ArcaOS an my main OS these days
(OS/2 version). It runs on bare metal with UEFI support.
A small company called Arca Noae LLC has developed a UEFI load
As a reminder, Interim Test Builds pull from the nnstable branch of projects
when it exists.
Release builds only pull from the master branch of the projects.
Although the ERROR.LOG issues warning messages regarding which projects are
using their unstable branch, I want to provide a note for th
