I tried RequestExecutionLevel user. It didn't prompt for a password,
but it wouldn't write any files in %programfiles%, probably because of
permissions. I can do a Just Scripts install.
It looks like if it needs to write an installer it needs admin
privileges to write in Program Files and write the uninstall info in the
registry. So how can anything that writes an uninstaller run without
admin privileges? How can I get the %appdata% before UAC does its
thing? What torture can we devise for the jerks that made all this
security necessary?
I'll have to do more research.
Gary
On 2/4/2016 3:47 AM, David Bailes wrote:
Hi Gary,
attached is the installer log when I attempt to install for current user who
has a standard account.
A couple of observations:
1. Its put the scripts in the wrong roaming profile: admin rather than the
current user.
2. When you open the installer, you immediately get a user account control
dialog, but if you only want to install for the current user, you shouldn't
have to go through one of these.
I wasnt' installing for more than one script language,
best wishes,
David.
On Wednesday, 3 February 2016, 18:05, Gary Campbell <campg2003@xxxxxxxxx> wrote:
can you still grab the installer.log file from the %programfiles%\JAWS
Script for Audacity folder?
Were you installing for more than one script language?
Thanks.
Gary
On 2/1/2016 4:14 AM, David Bailes wrote:
Hi Gary,
I came across a problem installing the script. When I tried to install for only
the current user, a dialog opened saying it could not complile audacity.jss
(details below). I then tried to install for all users, and that was fine. I
was installing from a standard user account, and then entering an admin
password in the user account control dialog.
The full text of the dialog was:
Could not compile audacity.jss, SCompile returned -1
$OutDir=C:\Users\Admin\Settings\enu, Output:
Compiling audacity.jss
Couldn't open file audacity.jss for reading
. Retry compile?
David.
On Friday, 29 January 2016, 19:51, Gary Campbell <campg2003@xxxxxxxxx> wrote:
Hi all,
I have just posted a new beta release of the JAWS script for
Audacity. This release features installer changes for
multi-language support. Currently English and Spanish are
supported. Silence Preview has also been updated to support
Audacity 2.1.2.
I am particularly interested in feedback from people with
non-English JAWS installations, since I don't have access to such an
environment.
Please note that although the installer installs and compiles the
scripts into the selected language folders, the JAWS script compiler
always compiles the script files for the language of the
currently-running version of JAWS. Therefore, after installing you
will need to run JAWS with each of the other languages and compile
the scripts "manually". This is a kind of silly implementation but
it's the best I've come up with so far given the way the script
ompiler works. I am open to any suggestions!
The script has a new home. The script is now hosted on GitHub. You
can download the 2.1.0-beta3 installer here.
The installer exe for the current "official release" is also there (although
not the same binary file, it should have been built from the same source and should be
functionally equivalent).
You can view the latest README. (This may be newer than the one in the beta 3
release.)
Let me know how it works for you.
Thanks.
Gary
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
