ssh access, was: Re: software speech

Gregory Nowak greg at
Thu Aug 21 14:24:26 EDT 2008

Hash: SHA1

On Thu, Aug 21, 2008 at 03:10:12AM -0700, Tony Baechler wrote:
> The problem is  
> Windows, not the ssh client.

Yes, I'd agree. Specifically, the way I see it, the problem is using a
text interface inside of a GUI interface, with a GUI screen
reader. Ssh access for me at least, was lots better under a dosbox
with the provox screen reader using win98, than it is nowadays in xp,
regardless of if I'm using a ssh client via the cmd.exe xp command
prompt, or using udf8 teratermpro, both via wineyes in my case.

> The problem I run into  
> is that a GUI environment doesn't do well at handling console apps,  
> specifically GUI screen readers don't do well with command prompts or  
> text-based programs such as the Cygwin ssh client, telnet, etc.

I'd definitely second that.

> I  
> wouldn't quite go so far as to say that access from Linux to another  
> Linux system is seemless, but it's a lot better than going through  
> Windows.  I've noticed that the Speakup keyboard echo is slightly less  
> responsive with ssh but I can certainly live with it.

Maybe I should've qualified my previous statements. If you're
interacting with a system at a remote location, what you describe is
indeed the case. However, if you're interacting with another system on
your home LAN, (which I believe is what Tyler is doing), then my
previous statements do stand, ssh access from gnu/linux is indeed
seamless in that case, speakup keyboard echo, and all.


- -- 
web site:
gpg public key:
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: or mail dns-manager at
Version: GnuPG v1.4.9 (GNU/Linux)


More information about the Speakup mailing list