[nfbcs] JAWS does not read the Windows 10 CMD prompt automatically

Tue Feb 13 22:23:42 UTC 2018

Ok, got it, my apologies for confusion between Jaws 18 and 2018.

Tony

On 2/13/2018 1:18 PM, Doug Lee via nfbcs wrote:
> Glen is part of Freedom Scientific, yes. JAWS 2018 is the next major version after JAWS 18. The version numbering system changed at that point, so that each JAWS version will be the year in which that version is most expected
> to be current. Think of JAWS 2018 as a rename of what would have been JAWS 19.
>
> On Tue, Feb 13, 2018 at 12:34:37PM -0800, NFBCS mailing list wrote:
> 1. I didn't reply to Gordon. I addressed JooYoung.
> 2. I don't know who Gordon is and whether he is affiliated with Freedom
> Scientific. I saw his reply.
> 3. As I mentioned before, I talked to Freedom Scientific a long time ago about
> that. In particular I called them in 2016 and they promised me that it'll be
> fixed in Jaws 17. And I remember they were using exactly the same argument:
> Microsoft changed something in their accessibility APIs and the next version
> of Jaws will take that into account. I don't know why I'm explaining all that
> to you, but I don't trust them anymore. I've been waiting for this fix for two
> years and it's still not there. I'm not sure if Jaws 2018 is the same as Jaws
> 18, but as I mentioned, I have Jaws 18 with all the latest updates installed
> and it still doesn't work for me.
>
> HTH
>
> 3.
> On 2/13/2018 12:16 PM, Littlefield, Tyler wrote:
>> Tony:
>> You are responding to an email from Glen Gordon, who says this:
>>
>>      Hi, JooYoung,
>>
>>      Changes in the Fall Creators' update required that JAWS rework how
>>      it detects newly written text in console windows. This is fixed in
>>      the current version
>>      of JAWS 2018.
>>      Unfortunately, there isn't a workaround for earlier JAWS versions.
>>
>> This says what you're saying, but provides a solution: windows 10 updates
>> changed how the console works; there is a fix in Jaws 2018.
>> HTH,
>>
>> 2/13/2018 2:44 PM, Tony Malykh wrote:
>>> Tyler,
>>>
>>>
>>> With all my respect, I don't think I'm starting a war. User had a
>>> problem and I suggested two ways to work around it.
>>>
>>>
>>> I have Jaws 18 installed on my computer and Windows 10 and I just
>>> confirmed that it deosn't work with command line. Same is true for my
>>> wife. Same as true for a few blind friends who are using Jaws. I don't
>>> think I have a problem on my end. If it works for you, I suspect you
>>> are using legacy console. I need to use some applications that are
>>> incompatible with legacy console, so that's not an option for me.
>>> That's why I suggested NVDA. If that person needs to use such
>>> applications, I'm afraid NVDA might be the only option for them.
>>>
>>>
>>> Tony
>>>
>>>
>>>
>>> On 2/13/2018 11:30 AM, Littlefield, Tyler wrote:
>>>> Tony:
>>>> Without starting a screenreader war, I've used the windows command
>>>> prompt for years with Jaws and it works just fine. The email which
>>>> you are replying to explains that 2018 has a command prompt fix,
>>>> and I happen to be doing work in command prompt on windows 10 with
>>>> jaws 2018. So in short, it might be worth investigation on your
>>>> issue, but it's incorrect to say that Jaws is broken and has been
>>>> for years with command prompt.
>>>> Thanks,
>>>>
>>>> On 2/13/2018 12:50 PM, Tony Malykh via nfbcs wrote:
>>>>> Hi Jooyoung
>>>>>
>>>>>
>>>>> Command line prompt has been broken in Jaws forever. I
>>>>> complained to Freedom Scientific about two years ago, and they
>>>>> just keep promising that they will fix it in the next release,
>>>>> which never happens. I have Jaws 18 on my computer and I just
>>>>> confirmed that it still doesn't work.
>>>>>
>>>>>
>>>>> There is one workaround you can try. Go to properties of CMD,
>>>>> go to Advanced tab and check "Use legacy console". Some
>>>>> programs won't work with legacy console, but hopefully you
>>>>> don't need them. Or if you're like me, consider switching to
>>>>> NVDA - it works with CMD and in my experience tends to work
>>>>> better with other program.s
>>>>>
>>>>>
>>>>> Tony
>>>>>
>>>>>
>>>>>
>>>>> On 2/12/2018 12:50 PM, Glen Gordon via nfbcs wrote:
>>>>>> Hi, JooYoung,
>>>>>>
>>>>>> Changes in the Fall Creators' update required that JAWS
>>>>>> rework how it detects newly written text in console
>>>>>> windows. This is fixed in the current version of JAWS
>>>>>> 2018.
>>>>>> Unfortunately, there isn't a workaround for earlier JAWS versions.
>>>>>>
>>>>>> --Glen
>>>>>>
>>>>>> Glen Gordon
>>>>>> VFO | Vice President & Chief Technology Officer
>>>>>> 11800 31st Court North, St. Petersburg, FL 33716
>>>>>> T 727-299-6230
>>>>>> ggordon at vfo-group.com
>>>>>> www.vfo-group.com
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: nfbcs <nfbcs-bounces at nfbnet.org> On Behalf Of
>>>>>> Jooyoung via nfbcs
>>>>>> Sent: Monday, February 12, 2018 2:09 PM
>>>>>> To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
>>>>>> Cc: Jooyoung <sjysky at gmail.com>
>>>>>> Subject: [nfbcs] JAWS does not read the Windows 10 CMD
>>>>>> prompt automatically
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>>
>>>>>> I have a question concerning Windows 10 CMD prompt reading with JAWS.
>>>>>>
>>>>>> I have recently set up JAWS 17 on Windows 10 system.
>>>>>>
>>>>>> If I open a CMD window, JAWS does not read the command
>>>>>> prompt automatically; I have to manually use the JAWS
>>>>>> cursor to interact with the screen.
>>>>>>
>>>>>> FYI, I have already set the "Screen Echo" as "All," and I
>>>>>> also have tried "Highlighted" as well. But none of them
>>>>>> worked.
>>>>>>
>>>>>> I opened the prompt using administrator's permission.
>>>>>> Also, I tried just general user permission. Regretably,
>>>>>> none of them worked, either.
>>>>>>
>>>>>>
>>>>>> Does anyone know how to tackle this issue?
>>>>>>
>>>>>> Any advice would be so much appreciated.
>>>>>>
>>>>>>
>>>>>> Sincerely,
>>>>>>
>>>>>>
>>>>>> JooYoung
>>>>>>
>>>>>> _______________________________________________
>>>>>> nfbcs mailing list
>>>>>> nfbcs at nfbnet.org
>>>>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>>>>> To unsubscribe, change your list options or get your
>>>>>> account info for nfbcs:
>>>>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ggordon%40vfogroup.com
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> nfbcs mailing list
>>>>>> nfbcs at nfbnet.org
>>>>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>>>>> To unsubscribe, change your list options or get your
>>>>>> account info for nfbcs:
>>>>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/anton.malykh%40gmail.com
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> nfbcs mailing list
>>>>> nfbcs at nfbnet.org
>>>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>>>> To unsubscribe, change your list options or get your account
>>>>> info for nfbcs:
>>>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
>>>>>
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/dgl%40dlee.org
>