Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!WATSUN.CC.COLUMBIA.EDU!freeman From: freeman@WATSUN.CC.COLUMBIA.EDU (Mike Freeman) Newsgroups: comp.os.cpm Subject: QTERM/MTS Kermit Message-ID: Date: 17 Jun 91 16:30:55 GMT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 15 In article <9107558@ub.cc.umich.edu>, Steve Graham writes: >I am still not able to get QTERM's KERMIT to talk to my local mainframe's >(MTS) kermit. Any ideas? Setting parity, file type, packet length >don't seem to do it. MTS sometimes give "unexpected packet type" messages, >or spits out a "d:" at the bottom right of the screen, otherwise nothing >but timeout errors. And they are offset on the screen by one line from >their labels, due to that at the bottom of the screen. I corresponded with Frank da Cruz (One of Columbia's Kermit gurus) regarding this problem and he says that it's likely the problem is with MTS-Kermit. Someone once told him that MTS-Kermit doesn't understand I-packets and goes crazy when it receives one. Steve Graham may be SOL on this one because Mr. da Cruz says nobody is supporting MTS-Kermit anymore. -- Mike K7UIJ --