Re: Using FreeDOS In 2022

Liste des GroupesRevenir à c misc 
Sujet : Re: Using FreeDOS In 2022
De : not (at) *nospam* telling.you.invalid (Computer Nerd Kev)
Groupes : comp.misc
Date : 22. Apr 2024, 23:20:05
Autres entêtes
Organisation : Ausics - https://newsgroups.ausics.net
Message-ID : <6626e295@news.ausics.net>
References : 1 2 3
User-Agent : tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i586))
Ben Collver <bencollver@tilde.pink> wrote:
On 2024-04-22, Kyonshi <gmkeros@gmail.com> wrote:
On 4/21/2024 5:07 PM, Ben Collver wrote:
I do like FreeDOS as such, but I would argue that Linux is much more
adaptable to human use. But well, I just like unixoid systems a lot.
I did start with MS-DOS when I was a kid, and I liked it back then, but
it always had too many limitations.
 
From my start i tried to make DOS more Unix-like.  Borland had
grep.exe and i remember using DesqView for multi-tasking.

I like the simplicity of DOS too, but when people talk about using
it instead of modern Linux or Windows it occours to me that after
loading USB, Ethernet, file system (long file name support), and
mouse drivers, Maybe even a full multi-tasking user environment as
you suggest, you're basically building a complex modern OS on top
of DOS one TSR program at a time. But without much documentation or
support. To that end you can run loadlin.exe and just boot Linux
from DOS (or start pre-NT Windows).

Perhaps the nice thing about FreeDOS could be that you can choose
exactly how much of that complexity you want more easily?

--
__          __
#_ < |\| |< _#

Date Sujet#  Auteur
21 Apr 24 * Using FreeDOS In 202238Ben Collver
22 Apr 24 +* Re: Using FreeDOS In 202228Kyonshi
22 Apr 24 i`* Re: Using FreeDOS In 202227Ben Collver
23 Apr 24 i +* Re: Using FreeDOS In 202225Computer Nerd Kev
23 Apr 24 i i+* Re: Using FreeDOS In 20229Ben Collver
24 Apr 24 i ii+- Re: Using FreeDOS In 20221Computer Nerd Kev
24 Apr 24 i ii`* Re: Using FreeDOS In 20227Lawrence D'Oliveiro
24 Apr 24 i ii `* Re: Using FreeDOS In 20226Ben Collver
24 Apr 24 i ii  `* Re: Using FreeDOS In 20225Kerr-Mudd, John
24 Apr 24 i ii   +- Re: Using FreeDOS In 20221Dan Cross
25 Apr 24 i ii   `* Re: Using FreeDOS In 20223Lawrence D'Oliveiro
25 Apr 24 i ii    `* Re: Using FreeDOS In 20222Kerr-Mudd, John
26 Apr 24 i ii     `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
23 Apr 24 i i`* Re: Using FreeDOS In 202215candycanearter07
23 Apr 24 i i +* Re: Using FreeDOS In 20227Kerr-Mudd, John
23 Apr 24 i i i+* Re: Using FreeDOS In 20225Kerr-Mudd, John
26 Apr 24 i i ii`* Re: Using FreeDOS In 20224Andy Burns
26 Apr 24 i i ii +- Re: Using FreeDOS In 20221Ben Collver
26 Apr 24 i i ii `* Re: Using FreeDOS In 20222Ben Collver
27 Apr 24 i i ii  `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
23 Apr 24 i i i`- Re: Using FreeDOS In 20221candycanearter07
24 Apr 24 i i `* Re: Using FreeDOS In 20227Lawrence D'Oliveiro
24 Apr 24 i i  `* Re: Using FreeDOS In 20226Bob Eager
24 Apr 24 i i   `* Re: Using FreeDOS In 20225candycanearter07
24 Apr 24 i i    +- Re: Using FreeDOS In 20221Bob Eager
25 Apr 24 i i    `* Re: Using FreeDOS In 20223Lawrence D'Oliveiro
25 Apr 24 i i     `* Re: Using FreeDOS In 20222candycanearter07
25 Apr 24 i i      `- Re: Using FreeDOS In 20221Bob Eager
24 Apr 24 i `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
22 Apr 24 +* Re: Using FreeDOS In 20225John McCue
24 Apr 24 i`* Re: Using FreeDOS In 20224Lawrence D'Oliveiro
24 Apr 24 i `* Re: Using FreeDOS In 20223John McCue
24 Apr 24 i  +- Re: Using FreeDOS In 20221Scott Dorsey
25 Apr 24 i  `- Re: Using FreeDOS In 20221Lawrence D'Oliveiro
25 Apr 24 `* FreeDOS caveats4Ivan Shmakov
25 Apr 24  `* Re: FreeDOS caveats3Ben Collver
26 Apr 24   `* Re: FreeDOS caveats2Ivan Shmakov
27 Apr 24    `- Re: FreeDOS caveats1D

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal