info-vax@ucbvax.ARPA (06/27/85)
From: *Hobbit* <AWalker@RUTGERS.ARPA> It seems that interrupt character handling across DECNET has changed wildly under 4.0VMS. If you do SET HOST <wherever>, log in, and then run some program at the remote end, you look fine until you type a ^C, whereupon you get DCL back. Okay, you say, that's what is supposed to happen, so why complain? Well, if I am running Telnet at the far end, ^C is supposed to be transmitted *through* that far end Telnet and be passed on to wherever I am Telnetted to. Instead, REMACP or RTdriver or whatever generates a $FORCEX for the image I am running. Unconditionally. This not only blows my TN connection away but leaves my terminal in strange states, as one might expect. Under 3.x this doesn't happen; the remote AST delivery mechanism functions properly. This FORCEX trash is in direct violation of what a ^C AST is supposed to do. Is there a way around it???? _H* -------
info-vax@ucbvax.ARPA (07/03/85)
From: hadron!jsdy@seismo (Joseph S. D. Yao) In article <8537@ucbvax.ARPA> you write: >From: *Hobbit* <AWalker@RUTGERS.ARPA> > >It seems that interrupt character handling across DECNET has changed >wildly under 4.0VMS. If you do SET HOST <wherever>, log in, and then >run some program at the remote end, you look fine until you type a ^C, >whereupon you get DCL back. ... > >Under 3.x this doesn't happen; the remote AST delivery mechanism functions >properly. This FORCEX trash is in direct violation of what a ^C AST is >supposed to do. Is there a way around it???? Are you sure you have installed your telnet image with the proper privileges? If I remember right, it takes (took?) special file permissions for a program to run and be able to turn off ^C. I wrote a program under VMS, years ago, that could read in cbreak mode but could not ignore ^C's for this very reason. Joe Yao hadron!jsdy@seismo.{ARPA,UUCP}