READ.ME for the latest TELNET code: Description: ------------ This package provides replacement files for TELNET.EXE, TELNETPM.EXE, TELNETD.EXE, TELNETDC.EXE, LOGNIUNX.EXE, TNLOGIN.EXE, TNLS16.DLL, TNLS32.DLL, ANSI.DLL and VT100.DLL. To date, these are the only files in the TELNET component that have had apar fixes made to them in OS/2 WARP SERVER. Installation instructions: -------------------------- You must have the following installed on your system: - OS/2 Warp Server with TCP/IP v310 You should put the TELFILES.EXE file in a temporary subdirectory and enter: TELFILES TELFILES.EXE file contents: -------------------------- READ.ME TELNET.EXE 254464 04-15-97 TELNETPM.EXE 291328 04-15-97 TELNETD.EXE 22416 04-30-97 TELNETDC.EXE 33660 04-02-97 LOGINUNX.EXE 12233 03-21-97 TNLOGIN.EXE 8085 03-21-97 TNLS16.DLL 47104 04-09-97 TNLS32.DLL 86528 04-09-97 ANSI.DLL 70655 07-23-97 VT100.DLL 71199 07-23-97 You should back up the current versions of these files on your system. Then replace the *.EXE files in the TCPIP\BIN directory and the *.DLL files in the MTPN\DLL directory. Apars included in this group of fixes with a brief description: (executables and/or dlls fixed) -------------------------------------------------- IC16297 - From an OS/2 WARP V4, customer telneted to an AIX machine. An executable file with the following content was created: echo "\033¬5i" ls echo "\033¬4i" This redirected control to printer. Control never redirected back to system. IC16793 - When the connected to a host over a dialup connection a message appears in the telnet window that the host screen size is not supported. IC17023 - Server applications (telnetD, RshD, and RexecD) that do not properly handle socket ownership will hang their corresponding clients because of unsuccessful calls to soclose(). This symptom is now occurring because of enhancements to soclose() processing in the latest version of the TCP/IP toolkit. With rshd and rexecd, this problem will only occur when started under inetd. For Telnetd, the problem will occur regardless of how it is started. IC17307 - Start a telnet daemon (i.e. telnetd) on the server. Have a client telnet into the server. Have the client log off the telnet session. Kill the telnet daemon on the server (i.e. ctrl-C). Restart the telnet daemon (same port #) Get message "Bind(): Address already in use." Problem only occurs if you try to restart the daemon on the same port number. IC17956 - Start a telnet daemon (i.e. telnetd) on the server. Have a client telnet into the server. Have the client run another utility/application. Second application will trap because of inadequate stack space. IC18086 - Start a telnet daemon (i.e. telnetd) on the server. Have a client telnet into the server. Have the client press up arrow key for repeat/retrieve function. Retrieve function improperly tabs over on same line.