Isn't this the same argument I made for broken hypervisors?

--
Kirn Gill II
Mobile: +1 813-300-2330 <+18133002330>
VoIP: +1 813-704-0420 <+18137040420>
Email: segin2...@gmail.com
LinkedIn: http://www.linkedin.com/pub/kirn-gill/32/49a/9a6


On Thu, Feb 27, 2025 at 4:03 PM tom ehlert via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:

> Hallo Herr Alain Mouette via Freedos-devel,
>
> am Donnerstag, 27. Februar 2025 um 21:53 schrieben Sie:
>
>
>
> > Em 27/02/2025 13:08, Bret Johnson via Freedos-devel escreveu:
> >> I don't know how often you use other versions of DOS (like MS or PC or
> DR or EDR or ...) compared to FreeDOS, but a TSR would solve the problem
> for all of them while modifying FreeDOS would only fix FreeDOS.  I
> personally prefer MS-DOS and mostly use others (including FreeDOS) just for
> compatibility testing.
> > I have been responsible for a lot of DOS boxes running 24/7 for the las
> > 20+ years (peak was 100, now just a few)...
>
> > FreeDOS is much more stable then MS-DOS due ot:
> > 1) Eric Auer did a nice job flushing files to disk which lowered
> > considerably power failure problems
> How exactly did he "flush to disk"? Other then "I don't cache writes"?
>
> > 2) It is much better then MS-DOS for compatibility with modern machines,
> > specialy big disks and memory
>
> > So I vote for implementing whatever is needed in FreeDOS's kernel. This
> > way it will be more compatible with big disks too
>
> I vote to do nothing about *this particular* machine. It's most likely a
> buggy BIOS/CSM or
> buggy firmware (unlikely, else windows wouldn't work), and not worth
> throwing valuable developer time at.
>
> Just don't execute DOS on this system.
>
> Tom
>
>
>
> _______________________________________________
> 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