VOGONS

Common searches


First post, by mbbrutman

User metadata
Rank Member
Rank
Member

A new mTCP is available. Here are some of the highlights:

  • Much improved DNS support, including a local HOSTS file and support for a local domain name.
  • TCP/IP flow control improvements for slow/bad connections and bug fixes for improved compatibility.
  • Improved compatibility with "WiFi" modems (ESP8266 devices) running SLIP firmware.
  • Proper dynamic DNS support for the FTP server.
  • Many bug fixes and some new features for the HTTP server.
  • A slightly more accurate SNTP, an additional Telnet config to fix screen drawing problems with some Telnet BBSes, broadcast Ping support, and other miscellaneous fixes and improvements sprinkled throughout.

The bug fixes and compatibility improvements are worth the time for the upgrade.

And here is where you can find it ...

No Ethernet? No problem!

  • Packet drivers exist for SLIP and PPP so you can use a standard serial port.
  • Other packet drivers exist for IBM Token Ring and Arcnet, making them look like Ethernet
  • PLIP (IP over your parallel port with a LapLink cable) is reported to work.

Reply 2 of 14, by keropi

User metadata
Rank l33t++
Rank
l33t++

new mTCP is always good news!
thanks for the heads up mbbrutman!

🎵 🎧 PCMIDI MPU , Orpheus , Action Rewind , Megacard , MK8330 and 🎶GoldLib soundcard website

Reply 5 of 14, by mbbrutman

User metadata
Rank Member
Rank
Member
maxtherabbit wrote on 2022-07-02, 15:21:

The hostname directive disappears from the config file after DHCP is run

Please see the PDF file ...

HOSTNAME is kind of weird in that it is both an input and output to DHCP. On the DHCP request the hostname is sent. The DHCP server may override it, so the line gets moved to the bottom of the file with the other DHCP server provided parameters.

Reply 7 of 14, by mbbrutman

User metadata
Rank Member
Rank
Member

What router/DHCP server is this? I really need a proper bug report with a packet trace to tell you what is going on.

If your router is doing this, it seems like bad behavior but it is not really affecting anything. None of the mTCP programs use the hostname field. It is just a request to a DHCP server so that other machines can find your machine by name. But if your DHCP server doesn't cooperate, well, that seems like a problem.

Reply 9 of 14, by maxtherabbit

User metadata
Rank l33t
Rank
l33t
mbbrutman wrote on 2022-07-02, 16:54:

What router/DHCP server is this? I really need a proper bug report with a packet trace to tell you what is going on.

If your router is doing this, it seems like bad behavior but it is not really affecting anything. None of the mTCP programs use the hostname field. It is just a request to a DHCP server so that other machines can find your machine by name. But if your DHCP server doesn't cooperate, well, that seems like a problem.

The hostname field was populated before running DHCP. After running DHCP, it disappears from the config file and my router shows the hostname as "DOSRULES" - presumably your default.

20220717_211909.jpg
Filename
20220717_211909.jpg
File size
1.7 MiB
Views
491 views
File license
Public domain
Filename
MTCP.CFG
File size
2.43 KiB
Downloads
10 downloads
File license
Public domain

Reply 11 of 14, by GuillermoXT

User metadata
Rank Member
Rank
Member

My 386pc has a 16GB CF using Dos 7.1 Fat32 and supports long file names. What is necessary to get the files copied with Filezilla? When I try copying Midifiles with more than 8 letters i always get an error. Any ideas?

My Retrosystems:
K6-2 400 running Win98SE
P1-133 with Win3.11
Tandon 286-8MHZ Running DOS 5.0 on XT-IDE Card

Reply 12 of 14, by mbbrutman

User metadata
Rank Member
Rank
Member

Assuming you are running the FTP server on the 386, it only supports 8.3 filenames. mTCP supports everything from DOS 2.1 and up, but only with standard DOS 8.3 filenames.

As a work-around you can transfer a zip file with the long names in it, and then unzip it on the 386.

Reply 13 of 14, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Thanks! Supporting DOS 2.0 would have been too tricky, anyway, I suppose, since it supported the question mark as a wildcard or joker and Unix style separators, too.
MS-DOS 2.10 already lost some of these features again, afaik. It's much more like the DOS 3 we knew and loved.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 14 of 14, by mbbrutman

User metadata
Rank Member
Rank
Member

Making a long story short, I eventually did get traces from routers that honored the HOSTNAME request but did not send it back to the client as a DHCP option. I have a work-around coded in a test version of the DHCP client. You can download it from https://brutman.com/mTCP/download/dhcp-2022-10-04.zip .

This version implements HOSTNAME_ASSIGNED. HOSTNAME is back to being read-only again. This work-around doesn't solve the problem in the DHCP servers, but at least it stops the nuisance problem of having the HOSTNAME line deleted in the configuration file.