Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ncrlnk!ncrwic!iss!mregeste
From: mregeste@iss.Wichita.NCR.COM (Mark Regester)
Newsgroups: ncr.sys.pcdos,ncr.communications,comp.sys.ibm.pc
Subject: Procomm "hangs" on <Esc>[
Message-ID: <147@iss.Wichita.NCR.COM>
Date: 13 Jul 89 15:44:42 GMT
Distribution: na
Organization: NCR Corporation, Wichita, Kansas
Lines: 39


I am having a problem with the new version of Procomm, 2.4.3.  I am using 
the vt-100 emulation.  If Procomm is sent <Esc>[, that is two characters, 
it will appear to "hang" the system.  If more than those two characters 
are sent, Procomm will continue working.  It appears that Procomm has 
received two characters and thinks, "that is a special sequence, I need 
to receive a few more characters before I know what to do,  I will wait 
until that happens". 

I have created a test to demonstrate it on our Un*x system, using a 
"c" program and the "sleep" command.

/* hangprcm.c */

main()
{
    printf("\033[");
}

Run above "c" program with the following command:

      hangprcm;sleep 30

When the "c" program sends the <Esc>[, Procomm will stop processing 
keyboard input.  When the sleep program returns, Procomm will process the 
keyboard input.  Unfortunately, we have a situation where Procomm is 
only being sent the <Esc>[, and no other characters.  At this point, the 
only thing we can do to exit Procomm is to reboot the pc.

Are there any patches to, or a later version of Procomm, available to deal
with this situation.  

P.S.: This situation does not occur using Procomm 2.4.2.

-- 
Mark Regester Information Systems & Services, NCR E&M Wichita
 NCR:654-8340 <M.Regester@Wichita.NCR.COM>
(316)636-8340 <{ece-csc,hubcap,gould,rtech}!ncrcae!ncrwic!m.regester>
              <{sdcsvax,cbatt,dcdwest,nosc.ARPA,ihnp4}!ncr-sd!ncrwic!m.regester>