Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request From: hpubvwa!ssc!Tad.Cook@cs.washington.edu Newsgroups: comp.dcom.telecom Subject: Re: How Does One Access a Hearing Impaired TTY Message-ID: <15495@accuvax.nwu.edu> Date: 17 Dec 90 18:04:31 GMT Sender: news@accuvax.nwu.edu Organization: TELECOM Digest Lines: 33 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 10, Issue 889, Message 1 of 10 In article <15419@accuvax.nwu.edu>, hayes!tnixon@uunet.uu.net (Toby Nixon) writes: > Your friend will need to either buy a TDD (they're not all that > expensive; $300-$500), or buy her brother a PC and a modem (which > would be a nice Christmas gift, and open up to him the whole world of > BBSing). I have found that several of my hearing impaired friends have TDDs from Krown and UltraTech which will support 300 bps ASCII. They tell me that many of the newer Terminal Devices for the Deaf have an "ASCII switch." I helped a hearing impaired friend shop for a computer, and I installed a 2400 bps modem and terminal software for her. She found modem communications in the chat mode quite liberating. With a TDD, it is really a simplex operation. At the end of your thought, you type "GA" (for go ahead), and the other party starts typing. Then when they are through, they type GA and you type. In chat mode with the computer, the screen was divided with the sending end displayed on the bottom, and the receiving end on the top. Not only that, but you get a full character set, rather than Baudot code with caps only. We could both type at the same time, and we soon found ourselves having more of a "normal" conversation ... interrupting each other and everything. Tad Cook Seattle, WA Packet: KT7H @ N7HFZ.WA.USA.NA Phone: 206/527-4089 MCI Mail: 3288544 Telex: 6503288544 MCI UW USENET:...uw-beaver!sumax!amc-gw!ssc!tad or, tad@ssc.UUCP