Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!yale!bunker!wtm
From: rbarth@tumtum.cs.umd.edu (Dick Barth)
Newsgroups: misc.handicap
Subject: Re: TDD bulletin boards?
Message-ID: <14620@bunker.UUCP>
Date: 3 Oct 90 01:33:35 GMT
Sender: wtm@bunker.UUCP
Reply-To: rbarth@tumtum.cs.umd.edu (Dick Barth)
Distribution: misc
Lines: 58
Approved: wtm@bunker.UUCP
Fidonet: Silent Talk Conference

Index Number: 10787

 In Digest #1529, Ann Stalnaker writes:

    Thanks for providing this TDD listing for us, Doug.  However, I can't
    see where many TDD users would call LD since they are only 300 bps.
    I remember when I first called the HEX BBS when I got my first TDD
    and my phone bill was a bit high... Also, it's a bit hard to keep
    up unless one has a 24-26 line monitor instead of a 1 line display
    screen, even though a printer may be in use, it's still hard to
    keep up

 Actually, it's worse than that. TDDs operate at 45.5 baud, not 300. Those 
 that run at 300 are actually using ASCII mode and are emulating a computer
 terminal. Most TDDs, particularly the older and less expensive models, can't
 do that. It's true that many phone companies give TDD users a discount on
 long distance calls, but it's still painfully slow and can get expensive
 even with the discount.

    I would love to see more software TDD compatible (hint hint hint).
    (grin)  It would be nice if TDD users could call the local BBS's
    in their area and join us in some of the echoes

 It's not just software, Ann. A TDD (as opposed to an ASCII machine) 
 does not use a standard ASCII modem. It needs a special TDD modem of
 where some are available comercially. They can also be home-brewed by
 those who are technically inclined; the HEX ran for years on a modified
 Bell-103 type of ASCII modem. The TDD modems on the market won't handle
 ASCII at rates above 300, so if you want to handle both TDD and a normal
 (i.e. 1200/2400/whatever to support downloading) you need two phone lines.
 HEX has that, but a lot of boards don't.

    I don't mean to sound negative but so many of those with hearing
    impairments have watched my BBS and they've complained about the
    speed being too fast for them to keep up with.  I've tried to explain
    that once one gets used to a BBS, they learn to read FAST!!!

 Reading fast (and 300 isn't really that fast for most people with normal
 vision - it's only 300 words per minute) isn't difficult with a CRT-type
 screen. Using a standard 24x80 many people can read 1200 baud with no trouble-
 that's only 1200 wpm. The problem of reading a one=line display at 300 baud
 is compounded by the fact that some TDD makers bollix up the design of their
 equipment. One well-known brand (which shall remain nameless) mis-translates
 an ASCII null into a backspace character. If your BBS sends them a null (as
 is often required for slow, pechanical printers) the TDD-as-ASCII erases the
 last few characters on the line before you can read them. Note that in Baudot
 code (which is what TDDs use, not ASCII) a null is correctly translated as a
 backspace in a TDD. This is standard, because the Baudot code doesn't have a 
 real backspace. That should obviously not be done in ASCII mode though.

    Comments from anyone else????

 You got 'em.

-----------------------------
Richard Barth, W3HWN,  rbarth@tumtum.cs.umd.edu
Handicapped Educational Exchange... (301) 593-7033 (TDD & 300 baud ASCII)
                                    (301) 593-7357 (300/1200 baud, 8N1)