DAVISM@kcgl1.eng.ohio-state.edu (Michael T. Davis) (06/26/89)
I recently accidentally discovered the code sequence to change the emulation mode on a LINK MC5 terminal running Version 2.01 ROM from native (Wyse 60) mode to VT320-7 mode; it's <ESC>~>. Has anyone discovered the code to change from Wyse 60 mode to VT320-8 mode? The following is addressed to David Ehlert at Link Technologies; feel free to hit N now. David, I would have sent this by mail, but I lost your address. I discovered the "missing spaces" problem was due to strange settings in the Tab Setup screen of Setup Mode. All is well now, as far as that goes. I did happen by another problem, though, which I believe could be traced to the ROM. When I'm in VT320-7 or VT320-8 mode, and the terminal receives the appropriate code to put a line in reverse video, the line is only in reverse video for as long as the line is being transmitted from the host. Once the cursor advances to the next line, the video attribute of the reverse video line reverts to normal video. A couple more points/suggestions... If the time field is set in the status line, should the running time be preserved across powering the terminal off/on? If not, it would be nice if it did, maybe in a future upgrade of the ROM and/or circuitry. The same is true of the Calendar in the Toolkit; once the month and year have been set, it would be preferable for the terminal to keep track of this data. Of course, this would mean that there would have to be a method of setting the current day within the month. Ideally, this would be accomplished via an escape sequence (besides setting these from the Toolkit) similar to that for setting the date field from Wyse 60 mode (<ESC>c8hhmm; per- haps setting date might be accomplished via <ESC>c9mmddyy). Then there might also be an option to display the current date in the status line. Since <ESC>FmessageCR is the command to set the status message, you might specify that if message is null (e.g. <ESC>FCR) that the date is loaded in the status message. This implies, then, that the terminal would have to maintain the status message across midnight; that is, once the date changes, if the date is being displayed in the status line, the terminal would have to update it. I realize these suggestions may be difficult and/or impossible to im- plement; I'm only stating my preferences. Mike ________________________________________________________________________ | THE InterNet address> davism@kcgl1.eng.ohio-state.edu | | CompuServe> 73667,541 | |------------------------------------------------------------------------| | These_Thoughts := My_Own | |************************************************************************| | "Daddy, Daddy!! Why's Mommy running across the field?" | | "Shut up Son, and reload." | ------------------------------------------------------------------------