| 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 house for free usage for this purpose(U know,that former school building,U r all ignoring me for pretty long time on this forum,maybe because I am the only female here).Y to accept the end of Legacy HW & create virtual BIOS replacements...Y to accept that UEFI garbage @ all? If Legacy architecture is abandoned,it may become public accessible,or some1 could reverse-engineer Legacy processors & MoBos & start to create new old HW,this should be the future of DOS,do not accept UEFI,restore the Legacy era.Have own HW for (Free)DOS. Live long & prosper. Sent from my BlackBerry Passport,RIM OS 10 smartphone named <b>Uhura</b> after deceased Star Trek actress Nichelle Nichols. <b><font color="darkgreen">With regards Sabina Zelená[=Green]. LIVE LONG & PROSPER,live & let live=DO NOT EAT,NOR WEAR ANIMALS,nor do not pay Their Murderers & oppressors,please. Shalom/Peace/Shanti/Mier/Nyugalom.</b>
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 loader for ArcaOS. They way I understand this is possible as the UEFI simply switches the Intel CPU to well 4 GB protect mode (legacy mode). But with OS/2 this is easier then DOS as it does not lean that hard on the BIOS after the OS has started. With DOS and Freedos this is most likely more complex as it is more depended on the BIOS. I have never liked virtualization from a "fun" perspective. I like it when an OS runs bare metal. I do not want to start a full blown Linux Desktop then start Virtualbox and run ArcaOS or MS-DOS. I like the OS to be really lean where possible. With the current X86S project coming up this is bad news for FreeDOS as this would also possibly kill hardware virtualisation in for example Virtualbox. QEMU can do full CPU instruction I understand and you can run this way FreeDOS also on an ARM CPU. But the question is how close can you bring FreeDOS to the hardware. I have always wondered if you can not stick QEMU directly in a UEFI loader. But how would QEMU then work for Freedos ? Well the crucial idea is that the UEFI loader never makes the call ExitFromBootServices(). Instead QEMU uses the disc and USB services offered by the UEFI firmware. QEMU becomes native UEFI app. When comes to being direct the video output is send directly the UEFI GOP frame buffer. QEMU then uses the UEFI disc services to read/write the FAT 32 volume on disc. You would still have a VM but its as close to the hardware as possible :-) This sollution might even work then on ARM CPU's and systems with X86S. As the UEFI loader would provide the X86 instruction chipset. I have also read that you can use multiple CPU's cores in EFI apps. I do not know if this can help speed up the performance somehow. Again I am not a developer, the whole idea was inspired by this project: https://github.com/shadlyd15/NesUEFI As NES emulator build inside a UEFI loader and it does not even use any other OS it uses the UEFI services. Effectively UEFI is as system BIOS from my perspective. The big difference with a legacy BIOS is the "ExitFromBootServices". As UEFI expects the OS to tale over. Your thoughs and comments are welcome. Roderick On 10/29/24 08:20 pm, Michał Dec via
Freedos-user wrote:
| ||
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
