PCjr Telnet Server Test

Jeff, Dave, Alexandre, Gordon and G?ran (and the others who have telneted in.) Thanks! I saw some messages last night on my session, but they must have come in past my bed time. :-) The sysop page is just a small beep - in the future the code will figure out it is on a PCjr and do something more elaborate, like take advantage of the 3 voice sound or the speech adapter sidecar. Totally superfluous though. I haven't looked at the logs yet because they are on the machine being tested, but so far things look good. In the last twelve hours: Highest number of concurrent sessions: 4 Total sessions: 49 Tcp Pkts Sent 22317 Rcvd 19353 Retrans 34 Seq/Ack errs 364 Dropped 0 (due to lack of TCP buffers) Pkt stats: Incoming pkts: 19969 Dropped: 0 (due to lack of pkt buffers) Sent: 22390 The last time I did this test I didn't have telnet option negotiation and I wasn't echoing characters. This time around the number of packets is significantly higher, which is great for testing. The machine running the test can be seen here: http://brutman.com/PCjr_WD_small.jpg That's not the network card it is running on at the moment, but I've used it in previous tests. Right now it's running on a parallel port adapter which gives me about half the throughput of the big Western Digital card. (I don't like the big card hanging out exposed like that for an extended test.) The machine is fairly vanilla. 640K, Nec V20 CPU, and two parallel ports upgraded to bi-directional. The .EXE file for the code it is running is only around 70KB in size. Total RAM required is probably less than what I used on the IRC client, so it should run in a 256K machine. For a telnet BBS (which is what it will be one day) a 512K or 640K machine will be plenty. Nobody has alerted me to bad behavior yet and the machine is not on fire, so if you want to pay a visit again to see the packet counts go up, try another telnet client, or try to break it please feel free ... The address again is: 97.86.233.68 Mike