Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!mcvax!kth!draken!tut!santra!chyde!ts
From: ts@chyde.uwasa.fi (Timo Salmi LASK)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm 2.4.2
Summary: config.sys break=off
Message-ID: <483@chyde.uwasa.fi>
Date: 30 Apr 89 07:34:53 GMT
References: <2769@garth.UUCP>
Reply-To: ts@chyde.uwasa.fi (Timo Salmi LASK)
Organization: University of Vaasa, Finland
Lines: 19

In article <2769@garth.UUCP> dbarnes@garth.UUCP (Dave Barnes) writes:
>Got a question about Procomm 2.4.2.  When I use it as a vt100 terminal
>here at work, it will get permanently trashed (stack overflow error) 
>if you hit the "Ctrl" and "Break" keys at the same time.  That's the
>break sequence with SmarTerm 220, which most everybody uses here, and 
>both I and another well-intentioned person have accidentally trashed 
>Procomm trying to unfreeze my system.  Yeah, I know the obvious solution 
>is to make sure I and others don't hit those keys, but is there a 
>more positive way to fix this, like reconfiguring the break key?

Here is the first crude solution that comes to mind even if I have
not tested whether it really works in your problem.  (I do not see
why it should not.) Put the following command in your config.sys
file: break=off

...................................................................
Prof. Timo Salmi
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: ts@chyde.uwasa.fi Funet: vakk::salmi Bitnet: salmi@finfun