[gui-talk] Fwd: some jaws7.1 goodies, ahem, people may not have seen!

Anthony Vece ajvece at verizon.net
Mon Jun 26 06:27:58 CDT 2006


As I said, Jaws 7.1 has more bugs in it than palmetto bugs in St. 
Petersburg.

It really is a disgrace.

The only reason why I am keeping JAWS is because I got it for nothing and I 
can't be bothered putting up with pressing wrong key strokes in WindowEyes.

However, I really believe that all these companies should be held to higher 
standards.
\
I am really not trying to bash Freedom Scientific however, it is obvious 
that they are just not concerned with the quality of there product or 
customer satisfaction.

Anthony


----- Original Message ----- 
From: "Steve Pattison" <srp at internode.on.net>
To: "GUI Talk" <gui-talk at nfbnet.org>; "Access-L" <access-l at access-l.com>
Sent: Sunday, June 25, 2006 9:32 PM
Subject: [gui-talk] Fwd: some jaws7.1 goodies, ahem, people may not have 
seen!


>
>>From: Geoff Chapman gch at internode.net.au
>>To: vision impaired persons list vip-l at softspeak.com.au
>>
>>from the website:
>>http://www.freedomscientific.com/fs_support/BulletinList.cfmQC=1081>
>>
>>there's a lot more here than I've posted, and to me, it's a good place to
>>start for all the real good dope on jaws stuff. you find some real gems
>>browsing in here.
>>whether they're polished gems or old sandstone, is of course, open to
>>subjective interpretation! <smile.>
>>
>>
>>Question:
>>
>>Why can't I use my PlaceMarkers from an earlier version of JAWS with JAWS
>>7.10 or later?
>>
>>Answer:
>>
>>PlaceMarkers created with JAWS 7.0 and earlier are not compatible with 
>>JAWS
>>7.10 or later, due to internal changes. Similarly, JAWS 7.10 PlaceMarkers
>>are
>>not compatible with JAWS 7.0 or earlier.
>>
>>If you copy PlaceMarker files from an earlier version of JAWS into your 
>>JAWS
>>7.10 user settings PlaceMarkers folder, the PlaceMarkers do not appear in
>>the
>>CTRL+SHIFT+K PlaceMarker list. You also cannot use the Navigation Quick 
>>Key
>>K to move to the PlaceMarkers.
>>
>>You must recreate your PlaceMarkers for the Web sites you visit in order 
>>to
>>use them with JAWS 7.10.
>>
>>
>>bc: hooly dooly! unbelievable!
>>saw absolutely no reference to this at all on the whatsnew for 7.1 page!
>><large sigh.>
>>
>>that's a pretty sad downer, especially since it appears their internal
>>changes that have now apparently broken any earlier place markers one 
>>may've
>>had, when using 7.10,
>>have not even addressed the seeming non ability to create a place marker,
>>directly, on top of an edit box field. such that you could then hit k to
>>jump to it, and straight away hit enter to enter forms mode and start
>>typing! grumph! i really hoped they were gunna fix that.
>><guess I should've reported it then eh. thought others might though. 
>><sigh.>
>>
>>
>>Category: Microsoft Word
>>
>>In Microsoft Word, if I use M or SHIFT+M to move to a misspelled word, why
>>is the entire word automatically selected?
>>
>>Answer:
>>
>>In Microsoft word, if you turn on the JAWS Navigation Quick Keys 
>>(INSERT+Z),
>>you can use M or SHIFT+M to navigate the document by misspelled word.
>>
>>Microsoft's documentation states that to move to the next/prior 
>>proofreading
>>item in the document you must use one of the GoTo functions. Then, once 
>>the
>>range is obtained, you must manually select that range. This, in turn,
>>causes it to be selected with the cursor on the first character of the
>>selection.
>>There is an advantage to having it selected: you can either leave Quick 
>>nav
>>mode and type over the word or better yet, you can press the application 
>>key
>>and land in the context menu to then choose to view suggestions for the
>>selected word.
>>
>>Unselecting the text prevents further movement forward or backward through
>>the document. The only way found at this time to do it consistently is to
>>leave
>>the item selected.
>>
>>
>>for jaws versions 4x plus?
>>(that's what it says for below,)
>>
>>Category: JAVA
>>
>>Short Description:
>>
>>Some Java Swing applications are not compatible with the newer Access 
>>Bridge
>>2.0.
>>
>>Problem:
>>
>>After updating Java Runtime Environment (JRE) 1.42_x with Access Bridge 
>>(AB)
>>1.2, to JRE 1.50_x and Access Bridge 2.0, the JAVA Swing UI application no
>>longer works with JAWS.
>>
>>Solution:
>>
>>You may need to uninstall Java 1.5.x and Sun Access Bridge 2.0 completely
>>and reinstall Java 1.4.x with Access Bridge 1.x in order to use the
>>application
>>with JAWS.
>>
>>Since JAWS uses WindowsAccessBridge.DLL, this .DLL file will not be 
>>removed
>>properly if you are running JAWS while uninstalling SUN's Access Bridge 
>>2.0.
>>For speech accessibility while uninstalling Java Access Bridge 2.0, you 
>>must
>>shutdown JAWS and start Windows Narrator (WINDOWS Key+U). This allows
>>WindowsAccessBridge.DLL
>>to be removed from the system32 folder in Windows.
>>
>>
>>
>>
>>
>>Version: 5.10 plus
>>
>>Category: Microsoft Outlook
>>
>>Question:
>>
>>Why can't I see the closed state of items in the Outlook 2003 mailbox tree
>>view?
>>
>>Answer:
>>
>>Based on our research and testing, we believe this issue is caused by a 
>>flaw
>>in Microsoft's implementation of MSAA (Microsoft Active Accessibility). In
>>Outlook 2003, there is no way to distinguish between a closed folder and a
>>folder that has no subfolders. If JAWS announces, "Closed," for a folder
>>with
>>multiple subfolders, it also reports, "Closed," for folders that do not 
>>have
>>subfolders.
>>
>>This may be resolved in a future version of Microsoft Office.
>>
>>
>>
>>Version: 7.10 plus
>>
>>Category: Installation
>>
>>Question:
>>
>>Why can't I see the state of the options in the tree view during a custom
>>install?
>>
>>Answer:
>>
>>If Microsoft Narrator starts and then stops during a custom JAWS
>>installation, the Windows Screen Reader flag is not activated. As a result
>>of this, some
>>Windows controls, such as tree view items, do not report if they were
>>correctly installed.
>>
>>
>>
>>Version: Any
>>
>>Category: MSAA
>>
>>Short Description:
>>
>>Quitting Microsoft Narrator while JAWS is running causes Microsoft Active
>>Accessibility (MSAA) controls to be incorrectly reported to JAWS.
>>
>>Problem:
>>
>>If you quit Microsoft Narrator while JAWS is running, the Windows Screen
>>Reader flag is turned off. This results in problems with MSAA reporting
>>incomplete
>>information when JAWS queries dialog controls that provide MSAA 
>>information.
>>For example checkable items in a tree view may not state their on/off 
>>state
>>or may not indicate that they are checked or unchecked.
>>
>>Solution:
>>
>>If you quit Microsoft Narrator while running JAWS, and you find that MSAA
>>controls are no longer reporting the correct information, quit and restart
>>JAWS.
>>The Screen Reader flag turns on when JAWS starts.
>>
>>
>>
>>Product Name: JAWS
>>
>>Version: 5.10 plus
>>
>>Category: Video
>>
>>Short Description:
>>
>>JAWS may become stuck in a reboot loop at startup, or a "Catastrophic
>>Failure" error message may appear.
>>
>>Problem:
>>
>>Because JAWS, MAGic and OpenBook cannot hook the JAWSVID DCM video 
>>intercept
>>if two video drivers are installed, when installing, the software may 
>>become
>>stuck in a reboot loop at startup, or a "Catastrophic Failure" error 
>>message
>>may appear. Some computer manufacturers, including Dell and HP, ship their
>>computers with one physical video card installed, but include two 
>>different
>>video drivers. This is done so that they can use the same operating system
>>image for multiple computer models. Freedom Scientific products cannot 
>>hook
>>the JAWSVID DCM video intercept if two video drivers are installed.
>>
>>This only affects Windows XP, Windows 2000 Pro, Windows 2000 Server, 
>>Windows
>>2000 Advanced Server, and Windows 2003 Server.
>>
>>The following symptoms may indicate if you are affected by this problem:
>>
>>* While installing or uninstalling a Freedom Scientific product, you are
>>continually prompted to reboot the computer. The install/uninstall process
>>does
>>not continue due to the reboot prompts.
>>
>>* The Freedom Scientific product is properly installed, but when you 
>>launch
>>it, you constantly receive a notification to hook the DCM video intercept.
>>You
>>hook the video intercept and reboot; however, each time you start the
>>Freedom Scientific product, you are again prompted to rehook the video
>>intercept.
>>
>>Solution:
>>
>>If you experience any of the problems described with JAWS, MAGic, 
>>OpenBook,
>>or Connect Outloud, check the list of video drivers found in Device 
>>Manager.
>>If more than one is present, determine which of the installed video 
>>drivers
>>listed does not apply to your currently installed physical hardware, and
>>uninstall
>>it. Reboot your computer after removing the video driver. Once you have
>>uninstalled the unwanted video driver, reboot the system.
>>
>>
>>Date Posted: 03/10/2006
>>
>>Product Name: JAWS
>>
>>Version: 7.0 plus
>>
>>Category: Synthesizer
>>
>>Short Description:
>>
>>JAWS crashes when you change to VoiceWare SAPI synthesizers.
>>
>>Problem:
>>
>>You can use the VoiceWare Paul and Kate voices with Kurzweil 1000 V10, but
>>you must first set your synthesizer to SAPI 5 in JAWS before choosing the 
>>VW
>>Paul or Kate voices. If you run JAWS as a service, JAWS will stop 
>>responding
>>after this change.
>>
>>Solution:
>>
>>If you want to use a VoiceWare synthesizer as your default synthesizer, 
>>run
>>JAWS as an application.
>>
>>To run JAWS as an application:
>>1. Choose Options from the menu bar in JAWS.
>>2. Choose Basics in the submenu.
>>3. Tab to the "Automatically start JAWS" check box and uncheck it.
>>
>>You must start JAWS manually when you start your computer. You can use a
>>shortcut key or launch JAWS from the run dialog by typing "JAWS70" or
>>"JAWS7."
>>
>>You can now use the VoiceWare Paul or VoiceWare Kate voices. If you switch
>>to a non-VoiceWare synthesizer, you can run JAWS as a service.
>>
>>
>>
>>Version: 6.0 plus
>>
>>Category: Authorization
>>
>>Short Description:
>>
>>Braille flash messages disappear too quickly to read when you press LEFT 
>>or
>>RIGHT ARROW in a marked-up Word document.
>>
>>Problem:
>>
>>If you are using braille and you read through a marked-up Word document,
>>Flash Messages appear on your braille display. These messages contain
>>information
>>about what type of editing was performed and/or who performed the editing.
>>If you press LEFT or RIGHT ARROW, the flash messages do not remain on the
>>display
>>long enough to read.
>>
>>Solution:
>>
>>Pressing INSERT+TAB will cause the Flash Message to appear again. This 
>>time,
>>the message will remain on the display long enough to read.
>
> Regards Steve
> Email:  srp at internode.on.net
> Skype:  steve1963
> MSN Messenger:  internetuser383 at hotmail.com
>
> _______________________________________________
> gui-talk mailing list
> gui-talk at nfbnet.org
> http://www.nfbnet.org/mailman/listinfo/gui-talk
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.9.4/375 - Release Date: 6/25/2006
> 



More information about the gui-talk mailing list