Adobe AIR
I have had the misfortune of looking at the full suite of CS5 and I have had moderate success "packaging" it with the proprietary s.w. to package it. However what is giving me grief is the friggen help files use AIR (f#&%*n Adobe). The install has a silent switch with accept EULA etc on install, but when the help file is triggered in (in this case) Photoshop, it presents the user with a EULA, this is not ideal (several expletives omitted)!
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
Lucid
13 years ago
Posted by:
blade2
13 years ago
Hi Lucid, thanks for the reply, sorry if it was vague.
The EULA gets accepted at install time with the .exe and a silent switch (as documented) so it is installed fine.
However when the user triggers a help file in (in this case) Photoshop which is using adobe air to present the help file the user is presented with a AIR EULA to accept. I want to stop a user seeing this.
The EULA gets accepted at install time with the .exe and a silent switch (as documented) so it is installed fine.
However when the user triggers a help file in (in this case) Photoshop which is using adobe air to present the help file the user is presented with a AIR EULA to accept. I want to stop a user seeing this.
Posted by:
dandirk
13 years ago
If I remember correctly Air creates a file in appdata which dictates if the EULA is prompted at lauch. Can't remember if this is a just a text file exist process, or a setting in a xml or something, take a look before and after first run. Since this is a per user file, eula will prompt for first run for each new user so you will have to find a solution to repair for each new user. This could be an advertised MIME entry point (sorry haven't had to do this yet) or use activesetup to run repair for each new user.
The eulaaccepted switch could be just during install, and not during run. You can find out by downloading sample air app.
You can test behavior as I said earlier by looking in appdata or local/appdata after install but before first use. After launch and accept prompt look again for the file. Copy file and do another clean install and copy file to same location and run Air again... Obviously goal is to get it NOT to come up.
The eulaaccepted switch could be just during install, and not during run. You can find out by downloading sample air app.
You can test behavior as I said earlier by looking in appdata or local/appdata after install but before first use. After launch and accept prompt look again for the file. Copy file and do another clean install and copy file to same location and run Air again... Obviously goal is to get it NOT to come up.
Posted by:
blade2
13 years ago
Posted by:
dandirk
13 years ago
Well amazing... I am working on the upgrade for this, my ex-co-worker worked on the previous version.
Working with the distributable version (which I assume is the exact same as normal downloadable... Signed up with Adobe blah blah blah
I prefer to use msi out-right so extracted the msi and files from exe.
%appdata%\Adobe\AIR contains a files called eulaAccepted (no ext) the file only contains the # "2"
I thought this would be a good time to try and create an advertised entry point for self-heal using associations, but found after an install it would be impossible. Probably could do it for .air which is generally used when installing an air application. In our case though we deploy some our air apps via custom msi (an I am not going to reinvent the wheel at this point) so the air installer is skipped entirely.
Also disabling the EULA is PROHIBITED by the adobe redistribution license, actually virtually any modification except disabling updates in an intranet is prohibited. So if this license compliance in this grey area is even remotely an issue I would not do it.
To modifiy auto-update.. place a file called "UpdateDisabled" in same dir as above. OR you can add a reg key DWORD value named UpdateDisabled to the HKey_Local_Machine\Software\Policies\Adobe\AIR registry key, and set the value to 1.
Working with the distributable version (which I assume is the exact same as normal downloadable... Signed up with Adobe blah blah blah
I prefer to use msi out-right so extracted the msi and files from exe.
%appdata%\Adobe\AIR contains a files called eulaAccepted (no ext) the file only contains the # "2"
I thought this would be a good time to try and create an advertised entry point for self-heal using associations, but found after an install it would be impossible. Probably could do it for .air which is generally used when installing an air application. In our case though we deploy some our air apps via custom msi (an I am not going to reinvent the wheel at this point) so the air installer is skipped entirely.
Also disabling the EULA is PROHIBITED by the adobe redistribution license, actually virtually any modification except disabling updates in an intranet is prohibited. So if this license compliance in this grey area is even remotely an issue I would not do it.
To modifiy auto-update.. place a file called "UpdateDisabled" in same dir as above. OR you can add a reg key DWORD value named UpdateDisabled to the HKey_Local_Machine\Software\Policies\Adobe\AIR registry key, and set the value to 1.
Posted by:
blade2
13 years ago
....disabling the EULA is PROHIBITED...Adobe are such a lovely bunch aren't they (rhymes with bankers), anyhow it is not being disabled, just pre-accepted ahead of time. I found the eula file worked (didn't have any values just a blank file); however the only way of disabling the update was to use the reg key.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.