In fact, the jfwservice service doesn't exist under Vista. I tried "net start jfwservice" at the command prompt and it said "invalid service name", something like that. -- Chris Hallsworth Derbyshire, UK E-mail christopherhallsworth71@xxxxxxxxxxxxxx MSN ch9675@xxxxxxxxxxx Skype chrishallsworth7266 Website http://www.chrishallsworth.co.nr Klango chrishallsworth FTP ftp://chrishallsworth.dyndns.org ----- Original Message ----- From: "Brian Hartgen" <jaws@xxxxxxxxxxx> To: <jawsscripts@xxxxxxxxxxxxx> Sent: Wednesday, August 20, 2008 6:10 PM Subject: [jawsscripts] Re: Why does this work? > The behaviour Jamal describes works exactly the same within Windows Vista > as > this is how I use it. > > Regards: > > Brian Hartgen > -----Original Message----- > From: jawsscripts-bounce@xxxxxxxxxxxxx > [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Hallsworth > Sent: 20 August 2008 17:58 > To: jawsscripts@xxxxxxxxxxxxx > Subject: [jawsscripts] Re: Why does this work? > > Ah, but this may not work for Vista users as JAWS doesn't actually load as > a > > service to speak the Windows Logon dialogue box. > > -- > Chris Hallsworth > > Derbyshire, UK > > E-mail > christopherhallsworth71@xxxxxxxxxxxxxx > > MSN > ch9675@xxxxxxxxxxx > > Skype > chrishallsworth7266 > > Website > http://www.chrishallsworth.co.nr > > Klango > chrishallsworth > > FTP > ftp://chrishallsworth.dyndns.org > ----- Original Message ----- > From: "Martin Courcelles" <martinfc@xxxxxxxxxx> > To: <jawsscripts@xxxxxxxxxxxxx> > Sent: Wednesday, August 20, 2008 5:14 PM > Subject: [jawsscripts] Re: Why does this work? > > >> Well, there is a jfwkill.exe file, but there's a much better way of doing >> things; through the net command. >> I've created 2 shortcut key combinations which use the below commands to >> load and unload Jaws as follows: >> net start JFWService >> Net stop JFWService >> I personally use hoekey, however the built-in windows shortcut keys >> should >> work. So now, if Jaws misbehaves, I can kill it in one keystroke and >> reload it with an other. >> Cheers, >> Martin >> >> >> >>> Date: Wed, 20 Aug 2008 17:07:14 +0100 >>> From: "Brian Hartgen" <jaws@xxxxxxxxxxx> >>> To: <jawsscripts@xxxxxxxxxxxxx> >>> ReplyTo: 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 >> > > __________ > 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