Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

mTCP new release 27/June/2010 - now ported to Open Watcom (Announce)

posted by mbbrutman Homepage, Washington, USA, 01.07.2010, 16:03

On the file transfer, it looks like you didn't specify binary before starting the transfer. So LFs (0x0a) were converted to CR/LFs (0x0a 0x0d) by the server during the transfer. There isn't much I can do about that without doing something ugly like stuffing a 'BIN' command in the command ahead of the transfer first. I'm going to call that one a user error. :-)

I don't know why the server closed the control connection. It's possible that it timed out, and on the first command that you sent the dropped connection was noted. From the statistics at the end I can see no retransmits. I can see an enormous amount of dropped packets though - you are losing more than 10% of the packets into your machine. Are you running something else on that machine in the background? What kind of machine is it? (My PCjr and other older machines don't drop packets like this unless I have turned on full tracing, and they have the slowest hard drives in the universe.)


On the config file comments:

I don't like defaults. It's not harsh to have the person set an environment variable to get to the configuration file. I could go looking for the packet interrupt too, but in the unlikely event that the person has two cards they would need to specify the packet interrupt anyway. Also, any extra code that I spend on initialization is stuck in memory long after it is needed so I prefer to keep the initialization code to a minimum.

Don't have a PCjr? Nobody is perfect. Set your own hostname then! I think it is used for DHCP - none of my other apps use it (yet).


BIN vs. ASCII existed long before I ever touched a keyboard. FTP was designed for data transfer across heterogeneous machines, and the only thing that was agreed upon back then was that nobody knew what a newline meant. Which is why Telnet specifies the 'CF/LF' pair and allows each side to translate as needed. FTP has a much richer command set and file transfer modes than anybody probably implements anymore. BIN vs. ASCII is just a holdover that they all still honor even if the other ones are not implemented.

The server determines the default, not the client. You need to send 'BIN' first. I can add 'IMAGE' as an alias.

---
mTCP - TCP/IP apps for vintage DOS machines!
http://www.brutman.com/mTCP

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22781 Postings in 2123 Threads, 402 registered users (0 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum