Very probably would work and here's why. The satogo.com system uses the resources not on the remote system but on the local system since that's where its temporary software gets installed on the local system. So so long as a remote connection can get done whatever resources that are on your system along with satogo.com will be used to service that connection. Rot47: <;F56]52D9:6==@?2GJ]>:=> -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Brent Harding Sent: Thursday, June 18, 2009 19:06 To: programmingblind@xxxxxxxxxxxxx Subject: Re: Using SA to Go for remote desktop access Wow! Would that work on those virtual private systems that have Windows on that you can get hosted these days? I have a feeling it might not because they might not have sound in them. ----- Original Message ----- From: Macarty, Jay {PBSG} <mailto:Jay.Macarty@xxxxxxxx> To: programmingblind@xxxxxxxxxxxxx Sent: Thursday, June 18, 2009 5:13 PM Subject: Using SA to Go for remote desktop access All, Just a little trick I stumbled across recently. I needed to perform some file permission maintenance on a remote machine which didn't have any screen reader software installed. I went to Remote desktop on my workstation and logged into the remote machine. Once connected, I pressed windows+r to get the popup dialog and then entered www.satogo.com and pressed enter. In a few seconds, I had speech prompting me to press alt+r to complete the install. I logged into my SA account (which is optional) and was able to use SA on the remote machine to get the file maintenance done. The response was just a touch sluggish but not bad at all. Just thought I would pass that along. __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind