Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!oliveb!3comvax!tymix!antares!pnelson
From: pnelson@antares.UUCP (Phil Nelson)
Newsgroups: comp.sources.d
Subject: Re: Remote control of PC via modem
Summary: I backspace all the time
Keywords: AT&T PC6300+ backspace ctty remote
Message-ID: <310@antares.UUCP>
Date: 16 Dec 88 03:02:47 GMT
References: <4652@phoenix.Princeton.EDU> <104@unibase.UUCP> <190@serene.UUCP> <13246@ncoast.UUCP> <208@serene.UUCP>
Reply-To: pnelson@antares.UUCP (Phil Nelson)
Organization: Tymnet QSATS, San Jose CA
Lines: 28

In article <208@serene.UUCP> rfarris@serene.cts.com (Rick Farris) writes:

>Had you hit a wrong key while you were calling up debug, and for
>instance typed "debuh", and then tried to correct it by typing
>backspace, your computer (yes, even your Toshiba laptop), would have
>locked.  For reasons I won't go into, I've had occasion to use ctty
>on a number of computers, and I've learned to be *very* careful.  For
>instance, in the example I just posited, I would just hit the return
>key, and let the computer tell me it couldn't find the command, and
>then I would re-enter the command.


 Uh, the way I read what he said, he did something very like your example
without problems. I can speak for the AT&T PC 6300+, which does have problems
with flow control (as in, I havn't been able to get it to work), but allows
use of the backspace with no problem. Just don't try it with CED or some such,
things can get very complicated. I use CTTY on the AT&T at 9600 baud often.
File transfers are difficult, but I can run DOS utility functions and some
other programs (Zoo, for one) without difficulty.


>Rick Farris   RF Engineering  POB M  Del Mar, CA  92014   voice (619) 259-6793
>rfarris@serene.cts.com     ...!uunet!serene!rfarris       serene.UUCP 259-7757


-- 
Phil Nelson at (but not speaking for)
Tymnet, McDonnell Douglas Network Systems Company      POTS:408-922-7508
UUCP:{ames|pyramid}oliveb!tymix!antares!pnelson   LRV: Component Station