Re: remote access
|
James Homuth
Understood. I’ve made NVDA crash in the weirdest ways before, and doing what I do will probably do it again, so was thinking corner cases. It’s also why I don’t use Tandem—if JAWS goes sideways, I’m pooched until I’m local to the machine.
From: main@jfw.groups.io <main@jfw.groups.io> On Behalf Of Nermin via Groups.Io
Sent: April-07-19 6:12 PM To: main@jfw.groups.io Subject: Re: remote access
Hi,
honestly, NVDA never ever quit on me on the remote device. If I had to restart the machine for whatever reason, NVDA always restarted itself and NVDA REmote along with it.
Regards, Nermin
From: James Homuth Sent: Monday, April 8, 2019 12:00 AM Subject: Re: remote access
That’s because JAWS Tandem, like NVDA Remote, relies on the screenreader to be up and stable to work. If JAWS or NVDA crashes, good luck. That’s why I was kind of hoping for Teamviewer. I don’t care which screenreader I end up using, honestly. But the ability to restart it when it inevitably falls over without needing to be in front of the machine would be helpful.
From: main@jfw.groups.io <main@jfw.groups.io> On Behalf Of Nermin via Groups.Io
Hi,
I did use TeamViewer now and then, with JAWS being installed on all machines. I remember that I had to do quite a bit of key pass-throughs to control some of the remote JAWS’ features. Your best bet is to install NVDA on both machines, have it start up on the machine you want to control, and install NVDA Remote on both. Works very well, and it will even come up when doing updates and restarting the remote machine or when your connection is bad now and then. JAWS Tandem has the disadvantage of not reconnecting or losing connection when JAWS restarts for some reason or other.
Regards, Nermin |
|
|