[jawsscripts] Re: Why does this work?

  • From: Jamal Mazrui <empower@xxxxxxxxx>
  • To: jawsscripts@xxxxxxxxxxxxx
  • Date: Wed, 20 Aug 2008 12:42:34 -0400 (EDT)

That helps, Bryan, and having now done more investigation of this issue,
I think the following is happening.

I guess FBSA is an abbreviation for Freedom Box System Access.  That is
the module name of the custom web browser for accessing the SA network of
content.  JAWS goes to sleep if only the SA browser is launched, and JAWS
is awake when Alt+Tabbing to other application windows besides the
browser.  When the browser is closed, JAWS remains active in any
application window (unless that app was specifically put to sleep).  This
is the expected behavior of JAWS, sleeping on a per-application basis.

On the other hand, if the SA screen reader is launched to give access to
applications other than the SA browser, SA kills the JAWS application.
SA apparently includes custom code that checks for JAWS running but
asleep in the FBSA browser.  If the SA screen reader finds that to be
the case, it eliminates JAWS completely from memory (I don't know by
what method).  When the SA screen reader is closed, JAWS has to be
relaunched.  So, the sleeping and waking up was not as automatic and
complete as the instructions may have implied, and which my friend
initially thought was the case.

Jamal

On Wed, 20 Aug 2008, Brian Hartgen wrote:

> Date: Wed, 20 Aug 2008 17:07:14 +0100
> From: Brian Hartgen <jaws@xxxxxxxxxxx>
> Reply-To: jawsscripts@xxxxxxxxxxxxx
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Why does this work?
>
> Hi Jamal
>
> There are two things going on here.
> 1. Sean is correct in that if you use the System Access Mobile Network
> browser, that is one application and so putting jaws to sleep in the .JCF
> will in fact work.  This would be logical and is the way jaws would treat
> any application as you observed.
> 2. However, certainly what happens for me if I launch the system access
> screen-reader, which is different altogether, if jaws is running it will be
> closed automatically and SA will take over.  When I close SA, jaws is not
> running so I would have to start it from the run dialog.
> This is a recent initiative. Previously, if jaws was running and I started
> the SA screen-reader, I would get a dialog to the effect that another
> screen-reader was running and I had to close it before running SA.  Now it
> is much more elegant as SA seems to close jaws automatically because there
> is an executable to stop jaws from running isn't there.
>
> Does that help at all?
>
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
> Sent: 20 August 2008 16:55
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Why does this work?
>
> Hi Sean,
> Normally, JAWS uses application settings when an application
> becomes the active window, but not otherwise.  This works
> regardless of what window is active.  By comparison, for example, if JAWS
> is put to sleep in the .jcf file for Open Book, that setting is only
> in effect when Open Book is the active application window.  If Open
> Book is open in another window (requiring Alt+Tab to get there), JAWS
> will not be asleep.
>
> Jamal
> --Original Message--
> Wed, 20 Aug 2008, Sean Farrow wrote:
>
> > Date: Wed, 20 Aug 2008 16:40:55 +0100
> > From: Sean Farrow <sean.farrow@xxxxxxxxxxxxxxxx>
> > Reply-To: jawsscripts@xxxxxxxxxxxxx
> > To: jawsscripts@xxxxxxxxxxxxx
> > Subject: [jawsscripts] Re: Why does this work?
> >
> > Hi Jamal:
> > This works as the systam accss application is called fbsa.exe. So what is
> being said is, when ever fbsa loads go to sleep/unmute the synthesizer.
> > Hth
> > Sean.
> >
> > -----Original Message-----
> > From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
> > Sent: 20 August 2008 16:27
> > To: jawsscripts@xxxxxxxxxxxxx
> > Subject: [jawsscripts] Why does this work?
> >
> > A friend uses System Access sometimes in addition to JAWS.  In an
> > SA-related forum, he found the instructions below on how to put JAWS to
> > sleep whenever SA is loaded, and automatically wake it up when SA is
> > unloaded.  It surprises me that this works because I thought JAWS could
> > only be put to sleep on a per-application basis (doing this in default.jcf
> > would not make sense, as far as I know)  Does anyone have ideas about how
> > this technically works?  My friend confirms that JAWS does
> > sleep and wake up as intended if the instructions are followed.
> >
> > Jamal
> >
> > 1. run jaws
> >
> > 2. insert+f2 and enter on config manager
> >
> > 3. ctrl+n new file named "fbsa" then press enter
> >
> > 4. alt+s for set options; then press a for advanced options
> >
> > 5. sleep mode enable checkbox checked
> >
> > 6. unload synthesizer checkbox checked
> >
> > 7. enter on okay
> >
> > 8. ctrl+s to save config file; then alt+f4
> >
> >
> > .
> >
> > __________ 
> > View the list's information and change your settings at
> > //www.freelists.org/list/jawsscripts
> >
> >
> >
> > __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3371 (20080820) __________
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> > __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3371 (20080820) __________
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> > __________ 
> > View the list's information and change your settings at
> > //www.freelists.org/list/jawsscripts
> >
> __________ 
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
> __________ 
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
__________ 
View the list's information and change your settings at 
//www.freelists.org/list/jawsscripts

Other related posts: