When I began my great adventure into the world of the Slug and the deep abyss of Linux I had no idea what it mean to telnet… I do now..
When I started I downloaded and used putty to telnet. It worked fine.
Somewhere along the way I was made to realize that a “run” and “cmd” script in Windows brought me to the command prompt (what I remembered as a “dos” screen) and the same telnet capacity as using putty.
Dumb question.. whats the difference and why use putty..
The telnet client that ships with windows is basic but works ok. Putty is a more feature rich client e.g. it supports colouring / coloring of text. It also can also support other types of connection e.g. ssh.
I did notice how impossible it was to cut/paste using windows.
Dave
And the reason that it specified by name in the wiki is that it doesn’t do proper vt52 emulation, so when you use a full-screen editor like nano, the screen gets corrupted on windows, whereas it works fine in putty.
That’s the reason it’s specified in the wiki that way.
But for most stuff, like diddling around on the console, windows telnet works fine.
I did notice how impossible it was to cut/paste using windows.
Dave
But for most stuff, like diddling around on the console, windows telnet works fine.
— Ron
And in XP etc, running Telnet in a command window, you can copy and paste using the mouse to a limited extent – right-click to get menu, select Mark with left click, left click and drag to highlight, then control-C to copy, then right click to get the menu and then select Paste with left click to drop the copied text in at the cursor.
Cheers,
Les.
Author
Posts
Viewing 6 posts - 1 through 6 (of 6 total)
The forum ‘General Discussion’ is closed to new topics and replies.