terminal settings with plink
Jo Hesse
when using Putty with ssh from PC (Win2k) to a Linux client we get the
right look of it. By using the following command "plink -ssh
SessionName" we get "?]2;nbint@ulmlx997:~?[34mnbint@ulmlx997:~ >?[0m"
as prompt.
Any suggestions? I used VT100+ as keyboard.
//Jo
Richard E. Silverman
JH> Hi, when using Putty with ssh from PC (Win2k) to a Linux client we
JH> get the right look of it. By using the following command "plink
JH> -ssh SessionName" we get
JH> "?]2;nbint@ulmlx997:~?[34mnbint@ulmlx997:~ >?[0m" as prompt.
JH> Any suggestions?
Yes: read the manual.
http://the.earth.li/~sgtatham/putty/0.53b/puttydoc.txt
...
You should then be able to log in as normal and run a session. The
output sent by the server will be written straight to your command
prompt window, which will most likely not interpret terminal control
codes in the way the server expects it to. So if you run any full-
screen applications, for example, you can expect to see strange
characters appearing in your window. Interactive connections like this
are not the main point of Plink.
...
--
Richard Silverman
sl...@shore.net
Hart Larry
options in Plink?
I did some searching--and looks like someone submitted a bug report to the
Putty/plink folks. They seemed to answer by saying they wouldn't fix it. I
wonder if any of the batch options implied in the manual would fix a terminal
screen?
Otherwise, what other commandline telnet or ssh applications can be run in a
DOS-box with clean terminal screens.
As I said several weeks ago, there is a telnet version which comes up in google
searches, however, there are many key conflicts with my screen-reader.
Thanks so much
Hart
Alan J. Flavell
> Well, Richard-and-All, I'm glad to se maybe a 3rd person ask about terminal
> options in Plink?
> I did some searching--and looks like someone submitted a bug report to the
> Putty/plink folks. They seemed to answer by saying they wouldn't fix it.
As the documentation says, Plink aims to be strictly a command-line
client, nothing more.
With respect, you seem to be hanging bits of what might turn out to be
a reasonable user requirement on the coat tails of an original request
that wasn't. I don't have an answer to your question yet, because I'm
not quite sure I know what _your_ question is, but let's at least
try...
> wonder if any of the batch options implied in the manual would fix a terminal
> screen?
> Otherwise, what other commandline telnet or ssh applications can be run in a
> DOS-box with clean terminal screens.
If I understand you right, you're looking for a screen-based (i.e not
just command-line-based) client that runs in a DOS-box? Presumably
because you have a screen reader that deals with the DOS-box
specifically? Because, after all, putty itself works just great
in its own window (which is what I'm typing into right now)...
In this kind of situation in the past (though I must admit it's been
some years since I played with it), I simply followed the instructions
on an old MS-DOS (version 5) manual regarding the setting up of
AUTOEXEC.BAT and CONFIG.SYS for the ANSI.SYS driver, and I told the
remote system to emulate a terminal type of ANSI, and it just worked.
Now, applying this idea to the components in the putty package: Plink
deliberately plays no part in this - it says it just writes the raw
data to the terminal: so I'm guessing that it might work in a similar
fashion, if the 'terminal' is a DOS window which supports the ANSI
driver conventions. But YMMV, because I haven't tried it, and indeed
it could just be that I've misunderstood your situation (the last
version of Windows on which I actually tried that was Windows 95, and
it must be half a decade back now).
good luck
Hart Larry
but since they don't offer unix shells, I telnet or ssh in to CTS which has had
shells for many years. My useing a shell requires much live interaction. Add
to the mix the fact that as some1 blind, I have a screen-reader. So the
interface-and-how the program writes to my screen are important.
Reason I tried an ssh client is to see if I would find a better interface.
Generally, I am looking at win32 applications which run in a DOS-box in win98.
Thanks again for responding
Hart
Richard E. Silverman
How about OpenSSH/Cygwin?
--
Richard Silverman
sl...@shore.net