KRT bug list for RSTS/E X04.64-51 -- 17Sep96 01) Odd address trap after too many NAKs? (See item 2) ++ Hasn't happened lately. May be fixed as a side effect of fixing ++ other things. Needs investigation. 02) Max receive size for binary files: 1200 < max-packet < 1500 *** Bump XKSIZE up to 2000 ??? Now works up to 1200. 1500 broke after a long transmit. 2000 broke ??? immediately 03) CTRL/Z acts WEIRD in command mode. OK made KBREAD return cmd$ex or cmd$ab for ctrl/z or ctrl/c 04) Help seems to have some memory of the last openned file, checks it first and declares it wrong version before finding the real help file. OK check for errors from fparse in KRTSER, KRTSHO, KRTXMO, and KRTHLP. OK Also, KRTUTL doesn't check, but we don't use this on RSTS. 05) Only I&D-space version so far. 06) Hangup goes into infinite loop. ** set up correct clock tick rate 07) No flow control in connect mode OK Use mode 33. 08) does link or console use private delims to reduce overhead? OK Fixed in Edit 51 09) XMODEM foo gives wrong error message OK boundary problem in displaying internal error messages - fixed 10) Need a set nomodem or set modem none command for null-modem links ("SET MODEM NONE" is the C-Kermit equivalent.) 11) Attributes, creation date, protection code don't seem to get written to output file on RSTS-RSTS transfers. ++ Now getting attributes through. Creation date and protection code ++ still not working. ++ May be fixed. Creation date appears to have NEVER worked. 12) Creation date, protection code not written to output file for anything-to-RSTS transfers 13) Zap attributes on output file if original file was RSTS and had no attributes, or if output file is text or block-mode binary and user doesn't want attributes. 14) In server mode - seems to switch in & out of binary mode. This is both expensive and sometimes lets control-characters (such as LAT FORWARD commands) get excuted instead of passed through. OK Fixed in Edit 51 15) Dialing problems. Is this the same timing problem as hangup? 16) Does it always correctly know if a "set line" has occured, and disallow appropriate things if not? 17) Set term vt gives "ER$AOP - allocation options error" OK ER$AOP was both an RMS error and an internal error ("ambiguous option"). OK redefined internal error code as ER$AMO to fix it. 18) Possible symptom of problem 10: saw a "AT Z" on the remote terminal after connecting after doing a "set term vt". Maybe artifact of an an attempt to reset the (null) modem. 19) Output file should be pre-extended if length is received. 20) Many attributes (creation date, protection code, length, internal info) were not being transmitted or received correctly. OK Fixed. 21) Support labelled file type. For RSTS-RSTS transfers, send attributes, RTS, caching options, dates, clustersize, full protection code, ... 22) Send abort appears not to close the input file. OK This was a side effect of item 23. 23) NAK on 1st packet causes packet size reduction, but it doesn't resend from the beginning of file, or close the input file when the transmission completes. OK Fixed. May also be a problem with KRT on RT-11. 24) Is it failing to honor send packet size? OK No, this works correctly. 25) SET TERM VT200 caused terminal to be set to TTY. OK This was a bug in KRT V3.63; fixed 26) Problems with logging of local delete and rename commands. 27) Remote directory to RSTS KRT in server mode hangs if there are no files matching filespec. 28) Remote set file type gives spurious error. 29) STATS has number of charaters/io received after SEND, but not after RECEIVE. Isn't this backwards?