Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!yale!eagle.wesleyan.edu!jtreworgy
From: jtreworgy@eagle.wesleyan.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Handshake gripes (was Re: Does ARP have problems?
Message-ID: <1991Mar17.174213.40358@eagle.wesleyan.edu>
Date: 17 Mar 91 22:42:12 GMT
References: <910317.154305.CST.C506634@umcvmb.missouri.edu>
Organization: Wesleyan University
Lines: 22

In article <910317.154305.CST.C506634@umcvmb.missouri.edu>, C506634@UMCVMB.MISSOURI.EDU (Eric Edwards) writes:
> In Message-ID: <1991Mar17.014544.40347@eagle.wesleyan.edu>
>           jtreworgy@eagle.wesleyan.edu said:
>>(I just don't use the phone book to avoid that one) is that random input (i.e.
>>someone picks up the phone while modeming, or random line noise) can often
>>cause a crash!!! This is not good. In my situation it crashes often enough to
> 
> Did the program actually crash or did the keyboard just seem to go dead?
> Like any good vt220 many of Handshake's settings can be changed with escape
> sequences.  For example, if you log into a VMS system in vt100 or vt102 mode
> the host will interogate the terminal, discover that it's really a vt220 and
> tell handshake to switch to vt220 mode!  The problem is, sometimes line noise
> can duplicate these sequences and put ther terminal in a very strange state.
> The standard solution from 2.12 is to toggle to vt52 and back.  (I don't
> remember if reset terminal works or not)

I've had that happen and have done that... but what I mean is a real lockup,
where the menus don't pop down anymore so I can't even try to reset the
terminal.
-- 
James A. Treworgy    -- No quote here for insurance reasons --
jtreworgy@eagle.wesleyan.edu         jtreworgy@WESLEYAN.BITNET