I got some mail, thanks for all.
One asked me where to download it to inspect,
it's here.
ftp://ftp.microsoft.com/bussys/Clients/LANMAN/
Run with /d option or use unzip for each file.
One told me LANMAN works fine with FreeDOS 0.99.
If it's really, this is important matter I think.
He also told
On Saturday 12 May 2007 20:11, Florian Xaver wrote:
> Hi Jim, I all!
Hi!
> *Using 4DOS as standard command tool, and Bash or freecom as choice.
4DOS is okay, but I would prefer to have Freecom by default, and the choice to
switch to bash/4DOS, because Freecom is the most similar to MSDOS
COMMA
Hi guys,
IMHO, we should list small and simple things to do first,
Specially because it is faster and we have not enough manpower :(
while we all want many things, we have to take care of our dreams
otherwise we can stall just like gnu Hurd, which is a *really* amazing project
but is almost dead
Florian Xaver wrote:
> Hi Jim, I all!
>
> What should change with FreeDOS 2.0? Some ideas, I think, they have to
> be a must :-)
>
>
> *Using an Editor which supports large files (like FED or SETEDIT)
>
FreeDOS Edlin can support large files!
Gregory Pietsch
-
> http://sourceforge.net/projects/doszip/ evolves... :-)
I don't like it. First time I tried it it looked ok...but there are
much better file managers out there.
> > *No more 386- support
Most changes, maybe all, which has been made, are for 386+ computers.
So one can use FreeDOS 1.0.
> I don't
Florian Xaver wrote:
> *Using an Editor which supports large files (like FED or SETEDIT)
Updated FED has been announced to a small audience only so far. For all
others: It's at http://www.bttr-software.de/fed/ :-)
> *One standard file manager (my choice would be FW or NDN)
http://sourceforge.ne
Hi Jim, I all!
What should change with FreeDOS 2.0? Some ideas, I think, they have to
be a must :-)
*Using 4DOS as standard command tool, and Bash or freecom as choice.
*Using JEMM as memory manager
*Using HX Extender & Co to support Windows programs in DOS
*PythonD as modern script language
*Usi
