Friends, the final solution to "UEFI problem" - is switching to the
opensource coreboot BIOS (although that may involve switching to the
worthy hardware compatible with coreboot). coreboot's default payload
- SeaBIOS - is a modern implementation of a classical BIOS, which is
written in C and is more refined in general. Moreover, you can even
take a FreeDOS virtual floppy and put it inside your coreboot+SeaBIOS
ROM's free place of a BIOS chip - and it will be permanently available
as a boot entry of your system. Efficient and simple, and don't have
to deal with the problems of UEFI crapware that has been coded for a
bowl of rice

2023-01-24 23:38 GMT+03:00, Steve Nickolas <usots...@buric.co>:
> On Tue, 24 Jan 2023, Bret Johnson wrote:
>
>> For purposes we're discussing here, I don't think DOSBox (or any of its
>> forks, including vDOS) is a viable solution.
>>
>> DOSBox really isn't DOS.  It's an environment designed to run certain
>> DOS applications.  A lot of stuff is missing in DOSBox that's needed to
>> make it a "real enough" DOS to be used for development and testing.
>> E.g., a lot of the internal structures that some DOS "extenders" need to
>> look at (like certain TSRs and Device Drivers) simply don't exist on
>> DOSBox.
>>
>> A perfect example of this are the "standard" DOS Devices: NUL, CON,
>> COM1-COM4, AUX, LPT1-LPT3, PRN, and CLOCK$.  In DOSBox, the only two
>> that exist in a form where other programs can "see" them using standard
>> methods (by scanning through the linked list of Device Driver addresses)
>> are NUL and CON.
>>
>> Things like that can cause lots of problems in certain situations.
>
> Though the hardware emulation may be useful, it would be better for such a
> situation to use that as a base to run an actual DOS on.
>
> -uso.
>
>
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>


_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to