Why does a client version of JAWS prompt a warning dialog each time a client manager utility is launched? (4/9/2008)

 

Date Posted: 4/9/2008
Product Name: JAWS
Version: 8.0 plus
Category: Network JAWS
 

Question:
Why does a client version of JAWS prompt a warning dialog each time a client manager utility is launched?
 

Answer:
In a Client installation of JAWS, when the client version launches a JAWS manager utility, such as Configuration Manager, a warning prompt is displayed. This is true with both Windows XP as well as Windows Vista. If you get an "Open File - Security Warning" dialog when trying to launch JAWS on the Network Client, then the server is not trusted in the Local intranet zone. To change this, do the following:
Go to Control Panel -> Internet Options.

In the Internet Properties dialog, select the Security tab.

Select the Local intranet zone and choose the Sites button.

In the Local intranet dialog, choose the Advanced button.

Type in the server path and choose Add.

Ensure that the "Require server verification (https:) for all sites in this zone" checkbox is unchecked.

Choose Close to exit the dialog.

Choose OK to exit the Local intranet dialog.
NOTE: It is recommended that you run a Network JAWS client under Vista with UAC turned off, otherwise you will have problems accessing UAC enabled applications which need elevated privileges. You can read more in the bulletin "If running Network JAWS as a Client in Windows Vista, JAWS cannot speak the UAC dialog."

---

If running Network JAWS as a Client under Vista, JAWS cannot speak the UAC dialog. (6/15/2007)

Bulletin Number: 32328
Date Posted: 6/15/2007
Product Name: JAWS
Version: 8.0 plus

Category: Network JAWS

Short Description:
If running Network JAWS as a Client under Vista, JAWS cannot speak the UAC dialog.

Problem:
If JAWS is running as a Network JAWS Client on Windows-Vista and the UAC is enabled you cannot get speech or braille while in the UAC dialog. Once UAC is accepted you have little control of JAWS while in the app which requested elevated privilege. In addition, if the UAC dialog is accepted and the app which requested elevation is now running then you will get limited JAWS speech and limited braille within that app. You can tab around but some elements may be difficult to use such as application page tab controls, highlights may not track properly, and key interrupt will not properly work. Once you close the elevated app then JAWS returns to normal.

Solution:
At this time the only solution is to turn UAC off. Once you do that the only thing which you will need to do is to select the run button when Vista prompts you as to whether or not to allow jfw.exe and FSProxy to run. You may get as many as 3 security prompts to start up a Network JAWS Client. So you can either temporarily start narrator to be able to read the initial security prompt for jfw.exe or you can just assume that you are prompted when you press enter on the JAWS icon on your desktop. Once you are prompted, press ALT+R to accept the security dialog and JAWS will start. You then will find one or two other prompts for FSProxy. You will want to allow them to be run as well. But at least you will have JAWS speech available to help you answer the other security dialogs.

If you must have UAC enabled on Windows Vista, then it is recommended that you do not do a Network JAWS installation and instead either do a standard JAWS installation or if you use roaming profiles do a "/type roam" install and then run hjadmin and setup a profile which matches the login name so that your user settings will be located in \\Program Files\Freedom Scientific\JAWS\9.0\Users\YourUserName\Settings\ENU for example and the shared settings will then be located in "\Program Files\Freedom Scientific\JAWS\9.0\Settings\ENU".

NOTE: You may also want to have the server added to the client's trusted zone so that the client does not get prompted with a warning dialog when loading the JAWS manager utilities. Why is a client version of JAWS prompt a warning dialog each time a client manager utility is launched?

---

If a Network JAWS Server is installed on Windows-XP, a Network JAWS Client installed on Windows Vista fails. (6/15/2007)

Bulletin Number: 32329
Date Posted: 6/15/2007
Product Name: JAWS
Version: 8.0 plus

Category: Network JAWS

Short Description:
If a Network JAWS Server is installed on Windows-XP, a Network JAWS Client installed on Windows Vista fails.

Problem:
If you install a Network JAWS Server on Windows-XP and you install a Network JAWS Client on Windows-Vista, the Vista client will fail. This is because there are components needed by the Vista client, such as FSProxy, which are not installed on the Windows-XP Network JAWS server.

Solution:
If you wish to run a Network JAWS Client on Windows-Vista, you will need to install and use a Network JAWS Server on another Windows-Vista. This solves the component problem because all files necessary for the Network JAWS Client to run on Vista are present and are available in the Network JAWS Server program folder.

NOTES:

It is recommended that you run a Network JAWS client under Vista with UAC turned off, otherwise you will have problems accessing UAC enabled applications which need elevated privileges. You can read more in the bulletin "If running Network JAWS as a Client in Windows Vista, JAWS cannot speak the UAC dialog."

You may also want to have the server added to the client's trusted zone so that the client does not get prompted with a warning dialog when loading the JAWS manager utilities. Why is a client version of JAWS prompt a warning dialog each time a client manager utility is launched?

---

JAWS cannot access Help files after Silent Network install. (4/29/2009)
 

Bulletin Number: 48822
Date Posted: 4/29/2009
Product Name: JAWS
Version: 10.0 plus

Category: Network Install

Short Description:
JAWS cannot access Help files after Silent Network install.

Problem:
When performing a silent network installation of JAWS, you must add PRODUCTVERSIONFOLDER to Settings.ini for JAWS to locate the help files, since the files are not installed to the default location.

Solution:
If you plan to perform a silent network install of JAWS, there are a few things you need to know in order for the help files to be accessible to JAWS.

Extracting the Setting.ini File

First, you must extract the Settings.ini from the install package using the /ExtractSettings switch. The syntax looks like the following:

C:\Temp\X /ExtractSettings c:\temp\Settings.ini
(where X is the JAWS file name, for example J10.0.1142.exe)

Note: This assumes that C:\Temp is the location of your install package. After the Settings.ini file is extracted, you can begin modifying it for your own use.

Modifying the Setting.ini File

When performing a network installation of JAWS, the help files are copied to "C:\Documents and Settings\All Users\Application Data\Freedom Scientific\JAWS\X\" (Windows XP) or "C:\Program Data\Freedom Scientific\JAWS\X\" (Windows Vista), where X is the current build being installed, for example, 10.0. The following shows the context of an install keys to give you an idea of how to modify the Settings.ini file that you extracted earlier: <\p>

[JAWSSilentServerWithSpeech]
Name = JAWS
File = msiexec.exe
; INSTALL_TYPE=8 indicates Network JAWS Server with Speech
; Set INSTALLDIR to the target folder.
Arguments = /i JAWS.msi /qn /l*v JAWS.log REBOOT=ReallySuppress INSTALL_TYPE=8 INSTALLDIR="C:\Program Files\Freedom Scientific\JAWS\10.0\" PRODUCTVERSIONFOLDER="C:\Documents and Settings\All Users\Application Data\Freedom Scientific\JAWS\10.0\"
AddSourceDir = yes

Note: The quotes are necessary because there are spaces in the path. You can also modify the installation path if you wish to install JAWS in a different location.

Running the Installer

Finally, you can run the installer. For example, if you wish to perform a SilentServerWithSpeech install, and you wish to use your modified Settings.ini file, type the following path:

C:\Temp\X /Type SilentRoam /ReplaceSettings C:\Temp\Settings.ini
(where X is the JAWS file name, for example J10.0.1142.exe)

Note: This assumes that C:\Temp is the location of both the install package and the Settings.ini file that you modified.

If you follow these instructions, the help files will be accessible to JAWS since the network installation process now looks for the files in a different location.

---