On Mon, Sep 07, 2020 at 07:48:33PM +0200, Mateusz Viste wrote:
> They are indeed - I've spent more nights than I can count debugging EtherDFS
> and EthFlop while battling with random freezes, memory corruptions, suddenly
> hanging games and such. TSRs are truly a toxic environment. But it's part
On 07/09/2020 18:15, Michael Brutman wrote:
Others have provided small utilities to let WATTCP apps use the mTCP
DHCP program. I think that is a reasonable solution given the history.
Interesting. Any links? mTCP seems to be quite popular nowadays - at
least as much as Wattcp-based
Thanks for the dictionary definition, but I think you missed the point
here. mTCP != WATTCP, and I have no interest in WATTCP. WATTCP is a
library and a set of programs from many contributors while mTCP is all my
work. Being compatible with something that I originally had no knowledge
of an no
On 07/09/2020 05:31, Michael Brutman wrote:
"Exotic" is a strange word ...
Let me help. Quick web search suggests such definition:
"Intriguingly unusual or different"
WATTCP uses its own configuration file, mTCP uses its own configuration file.
My point exactly. There are users now that
"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
The FreeDOS wiki links to a website that no longer exists. Yes, 12 years ago it
was saying "provided free without support.":
https://web.archive.org/web/20081002025059/http://www.trumpet.com.au:80/dosapps/
Today, however, the author's page does not feature such phrase - only a list of
On Sun, Sep 06, 2020 at 02:07:43PM -0400, dmccunney wrote:
> See http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_NTCPDRV
Thanks, I can see there confirmation it's free for personal use:
#v+
Licensing issues on this site are kept short and simple: "These DOS
applications are
On Sun, Sep 6, 2020 at 2:02 PM ZB wrote:
> On Sun, Sep 06, 2020 at 07:52:05PM +0200, Mateusz Viste wrote:
>
> > And the Trumpet TSR itself does not appear to be free:
> > http://www.trumpet.com.au/index.php/products/tcpip-driver.html
>
> From what I see there it's paid only for >=10 units (so
On Sun, Sep 06, 2020 at 07:52:05PM +0200, Mateusz Viste wrote:
> And the Trumpet TSR itself does not appear to be free:
> http://www.trumpet.com.au/index.php/products/tcpip-driver.html
>From what I see there it's paid only for >=10 units (so probably in case
of "corporate use" or similar)
--
On 06/09/2020 19:18, ZB wrote:
Perhaps it could be feasible to improve the programs to make them follow
such simple algorithm:
1. Let's find out, maybe Trumpet TSR offers its services?
2. If it's present, connect using Trumpet...
This is twice the programming work required for networking. Not
On Sun, Sep 06, 2020 at 06:43:34PM +0200, Mateusz Viste wrote:
> Trumpet is a networking TSR, while Wattcp, Watt-32 and mTCP are libraries
> embedded into the executable. Completely different approaches.
Perhaps it could be feasible to improve the programs to make them follow
such simple
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
On Sun, Sep 06, 2020 at 03:49:41PM +0200, Mateusz Viste wrote:
> Sounds good indeed. Is FDNPKG or Gopherus working as well? They rely on
> Watt-32 and Wattcp, respectively. The latter does not have DHCP support
> IIRC.
Now it sounds even better: after I downloaded newest versions of mTCP
package
On Sun, Sep 06, 2020 at 03:49:41PM +0200, Mateusz Viste wrote:
> Sounds good indeed. Is FDNPKG or Gopherus working as well? They rely on
> Watt-32 and Wattcp, respectively. The latter does not have DHCP support
> IIRC.
No, they don't work with my configuration.
Although I have network "up and
On 06/09/2020 02:33, ZB wrote:
Anyway I was able to ping and to log into FTP server - so I can assume
network is present
Sounds good indeed. Is FDNPKG or Gopherus working as well? They rely on
Watt-32 and Wattcp, respectively. The latter does not have DHCP support
IIRC.
Mateusz
Partial success - it turned out I was expecting too much.
I still cannot rely on the tools shipped with FreeDOS (I mean the ones by
M. Brutman) - but some of the utilities from that old Trumpet 2.01 package
seem to work, just they are (compared to Linux tools) rather cumbersome,
that's why I
16 matches
Mail list logo
