cloos@batcomputer.tn.cornell.edu (James H. Cloos Jr.) (02/29/88)
This is a warning of a bug I've found in the VersaTerm-Pro terminal emulation package. I'm using a University-owned copy, that appears to be version 2.00. I don't remember if this is the most recent version; so I'm not sure if this bug is documented or even fixed. I do know that *I* haven't seen anything about it on the net. The problem occurs with COMMAND SETs. I usually have the command set set to SHORTCUTS, which allows certain of the program's commands to be performed by typing OPTION-char. Shortcuts defines OPT-Q to QUIT the program. The prob- lem occurs when the remote computer sends non-text ascii characters. The program allows the mac to interpret the keyboard using the conventional routines, traps those defined as OPTION-char for its own use, and sends the conventional ascii characters to the remote computer. Unfortunately, when versaterm receives ascii characters w/ values >127, it interprets these TOO as if they were typed at the keyboard. What this comes down to is that, if you use the shortcuts commands, and the remote computer sends the ascii character whose value corresponds to the mac-ascii character 'oe,' the program QUITS! Depending on how you are connected to the remote computer, this may or may not result in disconnection. Unfortunately, if you are not disconnected, & you re-run the program, as soon as you hit a key or hit the button on the mouse, the program will resume receiving any data the host may still be sending. This could result in an infinite loop. (If this happens & there is no way for you to disconnect from your system while it is (for instance) CATing data (to use the UN*X syntax) or otherwise running a program, the loop can be terminated by running VT-PRO by double-clicking on a commands document other than shortcuts. This way, OPT-Q will not be synonymous to QUIT for session. I'm not too familiar with PROGRAMMING the Macintosh, so I'm not sure if what I'm about to propose can work, but if its possible for a program to differ- entiate between data coming from the modem/printer port vs. data from the keyboard port, then it should be simple to do this, and have VersaTerm only trap option chars comming from the keyboard, & either print or just ignore those comming from the modem/printer port. If I'm just rehashing old news, I appologise, but, as I said earlier I've not seen anything on it, & thought it important enough to post regardless. |==-==--==---==----==-----==------==-------==------==-----==----==---==--==-==| | #include <disclamers.h> | | James H. Cloos, Jr. "I *HATE* quotations" | | cloos@crnlthry.BITNET -Ralph Waldo Emerson | | cloos@batcomputer.tn.cornell.edu.ARPA -(emphasis added) | | {allegra,decvax,ihnp4,vax135}!cornell!batcomputer!cloos | |==-==--==---==----==-----==------==-------==------==-----==----==---==--==-==|