Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!unido!tub!tmpmbx!csch From: csch@tmpmbx.UUCP (Clemens Schrimpe) Newsgroups: comp.unix.wizards Subject: Re: uucp problem -- please help Keywords: uucp Message-ID: <1142@tmpmbx.UUCP> Date: 20 Aug 88 00:19:50 GMT References: <208@pwa-b.UUCP> Reply-To: csch@tmpmbx.UUCP (Clemens Schrimpe) Organization: netmbx GbR, Berlin Lines: 34 The problem seems to be in those rlogin-connections. As I could determine from your debug-info your uucico tries to utilize the so called 'g' protocol for transmission. This is quite right for non-MNP modemconnections but it also requires a FULL (!!!) 8-bit transparent connection which 'rlogin' wouldn't give you, since at least '~' has a special meaning to it. There are two possible solutions of that problem: a) Try to make your uucico use the 'f' protocol - it will only use 7 bits and avoid special characters like the most characters of col. 0/1 of the ascii-chart and DEL. Although you should set the ESCAPE character of either telnet or rlogin to some control-char instead of '~' ! The problem with this is, that if you have a very noisy telephone-line you'll get more problems, since the 'f' protocol relies on a flow-controlled (that's where the name comes from) almost error-free connection. b) Write a simple 8-bit transparent communications-program, which connects you to the 'uucp' port of the receiving machine. This programm could terminate if one side simply hangs up. (uucp = port 540/tcp [uucpd] - Berkeley Unix should support that) regards, Clemens Schrimpe, netmbx Berlin -- UUCP: csch@tmpmbx.UUCP {pyramid,unido,altger}!tmpmbx!csch BITNET: csch@db0tui6.BITNET csch@tub.BITNET PHONE: +49-30-332 40 15 TELEX: (066)+186672 net d PSI: PSI%026245300043106::CSCH X.25: 026245300043106 login: chat Password: talkmaster