This problem was already reported to [EMAIL PROTECTED] two weeks ago, but maybe someone on this list has already found a fix ... When using scp2 to copy a file to a SSH1 host without use of the "-1" cmd line flag, I get the error message: warning: Executing /client/bin/ssh1 for ssh1 compatibility. command-line line 0: Bad configuration option. scp2: warning: child process (ssh2) exited with code 255. OK, I can live with this, but from then on, my terminal is in an unusable state. The VI editor loops with an "At EOF" message, and commands which expect user input - like the "more" pager - behave as they get a CR before I can press any key. Changing the terminal program has no effect. The problem occurs with dtterm, plain xterm, shelltool or cmdtool. "stty sane" doesn't help either. There is also no difference in the "stty -a" output before and after the scp2 invocation. I have no such problems with scp2 on Linux, so the bug is probably Solaris/CDE (2.6/1.2) specific. Any hints? Thanks, -Juergen
