I used Terminals for the past couple weeks.  Not bad, but seems sorta
buggy and the minor issues I ran into annoyed me enough to stop using
it.

I've been using regular-comes with windows RDP client (mstsc.exe).  I
set up the client to the settings I want (screen size, colors, etc)
then put in a server, save it to an .rdp file.  Then I put the server
name as a "Magic Word" in Bayden SlickRun
(http://www.bayden.com/slickrun/) and point it to the .rdp file.  So
all I do is hit a key combo (Alt-Q for me), type the server name, and
I'm in.  For telnet/ssh, Putty all the way :)

Not as elegant a solution as Terminals, but really fast and handy.

Seth

On Thu, Sep 24, 2009 at 9:13 AM, Joseph Heaton <[email protected]> wrote:
> I've been using Terminals for a while, but only for RDP.  I noticed that 
> issue with telnet also.  For telnet I've used TeraTerm for years.  One thing 
> I haven't had a chance to delve into with Terminals:  I had the master 
> password set up so it would automatically log me into servers when I connect. 
>  When I had to change my network password recently, that automatic login 
> stopped, even though I've gone back and reset the master password as well.
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to