Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!indri!uflorida!beach.cis.ufl.edu!sld
From: sld@beach.cis.ufl.edu (Steven Louis Davis)
Newsgroups: comp.sys.ibm.pc
Subject: Re: 4-DOS : Replacement for COMMAND.COM
Keywords: command interpreter
Message-ID: <20439@uflorida.cis.ufl.EDU>
Date: 9 Jun 89 16:13:11 GMT
References: <2384@canisius.UUCP> <1232@nosc.NOSC.MIL>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: sld@beach.cis.ufl.edu ()
Organization: UF CIS Department
Lines: 21

In article <1232@nosc.NOSC.MIL> file@gandalf.nosc.mil.UUCP (Darren M. File) writes:
>
>  I tried 4DOS for a week, but I took it off my system due to a bug.
>  [file destruction while copying]
>  If 4DOS has this bug, it could also have others.

I have been using 4DOS for about 3 weeks now and like it.  It provides many
features I have become accustomed to using tsr programs like a history
mechanism (ced, dosedit, pced), file completion (filec), a rich command 
language, and on-line help.  I have had no problems such as the file 
destruction while copying (and if I do, i'll get rid of 4dos immediately)
and my only complaint is that the file completion is *not* unix style like
filec.  Instead of completing a name until the first ambiguity is reached
and then prompting the user for more characters, 4dos retrievs the first
possible match (the whole file name) and then if you don't like it, you can
ask for the next match (even this doesn't always seem to work for me).
Also, 4dos cannot complete file names if there is a ".." in the path.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steven L. Davis  Internet: sld@beach.cis.ufl.edu
                 UUCP: ...gatech!uflorida!beach.cis.ufl.edu!sld