> Am 21.08.2016 um 15:33 schrieb Jerome E. Shidel Jr. :
>
> Hello Ulrich,
>
> I will definitely look into it very soon.
> (Probably next weekend. Some changes at work have really limited my free time
> lately)
Hello Jerome,
thanks for the reply. No reason to hurry… :-)
>
Hello Ulrich,
I will definitely look into it very soon.
(Probably next weekend. Some changes at work have really limited my free time
lately)
Rugxulo has also pointed me to a FreeDOS based release that MetaDOS. It
seems to do the automatic networking setup pretty well. Under VirtualBOX,
it
Hi Jerome,
I experimented a bit more with your installer CD to find out the steps how to
install the programs I talked about in my last post.
Luckily most things are already there. Unfortunately there are some bugs.
Crynwr and MTCP are on the CD so you could just install them if you detect
Hi Jerome!
>>> One thing I would like to see make it into the release is some networking. I
>>> don’t think it would be practical to have a universal setup for each and
>>> every machine and NIC at this time. But, it may be possible to have
>>> the installer automatically do this for some of the
Hello,
Rugxulo pointed me at a custom FreeDOS release that has some networking
support. I haven't had time to look at it closely. But, initial quick and
simple tests showed support for VirtualBox and VMware (bridged NIC).
> On Jul 31, 2016, at 8:32 PM, Louis Santillan
A couple weeks late. Apologies.
I like this goal. The current FD 1.2pre 22 doesn't seem to have any
networking subsystem packages installed. For me, this affects our
direction. Michael Brutman has additional applicable analysis about
DOS networking here [0].
WatTCP/Watt-32: Lots of apps.
Hello all,
As you you may already know, we have been working on the FreeDOS 1.2 release.
One thing I would like to see make it into the release is some networking. I
don’t think it would be
practical to have a universal setup for each and every machine and NIC at this
time. But, it
may be