/build/static/layout/Breadcrumb_cap_w.png

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 9.7k  |  Created: 03/21/2017 by: mjhelto

Average Rating: 0
JAWS has 1 inventory records, 0 Questions, 0 Blogs and 1 links. Please help add to this by sharing more!

Deployment Tips (3)

Most Common Setup Type
Windows Installer (Delivered as an EXE)
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 3 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (switch driven)
0
Note
Found when running the EXE with the /? flag added to it:

/?

The Freedom Scientific setup package is a tool used to install or uninstall multiple components, including the main product.  The following explains the available, optional command-line options.  These commands are not case sensitive.

/MoreHelp 
Displays additional help information, if available, about the setup package such as a list of setup types.  The installation process is not performed.  
     Example: 
     c:\package.exe /MoreHelp 
/ExtractSettings <Path-to-file> 
Outputs the contents of Settings.ini to the output file specified.  The installation process is not performed.  If the output file already exists, it is overwritten.  If there are spaces in the path to the file, the path must be enclosed in quotes.  
     Example: 
     c:\package.exe /ExtractSettings "c:\FS setup\OldSettings.ini" 
/ReplaceSettings <Path-to-file> 
Specifies an initialization file for the setup package engine to use instead of the Settings.ini file stored in the resources.  This flag can be used if any of the contents in Settings.ini must be overridden.  If there are spaces in the path to the file, the path must be enclosed in quotes.
     Example: 
     c:\package.exe /ReplaceSettings "c:\FS setup\NewSettings.ini" 
/ReplaceLanguage <Path-to-file> 
Specifies a resource DLL for the setup package engine to use instead of the resource DLL file stored in the bootstrapper.  This flag can be used to specify an alternate, external set of resources for the installation.  If there are spaces in the path to the file, the path must be enclosed in quotes.
     Example: 
     c:\package.exe /ReplaceLanguage "c:\FS setup\NewResources.dll" 
/Log [Path-to-file] 
Allows the user to specify the location of the setup package log file. Logging is enabled even if this command line argument is not specified unless the /NoLog command line argument is used. If this command line argument is not specified the setup package log file will be located in C:\Users\Administrator\AppData\Local\Temp\J18.0.2118enu_x64\FS_Setup_Package.log.  
     Example: 
     c:\package.exe /Log "c:\myFolder\mySetup.log"
     The log file is created under c:\myFolder\mySetup.log. 
/NoLog 
Allows the user to disable the creation of the setup package log file. 
/Type <name>
Specifies the setup type to use instead of the default.  To view a list of available setup types, use the /MoreHelp command-line option.
     Example: 
     c:\package.exe /type ServerWithSpeech 
/Passthru <Installer1 [, Installer2, ..., InstallerN]>@<Command>
This argument will append the specified command to the specified installers in a given package.
<Installer1 [, Installer2, ..., InstallerN]> - this portion of the argument specifies the installers which will receive the command.  Each of the Installer strings should correspond to a section name in Settings.ini.
<Command> - the command to append to each of the specified installer's command-line.  If you wish to passthrough a command that includes the characters /, - or # you must use the following escape sequences:
     Sequence     String
       #0           #
       #1           -
       #2           /
     Please note:  All occurences of # in <Command> are interpreted as the beggining of an escape sequence.  All instances of # and the character which follows the # will be replaced if a matching string can be found.  If no corresponding string can be found then the # and the character following it will be removed
  For example, the sequence ## in <Command> would be removed where as #0 would be replaced with #.
     Example:
     c:\Package.exe /passthru AnInstaller,AnotherInstaller@#2l
     Asume that the following is the Settings.ini from the above package.exe.
     ---Begin Settings.ini---
     [default]
     PreInstall = AnotherInstaller|AThirdInstaller
     MainInstall = AnInstaller
     [AnInstaller]
     Name = AI
     File = msiexec.exe
     Arguments = /i AI.msi
     [AnotherInstaller]
     Name = AnI
     File = AnI.exe
     [AThirdInstaller]
     Name = AtI
     File = AtI.exe
     ---End Settings.ini---
     The complete command-line executed for AnInstaller would be:
     msiexec.exe /i AI.msi /l
     The complete command-line executed for AnotherInstaller would be:
     Ani.exe /l

/MoreHelp

The following is additional help information about the JAWS setup package command-line options.  These commands are not case sensitive.

/Type <SetupTypeName> 
Specifies the setup type to use instead of the default.  The following is a list of available setup types:
Silent 
Silently installs a typical installation of JAWS without displaying any installation dialog boxes or prompts.
Repair 
Repairs an installation of JAWS.  Once the repair begins, you will not be able to cancel the operation.  During the repair, progress dialogs are displayed and a clicking tone is played.  At the end, you will be prompted to restart your computer.
SilentRepair 
Silently repairs an installation of JAWS without displaying any installation dialog boxes or prompts.
Safe 
JAWS is installed without making system changes.  System changes include installing video hooks in Windows NT, 2000, and XP, and installing Microsoft Active Accessibility (MSAA). 
SilentSafe 
JAWS is installed silently and without making system changes.
Remote 
Use this setup type when installing JAWS on a computer that will be accessed through a terminal session by JAWS users. Special video hooks for terminal services are installed and the virtual speech and braille drivers are set up.  If you are running the installation from a remote location during a terminal session, this setup type is automatically detected. 
SilentRemote 
JAWS is silently installed as a Remote setup.
Setup Information:
Setup Type: Windows Installer (Delivered as an EXE)
Deployment Method Used: Vendor Provided Command Line (switch driven)
Deployment Difficulty: Average
Platform(s): Windows
0
Note
To silently uninstall I found the following online:

