Starting NVDA or Narrator from command prompt or power shell?

Jen Bottom

29 Jun 2017 29 Jun '17

5:13 p.m.

Hi everyone, I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run. I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while. This script installs the NVDA package using 'choco'. I don't think it's the latest but better than nothing. However NVDA does not automatically start once the package is installed. Note currently I don't have access to a physical box running Windows that I can test stuff out on. I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback. I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen. Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated. I think it is available on the box I have, but I may play with different Windows boxes in the future. Thanks in advance for any suggestions, Jen!

Show replies by date

Simon Eigeldinger

29 Jun 29 Jun

5:24 p.m.

Hi, Here are the commandline options from the help document: 14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy) Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...

Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

Ben Mustill-Rose

8:23 p.m.

Start NVDA by typing nvda. Start Narrator by typing narrator. On 6/29/17, Simon Eigeldinger wrote:

...

Hi,

Here are the commandline options from the help document:

14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy)

Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...
Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com

--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Ben Mustill-Rose

8:23 p.m.

Start NVDA by typing nvda. Start Narrator by typing narrator. On 6/29/17, Simon Eigeldinger wrote:

...

Hi,

Here are the commandline options from the help document:

14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy)

Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...
Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com

--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Guerra Access Technology Training LLC

8:28 p.m.

Can anyone provide any info or instructions about installing NVDA Remote on my own server and using it in place of NVDAremote.com -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ben Mustill-Rose Sent: Thursday, June 29, 2017 3:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell? Start NVDA by typing nvda. Start Narrator by typing narrator. On 6/29/17, Simon Eigeldinger wrote:

...

Hi,

Here are the commandline options from the help document:

14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy)

Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...
Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com

--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Ratha Moeuy

30 Jun 30 Jun

1:49 a.m.

I belive the latest version of nvda remote has an option to use given machine to act as a server. It is under options. Not sure if that is what it suppose to be for though. Never really did try it. Ratha -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Guerra Access Technology Training LLC Sent: Thursday, June 29, 2017 4:28 PM To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell? Can anyone provide any info or instructions about installing NVDA Remote on my own server and using it in place of NVDAremote.com -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ben Mustill-Rose Sent: Thursday, June 29, 2017 3:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell? Start NVDA by typing nvda. Start Narrator by typing narrator. On 6/29/17, Simon Eigeldinger wrote:

...

Hi,

Here are the commandline options from the help document:

14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy)

Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...
Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com

--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Jen Bottom

10 Jul 10 Jul

4:30 p.m.

I have finally managed to get a Vagrant box provisioned with NVDA and talking. Currently I am using Virtual Box, because for reasons I won't go in to, the VMWare Vagrant plugin is falling short. Also I have found the keyboard is automatically captured when VirtualBox is put in full-screen mode, after the machine is started. If anyone is interested all my Vagrant code is here: https://swarm.workshop.perforce.com/files/guest/jen_bottom/vagrant It's pretty basic and not pretty, but most of it works :D Cheers, Jen. On 6/30/17, Ratha Moeuy wrote:

...

I belive the latest version of nvda remote has an option to use given machine to act as a server. It is under options. Not sure if that is what it suppose to be for though. Never really did try it.

Ratha

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Guerra Access Technology Training LLC Sent: Thursday, June 29, 2017 4:28 PM To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell?

Can anyone provide any info or instructions about installing NVDA Remote on my own server and using it in place of NVDAremote.com

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ben Mustill-Rose Sent: Thursday, June 29, 2017 3:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell?

Start NVDA by typing nvda. Start Narrator by typing narrator.

On 6/29/17, Simon Eigeldinger wrote:

...
Hi,

Here are the commandline options from the help document:

14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy)

Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...
Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com

--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Jen Bottom

4:30 p.m.

...

I belive the latest version of nvda remote has an option to use given machine to act as a server. It is under options. Not sure if that is what it suppose to be for though. Never really did try it.

Ratha

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Guerra Access Technology Training LLC Sent: Thursday, June 29, 2017 4:28 PM To: 'Blind sysadmins list' Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell?

Can anyone provide any info or instructions about installing NVDA Remote on my own server and using it in place of NVDAremote.com

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ben Mustill-Rose Sent: Thursday, June 29, 2017 3:23 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Starting NVDA or Narrator from command prompt or power shell?

