3 ms·

For those of you missing context, mTCP is a TCP/IP library and some of the more common applications. It runs on anything from an old 41 year old IBM PC up to e

For those of you missing context, mTCP is a TCP/IP library and some of the more common applications. It runs on anything from an old 41 year old IBM PC up to emulated virtual machines. Applications include fresh implementations of a DHCP client, FTP client and server, HTTP server, IRC client, Telnet Client, SNTP client, Ping, and some other goodies. (These are not stale ports of old code.) Everything runs in 16 bit DOS and the library is open source. The target is retro-computing hobbyists and people stuck with embedded solutions that use DOS. A good FTP client can be a godsend in that situation.

tssva 4y ago
Didn't see mention of it in the release notes but did you happen to implement the ability to disable the ftp server login beep via the config file. We exchanged some email regarding this a while ago. If I forget to do so manually the beep sends my dog into a barking frenzy when I connect. You mentioned implementing for the next version.
- mbbrutman 4y ago
  Ouch - I thought I had it and I missed it. I'll email you a patched version.
  - ngcc_hk 4y ago
    Would the core be patched ?
oso2k 4y ago
Thanks a ton Mike! One of these days I want to start working on a djgpp version of the library code. 32-bit clients could be useful for some things.
bennysomething 4y ago
Does each application implement its own tcp up stack? Or does dos have one already?
- mbbrutman 4y ago
  Each program is linked against a TCP/IP library. #defines control what parts each program gets, depending on what it needs. The DOS TSR approach would make TCP/IP a common service for DOS programs. I went with the library approach for speed and customization purposes.