Silent Uninstall
If you are a network administrator and need to uninstall JAWS silently, do
the following:

  1.. Press WINDOWS Key+R.
  2.. Choose the Browse button.
  3.. Navigate to the folder C:\Program Files\Freedom Scientific
Installation Information, and then select and open the appropriate GUID
(Global Unique Identifier). For JAWS, the GUID begins with the digits 356. 
The digits at the end of the GUID identify the JAWS version number.
  4.. Select the file UninstallJAWS.exe and press ENTER.
  5.. Focus returns to the Run dialog box. If necessary, press TAB to make
sure that focus is in the Open combo box.
  6.. Press END and then press the SPACEBAR.
  7.. Type one of the following:
    a.. /Type Silent - Uninstalls JAWS.
    b.. /Type SilentRemoveShared - Uninstalls JAWS and removes all shared
components.
  8.. Press ENTER.
  9.. If the User Access Control dialog box opens, choose Continue or Yes to
continue.
  10.. Follow the remaining instructions that appear to uninstall JAWS.
      Back
       Next
Setup Information:
Setup Type: Windows Installer (Delivered as an EXE)
Deployment Method Used: Vendor Provided Command Line (switch driven)
Deployment Difficulty: Average
Platform(s): Windows
0
Note
This is my batch files I made for installation and uninstallation of 18.0:

install_jaws.cmd

:: Turn echo off and clear command prompt window.
@echo off
cls
:: set program=Program Name
set program=JAWS
:: set installer=%~dp0somefile.ext
set installer=%~dp0J18.0.2118enu-x64.exe
set regFile=%~dp0JawsHost.reg
set logLoc=%~dp0Logs\Setup.log
echo Installing %program% - Please Wait
echo Started @ %time%
echo Window will close once complete.
echo.
echo.
:: Check if program exists or not
if exist "%programfiles%\Freedom Scientific\Runtime JAWS" (
echo %program% found.  Uninstall the current version and
echo then try to install again.  Exiting with error.
set EXIT_CODE=1337
goto end
)
:: Importing the registration server information
echo %program% not installed.
echo.
echo Importing %program% registration information.
regedit.exe /s JawsHost.reg
:: Make the Logs directory inside the installation directory for troubleshooting
mkdir %~dp0Logs
:: Install program
echo.
echo Installing %program%.
start /wait "%program% Installing" "%installer%" /Type Silent /Log "%logLoc%"
:end
:: Finish time
echo.
echo Finished @ %time%
:: Return exit code to SCCM
exit /B %EXIT_CODE%

Blank lines were removed from this for condensation but you can add them back in if you use it.  It will create a log directory in the installation location and dump all logs into it (there are a lot), install the software silently, and exit.  If it detects another version of JAWS it will fail the install as it doesn't seem to let you install over top of an existing install.

JawsHost.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]
"LSFORCEHOST"="YOURHOSTSERVER"


uninstall_jaws.cmd

:: Turn echo off and clear command prompt window.
@echo off
cls
:: Set "program=Program Name"
:: Only need quotes for spaces in the variable
set "programJAWS=JAWS 18.0"
set "programFS=FSReader 3.0"
set "programSentinel=Sentinel System Driver"
set "programTOC=JAWS Table of Contents"
:: These might need changed for future versions
set "JAWSuninstaller=%programfiles%\Freedom Scientific Installation Information\356DE2A8-01EB-464e-9C33-0EEA3F923000-18.0\UninstallJAWS.exe"
set "fsUninstaller=%programfiles%\Freedom Scientific\FSReader\3.0\UninstallFSReader.exe"
echo Uninstalling %programJAWS% - Please Wait
echo Started @ %time%
echo Window will close once complete.
echo.
echo.
:: Check if program exists or not
if exist "%programfiles%\Freedom Scientific\JAWS\18.0" (
:: Uninstall JAWS
echo %programJAWS% found. Uninstalling.
start /wait "%programJAWS% Uninstalling" "%JAWSuninstaller%" /Type SilentRemoveShared

:: Uninstall FSReader
echo.
echo Uninstalling %programFS%.
start /wait "%programFS% Uninstalling" "%fsUninstaller%" /Type SilentRemoveShared

:: Uninstall the Sentinel driver
echo.
echo Uninstalling %programSentinel%.
msiexec.exe /x {FAEE61D3-2A5E-4F7F-926F-77AAC08CE4DD} /qn

:: Uninstall the Table of Contents
echo.
echo Uninstalling %programTOC%.
msiexec.exe /x {7CF044D4-CFBC-4761-BDB8-7CE4513EB7BF} /qn

goto end
)
:: Program was not found so error
echo %programJAWS% not found.  Exiting.
set EXIT_CODE=1337
goto end
:end
:: Finish time
echo.
echo Finished @ %time%
:: Return exit code to SCCM
exit /B %EXIT_CODE%

This one was a bit tricky and my uninstall DOES NOT remove all the VC++ and other Microsoft shared components.  What's odd is the SilentRemoveShared flag does not remove FSReader, the Sentinel Driver, or the TOC, which remain if you don't uninstall them directly.  The above code will check to see if 18.0 is installed and if not, fail.  If it's found it uninstalls JAWS and (supposedly) all the shared content from it, the Sentinel driver, and finally the TOC.  No Freedom Scientific folders remain after doing this.

Setup Information:
Setup Type: Windows Installer (Delivered as an EXE)
Deployment Method Used: Vendor Provided Command Line (switch driven)
Deployment Difficulty: Average
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

JAWS

Version

18

Questions & Answers (0)

Questions & Answers related to Freedom Scientific JAWS

Blogs (0)

Blog posts related to Freedom Scientific JAWS

Reviews (0)

Reviews related to Freedom Scientific JAWS

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