Start NVDA by typing nvda. Start Narrator by typing narrator.

On 6/29/17, Simon Eigeldinger wrote:

...
Hi,

Here are the commandline options from the help document:

14. Advanced Topics 14.1. Command Line Options NVDA can accept one or more additional options when it starts which alter its behavior. You can pass as many options as you need. These options can be passed when starting from a shortcut (in the shortcut properties), from the Run dialog (Start Menu -> Run or Windows+r) or from a Windows command console. Options should be separated from the name of NVDA's executable file and from other options by spaces. For example, the Desktop shortcut that NVDA creates during installation has the -r option, which tells NVDA to close the currently running copy before starting the new one. Another useful option is --disable-addons, which tells NVDA to suspend all running add-ons. This allows you to determine whether a problem is caused by an add-on and to recover from serious problems caused by add-ons. As an example, you can exit the currently running copy of NVDA by entering the following in the Run dialog: nvda -q Some of the command line options have a short and a long version, while some of them have only a long version. For those which have a short version, you can combine them like this: nvda -rm This will exit the currently running copy of NVDA and will start a new copy with startup sounds disabled, etc. nvda -rm --disable-addons Same as above, but with add-ons disabled Some of the command line options accept additional parameters; e.g. how detailed the logging should be or the path to the user configuration directory. Those parameters should be placed after the option, separated from the option by a space when using the short version or an equals sign (=) when using the long version; e.g.: nvda -l 10 Tells NVDA to start with log level set to debug nvda --log-file=c:\nvda.log Tells NVDA to write its log to c:\nvda.log nvda --log-level=20 -f c:\nvda.log Tels NVDA to start with log level set to info and to write its log to c:\nvda.log Following are the command line options for NVDA: Short Long Description -h --help show command line help and exit -q --quit Quit already running copy of NVDA -r --replace Quit already running copy of NVDA and start this one -k --check-running Report whether NVDA is running via the exit code; 0 if running, 1 if not running -f LOGFILENAME --log-file=LOGFILENAME The file where log messages should be written to -l LOGLEVEL --log-level=LOGLEVEL The lowest level of message logged (debug 10, info 20, warning 30, error 40, critical 50), default is warning -c CONFIGPATH --config-path=CONFIGPATH The path where all settings for NVDA are stored -m --minimal No sounds, no interface, no start message etc -s --secure Secure mode (disable Python console) None --disable-addons Addons will have no effect None --debug-logging Enable debug level logging just for this run. This setting will override any other log level ( --loglevel, -l) argument given. None --no-sr-flag Don't change the global system screen reader flag None --install Installs NVDA (starting the newly installed copy) None --install-silent Silently installs NVDA (does not start the newly installed copy)

Am 29.06.2017 um 19:13 schrieb Jen Bottom:

...
Hi everyone,

I am still on my quest to be able to set up a Windows Box with Vagrant, that is provisioned with NVDA and that will provide some sort of speech output once the provisioner has run.

I have now managed to get the provisioner to run on a Windows10 box, after messing about with 'winrm' for a while.

This script installs the NVDA package using 'choco'.

I don't think it's the latest but better than nothing.

However NVDA does not automatically start once the package is installed.

Note currently I don't have access to a physical box running Windows that I can test stuff out on.

I am looking for a way to start either NVDA or Narrator from the command prompt or power shell, so I can at least get some feedback.

I have tried going to the VM GUI and using the NVDA short cut key as a quick work-around, but nothing seemed to happen.

Also as I am being lazy and not building my own Vagrant box, a quick way to enable Audio if it is disabled is appreciated.

I think it is available on the box I have, but I may play with different Windows boxes in the future.

Thanks in advance for any suggestions, Jen!

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

-- Simon Eigeldinger Follow me on Twitter: http://www.twitter.com/domasofan/ E-Mail: simon.eigeldinger@vol.at MSN: simon_eigeldinger@hotmail.com ICQ: 121823966 Jabber: domasofan@andrelouis.com

--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

2625

Age (days ago)

2636

Last active (days ago)

List overview

Download

7 comments

5 participants

participants (5)

Ben Mustill-Rose
Guerra Access Technology Training LLC
Jen Bottom
Ratha Moeuy
Simon Eigeldinger

Starting NVDA or Narrator from command prompt or power shell?

tags

participants (5)