RE: Windows Accessible Remote Access?
- From: "Jim Schulz" <jim.schulz@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sat, 8 Jan 2011 12:47:38 -0600
No, I wasn't sure, and I am very pleased to learn I was wrong! Thanks for
the link.
Jim
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Client Services
Sent: Friday, January 07, 2011 5:35 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Windows Accessible Remote Access?
Hi-
Are you sure remote desktop does not work on amazon ec2 instances.
I thought I saw something on blind cool tech about this very topic.
I have not done it myself but I believe remote desk top uses your sound card
and not the server.
Here is a pod cast about using virtual servers and jaws.
DO a search for Virtual Servers
http://www.blindcooltech.com/
Here is what it says:
Virtual Servers Accessible
7/21/2010 Chris Nestrud
shows how to set up a remote Windows Server 2008 on Amazon's Elastic Cloud 2
and use JAWS or even NVDA or System Access to access it.
39.9 MB
H.R. Soltani
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Schulz
Sent: Friday, January 07, 2011 12:07 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Windows Accessible Remote Access?
A few notes from my struggles with obtaining remote access...
1. As far as I know, JAWS and probably WE require a sound card to be
installed on the remote machine, and given that the remote machine is
often some kind of server, sound is not always enabled. I do some work
with amazon ec2 instances, and I don't believe there is any way to
enable sound on one of those guys. So, be sure this won't be an issue
for you before spending any money.
2. I have been able to do a reasonable amount of work using
Microsoft's powershell which is just a command line shell that
supports remote sessions. It's definitley not as useful as being able
to drive the GUI, but a lot of things can be done these days with
command line tools if you can figure out how!
3. ssh is another command line option but I've never found a client
tha'ts very friendly to my sscreen reader (JAWS), and it requires the
installation of a server side component that you may or may not be
able to accomplish. Powershell has to be enabled as well (and even
installed on older windows versions), but because it's a MS tool that
may be more palatable to the IT police.
Good luck!
Jim
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of chris hallsworth
Sent: Friday, January 07, 2011 2:54 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Windows Accessible Remote Access?
Hi all.
With Window-Eyes, you install the software on both sides. On the server
you configure Window-Eyes to install the video support for RDP (only
required for Windows 2000 Server and Windows XP Professional and Windows
2003; Windows Vista and later uses Mirror Driver technology). On the
client configure Window-Eyes to enable Microsoft RDP virtual channel
support. Back on the server, select Microsoft (RDP) virtual synthesizer
and on the client use whatever synthesizer. With this configuration you
should hear the local copy of Window-Eyes speaking the output of the
remote machine.
As for NVDA, currently there is no direct RDP support other than to
stream the audio back to the client, however research has begun into
finding a solution similar to what the other screen readers use.
Take care.
Chris Hallsworth
You can contact me at the following channels:
E-mail and Facebook: challsworth2@xxxxxxx
MSN: ch9675@xxxxxxxxxxx
Skype: chrishallsworth7266
Twitter: http://twitter.com/christopherh40
On 07/01/2011 08:44, Kerneels Roos wrote:
> Thanks for that Chris. With Windows-Eyes, is it a zero-install on the
> remote machine, as in, can you Terminal Service to any machine and it
> just works? or does it require some kind of remote installation? It's
> very impressive if this can work -- I thought it's only images that is
> sent via the RDP protocol. I suppose NVDA doesn't support RDP access at
> all? Since work on the remote server tends to be much less than on one's
> local machine you don't need (in many cases I suppose) the full power of
> JAWS or WE,but just something to get by with.
> Perhaps another zero cost solution would be to run the NVDA portable
> version on the remote box and then listen to the audio stream via the
> RDP client?
> Wow, what about this. Have the remote NVDA send data through to a local
> NVDA which will then voice it locally? Would work much better since you
> don't lug an audio stream around cyberspace but just a stream of text?
> So many possibilities with computers....
>
> On 1/7/2011 9:32 AM, chris hallsworth wrote:
>> Hi all.
>> For JAWS, you need JAWS Professional, plus the Terminal Services
>> option enabled on your license, which is an additional $200 on top of
>> your JAWS Professional purchase. For Window-Eyes, Terminal Services
>> access is completely free, even in the demonstration copy,. I also
>> believe Dolphin's line of products support Terminal Services. I also
>> know of Cobra supporting it, but as yet haven't got it to work.
>> Take care.
>>
>>
>> Chris Hallsworth
>> You can contact me at the following channels:
>> E-mail and Facebook: challsworth2@xxxxxxx
>> MSN: ch9675@xxxxxxxxxxx
>> Skype: chrishallsworth7266
>> Twitter: http://twitter.com/christopherh40
>>
>> On 07/01/2011 07:15, Kerneels Roos wrote:
>>> Hi list,
>>> Currently, what would be the best way to obtain speech and Braille
>>> output when accessing a remote server via the standard graphical remote
>>> terminal clients such as Terminal Services, Remote Desktop Sharing, VNC
>>> and others?
>>> I'm investigating potential work that would require this type of remote
>>> access, and last time I had to do this kind of thing I was able to only
>>> use ZoomText -- now I need speech.
>>> Any advice would be much appreciated.
>>> Kerneels
>>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
