Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!munnari.oz.au!csc!myb100
From: myb100@csc.anu.oz
Newsgroups: comp.sys.amiga
Subject: XPRKermit problems with VLT4.824...:-(
Message-ID: <2700.26d6fea8@csc.anu.oz>
Date: 25 Aug 90 22:41:43 GMT
Organization: Computer Services, Australian National University
Lines: 46


G'day y'all

	I've got a small problem with the new VLT (4.824) and it's use of
XPRKermit. After installing everything per instructions, everything appeared
to work fine, until I tried to transfer a file (binary/text) from our 
mainframes. From Unix boxes there appeared to be no problem , but from the 
VAX/VMS...:

   At the end of a transfer, I get a double-beep, and the XPRK. window is still
up. So far, so normal. I then hit right-Amiga-Y to send the Kermit bye. As soon
as I touch the right Amiga key the kermit window goes away, but comes back
after I hit the Y-key. The VAX says 'Ok, connection closed' and any other key
thereafter will get rid of the kermit window. I then find my terminal in some
strange non-communicative never-never land :-( It swallows all my control
characters, like ^Y, ^C (break/cancel) ^T (show time) ^X (clear buffer) ^P
(swap sessions on our terminal server) etc. . Mostly they tend to behave like a
<return> i.e. they send a <cr> to the VAX. Also, my input is no longer echoed.
Typing 'set term/echo' brings it back.. But the cursor arrow keys no longer
appear to do the right thing. Up/down will recall commands, but left/right are
totally ignored - no line editing. The 'del' key now functions like a return
key as well, while the '<-' key works like a nondestructive backspace. 

To put it simply..: 'HELP !!! What am I doing wrong ???' Have I set up
kermit incorrectly (how??) Is there a bug in XPRKermit somewhere ? (doubt it).

It appears that the problem lies in how the VAX sees my terminal - some 
commands (typed in blindly) do reset some of the problems (like the echo)
but not all (like characters swallowed). Logging off and back in
resets everything back to normal. Swapping to another session
on the terminal server gets me to another VAX and/or UNIX box - no problems 
there....Oh, while I think of it - there is a problem using kermit on the 
Unix box: quiting kermit sends a ^D which is a logout.....

What is kermit sending to the mainframe when I ain't looking ?????

**ANY** help greatly appreciated ! 

===============================================================================
 Markus Buchhorn                                           ///  | This space
 Mt Stromlo and Siding Spring Observatories, Canberra     ///   | 
 PMB Weston Ck. P.O. A.C.T. 2611, Australia           \\\///    | intentionally
 markus@mso.anu.oz.au  -or-  nssdca::psi%mssso::markus \XX/     | left blank
-------------------------------------------------------------------------------
 Phone donations: AUS-6-249-0280 Flames: alt.dev.null  Disclaimer: standard
===============================================================================