"Exotic" is a strange word ... WATTCP uses its own configuration file, mTCP uses its own configuration file. I knew about Trumpet when I started mTCP but not WATTCP. After WATTCP came to my attentioned I looked at it and determined that I would continue to do my own thing.
You did write picoSNTP even though SNTP clients already exist, right? Isn't this another example of a wheel being reinvented? On Sun, Sep 6, 2020 at 9:44 AM Mateusz Viste <mate...@viste.fr> wrote: > On 06/09/2020 17:03, ZB wrote: > > Gopherus works (although still it wants to configure network, that > already > > has been configured using mTCP's DHCP; so it seems Gopherus doesn't do > any > > detection "do I already have network acccessibler?" at all), > > mTCP is kind of an exotic piece of software - its networking > configuration works only with the tools that are supplied with the mTCP > package. > > Back in the day, the usual way to interact with IP/Ethernet networking > was to rely on the Wattcp library (later forked as Watt-32). Watt-32 > uses its own configuration file, so you'd have to set it up first for > being able to use Wattcp/Watt-32 based tools (or rely on DHCP, which is > the default fallback if no config file is found). I can only wonder why > Michael didn't make his software compatible with the Wattcp > configuration file instead of reinventing the wheel. > > > So both programs seem to dislike Trumpet TCP (different API?) > > Trumpet is a networking TSR, while Wattcp, Watt-32 and mTCP are > libraries embedded into the executable. Completely different approaches. > > Mateusz > > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user >
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
