Hi Glen,
A fix in the meantime is to go into a command prompt, press Alt Space and go
down to Properties, then in there, tick the box that says Legacy Console.
JAWS will be happy and the world will be round again.
All, the best
Steve
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Glen
Gordon
Sent: 20 November 2017 15:44
To: Blind sysadmins list
Subject: Re: [Blind-sysadmins] Command line in Windows 10 build 17,040
I can speak only to the JAWS issues.
They will be fixed in the JAWS 2018 December update.
--Glen
Glen Gordon
VFO | Vice President & Chief Technology Officer
11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230
ggordon@vfo-group.com www.vfo-group.com
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of
Katherine Moss
Sent: Monday, November 20, 2017 8:50 AM
To: blind-sysadmins@lists.hodgsonfamily.org
Subject: [Blind-sysadmins] Command line in Windows 10 build 17,040
Hi all,
I was having a recent discussion on twitter with a couple of people
regarding this very issue, and I've found mixed responses; some say that the
recent command line issues with NVDA/JAWS are fixed, but it doesn't seem to
be on my dell Latitude E6540. I have to launch Narrator every time I want to
use the command line, and while that works, it's not ideal if I can help it.
I much prefer the speed and agility of NVDA. Any advice? Thanks.
_______________________________________________
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