There should be no conflict between mTCP and other networking programs.
The only exception is if NetDrive is loaded; WATTCP programs probably don't
like the fake packet driver that NetDrive presents. (Fixing that is on the
to-do list.)

What exactly were you seeing that makes you think there is a conflict?

Side note: The UTF-8 code for Al's was adapted from my mTCP code.



On Wed, Apr 29, 2026, 04:05 hollow-one via Freedos-user <
[email protected]> wrote:

> That's very cool, does it work with MTCP?
>
> I found some programs using WatTCP/32 work and some colide with MTCP suite
> from Michael Brutman, thus asking.
>
> -h1
> On 28/04/2026 22:38, Vladimiro Burlak via Freedos-user wrote:
>
> Hi, is there a compiled version?
> The only file available for download is from 2021.
> At least I couldn't find the latest version.
>
> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
> [email protected]) escribió:
>
>> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>> include (AI-generated) CP437/UTF-8 basic compatibility. It's based on
>> Toyoyo's fork (with AI-generated implementations of updated Ed25519,
>> Curve25519 encryption) of AnttiTakala's fork (which included updates for
>> DH, AES, and SHA256).
>>
>> https://github.com/ajrossnz/ssh2dos
>> https://github.com/Toyoyo/ssh2dos
>> https://github.com/AnttiTakala/SSH2DOS
>> https://sshdos.sourceforge.net/
>> _______________________________________________
>> Freedos-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
> _______________________________________________
> Freedos-user mailing 
> [email protected]https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> _______________________________________________
> Freedos-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to