DOS (PC) FTP server testing needed

Hi, I made some changes in my TCP/IP code to make it behave better when packets are lost and it has to retransmit. The old code used to wait a fixed amount of time before retrying, which was painfully slow on a local connection. The new code is adaptive and should work much better on a wide range of connections. If you'd like to help me test it I have my PCjr running the mTCP FTP server with some old computer pictures, some software, and some text files. (I'll add more during the day to keep it interesting.) You can connect by going to the following address: ftp://96.42.84.69:2021/ That URL should work in most browsers (Firefox, IE and Chrome). Chrome tends to be a bit of a pig and it tries to preload the content that it finds, so if you see it going slowly it is probably due to multiple connections. The poor PCjr is only setup for 9 simultaneous connections. If you use an FTP client anonymous FTP should work fine. Note the non-standard control port - 2021. Which also means that if you are using a real FTP client (and not a browser) you should be using PASSIVE mode. (Port mode with a non-standard control port confuses most firewalls, and they won't pick it up. Most browsers use PASSIVE mode by default.) Uploading is not turned on for this test, but if you are dying to upload contact me and I'll give you the password. Fun facts: - The machine is a PCjr with a jrIDE sidecar, 20GB IDE hard drive, WD8003 ISA Ethernet adapter, NEC V20 CPU, and an IBM PC 5150 keyboard. Yes, this is the same machine that was recently maligned on the list. ;-0 - If you want to see how the TCP/IP code is holding up you can get statistics by using the "SITE STATS" command in a suitable FTP client. - This is a DOS machine - you have to use DOS filenames and paths, except for the directory delimiter - that uses the standard forward slash. (Using the DOS backslash was too difficult for most clients and browsers.) Also, if you use MGET remember that you have to use *.* and not just * for a filespec. Comments and bug reports are welcome. Use good judgement to avoid cluttering up the list too much ... Mike