[nfb-talk] need help with jaws
John Heim
john at johnheim.net
Fri Jun 10 15:23:27 UTC 2011
Right, I know that a normal window set to 80x25 would be about the same
thing as a full screen window. But I didn't intend to ask for help on how
best to run ssh. There are a few fairly minor reasons to prefer a full
screen window. But yeah, the reasons for prefering a full screen window are
fairly trivial. But like I said, I was just asking if people could duplicate
the problem I am having because Freedom Scientific tech support says they
can't do that.
Anyway, NVDA does work in a full screen command window in every combination
of Windows and jaws I have access to right now, win XP and jaws 9, win XP
and jaws 12, and Win 7 and jaws 12. So chock one up for open source
software, I guess.
----- Original Message -----
From: "Steve Jacobson" <steve.jacobson at visi.com>
To: "NFB Talk Mailing List" <nfb-talk at nfbnet.org>
Sent: Thursday, June 09, 2011 9:08 PM
Subject: Re: [nfb-talk] need help with jaws
> John,
>
> I forgot to ask which operating system you were using. The fact that NVDA
> works with this surprises me some but
> makes me wonder if you are using Windows 7. I just tried ALT-ENTER on my
> Windows 7 64-bit machine and it didn't
> seem to do anything as far as I could tell, so my information might be out
> of date. I am a window-eyes user, but in the
> past Window-Eyes acted the same as JFW in this respect, but my
> understanding was that in full-screen mode, the
> content of the command prompt was more or less invisible to Windows as a
> whole. Anyway, maybe there is someone
> on NFBCS who would know more about this. I think, though, that you should
> be able to get 25 by 80 displayed
> without full-screen mode, so there is probably still an element here I
> don't understand.
>
> Best regards,
>
> Steve Jacobson
>
> On Thu, 9 Jun 2011 16:18:30 -0500, John Heim wrote:
>
>>Yeah, I think you understand what I'm saying exactly. As I said in another
>>message, I expected FS to tell me it was a known bug and that they
>>couldn't
>>do anything about it. But then they told me they couldn't replicate it and
>>I
>>started thinking it was just me. I just figured there was no harm in
>>asking
>>FS about the problem especially since nvda does read the text in a full
>>screen command window.
>
>>What I'm really trying to do is run curses applicationson a linux machine
>>via ssh. Specifically, dpkg and the kernel configuration program. These
>>programs run in character mode like an old DOS screen. A maximized ssh
>>window does okay most of the time but the problem is that a mistake when
>>setting kernel config parameters can keep your machine from booting. I
>>don't
>>know if you ever had to fall back to a previous kernel when booting a
>>linux
>>machine but its really a PITA. So what I've been doing when I really need
>>to
>>make sure I don't make any mistakes is stop jaws, load nvda, and put the
>>ssh
>>window into full screen mode. Either that or reboot my desktop into linux
>>and use speakup.
>
>>Well, I'm getting a little off topic for this list. I guess the lesson is
>>that if you really want to talk to a linux machine, use another linux
>>machine.
>
>>----- Original Message -----
>>From: "Steve Jacobson" <steve.jacobson at visi.com>
>>To: "NFB Talk Mailing List" <nfb-talk at nfbnet.org>
>>Sent: Thursday, June 09, 2011 1:56 PM
>>Subject: Re: [nfb-talk] need help with jaws
>
>
>>> John,
>>>
>>> You might get better answers on GUI-Talk, but I'll comment here. If
>>> what
>>> you are encountering is that you don't get speech when you are in full
>>> screen
>>> mode, that is not a bug as such, or at least it is not a JFW-Specific
>>> bug.
>>> The full screen mode works differently than even running maximized so
>>> screen
>>> readers seem not to be able to get the information they need. If you
>>> create a shortcut for the command prompt that runs it maximized, you
>>> should achieve
>>> most of what you are after and JFW should still speak.
>>>
>>> If I am understanding what you wrote correctly, this is an old and
>>> well-known limitation and FS should have been able to explain this and
>>> certainly duplicate
>>> it. If I have not understood correctly, please describe in more detail
>>> and I'll try again.
>>>
>>> Best regards,
>>>
>>> Steve Jacobson
>>>
>>> On Thu, 9 Jun 2011 11:35:12 -0500, John Heim wrote:
>>>
>>>>All,
>>>
>>>>I'm having a problem with my jaws screen reader. I submitted a bug
>>>>report
>>>>but Freedom Scientific tells me they can't reproduce the bug. My
>>>>experience
>>>>has been that all version of jaws have had this problem and it happens
>>>>on
>>>>every computer I've ever tried it on. So I was hoping other users of
>>>>jaws
>>>>could tell me if they can reproduce the problem.
>>>
>>>>The problem is that jaws can't read text in a full screen command
>>>>window.
>>>>A
>>>>command window is the way Microsoft Windows lets you ttype in commands
>>>>sort
>>>>of like the old days of DOS. If you use jaws I think you may be able to
>>>>reproduce my problem by doing the following:
>>>
>>>>1. Press Windows+r to open a run dialog box. Jaws should say "Type the
>>>>name
>>>>of a program etcetera" Type the word command and press enter. That
>>>>should
>>>>open a command window.
>>>>2. Press Alt+Enter to make the window full screen. At this point, if you
>>>>type a command like dir or help, text will be displayed on the screen
>>>>but
>>>>not spoken by jaws. Or at least that is what it does for me.
>>>>3. Put the window back to normal size by pressing Alt+Enter again. Now
>>>>when
>>>>you type a command, jaws will work correctly and read the text that is
>>>>displayed.
>>>
>>>
>>>>_______________________________________________
>>>>nfb-talk mailing list
>>>>nfb-talk at nfbnet.org
>>>>http://www.nfbnet.org/mailman/listinfo/nfb-talk_nfbnet.org
>>>>To unsubscribe, change your list options or get your account info for
>>>>nfb-talk:
>>>>http://www.nfbnet.org/mailman/options/nfb-talk_nfbnet.org/steve.jacobson%40visi.com
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> nfb-talk mailing list
>>> nfb-talk at nfbnet.org
>>> http://www.nfbnet.org/mailman/listinfo/nfb-talk_nfbnet.org
>>> To unsubscribe, change your list options or get your account info for
>>> nfb-talk:
>>> http://www.nfbnet.org/mailman/options/nfb-talk_nfbnet.org/john%40johnheim.net
>>>
>
>
>>_______________________________________________
>>nfb-talk mailing list
>>nfb-talk at nfbnet.org
>>http://www.nfbnet.org/mailman/listinfo/nfb-talk_nfbnet.org
>>To unsubscribe, change your list options or get your account info for
>>nfb-talk:
>>http://www.nfbnet.org/mailman/options/nfb-talk_nfbnet.org/steve.jacobson%40visi.com
>
>
>
>
>
> _______________________________________________
> nfb-talk mailing list
> nfb-talk at nfbnet.org
> http://www.nfbnet.org/mailman/listinfo/nfb-talk_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> nfb-talk:
> http://www.nfbnet.org/mailman/options/nfb-talk_nfbnet.org/john%40johnheim.net
>
More information about the nFB-Talk
mailing list