Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!rutgers!cmcl2!yale!eagle!flinton From: flinton@eagle.wesleyan.edu Newsgroups: comp.misc Subject: Message-ID: <4885@eagle.wesleyan.edu> Date: 13 Dec 89 17:00:09 GMT References: <317@usna.MIL> Followup-To: comp.sys.ibm.pc Lines: 23 In article <317@usna.MIL>, baldwin@usna.MIL (J.D. Baldwin) : > ... "What is with this character set?" ... everything I type > (or is typed back to me) is in "garbage" characters--the character set seems > to have been mapped to the upper half of the IBM extended character set. > > In any case, I got several answers ...[among them:] ... echo "^V^O" I've used a similar ploy on the VT-220 and VT-320 terminals Wesleyan uses w/ its VAX -- only I enter Set-Up, change On-Line to Local, exit Set-Up, press -O, re-enter Set-Up, change back to On-Line, re-exit Set-Up, done (and it's fewer keystrokes than the DCL-ish monstrosity WRITE SYS$OUT "-V-O" one must use where echo "^V^O" should do. Same explanation -- something sent the terminal a -N to select the "wrong" 128-character font-set, and the terminal needs to see a -O to get back to normal. Actually, I'm in the habit of selecting Clear Comm, too, while I'm in Set-Up, because, as often as not, the terminal has also seen a -S (or other keyboard-locking escape sequence) and is therefore locked up -- Clear Comm seems to fix that. -- Fred