Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!cbatt!cbosgd!ihnp4!inuxc!pur-ee!pucc-j!u14 From: u14@pucc-j (Dan Severance) Newsgroups: net.micro.pc Subject: Re: Procomm 2.3 Message-ID: <1557@pucc-j> Date: Mon, 14-Jul-86 14:31:32 EDT Article-I.D.: pucc-j.1557 Posted: Mon Jul 14 14:31:32 1986 Date-Received: Tue, 15-Jul-86 06:12:54 EDT Reply-To: u14@pucc-j.UUCP (Dan Severance) Organization: Purdue University Computing Center Lines: 48 This is how my Procomm 2.3 Kermit setup looks for text transfers: 1) Control quote char ... 35 (ASCII) 2) Maximum packet size .. 94 3) Pad character ........ 0 (ASCII) 4) Number of pad chars .. 0 5) 8th bit quote char ... 38 (ASCII) 6) 8th-bit quoting ...... ON 7) End of line char ..... 13 (ASCII) 8) File type ............ TEXT { BINARY for binary transfers } 9) Block check type ..... 3 BYTE CRC My C-kermit parameters on UNIX 4.2BSD are : Line: /dev/tty, speed: -1, mode: remote, modem-dialer: direct Parity: even, duplex: full, flow: xon/xoff, handshake: none Protocol Parameters: Send Receive Timeout: 10 10 Padding: 0 0 Pad Character: 0 0 Packet Start: 1 1 Packet End: 13 13 Packet Length: 94 94 Block Check Type: 3, Delay: 5 8th-Bit Prefix: '&' Repeat-Count Prefix: '~' File parameters: File Names: converted Debugging Log: none File Type: text Packet Log: none File Warning: off Session Log: none File Display: on Transaction Log: none Incomplete File Disposition: discard, Init file: .kermrc Improper parity or framing can also cause failures in transfer, I also use the same setup with an IBM3081 with the VM operating system. I hope this helps. The UNIX and VM systems here have 7 data bits and EVEN parity for reference on the above values. The UNIX C-kermit here assumes No parity by default, so I had to change it to EVEN. Dan Severance